Video summary

IOLK01. IO-Link Overview and Knowledge Sharing, Smart Sensor & Smart Devices

Main summary

Key takeaways

Technology

Summary of the subtitles (IO-Link overview, setup, and practical guidance)

Video series introduction & hardware used

  • The video series introduces an “IO-Link series” focused on:
    • Connecting an IO-Link master to IO-Link sensors
    • Reading process data
    • Configuring/writing parameters
  • The presenter acquired multiple example products to cover common scenarios:
    • An IO-Link master with PROFINET/performance bus support (subtitle: “perfinite fuel bus function”)
    • An IO-Link master with Ethernet/IP support (subtitle: “Ethernet IP fuelb function”)
    • A Siemens CM (4-port) IO-Link master intended for installation on the right side of a Siemens ET200 system
    • An example IO-Link sensor: a distance measurement sensor
  • They estimate these modules cover ~80–90% of common use cases in real systems.

What IO-Link is (architecture & topology)

  • IO-Link requires:
    • An IO-Link master, which connects to a PLC via a fieldbus such as PROFINET, Ethernet/IP, or EtherCAT (examples mentioned)
    • IO-Link devices (e.g., sensors/actuators)
  • Point-to-point communication:
    • Each IO-Link device is connected directly to the IO-Link master.
    • No daisy-chaining / downstream chaining.
    • Typical maximum cable length: < 20 m (repeated for multiple connections).
  • Master ports:
    • Typical IO-Link masters have 4, 8, or 16 ports.
    • Each port corresponds to one IO-Link device.

IODD files (device description)

  • Every IO-Link device provides an IODD file (IO-Link Device Description), similar to GSD files in PROFINET.
  • The IODD contains important identifiers and configuration data, including:
    • Vendor ID
    • Device ID
    • Process data layout
    • Parameter indexes
  • The master uses the IODD to correctly understand and configure different device models and brands.

Why IO-Link differs from traditional sensors

  • Traditional sensors/actuators often use:
    • Power (e.g., 24V + / 24V −)
    • A simple signal
  • IO-Link uses a 5-wire IO-Link connection:
    • Communication is integrated into the cable
    • It supports digital communication, configuration, and diagnostics

Cable/pin concepts and connector notes

  • IO-Link uses a 5-pin male/female cable:
    • One end is male, the other is female (depending on master/device connector type).
  • Pin functions are described in the subtitles as:
    • Pin 1: power
    • Pin 3: power negative
    • Pin 2: configurable digital input/output (connector-type dependent)
    • Pin 4: primary IO-Link communication
  • Type B is mentioned as supporting additional power via pin 2 and pin 5.
  • Constraint reiterated:
    • Unshielded cables are acceptable when distance < 20 m.

Communication speed (important constraint)

  • IO-Link supports three communication speeds (exact values not provided in the subtitles).
  • The master performs adaptive communication based on the device’s defined working speed.
  • Since IO-Link is point-to-point, there may still be concerns about reaction speed / throughput for fast control loops.

Tutorial/guide focus: parameter read/write (not plug-and-play)

  • The presenter stresses IO-Link is not fully plug-and-play:
    • You usually need engineering tools to configure the master and device.
    • Many smart devices require parameter writing using the IODD-based workflow.
  • One mentioned exception:
    • If you only need to read process IO, you may be able to avoid full IODD/parameter configuration depending on the workflow.

Process data vs. parameters

  • Process data (cyclic communication):
    • Used for exchanging real-time measurement values and simple control values (e.g., lamp control).
    • Can also include device status/quality, such as invalid measurements due to contamination.
  • Parameters (event/configuration):
    • Typically require special PLC programming.
    • Parameter read/write usually needs function blocks rather than simple IO reads.
    • Siemens is referenced as providing IO-Link function blocks and sample programs.

Tools for configuration

  • Configuration can be done via two common approaches:
    1. PLC function blocks/programming
    2. Vendor engineering/configuration tools (PC software)
  • Example:
    • Siemens provides an “i7 PCT” tool (subtitle indicates IO-Link configuration tool), where you can:
      • Load IODD
      • Let the master identify devices
      • Modify parameters
  • They note that some vendor tools are free, while others may require purchase.

Selecting an IO-Link master

Key selection criteria:

  • The master must support the required PLC connectivity (PROFINET, Ethernet/IP, EtherCAT, etc.).
  • The master ecosystem should provide sample programs/function blocks for your PLC platform.
  • Engineers should align:
    • Control software capability
    • Field deployment requirements
    • Your existing PLC ecosystem

Troubleshooting identifiers: vendor ID & device ID

  • Two identifiers are repeatedly emphasized:
    • Vendor ID
    • Device ID
  • Helpful online resources mentioned:
    • A “Wonder ID” table/list
    • iodfinder.ioink.com (to search for devices and obtain the correct IODD file)
  • Example troubleshooting/config workflow:
    • Even if a Siemens CM auto-discovery workflow doesn’t work, you can configure a port manually using vendor ID/device ID from the IODD or the device manual.

What the next videos will cover

The next videos will use three scenarios:

  1. IO-Link master with PROFINET
  2. IO-Link master with Ethernet/IP
  3. Siemens CM module (CM + ET200)

They will demonstrate:

  • Reading process data / regular IO
  • Reading and writing device parameters

Main speakers/sources

  • Main speaker: The video author/presenter (no name provided in the subtitles).
  • Sources/products mentioned:
    • Siemens: CM module, ET200, IO-Link configuration tool, function blocks
    • Example device/master vendors referenced: ifm, SICK, Rockwell, Baumer (brands mentioned as examples)
    • External resources:
      • iodfinder.ioink.com
      • IO-Link IODD / Wonder ID listings

Original video