NC Error Codes Diagnostics 78 Version: 1.0 Error(Hex) Error(Dec) Error Type Description 4292 17042 Monitoring "Command not be executed because the command buffer is full filled" The command is rejected because the command buffer is full filled. 4293 17043 Internal "Command is rejected due to an internal error in the Look Ahead" (INTERNAL ERROR) The command is rejected due to an internal error in the "look ahead". 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.
429A 17050 Function Restart has Failed There is already a motion command within the PTP command buffer and a further new motion command that should have modified the current motion command by restart has failed. 429B 17051 Monitoring „collect error for invalid start parameters“ This error refers to a wrong parameterization of the user (collect error). E. g. dynamic parameters like Velo, Acc or Dec could be equal or less than zero. Or following errors: - BaseFrequence 200 - BaseAmplitude = 1/(2*CycleTime) 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