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?

-----------------------------------------------------------------------------------------------------

On 7/7/09, Maks Wilde <mwilde@xxxxxxxx> wrote:
> Len,
> You can find more information on this in a previous thread titled "Compound
> Device/Alarm 
> Groups<http://www.freelists.org/post/foxboro/foxboro-Compound-DeviceAlarm-Groups,11>
> "
>
>
> Quoting Alex Johnson:
>
> The normal thing to do is inhibit alarm annunciation on these blocks. If
> the client won't allow that the 2nd best approach is to send the alarms
> to an alarm group that does not have any alarm destinations in it (or
> maybe only your historian).
>
> There are 8 alarm groups:
>
> 1) Groups 1-3 are defined in the compound that hold the block
> 2) Groups 4-8 are defined in the STATION block.
>
> You could define a group in your STATION block to be "empty" and
> associate this group number with the troublesome alarms.
>
> There is no penalty to doing this, but I can see a time in the future
> when someone sees this "empty" group and decides to use it for something
> else. There's no way to "comment" the use of this group in the STATION
> block so you will have to find a way to do this procedurally in the
> company.
>
>
>
> Hope this helps,
>
> Maks Wilde
>
> --
> Confidentiality Warning: This message and any attachments are intended only
> for the use of the intended recipient(s), are confidential, and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, retransmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return e-mail, and delete this message and any attachments
> from your system.
>
>
>
>
> _______________________________________________________________________
> 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: