5/13/2010 9:16 AM | |
Joined: 11/21/2007 Last visit: 8/12/2024 Posts: 2325 Rating: (308) |
Hello Weusing a PCS7 system to automate a process plant with approx 300 POs. Presently we are using CPU-416 with ET-200M / ET200S I/Os. We are looking for a LOW COST ( Cost is a very important factor here ) in which we can have a CPU redundency ( with limitations ), however we do not want to use PCS7 417-H and also avoid Y-Links ( Due to the cost involved ) The basic requirements are as follows : a) The process can tolerate lack of control for upto 5 minutes. b) Setpoints / settings and other data should be updated in the standby CPU continuously so that same settings are available in standby CPU in case of a changeover. We are planning a configuration as below ( Pl see attachment ) : a) 2 Nos. PCS7 racks with PS+CPU+CP443-1+1x DI + 1x DO Modules b) The Two Racks shall monitor each other through DIs / DOs for life sign and decide which CPUs is in operation. c) One of the DP Ports of the CPUs shall be coupled to each other, This will be used to Update Data Blocks from Master to Standby d) The 2nd DP Port as well as the Ethernet ports on the two racks shall have the same profibus and IP addresses. e) The Ethernet Switch (SCALANCE) and Bus Repeater of the Master CPU shall be powered on through DOs of the CPU (the Switch and Repeater of only the master shall bepowered on ) f) In case the Master CPU fails its Switch and Repeater get switched Off. The standby CPU ( After a time delay ) shall detect the failure of master CPU ( through lifebeat monitoring using DI/DOs ) and switch on its Switchand repeater and take overthe controls. We feel that ( With the obvious limitations ) the system is workable. Would like to welcome your comments on the configurations. Is there any problemwith this configuration, that I may have missed ? Or Is there a better ( and Cost Effective ) solution available ? Thanks Navnag AttachmentPCS7_Cold_Standby.PDF (75 Downloads) |
Last edited by: Navnag at: 5/13/2010 10:19 AMThere is no such thing as the last bug in a program |
|
Follow us on