Generic Control Expert Protocol error.

Generic communication error.

PLC is reserved by someone else.

You must reserve the PLC.

Unknown request or subcode.

Unknown object (for example: %Z not implemented).

The response could not be built.

Request has invalid parameters (for example: the request is badly built, or has few/many parameters or has a bad Csa command, and so on.)

Bad sequence (for example: EndDownload executed before BeginDownload).

The size of the response exceed the size of the available buffer.

Module not configured (may be bad address).

Action is not permitted on this object.

Busy state: the previous operation is still working, or all internal resources are busy for the I/O request, or too much parallel upload, and so on.

Generic error: something wrong in application.

Access violation: write read-only block, or read-only variable, or download while memory is protected, and so on.

Object not accessible because it is in use.

Out of bounds: exceeds the range of %MW, or too many breakpoints, or call stack too large, and so on.

Invalid length.

Reference to a non-existent resource or task, or variable address is not in the DFB data area, and so on.

The object or resource is already defined. For example: trying to start an already started, or a breakpoint-ID already used, and so on.

Data inconsistent or data state not allowed. For example: wrong data or bad value when writing an object.

The object exists but is not initialized.

Channel out of bounds in an I/O request.

Request not yet implemented.

Incompatible application, wrong target, or platform.

Signature check failed.

Wrong PCMCIA memory configuration.

PLC is not in the right mode: download with PLC in RUN mode, or debug while PLC in NOCONF, try to step a task, not break-pointed, upload operation aborted by download or OnlineChange, and so on.

Mode cannot be changed: an I/O forces premium to stop.

An internal timeout occurred.

The watchdog time is elapsed.

Data dictionary generic report code

Undefined general error.

Exchange error.

Another explicit exchange is in progress.

Operation is impossible.

Data is rejected by the IOB.

Writing is not authorized.

Maximum number of exchanges.

Unknown object.

Invalid read buffer.

Unknown or invalid action.

All the buffers are in use.

Object out of range.

Object value forbidden (write operations only).

Channel out of range.

Exchange stop on timeout.

Exchange stop on user request (CANCEL).

Incorrect address format.

Incorrect destination address

Incorrect management parameter format.

Incorrect specific parameters.

Error detected in sending to the destination.

Reserved.

Insufficient receive buffer size.

No processor system resources.

Incorrect exchange number.

No telegram received.

Incorrect length.

Telegram service not configured.

Network module missing.

Request missing.

Application server already active.

UNI-TE V2 transaction number incorrect.

Request not processed.

Incorrect response.

No resources towards the processor.

No line resources.

No device or device without resources.

Line error.

Length error.

Faulty communication channel.

Addressing error.

Application error.

No system resources.

Communication function not active.

Destination missing.

Intra-station routing problem or channel not configured.

Address format not managed.

No destination resources.

Non-operational connection (example: Ethernet TCP/IP).

No resource on the local channel.

Access not authorized (example: Ethernet TCP/IP).

Inconsistent network configuration (example: Ethernet TCP/IP).

Connection temporarily unavailable.

Application server stopped.

Transmission error.

A connection-related service was unsuccessful along the connection path.

Resources needed for the object to perform the requested service were unavailable.

See status code 0x20, which is the preferred value to use for this condition.

The path segment identifier or the segment syntax was not understood by the processing node. Path processing stops when a path segment error is detected.

The path is referencing an object class, instance, or structure element that is not known or is not contained in the processing node. Path processing stops when a path destination unknown error is detected.

Only part of the expected data was transferred.

The messaging connection was lost.

The requested service was not implemented or was not defined for this object class/instance.

Invalid attribute data detected.

An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero status.

The object is already in the mode/state being requested by the service.

The object cannot perform the requested service in its current mode/state.

The requested instance of object to be created already exists.

A request to modify a non-modifiable attribute was received.

A permission/privilege check was unsuccessful.

The mode/state of the device prohibits the execution of the requested service.

The data to be transmitted in the response buffer is larger than the allocated response buffer.

The service specified an operation that is going to fragment a primitive data value, that is, half a REAL data type.

The service did not supply enough data to perform the specified operation.

The attribute specified in the request is not supported.

The service supplied more data than was expected.

The object specified does not exist in the device.

The fragmentation sequence for this service is not currently active for this data.

The attribute data of this object was not saved prior to the requested service.

The attribute data of this object was not saved due to an unsuccessful attempt.

The service request package was too large for transmission on a network in the path to the destination. The routing device was forced to abort the service.

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.

The service did not supply an attribute in a list of attributes that was needed by the service to perform the requested behavior.

The service is returning the list of attributes supplied with status information for those attributes that were invalid.

An embedded service resulted in a detected error.

A vendor-specific error has been detected. The additional code field of the error response defines the particular error encountered. Use this general code only when none of the codes presented in this table or within an object class definition accurately reflect the detected error.

A parameter associated with the request was invalid. This code is used when a parameter does not meet the requirements of this specification and/or the requirements defined in an application object specification.

An attempt was made to write to a write-once medium (for example, WORM drive, PROM) that has already been written, or to modify a value that cannot be changed once established.

An invalid reply is received (for example, reply service code does not match the request service code, or reply message is shorter than the minimum expected reply size). This status code a serve for other causes of invalid replies.

The message received is larger than the receiving buffer can handle. The entire message was discarded.

The format of the received message is not supported by the server.

The key segment that was included as the first segment in the path does not match the destination module. The object-specific status indicates which part of the key check was unsuccessful.

The size of the path that was sent with the service request is either not large enough to allow the request to be routed to an object or too much routing data was included.

An attempt was made to set an attribute that is not able to be set at this time.

The member ID specified in the request does not exist in the specified class/instance/attribute.

A request to modify a non-modifiable member was received.

This detected error code may only be reported by DeviceNet group 2 only servers with 4 Kb or less code space and only in place of service not supported, attribute not support, or attribute not settable.

A CIP to Modbus translator received an unknown Modbus exception code.

A request to read a non-readable attribute was received.

Reserved by CIP for future extensions.

This range of detected error codes is used to indicate object class-specific detected errors. Use this range only when none of the codes presented in this table accurately reflect the error that is detected.