Overview of NC errors TwinCAT 19 Version: 1.1 Error(Hex) Error(Dec) Error type Description 426D 17005 Function "Activation position under/overrun" The requested activation position is located in the past of the master (e.g. when exchanging a cam table). 426E 17006 Function "Activation impossible: Master is standing" The required activation of the correction is impossible since the master axis is not moving. A synchronization is not possible, because the master axis standing and the slave axis is still not synchronous.
426F 17007 Function "Activation mode not possible" The requested activation mode is not possible when the slave axis is moving (otherwise the slave velocity would jump to zero). 4270 17008 Parameter "Start parameter for the compensation is invalid" One of the dynamic parameters for the compensation is invalid (necessary condition): Acceleration (>0) Deceleration (>0) Process velocity (>0) 4271 17009 Parameter "Start parameter for the compensation is invalid" Velocity camber is negative. 4272 17010 Parameter "Start parameter for the compensation is invalid" The section on which the compensation is to occur is not positive.
4273 17011 Monitoring "Target position under/overrun" (INTERNAL ERROR) The position (calculated from the modulo-target-position) where the axis should stand at end of oriented stop has been run over. 4274 17012 Monitoring "Target position will be under/overrun" (INTERNAL ERROR) The position (calculated from the modulo-target- position) where the axis should stand at end of oriented stop is too near and will be run over. 4276 17014 Monitoring "GROUPERR GUIDERSTARTDATA" _ 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 "GROUPERR GUIDEROVERRUN" _ 427A 17018 Monitoring "GROUPERR GUIDERLOOKAHEAD" _ 427B 17019 Monitoring "GROUPERR GUIDERLOOKAHEADEND" _ 427C 17020 Monitoring "GROUPERR GUIDERLOOKAHEADREQU" _ 427D 17021 Monitoring "GROUPERR GUIDERMODE" _ 427E 17022 Monitoring "A requested motion command could not be realized (BISECTION)" A requested motion command could not be realized using the requested parameters. The command has been executed best possible and this message is therefore to be understood just as a warning. Examples:
A axis motion command is requested while the axis is in a unfavorable dynamic situation (acceleration phase), in which the covered distance is too short or the velocity is clearly 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. 427F 17023 Monitoring "The new target position either has been overrun or will be overrun" The new target position either has been overrun or will be overrun, since until there it is impossible to stop. A internal stop command is commended.