Danfoss VLT Servo Drive MSD510 Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| 0x1000 / 0x100 Generic application error | Cause: Generic application error. Remedy:
|
| 0x2310 / 0x101 Overcurrent on output | Cause: Overcurrent on output. Remedy:
|
| 0x2311 / 0x15F High current overload | Cause: High current overload error. Remedy:
|
| 0x2312 / 0x160 I²T current overload | Cause: I²T current overload error. The motor or drive thermal limit has been reached. Remedy:
|
| 0x2313 / 0x161 High power overload | Cause: High power overload error. Remedy:
|
| 0x2314 / 0x162 PT power overload | Cause: PT power overload error. Remedy:
|
| 0x2320 / 0x163 Short circuit | Cause: DC overcurrent short circuit error. Remedy:
|
| 0x2330 / 0x151 Earth leakage | Cause: Current leaking to earth. Remedy:
|
| 0x2391 / 0x125 AUX overcurrent | Cause: Current on the AUX line has reached the overcurrent limit. Remedy:
|
| 0x2393 / 0x127 AUX user limit current | Cause: Current on the AUX line has reached the user-defined limit for fault. Remedy:
|
| 0x2394 / 0x128 AUX user limit current warning | Cause: Current on the AUX line has reached the user-defined limit for warning. Remedy:
|
| 0x2395 / 0x129 AUX fuse failure | Cause: Fuse failure. Current or voltage is above the limit on the AUX line. Remedy:
|
| 0x2396 / 0x15C DC Overcurrent trip | Cause: DC overcurrent trip. Remedy:
|
| 0x2397 / 0x12B Output power trip | Cause: The peak output power of the device is exceeded. Remedy:
|
| 0x239B / 0x102 I²T overload motor | Cause: I²T overload motor error. Remedy:
|
| 0x3130 / 0x12F Mains phase loss | Cause: Mains phase loss detected. This occurs when a phase on mains is missing, or when the mains is imbalanced. Remedy:
|
| 0x3210 / 0x103 DC link overvoltage | Cause: DC-link voltage exceeds limit. Remedy:
|
| 0x3210 / 0x103 (SW) Overcurrent trip SW | Cause: DC-link voltage exceeds limit (Software trip). Remedy:
|
| 0x3220 / 0x104 DC link undervoltage | Cause: DC-link voltage below limit in “Operation enabled” state. Remedy:
|
| 0x3230 / 0x152 UDC charging error | Cause: The maximum time limit to charge the DC-link has been exceeded. Remedy:
|
| 0x3280 / 0x153 DC Link Voltage unbalanced | Cause: DC-link voltage unbalanced. Remedy:
|
| 0x3291 / 0x132 UAUX high voltage | Cause: UAUX above warning limit. Remedy:
|
| 0x3292 / 0x133 UAUX overvoltage | Cause: UAUX above overvoltage limit. Remedy:
|
| 0x3293 / 0x134 UAUX low voltage | Cause: UAUX below warning limit. Remedy:
|
| 0x3294 / 0x135 UAUX undervoltage | Cause: UAUX below undervoltage limit. Remedy:
|
| 0x3295 / 0x136 UDC high voltage | Cause: The DC-link voltage is higher than the high-voltage warning limit. Remedy:
|
| 0x3296 / 0x137 UDC low voltage | Cause: The DC-link voltage is lower than the low-voltage warning limit. Remedy:
|
| 0x3297 / 0x154 UAUX charging error | Cause: Load error when UAUX is charging. The maximum time limit to charge the AUX line has been exceeded. Remedy:
|
| 0x3298 / 0x165 UDC shutdown error | Cause: Error when UDC is in shutdown phase. Remedy:
|
| 0x3299 / 0x155 UAUX shutdown error | Cause: Error when UAUX is in shut down phase. Remedy:
|
| 0x329A / 0x156 UAUX undervoltage hardware | Cause: UAUX undervoltage detected by hardware circuit. Remedy:
|
| 0x329B / 0x168 Automated fault reset failure | Cause: Too many auto fault resets have been executed in the intended time interval. Remedy:
|
| 0x4210 / 0x157 Device overtemperature | Cause: Triggered when the maximum temperature of the main device component is exceeded. PSM: Thyristor rectifier module. DAM: Maximum temperature of both high side and low side IGBTs. Remedy:
|
| 0x4220 / 0x138 Too low temperature | Cause: The device is too cold to operate. Remedy:
|
| 0x4290 / 0x105 Overtemperature: Power module | Cause: Overtemperature on power module. Remedy:
|
| 0x4291 / 0x106 Overtemperature: Control card | Cause: Maximum temperature of control card exceeded. Remedy:
|
| 0x4292 / 0x107 Overtemperature: Power card | Cause: Maximum temperature of power card exceeded. Remedy:
|
| 0x4293 / 0x13C Inrush overtemperature: DC link | Cause: Inrush fault. Too many transitions into state “Operation enabled” in a short time period. Remedy:
|
| 0x4294 / 0x13D Inrush overtemperature AUX line | Cause: Inrush fault. Too many power-ups of the AUX voltage have occurred within a short time period. Remedy:
|
| 0x4310 / 0x108 Overtemperature: Motor | Cause: Overtemperature on motor. Remedy:
|
| 0x5112 / 0x109 UAUX undervoltage | Cause: Undervoltage on auxiliary voltage. Remedy:
|
| 0x5121 / 0x158 Charge switch failure voltage | Cause: Indicates a malfunction of the internal charge circuit. Remedy:
|
| 0x5530 / 0x10A EE Checksum Error (parameter missing) | Cause: Missing parameter in internal device configuration. Remedy:
|
| 0x6320 / 0x10B Parameter error | Cause: A parameter has an invalid value. Remedy:
|
| 0x6382 / 0x15D Configuration parameters version error | Cause: Configuration parameter set version mismatch: parameter set is not valid for this device. Remedy:
|
| 0x6383 / 0x164 Configuration parameters limits error | Cause: ≥1 parameter in the configuration parameter set is out of limits: the parameter set is not valid for this device. Remedy:
|
| 0x6384 / 0x166 Power EEprom configuration error | Cause: The power device Eeprom is corrupt or incompatible with this control board. Remedy:
|
| 0x7111 / 0x141 Brake chopper failure | Cause: The brake chopper is monitored during operation. A brake failure has been detected by the brake check function. Remedy:
|
| 0x7112 / 0x167 Brake chopper overcurrent | Cause: The brake chopper current exceeds the limit. Remedy:
|
| 0x7181 / 0x142 Brake resistor maximum power limit | Cause: The brake resistor maximum power limit is exceeded. Remedy:
|
| 0x7182 / 0x143 Brake resistor user power limit | Cause: The brake resistor power limit is exceeded. The power transmitted to the brake resistor is calculated as an average value over the last 300 s of run time. Calculation is based on DC-link voltage and brake resistor value set in parameter 2-16. Remedy:
|
| 0x7183 / 0x159 Brake mains voltage too high | Cause: The brake resistor mains voltage is too high. Remedy:
|
| 0x7320 / 0x10C Internal position sensor error | Cause: Absolute position sensor error. Remedy:
|
| 0x7380 / 0x10D External position sensor error | Cause: External encoder data could not be read. Remedy:
|
| 0x8611 / 0x10E Following error | Cause: A following error has occurred. Remedy:
|
| 0x8693 / 0x10F Homing error on entering homing mode | Cause: Could not enter homing mode (for example velocity not 0). Remedy:
|
| 0x8694 / 0x110 Homing error on start homing method | Cause: Could not start homing method (for example drive not in standstill). Remedy:
|
| 0x8695 (0x111) Homing error distance | Cause: Homing distance reached. Remedy:
|
| 0xFF01 (0x112) Mechanical brake failure | Cause: No brake or wire failure detected. Remedy:
|
| 0xFF02 (0x113) Short circuit in mechanical brake control | Cause: Short circuit in brake control. Remedy:
|
| 0xFF0A (0x114) External interface power failure | Cause: External interface power supply failure. Remedy:
|
| 0xFF10 (0x14F) Communication interrupted | Cause: The fieldbus communication has been interrupted while the device was enabled. Remedy:
|
| 0xFF21 (0x145) Fan feedback inconsistent | Cause: Internal fan fault. Internal fan not running/mounted. Remedy:
|
| 0xFF22 (0x15A) Fan lifetime critical | Cause: The theoretical lifetime of the fan has been exceeded. Remedy:
|
| 0xFF60 (0x115) Timing violation 1 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF61 (0x116) Timing violation 2 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF62 (0x117) Timing violation 3 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF63 (0x118) Timing violation 4 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF64 (0x119) Timing violation 5 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF65 (0x11A) Timing violation 6 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF66 (0x168) Timing violation 7 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF67 (0x16B) Timing violation 8 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF68 (0x16C) Timing violation 9 | Cause: Internal timing violation detected. Remedy:
|
| 0xFF70 (0x11B) Firmware: Package description mismatch | Cause: The firmware found does not match the package description. Remedy:
|
| 0xFF71 (0x11C) Firmware: Power cycle needed | Cause: The firmware update transfer is completed but a power cycle is required before the new firmware is active. Remedy:
|
| 0xFF72 (0x11D) Firmware: Update started | Cause: Firmware update is in progress. Warning changes to error when an attempt is made to enable the device in this state. Remedy:
|
| 0xFF73 (0x15B) Firmware: Update invalid | Cause: Invalid or corrupted firmware package update. Last valid firmware package has been loaded. Remedy:
|
| 0xFF80 (0x11E) STO active while drive enabled | Cause: STO activated while drive was enabled or tried to enable while STO active. Remedy:
|
| 0xFF81 (0x11F) STO mismatch | Cause: Dual diagnosis of STO voltage not plausible. Remedy:
|
| 0xFF85 (0x120) P_STO error | Cause: P_STO voltage on the power card exceeds the limits. Remedy:
|
| 0xFF90 (0x121) Guide value reversed | Cause: Position guide value went backwards while the servo drive was in CAM mode. Remedy:
|
| 0xFF91 (0x122) Guide value implausible | Cause: Increments between succeeding values too large. Remedy:
|
| 0xFF95 (0x14E) Sign of life error | Cause: Sign of life error detected. Remedy:
|