Overview of NC errors TwinCAT 22 Version: 1.1 Error(Hex) Error(Dec) Error type Description 4294 17044 Monitoring "Command is rejected because the segment target velocity is not realized"The command is rejected, because the new target segment velocity Vrequ is not realizable and an internal optimizing is impossible. 4295 17045 Monitoring "Successive commands have the same final position"Successive commands have the same final position. So the moving distance is zero.
4296 17046 Monitoring "Logical positioning direction is inconsistent with the direction of the buffer command"In the extended buffer mode, where the actual end position is replaced by the new buffer start position, the logical positioning direction is inconsistent with the direction of the buffer command (=> contradiction).A buffered command (BufferMode, BlendingLow, BlendingPrevious, BlendingNext, BlendingHigh) is rejected with error 0x4296 if the command is using the Beckhoff specific optional BlendingPosition but the blending position is located beyond the target position of the previous motion command.
4297 17047 Monitoring "Command is rejected because the remaining positioning length is to small"The command is rejected because the remaining path length is too small. E.g. when the buffer mode is used and the remaining positioning length in the actual segment is too small for getting the axis in a force free state or to reach the new target velocity at the change of segment. 429C 17052 Monitoring "Reference cam is not found" During the referencing process for an axis it is moved in the direction of the referencing cam. This reference cam, however, was not found as expected (=> leads to the abortion of the referencing procedure).
429D 17053 Monitoring "Reference cam became not free" During the referencing process for an axis it is moved in the direction of the referencing cam, and is only stopped again when the cam signal is reached. After the axis has also come to a physical standstill, the axis is subsequently started regularly from the cam again. In this case, the reference cam did not become free again as expected when driving down (=> leads to the abortion of the referencing procedure).
429E 17054 Monitoring "IO sync pulse was not found (only when using hardware latch)" If the hardware latch is activated, a sync pulse (zero pulse) is expected to be found and a sync event triggered following the expiry of a certain time or a certain distance. If this is not the case, the reaction is an error and the abortion of the referencing procedure. 42A0 17056 Internal "Group/axis consequential error" Consequential error resulting from another causative error related to another axis within the group. Group/axis consequential errors can occur in relation to master/slave couplings or with multiple axis interpolating DXD groups.
If, for instance, it is detected that the following error limit of a master axis has been exceeded, then this consequential error is assigned to all the other master axes and slave axes in this group.