Skip to main content

Modbus TCP + RTU Bridge

Status: In development: its code is written and tested on its own, but it does not work end to end on the platform yet. It cannot be installed.

KindVersionPublisherLicence
Data source1.0.0ZAITRACKApache-2.0

What it does​

Reads the configured points (coils, discrete inputs, holding and input registers) of a Modbus device over TCP, or RTU through a TCP gateway, on a schedule, scaled into readings. Exceptions and silent devices are reported, never zeroes.

  • Data it brings: time_series, event_stream
  • Filters it applies at the source: —
  • Regions: US, EU, AE, IN, CN, JP, SA
  • Capabilities: data_source.industrial.modbus.read_coils, data_source.industrial.modbus.read_discrete_inputs, data_source.industrial.modbus.read_input_registers, data_source.industrial.modbus.read_holding_registers

How to use it​

Not yet: see its status above.

Configuration​

SettingTypeRequiredAllowed values and default
endpointstringyeshost:port the device (or its serial-to-TCP gateway) answers on; a public address
transportstringnoone of tcp, rtu; tcp (Modbus TCP, MBAP) or rtu (RTU frames over TCP, through a gateway); default tcp
unit_idintegernofrom 0 to 247; The device's unit (slave) id, 0 to 247; default 1
poll_interval_sintegernofrom 10 to 86400; How often every point is read, 10 to 86400; default 60
pointsarrayyesWhat to read: a list of {name, function (coil

Credentials​

None.

Limits​

  • Memory: 256 MB
  • Time per call: 30,000 ms
  • Largest message: 1,048,576 bytes
  • Calls at once: 8
  • Network: only *

Troubleshooting​

  • It cannot reach the endpoint. The endpoint must be reachable from where the adapter runs: open the firewall for it, or run it at the edge near the equipment.
  • Values look wrong. Check the unit or node addresses and the register map of the equipment; scaling and byte order are the equipment's.
  • Reads time out. Raise the timeout within its range, or poll less often.

Source​

adapters/datasources/modbus-tcp-rtu