Re: [foxboro] I/O Bad Problem
- From: "Doucet, Terrence" <tdoucet@xxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 15 May 2006 13:56:05 -0400
Look at BADOPT in your AIN blocks. You likely have BAD + HOR + LOR
Code 3
If you set BADOPT =3D 0 it will ignore HOR and LOR
Your digital inputs do not have HOR or LOR so that is likely why
You get more bad states for your Analog blocks.
Terry
-----Message d'origine-----
De=A0: foxboro-bounce@xxxxxxxxxxxxx =
[mailto:foxboro-bounce@xxxxxxxxxxxxx] De la part de prabhakar
Envoy=E9=A0: May 15, 2006 1:49 PM
=C0=A0: foxboro@xxxxxxxxxxxxx
Cc=A0: brad.s.wilson@xxxxxxxxxxxxxx
Objet=A0: [foxboro] I/O Bad Problem
Dear All,
Can anyone tell me why do we face I/O Bad problem with Analog Inputs =
more=20
often than digital inputs. IS ther any option in Foxboro ICC for =
filtering=20
Cyan or I/O bad in DIgital inputs. Of course there is option for Analog=20
inputs
Do we hav to write a calca for avoiding this
rgds
Prabhakar
Instrumentation Engineer
Refinery,
RIL,India=20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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: