element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Essentials
  • Learn
  • Learning Center
  • Essentials
  • More
  • Cancel
Essentials
Documents Designing an IO-Link Sensor - Industrial Sensing
  • Forum
  • Documents
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Essentials to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Engagement
  • Author Author: pchan
  • Date Created: 10 Aug 2022 6:25 PM Date Created
  • Last Updated Last Updated: 31 May 2023 3:21 PM
  • Views 11823 views
  • Likes 8 likes
  • Comments 10 comments
Related
Recommended

Designing an IO-Link Sensor - Industrial Sensing

essentials logoSensors Series - Part 09 - Industrial Sensing

As programmable logic controllers (PLCs) evolve, they are quickly becoming an integral component within Industry 4.0 smart factories. This is due to a need for faster, low power, and innovative solutions. The IO-Link standard was created in part to give the legacy sensors that were previously installed the capabilities of a smart sensor. IO-Link is a point-to-point communication link with standardized connectors, cables, and protocols. This article explains IO-Link smart sensor technology, analyzes IO-Link sensor design, and discusses its advantages over traditional systems.
Related Components | Test Your Knowledge test link

sponsored byimage

2. Objectives


Upon completion of this module, you will be able to:

  • Understand what an IO-Link is and its components
  • Describe the IO-Link data communication protocol and its pin configuration
  • Discuss the benefits of using IO-Link in Industry 4.0 by comparing it with conventional sensors
  • Explain how to design an IO-Link smart sensor

3. Basic Concepts

Back to Top

1. Traditional Sensors

Traditional sensors typically consist of a sensing element and a method for transmitting data to a controller. Figure 1 illustrates how traditional sensors frequently send data in a unidirectional, analog format. This type of data transmission requires additional operations, including additional digital-to-analog and analog-to-digital conversions, which can add noise, not to mention increasing the cost and footprint of the device. As shown in Figure 1, a traditional binary sensor indicates the status of a switch, either ON or OFF. An ON signal would be represented by a high (24V) signal, while an OFF signal would be represented by a low (0V) signal. In most cases, the data flow of traditional sensors is limited to one direction, from the sensor to the controller, as indicated in Figure 1.

figure 1
Figure 1: Traditional sensor block diagrams - Analog and Binary

Newer, more advanced sensors have replaced traditional sensors. The IO-Link standard was created to better meet the demands of Industry 4.0 where advanced smart sensors and reconfigurable factory floors will become commonplace. The following content offers a detailed explanation of the many benefits of IO-Link.

2. What is IO-Link?

IO-Link is a point-to-point, bus-independent, serial digital communication protocol defined by international standard IEC 61131-9. IO-Link is designed to link sensors and actuators to PLCs. IO-Link enables "last meter" digital data communication to sensors and actuators. It enables bidirectional transmission of parameterization and diagnostic data, where previously, only binary states (ON/OFF) or analog signals were communicated. A system with IO-Link functionality can benefit from reduced downtime for maintenance and increased flexibility when configuring and reconfiguring. IO-Link can transform a manual sensor installation into one which allows a user to "plug-and-play and walk away.”

3. The Components of IO-Link

Figure 2 depicts the block diagram of an IO-Link system, which is comprised of two types of components: the "IO-Link controller" and the "IO-Link device" (sensor or actuator). All IO-Link data exchange is controller-agent based, meaning the IO-Link controller communicates with IO-Link devices, collecting their data, and transmitting it to the higher-level bus system. The controller can have multiple ports (usually four or eight). Each port of the controller connects to a unique IO-Link device. The design of IO-Link enables it to work with existing industrial architectures, such as fieldbus or Industrial Ethernet, providing connectivity to existing PLCs or human-machine interfaces (HMIs).

figure 2
Figure 2: IO-Link controller/device interface

An IO-Link layer can be present on any given network. Installation of the IO-Link controller is possible within either the control cabinet, or directly in the field as a remote I/O with an industrial environment rated enclosure (IP65/67). The IO-Link device (any sensor, actuator, or combination of both) couples with the controller using a standard sensor/actuator cable, and transmits and receives data sent directly via IO-Link in a digital format. The following are highlights of IO-Link:

  1. The IO-Link standard states that sensor/actuator cables must have a length of 20 meters or less and be constructed from unshielded cables using standard connectors common to industrial systems. M8 and M12 connectors are in widespread use.
  2. Communication between controller and agent devices is half-duplex with three transmission rates: COM1: 4800 baud, COM2: 38.4 kbaud, and COM3: 230.4 kbaud. The IO-Link device only supports one data rate, while the IO-Link controller supports all three data rates.
  3. The IO-Link system supply range is 20V to 30V for the controller and 18V to 30V for the device (sensor or actuator).

a) IO-Link Pin Definitions

IO-Link is a standard for SDCI (single-drop communication interface), as described in IEC-61131-9, that maintains backward-compatibility with binary sensors. There are two port classes for the connectors, class A and class B. Port class A comprises 4 pins, as illustrated in Figure 3. The wiring for port class A uses three wires: (L+, L-, C/Q), with the fourth wire available as an additional signal line complying with IEC 61131-2. Its support is optional in both controller and devices.

Binary drivers use a standard 24V, 3-wire industrial interface. These drivers typically support high-side (PNP), low-side (NPN), or push-pull configurations along with normally open (NO) or normally closed (NC) logic.

figure 3
Pin Signal Designation
1 L+ Power supply (+)
2 I/Q NC/DI/DO (port class A) P24 (port class B)
3 L- Power supply (-)
4 C "Switching signal" (SIO)
Q "Coded switching" (COM1, COM2, COM3)

Figure 3: Class A pin description

Figure 4 depicts a port class B connector. Class B connectors have 5-wire connections (L+, P24, L-, C/Q, N24). These are present in devices that need additional power from an independent 24V supply.

figure 4
Pin Signal Designation
1 L+ Power supply (+)
2 I/Q P24 NC/DI/DO (port class A) P24 (port class B)
3 L- Power supply (-)
4 C/Q SIO/SDCI
5 NC
N24
NC (port class A)
N24 (port class B)

Figure 4: Class B pin description

Communication can take place using standard I/O (SIO) or SDCI bidirectional communication modes. SIO mode ensures backwards compatibility with existing sensors. IO-Link mode provides bidirectional communication. Data is transmitted over the CQ line using nonreturn-to-zero (NRZ) modulation; logic 0 is 24V between C/Q and L- and logic 1 is 0V between C/Q and L-. In IO-Link mode, pin 2 can operate in DI mode as a digital input, DO mode as a digital output, or not connected (NC).

b) Data Types

Figure 5 illustrates the initiation of communication between the controller and device; all communication must start with a request from the controller and after that, follow a fixed schedule. The device must answer all requests from the controller. A back-and-forth communication sequence is called an M-sequence (message sequence) and can take many different forms, varying in total length. All data communication uses a UART frame, consisting of 11 bits = 1 start bit + 8 data bits + 1 parity bit + 1 stop bit.

figure 5a
figure 5b

Figure 5: IO-Link Controller-Device communication sequence

To configure a device or communicate with it for the first time, the controller sends a wake-up request. When the wake-up request is received, the device configures itself to receive mode. The second step involves establishing the data rate for communication. The controller sends multiple messages over the range of data rates from fastest to slowest, waiting for the device to respond after each send. The device responds to the message sent at its own data rate. All IO-Link devices must have an associated IO-Link device description (IODD) file, an XML file that is used by the controller for identification, data interpretation, and configuration of the device.

IO-Link data communication can be cyclic or acyclic. Cyclic communication consists of data that is transmitted during regular operation, and include process data and measurements from the sensor. Acyclic data is on-request and can contain configuration or maintenance information, event-triggers (like notifications, warnings, errors), service data for large data structures, and page data for direct reading of device parameters.

4. Analysis

Back to Top

Designing an IO-Link Sensor

The IO-Link communication protocol allows smart sensors to work with IO-Link controllers. Figure 6 illustrates the basic structure of an IO-Link sensor. Some of the questions the system designer must consider are:

  1. What type of sensor(s) is/are being integrated (optical, temperature, etc.)?
  2. Which MCU is interfacing with the sensor and running the IO-Link device stack?
  3. What is the IO-Link transceiver (or physical layer/PHY) being used?
  4. What are the various voltage and current ratings required?
  5. What connector types are being used?
  6. What external protection (TVS for surge, EFT/burst, ESD, etc.) is required?
figure 6

Figure 6: Building blocks of an IO-Link sensor

5. Reference Designs from Maxim Integrated

Back to Top

In IO-Link applications, the IO-Link device transceiver serves as the microcontroller's physical layer (PHY) interface. The transceiver runs the data-link layer protocol and supports digital inputs and outputs at voltages up to 24V. Maxim transceivers are capable of supporting IO-Link specifications at very low power dissipation levels; the third-generation MAX14828 single-channel transceiver and the MAX14827A dual-channel transceiver dissipate only 70mW when driving a 100mA load. In addition, Maxim’s latest IO-Link transceiver, the MAX22513, features a selectable control interface, an internal high-efficiency DC-DC buck regulator, two internal linear regulators, and integrated surge protection.

1. Temperature sensor reference design - MAXREFDES164

Figure 7 depicts the block diagram for the MAXREFDES164 temperature sensor reference design. The MAXREFDES164 is a collaborative product from Technologie Management Gruppe Technologie und Engineering (TMG TE), Maxim, and TEConcept. The design comprises a Maxim IO-Link device transceiver (MAX14828), a MAX32660 ultra-low-power 32-bit microcontroller using TMG TE's or TEConcept's IO-Link device stack, and a Maxim local temperature sensor (MAX31875).

Due to its minimal power requirements, small form factor, and low cost, the MAXREFDES164 IO-Link local temperature sensor is well-suited to industrial control and automation applications.

figure 7
figure 7b

Figure 7: MAXREFDES164 IO-Link temperature sensor block diagram

The MAX14828 is a small form factor (2.5mm x 2.5mm) IO-Link device transceiver that is compliant with the IO-Link version 1.1.3/1.0 physical layer. The MAX14828 features two ultra-low-power drivers with active reverse-polarity protection. Operation is specified for typical 24V supply voltages, supporting a maximum of 60V. An SPI interface is available and for IO-Link operation, a three-wire UART interface is provided. The MAX14828 includes integrated 3.3V and 5V linear regulators, which provide the low-noise supply rails for the other components on the board.

The MAX32660 is an ultra-low-power, cost-effective, highly integrated microcontroller. It combines a flexible and versatile power management unit with an Arm® Cortex®-M4 with a floating-point unit (FPU). The device integrates up to 256KB of flash memory and 96KB of RAM to accommodate application and sensor code. It supports SPI, UART, and I2C communication.

The MAX31875 is a ±1°C-accurate local temperature sensor with an I2C/SMBus interface. The I2C-compatible two-wire serial interface allows access to conversion results, and standard I2C commands can be used for configuration and reading data.

2. Distance sensor reference design - MAXREFDES171

Figure 8 depicts the MAXREFDES171, a distance sensor reference design. The MAXREFDES171 consists of an MAX22513 IO-Link device transceiver, a MAX32660 ultra-low-power 16-bit microcontroller utilizing the TMG TE IO-Link device stack, and a VL53L1 time-of-flight (ToF) laser-ranging distance sensor. The design is compliant with the IO-Link version 1.1.3/1.0 standard.

figure 8
figure 8b

Figure 8: MAXREFDES171 IO-Link device distance sensor

The MAX22513 is an IO-Link device transceiver, complying with the IO-Link version 1.1/1.0 physical layer specification. The high-voltage components often found in industrial sensors are integrated, including drivers, a high-efficiency DC-DC buck regulator, and two linear regulators. All four IO pins (V24, C/Q, DO/DI, and GND) have built-in reverse-voltage and short circuit protection, and feature integrated 1kV/500Ω surge protection. External transient protection can be simplified due to the transceiver’s high voltage tolerance (65V absolute maximum rating) and integrated surge protection. The integrated DC-DC buck regulator in MAX22513 provides the 3.3V and 5V rails, and delivers a load current of up to 300mA. The MAX22513 features a flexible control interface, allowing control through either an SPI or I2C interface. I2C allows both the MAX22513 and the sensor IC to be on the same bus. A 3-wire UART interface is provided to facilitate IO-Link operation. Because of the integrated surge protection within the MAX22513 at the IO-Link interface, the MAXREFDES171 does not require external protection, such as varistors or TVS diodes.

The MAX32660 is an ultra-low-power, cost-effective, highly integrated microcontroller, featuring a powerful Arm® Cortex®-M4 with FPU. The device offers up to 256KB of flash memory and 96KB of RAM to accommodate applications and sensor code. It supports SPI, UART, and I2C communication and comes in a tiny form factor.

The VL53L1X is a ToF laser-ranging sensor that provides accurate distance measurements up to 400cm.

6. Glossary

Back to Top

  • Acyclic data: Data that is transmitted from the controller only after a request. This includes data such as configuration and diagnostic information.
  • Analog Front End (AFE): The analog portion of a circuit which precedes A/D conversion.
  • COM1-3: The available rates that IO-Link data is transmitted. There are three available data rates: COM1: 4800 baud, COM2: 38.4 kbaud, and COM3: 230.4 kbaud.
  • Cyclic data: Data that is transmitted by the controller automatically and at regular intervals. This includes data such as process data and value status.
  • IEC 61131-9: The International standard listing specifications for programmable controllers. IO-Link is described in part 9:
    Single-drop digital communication interface for small sensors and actuators (SDCI).
  • IODD (IO-Link Device Description): An electronic description of an IO-Link device’s specifications. An IODD file is required for every IO-Link device. IODD is represented in XML format and contains the necessary properties to establish communication with the device, the device’s parameters, identification information, process and diagnostic information, an image of the device, and the manufacturer’s logo.
  • IO-Link device: A field device that is monitored and controlled by an IO-Link controller.
  • IO-Link controller: The device that represents the connection between a higher-level PLC/controller and IO-Link devices. The IO-Link controller monitors and controls the IO-Link devices.
  • Non Return to Zero (NRZ): A binary encoding scheme in which ones and zeroes are represented by opposite and alternating high and low voltages, and where there is no return-to-zero (reference) voltage between encoded bits. That is, the stream has only two values: low and high.
  • Port: A port is an IO-Link communication channel.
  • Sensor: A device that detects a physical parameter, such as temperature, motion, light, or sound, and converts it to an electrical signal that can be measured and used by an electrical or electronic system.
  • Serial Interface: An interface in which data is sent in a single stream of bits, usually on a single wire-plus-ground.
*Trademark. Maxim Integrated is a trademark of Maxim Integrated ADI. Other logos, product and/or company names may be trademarks of their respective owners.

Related Components

Back to Top

Sensors 9

IO-Link is a standard for industrial networking (IEC 61131-9) that enables bidirectional communication between devices, such as sensors, actuators, and controllers. The IO-Link standard also specifies backwards compatibility with legacy sensors and actuators, enabling smart functionality in existing systems. Maxim Integrated offers several reference designs featuring full IO-Link compatibility.


Product Image
Buy Now
MAX14828EVKIT
MAX14828 IO-Link Device Transceiver- Evaluation Kit
Product Image
Buy Now
MAXREFDES171
IO-Link Distance Sensor Reference Design
Product Image
Buy Now
MAXREFDES177
IO-Link Universal Analog IO Reference Design
Product Image
Buy Now
MAXREFDES23DB
IO-Link Light Sensor Reference Design
Product Image
Buy Now
MAXREFDES42
IO-Link RTD Temp Sensor Reference Design

For more IO-Link sensors products. Shop Now


Take the Quiz

Back to Top

Sensors VIIII

Sensors VIIII

Complete our Essentials: Sensors VIIII course, take the quiz, and leave your feedback to earn this badge.

Are you ready to demonstrate your IO-Link sensors knowledge? Then take this 10-question quiz. To earn the Sensors IX Badge, read through the module, attain 100% in the quiz, and leave us some feedback in the comments section.

To learn more about connectors click the next button for more educational modules.

  • industry 4.0
  • io-link
  • sensors
  • binary sensor
  • maxim integrated
  • industrial sensing
  • transceiver
  • industrial sensor
  • sdci
  • uart
  • smart sensor
  • io-link sensor
  • industrial sensors
  • ess_module
  • Share
  • History
  • More
  • Cancel
  • Sign in to reply
  • Former Member
    Former Member 9 months ago

    Good learning

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • misaz
    misaz over 2 years ago in reply to cghaba

    No. You can use whatever MCU you want. You need one GPIO, one SPI and one UART according to datasheet.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • cghaba
    cghaba over 2 years ago

    Do we need a 32-bit microcontroller to talk to MAX14828 or we can use also a 16-bit one?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • will06
    will06 over 2 years ago

    Interesting. By the way the Roman numeral for 9 is IX not VIIII.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • kmikemoo
    kmikemoo over 2 years ago

    Great learning.  Sorry folks, I can't help but think of the cartoon "How standards proliferate". Laughing

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • mp2100
    mp2100 over 2 years ago

    The explanation here about IO-Link is better than I get in the PLC industry, where it's all marketign jargon, so thank you E-14.

    I'm surprised they use an M4 microprocessor to send this data, it's usually minimal information per sensor.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • misaz
    misaz over 2 years ago

    After previous IO-link quiz it was much easier. It is nice that there is opportunity to test this in practise as part of RoadTest which runs at the same time as essential module and quiz was published. It is nice concept. I think it is nice to combine running Roadtest and Essentials at the same time.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • misaz
    misaz over 2 years ago in reply to dougw

    Question about "11bit thing" is crazy. I was prepared after reading your comment. I alaways gueset that start, stop and partity bits do not count as part of UART frame size...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • dougw
    dougw over 2 years ago

    I missed that 11 bit thing....

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • ralphjy
    ralphjy over 2 years ago

    Interesting information.  As one who doesn't design or use industrial networks, I'm not sure when I would be able to put it to use.  Maybe one day residential sensor/control networks will be more robust...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube