5 Implementation of EtherNet/IP
5.2 Classes and instances of the EtherNet/IP-gateway
XI/ON: XNE-GWBR-2ETH-IP
09/2011 MN05002007Z-EN
www.eaton.com
61
18
No stored attribute
data
The attribute data of this object was not saved prior to the
requested service.
19
Store operation
failure
The attribute data of this object was not saved due to a
failure during the attempt.
1A
Routing failure,
request packet too
large
The service request packet was too large for transmission
on a network in the path to the destination. The routing
device was forced to abort the service.
1B
Routing failure,
response packet too
large
The service response packet was too large for transmission
on a network in the path from the destination. The routing
device was forced to abort the service.
1C
Missing attribute list
entry data
The service did not supply an attribute in a list of attributes
that was needed by the service to perform the requested
behavior.
1D
Invalid attribute value
list
The service is returning the list of attributes supplied with
status information for those attributes that were invalid.
1E
Embedded service
error
An embedded service resulted in an error.
1F
Vendor specific error A vendor specific error has been encountered. The Addi-
tional Code Field of the Error Response defines the parti-
cular error encountered. Use of this General Error Code
should only be performed when none of the Error Codes
presented in this table or within an Object Class definition
accurately reflect the error.
20
Invalid parameter
A parameter associated with the request was invalid. This
code is used when a parameter does not meet the require-
ments of this specification and/or the requirements defined
in an Application Object Specification.
21
Write-once value or
medium already
written
An attempt was made to write to a write-once medium (e.g.
WORM drive, PROM) that, has already been written, or to
modify a value that cannot be changed once established.
22
Invalid Reply
Received
An invalid reply is received (e.g. reply service code does not
match the request service code, or reply message is shorter
than the minimum expected reply size). This status code can
serve for other causes of invalid replies.
23 to 24 Reserved by CIP for future extensions
25
Key Failure in path
The Key Segment that was included as the first segment in
the path does not match the destination module. The object
specific status shall indicate which part of the key check
failed.
Table 18:
General status
codes according
to CIP spec.
Status
code
(hex)
Status name
Description