Skip to main content

Modbus TCP

The printer has a built-in Modbus TCP server. A PLC, or any other Modbus client, can use it to:

  • read printer status, such as ready, printing and ink low,
  • run printer actions, such as starting the ink system or aborting a print,
  • select what to print, by label name or by looking up a key in a table,
  • read and write counters, variables and the line speed,
  • read production statistics,
  • exchange data with software running on the printer, such as an extension.

Nothing is exposed by default. Each coil and register the PLC can use is mapped in the printer settings to a signal, action, counter, variable or other target. The set of mappings is specific to each installation.

Who does what​

A Modbus integration usually involves two roles, often two different people:

  1. The integrator configures the printer: enables the Modbus server and creates the mappings. See Printer setup.
  2. The PLC programmer writes the PLC program against the mapping list exported from the printer.

The mapping list says which coils and registers exist on a given printer. This documentation describes the rules that are the same on every printer: how to address them, how values are encoded, and what each kind of mapping does.

At a glance​

ItemValue
ProtocolModbus TCP
RoleThe printer is the server (slave), the PLC is the client (master)
Port502
Unit identifierIgnored
CoilsSignals and actions, addresses 0–65535
RegistersCounters, variables, statistics, speed, print job selection and storage registers, addresses 0–65535
Byte orderBig-endian, high word first for 32-bit values

Where to start​

The examples throughout this section use one printer with the ID NoLabel, and the example mapping list shown in The mapping list.

tip

Software running on the printer can read and write named storage registers with the Aurora API Modbus methods. See Internal register.