Nidec & Control Technique Unidrive M400 Drive

Nidec & Control Technique Unidrive M400 Drive Fault Codes:

Fault Code and MeaningCause and Remedy
28
An Input 1 Loss
Cause: Current loss detected in current mode on Analog input 1 (Terminal 2). In 4-20 mA and 20-4 mA modes, loss is detected if current falls below 3 mA.



Remedy:

  • Check control wiring is correct

  • Check control wiring is undamaged

  • Check the Analog Input 1 Mode (07.007)

  • Ensure current signal is present and greater than 3 mA
189
An Input 1 OI
Cause: Analog input 1 over-current. Current input on analog input 1 exceeds 24mA.



Remedy:

  • Check input signal level.
29
An Input 2 Loss
Cause: Current loss detected in current mode on Analog input 2 (Terminal 5). In 4-20 mA and 20-4 mA modes, loss is detected if current falls below 3 mA.



Remedy:

  • Check control wiring is correct

  • Check control wiring is undamaged

  • Check the Analog Input 2 Mode (07.011)

  • Ensure current signal is present and greater than 3 mA
190
An Input 2 OI
Cause: Analog input 2 over-current. Current input on analog input 2 exceeds 24 mA.



Remedy:

  • Check input signal level.
11
Autotune 1
Cause: Required speed could not be reached during autotune. Sub-trip 2: The motor did not reach the required speed during rotating autotune or mechanical load measurement.



Remedy:

  • Ensure the motor is free to turn i.e. mechanical brake is released

  • Ensure Mechanical Load Test Level (05.021) is set correctly
13
Autotune 3
Cause: Measured inertia has exceeded the parameter range (RFC-A mode only).

Sub-trip 1: Measured inertia exceeded range.

Sub-trip 3: Mechanical load test unable to identify motor inertia.



Remedy:

  • Check motor cable wiring is correct
18
Autotune Stopped
Cause: Autotune test stopped before completion because drive enable or drive run were removed.



Remedy:

  • Check the drive enable signal (Terminal 31 & 34 on size 1 to 4, or terminal 31 & 35 on size 5 to 9) were active during the autotune.

  • Check the run command was active in Digital input 3 or 4 state (Pr 08.003 or Pr 08.004) during the autotune.
19
Brake R Too Hot
Cause: Braking resistor overload timed out (I2t). The Braking Resistor Thermal Accumulator (10.039) has reached 100%.



Remedy:

  • Ensure the values entered in Pr 10.030, Pr 10.031 and Pr 10.061 are correct.

  • Check resistor value and power rating.

  • If an external thermal protection device is being used and software protection is not required, set Pr 10.030, Pr 10.031 or Pr 10.061 to 0 to disable the trip.
185
Card Access
Cause: NV Media Card Write fail. The drive was unable to access the card, or data transfer was corrupted/incomplete.



Remedy:

  • Check NV Media Card is installed / located correctly

  • Replace the NV Media Card
178
Card Busy
Cause: NV Media Card cannot be accessed as it is being accessed by an option module.



Remedy:

  • Wait for the option module to finish accessing the NV Media Card and re-attempt the required function
188
Card Compare
Cause: NV Media Card file/data is different to the one in the drive. A compare has been carried out and differences found.



Remedy:

  • Set Pr mm.000 to 0 and reset the trip

  • Check to ensure the correct data block on the NV Media Card has been used for the compare
179
Card Data Exists
Cause: Attempt made to store data on an NV Media Card in a data block which already contains data.



Remedy:

  • Erase the data in data location

  • Write data to an alternative data location
187
Card Drive Mode
Cause: NV Media Card parameter set not compatible with current drive mode. The drive mode in the data block is different from the current drive mode.



Remedy:

  • Ensure the destination drive supports the drive operating mode in the parameter file.

  • Clear the value in Pr mm.000 and reset the drive

  • Ensure destination drive operating mode is the same as the source parameter file
182
Card Error
Cause: NV Media Card data structure error.

Sub-trip 1: Required folder/file structure not present.

Sub-trip 2: The 000.DAT file is corrupted.

Sub-trip 3: Two or more files in the MCDF folder have the same ID.



Remedy:

  • Erase all the data block and re-attempt the process

  • Ensure the card is located correctly

  • Replace the NV Media Card
184
Card Full
Cause: NV Media Card full. Not enough space left on the card.



Remedy:

  • Delete a data block or the entire NV Media Card to create space

  • Use a different NV Media Card
183
Card No Data
Cause: NV Media Card data not found. Access attempted on a non-existent file.



Remedy:

  • Ensure data file number is correct
180
Card Option
Cause: Option module installed is different between source drive and destination drive.



Remedy:

  • Ensure the correct option module is installed.

  • Press the red reset button to acknowledge that the parameters for the option module installed will be at their default values

  • This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
175
Card Product
Cause: NV Media Card data blocks are not compatible with the drive derivative.

Sub-trip 1: Drive Derivative (11.028) differs.

Sub-trip 2: Product Type (11.063) differs or file corrupted.



Remedy:

  • Use a different NV Media Card

  • This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive, if sub-trip 1.

  • Choose a file compatible between the source and target drives, if sub-trip 2.
186
Card Rating
Cause: The voltage and/or current rating of the source and destination drives are different.



Remedy:

  • Reset the drive to clear the trip

  • Ensure that the drive rating dependent parameters have transferred correctly.

  • This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
181
Card Read Only
Cause: NV Media Card has the Read Only bit set. Attempt made to modify read-only data.



Remedy:

  • Clear the read only flag by setting Pr mm.000 to 9777 and reset the drive. This will clear the read-only flag for all data blocks in the NV Media Card
174
Card Slot
Cause: Option module file transfer has failed. The option module does not respond correctly.



Remedy:

  • Check option module installation and status.
35
Control Word
Cause: Trip initiated from the Control Word (06.042) when bit 12 is set and control word is enabled.



Remedy:

  • Check the value of Pr 06.042.

  • Disable the control word in Control Word Enable (Pr 06.043).

  • Note: When enabled, trip can only be cleared by setting bit 12 to zero.
225
Current Offset
Cause: Current feedback offset error. The current offset is too large to be trimmed.



Remedy:

  • Ensure that there is no possibility of current flowing in the output phases of the drive when the drive is not enabled

  • Hardware fault – Contact the supplier of the drive
97
Data Changing
Cause: Drive parameters are being changed. A user action or file system write is active while the drive is enabled (e.g., loading defaults, changing mode, transferring card data).



Remedy:

  • Ensure the drive is not enabled when one of the following is being carried out:

  • Loading defaults

  • Transferring user program

  • Changing drive mode

  • Transferring data from NV Media Card
110
DCCT Ref
Cause: DCCT Reference out of range for size 5 upwards only.



Remedy:

  • Hardware fault – Contact the supplier of the drive
246
Derivative ID
Cause: Derivative file error.

Sub-trip 1: File missing or invalid.

Sub-trip 2: File does not match control board hardware.

Sub-trip 3: File has been changed for a different derivative number.



Remedy:

  • Contact the supplier of the drive
248

Derivative product image error
Cause: The Derivative Image trip indicates that an error has been detected in the derivative product image. The reason for the trip can be identified by the sub-trip number.



Remedy:

  • Contact the supplier of the drive.
199

Destination parameter conflict
Cause: The Destination trip indicates that destination parameters of two or more functions (Menus 7, 8, 9, 12 or 14) within the drive are writing to the same parameter.



Remedy:

  • Set Pr mm.000 to ‘Destinations’ or 12001 and check all visible parameters in all menus for parameter write conflicts.
232

Drive configuration
Cause: The hardware ID does not match the user software ID.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
31

EEPROM Fail
Cause: Default parameters have been loaded. This indicates that default parameters have been loaded due to corrupted data (User Save or Power Down Save) or checksum failure in the non-parameter area of the EEPROM.



Remedy:

  • Default the drive and perform a reset.

  • Allow sufficient time to perform a save before the supply to the drive is removed.

  • If the trip persists – return drive to supplier.
6

External Trip
Cause: An External Trip trip has occurred. This is initiated by writing a value of 6 in Pr 10.038 or via digital input.



Remedy:

  • Check the value of Pr 10.032.

  • Select ‘Destinations’ (or enter 12001) in Pr mm.000 and check for a parameter controlling Pr 10.032.

  • Ensure Pr 10.032 or Pr 10.038 (= 6) is not being controlled by serial comms.
173

Fan Fail
Cause: Fan fail. This trip cannot be reset until 10 s after the trip was initiated.



Remedy:

  • Check that the fan is installed and connected correctly.

  • Check that the fan is not obstructed.

  • Contact the supplier of the drive to replace the fan.
247

File changed
Cause: The file system configuration or data has changed.



Remedy:

  • Power cycle the drive.
237

FW incompatible
Cause: The FW incompatible trip indicates that the user firmware is incompatible with the power firmware.



Remedy:

  • Re-program the drive with the latest version of the drive firmware for Unidrive M400, using Unidrive M Connect.
HF01

Data processing error: CPU hardware fault
Cause: A CPU address error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF02

Data processing error: CPU memory management fault
Cause: A DMAC address error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF03

Data processing error: CPU has detected a bus fault
Cause: A bus fault has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF04

Data processing error: CPU has detected a usage fault
Cause: A usage fault has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF07

Data processing error: Watchdog failure
Cause: A watchdog failure has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF08

Data processing error: CPU Interrupt crash
Cause: A CPU interrupt crash has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF09

Data processing error: Free store overflow
Cause: A free store overflow has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF11

Data processing error: Non-volatile memory comms error
Cause: A non-volatile memory comms error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • If Sub-trip 1: Hardware fault – contact the supplier of the drive.

  • If Sub-trip 2: Re-program drive with compatible user firmware.
HF12

Data processing error: Main program stack overflow
Cause: The main program stack overflow has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF16

Data processing error: RTOS error
Cause: A RTOS error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF18

Data processing error: Internal flash memory has failed
Cause: The internal flash memory has failed when writing option module parameter data.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF19

Data processing error: CRC check on the firmware has failed
Cause: The CRC check on the drive firmware has failed. The drive is now in its Bootloader and is waiting for a new image.



Remedy:

  • Re-program the drive with latest control and power firmware using Unidrive M Connect.

  • Hardware fault – Contact the supplier of the drive.
HF23

Hardware fault
Cause: General hardware failure.



Remedy:

  • If this trip occurs, contact the supplier of the drive.
250

Hot Rect/Brake
Cause: Over-temperature detected on input rectifier or braking IGBT.



Remedy:

  • Increase ventilation by setting Cooling Fan Control (06.045) > 0.
231

I cal. range
Cause: Current calibration range error.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
26

I/O Overload
Cause: The total current drawn from the AI adaptor 24 V or from the digital output has exceeded the limit.



Remedy:

  • Check total loads on digital outputs and 24 V.

  • Check control wiring is correct.

  • Check output wiring is undamaged.
34

Keypad Mode
Cause: The drive is in keypad mode [Reference Selector (01.014) = 4 or 6] and the keypad has been removed or disconnected.



Remedy:

  • Re-install keypad and reset.

  • Change Reference Selector (01.014) to select the reference from another source.
90

LF Power Comms
Cause: Communication has been lost / errors detected between power, control and rectifier modules.



Remedy:

  • Hardware fault – contact the supplier of the drive.
20
Motor Too Hot
Cause: Motor thermal overload detected based on the Motor Rated Current and Thermal Time Constant. The drive trips when the estimated motor temperature reaches 100%.



Remedy:

  • Ensure the load is not jammed / sticking.

  • Check the load on the motor has not changed.

  • Tune the motor rated speed parameter (Pr 5.008) (RFC-A mode only).

  • Ensure the motor rated current is not zero.
236
No power board
Cause: No communication between the power and control boards.



Remedy:

  • Hardware fault – contact the supplier of the drive.
219
OHt Control
Cause: Control stage over-temperature detected (often if Cooling Fan Control = 0). This causes the option module to go to standby.



Remedy:

  • Increase ventilation by setting Cooling Fan Control (06.045) > 0.
27
OHt dc bus
Cause: DC bus component over temperature based on a software thermal model. Causes include output current effects and DC bus ripple.



Remedy:

  • Check the AC supply voltage balance and levels.

  • Check DC bus ripple level.

  • Reduce duty cycle.

  • Reduce motor load.

  • Check the output current stability. If unstable:

    • Check motor map settings against nameplate.

    • Disable slip compensation (Open loop).

    • Disable dynamic V to F operation (Open loop).

    • Select fixed boost (Open loop).

    • Select high stability space vector modulation (Open loop).

    • Disconnect load and complete rotating auto-tune.

    • Reduce frequency loop gains (RFC-A).
21
OHt Inverter
Cause: IGBT junction over-temperature detected based on a software thermal model (Trip at 145 °C).



Remedy:

  • Reduce the selected drive switching frequency.

  • Ensure Auto-switching Frequency Change Disable (05.035) is set to OFF.

  • Reduce duty cycle.

  • Increase acceleration / deceleration rates.

  • Reduce motor load.

  • Check DC bus ripple.

  • Ensure all three input phases are present and balanced.
22
OHt Power
Cause: Power stage over-temperature has been detected. The sub-trip identifies the specific thermistor location.



Remedy:

  • Check enclosure / drive fans are still functioning correctly.

  • Force the heatsink fans to run at maximum speed.

  • Check enclosure ventilation paths and door filters.

  • Increase ventilation.

  • Reduce the drive switching frequency.

  • Reduce duty cycle.

  • Increase acceleration / deceleration rates.

  • Use S Ramp Enable (02.006).

  • Reduce motor load.

  • Check the derating tables and confirm the drive is correctly sized.

  • Use a drive with larger current / power rating.
3
OI ac
Cause: Instantaneous output over current detected (exceeded Pr 11.061). Can be caused by short circuits or incorrect loop gains.



Remedy:

  • Increase acceleration/deceleration rate.

  • If seen during auto-tune reduce the voltage boost.

  • Check for short circuit on the output cabling.

  • Check integrity of the motor insulation using an insulation tester.

  • Is the motor cable length within limits for the frame size?

  • Reduce the values in the frequency loop gain parameters.

  • Reduce the values in the current loop gain parameters.
92
OI Snubber
Cause: Over-current condition detected in the rectifier snubbing circuit.



Remedy:

  • Ensure the internal EMC filter is installed.

  • Ensure the motor cable length does not exceed the maximum for selected switching frequency.

  • Check for supply voltage imbalance.

  • Check for supply disturbance such as notching from a DC drive.

  • Check the motor and motor cable insulation with an insulation tester.

  • Fit an output line reactor or sinusoidal filter.
4
OI Brake
Cause: Over current detected in braking IGBT or braking IGBT protection has been activated.



Remedy:

  • Check brake resistor wiring.

  • Check braking resistor value is greater than or equal to the minimum resistance value.

  • Check braking resistor insulation.
98
Out Phase Loss
Cause: Output phase loss detected at the drive output while running.



Remedy:

  • Check motor and drive connections.

  • To disable the trip set Output Phase Loss Detection Enable (06.059) = 0.
228
Output phase s/c
Cause: Over-current detected on drive output when enabled. Possible motor ground fault.



Remedy:

  • Check for short circuit on the output cabling.

  • Check integrity of the motor insulation using an insulation tester.

  • Is the motor cable length within limits for the frame size?
7
Over Speed
Cause: Motor frequency has exceeded the over frequency threshold set in Pr 03.008 or derived from Pr 01.006.



Remedy:

  • Check that the motor is not being driven by another part of the system.

  • Reduce the Frequency Controller Proportional Gain (03.010) to reduce frequency overshoot.

  • Reduce Current Controller Ki Gain (04.014).
2
Over Volts
Cause: DC bus voltage has exceeded the peak level or maximum continuous level for 15 seconds.



Remedy:

  • Increase deceleration ramp (Pr 00.004).

  • Decrease the braking resistor value (staying above the minimum value).

  • Check nominal AC supply level.

  • Check for supply disturbances which could cause the DC bus to rise.

  • Check motor insulation using an insulation tester.
32
Phase Loss
Cause: Supply phase loss, large supply imbalance, or excessive DC bus ripple.



Remedy:

  • Check the AC supply voltage balance and level at full load.

  • Check the DC bus ripple level with an isolated oscilloscope.

  • Check the output current stability.

  • Check for mechanical resonance with the load.

  • Reduce the duty cycle.

  • Reduce the motor load.

  • Disable the phase loss detection, set Pr 06.047 to 2.
235
Power Board HF
Cause: Power processor hardware fault.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
245
Power Boot Mode
Cause: Power board is in bootloader mode.



Remedy:

  • Send power board firmware file to reprogram the power board using Unidrive M Connect and power cycle drive.
93
Power Comms
Cause: Communication has been lost / errors detected between control and power board (e.g., PLL range out of lock, CRC error).



Remedy:

  • Hardware fault – Contact the supplier of the drive.
220
Power Data
Cause: Power system configuration data error.

This trip indicates that there is an error in the configuration data stored in the power system. The trip is related to the table uploaded from the power system at power-up.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
37
Power Down Save
Cause: Power down save error.

The Power Down Save trip indicates that an error has been detected in the power down save parameters saved in non-volatile memory.



Remedy:

  • Perform a 1001 save in Pr mm.000 to ensure that the trip doesn’t occur the next time the drive is powered up.
5
PSU
Cause: Internal power supply fault.

The PSU trip indicates that one or more internal power supply rails are outside limits or overloaded.



Remedy:

  • Remove the option module and perform a reset.

  • There is a hardware fault within the drive – return the drive to the supplier.
Reserved
Various Codes
Cause: Reserved trips.

Codes: 01, 09, 12, 14-17, 23, 38, 39, 91, 94-95, 99, 101-109, 111, 168-172, 176, 191-198, 205-217, 222-224, 229-230, 233, 238-244, 251-254.

These trip numbers are reserved for future use and should not be used by user application programs.



Remedy:

  • No specific remedy available.
33
Resistance
Cause: Measured resistance has exceeded the parameter range.

The measured stator resistance of the motor during an auto-tune test has exceeded the maximum possible value, or a value written exceeds the limit. This can occur if the motor is very small in comparison to the rating of the drive.



Remedy:

  • Ensure the stator resistance of the motor falls within the range of the drive model. (Ratio of drive size to motor size > 15:1 may cause problems).

  • Check that a value has not been entered in the Stator Resistance that exceeds the allowed range.

  • Check the motor cable / connections.

  • Check the integrity of the motor stator winding using an insulation tester.

  • Check the motor phase to phase resistance at the drive terminals.

  • Check the motor phase to phase resistance at the motor terminals.

  • Select fixed boost mode (Pr 05.014 = Fd) and verify output current waveforms.

  • Replace the motor.
204
Slot 1 Different
Cause: Option module in option slot 1 has changed.

The option module in slot 1 is a different type to that installed when parameters were last saved.



Remedy:

  • Turn off the power, ensure the correct option module is installed in the option slot and re-apply the power.

  • Confirm that the currently installed option module is correct, ensure option module parameters are set correctly and perform a user save in Pr mm.000.
202
Slot 1 Error
Cause: Option module in option slot 1 has detected a fault.

The option module in slot 1 has detected an error. The reason can be identified by the sub-trip number.



Remedy:

  • See relevant option module User Guide for details of the trip.
200
Slot 1 HF
Cause: Option module 1 hardware fault.

The drive detected a hardware fault with the module in Slot 1. Causes vary by sub-trip (e.g., ID failure, memory insufficient, timeout).



Remedy:

  • Ensure the option module is installed correctly.

  • Replace the option module.

  • Replace the drive.
203
Slot 1 Not Fitted
Cause: Option module in option slot 1 has been removed.

The option module in slot 1 has been removed since the last power up.



Remedy:

  • Ensure the option module is installed correctly.

  • Re-install the option module.

  • To confirm that the removed option module is no longer required perform a save function in Pr mm.000.
201
Slot 1 Watchdog
Cause: Option module watchdog function service error.

The option module installed in Slot 1 started the watchdog function and failed to service it correctly.



Remedy:

  • Replace the option module.
226
Soft Start
Cause: Soft start relay failed to close, soft start monitor failed.

The soft start relay in the drive failed to close or the monitoring circuit has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
234
STO Error
Cause: No Safe Torque Off board fitted.

The STO board is not fitted.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
221
Stored HF
Cause: Hardware trip has occurred during last power down.

A hardware trip (HF01 – HF18) occurred and the drive has been power cycled.



Remedy:

  • Enter 1299 in Pr mm.000 and press reset to clear the trip.
227
Sub-array RAM
Cause: RAM allocation error.

An option module derivative or user program image has requested more parameter RAM than is allowed.



Remedy:

  • Check the specific sub-trip to identify the cause (Applications menus, Derivative image, User program image, etc.).
218
Temp Feedback
Cause: Internal thermistor has failed.

An internal thermistor has failed in the drive (open circuit or short circuit).



Remedy:

  • Hardware fault – Contact the supplier of the drive.
10
Th Brake Res
Cause: Brake resistor over temperature.

Hardware based braking resistor thermal monitoring is connected and the resistor is overheating.



Remedy:

  • Check brake resistor wiring.

  • Check braking resistor value is greater than or equal to the minimum resistance value.

  • Check braking resistor insulation.
25
Th Short Circuit
Cause: Motor thermistor short circuit.

The motor thermistor connected to terminal 14 (digital input 5) is short circuit or low impedance (<50 Ω).



Remedy:

  • Check thermistor continuity.

  • Replace motor / motor thermistor.
24
Thermistor
Cause: Motor thermistor over-temperature.

The motor thermistor connected to terminal 14 indicates a motor over-temperature.



Remedy:

  • Check Threshold Level (Pr 07.048).

  • Check motor temperature.

  • Check thermistor continuity.
8
User OI ac
Cause: User OI ac trip.

Initiated if the output current of the drive exceeds the trip level set by User Over Current Trip Level (Pr 04.041).



Remedy:

  • Check load conditions and trip level settings.
96
User Prog Trip
Cause: Trip generated by an onboard user program.

This trip is initiated from within an onboard user program using a function call.



Remedy:

  • Check the user program.
249
User Program (Onboard user program error)
Cause: An error has been detected in the onboard user program image. The sub-trip indicates the reason for the trip (e.g., Divide by zero, Undefined trip, Array bounds violation, CRC failure).



Remedy:

  • Check the user program code for logic errors (e.g., divide by zero, pointer access).

  • Ensure the image is compatible with the control board and firmware version.

  • If “Customizable menu table changed” occurs, save drive parameters.

  • Review specific sub-trip codes (1-208) in the manual for detailed debugging.
36
User Save
Cause: User Save error / not completed. The trip indicates that an error has been detected in the user save parameters saved in non-volatile memory. For example, following a user save command, if the power to the drive was removed when the user parameters were being saved.



Remedy:

  • Perform a user save in Pr mm.000 to ensure that the trip doesn’t occur the next time the drive is powered up.

  • Ensure that the drive has enough time to complete the save before removing the power to the drive.
40 – 89, 112 – 167
User Trip
Cause: User generated trip. These trips are not generated by the drive and are to be used by the user to trip the drive through an application program.



Remedy:

  • Check the user program.
30
Watchdog
Cause: Control word watchdog has timed out. The Watchdog trip indicates that the control word has been enabled and has timed out.



Remedy:

  • Once Pr 06.042 bit 14 has been changed from 0 to 1 to enable the watchdog, this must be repeated every 1s or a Watchdog trip will be initiated.

  • The watchdog is disabled when the trip occurs and must be re-enabled if required when the trip is reset.
HFxx
Internal faults
Cause: Internal drive problems (Trips HF01 to HF23).


Remedy:

  • These faults indicate internal problems.

  • Cannot be reset.

  • All drive features are inactive after these trips occur.

  • If non-permanent: Power cycle the drive.
{Stored HF}
Stored HF trip
Cause: A non-permanent HF trip occurred and the drive was power cycled. The sub-trip number indicates the original HF fault code.


Remedy:

  • Enter 1299 in Parameter (mm.000).

  • Initiate a reset to clear the trip.
218 to 247, {Slot 1 HF}
Non-resettable trips
Cause: Severe hardware or software fault.


Remedy:

  • These trips cannot be reset.

  • Check drive hardware / internal connections.
{EEPROM Fail}
Volatile memory failure
Cause: Failure in volatile memory (RAM/EEPROM) consistency.


Remedy:

  • Set Parameter mm.000 to 1233 or 1244.

  • Or, set Load Defaults (11.043) to a non-zero value.
174, 175, 177 to 188
NV Media Card trips
Cause: Issues related to the Non-Volatile Media Card.


Remedy:

  • Check the NV Media Card installation.

  • Note: These trips are priority 5 during power-up.
{PSU}
Internal 24V
Cause: Rectifier 24 V internal supply issue.


Remedy:

  • Check internal power supply conditions.
{OI.ac}, {OI Brake}, {Fan Fail}
Trips with extended reset times
Cause: Over-current or Fan failure detected.


Remedy:

  • Wait for the extended timer to expire.

  • These trips cannot be reset until 10 seconds after the trip was initiated.
{Phase Loss}, {OHt dc bus}
Phase loss and d.c. link protection
Cause: Input phase loss detected or DC link thermal protection active.


Remedy:

  • Check input power wiring.

  • The drive attempts to stop the motor before tripping (unless Action On Trip Detection 10.037 is disabled).

  • Drive always attempts to stop the motor before tripping on {OHt dc bus}.
Brake Resistor
Brake resistor overload
Cause: Braking Resistor Thermal Accumulator (10.039) has reached 75.0% of the trip value.


Remedy:

  • Check braking cycle and load.

  • Verify resistor sizing.
Motor Overload
Motor Protection Accumulator Warning
Cause: Motor Protection Accumulator (4.019) has reached 75.0% of the trip value and load is >100%.


Remedy:

  • Reduce motor load.

  • Check motor parameters.
Drive Overload
Drive over temperature
Cause: Percentage of Drive Thermal Trip Level (07.036) is greater than 90%.


Remedy:

  • Check drive cooling and ambient temperature.

  • Reduce load.
Auto Tune
Auto tune in progress
Cause: The autotune procedure has been initialized.


Remedy:

  • Wait for autotune to complete.

  • No action required unless it hangs.
Limit Switch
Limit switch active
Cause: Indicates that a limit switch is active causing the motor to be stopped.


Remedy:

  • Check machine position.

  • Check limit switch wiring.
Option Slot 1
Option slot alarm
Cause: Alarm generated by the module in Slot 1.


Remedy:

  • Check Option Module diagnostics.
Low AC
Low voltage mode
Cause: Drive is in Low Voltage mode.


Remedy:

  • See Low AC Alarm (10.107) for details.
Current limit
Current limit active
Cause: Drive is operating at current limit.


Remedy:

  • See Current Limit Active (10.009).

  • Check mechanical load or acceleration rate.
24V Backup Lost
24V Backup not present
Cause: The 24V backup supply is missing.


Remedy:

  • Check external 24V supply.

  • See 24V Alarm Loss Enable (11.098).
Inhibit
Drive inhibited
Cause: Safe Torque Off (STO) signals not applied or Pr 06.015 is set to 0.


Remedy:

  • Check Safe Torque Off terminals.

  • Check Enable Conditions (06.010).

  • Drive output is disabled.
Ready
Drive ready
Cause: Drive enable is active, but inverter is not active (final drive run not active).


Remedy:

  • Give Run command to start.

  • Drive output is disabled.
Stop
Drive stopped
Cause: Drive is holding zero frequency.


Remedy:

  • Drive output is enabled.
Run
Drive running
Cause: Drive is active and running.


Remedy:

  • Normal operation. Drive output is enabled.
Supply Loss
Supply loss condition
Cause: Supply loss condition has been detected.


Remedy:

  • Check incoming power supply.
Deceleration
Decelerating
Cause: Motor is decelerating to zero because final drive run was deactivated.


Remedy:

  • Normal stopping sequence.
dc Injection
DC Injection Braking
Cause: The drive is applying DC injection braking.


Remedy:

  • Normal braking operation.
Trip
Drive Tripped
Cause: The drive has tripped and is no longer controlling the motor.


Remedy:

  • Check the trip code in the lower display.

  • Resolve the fault and reset.

  • Drive output is disabled.
Under Voltage
Under voltage state
Cause: Drive is in under voltage state (low or high voltage mode).


Remedy:

  • Check DC bus voltage and input supply.

  • Drive output is disabled.
Heat
Motor pre-heat
Cause: The motor pre-heat function is active.


Remedy:

  • Normal operation if configured.

  • Drive output is enabled.