You can check the block status bits to see, but my old notes show FoxView
has the following standard color behavior:
OOS Hi-CYAN
DISCONNECTED LT-BLUE
BAD Hi-RED
ERROR Hi-Green
These are listed in priority, so if all the bits were true the color would
show OOS status as Hi-CYAN. For Hi-Green to show only the error bit should
be true.
I recall seeing some blocks with Green color that may have been set via
bits passed by BCALC parameters, and in some cases re-installing the block
was needed: DELETE-UNDELETE
Rick Rys
http://www.r2controls.com
On 9/15/16, 3:59 PM, "JACQUES GIRAUD" <foxboro-bounce@xxxxxxxxxxxxx on
behalf of jacques_giraud@xxxxxxx> wrote:
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
