iolinki documentation
Build an IO-Link device or integrate the companion master stack. These guides publish the source documentation as readable, searchable pages, using the same MkDocs Material approach as LabWired.
| Product | Start here | Reference | Validation |
|---|---|---|---|
| Device v2.1.0 | Run the reference device | Device API, porting | Released firmware simulation |
| Master v1.0.0 | Build the master demos | Master API, PHY contract | Software tests, hardware matrix |
Choose a starting point
- Evaluate on a computer: run the counter/button/LED device.
- Build MCU firmware: use STM32G0/TIOL112 and native IAR, ESP32-C3/L6362A, or STM32U5/Zephyr.
- Describe a sensor: start with the switching sensor and IODD command-line tools.
- Author an IODD with your assistant: use the free shared editor, CLI and MCP server.
- Connect the master to a board: implement the master PHY contract and complete the physical validation matrix.
Read the evidence at its actual level
Host assertions prove software behavior. A target build proves compilation and linking. The released G0 and C3 recipes execute MCU firmware in LabWired, with the engine pins and assertions listed on the simulation page. None of those results is physical-master interoperability or official certification. Native IAR source projects are provided; an IAR build was not run for the release.
Technical documentation is pinned to device ad892f43fa72 and master
d23fd3034c02. Follow each page's source snapshot link for its immutable original.
Licensing and publication sources distinguish release snapshots
from current commercial offers. Return to iolinki.com
for product and evaluation information.