01
One master for two major PLC networks
Multiprotocol support reduces hardware variants when machines are deployed with PROFINET or EtherNet/IP.
ifm · IO-Link
ifm SolutionBlock IO-Link Masters
Combine field-level IO-Link connectivity with OT and IIoT communication in one field-mounted AL15xx platform. SolutionBlock is intended for architectures that need sensor data for machine control and higher-level IT systems without adding a separate edge gateway.
AL15xx8 IO-Link portsPROFINET + EtherNet/IPOPC UA / MQTT / RESTIODD interpreter
Device ports8Direct IO-Link device connections
FieldbusMultiprotocolPROFINET and EtherNet/IP
PowerM12 L-coded16 A US / 16 A UA architecture
IT layerIntegratedOPC UA, MQTT(s), HTTP(s)/REST
Why SolutionBlock
Bring machine data to OT and IT without adding another gateway layer
The AL15 family is the right route when an IO-Link master must do more than exchange cyclic process data with a PLC.
02
Integrated OPC UA and MQTT
Sensor data can be exposed to higher-level systems through standard industrial IT interfaces.
03
IODD interpreter in the master
Uploaded IODDs translate raw IO-Link bytes into readable engineering values such as °C or m³/h.
04
Daisy-chain power, network and IIoT
L-coded power and daisy-chain architecture can reduce cabling in distributed machine layouts.
System architecture
One field device between smart sensors, PLC control and data platforms
SolutionBlock can keep real-time machine communication on the fieldbus while also exposing structured device data to IT/IIoT systems. The architecture is particularly useful when sensors provide several process values or diagnostic parameters.
Machine controlPROFINET or EtherNet/IP exchanges process data with the controller.
IIoT layerOPC UA, MQTT and REST/JSON provide higher-level data access.
Time synchronisationNTP support enables precise network time alignment.
Configurationmoneo configure and the integrated web functionality support commissioning and device setup.
Field devicesIO-Link sensors / actuators
→
Edge + masterAL15 SolutionBlock
→
OTPLC / PROFINET / EtherNet/IP
+
ITOPC UA / MQTT / REST
Current AL15 route
Select the SolutionBlock version for the installation environment
Keep AL15-specific capabilities on this family page; do not automatically apply them to AL13, AL14 or AL19 masters.
SolutionBlock
AL1590
Factory-automation / coolant version of the AL15 SolutionBlock.
- 8 IO-Link ports
- PROFINET + EtherNet/IP multiprotocol
- OPC UA / IIoT functions
- M12 L-coded power architecture
SolutionBlock
AL1591
Food / washdown-oriented SolutionBlock route where the corresponding housing/environment rating is required.
- Same AL15 OT/IT architecture
- Select by installation environment
- Verify current environmental approvals before final selection
Master selection
SolutionBlock is not the default answer for every IO-Link project
Choose the master family by power architecture, installation location, fieldbus and whether independent IT/IIoT access is actually required.
| Route | Typical role | Power / location | IT / IIoT | Use when |
|---|---|---|---|---|
| AL15 SolutionBlock | IO-Link master + edge/IIoT functions | L-coded 16 A field architecture | Integrated OPC UA / MQTT / REST functions | Best for OT + IT |
| AL14 PerformanceLine | High-power field master | L-coded 16 A field architecture | Different IT feature set by model | Power distribution and fieldbus are the priority |
| AL13 DataLine | General field IO-Link master | A-coded power | Separate IIoT port on relevant versions | Standard machine IO-Link connectivity |
| AL19 CabinetLine | Control-cabinet master | IP20 cabinet installation | IIoT access on relevant versions | Centralised or retrofit cabinet architectures |
Engineering checks
Confirm the network and data architecture before selecting an AL15 master
Key SolutionBlock data
These family-level values describe the current AL15 architecture. Exact environmental ratings, port current limits, firmware and approvals should still be checked on the selected order number.
FamilyAL15xx SolutionBlock
IO-Link device ports8
FieldbusPROFINET / EtherNet/IP multiprotocol
Power architectureM12 L-coded, 16 A US / 16 A UA
IIoT interfacesOPC UA, MQTT(s), HTTP(s) / REST JSON
Data supportIODD interpreter, NTP, moneo integration
Do not copy AL15 features across the entire ifm master portfolio. Node-RED/Linux/edge functionality, multiprotocol behaviour and IIoT interfaces must be verified per master family and order number.
Requirement capture
Inputs required to define the correct IO-Link master
PLC / fieldbusPROFINET, EtherNet/IP or another protocol.
IO-Link devicesNumber of ports, Class A/B needs and connected sensor current.
Power distributionAvailable supply, actuator load and daisy-chain requirement.
IT requirementOPC UA, MQTT, REST, dashboard or condition-monitoring data.
EnvironmentFactory automation, washdown, cabinet or field mounting.
ArchitectureStandalone machine, production line, retrofit or scalable OEM platform.