Re: [foxboro] Opening overlays automatically
- From: "Brian Hueni" <Brian.Hueni@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 15 Jul 2008 10:20:57 -0500
David,
One other thing to protect for is the scenario where the workstation that
the dmcmd command is issued to is down/offline/etc. Without error checking
during this scenario, the sequence will fail to manual with a -45
(setconfirm error). This can be prevented by implementing a TO_SYS_ERROR
SBX. The TO_SYS_ERROR SBX would be similar to that below. The action code
would need to be surrounded with an IF construct to bypass the callup based
on an auto-callup active flag (AUTO_CALLUP). Since other setconfirm errors
will throw a -45 as well, we can set/unset a flag (DMCMD_SET) before/after
to know that the auto-callup is the offender.
I've set this type of code up on a few batch units where the operator has
the option to turn on (and off) the auto-callup to cause the displays to
follow the batch processing. The same mechanisms also work well to have
sequences launch shell scripts and other applications at the workstation
level.
SBX Code Snippet:
BLOCK_EXCEPTION TO_SYS_ERROR
...
IF (OP_ERR = -45 AND DMCMD_SET) THEN
AUTO_CALLUP := FALSE;
ENDIF;
...
Subroutine Snippet (note the snippet would now need to be in a subroutine):
...
/* Open Alert Overlay */
IF (AUTO_CALLUP) THEN
DMCMD_SET := TRUE;
:OV_DM :=3D "dmcmd ov ",OV_Alert," -l UR";
DMCMD_SET := FALSE;
ENDIF;
/* Close Alert Overlay */
IF (AUTO_CALLUP) THEN
DMCMD_SET := TRUE;
:OV_DM :=3D "dmcmd close -name ",OV_Alert;
DMCMD_SET := FALSE;
ENDIF;
...
Brian Hueni
Principle Solutions Architect
Strategic Automation Services, LLC
Suite 303
16360 Park Ten Place
Houston, Texas 77084
T: 1.713.494.0365
F: 1.866.483.7164
E: Brian.Hueni@xxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Badura, Tom
Sent: Monday, July 14, 2008 4:17 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Opening overlays automatically
David,
We do something like this to alert and get the operators attention now
that we have moved to Foxview. We used to use the button blink command
in Display Manager, but that does not exist in Foxview. Essentially the
AlertOverlay is a small display (overlay) that we position in the upper
corner of the process graphic. We usually configure it to blink and may
add a pick to take the operator to a specific display (rather than just
changing the graphic they are looking at). DMNAMEDMCMD is the name of
the DM plus DMCMD which is a global variable that can use to write DM
commands to the DM or Foxview from sequence code (i.e. DM001DMCMD).
Below is a generic HLBL snippet. Maybe this will do what you want. See
document B0193DF - I/A Series System Display Manager Commands for a full
explanation. Note that this will only open the overlay on the specified
DM.
#define OV_DM DMNAMEDMCMD
#define OV_Alert "/usr/plenco/overlays/AlertOverlay"
WAIT UNTIL Some_Condition;=09
/* Open Alert Overlay */
:OV_DM :=3D "dmcmd ov ",OV_Alert," -l UR";
WAIT UNTIL NOT Some_Condition;
/* Close Alert Overlay */
:OV_DM :=3D "dmcmd close -name ",OV_Alert;
Tom Badura
Plastics Engineering Company
920-458-2121 x3366
tbadura@xxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Nimmons, David
Sent: Thursday, July 10, 2008 2:53 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Opening overlays automatically
Hello Ya'll,
I have been tasked with developing an overlay that will open
automatically on either a periodic basis or in response to process
conditions and I am not finding an easy way to do this. Can somebody
point me in the right direction?
Thanks in advance
David Nimmons
DCS Technician
Flint Hills Resources
Odessa, TX
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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:
