Re: [foxboro] Substitution lists
- From: "Grumelart, Alain" <agrumela@xxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Fri, 2 Nov 2001 17:13:42 -0500
Tim
You can put substitution patterns in the static text portion of your text
object,
that will cause FoxView to display the substituted text (in your example,
the C:B.P name).
You an also configure a dynamic update or an operator action for your text
object
and put the substitution pattern in the object field;
then, when you call-up the display via the substitution file,
the substitution string will replace the pattern.
In your example, if you configure a text contents connection and type
<VAL1>______________ in the object field the text object would display the
value of the C:B.P
rather than its name.
If you configured a relative pick action with <VAL1>________________ in the
object field and changed the line in your substitution file as follows:
<VAL1>==PICK1 COMP:BLOCK1.PARAM
then, when you select the text field on the display, the action will store
the
C:B.P name in the PICK1 variable.
You could then have a button that calls a trend overlay that connect to
$PICK1.
I think this is what you are trying to do.
Of course there are other ways of doing this, once you understand the
principle,
you can make this as complex as you want.
Make sure you put enough trailing underscores in your patterns to
accommodate
the size of the string after the substitution, otherwise the substitution
strings
will be truncated and the connection won't work.
A word of warning ...
You should keep in mind that displays with substitution patterns never
optimize.
i.e. FoxView will always broadcast over the network to find the address of
the compound.
This may or may not be an issue depending on how much your network is
already loaded,
how much your CPs are loaded and how frequently the displays are used.
Remember that every CP and GW is adversely affected by a broadcast.
Substitution files are great to implement reusable displays but they do
carry a price
in terms of performance and overhead.
Hope this helps
Alain Grumelart Ing.
Systems Integration & IT
Invensys Process Systems
Foxboro Canada Inc.
Tel 514 421 4210 ext 8258
Fax 514 421 8054
-----Original Message-----
From: Lowell, Tim: [mailto:tlowell@xxxxxxxx]
Sent: Friday, November 02, 2001 1:35 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] Substitution lists
I have a question about substitution lists. I have created a display in
FoxView that is opened by a substitution list. The substitution list looks
like this:
dmcmd subslist /usr/menus/d1/SUB_DISPLAY.fdf
<VAL1>=COMP:BLOCK1.PARAM
<VAL2>=COMP:BLOCK2.PARAM
etc.
On the display in /usr/menus/d1/SUB_DISPLAY.fdf are normal text fields
configured for <VAL1>, <VAL2>, etc that get filled in by the substitution
list. My problem is, I want to be able to click on the normal text field
filled in by <VAL1>, <VAL2>, etc and say, open a trend of that C:B.P. How
do you tell FoxView that the value you want to send to the trend is the one
contained in <VAL1>, for example? I tried using $<VAL1> or `<VAL1>`, but
neither of these worked. It seems as though FoxView completely forgets what
<VAL1> refers to once the substitution list is done executing. Using the
"@" sign doesn't work either, because it evaluates that as the floating
number represented by <VAL1>, not the C:B.P. Anyone else ever try this?
Tim Lowell
Control Systems Engineer
Phillips Petroleum Company, Trainer Refinery
Phone: 610-364-8362
Fax: 610-364-8211
tlowell@xxxxxxxx
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist
list info: //www.freelists.org/list/foxboro
subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist
list info: //www.freelists.org/list/foxboro
subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
