Back to overview
Knowledge · IODD

What is an IODD – and why does IODD parsing matter for LoRaWAN?

An IO-Link sensor only sends bytes. Its device description, the IODD, defines what those bytes mean. This page explains the concept, how parsing works and why it makes the difference between raw data and usable measurements on LoRaWAN.

IODD
IO Device Description – XML device description per sensor
Standard
Part of the IO-Link specification (IEC 61131-9)
Source
Manufacturer, centrally via the IODDfinder portal
Parsing
Bytes → name, value, unit, status
01 · The concept

A package leaflet for every device

The IODD is a standardised XML file the manufacturer provides for every IO-Link device. It describes process data, parameters, events, units, scaling and value ranges. Software reads this file instead of maintaining custom byte tables for every device.

  • Device identity

    Vendor ID, device ID, name and variant – so it is clear which description applies.

  • Process data

    Which bits and bytes are transmitted cyclically, with data type and position.

  • Parameters (ISDU)

    Configurable values such as switch points, filters or units – with index and access rights.

  • Units & scaling

    Factor, offset and unit that turn the raw number into a physical value.

  • Events & diagnostics

    Codes for warnings and errors with plain-text descriptions.

  • Texts & languages

    Labels in several languages for display in tools and dashboards.

Excerpt · simplified example.xml
<IODevice>
  <DeviceIdentity vendorId="310" deviceId="…"/>
  <ProcessDataIn bitLength="32">
    <RecordItem subindex="1" bitOffset="16">
      <SimpleDatatype type="UIntegerT" bitLength="16"/>
      <Name textId="distance"/>   <!-- mm -->
    </RecordItem>
    <RecordItem subindex="2" bitOffset="8">
      <SimpleDatatype type="BooleanT"/>
      <Name textId="switch_output_1"/>
    </RecordItem>
  </ProcessDataIn>
</IODevice>
Simplified, illustrative example – not a complete IODD excerpt of a real device.
02 · IODD parsing

From 4 bytes to a measurement in four steps

  1. 1

    Identify the device

    Vendor and device ID identify the sensor and its matching IODD.

  2. 2

    Split the bytes

    The IODD defines bit position and length of every process data item.

  3. 3

    Type & scaling

    Data type, factor and offset convert the raw number into a value.

  4. 4

    Add meaning

    Name, unit and status turn it into e.g. “distance: 386 mm”.

01 82distance386 mm
00switch_output_1active
3CstatusOK

Illustrative example, not a real sensor value.

03 · Why it matters for LoRaWAN

LoRaWAN carries compact bytes – the meaning has to come from elsewhere

LoRaWAN is built for small, periodic messages. An uplink carries only a few dozen bytes, without field names or units. Without interpretation, your application receives cryptic hex values.

  • Small payloads

    Sending field names and units over the air would cost airtime and battery. The IODD adds them afterwards.

  • No decoder per sensor

    Instead of writing a payload decoder for every sensor type, the device's IODD is used.

  • Vendor-independent

    Whether ifm, SICK, Balluff or others: the IODD is standardised, the process stays the same.

  • Fewer errors

    Scaling and units come from the manufacturer, not from hand-written tables.

  • Swap sensors without reprogramming

    New sensor, new IODD – the data chain stays in place.

  • Directly usable data

    Dashboards, MQTT or REST consumers receive named values instead of bytes.

04 · Where parsing happens

Device, network server or cloud

Interpretation can happen at different points in the chain. With the AION LIO the radio transmission stays compact; translation happens where the IODD is available – for example in the Sentinum Cloud or in your own application. The overview on the home page shows which approaches are available and which are planned.

See the four approaches
Discover AION LIO