IO-Link is already the dominant standard for the lowest level of industrial automation — the sensor-to-controller connection. Over 250 million IO-Link ports are installed globally. The technology defines how sensors and actuators communicate their state to a master device, which then passes that data up to the PLC or edge system above it. It’s unglamorous but critical: it’s how you know whether a valve is open, how much pressure is in a line, or whether a component has passed a quality check.
The one thing IO-Link always required was a cable. That’s fine for most factory applications, where sensors are fixed in position and cable routing is planned at installation time. But cables become a genuine problem on rotating equipment, on mobile robots, on machine modules that need to be repositioned frequently, and on retrofit applications where running new cables is expensive or impractical. IO-Link Wireless solves this.
What IO-Link Wireless Is
IO-Link Wireless is a wireless extension of IO-Link, standardised as IEC 61131-9. It uses the 2.4 GHz ISM band, operates globally without frequency licensing issues, and maintains the real-time communication characteristics that industrial automation demands. Cycle times start from 5 milliseconds — fast enough for the monitoring and control tasks that IO-Link handles at the sensor layer.
Each IO-Link Wireless master can handle up to 40 devices simultaneously. The wireless protocol uses time-division multiple access (TDMA) scheduling to manage the radio channel, which gives it deterministic timing behaviour rather than the random-access contention that makes Wi-Fi unsuitable for time-sensitive industrial communication. Packet loss rates are kept very low through forward error correction and automatic repeat request mechanisms, with the protocol designed to function reliably in the electrically noisy environments typical of factories.
The logical model maps directly onto wired IO-Link. An IO-Link Wireless master looks to the PLC above it exactly like a standard IO-Link master — same port structure, same data model, same parameter access. Existing IO-Link tooling and engineering workflows carry over. A sensor manufacturer can add wireless communication to an existing IO-Link sensor without changing anything in the data model or the PLC programme.
Where It’s Being Used
The application profile that comes up most consistently is rotating machinery. Attaching a sensor to a rotating shaft or drum with a cable is either impractical or requires a slip ring — a mechanical component that introduces maintenance complexity. IO-Link Wireless gives you direct wireless communication from the sensor on the rotating element, with real-time monitoring data reaching the PLC without the slip ring.
Mobile robotics is the second major use case. An autonomous mobile robot (AMR) operating on a factory floor needs to communicate sensor data from its onboard systems to the production line infrastructure as it moves. IO-Link Wireless handles this without requiring the robot to maintain a cable connection to the network — it communicates through fixed wireless masters positioned around the facility.
Flexible manufacturing cells are the third area. A machine module that can be repositioned between product runs benefits enormously from not needing to be re-cabled each time it moves. IO-Link Wireless masters at fixed positions in the cell communicate with the sensors on the moveable modules. Repositioning the module means unplugging and replugging the mechanical power connection — the sensor communication continues automatically once the module is within range of a master.
Where the Ecosystem Stands
Balluff and WIOT Group are among the manufacturers currently shipping IO-Link Wireless hardware. OEMs in the German-speaking manufacturing region began first series applications in 2025, and the technology is expanding beyond early adopters. An annual IO-Link Interop Workshop, where wireless compatibility, profile implementations, and IIoT integration are tested across vendor hardware, has been running since 2024.
The honest assessment is that IO-Link Wireless is still in its earlier commercial phase — well past proof-of-concept, into early production use, but not yet the mainstream default for wireless sensor communication in factories. The established players in industrial wireless (WirelessHART for process automation, ISA100.11a, and proprietary protocols from major automation vendors) have large installed bases and aren’t going anywhere. IO-Link Wireless’s advantage is its alignment with IO-Link’s existing ecosystem: the same port architecture, the same tooling, the same device model.
Integration with Edge and IIoT Systems
An IO-Link Wireless master typically connects to the PLC layer via Ethernet-based fieldbus — EtherNet/IP, PROFINET, or EtherCAT depending on the environment. From there, the data flows up the standard industrial architecture hierarchy the same way wired IO-Link data does.
For edge computing and IIoT connectivity, IO-Link data can be exposed to higher-level systems through OPC UA (using the OPC UA for IO-Link companion specification) or MQTT. An IO-Link master with an integrated OPC UA server publishes device data as structured information objects that can be consumed by a Unified Namespace, a cloud data pipeline, or a local edge analytics platform. This is where IO-Link Wireless data becomes useful for predictive maintenance, anomaly detection, and process optimisation — the use cases that require the sensor data to reach systems above the PLC layer.
Getting Started
The practical entry point for most teams is a development kit from one of the established IO-Link Wireless manufacturers. Balluff offers evaluation kits with a wireless master, a set of wireless sensors, and a getting-started guide that covers the configuration workflow. The configuration tooling (IO-Link Device Tool, IODD Finder for device descriptions) is shared with wired IO-Link, so teams already working with IO-Link will find the wireless system familiar.
For retrofit use cases — the most compelling immediate opportunity — the workflow is: identify sensors on rotating or mobile equipment where cabling is a pain point, evaluate whether IO-Link Wireless cycle times and wireless coverage meet the application requirements, and replace the wired sensor with a wireless equivalent. The PLC doesn’t change; only the physical connection layer does.