Bode Return Codes
The following bode plot specific error codes are used in the bode plot server:
Code (Hex) | Code (Dec) | Symbol | Description |
|---|---|---|---|
0x8100 | 33024 | INTERNAL | Internal error |
0x8101 | 33025 | NOTINITIALIZED | Not initialized (e.g. no nc axis) |
0x8102 | 33026 | INVALIDPARAM | Invalid parameter |
0x8103 | 33027 | INVALIDOFFSET | Invalid index offset |
0x8104 | 33028 | INVALIDSIZE | Invalid parameter size |
0x8105 | 33029 | INVALIDSTARTPARAM | Invalid start parameter (set point generator) |
0x8106 | 33030 | NOTSUPPORTED | Not supported |
0x8107 | 33031 | AXISNOTENABLED | Nc axis not enabled |
0x8108 | 33032 | AXISINERRORSTATE | Nc axis in error state |
0x8109 | 33033 | DRIVEINERRORSTATE | IO drive in error state |
0x810A | 33034 | AXISANDDRIVEINERROR-STATE | Nc axis AND IO drive in error state |
0x810B | 33035 | INVALIDDRIVEOPMODE | Invalid drive operation mode active or requested |
0x810C | 33036 | INVALIDCONTEXT | Invalid context for this command (mandatory task or windows context needed) |
0x810D | 33037 | NOAXISINTERFACE | Missing TCom axis interface (axis null pointer). There is no connection to the NC axis. Either no axis (or axis ID) has been parameterized, or the parameterized axis does not exist. |
0x810E | 33038 | INPUTCYCLECOUNTER | Invalid input cycle counter from IO drive (e.g. frozen). The cyclic drive data are backed up by an ‘InputCycleCounter’ during the bode plot recording. This allows firstly the detection of an unexpected communication loss (keyword: LifeCounter) and secondly a check for temporal data consistency to be performed. 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 %). Note: 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: |
0x8110 | 33040 | DRIVELIMITATIONDETECTED | 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 device, 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: |
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. Typical error message in the logger: |
0x8112 | 33042 | NCERR_BODEPLOT_WCSTATE | WC state error (IO data working counter) IO working counter error (WC state), for example due to real-time errors, EtherCAT CRC errors or telegram failures, EtherCAT device not communicating (OP state), etc. |
0x8113- | 33043- | RESERVED | Reserved range |