Explicit messages – Rockwell Automation 1791ES-IB16 Guard I/O EtherNet/IP Safety Modules User Manual
Page 88

88
Rockwell Automation Publication 1791ES-UM001D-EN-P - May 2013
Appendix A
Get Diagnostic Status from Modules by Using Explicit Messaging
Explicit Messages
Explicit messaging can also be used to read individual channel status for safety
inputs, safety outputs, test outputs, and power status. Communication error
settings can also be configured and monitored for test outputs as well.
Table 23 - Reading the Cause of the Safety Input Error
Explicit
Message
Service
Function
Command (hex)
Response (hex)
Service
Code
Class
ID
Instance
ID
Attribute ID
Data Size
Safety Input
Cause of Error
(Fault)
Information
Read
Get
Attribute
Single
Reads the cause
for the status bit
(1…n), specified
by the Instance ID,
turning OFF.
0E
3D
01…n
6E
-
0: No error
01: Configuration invalid
02: External test signal error
03:Internal input error
04: Discrepancy error
05: Error in the other dual channel
input
Table 24 - Reading the Cause of the Safety Output Error
Explicit Message
Service
Function
Command (hex)
Response (hex)
Service
Code
Class
ID
Instance ID
Attribute ID
Data Size
Safety Output
Cause of
Error (Fault)
Information
Get Attribute
Single
Reads the cause for the
status bit (1…n),
specified by the
Instance ID, turning
OFF.
0E
3B
01…n
6E
-
0: No error
01:
Configuration invalid
02:
Over current detected
03:
Short circuit detected
04:
Output ON error
05:
Error in the other dual channel output
08:
Output data error
09:
Short circuit detected at
safety output
Table 25 - Monitoring the Test Output Point
Explicit Message
Service
Function
Command (hex)
Response (hex)
Service
Code
Class
ID
Instance ID
Attribute ID
Data
Size
Test Output
Cause of Error (Fault)
Information
Get Attribute
Single
Reads the cause for
the status bit (1…n),
specified by the Instance ID,
turning OFF.
0E
09
01…n
76
-
0 = No error
01:
Configuration invalid
02:
Overload detected
05:
Output ON error
06:
Undercurrent detected for
muting lamp