Skip to content

Modbus TCP

CONNECT works as a Modbus TCP client (drives, sensors, gateways) or as a server that an external PLC, HMI or SCADA system connects to as master.

ParameterExample
Host / Port192.168.1.60 / 502
Unit id1
Word orderABCD, CDAB, BADC, DCBA
Connection timeout10000 ms (default) — bounds the connect and every read and write

Addresses name one of the four standard tables plus an offset, with an optional bit suffix:

PrefixTableWritable
HRHolding registeryes
IRInput registerno
CCoilyes
DIDiscrete inputno

Both notations are accepted: classic five-digit Modicon (HR40001 = offset 0, C00013 = offset 12) and the modern short form (HR0, C12). HR40010.3 addresses bit 3 of a holding register.

Modbus RTU is reserved in the configuration but not yet implemented.

CONNECT listens as a Modbus slave; an external PLC, HMI or SCADA system connects to it as the master. The address model is the same as the client, but the direction is reversed. The server must be able to write values that a client can only read.

  • Manually. Enter the table prefix and offset: HR40001 (classic Modicon) or HR0, C12 (short form), HR40010.3 for bit 3 of a holding register. The dialog shows examples and validates the address with the parser the interface uses at connect time.
  • Browse. No browse: Modbus has no mechanism to ask a device what it offers. Enter addresses by hand.
  • File import. No protocol-specific file import.
  • From the model. Use Addresses → Import address table… in the signal-mapping section of the CONNECT panel: a CSV or TSV with name;address[;dataType[;topic]] rows, where the name is the model’s signal name. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. Fill from controller… has nothing to match, because this protocol cannot be browsed. See Configuring interfaces.

How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.