beckhoff TwinCAT 2 Motion — 2.11 Bode Return Codes

Overview of NC Errors NC Errorcodes 78 Version: 1.1 Code Hex Code Dec Symbol Description Example 1: This error can occur if the cycle time of the calling task is larger than the assumed drive cycle time (in this case, however, the error occurs right at the start of the recording). Example 2: This error can occur if the calling task has real-time errors (e.g. the "Exceed Counter" of the task increments or the task has a lower priority, as is often the case, for example, with the PLC). In this case the error can also occur at any time during the recording. Example 3: This error can occur more frequently if the real-time load on the computer is quite high (>50 %).

Refer also to the corresponding AX5000 drive error code F440. 0x810F 33039 POSITION MONITORING (=> 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 start 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 velocity 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, velocity 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 user interface crash or a major malfunction of the Windows context.