Library Diagnostic Codes

Library-Specific Diagnostic Codes

This table presents the diagnostic codes of the library:

NOTE: Refer to the drive documentation for an overview of the drive-specific error codes (see documentation of the drive).

Value (hex)

Description

0

No error detected.

1

Interface not implemented.

The function block is not supported by the device.

2

Axis blocked.

The axis is blocked by a different function block which cannot be interrupted.

3

Power disabled.

The power stage must be enabled before the function block can be executed.

4

No re-execution.

The function block cannot be repeated as long as the output Busy = TRUE.

A

Length value out of range.

The value specified for the input Length is outside of the permissible value range. Range: 1 to 4.

B

Parameter address invalid.

The specified parameter address is not supported by the device.

C

Input number out of range.

The number specified for the signal input is outside of the permissible value range1.

D

Output number out of range.

The number specified for the signal output is outside of the permissible value range1.

E

An internal error has been detected. Contact your Schneider Electric service representative.

65

Done.

Execution of the command terminated successfully.

66

Working.

The command is still being executed.

67

Initialization unsuccessful.

Initialization of the library not successful.

68

Configuring.

The command was not executed, the device is not ready.

69

Indeterminable device state.

Internal error detected. Contact your Schneider Electric service representative.

6A

ID out of range.

Internal error detected. Contact your Schneider Electric service representative.

6B

Order not present.

Internal error detected. Contact your Schneider Electric service representative.

6C

Communication error detected. The connection to the device has been interrupted.

6D

Device state invalid.

The function block cannot be executed in the current operating state of the device.

6E

Time-out.

The command was not executed within the time window.

6F

Value out of range.

The value is outside the permissible value range1.

70

Parameter error detected.

Error detected while reading or writing a parameter.

71

Indeterminable response.

Indeterminable response while reading or writing a parameter.

72

Command error detected.

Internal error detected. Contact your Schneider Electric service representative.

73

Buffer full.

Internal error detected. Contact your Schneider Electric service representative.

74

The command was aborted.

75

Parameter not supported by device.

76

Touch probe number invalid.

The specified value for the number of the Touchprobe input is invalid.

77

The specified edge of the Touchprobe input is invalid.

78

Touch probe limit error detected.

The specified value for the number of the Touchprobe inputs is not supported by the library. Up to three Touchprobe inputs are supported.

79

Touch probe inactive.

An attempt has been made to cancel an inactive Touchprobe.

7A

Touch probe active.

An attempt has been made to execute an active Touchprobe.

7B

Attempt to reset an unrecoverable error.

The detected error cannot be reset with MC_Reset.

Restart the device after having remedied the cause of the detected error.

7C

Acceleration out of range.

The value for the acceleration is outside of the permissible value range 1.

7D

Deceleration out of range.

The value for the deceleration is outside of the permissible value range 1.

7E

Position out of range.

The value for the target position is outside of the permissible value range 1.

7F

Velocity out of range.

The value for the target velocity is outside of the permissible value range 1.

80

Torque out of range.

The value for the target torque is outside of the permissible value range 1.

81

Numerator out of range.

The value for the numerator is outside of the permissible value range 1.

82

Denominator out of range.

The value for the denominator is outside of the permissible value range 1.

83

External transition to NST.

The command is not executed due to an external blocking event.

84

Halt active.

The Halt function is active and the command is not executed.

85

Function block Control_ATV active.

The function block cannot be executed as long as the function block Control_ATV is enabled.

86

Not ready for power-on.

The power stage cannot be enabled in the current operating state of the drive.

87

Incorrect drive type.

The function block does not support the linked Axis_Ref type.

88

Setpoint source invalid.

Invalid value at the input SetpointSource of the function block TorqueControl_LXM32 or MoveVelocity_LXM32.

89

The selected homing method is not supported.

8A

The digital output is set to an incorrect signal output function. Set the signal output function to Freely Available.

8B

The operating mode is not supported.

8F

Time-out occurred while enabling/disabling the power stage.

(1) See the respective function blocks documentation for permissible value range.

Fieldbus-Specific Diagnostic Codes for EtherNet/IP and Modbus TCP

This table presents the communication error and diagnostic codes for EtherNet/IP and Modbus TCP:

Value (hex)

Description

100

The exchange is valid.

101

The exchange stopped when the time-out expired.

102

The exchange was stopped by a user request (the Abort command).

103

The address format is incorrect.

104

The address of the remote device is incorrect.

105

The management table format is incorrect.

106

Specific parameters are incorrect.

107

An error occurred while sending the request to the destination.

109

The reception buffer size is insufficient.

10A

The transmission buffer size is insufficient.

10B

A system resource is unavailable.

10C

The transaction number is incorrect.

10E

The length is incorrect.

1FE

The operation error code contains a protocol-specific code.

1FF

The message was refused.

201

The target system resource is incommunicative.

205

The length is incorrect.

206

The communication channel is associated with an error detected.

207

The address is incorrect.

20B

A system resource is unavailable.

20C

A target communication function is not active.

20D

The target is incommunicative.

20F

The channel is not configured.

300

The exchange is valid.

301

The request has not been processed.

302

The received response is incorrect.

400

Service was successfully performed by the object specified.

401

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

402

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

403

Internal error code. Contact your local Schneider Electric service representative.

404

The path segment identifier or the segment syntax was incorrect. Path processing stops when this error is encountered.

405

The path is referencing an object class, instance, or structure element that is incorrect or is not contained in the processing node. Path processing stops when this error is encountered.

406

Only part of the expected data was transferred.

407

The messaging connection was lost.

408

The requested service was not implemented or was not defined for this Object Class/Instance.

409

Invalid attribute data.

40A

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

40B

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

40C

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

40D

The requested instance of object to be created already exists.

40E

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

40F

A permission/privilege check is unsuccessful.

410

The mode/state of the device does not allow the execution of the requested service.

411

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

412

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

413

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

414

The attribute specified in the request is not supported.

415

The service supplied more data than expected.

416

The object specified does not exist in the device.

417

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

418

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

419

The attribute data of this object was not saved.

41A

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.

41B

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.

41C

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

41D

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

41E

An embedded service resulted in an error.

41F

A vendor-specific error has been encountered. The Additional Code field of the error response defines the particular error encountered. Use of this general diagnostic code should only be performed when none of the diagnostic codes presented in this table or within an Object Class definition accurately reflect the error.

420

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.

421

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.

422

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 can serve for other causes of invalid replies.

423

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

424

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

425

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

426

The size of the path which 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.

427

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

428

The member ID specified in the request does not exist in the specified Class/Instance/Attribute.

429

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

42A

This diagnostic code may only be reported by Group 2. Only servers with 4 K or less code space and only in place of service not supported, attribute not supported and attribute not settable.

42B

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

42C

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

42D

The requested object instance cannot be deleted.

42E

The object supports the service, but not for the designated application path (for example, attribute).

4FE

The operation error code contains protocol specific code.

The explicit message has been sent but the target has not responded it or has replied with an error code.

4FF

No response from the target.

Fieldbus-Specific Diagnostic Codes for CANopen

This table presents the communication error and diagnostic codes for CANopen:

Value (hex)

Description

FF00

General SDO protocol error detected.

FF01

Toggle bit not alternated.

FF02

SDO protocol timed out.

FF03

Client/server command specifier is not valid or unknown.

FF04

Invalid block size (block mode only).

FF05

Invalid sequence number (block mode only).

FF06

CRC error (block mode only).

FF07

Out of memory.

FF08

Unsupported access to an object.

FF09

Attempt to read a write-only object.

FF0A

Attempt to write a read-only object.

FF0B

Object does not exist.

FF0C

Object cannot be mapped to the PDO.

FF0D

The number and length of the objects to be mapped exceed the maximum PDO length.

FF0E

Parameter is incompatible (general).

FF0F

Internal incompatibility (general).

FF10

Access not possible due to a hardware error.

FF11

Data type does not match, length of service parameter does not match.

FF12

Data type does not match, excessive length of service parameter.

FF13

Data type does not match, insufficient length of service parameter.

FF14

Subindex does not exist.

FF15

Invalid value for parameter (download only).

FF16

Excessive value of parameter written (download only).

FF17

Insufficient value of parameter written (download only).

FF18

Maximum value is less than minimum value.

FF19

Resource not available: SDO connection

FF1A

General error

FF1B

Data cannot be transferred or stored to the application.

FF1C

Data cannot be transferred or stored to the application because of local control.

FF1D

Data cannot be transferred or stored to the application because of the present device state.

FF1E

Object dictionary dynamic generation not possible or no object dictionary is present (for example object dictionary is generated from file and generation not possible due to a file error).

FF1F

No data available.