Re: [foxboro] Use of null device groups
- From: Corey R Clingo <corey.clingo@xxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 9 Jul 2009 02:28:19 -0500
The issue I know of with "group 0" is that while you can configure this in
ICC, you cannot change it to 0 from the detail display. Apparently the
graphic is configured to limit the range to a low value of 1, at least in
DM.
It is not a problem if you never touch it after configuration, but if you
change it to something else from the detail, you cannot change it back.
And this parameter is not connectable, so locking it is not an option.
You could I guess change the detail displays, or set protection classes on
them to prevent operator changes, or even have an "enforcer" program keep
resetting the group to 0. I took the easy route and just decided to use a
group with no devices instead. The docs _do_ say 1-8 after all...
Corey Clingo
BASF Corp.
Len Collinge <lencollinge@xxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
07/08/2009 02:57 PM
Please respond to
foxboro@xxxxxxxxxxxxx
To
foxboro@xxxxxxxxxxxxx
cc
Subject
Re: [foxboro] Use of null device groups
Thanks, however I haven't seen a definitive responce on using group 0.
Is Device Group 0 a valid null device for today and forward?
Reference the following pasted question from Joseph.
-------------------------------------------------------------------------------------------------------
From: "Joseph M. Riccardi" <Joe@xxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Date: Fri, 13 Jun 2008 12:03:46 -0400
Maybe something has changed over the years, but I also used to use Group
0 as LaLa Land (nowhere). However, I notice lately that this trick no
longer works. Can't remember the details, but either the block would
not accept Group 0, or it retained the previous value. Has something
changed that would prevent Group 0 from being a valid value for LaLa
Land?
_______________________________________________________________________
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: