01
Direct engineering values
Supported sensors can provide °C, bar, mm, l/min, position or level directly to the PLC.
ifm · IO-Link
IO-Link & Smart Factory Connectivity
Build a digital point-to-point sensor layer that carries process values, parameters and diagnostics between field devices and the controller, while using the correct master, modules and IIoT route for the machine architecture.
Digital field dataMasters & devicesParameter backupDiagnosticsOT / IT separation
CommunicationPoint-to-pointDevice connects to one master port
Process layerDigitalProcess values without analogue scaling loss
Device data3 typesCyclic, acyclic and event data
IntegrationPLC + IIoTControl and information routes can coexist
System architecture
From intelligent field device to PLC and higher-level data
IO-Link is not an Ethernet fieldbus at the device port. The master terminates the point-to-point device links and bridges them to the selected industrial network and, on suitable masters, to IIoT interfaces.
FieldIO-Link sensors / actuators
→
AggregationIO-Link master
→
ControlPLC / fieldbus
+
InformationMQTT / JSON / OPC UA by master
Important: conventional digital or analogue devices can be brought into the topology through suitable IO-Link hubs/modules, but those hubs do not replace the IO-Link master.
Why IO-Link
More than replacing an analogue wire with digital communication
The value comes from combining precise process data with remote parameterisation, device identity and diagnostic information.
02
Know the installed device
Vendor/device identifiers, article number and serial information can support machine validation.
03
Remote setup & replacement
Configure switch points, scaling and selected device behaviour and restore parameters after replacement.
04
Detect faults earlier
Status bits and event information expose device issues and application changes on supported devices.
Portfolio routes
Layer selection within the IO-Link portfolio
The system usually combines devices, a master and optional field modules. Higher-level software is selected separately.
Masters
IO-Link Masters
Gateway from field devices to the selected PLC network; current ifm portfolio includes DataLine, PerformanceLine, CabinetLine and SolutionBlock.
- Up to 8 IO-Link ports by family
- Fieldbus depends on master
- IIoT functions differ by family
Modules
IO-Link Hubs & Modules
Bring conventional digital, analogue and actuator signals into an IO-Link topology without running every signal back to the cabinet.
- DI / DO / AI routes
- Coolant and food variants
- Upstream master still required
High power
PerformanceLine
Use AL14xx when higher actuator current, L-coded power and configurable B-port architecture are central to the application.
- L-coded M12 supply
- Up to 2 A outputs by route
- Per-port current monitoring
Communication model
Cyclic, acyclic and event data serve different purposes
Process values used continuously by the controller are cyclic. Parameters and identification are normally exchanged acyclically. Events communicate device or application status changes. The IODD describes the device data model and parameters.
CyclicProcess values and switching information used during machine operation.
AcyclicConfiguration, identification, counters and other device parameters.
EventsDiagnostic or status information when supported.
IODDDevice description used to interpret the device data model.
Application value
IO-Link architecture application scope
Prioritise applications where configuration effort, diagnostics, additional process data or repeated machine builds justify the architecture.
01
Standardised device setup
Parameter backup and repeatable configuration reduce commissioning variation across series machines.
02
Multiple values
A smart process sensor can provide primary and secondary process values plus status without extra analogue channels.
03
Expose extra data
Make diagnostics, temperature, counters or consumption data available to analytics layers.
Requirement capture
Inputs required to design the IO-Link layer
Start with the PLC/network and field-device count. Do not start by choosing a master only from port count.
PLC / fieldbusPROFINET, EtherNet/IP, EtherCAT, Modbus TCP or other required network.
Device countIO-Link devices plus conventional DI/DO/AI signals.
Power demandSensor-only ports versus higher-current actuators / B ports.
EnvironmentCabinet, IP67 field, washdown, coolant or hygienic area.
IT dataMQTT, JSON, OPC UA or higher-level software requirement.
TopologyDaisy chain, machine zones, cable lengths and cabinet layout.