Device & master software
IO-Link stacks.
Built for your firmware.
Connect your sensors and actuators with the device stack. Build multiport controllers with the master stack. Two focused libraries, ready to evaluate in your own development workflow.
Public source · Linux evaluation · Commercial licensing
Architecture diagram · Each link uses a physical transceiver.
One protocol. Two sides.
Start with the stack your product needs.
Work with IO-Link V1.1.5 protocol software through a hardware abstraction. Keep your application, platform and transceiver integration under your control.
For sensors
and actuators.
The iolinki device stack serves process data, mandatory parameters, events and ISDU services through a PHY abstraction for Zephyr and bare-metal systems.
- Device-side application interface
- Hardware-specific PHY integration
- Host and embedded reference examples
For ports
and controllers.
The separate iolinki-master C library drives startup, cyclic process data, ISDU reads and writes, diagnostics, and SIO DI/DQ modes for master ports and multiport controllers.
- Master-side port management
- Independent master application API
- Real device / master software testing
Fit your development workflow
Evaluate on a host.
Integrate on your target.
The stacks stay separate, sharing narrow protocol helpers rather than one application API. Choose a platform, connect your PHY and validate the complete product.
Explore hardware & IDE paths ↗Linux
Repeatable host builds and software tests before choosing a board.
Zephyr & bare-metal
STM32G0 and STM32U5 reference projects with TIOL112 integration.
ESP-IDF
ESP32-C3 reference firmware with the L6362A transceiver board.
A practical first step
Run it. Read the evidence.
Build a pinned release
Clone v2.1.1 and build the Linux host stack with CMake. No IO-Link board is required.
Run the host checks
Use CTest, then try the separately pinned counter, button and LED reference demonstration.
Choose your hardware
Compare build evidence and remaining validation work for your MCU and transceiver.
Validation is specific to the version and setup.
Host tests, real-stack integration, physical interoperability and official certification have different evidence. The current integration pair has known failures.
From evaluation to your product
Choose a license
for the way you build.
Evaluate the public source under its GPLv3 license. For proprietary products, review royalty-free commercial licensing and agree the scope for each product before purchase. Device and master stack licensing are covered by product-specific agreements.
Read the licensing FAQ ↗