3100

Generic Control Expert Protocol error.

3180

Generic communication error.

3181

PLC is reserved by someone else.

3182

You must reserve the PLC.

3183

Unknown request or subcode.

3184

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

3185

The response could not be built.

3186

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.)

3187

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

3188

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

3189

Module not configured (may be bad address).

318A

Action is not permitted on this object.

318B

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.

3190

Generic error: something wrong in application.

3191

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

3192

Object not accessible because it is in use.

3193

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

3194

Invalid length.

3195

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

3196

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

3197

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

3198

The object exists but is not initialized.

3199

Channel out of bounds in an I/O request.

319A

Request not yet implemented.

31A0

Incompatible application, wrong target, or platform.

31A1

Signature check failed.

31A2

Wrong PCMCIA memory configuration.

31B0

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.

31B1

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

31B2

An internal timeout occurred.

31B3

The watchdog time is elapsed.

31C0

Data dictionary generic report code

31FF

Undefined general error.

3202

Exchange error.

3207

Another explicit exchange is in progress.

3209

Operation is impossible.

320A

Data is rejected by the IOB.

320B

Writing is not authorized.

320C

Maximum number of exchanges.

3284

Unknown object.

3286

Invalid read buffer.

328A

Unknown or invalid action.

328B

All the buffers are in use.

3293

Object out of range.

3297

Object value forbidden (write operations only).

3299

Channel out of range.

3401

Exchange stop on timeout.

3402

Exchange stop on user request (CANCEL).

3403

Incorrect address format.

3404

Incorrect destination address

3405

Incorrect management parameter format.

3406

Incorrect specific parameters.

3407

Error detected in sending to the destination.

3409

Reserved.

340A

Insufficient receive buffer size.

340B

No processor system resources.

340C

Incorrect exchange number.

340D

No telegram received.

340E

Incorrect length.

340F

Telegram service not configured.

3410

Network module missing.

3411

Request missing.

3412

Application server already active.

3413

UNI-TE V2 transaction number incorrect.

3501

Request not processed.

3502

Incorrect response.

3601

No resources towards the processor.

3602

No line resources.

3603

No device or device without resources.

3604

Line error.

3605

Length error.

3606

Faulty communication channel.

3607

Addressing error.

3608

Application error.

360B

No system resources.

360C

Communication function not active.

360D

Destination missing.

360F

Intra-station routing problem or channel not configured.

3611

Address format not managed.

3612

No destination resources.

3614

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

3615

No resource on the local channel.

3616

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

3617

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

3618

Connection temporarily unavailable.

3621

Application server stopped.

3630

Transmission error.

3701

Connection unsuccessful

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

3702

Resource unavailable

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

3703

Invalid parameter value

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

3704

Path segment error

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.

3705

Path destination unknown

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.

3706

Partial transfer

Only part of the expected data was transferred.

3707

Connection lost

The messaging connection was lost.

3708

Service not supported

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

3709

Invalid attribute value

Invalid attribute data detected.

370A

Attribute list error

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

370B

Already in requested mode/state

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

370C

Object state conflict

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

370D

Object already exists

The requested instance of object to be created already exists.

370E

Attribute not settable

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

370F

Privilege violation

A permission/privilege check was unsuccessful.

3710

Device state conflict

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

3711

Reply data too large

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

3712

Fragmentation of a primitive value

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

3713

Not enough data

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

3714

Attribute not supported

The attribute specified in the request is not supported.

3715

Too much data

The service supplied more data than was expected.

3716

Object does not exist

The object specified does not exist in the device.

3717

Service fragmentation sequence not in progress

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

3718

No stored attribute data

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

3719

Store operation unsuccessful

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

371A

Routing unsuccessful, request packet too large

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.

371B

Routing unsuccessful, 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.

371C

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.

371D

Invalid attribute value list

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

371E

Embedded service error

An embedded service resulted in a detected error.

371F

Vendor-specific 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.

3720

Invalid parameter

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.

3721

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 to modify a value that cannot be changed once established.

3722

Invalid reply received

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.

3723

Buffer overflow

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

3724

Message-format error

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

3725

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 indicates which part of the key check was unsuccessful.

3726

Path size invalid

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.

3727

Unexpected attribute in list

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

3728

Invalid member ID

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

3729

Member not settable

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

372A

Group 2 only server — general error

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.

372B

Unknown Modbus error

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

372C

Attribute not gettable

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

372D...37CF

–

Reserved by CIP for future extensions.

37D0...37FF

Reserved for object class and service errors

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.