[foxboro] Fw: peer 2 peer loop strategy conclusion
- From: Ajit.S.Kumar@xxxxxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 2 Apr 2012 01:29:23 +0300
Thanks Timothy,
True....we have it in different CP. However we have the AOUT of one block
(channel) connected through hardwired to AIN of the another block in
different CP controlling the process. The reason is both are located in a
different instrument house. The design concept was to avoid P2P due to
complexity of the loop originally. Now to reconsider the loop strategy can
this be connected as P2P if yes then was are the consequences in case of
P2P failure.
ESD System's do not permit Soft linkages or P2P as in the case PLC to DCS
it is hardwired.
Thanks and best regards
A.kumar
----- Forwarded by Ajit S Kumar/Technical/SAMREF/SA on 04/02/2012 01:19 AM
-----
From: "Lowell, Timothy" <Timothy.Lowell@xxxxxxxxxxx>
To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
Date: 04/02/2012 01:17 AM
Subject: Re: [foxboro] peer 2 peer loop strategy conclusion
Sent by: foxboro-bounce@xxxxxxxxxxxxx
Perr-to-peer refers to loops that have connections across Control
Processors, not between two FBM's that are hosted by the same Control
Processor.
The disadvantage of peer-to-peer
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Ajit.S.Kumar@xxxxxxxxxxxxx [Ajit.S.Kumar@xxxxxxxxxxxxx]
Sent: Sunday, April 01, 2012 3:43 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] peer 2 peer loop strategy conclusion
Dear All,
Suggestions required, Thanks in advance.
What are the advantages/disadvantages of P2P communication in an complex
loop.
We have few control loop hardwired between FBM's due to complicity but
need to find a better way to avoid FBM failures or Open wires which drives
the complex loops to plant upset.
Is P2P a better industrial way in the Refinery Applications. The present
scenario is to convert the FBM to redundant type, but still we need a
better answer to use P2P.
Thanks and best regards
A.kumar
_______________________________________________________________________
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: //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: //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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
- » [foxboro] Fw: peer 2 peer loop strategy conclusion - Ajit . S . Kumar
