Implementing IO-Link Safety – with TEConcept from Concept to Certification

IO-Link Safety extends the IO-Link protocol with safety-related communication up to SIL 3 – using IO-Link itself as a so-called black channel. Safety-relevant and standard data run over the same channel, without additional wiring. Standardized as IEC 61139-2, IO-Link Safety is recognized worldwide and particularly attractive for device manufacturers: a single protocol covers both conventional and safety-related applications. TEConcept guides you along this path – with specialized development tools, test systems for IO-Link Safety devices and masters, and hands-on consulting from initial concept to certification.

Are you planning a new IO-Link Functional Safety development – or want to extend an existing product with Functional Safety?

Our IO-Link software components as well as diagnostic and test systems support you in your development
Contact us

IO-Link Safety Device and Master Stack

Similar to the IO-Link Device Stack and IO-Link Master Stack software stacks, TEConcept is working on the final completion of the software for the functional safety implementation. The Safety Master Stack is already pre-certified and in the final stages of certification, and the Safety Device Stack is also expected to be ready for use in the near future.

TEConcept IO-Link Safety Master Stack

IO-Link Safety Master Stack

An extension of the Master Stack adding IO-Link Safety support – enabling standards-compliant, safety-oriented communication in automation applications.

IO-Link Safety Device Stack (in progress)

Will enable IO-Link Safety integration in sensors and actuators. Contact us for more information on the planned release date.

IO-Link Safety Diagnostic and Test Tools

For the safety protocol test, TEConcept already has the right tool at hand with the Safety Master Tester, to reliably test and validate safety masters.

TEConcept IO-Link Safety Master Tester for IO-Link Safety Masters

IO-Link Safety Master Tester

The IO-Link Safety Master Tester automatically checks whether your IO-Link Safety Master meets the required specifications and generates a PDF report for certification.

Still have questions about IO-Link Functional Safety?

Do you need further information or specific adaptations? Contact our team of experts – we are happy to provide individual support.

Why should you work with us on Functional Safety?

Mann arbeitet mit Laptop und TECOncept Software – TECOncept Software: Veröffentlichungsrhythmus & Updates im Blick
Release
cycle
All our Stacks are continuously adapted to the current IO-Link specification. Typical release cycles for new IO-Link versions are 6–12 months.
Entwickler arbeitet an TEConcept IO-Link Hardware – spezielle Konfiguration, OEM-Anpassung oder Integration möglich.
Expertise & Experience
As an IO-Link Competence and Test Center, TEConcept has years of experience not only in standard IO-Link, but has also been active in the field of Safety for some time.
Headset auf Schreibtisch – symbolisiert Fragen oder technische Unterstützung.
IO-Link from a Single Source
TEConcept is not just a supplier of software stacks – we also support your IO-Link project in the concept phase, the certification phase, and through to market launch.

We work with these partners

Logo Texas Instruments
Analog Devices logo
STMicroelectronics N.V. logo
Renesas Electronics logo
Nanjing Loyst Industrial Networks Co,.Ltd. logo
Logo EmbedCoreTec
Logo M2M
Logo NXP

FAQ on IO-Link Safety

IO-Link Safety extends IO-Link with a safety communication layer (SCL) on both the master and device side. It can be used up to SIL 3. The concept has been reviewed by TÜV SÜD.

OSSDe does not support bidirectional communication or parameterization. Without IO-Link Functional Safety, a manufacturer would need to implement several FSCP protocols (PROFIsafe, CIP Safety, etc.). With Safety, a single device type suffices for all FSCP platforms.

IO-Link is used as a transmission channel without needing to be assessed against IEC 61508 itself. Safety is provided by the protocol itself: counter/inverted counter, watchdog with acknowledgment, authentication at protocol startup, and CRC signature (CRC-16 or CRC-32).

Protocol parameters (FSP_) are set via the FS Master Tool and the IODD. Device-specific safety parameters (FST_) are transmitted by a supplied dedicated tool, which calculates a CRC signature across all technology parameters. The FS device checks this signature at every startup.

A single device type covers both FS-DI operation (OSSDe) and FS master operation (IO-Link Safety) – without variants, without license fees. This includes bidirectional data transmission, integrated diagnostics for condition monitoring and predictive maintenance, as well as a clear foundation for Industry 4.0 / IIoT.

Yes. The specification can be found on the IO-Link Community website in the download area under the name IO-Link Safety Systems Extension.

Contact

Use our contact form for general inquiries, project ideas, or questions about our products. The more precise your information, the more targeted our response can be.


Please note our privacy policy.