8-27
8 Message Communications
NJ-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
8-2 Using CIP Message Communications
8
8-2-9 Response Codes
0D Object already exists The requested instance of object to be created already
exists.
0E Attribute not settable A request to modify a non-modifiable attribute was
received.
0F Privilege violation A permission/privilege check failed.
10 Device state conflict The device’s current mode/state prohibits the execution of
the requested service.
11 Reply data too large The data to be transmitted in the response buffer is larger
than the allocated response buffer.
12 Fragmentation of a primitive value The service specified an operation that is going to frag-
ment a primitive data value, i.e. half a REAL data type.
13 Not enough data The requested service did not supply enough data to per-
form the specified operation.
14 Attribute not supported The attribute specified in the request is not supported.
15 Too much data The service supplied more data than was expected.
16 Object does not exist An object that does not exist was specified for the
requested service.
17 Service fragmentation sequence
not in progress
The fragmentation sequence for this service is not cur-
rently active for this data.
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 transmis-
sion 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 occurred. The Additional Code
Field of the error response defines the error. This is a gen-
eral error code that is used only for errors that do not cor-
respond to any of the error codes in this table and are not
in an object class definition.
20 Invalid parameter A parameter for the requested service is invalid. This code
is used when a parameter does not meet the requirements
of the 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 or PROM) that was previously written or
cannot be changed.
22 Invalid Reply Received An invalid reply was received. (For example, the reply ser-
vice code does not match the request service code, or the
reply message is shorter than the minimum expected
reply size.) This status code is used for other causes of
invalid replies.
23-24 Reserved by CIP for future extensions.
General sta-
tus code (hex)
Status name Description of status
To Next Page
Loading...
