Re: [foxboro] Auto open overlay

Both approaches so far pop the overlay up regardless of the Display on the
WP.

I don't know, but I suspect that the desired behavior is:

1) Call up display
2) While display is up, raise overlay if the bit is set (or reset or toggles
whatever)
3) Close display and have the monitoring stop.

The problem with just popping up an overlay is that it could be VERY
inconvenient for the operator and you don't know where to put it
necessarily.

So, I think the sequence block is closer since a display could start the
sequence block when it is raised. Sadly, there is no "close" display action
as there is an "open" action so the sequence block will need to monitor the
WP to see if the display is still up.

I guess I would do the following if I didn't want to write a C program:

1) Build a sequence block as described
2) Have the display put the DMNAME in a string parameter (dmcmd run
/opt/fox/bin/tools/omset -s $DMNAME C:B.SN0001) when called up
3) Have the display put the display name in a string parameter (dmcmd run
/opt/fox/bin/tools/omset -s $ST0 C:B.SN0001) when called up
4) Have the display start the sequence block using the 'setb' command on the
ACTIVE parameter
5) Have the sequence block monitor the point and the value of <dmName>ST0.
The point to trigger the overlay the ST0 Shared Variable to see if the
display is still up.
6) Have the sequence block clear the name in .SN0001 when the display
changes and stop.

This could be generalized to handle more than one display per sequence
block.


Of course, a program could be written and run on each WP to do much the same
thing if you find that easier. In this case, it would monitor ST0 for the
"right" display and consulting a database like Chris Rickers monitor the
right points. If the display changes, the trigger would not be fired until
the display is recalled.

What is really needed is the ability to trigger a script on a Boolean value
change in FV/DM, but we don't have that.


Hope this helps.



Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
For the latest information on ArchestrA, go to
www.invensys.com/Archestra.html.

 -----Original Message-----
From:   Roger Smith [mailto:RSmith@xxxxxxxxxxxxxxxx] 
Sent:   Thursday, March 27, 2003 12:14 PM
To:     'foxboro@xxxxxxxxxxxxx'
Subject:        Re: [foxboro] Auto open overlay

We monitor the alarm bit with an Independent Sequence block.  When the bit
turns, we set the DMCMD global to the overlay name or other command we want
the WP's to run.  Here is some sample code:

IF ML_TRIGGER THEN
:2WP51B DMCMD:="dmcmd run /opt/coa/prog/second/ml_popup";
:R1WPA1 DMCMD:="/opt/coa/over/second/mliquor/ml_popup.fdf";

In the first case, the display manager named 2WP51A will run a script file,
in the second case, the display manager named R1WPA1 will load a overlay
file.

Roger B. Smith
Chief, Process Control Engineering
Waste Water Services
City of Atlanta
404 350-4952

 -----Original Message-----
From:   foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Burnham, Rob C.
Sent:   Thursday, March 27, 2003 11:32 AM
To:     Foxboro List
Subject:        [foxboro] Auto open overlay


Hello List,

I would like a overlay to automatically open
when an alarm bit is set. I have the DM commands
but how do I call them based on the alarm status

Rob Burnham
Systems Engineer - Process
GLATFELTER
> http://www.glatfelter.com
Ph: 920-727-2426

Beyond Paper.....                                                       =09
  is everything we do above and beyond making great paper - that makes =
us unique.


 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 


-- No attachments (even text) are allowed --
-- Type: application/ms-tnef


 
 
_______________________________________________________________________
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:             http://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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: