MODBUS_ENERGY: multiple stations with different Modbus Unit ID and one IP address: driver crashes in the runtime when the driver is stopped
Summary
MODBUS_ENERGY driver - Issue when the option join connections is active. If the MODBUS gateway is disconnected and connections to this gateway exist which have not yet been activated (no variable of the connection has been requested since runtime start) the driver stops working.
Description
MODBUS_ENERGY driver - Issue when the option join connections is active. If the MODBUS gateway is disconnected and connections to this gateway exist which have not yet been activated (no variable of the connection has been requested since runtime start) the driver stops working.
Information
delet the variables with this driver
Issue Number: 171694
Fixed on Date: 9.1.2019
Versions: 8.00 0 BUILD 55271 | 7.60 0 BUILD 56016 | 8.10 0 BUILD 57250 | 8.20 0 BUILD 65124
Related Articles
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: ...
Modbus_Energy driver: Status of TCP/IP connection is not displayed
Description For variables from the Modbus Energy driver, the status of the TCP/IP connection is not displayed in the Service Engine for suitable elements. This behavior has been changed. The connection status is now displayed. To benefit from this ...
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 ...
MODBUS_ENERGY: Variables remain without value / status under specific circumstances
Summary Under specific circumstances, the MODBUS_ENERGY driver configured to bundle connections has connections for which variables remain without value and without status, due to connectivity issues for another connection using the same IP address. ...
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] ...