Depending on your system Modbus might need to be updated.
EcoStruxure Building Operation 5.0 and earlier versions use round-robin scheduling for communication among Modbus devices. In EcoStruxure Building Operation 6.0 and later, round-robin scheduling is only used within the Serial client. For TCP connections, communication is always enabled, allowing each Modbus device to have its own network queue and TCP connection processing. This change results in significantly faster communication speeds among multiple devices.
However, after upgrading from EcoStruxure Building Operation 5.0 or earlier to EcoStruxure Building Operation 6.0 or later, you might experience slower communication or an increase in offline alarms, especially with older Modbus devices. It is recommended to diagnose the Modbus devices a few days after the upgrade.
Für weitere Informationen siehe Opening Modbus Diagnostics .
Based on the results of your diagnostics, you may need to make adjustments to your Modbus devices.
When upgrading to version 7.0 or later, all Modbus objects configured with bitmasks are converted to the new bitmask structure, as long as they have valid settings. For example, if you have three Analog Input points with read code 4 (Read Input Registers) for register 101 in version 5.0, they will be transformed into a Bitmask Input Register for register 101. This new register will contain three Integer Input bitmask objects. All bindings within the server will be updated accordingly.
However, bindings between an Enterprise Server and attached field servers are not automatically converted. These bindings must be updated manually.
Modbus bindings must be updated on the server that owns the binding.
Für weitere Informationen siehe Updating Modbus Bindings between EcoStruxure Building Operation Servers .