MODRTU32 driver stops with more than one plc on a serial connection under certain conditions

• Related Articles

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• IEC870 driver in serial communication (-101): when one connection is not reachable all the others do not communicate

  Summary Conditions: IEC870 driver, serial communication (60870-5-101), multiple connections - to few PLCs. At the start of the Runtime, if one of the serial communication is broken (e.g. 3th), the driver cannot establish the communication with the ...

• MODBUS_ENERGY: driver stops communication with all slaves when one slave does not accept TCP data anymore (connection is alive, but received data is not consumed by the slave)

  Summary MODBUS_ENERGY driver stops communicating with all slaves when one slave does not accept TCP data anymore (connection is alive, but received data is not consumed by the slave) Description MODBUS_ENERGY driver stops communicating with all ...

• Checklist: Communication to TwinCat via BeckhoffNG driver

  Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. TwinCAT ADS communication library ...

• 3S_V3 driver communication stops after executing a warm or cold restart on the PLC

  Summary The delevopment environment of Codesys V3 provides a function "warm restart" and "cold restart". If used the PLC program stops and so does the comunication. Values can be written but are not read. After starting the Soft PLC again the polling ...