Re: [foxboro] BADOPT=3 and OSV

Turn "CEOPT" off (set to zero) on your controller block.




Please respond to foxboro@xxxxxxxxxxxxx
Sent by:        foxboro-bounce@xxxxxxxxxxxxx
To:     "'Foxboro - Cassandra'" <foxboro@xxxxxxxxxxxxx>
cc: 

Subject:        [foxboro] BADOPT=3 and OSV



This weekend we ran into a situation that caused some critical 
transmitters to hit the high end of their scale and exceed the default 2% 
OSV.  Since we use BADOPT=3 this marked these AIN's as bad causing 
undesired control action (since the transmitters were not truly BAD).

Could someone share their philosophy or rules used for setting OSV's?  We 
don't want to make the OSV too large as to render this feature useless. 
Also, I want to keep the instrument departments involvement to a minimum.

Thanks,
Rory Loupe
Dow Chemical



_______________________________________________________________________
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: