Skip to content
English
  • There are no suggestions because the search field is empty.

Understanding Modbus Communication in Enbase

Learn how Enbase uses Modbus to exchange data with external devices over serial and TCP networks and how Modbus data is represented in Enbase.

Modbus is an industrial communication method supported by the Enbase Hub for exchanging data with compatible controllers, meters, and other field devices.

How Enbase Uses Modbus

The Hub can communicate with Modbus devices over serial or TCP networks and store returned values in Enbase Tags.

As Tags, the values can be displayed and, when configured, trended, logged, or used for alarms.

Modbus Master and Modbus Slave

Depending on the application, the Hub can communicate in two common ways:

  • As a Modbus Master, the Hub requests data from compatible Modbus Slave devices.
  • As a Modbus Slave, the Hub can make selected Tag data available to an external Modbus Master.

The exact configuration depends on the installation and should be managed by authorized personnel.

Modbus Over Serial and TCP

Enbase supports Modbus over serial and TCP. The Hub also supports advanced Modbus passthrough for certain installations where multiple systems share a Modbus network.

What Does a Modbus Communication Problem Look Like?

If Enbase cannot retrieve a Modbus value, the affected Tag may show a Scan Error. Grid View provides Scan Status and Scan Error counters for troubleshooting.

Modbus mapping, port settings, network addresses, Channels, and Tasks are advanced settings. Contact Enbase Support before changing them or if Modbus data stops updating.