Error Codes and Values
(Original Document)
About us
Introduction
The tables presented in this section list the error codes and values generated by the blocks in the MotionFunctionBlock library.
Motion Function Blocks
The following table contains the error codes and values generated in the ErrorId output parameter of MFB blocks.
Error_Id (decimal format)
Meaning
0
Correct execution.
1
Premium and Atrium PLC messaging or M340 PLC messaging system deferred error, to see details use MC_ReadAxisError block with the MSGERRORID information.
2
-
3
The block was interrupted due to a power cut.
4
Cancelled block (Enable switched to 0 during execution).
5
-
6
Faulty axis or axis missing.
7
Axisref changed value during execution of block or the same instance programmed with another Axis_Ref.
If the value belongs to the Can_Handler block, the Axis_Ref is not intended for the CAN_Handler variable.
8
The servodrive has rejected the command (to see details, use MC_ReadAxisError block).
9
This block cannot be executed in this axis mode (axis mode available using MC_ReadStatus).
10
Bad condition for jog direction: Both forward and backward inputs are active. If the axis was moving, it will be stopped.
11
The block was interrupted by a MC_Stop.
12
The block was interrupted by another block (for example: one MC_MOVE interrupting another).
13
The block has stopped because the servodrive has taken too long to perform the command (e.g.: MC_POWER).
14
The servodrive should be enabled but it is not now.
15
-
16
-
17
During an implicit exchange with the servodrive, the block has either:
  • lost the semaphore because a priority block took it,
  • or the block has not been invoked for n cycles, the system has therefore withdrawn the semaphore.
18
Unable to execute the MFB.
19
During an implicit exchange with the servodrive, the semaphore could not be obtained in the time allowed (too many blocks waiting for the servodrive, or servodrive too slow to react).
20
Internal error.
21
Parameter transfer error (corrupted data); TE_UpLoadDriveParam and TE_DownLoadDriveParam blocks.
22
During an implicit messaging exchange with the servodrive, the block has either:
  • lost the semaphore because a priority block took it,
  • or the block has not been invoked for n cycles, the system has therefore withdrawn the semaphore.
23
Internal error.
24
During a messaging exchange with the servodrive, the PLC’s messaging system was saturated for more than five PLC cycles.
25
Internal error.
26
The AMT has configured a servodrive that the MFB cannot program.
27
PLC messaging system immediate error, see details using MC_ReadAxisError block with the MSGERRORID information.
28
Axis programmed in two CAN_HANDLERs.
29
InitAxis: No network at the programmed network address.
30
-
31
Internal error.
32
Temporary error sent back by MC_Readstatus during a warm restart.
33
SET variable is too small for the data to write.
34
SET variable is incompatible with this servodrive.
35
LIST variable is incompatible with this servodrive.
36
LIST variable corrupted (checksum error).
37
SET variable corrupted (checksum error).
38
Restarting of Can_handler
39
The TSX CPP 110 card does not see the device at the configured address.
40
The family in the configuration does not match the one in the current servodrive.
41
The reference in the configuration does not match the one in the current servodrive.
42
Servodrive unknown.
43
The parameters List version does not match the Set version set of parameters.
44
The servodrive is still faulty after a reset.
45
The device does not work correctly when the MFB command is performed (only for Lexium 17).