| ASCII - Command | ERRCODE * | |||
| Syntax Transmit | ERRCODE * | |||
| Syntax Receive | ERRCODE * <Data> | Available in | ||
| Type | Command | MMI | Yes | |
| ASCII Format | Integer32 | CANBus Object Number | No | |
| DIM | - | PROFIBUS PNU | No | |
| Range | 0 .. 0xFFFFFFFF | DPR | No | |
| Default | - | |||
| Opmode | All | Data Type Bus/DPR | - | |
| Drive State | - | Weighting | ||
| Start Firmware | 1.20 | |||
| Configuration | No | Last Change of this Object | 1.3 | |
| Function Group | Drive Status | EEPROM | - | |
| Short Description | Output Error Register | |||
Description
| The ERRCODE* command returns the internal status information in the form of a bit-variable. A bit is set for as long as the corresponding error/fault is detected. The bit is deleted by the hardware reset of the amplifier. Faults that are designated by the SW label can also be deleted by a software reset (function CLRFAULT – clear fault). Level gives an information about the error handling in the drive. Level 2: A fault causes an emergency stop. The stop of the motor is done in velocity control using the emergency stop ramp (DECSTOP). When the motor reaches the zero velocity level (VEL0) (limited by max. 5 sec), the power stage is disabled. The Ready-to-Operate relay is switched off. The drive has to be reset before it can be enabled again. The fault is displayed. Level 3: (starting with firmware 4.01) A fault causes an emergency stop. The stop of the motor is done without feedback device (sensorless). When the motor has stopped, the power stage is disabled. The Ready-to-Operate relay is switched off. The drive has to be reset before it can be enabled again. The fault is displayed. Level 4: A fault causes an directly disable of the power stage. The motor has no torque (coast). The Ready-to-Operate relay is switched off. The drive has to be reset before it can be enabled again. The fault is displayed. Faults, that have different levels (2/3 and 4), the behaivior is controlled by ACTFAULT and MBRAKE or STOPMODE ACTFAULT=1 or MBRAKE=1 LEVEL 2 or 3 (Default-Setting) ACTFAULT=0 and MBRAKE=0 LEVEL 4 |
||
| Bit/Displ./Reset/Level | Bit | Description |
| 00/F01/SW/2,4 | 0x00000001 | =1 Heatsink overtemperature is set, if the heatsink temperature TEMPH exceeds the max allowed threshold MAXTEMPH. |
| 01/F02/SW/2,4 | 0x00000002 | =1 DC-link overvoltage Is set, if the DC-link voltage exceeds the max threshold selected by VBUSBAL. |
| 02/F03/SW/2 | 0x00000004 | =1 Contouríng error of the external trajectory (OPMODE=6/SERCOS or =5 external trajectory) Is set, if the target speed which is given by the extrnal trajectory is higher than VLIM/VLIMN. Note: "F03" will only occur if you run the drive with an external trajectory, i.e. OPMODE = 5 or 6. It's called "Contouring Error" and means that the step caused by the trajectory causes a speed above VLIM or VLIMN. Running the other position modes (OPMODE = 4 or 8) a position following error will cause "n03". >> DRVSTAT |
| 03/F04/HW/3,4 | 0x00000008 | =1 Feedback error Is set, if a feedback error was detected. The drive decelerates by current controller. |
| 04/F05/SW/2,4 | 0x00000010 | =1 Undervoltage protection Is set, if the DC-link voltage is lower than VBUSMIN (only if the drive is enabled). |
| 05/F06/HW/2,4 | 0x00000020 | =1 Motor overtemperature is set, if the heatsink temperature TEMPM exceeds the max allowed threshold MAXTEMPM. |
| 06/F07/HW/2,4 | 0x00000040 | =1 if the internal electronic supply is faulty. |
| 07/F08/SW/3,4 | 0x00000080 | =1 Overspeed Is set, if the velocity of the motor exceeds the overspeed threshold (VOSPD). The drive decelerates by current controller. |
| 08/F09/HW/4 | 0x00000100 | =1 EEPROM Checksum error Is set, if the data read/written from the EEPROM is not valid. There are two possibilities, that can cause this error. First is a defect EEPROM and the second is a wrong checksum in the EEPROM. In the second case, a SAVE can solve the problem. |
| 09/F10/HW | 0x00000200 | Reserved |
| 10/F11/HW/2,4 | 0x00000400 | =1 Brake error Is set, if the brake switch detects a fault (e.g. Brake is selected, but no brake is connected). |
| 11/F12/HW | 0x00000800 | =1 Missing motor connection. This error occurs, if a motor connection (not feedback device) is missing. The error can be disabled by CPHASE = 0. |
| 12/F13/SW/2,4 | 0x00001000 | =1 Ambient overtemperature is set, if the ambient temperature TEMPE exceeds the max allowed threshold MAXTEMPE. |
| 13/F14/HW/2,4 | 0x00002000 | =1 Output stage fault This fault can be caused by: Earth short circuit of the motor Short circuit of the motor phases Short circuit of the regen. |
| 14/F15/SW/2,4 | 0x00004000 | =1 I˛tmax override Is set, if I˛t exceeds 105% of ICONT (FOLDMODE=2). |
| 15/F16/SW/2,4 | 0x00008000 | =1 Mains BTB |
| 16/F17/HW/2,4 | 0x00010000 | =1 A/D converter error |
| 17/F18/HW/2,4 | 0x00020000 | =1 Regen error destroyed regen transistor regen resistor extern selected, but the internal one is used. |
| 18/F19/SW/2,4 | 0x00040000 | =1 line phase missing (PMODE=2) |
| 19/F20/HW/2,4 | 0x00080000 | =1 Slot error Error depends on the type of Slot board: 1. I/O expansion board The error is caused by a missing 24V supply at the I/O board. 2. DPR Slot board (Beckhoff, L&B, Sigmatek) The error is generated, if the DPR interrupt fails to appear. The watch-dog time can be selected by EXTWD. 3. PROFIBUS Error in the initialization time. |
| 20/F21/HW/2,4 | 0x00100000 | =1 PROFIBUS handling error If the OPMODE is changed by another communication channel than PROFIBUS, when the drive is under control of the PROFIBUS, this error is generated. Exception: Working mode -126 for PROFIBUS. This is the safe opmode when the drive is switched on. |
| 21/F22/HW/2,4 | 0x00200000 | =1 Earth short circuit The earth short circuit supervisor of the 40/70 A units. |
| 22/F23/HW/2,4 | 0x00400000 | =1 CANopen Bus-Off Fault in CAN communication. The communication fault BUSOFF is generated by layer 2 (CAN controller). This fault can have several resons. Some examples are: Drive tries to establish communication, but there is no other node. CAN nodes have different baud rates, Bus cable defekt, reflections because of missing or wrong bus terminations, etc. A BUSOFF is displayed by the drive, if another CAN node is connected and minimum one errorfree object is generated. If the BUSOFF is generated and the drive is moving the motor, the motor is stopped using the emergency ramp and then the drive is disabled. |
| 23/F24/SW/2,4 | 0x00800000 | Warning generates a error message (defined by WMASK) |
| 24/F25/HW/3,4 | 0x01000000 | Commutation Error (Run-away of the motor) The drive decelerates by current controller. See also VCOMM |
| 25/F26/SW/2,4 | 0x02000000 | Hardware limit switch error at homing move (defined by REFLS) |
| 26/F27/HW/4 | 0x04000000 | =1 "-AS-Option" error If the ENABLE signal of the drive is high and the -AS-option is activated, this error is generated (starting Version 3.44). |
| 27/F28/SW/2 | 0x08000000 | =1 error "external tarjectory" is generated, if an external position profile generator creates a step, that exceeds the maximum value. =1 EtherCAT: The error message "Synchronisation" is generated if the synchronisation during the phase startup process is not sucsessfull or if the controller EtherCAT status „Operational“ is running out of synchronisation. |
| 28/F29/SW/2 | 0x10000000 | =1 Slot card error (example SERCOS) is generated if the drive is running out of communication or if a software enable is set via slot card without hardware enable set. =1 DPR-Card (for example EtherCAT) is gerenated, if the communicationphase on an enabled drive is switched to lower levels or a not supported mapping for cyclic data is select or the drive gets a SW disable via slotcard without set HW enable |
| 29/F30/SW | 0x20000000 | Emergency stop time out |
| 30/F31/SW | 0x40000000 | =1 MACRO MACRO program error |
| 31/F32/HW/4 | 0x80000000 | =1 System error Is set, if an error occurred in the system check of the initialization phase or a watch-dog error in the working phase. Following reasons are possible: 1. Wrong program data in the FLASH (e.g. interrupted program download) 2. Macro error (the macros could not be compiled) 3. Software watch-dog activated 4. Error with the EEPROM (read or write). 5. FPGA error (FPGA could not be loaded correctly) 6. Macro RAM (the compilation of the MACROs detect too less RAM) When the drive is switched on, a detailed message is send vis RS232. In case of F32 error try a SAVE command. When this procedure is finnished reset the drive. |