IO-Link Events: Example implementations of event propagation

Ethernet/IP

1.) Check if events are pending
2.) Read out event details
2.1) Explicit message
3.) Interpretation of event details

Ethernet/IP

Attached example program (SIG350_EventExample.ACD) shows how events could be read using SIG350 with Ethernet/IP interface.

• PLC:   Allen Bradly, L30ER
• IO-Link Master:   SIG350
• Rockwell Logix Designer, Studio 5000

1.) Check if events are pending

Source: SIG350 user manual

Ethernet/IP input process data of SIG350 contains a IOL status byte which has following coding:

Source: SIG350 user manual

Using Bit3 the IO-Link Master reports if there are currently events pending or not.

First line in the main program of the example project copies the flag into a variable.

2.) Read out event details

To read the details (Event Qualifier, Event Code) there is CIP object which offers access to all information.

Details are found in the attached document (IO-Link CIP Integration-v58.pdf), chapter 8.
To get the event details the CIP explicit messaging system needs to be used.

The easiest access offers attribute 22.

The response of the explicit message is the oldest pending event at the respective port.
Reading the event automatically deletes this event from the queue in the IO-Link master.
As soon as all pending events have been read / have been deleted the "Event Flag" in the Ethernet/IP process data is erased.

2.1) Explicit message

• Service Code: 0x0E
• Class code: 0x41
• Instance: 100...107
• Attribute: 0x16

3.) Interpretation of event details

In the attached example program you find an example implementation how an event could be interpreted.

The interpreted event is then found in the controller tags of the example program.