Communication of PM564ETH with 3rd Party SCADA & PLC via Modbus TCP
I am willing to use 2 Nos. PM564ETH as RIO nodes in a project. Total IO requirement is 120 DIs. I am planning to use DI571 module. In order to use 15 nos. module, I am considering 2 nos. CPU. I have to transmit these DIs to one Third Party SCADA and one Third Party PLC through Modbus TCP. What will be the configuration for this communication in Automation Builder & whether any logic is required to be written or only assigning the variables in global variable will do.
in configuration tree you'll have to attach Modbus TCP server protocol to Ethernet port of controller. After you need to declare global variables mapped to specific Modbus addresses (i.e wMyVar1 AT %MW0.0 : WORD;). And the last part you'll have to write a piece of code which will copy your inputs to Modbus mapped variables.
Check out this youtube video (although it's in Turkish you'll get the idea): https://www.youtube.com/watch?v=BYFve...
With AC500 PLCs, configuring them as a server is pretty simple and is how it is explained by Mr. Lurii.
In case the third party SCADA has an OPC client, you can directly fetch the data in the PM564-ETH PLCs using the AC500's Codesys OPC server installed on the SCADA Connectivity PC.
However, if you are planning to use a Modbus TCP/IP driver on the third party SCADA as Modbus client, then in the Modbus TCP IP Server settings of the AC500 PLC, you will have to select Server Connections=2. This is assuming that the 3rd party PLC will also act as a Modbus TCP/IP client to the two ABB PLCs (Modbus TCP Server).
In other words, setting Server Connections=2 will allow two Modbus clients to simultaneously communicate with an AC500 PLC.