Program

We recommend you, to use an AC500 PLC node (Automation_Builder configuration + program) download to both PLCs, create boot project in both and restart the complete system.

We recommend you, to use the IP address of CPU A as IP1 in HA_CS31_CONTROL function block.

HA-CS31 utility function blocks are synchronized internally. Any other synchronization requirement is to be done through HA_CS31_DATA_SYNC function block.

Restart the complete system if any of the HA-CS31 library function blocks changed. Else the system may become unstable as HA library function blocks are not supporting online changes.

If online program modification is required on a running high availability application (e.g. additional variable, number or type of the variable in HA_CS31_DATA_SYNC), it is necessary to restart the whole system to recreate synchronization.

SFC language (Sequential Function Chart) is not recommended for HA programming as too much and too spread data is to synchronize.

If web visualization is required, the following setup is recommended: Onboard ETHERNET for web server and OPC & Automation_Builder communication, CM577-ETH for HA data synchronization, refer to Requirements.

For web visualization users have to use onboard ETHERNET slot. If a user has a PLC with more than one onboard ETH port (Example: PM595, PM591-2ETH) the user can use ETH1 port for UDP Data exchange and ETH2 for web server.

If a user is using a PLC with one onboard ETH port and requires web visualization, then use onboard ETH for web visualization (CM577-ETH does not support web server) and CM577-ETH for UDP data exchange. This change may be able to make some impact on UDP data exchange performance as CM577-ETH port has a lower priority than the PLC on board port.

Use DigiVis and OPC server for writing data as it will be written to both PLCs at the same time. We recommend you, not to use HMI for writing data as it is not written to both PLCs.

Note

PM591-2 ETH and PM595 PLCs must use onboard ETH1 for UDP data communication.