Both Sides of an IO-Link Link

A vendor-agnostic implementation of the IO-Link V1.1.5 protocol.
Device firmware and master-side tools can now be developed and tested together.

  • Portable
  • Fast
  • Compliant

Device Stack

The original iolinki stack runs in sensors and actuators. It serves process data, mandatory parameters, events, and ISDU services through a clean PHY abstraction for Zephyr and bare-metal systems.

Master Stack

iolinki-master is a separate C library for master ports and multi-port controllers. It drives wake-up, startup, preoperate, cyclic process data, ISDU reads and writes, diagnostics, and SIO DI/DQ modes.

Shared Boundary

The stacks are intentionally separate. They share narrow protocol helpers such as CRC and frame encode/decode, but the master is not bolted into the device API.

Technical Capabilities

Everything you need to build and test production IO-Link conversations.

  • ISDU Protocol

    Device-side mandatory service handling plus master-side read/write APIs and verification flows.

  • Data Storage

    Consistent parameter backup for seamless, tool-less device replacement (V1.1).

  • Event Management

    Integrated diagnostic and notification event dispatching from the Device stack to the Master stack.

  • Full-Link Testing

    Run a real device stack against a real C master stack in simulation before hardware is available.

Production Ready

GPLv3-or-later for GPL-compatible use, with commercial licensing available for proprietary products.