Issue
After upgrading EcoStruxure Building Operation, Modbus communication performance may change, older devices may generate offline alarms, and Modbus bindings between Enterprise Server and attached servers may no longer function correctly. Systems using Modbus bitmask objects may require binding updates after upgrade.
Product Line
EcoStruxure Building Operation
Environment
- EcoStruxure Building Operation 5.0 and earlier
- EcoStruxure Building Operation 6.0 and later
- EcoStruxure Building Operation 7.0 and later
- Modbus TCP devices
- Modbus Serial Client
- Enterprise Server
- Attached field servers
Cause
Changes to Modbus communication architecture introduced in version 6.0 and the Modbus bitmask structure introduced in version 7.0 can affect communication behavior and existing Modbus bindings. External bindings between Enterprise Server and attached servers are not automatically converted during upgrade.
Resolution
After upgrading from version 5.0 or earlier to version 6.0 or later, run Modbus diagnostics after several days of operation to evaluate device performance and connectivity. Based on the diagnostic results, adjust settings or configurations on Modbus devices if required.
Be aware of the following Modbus Serial Client changes in version 6.0 and later:
- Silent character is fixed at 3.5 and cannot be changed.
- Poll delay defaults to 10 ms and cannot be changed. Existing customized values from earlier versions are retained but hidden.
- Poll delay (%) is obsolete because compatible Modbus devices communicate in parallel.
When upgrading to version 7.0 or later, valid Modbus objects configured with bitmasks are converted to the new bitmask structure. Internal server bindings are updated automatically. External bindings between Enterprise Server and attached field servers must be updated manually on the server that owns the binding.
To update Modbus bindings between EcoStruxure Building Operation servers:
- In WorkStation, expand the System folder and select Upgrade history.
- Open Moved objects properties and save the content as a text file.
- Open the objects that contain external Modbus bindings.
- Right-click the object and select Edit bindings.
- Copy the existing binding path.
- Open the Moved objects file from the target server.
- Search for the copied binding path. The old and new paths are separated by "->".
- Copy the new binding path from the target server entry.
- Paste the updated binding path into the Edit bindings view on the source server.
After the binding path is updated, the binding is corrected.
Validation
Verify previously affected Modbus devices remain online and no recurring offline alarms are generated
