Basic format of explicit messages – Rockwell Automation 1791DS-IBxxxx Guard I/O DeviceNet Safety Modules User Manual
Page 157
![background image](/manuals/579642/157/background.png)
Rockwell Automation Publication 1791DS-UM001J-EN-P - May 2013
157
Get Point Status from Modules by Using Explicit Messaging
Appendix A
Basic Format of Explicit
Messages
The basic format of each command and response is as follows.
· Destination Node Address - The node address of the module that is
sending the explicit messages is specified with a 1 byte hexadecimal.
· Service Code, Class ID, Instance ID, Attribute ID - The parameters used
for specifying the command, processing object, and processing content.
· Data - Data is not required when the read command is used.
· Number of Bytes Received - The number of bytes received from the source
node address is returned in hexadecimal. When an error response is
returned for an explicit message, the number of bytes is always 0004 hex.
· Source Node Address - The node address of the node from which the
command was sent is returned in hexadecimal.
· Service Code - For normal completions, the service code specified in the
command with the leftmost bit turned ON is stored as shown in the
See Function, Command Service Code, and Response Service Code on
page 157
.
When an error response is returned for an explicit message, the value is always 94
hex.
· Data - Read data is included only when a read command is executed.
· Error code - The explicit message error code
Table 26 - Command Block
Destination Node Address
Service Code
Class ID
Instance ID
Attribute ID
Data
Table 27 - Normal Response Block
Number of Bytes Received
Source Node Address
Service Code
Data
Table 28 - Error Response Block
Number of Bytes Received 0004 hex (fixed)
Source Node Address
Service Code
Error Code
Table 29 - Function, Command Service Code, and Response Service Code
Function
Command Service Code (hex)
Response Service Code (hex)
Read Data
10
90
Write Data
0E
8E
Reset
05
85
Save
16
96