NC Error Codes Diagnostics 77 Version: 1.0 Error(Hex) Error(Dec) Error Type Description 4287 17031 Monitoring "A activation cannot be executed due to a pending activation" A activation e.g. "CamIn", "CamScaling" or "WriteMotionFunction" cannot be executed due to a pending activation (e.g. "CamIn", "CamScaling", "WriteMotionFunction"). Only activation can be enabled. 4288 17032 Monitoring "Illegal combination of different cycle times within an axis group" A logical axis group includes elements (axes) with different cycle times for a common setpoint generator and I/O-execution, resp.
This situation can occur with Master/Slave-coupling or configuring 3D- and FIFO-groups (including path, auxiliary, and slave axes). 4289 17033 Monitoring "Illegal motion reversal" Due to the actual dynamical state a motion reversal will happen. To avoid this motion reversal the axis command is not performed and the previous system state restored. 428A 17034 Monitoring "Illegal moment for an axis command because there is an old axis command with activation position still active" The moment for the command is illegal because there is still an old command with activation position active (e.g. "go to new velocity at threshold position" or "reach new velocity at threshold position").
428B 17035 Monitoring "Error in the stop-calculation routine" (INTERNAL ERROR) Due to an internal error in the stop-calculation routine the current commando cannot be performed. The previous system state is restored. 428C 17036 Monitoring "A command with activation position cannot fully be performed because the remaining path is too short"A command with activation position (threshold) like "reach a new velocity at a position" can be just partially executed because the path from the actual position to the activation position is too short. 428D 17037 Monitoring "Illegal decouple type when decoupling a slave axis" The decouple and restart command contains an invalid decouple type.
428E 17038 Monitoring "Illegal target velocity when decoupling a slave axis" The decouple and restart command contains an illegal target velocity [1 428F 17039 Monitoring "The command new dynamic parameter cannot be performed since this would require a new target velocity"Das Kommando zum Aktivieren neuer Dynamikparameter wie Beschleunigung, Verzögerung und Ruck kann nicht durchgeführt werden, da dies eine neue beauftragte Fahrgeschwindigkeit erfordern würde. This situation can occur, for example, if the axis is near the target position in an accelerated state and the dynamics parameter are chosen softer.
4290 17040 Monitoring "A command with activation position cannot be performed because the axis is already in the brake phase" A command with activation position (threshold) e.g. "reach new velocity at position" cannot be performed because the axis is already in the brake phase and the remaining path from the actual position to the activation position is too short. 4291 17041 Monitoring "Decouple routine of slave axis doesn't return a valid solution" Internal jerk scaling of decouple routine cannot evaluate a valid solution (decoupling slave axis and transform to master axis).
The command is rejected because velocity can become too high, a reversal of movement can occur, or the target position can be passed.