Re: [foxboro] FoxView Overlay
- From: "Heath, Graham" <Graham.Heath@xxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 24 Feb 2014 03:43:16 -0500
Further thought which we have used on several projects
One issue with all that has been proposed is that the visibility is either
system wide or AW wide (think of the case where you have server running 10
FoxViews).
We used a script that runs on start-up of each AW to generate a boulean shared
variable for each DM in the form 'DMNAME'VIS. The Visibilty connection is in
the form $DMNAMEVIS. As is the action that toggles the shared variable
Local shared variable so no network traffic
Only affects local Foxview
Our script uses the dmcfg file to get the dmnames existing on each box so no
configuration either.
Cheers Graham
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Lowell, Timothy
Sent: 21 February 2014 21:48
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxView Overlay
Richard,
Expanding on Alex's comment...
For a limited number of connections, you can create a dummy CIN block with
IOMOPT of zero that serves this purpose. Just assign the .CIN value of this
block to the Visibility parameter of your overlays. Then you can have a little
button on the screen that toggles the value of this CIN block from 0 to 1. This
will toggle the visibility of the objects on the screen that are configured
with the .CIN in the Visibility field.
If you want to make this a site-wide thing on many graphics, you will want to
use a DM variable. DM variables can be created in
d:\usr\fox\bin\data\init.user. You can create a DM variable called something
like FOXDISPVIS, and then assign the visibility of your sub-overlays to this
variable (using the reference $FOXDISPVIS, for example). The advantage of DM
variables is that if you have a ton of objects configured this way, they won't
all be taking up network bandwidth checking that CIN block each time the screen
updates. DM variables are self-contained within the AW and the only resources
used are CPU time and RAM. The downside is that you have to edit init.user on
every station where you want to create and use a DM variable, and then maintain
that edit through every Day Zero.
As Alex said, the p1 through p8 DM variables also exist for things like this,
but if you use one of these, you need to remember which one is used for which
function. It's a little easier to maintain and understand if you declare a
variable specifically for this function.
Thanks,
Tim
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Coon, Richard M
Sent: Friday, February 21, 2014 3:01 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FoxView Overlay
Is there a way to show/hide objects in overlays? I would like to use
pushbuttons to show/hide or call up sub overlays similar to the detail display
components.
Regards,
_______________________________________________________________________
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
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please select the Legal Entities link at invensys.com.
Invensys PLC is owned by the Schneider-Electric Group.
You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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:
