I forget the exact settings, but whether you get red or green on an out of
range usually depends on how the BAD and/or BADOPT are configured when an
out of range occurs. I think you get green if no BAD is configured but the
signal goes out of range, or at least if BAD is not configured to consider
the out of range condition.
Neil Martin, P.E.
Huntsman Performance Chemicals
Dayton , TX.
Dayton ph) 936-257-4212
pager) 936-522-0052
From: JACQUES GIRAUD <jacques_giraud@xxxxxxx>
To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>,
Date: 09/15/2016 03:34 PM
Subject: Re: [foxboro] the green, the red and the ugly
Sent by: foxboro-bounce@xxxxxxxxxxxxx
Thanks Scott.
Condition observed is two 4-20mA analog inputs on the same brand new
fbm201, each with its own AIN block residing in the same compound.
Open wiring on one loop - rawcounts drop to zero and block detail display
and background text tied to that point go green.
Open wiring on the other loop drops rawcounts to zero but everything goes
red.
One AIN block was created by typing from scratch in the ICC and the other
was a clone of the first one with only description and point number
changed.
I read the info at both locations you cited but I don't see either
explaining why this would be happening in my situation, one loop going
green to suggest an "UNCERTAIN" state and the other going red to suggest a
"BAD" state when open circuited.
________________________________
From: foxboro-bounce@xxxxxxxxxxxxx <foxboro-bounce@xxxxxxxxxxxxx> on behalf
of Landry, Scott <Scott.Landry@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, September 15, 2016 3:10 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] the green, the red and the ugly
Take a look at FAQ955 and SOL1563
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf
Of JACQUES GIRAUD [jacques_giraud@xxxxxxx]
Sent: Thursday, September 15, 2016 2:59 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] the green, the red and the ugly
Anyone know why seemingly random points would consistently illuminate their
background text green with white lettering instead of red with white
lettering to indicate an out-of-range condition in FoxView?
Out-of-service is always cyan as it should be but seven points in our
system decided they prefer green to red and I cannot find out why. I
checked Foxboro documentation and compared parameter by parameter in ICC
with other blocks in the same compound and it doesn't add up.
_________________________________________________________________________
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
