RSTi-OM User Manual Section 10
GFK-3212A Jun 2021
PROFINET IO Reference Information
106
10.3 Diagnostic Alarm
Events from IO-Link Master and IO-Link devices are mapped to PROFINET alarms and channel
diagnostics according to the IO-Link on PROFINET Working Document Version 13.4.2015 with some
modifications.
10.3.1 IO-Link Event Mapping Overview
IO-Link events are mapped into PROFINET Alarms and Channel Diagnostics using the following table.
Each appearing IO-Link event (mode Coming) results in adding channel diagnostics. Each
disappearing IO-Link event (mode Going) results in removing channel diagnostics. IO-Link events that
have mode Single will be mapped to the PROFINET process alarm.
In addition, only IO-Link events that have the type of Error or Warning are mapped to PROFINET
channel diagnostics. Type Message IO-Link events are not mapped.
Note: Process alarms are reported as ‘Unexpected PROFINET Alarms’ in the IO fault table of the PLC.
10.3.2 IO-Link EventCode Mapping
IO-Link events that are generated by IO-Link devices (remote events) are mapped to PROFINET
diagnostics using ChannelErrorType 0x500 and0x501.
• For an EventCode that is between 0x0000 and 0x7FFF, ChannelErrorType 0x500 is used. The
EventCode is directly mapped to ExtChannelErrorType.
• For an EventCode that is between 0x8000-0xFFFF, ChannelErrorType 0x501 is used. The
EventCode is mapped to ExtChannelErrorType with the MSB set to 0.
• For IO-Link events that are generated by IO-Link Master (local events), ChannelErrorType
0x502 is used.
• EventCode is directly mapped to ExtChannelErrorType.
The following table summarizes how IO-Link EventCode is mapped to PROFINET diagnostics.
To Next Page
Loading...
