IO-Link Device Stack – certified software stack for IO-Link devices
Anyone developing an IO-Link-capable sensor or actuator faces a choice: implement the communication protocol themselves—or rely on a ready-made, standards-compliant solution. TEConcept’s IO-Link Device Stack always complies with the current specification of the IO-Link Community and implements the complete protocol layer in accordance with IEC 61131-9, allowing developers to focus on what makes their product unique. The result: shorter development time, lower risk, and reliable IO-Link integration that is interoperable from day one.
Would you like to test our IO-Link Device Stack?
IO-Link Device Stack features
- Complies with the latest IO-Link communication specification
- Enables synchronous and asynchronous process data access
- DataStorage, block transfer, and event support included
- Optimized for short response times
- Modular stack design enables support and replacement of various MCUs and IO-Link transceiver chips
- Sample application footprint (incl. RAM for example parameters with maximum length): Flash 14 kB, RAM 3.5 kB
Implementation of the IO-Link Device Stack
- IO-Link parameters must be stored non-volatilely. In most cases, storage is implemented in an external EEPROM. Storage routines and EEPROM drivers are not part of the delivery.
- Real-time requirement: The IO-Link specification defines the maximum response time to requests from the IO-Link master for IO-Link devices. The maximum permitted response time depends on the baud rate used. For COM3 (230400 baud), the maximum response time is 43 µs; for COM2 (38400 baud), it is 260 µs. The IO-Link Device Stack must be executed within this response time. Especially for COM3, the Device Stack generally requires the highest interrupt priority, or the system clock must be set relatively high. The exact timing behavior depends on various factors (system clock, optimization, interrupt priority, etc.).
Processors and transceiver ICs supported by the IO-Link Device Stack
Our flexible stack structure enables easy porting of our IO-Link Device Software Stack to any microcontroller/ASIC to meet the requirements of our business partners.
The supported MCUs or PHYs listed here are examples of existing ports. All listed components have already been verified/used with our stack. If you would like to use a different MCU or an IO-Link PHY that is not listed here, or if you require special hardware or an FPGA-based design, please contact us.
Examples of existing MCUs
STMicroelectronics
- GD32F
- STM32C0
- STM32F0 – STM32F4
- STM32G0, STM32G4
- SM32H5, STM32H7
- STM32L0, STm32L4
- STM32MP1
- STM32U5
- STM32WB55
- STM8L151, STM8L152
- STM8S
Analog Devices
- MAX22522
- MAX32660
Renesas
- RA6M4
- RL78
- RX72M
Texas Instruments
- MSP430
- MSPM0G
- MSPM0L
NXP
- LPC17
- LPC54
- S32K11
- S32K144
Other
Infineon:
- PSoC4
- XMC1000
Microchip:
- ATM328
- ATSAMD51
- dsPIC33E
Examples of existing IO-Link transceiver ICs
STMicroelectronics
- L6362A
- L6364
Analog Devices
- LT3669-2
- MAX14820
- MAX14821
- MAX14826
- MAX14827
- MAX14829
- MAX22513
- MAX22515
- MAX22516
- MAX22522
Renesas
- CCE4502
- CCE4503
- RH4Z2501
- RH4Z2522
Texas Instruments
- SN65HVD101
- SN65HVD102
- TIOL112
Other
HMT:
- HMT7742
- HMT7748/li>
iC-Haus:
- iCGF
Compilers / development environments supported by the IO-Link Device Stack
The Device Stack code is written in pure C. This means any C compilers and development environments can be used.
- KEIL-MDK
- SiLabs IDE
- ST Visual Develop
- Eclipse/GCC/NXP LPCXpresso
- IAR
- Cosmic
- Visual Studio Code
License information and scope of delivery for the IO-Link Device Stack
- Developer license with access to the complete source code
- Manufacturer license is royalty-free and depends only on the number of device IDs
- No restriction to a vendor ID / device ID combination.
- One year of maintenance included
- IO-Link Device Stack is ported to target hardware or to developer kits
- Driver for one processor architecture
- Driver for one selected transceiver chip
- IO-Link Device Stack API user manual
- Installation manual and API description of the device driver.
- Demo application
- Compiler and linker example project
Please contact our sales department for further details on licensing, the scope of delivery, and practical project implementation.
Additional offerings for the IO-Link Device Software Stack
- Evaluation boards
- IO-Link Device Descriptor IODD support
- IO-Link 1-port USB-C development master
- Software/hardware development support
- Conducting conformity tests
- Provision of Test and diagnostic equipment (Device Tester, Physical Layer Tester & EMC Test Master)
Add-on for the IO-Link Device Software Stack: simplifies ISDU parameter implementation through table-based definition, automatic DataStorage handling, and a ready-made interface for non-volatile storage. Royalty-free, full source code, available only in combination with the Device Stack.
Add-on for the IO-Link Device Software Stack: secure firmware updates via IO-Link in accordance with the BLOB Transfer Profile. Extendable with Verified Firmware Boot — cryptographic signature verification at every boot as a building block for EU CRA compliance.
Add-on for the IO-Link Device Software Stack: transfers data sets of any size (log files, FFT data, calibration data) via ISDU over standard IO-Link masters. Compliant with the BLOB Transfer Profile. Basis for the TEConcept firmware-update bootloader.
Contact
- +49 761 21443640
- +49 761 21443636
- info@teconcept.de
Please use our contact form if you have further questions about our IO-Link Device Stack—also for additional project ideas or questions about our other products. The more precise your information, the more specifically we can respond.