Status code Status name Description
0x16 Object instance does
not exist
The specified object does not exist in the device.
0x17 Service fragmentation
out of sequence
The fragmentation sequence for this service is not active for this
data.
0x18 No stored attribute
data
The attribute data of this object was not stored before the requested
service.
0x19 Store operation failure The attribute data of this object was not stored due to a detected
error during the attempt.
0x1A 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 stop the service.
0x1B 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 stop the service.
0x1C Missing attribute list
entry data
The service did not provide an attribute from the attribute list
required by the service to perform the requested behavior.
0x1D Invalid attribute value
list
The service returns the list of attributes that contains status
information about invalid attributes.
0x1E Embedded service
error
An embedded service resulted in an error.
0x1F Vendor specific error A vendor-specific error was detected. The additional code field of the
error response specifies the detected error. This general error code
must only be used if none of the error codes displayed in this table
or in an object class definition accurately represents the detected
error.
0x20 Invalid parameter A parameter associated with the request was invalid. This code is
used if a parameter does not comply with the requirements of this
specification and/or the requirements defined in an application object
specification.
0x21 Write-once value or
medium already
written
An attempt was made to write to a write-once medium (for example,
WORM drive, PROM) that has already been written. Or, an attempt
was made to modify a value that cannot be modified once
established.
0x22 Invalid Reply Received An invalid response is received (for example, reply service code
does not correspond to the request service code, or the response
message is shorter than the minimum expected response size). This
status code can be used for other purposes of invalid responses.
0x23 Buffer Overflow The message received is larger than the receiving buffer can handle.
The entire message was discarded.
0x24 Message Format Error The format of the received message is not supported by the server.
0x25 Key Failure in path The key segment that was included as the first segment in the path
does not correspond to the target module. The object-specific status
must specify which part of the key check was unsuccessful.
0x26 Path Size Invalid The size of the path sent with the service request is either not large
enough to allow the request to be forwarded to an object, or too
much routing data has been included.
0x27 Unexpected attribute in
list
The attribute cannot be set at this time.
0x28 Invalid Member ID The member ID specified in the request does not exist in the
specified class/instance/attribute.
17.34 CIPMGET (CIP Message Data Getting)
17-178 WUME-FP7CPUPGR-12
To Next Page
Loading...
Need help?
General
