SYNPOL D CMA135 3EDDE300415 端子板

If you use OPC server software and have redundant PLCs, the software communicating with these PLCs must be able to support this architecture. CMA135 software needs to know which PLC is the main PLC, which is the auxiliary PLC, what conditions will cause a fault to transfer to the auxiliary PLC, and when to switch back to the main PLC.

Ideally, the software will also provide you with a way to monitor and display which PLC (primary or auxiliary) the OPC server is communicating with in the HMI, SCADA, or alarm system.

Software and IT hardware system redundancy
Diagram – Dual Redundant Hardware and Networks We don’t want to stop here, CMA135 makes computers running OPC servers a single point of failure. This means we need redundant OPC servers on redundant PCs. For this reason, our OPC client can support redundant OPC servers.

Supporting redundant OPC servers means that the OPC client – your HMI/SCADA system, alarm system, MES system, or other system – will need to know which OPC server to communicate with. You also need to decide whether you want two OPC servers to poll your device simultaneously, or whether you want one OPC server to poll, with the backup server on standby but not polling. By managing the activity status of projects in the OPC server (which is the responsibility of the OPC client in the OPC client server relationship), these two situations can be achieved.