Re: [foxboro] Help sought on Configuring Trend displays in DM

  • From: "Kubbenga, Otto" <okubbeng@xxxxxxxxxxx>
  • To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
  • Date: Tue, 1 Jun 2004 04:47:06 -0400

Hi Maneesh,

Basically g_edit is not able to update text fields.  But how it works might
accomplish that what you are looking for.
The g_edit update function removes first the entire group (faceplate), then
adds the group from the Faceplate library (using the block type as the group
name), then updates the faceplate/group connections.  During this process,
text connections (like description and eng. units) will be removed and the
text field will be substituted with the actual OM block parameter value.
I.e. the block must be configured and online (g_edit is not able to access
ICC database).  So updating a description can be done by updating the
faceplate. Custom (user) faceplates (per blocktype) can be built to make
your own template. 


I hope this answers your question.

Regards
Otto 


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Maneesh.Agrawal@xxxxxxxxxxxx
Sent: maandag 31 mei 2004 19:17
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Help sought on Configuring Trend displays in DM

hi list,
 Duc and Otto,thanks for the suggestion.We were able to use the g_edit 
utilities to configure our group displays and trend displays.
I need one more help from the list.
We were succesful in creating the required tend displays with the correct 
ranges,but were unable to get the historian name and the description for 
each tag in the trend displays.
1.I understand that by editing the historian name in the gdblk50,.db file, 
the historian name gets updated,.Can somebody give the exact syntax 
required for the same as these scripts are very syntax-specific.
2.Is there a way to update the descriptions which are same as that in the 
ICC in these trend displays by editing the configuration file, If yes 
which  file needs to be modifired and what will be the syntax?

Thanks & Regards,
Maneesh Agrawal,
Systems Engineer,Invensys Middle East,Kuwait Operations.





"Kubbenga, Otto" <okubbeng@xxxxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
05/22/2004 11:24 PM
Please respond to foxboro

 
        To:     "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
        cc: 
        Subject:        Re: [foxboro] Help sought on Configuring Trend
displays in DM


Correct,
you may use g_edit50 to build/update display files as used by the old
Display Manager (20 and 50 series).  Documentation and examples are 
available.  However, g_edit does not build FoxView (.fdf) displays. 

Regards,
Otto Kubbenga

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
On
Behalf Of duc.do@xxxxxxxxxxxxxx
Sent: donderdag 20 mei 2004 15:57
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Help sought on Configuring Trend displays in DM

Maneesh,

Have you checked out g_edit (/usr/fox/wp/bin/tools/g_edit)? Not the 
easiest
of utilities to master, but it'll do exactly what you want.

Duc

-- 
Duc M. Do
Dow Corning Corp.
Carrollton Plant
Carrollton, KY, US


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of
Maneesh.Agrawal@xxxxxxxxxxxx
Sent: Wednesday, May 19, 2004 3:24 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Help sought on Configuring Trend displays in DM


hi list,
Does anybody know/have any scripts or utilities that would help to 
configure the standard full page trend displays in the Display Manager?
We have to configure around 50-60 trend displays and were thinking of a 
possibilty of having a text file with the required info like C:B.P, the 
ranges, historian name etc and run the scripts or utilities to generate 
these displays.

Thanks & Regards,
Maneesh Agrawal,
Systems Engineer,Invensys Middle East,Kuwait Operations.

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 




 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: