IO-Link Explained: How It Works, What It Adds, and When to Use It

What Is IO-Link?

IO-Link is a standardised point-to-point serial communication protocol defined by IEC 61131-9. It operates over the same unshielded 3-wire M12 cable used for conventional binary sensors and adds a bidirectional digital channel on pin 4 (C/Q).

An IO-Link device can be a sensor, actuator, or RFID reader. The corresponding port on a PLC or remote I/O module is called the IO-Link master. Each master port connects to one device — there is no shared bus.

Key benefits over traditional analogue or binary interfaces:

• Multiple process values in a single cycle (e.g., distance + temperature + output logic state from one sensor)
• Remote parameterisation — change sensing range, setpoints, or output logic from the PLC without physically touching the sensor
• Standardised diagnostics — device fault codes accessible from the control system
• Auto-device replacement — stored parameter sets download automatically to a replacement sensor
• No calibration drift — the signal is digital end-to-end, unlike 4–20 mA which accumulates noise and loop resistance errors

IO-Link was developed by a consortium now managed by the IO-Link Community (part of PROFIBUS & PROFINET International). As of 2025 there are over 40 million IO-Link nodes installed globally and more than 5,000 certified device types.

Physical Layer

IO-Link reuses the same hardware found on any standard DI port:

The C/Q pin is modulated with the IO-Link signal by the master. Prior to the master initiating a wake-up sequence, an IO-Link capable device behaves as a standard DI/DO — it falls back to SIO mode (Standard Input/Output). This means you can plug an IO-Link sensor into an ordinary DI card and it still works as a binary switch; you just lose the IO-Link features.

The 20 m cable limit is generous for machine-level wiring. For longer runs, IO-Link hubs or repeaters can extend reach, but each segment remains ≤ 20 m.

Communication Modes

IO-Link defines three baud rates, called COM modes:

The master automatically negotiates the COM mode with the device during the wake-up handshake. COM3 at 230.4 kbaud gives a minimum cycle time around 0.4–2 ms for a 2-byte process data device, which is fast enough for most sensor feedback loops.

A single IO-Link frame carries:

• Process Data Out (PDO) — control data from master to device (e.g., output channel state)
• Process Data In (PDI) — measurement data from device to master
• On-Request Data (OD) — service channel embedded in each cycle for parameter read/write or event notification

Process data size is 1 to 32 bytes in each direction, defined by the IODD file. A simple on/off sensor might send 1 bit of PDI; a multi-function flow sensor might send 8 bytes (flow rate, temperature, totaliser, status flags).

Process, Parameter & Event Data

Process Data

Process data is exchanged in every IO-Link cycle. It is the equivalent of the signal on a 4–20 mA loop — the primary measurement value — but in digital form and potentially containing multiple values simultaneously. The master maps process data into standard PLC I/O memory.

Parameter Data (Acyclic)

Parameters are read or written via the on-request service channel — acyclically, outside the normal process data exchange. Typical parameters include:

• Sensing range setpoints (near/far limit switches on ultrasonic sensors)
• Output logic polarity (NO/NC)
• Engineering unit selection (mm / inches, °C / °F)
• Filter time constants
• Tag name stored in the device (useful for maintenance)

Parameter writes do not interrupt process data exchange. The master schedules the write in the OD channel during normal cycling.

Event Data

Devices can asynchronously signal events: temperature overrange, contamination warning, wire break detected, configuration changed. The master reads the event code and can pass it as a diagnostic alarm to the PLC application. Event codes are standardised in the IO-Link specification so different vendors' alarms map to the same codes in your SCADA.

Device Identity

Every IO-Link device holds a Vendor ID, Device ID, and serial number in its identity object (index 0x0010–0x0017). The master can read these automatically and verify that the correct device type is wired to each port — providing automatic type checking that is impossible with 4–20 mA.

IODD Files

An IO Device Description (IODD) is an XML file provided by the sensor manufacturer. It describes everything the master needs to communicate with that specific device:

• Vendor ID and Device ID (for identity matching)
• Process data structure — byte layout, data types, engineering units
• All parameters — index, subindex, name, data type, min/max, default values
• Event codes and their text descriptions
• Device image (JPEG) for display in engineering tools

Engineering tools load IODDs from the IODD Finder (ioddfinder.io-link.com) or from a local library. Once imported into TIA Portal, Studio 5000, or CODESYS, the tool auto-populates the port configuration and creates PLC tags for each process data field.

If you install a replacement sensor of the same type, the master detects the device identity match and automatically downloads the stored parameter set — no re-configuration required. This is called DS (Data Storage) and is one of IO-Link's highest-value maintenance features.

Master Architecture

IO-Link masters come in several form factors:

A typical architecture:

1. Sensors connect via M12 cables to IO-Link master ports (field level)
2. Master connects via PROFINET or EtherNet/IP to PLC (control level)
3. PLC maps IO-Link process data to standard I/O tags — no special PLC code needed
4. Parameterisation and diagnostics are available via acyclic services from the PLC, HMI, or engineering tool

Most masters present each IO-Link device as a sub-slot or sub-module in the fieldbus configuration. Once the IODD is imported and the port is configured, process data appears as normal input/output bytes in the PLC's I/O image.

IO-Link vs 4–20 mA

For new machine builds where cable runs are under 20 m, IO-Link is almost always the better choice for smart sensors. The only situations that still favour 4–20 mA are very long runs, applications requiring Ex ia intrinsic safety with existing infrastructure, or integration into legacy analogue I/O systems that will not be upgraded.

For process plant instrumentation (flow, pressure, level transmitters) with runs of hundreds of metres, 4–20 mA with HART remains dominant — IO-Link's 20 m limit is a hard constraint.

When to Use IO-Link

Strong candidates for IO-Link

• Machine-level sensors close to the control cabinet (< 20 m)
• Sensors that need regular parameter changes (e.g., recipe-dependent setpoints)
• High sensor counts where remote diagnostics reduce maintenance cost
• Applications requiring multiple simultaneous measurements from one device (e.g., colour sensor reporting R, G, B, and intensity)
• New builds where Auto-Device Replacement (DS) reduces commissioning time

Stick with 4–20 mA or fieldbus when

• Cable runs exceed 20 m
• The device is a transmitter in a hazardous area requiring Ex ia without IO-Link Ex hardware
• You are retrofitting into an existing AI card infrastructure with no IO-Link master budget
• The device does not have an IO-Link variant (some legacy pressure transmitters)

Setup Steps

1. Select hardware — choose an IO-Link master compatible with your fieldbus (PROFINET, EtherNet/IP, EtherCAT, or direct backplane).
2. Download IODD — get the IODD file for your sensor from the manufacturer's website or IODD Finder.
3. Import IODD into engineering tool — in TIA Portal: Options → Manage general station description files; in Studio 5000: Add-On Profile wizard.
4. Configure master port — select device type, set process data size, enable Data Storage if desired.
5. Wire sensor — connect M12 cable; pin 1 = L+, pin 3 = L−, pin 4 = C/Q.
6. Download and go online — verify process data tag is updating; read device identity to confirm type match.
7. Write parameters if needed — use the master's acyclic write function or the engineering tool's device parameterisation screen.
8. Test diagnostics — disconnect pin 4; verify the master raises a device-not-present alarm in the PLC.

Frequently Asked Questions

What cable does IO-Link use?

IO-Link uses standard unshielded 3-wire sensor cable (M12 or M8 connector). No special shielded cable is required because the point-to-point distance is limited to 20 m.

What is the maximum data rate for IO-Link?

IO-Link COM3 mode runs at 230.4 kbaud — the fastest of the three baud rates (COM1: 4.8 k, COM2: 38.4 k, COM3: 230.4 k). Most modern IO-Link sensors use COM3.

How many devices can connect to one IO-Link master?

Each IO-Link master port connects to exactly one device (point-to-point). Masters typically have 4, 8, or 16 ports. There is no bus topology — each sensor gets its own dedicated port.

Can IO-Link replace 4–20 mA?

IO-Link can replace 4–20 mA for new installations and delivers more: digital accuracy, multi-value transmission, remote parameterisation, and diagnostics. However, 4–20 mA remains preferable for very long cable runs (>20 m), legacy systems, and where intrinsic safety (Ex ia) is required without IO-Link Ex-rated hardware.

What is an IODD file?

An IODD (IO Device Description) is an XML file supplied by the device vendor. It describes all process data, parameters, and device identity for a specific IO-Link device. The engineering tool (TIA Portal, Studio 5000, CODESYS) uses the IODD to auto-configure the master port and map data to PLC tags.