earth_america
user_standard Anmelden
action_search_stroke
earth_america
Log on to rate and give feedback 1 2 3 4 5 Log on to rate
0
Ratgeber

Ratgeber


Produkte: AS-B, AS-P, Project Configuration Tool
Funktionen: Modbus
Produktversion: 7.0
30.04.2025

Updating Modbus Bindings between EcoStruxure Building Operation Servers

You update Modbus external bindings between Enterprise Server and attached servers or between automation servers after upgrading from version 6.0 and earlier to version 7.0 and later.

Mehr zeigen
action_close

Depending on your system Modbus might need to be updated.

Modbus Diagnostics after Upgrade from Version 5.0 to Version 6.0

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.

Modbus Bitmask Structure and Bindings after Upgrade to 7.0

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 .

To update Modbus bindings between EcoStruxure Building Operation servers

  1. In WorkStation, in the System Tree , expand the System folder, and click the Upgrade history folder.

  2. In the Upgrade history folder click the Moved objects properties and save the content as a text file.

  3. In WorkStation, open the objects that have external Modbus bindings.

  4. Right-click and click Edit bindings .

  5. Copy the binding in the object.

  6. Open the Moved object file from the server that is the target.

  7. Search for the binding that you copied from the Modbus object in the Moved object properties.

    The old path and the new path are separated by "->".

  8. In the Moved object file, copy the new binding path on the target server.

  9. In the Edit bindings view, paste the new, correct, binding on the source server.

The binding is now correct.

Siehe auch

  • Modbus Upgrade
  • Methods of Binding
  • Bindings View
  • Modbus Diagnostics Properties - Basic Tab
  • Binding Values Manually
  • Selecting a Binding in Bindings View