Select the IO-Link master by fieldbus, installation location, port type, power architecture and IIoT requirement—not simply by the number of ports. Current ifm families cover field, high-power, cabinet and advanced OT/IT architectures.
The exact fieldbus and port count still depend on the selected order number within each family.
Field-installed master for standard IO-Link devices with A-coded supply and a separate IIoT path on supported models.
For field applications that need more actuator power and power daisy chaining.
IP20 master for cabinet or sub-panel mounting using removable terminal architecture.
Advanced field master with multiprotocol control-network support and richer IT connectivity.
Use this as an architecture filter; confirm exact product data on the final model.
| Family | Series | Power | Port architecture | IIoT | Best fit |
|---|---|---|---|---|---|
| DataLine | AL13xx | M12 A-code | 4 / 8 A ports | HTTP(S), JSON, MQTT on current routes | Standard field IO-Link + data access |
| PerformanceLine | AL14xx | M12 L-code | 4 B ports or 4 B + 4 A | Not primary IIoT family | High-current actuators / power distribution |
| CabinetLine | AL19xx | Cabinet terminals | 8 A ports | HTTP(S), JSON, MQTT on current routes | Main/sub-panel integration |
| SolutionBlock | AL15xx | M12 L-code | 4 B + 4 A | HTTP(S), JSON, MQTT, OPC UA | Flexible OT/IT architecture |
Field devices communicate point-to-point with the master. The master then exposes that data to the selected PLC fieldbus and, on suitable families, independently to IT/IIoT services.
Port count alone is not enough.
Choose the supported controller network before the hardware variant.
High-current actuators can require PerformanceLine or SolutionBlock B-port architecture.
Use IP67/IP69K field hardware where required; CabinetLine is IP20.
Confirm housing and connector materials for coolant or hygienic zones.
Master families provide different information-system routes.
Power and fieldbus daisy-chain capability differs by family.