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

How Enbase Communicates With External Controllers

Learn how the Enbase Hub can receive data from external controllers using supported industrial communication methods such as Modbus and CAN/J1939.

The Enbase Hub can collect data from sensors and I/O and can also communicate with external controllers and other industrial devices.

This allows Enbase to monitor data already available inside another controller.

Supported Communication Methods

The method depends on the external device and installation. Supported methods described in Enbase documentation include:

  • Modbus over serial communication.
  • Modbus over TCP networks.
  • CAN/J1939 communication.
  • Cat Data Link in supported compressor controller applications.

How External Controller Data Appears in Enbase

Data from an external controller is typically represented as an Enbase Tag so the value can be displayed and, when configured, trended, logged, or alarmed.

Examples include engine speed, equipment status, shutdown information, alarms, and diagnostics.

Channels and Tasks

Inside the Hub, communication ports are represented by Channels, and built in Tasks use those Channels for functions such as Modbus or J1939 communication.

Channel and Task properties are advanced configuration. Do not change port assignments, baud rates, protocol Tasks, or related properties unless instructed by Enbase Support.

Why Communication Configuration Varies

Controller protocols, addresses, settings, and wiring vary by installation. Contact Enbase Support when adding or replacing a controller or troubleshooting missing controller data.