The IOLinkDeviceEventType is the base EventType for Events generated from IO-Link Devices. It is formally defined in Table 48.

Table 48– IOLinkDeviceEventType Definition








Node Class




Modelling Rule

Subtype of IOLinkEventType defined in section 9.2.




The following rules for the inherited Properties apply.

  • The mandatory Property SourceNodeshall be the NodeId of the object representing the IO-Link Device the event originates from.
  • The mandatory Property SourceNameshall be the string part of the BrowseName of the Object representing the IO-Link Device the Event originates from.
  • The mandatory Property Timeshall be the time the IO-Link Master receives the Event from the IO-Link Device.

Note that the event might have been generated already at an earlier time (more than communication delays) in the IO-Link Device, before it was received by the IO-Link Master.

  • The mandatory Property ReceiveTimeshall be set to the time the OPC UA Server receives the event. In case the OPC UA Server runs on the IO-Link Master, this might be the same value as the value of Property Time.
  • In case the IO-Link event code is not described in an IODD, the mandatory Property Messageshall be set to “IO-Link EventCode: 0x<xxxx>” for the English locale, where xxxx is the event code as hexadecimal representation. For example, for event code 0x18FF the message shall be “IO-Link EventCode: 0x18FF”. The server may provide different locales containing a translation of that string. In case the IO-Link Specificationdefines a specific string (Table D.1 of IO-Link Specification) for a specific event code, the server may also use that string instead of the generic message. For example, for event code 0x4000 the string “Temperature fault – Overload” is defined and can be used alternatively as Message.
  • The mandatory Property IOLinkEventCodeshall provide the two-octet event code of the IO-Link Device as UInt16.