Overview of NC errors 2.12 Further Error Codes Table 1: TwinCAT 52 Version: 1.1 0x810F 33039 POSITIONMONITORING (=> NC Runtime Error) Position monitoring: Axis position is outside of the maximum allowed moving range. The axis has left the parameterized position range window, whereupon the recording was aborted and the NC axis was placed in the error state 0x810F (with standard NC error handling). The position range window acts symmetrically around the initial position of the axis (see also parameter description Position Monitoring Window). Typical error message in the logger: "BodePlot:
'Position Monitoring' error 0x%x because the actual position %f is above the maximum limit %f of the allowed position range (StartPos=%f, Window=%f)" 0x8110 33040 DRIVELIMITATIONDETECTE D Driver limitations detected (current or velocity limitations) which causes a nonlinear behavior and invalid results of the bode plot. A bode plot recording requires an approximately linear transmission link. If the speed or current is limited in the drive unit, however, this non-linear behavior is detected and the bode plot recording is aborted. Reasons for these limitations can be:
choosing too large an amplitude for the position, speed or torque interface, or an unsuitable choice of amplitude scaling mode (see also parameter description Amplitude Scaling Mode, Base Amplitude, Signal Amplitude). Typical error message in the logger: "BodePlot: Sequence aborted with error 0x%x because the current limit of the drive has been exceeded (%d times) which causes a nonlinear behavior and invalid results of the bode plot" 0x8111 33041 LIFECOUNTERMONITORING (=> NC Runtime Error) Life counter monitoring (heartbeat): Lost of communication to GUI detected after watchdog timeout is elapsed.
The graphical user interface from which the bode plot recording was started is no longer communicating with the bode plot driver in the expected rhythm (keyword: ‘Life Counter’). Therefore the recording is terminated immediately and the NC axes are placed in the error state 0x8111 (with standard NC error handling). Possible reasons for this can be an operating interface crash or a major malfunction of the Windows context. Typical error message in the logger: "BodePlot: Sequence aborted with GUI Life Counter error 0x%x because the WatchDog timeout of %f s elapsed ('%s')" Error(Hex) Error(Dec) ErrorType Description 0x8120 33056 Environment Invalid configuration for Object (e.g.
in System Manager) 0x8121 33057 Environment Invalid environment for Object (e.g. TcCom- Object's Hierarchy or missing/faulty Objects) 0x8122 33058 Environment Incompatible Driver or Object