Re: [foxboro] FW: parameter state at CP boot
- From: David Johnson <drjohn@xxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 30 Jan 2006 10:17:32 -0600
I haven't seen much mention of the PLB COMMF - FAILSF bits. But if you are
using PLB for discrete I/O you can do something like the following.
You may have to line it up a bit.
COMMF OFL_1
---| |--------------------------------------------(L)---
CP-FBM Comms
CommFlt Failed
OFL_1 FAILSF
---| |--------------------------------------------( )---
Comms De-Eng
Failed Outputs
IFL_1 OFL_1
---| |-------------------------------------------(U)---
Operatr Comms
Reset Failed
Regards,
David
_______________________________________________________________________
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
- References:
- Re: [foxboro] FW: parameter state at CP boot
- From: Pauwels, Dirk - RSM
Other related posts:
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- » Re: [foxboro] FW: parameter state at CP boot
- Re: [foxboro] FW: parameter state at CP boot
- From: Pauwels, Dirk - RSM