Danfoss VLT Servo Drive MSD510

Fault Code and MeaningCause and Remedy
0x1000 / 0x100

Generic application error

Cause:


Generic application error.



Remedy:



  • Check application settings and logs.

  • Restart the system.


0x2310 / 0x101

Overcurrent on output

Cause:


Overcurrent on output.



Remedy:



  • Check motor cables for short circuits.

  • Check motor insulation.

  • Check if the motor load is too high.


0x2311 / 0x15F

High current overload

Cause:


High current overload error.



Remedy:



  • Reduce load on the motor.

  • Check drive sizing relative to the load.


0x2312 / 0x160

I²T current overload

Cause:


I²T current overload error. The motor or drive thermal limit has been reached.



Remedy:



  • Allow the system to cool down.

  • Check ventilation and ambient temperature.

  • Reduce continuous load.


0x2313 / 0x161

High power overload

Cause:


High power overload error.



Remedy:



  • Check system power requirements.

  • Verify power supply stability.


0x2314 / 0x162

PT power overload

Cause:


PT power overload error.



Remedy:



  • Check power supply module load.


0x2320 / 0x163

Short circuit

Cause:


DC overcurrent short circuit error.



Remedy:



  • Check cabling for short circuits.

  • Inspect motor windings.

  • Check internal drive components.


0x2330 / 0x151

Earth leakage

Cause:


Current leaking to earth.



Remedy:



  • Check motor and cable insulation.

  • Check for ground faults in the installation.


0x2391 / 0x125

AUX overcurrent

Cause:


Current on the AUX line has reached the overcurrent limit.



Remedy:



  • Check 24V/AUX supply wiring.

  • Check for short circuits on AUX lines.


0x2393 / 0x127

AUX user limit current

Cause:


Current on the AUX line has reached the user-defined limit for fault.



Remedy:



  • Check load on AUX supply.

  • Adjust user-defined limits if appropriate.


0x2394 / 0x128

AUX user limit current warning

Cause:


Current on the AUX line has reached the user-defined limit for warning.



Remedy:



  • Reduce load on AUX supply to prevent tripping.


0x2395 / 0x129

AUX fuse failure

Cause:


Fuse failure. Current or voltage is above the limit on the AUX line.



Remedy:



  • Check and replace the AUX fuse.

  • Investigate cause of high current/voltage before replacing.


0x2396 / 0x15C

DC Overcurrent trip

Cause:


DC overcurrent trip.



Remedy:



  • Check DC link connections.

  • Check for short circuits in the DC bus.


0x2397 / 0x12B

Output power trip

Cause:


The peak output power of the device is exceeded.



Remedy:



  • Reduce dynamic load peaks.

  • Check acceleration ramps.


0x239B / 0x102

I²T overload motor

Cause:


I²T overload motor error.



Remedy:



  • Motor is overheating or calculated thermal load is too high.

  • Check motor cooling.


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:



  • Check mains supply fuses.

  • Check mains voltage balance.

  • Check input wiring.


0x3210 / 0x103

DC link overvoltage

Cause:


DC-link voltage exceeds limit.



Remedy:



  • Check for regenerative energy from the motor (braking).

  • Check if braking resistor is connected/functioning.

  • Check mains voltage level.


0x3210 / 0x103 (SW)

Overcurrent trip SW

Cause:


DC-link voltage exceeds limit (Software trip).



Remedy:



  • See remedies for DC link overvoltage.


0x3220 / 0x104

DC link undervoltage

Cause:


DC-link voltage below limit in “Operation enabled” state.



Remedy:



  • Check mains supply voltage.

  • Check input fuses.

  • Verify pre-charging circuit.


0x3230 / 0x152

UDC charging error

Cause:


The maximum time limit to charge the DC-link has been exceeded.



Remedy:



  • Check for short circuit in DC link.

  • Check DC link capacitance.


0x3280 / 0x153

DC Link Voltage unbalanced

Cause:


DC-link voltage unbalanced.



Remedy:



  • Check supply phases.

  • Check DC bus connections between modules.


0x3291 / 0x132

UAUX high voltage

Cause:


UAUX above warning limit.



Remedy:



  • Check auxiliary power supply voltage.


0x3292 / 0x133

UAUX overvoltage

Cause:


UAUX above overvoltage limit.



Remedy:



  • Check auxiliary power supply immediately.


0x3293 / 0x134

UAUX low voltage

Cause:


UAUX below warning limit.



Remedy:



  • Check auxiliary power supply load and connections.


0x3294 / 0x135

UAUX undervoltage

Cause:


UAUX below undervoltage limit.



Remedy:



  • Check auxiliary power supply source.


0x3295 / 0x136

UDC high voltage

Cause:


The DC-link voltage is higher than the high-voltage warning limit.



Remedy:



  • Monitor DC bus voltage.

  • Check braking settings.


0x3296 / 0x137

UDC low voltage

Cause:


The DC-link voltage is lower than the low-voltage warning limit.



Remedy:



  • Monitor mains supply stability.


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:



  • Disconnect load on AUX line and retry.

  • Check for shorts on AUX line.


0x3298 / 0x165

UDC shutdown error

Cause:


Error when UDC is in shutdown phase.



Remedy:



  • Cycle power to the drive.

  • Contact Danfoss service if persists.


0x3299 / 0x155

UAUX shutdown error

Cause: Error when UAUX is in shut down phase.

Severity: Error | LCP Name: UAUX shtdwn err




Remedy:

  • Check UAUX supply status.


0x329A / 0x156

UAUX undervoltage hardware

Cause: UAUX undervoltage detected by hardware circuit.

Severity: Error | Valid for: PSM 510, DAM 510, ACM 510




Remedy:

  • Check auxiliary voltage supply.

  • Check hardware connections.


0x329B / 0x168

Automated fault reset failure

Cause: Too many auto fault resets have been executed in the intended time interval.

Severity: Trip lock | LCP Name: afr failure




Remedy:

  • Investigate the underlying recurring fault causing the resets.

  • Cycle power to reset the trip lock.


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.

Severity: Warning, Error | LCP Name: overtemp device




Remedy:

  • Check cooling system and fans.

  • Check for overload conditions.

  • Check ambient temperature.


0x4220 / 0x138

Too low temperature

Cause: The device is too cold to operate.

Severity: Error | LCP Name: low temp device




Remedy:

  • Ensure ambient temperature is within specified operating range.


0x4290 / 0x105

Overtemperature: Power module

Cause: Overtemperature on power module.

Severity: Error | Valid for: SDM 511/SDM 512




Remedy:

  • Check power module cooling.


0x4291 / 0x106

Overtemperature: Control card

Cause: Maximum temperature of control card exceeded.

Severity: Error | LCP Name: overtemp CC




Remedy:

  • Check control cabinet ventilation.


0x4292 / 0x107

Overtemperature: Power card

Cause: Maximum temperature of power card exceeded.

Severity: Warning, error | LCP Name: overtemp PC




Remedy:

  • Check device cooling.


0x4293 / 0x13C

Inrush overtemperature: DC link

Cause: Inrush fault. Too many transitions into state “Operation enabled” in a short time period.

Severity: Error | LCP Name: inrush UDC




Remedy:

  • Limit the frequency of enabling operation.

  • Check DC link connections.


0x4294 / 0x13D

Inrush overtemperature AUX line

Cause: Inrush fault. Too many power-ups of the AUX voltage have occurred within a short time period.

Severity: Error | Valid for: DAM 510




Remedy:

  • Reduce frequency of AUX voltage power cycles.


0x4310 / 0x108

Overtemperature: Motor

Cause: Overtemperature on motor.

Severity: Error | LCP Name: overtemp motor




Remedy:

  • Check motor cooling.

  • Check motor load (overload).

  • Check thermal sensor connection.


0x5112 / 0x109

UAUX undervoltage

Cause: Undervoltage on auxiliary voltage.

Severity: Error, trip lock | Valid for: SDM 511/SDM 512




Remedy:

  • Check auxiliary power supply.


0x5121 / 0x158

Charge switch failure voltage

Cause: Indicates a malfunction of the internal charge circuit.

Severity: Trip lock | LCP Name: Chg switch fail




Remedy:

  • Contact service/support (Internal hardware fault).


0x5530 / 0x10A

EE Checksum Error (parameter missing)

Cause: Missing parameter in internal device configuration.

Severity: Trip lock | LCP Name: config err




Remedy:

  • Re-download configuration or firmware.

  • Contact service if error persists.


0x6320 / 0x10B

Parameter error

Cause: A parameter has an invalid value.

Severity: Trip lock | LCP Name: param err




Remedy:

  • Check parameter settings.

  • Reset parameters to factory default if necessary.


0x6382 / 0x15D

Configuration parameters version error

Cause: Configuration parameter set version mismatch: parameter set is not valid for this device.

Severity: Trip lock | LCP Name: conf par ver




Remedy:

  • Ensure correct parameter set is loaded for the device version.


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.

Severity: Trip lock | LCP Name: conf par lim




Remedy:

  • Check parameter values against allowed limits.


0x6384 / 0x166

Power EEprom configuration error

Cause: The power device Eeprom is corrupt or incompatible with this control board.

Severity: Trip lock | LCP Name: conf par EEPROM




Remedy:

  • Contact service/support (Hardware incompatibility or corruption).


0x7111 / 0x141

Brake chopper failure

Cause: The brake chopper is monitored during operation. A brake failure has been detected by the brake check function.

Severity: Warning, error | Valid for: PSM 510




Remedy:

  • Check brake chopper circuit.

  • Check brake resistor connection.


0x7112 / 0x167

Brake chopper overcurrent

Cause: The brake chopper current exceeds the limit.

Severity: Trip lock | LCP Name: brake ch overcurr




Remedy:

  • Check for short circuit in brake resistor or cable.

  • Check brake resistor resistance value.


0x7181 / 0x142

Brake resistor maximum power limit

Cause: The brake resistor maximum power limit is exceeded.

Severity: Warning, error | LCP Name: brake pwr lim




Remedy:

  • Check application regeneration requirements.

  • Verify brake resistor sizing.


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.

Severity: Warning, error | LCP Name: brake usr pwr lim




Remedy:

  • Check load cycle and braking duty.

  • Check parameter 2-16 settings.


0x7183 / 0x159

Brake mains voltage too high

Cause: The brake resistor mains voltage is too high.

Severity: Warning | LCP Name: brake volt high




Remedy:

  • Check mains supply voltage.


0x7320 / 0x10C

Internal position sensor error

Cause: Absolute position sensor error.

Severity: Trip lock | LCP Name: int sensor err




Remedy:

  • Check internal sensor connections (if accessible).

  • Replace unit if hardware failure.


0x7380 / 0x10D

External position sensor error

Cause: External encoder data could not be read.

Severity: Error | LCP Name: ext sensor err




Remedy:

  • Check external encoder connections and cabling.

  • Check encoder power supply.


0x8611 / 0x10E

Following error

Cause: A following error has occurred.

Severity: Warning, error | LCP Name: following err




Remedy:

  • Check control loop tuning.

  • Check for mechanical blocking or high friction.


0x8693 / 0x10F

Homing error on entering homing mode

Cause: Could not enter homing mode (for example velocity not 0).

Severity: Warning | LCP Name: Homing mode fail




Remedy:

  • Ensure motor is stopped before starting homing.


0x8694 / 0x110

Homing error on start homing method

Cause: Could not start homing method (for example drive not in standstill).

Severity: Warning | LCP Name: Homing method fail




Remedy:

  • Ensure drive status allows for homing initiation.


0x8695 (0x111)
Homing error distance

Cause: Homing distance reached.


Remedy:

  • Severity: Warning

  • Check homing parameters and distance settings.

  • LCP Name: Homing distance


0xFF01 (0x112)
Mechanical brake failure

Cause: No brake or wire failure detected.


Remedy:

  • Severity: Trip lock

  • Check mechanical brake wiring.

  • Check brake connection.

  • LCP Name: brake mech fail


0xFF02 (0x113)
Short circuit in mechanical brake control

Cause: Short circuit in brake control.


Remedy:

  • Severity: Trip lock

  • Check for short circuits in the brake cabling.

  • LCP Name: brake mech short


0xFF0A (0x114)
External interface power failure

Cause: External interface power supply failure.


Remedy:

  • Severity: Error

  • Check external power supply connections.

  • LCP Name: ext IF pwr fail


0xFF10 (0x14F)
Communication interrupted

Cause: The fieldbus communication has been interrupted while the device was enabled.


Remedy:

  • Severity: Error

  • Check fieldbus cabling and master.

  • LCP Name: Comm interrupt


0xFF21 (0x145)
Fan feedback inconsistent

Cause: Internal fan fault. Internal fan not running/mounted.


Remedy:

  • Severity: Warning

  • Check if the fan is blocked or disconnected.

  • Replace fan if necessary.

  • LCP Name: fan feedback


0xFF22 (0x15A)
Fan lifetime critical

Cause: The theoretical lifetime of the fan has been exceeded.


Remedy:

  • Severity: Warning

  • Plan to replace the fan.

  • LCP Name: fan lifetime


0xFF60 (0x115)
Timing violation 1

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 1


0xFF61 (0x116)
Timing violation 2

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 2


0xFF62 (0x117)
Timing violation 3

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 3


0xFF63 (0x118)
Timing violation 4

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 4


0xFF64 (0x119)
Timing violation 5

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 5


0xFF65 (0x11A)
Timing violation 6

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 6


0xFF66 (0x168)
Timing violation 7

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 7


0xFF67 (0x16B)
Timing violation 8

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 8


0xFF68 (0x16C)
Timing violation 9

Cause: Internal timing violation detected.


Remedy:

  • Severity: Trip lock

  • Contact Danfoss.

  • LCP Name: timing err 9


0xFF70 (0x11B)
Firmware: Package description mismatch

Cause: The firmware found does not match the package description.


Remedy:

  • Severity: Trip lock

  • Check firmware version and package.

  • LCP Name: FW pack err


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:

  • Severity: Warning, error

  • Perform a power cycle (Power Off/On).

  • LCP Name: need power cycle


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:

  • Severity: Warning, error

  • Wait for update to complete.

  • Do not enable the device.

  • LCP Name: FW update


0xFF73 (0x15B)
Firmware: Update invalid

Cause: Invalid or corrupted firmware package update. Last valid firmware package has been loaded.


Remedy:

  • Severity: Error

  • Retry firmware update with a valid package.

  • LCP Name: FW upd invalid


0xFF80 (0x11E)
STO active while drive enabled

Cause: STO activated while drive was enabled or tried to enable while STO active.


Remedy:

  • Severity: Error

  • Ensure STO signals are correct before enabling drive.

  • LCP Name: STO active


0xFF81 (0x11F)
STO mismatch

Cause: Dual diagnosis of STO voltage not plausible.


Remedy:

  • Severity: Trip lock

  • Check STO wiring and channels.

  • LCP Name: STO mismatch


0xFF85 (0x120)
P_STO error

Cause: P_STO voltage on the power card exceeds the limits.


Remedy:

  • Severity: Trip lock

  • Check power card supply voltages.

  • LCP Name: P_STO error


0xFF90 (0x121)
Guide value reversed

Cause: Position guide value went backwards while the servo drive was in CAM mode.


Remedy:

  • Severity: Error

  • Check CAM profile generation.

  • LCP Name: guide val rev


0xFF91 (0x122)
Guide value implausible

Cause: Increments between succeeding values too large.


Remedy:

  • Severity: Error

  • Check setpoints and guide value generation.

  • LCP Name: guide val impl


0xFF95 (0x14E)
Sign of life error

Cause: Sign of life error detected.


Remedy:

  • Severity: Error

  • Check communication or internal health.

  • LCP Name: SOL error