beckhoff TwinCAT 2 Motion — 2.3 Group Errors

Overview of NC Errors NC Errorcodes 25 Version: 1.1 Error(Hex) Error(Dec) Error type Description The position designated for the end of the oriented stop (calculated from the modulo target position) is too close and will be overrun. 4275 17013 Parameter Group parameter is invalid A group parameter is invalid. This can be, for example, a parameterized velocity, acceleration, deceleration, jerk or NC cycle time whose value has been parameterized to be less than or equal to zero. 4276 17014 Monitoring Group error at the start of the setpoint generation When starting the setpoint generation for e.g. the flying saw, different parameters or states can lead to this error.

For example, dynamic parameters such as acceleration, deceleration and jerk may be invalid (less than or equal to zero) or the NC cycle time or the override value at startup may be outside the range from 0% to 100%. 4277 17015 Monitoring Dynamic parameters not permitted (internal error) The dynamic parameters resulting from internal calculation like acceleration, deceleration and jerk are not permitted. 4279 17017 Monitoring New target position is invalid or cannot be reached A newly commanded target position is invalid, since it has either already been passed over or is passed over during a stop with the momentarily acting dynamics.

427A 17018 Monitoring New travel velocity or final velocity is invalid For a newly commanded command, either the required travel velocity or the required final velocity (target velocity in the target position) is invalid. The travel velocity must always be greater than zero and the final velocity must always be greater than or equal to zero (default case is zero). 427B 17019 Monitoring New final velocity or new target position is invalid For a newly commanded command, either the requested final velocity (target velocity in the target position) or the requested target position is invalid. The final velocity must always be greater than or equal to zero (default case is zero).

427C 17020 Monitoring New travel velocity is invalid A newly commanded travel velocity is invalid because it is either less than or equal to zero or other reasons do not allow this velocity. 427D 17021 Monitoring Internal start mode is invalid For a newly commanded command the start mode is invalid or is not allowed in this travel situation. A user cannot directly influence the start mode. 427E 17022 Monitoring A requested movement command could not be realized (BISECTION) A requested movement command could not be realized using the requested parameters. The movement command has been executed best possible and this message is therefore to be understood just as a warning. Examples:

An axis start is requested in motion in an unfavorable dynamic situation (acceleration phase) in which the travel distance is too short or the velocity is significantly too high. Another possibility is a slave axis, which is decoupled in motion in a unfavorable dynamic situation and is afterwards given a motion as in the previous case.