Diagnostic Alarm; Io-Link Event Mapping Overview; Io-Link Eventcode Mapping - Emerson RSTi-OM User Manual

Fieldbus module with profinet io and modbus/tcp
Hide thumbs Also See for RSTi-OM:
Table of Contents

Advertisement

RSTi-OM User Manual
GFK-3212A
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.
IO-Link Event Mapping
IO-Link Event Mode
Single
Coming
Going
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.
The following table summarizes how IO-Link EventCode is mapped to PROFINET diagnostics.
IO-Link EventCode Mapping
Source
IO-Link
Device
(remote)
IO-Link
Device
(remote)
IO-Link
Master
(local)
PROFINET IO Reference Information
PROFINET
Process alarm
Add channel diagnostics
Remove channel diagnostics
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.
EventCode
0x0000-0x7FFFF
0x8000-0xFFFF
0x0000-0x7FFFF
ChannelError
ExtChannel
Type
ErrorType
0x0000-
0x500
0x7FFFF
0x0000-
0x501
0x7FFFF
0x0000-
0x502
0x7FFFF
Section 10
Comment
Direct mapping of
EventCode to
ExtChannelErrorType (e.g.
EventCode 0x6321 will be
mapped to
ExtChannelErrorType
0x6321)
Mapping of EventCode to
ExtChannelErrorType. Set
MSB (EventCode) to "0"
(e.g. EventCode 0x8005
| ExtChannelErrorType
0x0005
Direct mapping of local
EventCode to
ExtChannelErrorType
Jun 2021
106

Advertisement

Table of Contents
loading

This manual is also suitable for:

Omiolm001

Table of Contents