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)

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 slaves when one slave does not accept TCP data anymore (connection is alive, but received data is not consumed by the slave)



Issue Number: 136431
Fixed on Date: 8.5.2018
Versions: 7.60 0 BUILD 49005 | 8.00 0 BUILD 48821
    • 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] ...
    • MODBUS ENERGY: Support for RTU frames over TCP/IP

      Summary The Modbus Energy driver supports communication of RTU frame via TCP/IP. Description For this purpose, the new Modbus TCP/RTU frame via TCP radio button has been implemented in the Settings tab of the driver configuration dialog. Item ID: ...
    • 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 ...
    • FAQ: How can I monitor and react on the communication status of my devices with zenon?

      Data quality is very important to the integrity of a HMI or SCADA system. As such, zenon has numerous ways to monitor the communication status of different devices within your automation environment. Here are some options that you can use in your ...
    • Checklist: Smart Client cannot establish a reliable communication

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