![background image](http://html1.mh-extra.com/html/omron/e5zn-drt/e5zn-drt_operation-manual_742104107.webp)
92
Overview of Explicit Message Communications
Section 6-1
Note The number of digits used for the Class ID, Instance ID, and Attribute ID
depends on the master used. When sending parameters from an OMRON
Master Unit, the values are expressed as follows:
Class ID:
4-digit (2-byte) hexadecimal
Instance ID: 4-digit (2-byte) hexadecimal
Attribute ID: 2-digit (1-byte) hexadecimal
Response Block
• The following format is used when a normal response is returned for the
sent explicit message.
• The following format is used when an error response is returned for the
sent explicit message.
Number of Bytes Received
The number of data bytes received from the source node address is returned
as a hexadecimal. When an error response is returned for the explicit mes-
sage, the contents is always 0004 hex.
Source Node Address
The node address of the master that sent the explicit message is returned as
a hexadecimal.
Service Code
For normal responses, the value for when the most significant bit (bit 07) of
the service code specified in the command turns ON is returned. (When the
service code of the command is 0E hex, the service code of the response will
be 8E hex.) When an error response is returned for the explicit message, the
contents is always 94 hex.
Data
Read data is included only when a read command is executed.
Error Code
The following table shows the error codes for explicit messages.
Note For DeviceNet Communications Units, set the DeviceNet message monitor
timer to 6 s or longer, using the following procedure.
No. of bytes
received
Source node
address
Service code
Data
No. of bytes
received
0004 hex, fixed
Source node
address
Service code
Error code
(2 bytes, fixed)
Error
code
Error name
Cause
08FF
Service not supported
The service code is not supported.
09FF
Invalid Attribute value
The Attribute Value is not supported.
16FF
Object does not exist
The Instance ID is not supported.
15FF
Too much data
The data string is too long.
13FF
Not enough data
The data string is too short.
14FF
Attribute not supported The Instance ID is not supported.
0CFF
Object state conflict
The command cannot be executed.
• Error in communications with Temperature Con-
troller.
• The BCC value did not match in the response
from the Temperature Controller.
20FF
Invalid Parameter
The specified parameter is incorrect.
0EFF
Attribute not settable
A write service code was sent for a read-only
Attribute ID.
1F
**
Vendor specific error
An error response was returned for a CompoWay/F
message sent to the Temperature Controller.
Note
The
**
in the code indicate the MRC of the
CompoWay/F response.
Summary of Contents for E5ZN-DRT
Page 3: ...iv ...
Page 5: ...vi ...
Page 9: ...x ...
Page 15: ...xvi EC Directives 6 ...
Page 83: ...68 Ladder Programming Examples Section 4 5 ...
Page 123: ...108 Sending Explicit Messages Section 6 5 ...
Page 135: ...120 Message Communications Characteristics Section 7 2 ...
Page 157: ...142 Index Unit status 57 85 user set allocations 43 61 V variable types C0 51 C1 51 C3 52 ...
Page 159: ...144 Revision History ...
Page 161: ...E5ZN DeviceNet Communications Unit Cat No H119 E1 01 OPERATION MANUAL ...