Nidec & Control Technique HVAC Drive H300 Drive

Nidec & Control Technique HVAC Drive H300 Drive Fault Codes:

Fault Code and MeaningCause and Remedy
28
An Input 1 Loss (Analog input 1 current loss)
Cause: Current loss detected in current mode on Analog input 1 (Terminal 5, 6). In 4-20 mA and 20-4 mA modes, loss of input is detected if the 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.
29
An Input 2 Loss (Analog input 2 current loss)
Cause: Current loss detected in current mode on Analog input 2 (Terminal 7). In 4-20 mA and 20-4 mA modes, loss of input is detected if the 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.
219
An Output Calib (Analog output calibration failed)
Cause: The zero offset calibration of one or both of the analogue outputs has failed. Likely hardware failure or voltage applied to output via low impedance/wiring error.

Sub-trip 1: Output 1 failed (Terminal 9).

Sub-trip 2: Output 2 failed (Terminal 10).



Remedy:

  • Check the wiring associated with analog outputs.

  • Remove all the wiring that is connected to analog outputs and perform a re-calibration by power cycling the drive.

  • If trip persists, replace the drive.
217
App Menu Changed (Customization table changed)
Cause: The customization table for an application menu has changed (Menu 18, 19, or 20). If more than one menu changed, the lowest menu has priority.



Remedy:

  • Reset the trip and perform a parameter save to accept the new settings.
11
Autotune 1 (Position feedback or speed error)
Cause: Tripped during autotune.

Sub-trip 1: Position feedback did not change during rotating autotune.

Sub-trip 2: Motor did not reach required speed during rotating autotune or mechanical load measurement.



Remedy:

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

  • Ensure Pr 03.026 is set correctly (or appropriate 2nd motor map parameter).

  • Check feedback device wiring is correct.

  • Check encoder mechanical coupling to the motor.
12
Autotune 2 (Position feedback direction incorrect)
Cause: Tripped during rotating autotune.

Sub-trip 1: Position feedback direction incorrect.

Sub-trip 2: SINCOS encoder with comms used, position rotating opposite to sine wave based position.



Remedy:

  • Check motor cable wiring is correct.

  • Check feedback device wiring is correct.

  • Swap any two motor phases.
13
Autotune 3 (Measured inertia / Commutation signals)
Cause: Tripped during rotating autotune or mechanical load measurement test.

Sub-trip 1: Measured inertia exceeded parameter range.

Sub-trip 2: Commutation signals changed in wrong direction.

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



Remedy:

  • Check motor cable wiring is correct.

  • Check feedback device U,V and W commutation signal wiring is correct.

  • Increase the test level.

  • If test was carried out at standstill, repeat the test with the motor rotating within the recommended speed range.
17
Autotune 7 (Motor poles / position feedback resolution)
Cause: Initiated during rotating autotune if the motor poles or the position feedback resolution have been set up incorrectly.



Remedy:

  • Check line per revolution for feedback device.

  • Check the number of poles in Pr 05.011.
18
Autotune Stopped (Stopped before completion)
Cause: Prevented from completing autotune because either drive enable or drive run were removed.



Remedy:

  • Check the drive enable signal (Terminal 29) was active during the autotune.

  • Check the run command was active in Pr 08.005 during autotune.
19
Brake R Too Hot (Braking resistor overload timed out)
Cause: Braking resistor overload timed out ($I^2t$). The trip is initiated when Braking Resistor Thermal Accumulator (10.039) reaches 100%.



Remedy:

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

  • 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 (NV Media Card Write fail)
Cause: Drive unable to access NV Media Card. File being written may be corrupted or transfer incomplete.



Remedy:

  • Check NV Media Card is installed / located correctly.

  • Replace the NV Media Card.

  • Restore parameters by powering drive down and up again (if failed during transfer).
177
Card Boot (Menu 0 param modification not saved)
Cause: Write to Menu 0 initiated but necessary boot file not created on NV Media Card. Occurs when Pr 11.042 changed to Auto or Boot mode but drive not reset.



Remedy:

  • Ensure that Pr 11.042 is correctly set, and then reset the drive to create the necessary file on the NV Media Card.

  • Re-attempt the parameter write to the Menu 0 parameter.
178
Card Busy (NV Card accessed by option module)
Cause: Attempt to access file on NV Media Card while it is already being accessed by an option module. No data transferred.



Remedy:

  • Wait for the option module to finish accessing the NV Media Card and re-attempt the required function.
188
Card Compare (File/data different to drive)
Cause: Compare carried out between file on NV Media Card and drive; parameters differ.



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 (Location already contains data)
Cause: Attempt made to store data in a block which already contains data.



Remedy:

  • Erase the data in data location.

  • Write data to an alternative data location.
187
Card Drive Mode (Parameter set not compatible)
Cause: Drive mode in data block differs from current drive mode, or operating mode in data block is outside allowed range.



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 (NV Media Card data structure error)
Cause: Error detected in data structure.

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

Sub-trip 2: The <000> file is corrupted.

Sub-trip 3: Two or more files have same identification number.



Remedy:

  • Erase all the data block and re-attempt the process (Note: Resetting trip erases folder structure).

  • Ensure the card is located correctly.

  • Replace the NV Media Card.
184
Card Full (NV Media Card full)
Cause: Not enough space left on the card to create a data block.



Remedy:

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

  • Use a different NV Media Card.
183
Card No Data (NV Media Card data not found)
Cause: Attempt made to access non-existent file or block on a NV Media Card.



Remedy:

  • Ensure data block number is correct.
180
Card Option (Option modules installed are different)
Cause: Option module categories differ between source and destination drives. This is a warning; data for option modules different will be set to defaults.



Remedy:

  • Ensure the correct option modules are installed.

  • Ensure the option modules are in the same option module slot as the parameter set stored.

  • Press the red reset button to acknowledge defaults loaded for option modules.

  • This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
175
Card Product (Data blocks not compatible with drive derivative)
Cause: Drive Derivative (11.028) or Product Type (11.063) differ between source and target drives.

Sub-trip 1: Drive Derivative differs.

Sub-trip 2: Product Type differs or file corruption.

Sub-trip 3: Unidrive SP parameter value found with no equivalent.



Remedy:

  • Use a different NV Media Card.

  • This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
186
Card Rating (Voltage / current rating different)
Cause: Current and/or voltage ratings are different between source and destination drives. Rating specific parameters may not be transferred.



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 (Read Only bit set)
Cause: Attempt made to modify a read-only NV Media Card or read-only data block.



Remedy:

  • Clear the read only flag by setting Pr mm.000 to 9777 and reset the drive.

  • This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
174
Card Slot (Option module application program transfer failed)
Cause: Transfer of an option module application program failed because the option module did not respond correctly.



Remedy:

  • Ensure the source / destination option module is installed on the correct slot.
111
Configuration
Cause: The number of power modules installed is different from the modules expected (Pr 11.071), or the number of external rectifiers (Pr 11.096) is incorrect.



Remedy:

  • Ensure that all the power modules are correctly connected.

  • Ensure all the power modules have powered up correctly.

  • Ensure that the value in Pr 11.071 is set to the number of power modules connected.

  • Set Pr 11.035 to 0 to disable the trip if it is not required.

  • Ensure that all the external rectifiers are connected correctly.

  • Ensure that the value in Number Of Rectifiers Expected (11.096) is correct.
35
Control Word
Cause: Trip initiated from the Control Word. Bit 12 on the control word in Pr 06.042 was set when the control word was enabled (Pr 06.043 = On).



Remedy:

  • Check the value of Pr 06.042.

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

  • Clear the trip by setting bit 12 to zero.
225
Current Offset
Cause: Current feedback offset error. The current feedback offset is too large to be trimmed correctly.



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 while the drive is active. Actions include loading defaults, changing drive mode, or transferring data from NV memory card.



Remedy:

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

  • Loading defaults.

  • Changing drive mode.

  • Transferring data from NV Media Card or position feedback device.

  • Transferring user programs.
247
Derivative ID
Cause: There is a problem with the identifier associated with derivative image which customizes the drive.

Sub-trip 1: Image erased.

Sub-trip 2: Identifier out of range.

Sub-trip 3: Derivative image changed.



Remedy:

  • Check the derivative image status.

  • Contact the supplier of the drive.
248
Derivative Image
Cause: Derivative Image error. An error has been detected in the derivative image.

See sub-trip codes (1-52, 61-64, 70-74, 80-81) for specific details regarding option slots or missing images.



Remedy:

  • Contact the supplier of the drive.
199
Destination
Cause: Two or more parameters are writing to the same destination parameter.



Remedy:

  • Set Pr mm.000 to ‘Destinations’ or 12001 and check all visible parameters in all menus for parameter write conflicts.
224
Drive Size
Cause: Power stage recognition: Unrecognized drive size. The control PCB has not recognized the drive size of the power circuit.



Remedy:

  • Ensure the drive is programmed to the latest firmware version.

  • Hardware fault – return drive to supplier.
31
EEPROM Fail
Cause: Default parameters have been loaded. The exact cause is identified by the sub-trip number (e.g., checksum failure, version change, CRC error).



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.
197
Encoder 9
Cause: Position feedback is selected from an option module slot which does not have a feedback option module installed.



Remedy:

  • Check the setting of Pr 03.026.

  • Ensure that the option slot selected in Pr 03.026 has a feedback option module installed.
6
External Trip
Cause: An External trip is initiated via Pr 10.038, Safe Torque Off input state, or Serial Comms.



Remedy:

  • Check the Safe Torque Off signal voltage on terminal 29 equals to 24 V.

  • Check the value of Pr 08.009 (digital state of terminal 29).

  • If external trip detection of STO is not required, set Pr 08.010 to Off (0).

  • 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.
HF01
Data processing error: CPU address error
Cause: The control PCB on the drive has failed (CPU address error).



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF02
Data processing error: DMAC address error
Cause: A DMAC address error has occurred. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF03
Data processing error: Illegal instruction
Cause: An illegal instruction has occurred. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF04
Data processing error: Illegal slot instruction
Cause: An illegal slot instruction has occurred. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF05
Data processing error: Undefined exception
Cause: An undefined exception error has occurred. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF06
Data processing error: Reserved exception
Cause: A reserved exception error has occurred. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF07
Data processing error: Watchdog failure
Cause: A watchdog failure has occurred. The control PCB 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. The control PCB 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. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF10
Data processing error: Parameter routing system error
Cause: A Parameter routing system error has occurred. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF11
Data processing error: Access to EEPROM failed
Cause: Access to the drive EEPROM has failed. The control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF12
Data processing error: Main program stack overflow
Cause: Main program stack overflow has occurred. The stack can be identified by the sub-trip number (1: Background tasks, 2: Timed tasks, 3: Main system interrupts). This indicates the control PCB has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF13
Data processing error: Firmware incompatible with hardware
Cause: The drive firmware is not compatible with the hardware. Indicates control PCB failure. Sub-trip gives the ID code of the board.



Remedy:

  • Re-program the drive with the latest version of the drive firmware.

  • Hardware fault – Contact the supplier of the drive.
HF14
Data processing error: CPU register bank error
Cause: A CPU register bank error has occurred. Indicates control PCB failure.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF15
Data processing error: CPU divide error
Cause: A CPU divide error has occurred. Indicates control PCB failure.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF16
Data processing error: RTOS error
Cause: A RTOS error has occurred. Indicates control PCB failure.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF17
Data processing error: Clock supplied to control board out of spec
Cause: The clock supplied to the control board logic is out of specification. Indicates control PCB failure.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF18
Data processing error: Internal flash memory has failed
Cause: Internal flash memory failed when writing option module parameter data. Sub-trip identifies reason (e.g., Timeout, CRC errors).



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF19
Data processing error: CRC check on firmware has failed
Cause: The CRC check on the drive firmware has failed.



Remedy:

  • Re-program the drive.

  • Hardware fault – Contact the supplier of the drive.
HF20
Data processing error: ASIC is not compatible with the hardware
Cause: The ASIC version is not compatible with the drive firmware.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
HF23 to HF25
Hardware fault
Cause: General hardware failure detected.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
I/O Overload
(Trip 26)
Digital output overload
Cause: Total current drawn from 24 V user supply or digital output exceeded limit (100 mA).



Remedy:

  • Check total loads on digital outputs.

  • Check control wiring is correct.

  • Check output wiring is undamaged.
Inductance
(Trip 8)
Motor inductances not suitable
Cause: Occurs in RFC-S mode. The ratio or difference between Ld and Lq is too small, or saturation characteristic cannot be measured.



Remedy:

  • Sub-trip 1: Ensure RFC Low Speed Mode (05.064) is set to Non-salient (1), Current (2) or Current No test (3).

  • Sub-trip 2: Ensure RFC Low Speed Mode (05.064) is set to Non-salient (1), Current (2) or Current No test (3).

  • Sub-trip 3: None (Acts as warning).

  • Sub-trip 4: Stationary autotune not possible; perform minimal movement or rotating autotune. Phasing test on starting not possible; use position feedback device.
Inter-connect
(Trip 103)
Multi-power module drive interconnection cable error
Cause: A power module has detected a fault (sub-trip “xx.0.00” indicates module number). Initiated if communication fails, rectifier signals fault, or trip is reset.



Remedy:

  • Check interconnection cables between power modules.

  • Verify module status.
Keypad Mode
(Trip 34)
Keypad removed when drive receiving reference from keypad
Cause: Drive is in keypad mode [Reference Selector (01.014) = 4 or 6] and keypad has been removed or disconnected.



Remedy:

  • Re-install keypad and reset.

  • Change Reference Selector (01.014) to select the reference from another source.
Motor Too Hot
(Trip 20)
Output current overload timed out (I2t)
Cause: Motor thermal overload based on rated current (Pr 05.007) and motor thermal time constant. Trip occurs when accumulator reaches 100%.



Remedy:

  • Ensure the load is not jammed / sticking.

  • Check the load on the motor has not changed.

  • If seen during auto-tune in RFC-S mode, ensure motor rated current (05.007) is ≤ Heavy duty current rating.

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

  • Check feedback signal for noise.

  • Ensure the motor rated current is not zero.
Name Plate
(Trip 176)
Electronic nameplate transfer has failed
Cause: Electronic nameplate transfer between drive and motor failed. Reasons include: Not enough memory, Comms failed, or Checksum failed.



Remedy:

  • Ensure device encoder memory has at least 128 bytes.

  • When writing motor object, ensure encoder memory has at least 256 bytes.

  • Ensure option slot has a feedback option module installed.

  • Check if encoder has been initialized (Position Feedback Initialized 03.076).

  • Verify the encoder wiring.
OHt Brake
(Trip 101)
Braking IGBT over-temperature
Cause: Braking IGBT over-temperature detected based on software thermal model.



Remedy:

  • Check braking resistor value is greater than or equal to the minimum resistance value.
OHt Control
(Trip 23)
Control stage over temperature
Cause: Control stage over-temperature detected. Sub-trip identifies location (01: Control board thermistor 1, 02: Control board thermistor 2, 03: I/O board thermistor).



Remedy:

  • Check enclosure / drive fans are still functioning correctly.

  • Check enclosure ventilation paths.

  • Check enclosure door filters.

  • Increase ventilation.

  • Reduce the drive switching frequency.

  • Check ambient temperature.
OHt dc bus (27)

DC bus over temperature
Cause:


A DC bus component over-temperature has been detected based on a software thermal model (includes effects of output current 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.

  • Check motor map settings (Pr 05.006 – 05.011).

  • Disable slip compensation (Pr 05.027 = 0) (Open loop).

  • Select fixed boost (Pr 05.014 = Fixed) (Open loop).

  • Check encoder signals for noise (RFC-A, RFC-S).
OHt Inverter (21)

Inverter over temperature
Cause:


An IGBT junction over-temperature has been detected based on a firmware thermal model.



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.

  • Reduce the braking load (for sub-trip 300).
OHt Power (22)

Power stage over temperature
Cause:


A power stage over-temperature has been detected (heatsink or specific power module components).



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 or motor load.

  • Decrease acceleration / deceleration rates.

  • Check derating tables to confirm drive is correctly sized.
OI ac (3)

Instantaneous output over current
Cause:


Instantaneous drive output current has exceeded VM_DRIVE_CURRENT_MAX.



Remedy:



  • Acceleration/deceleration rate is too short.

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

  • Check for short circuit on the output cabling.

  • Check integrity of motor insulation using an insulation tester.

  • Check feedback device wiring and mechanical coupling.

  • Check feedback signals are free from noise.

  • Ensure motor cable length is within limits.

  • Reduce speed loop gain parameters (Pr 03.010 – 03.012).
OI Brake (4)

Braking IGBT over current
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.
OI dc (109)

Power module over current
Cause:


Short circuit protection for the drive output stage has been activated (detected from IGBT on state voltage monitoring).



Remedy:



  • Disconnect the motor cable at the drive end and check the motor and cable insulation with an insulation tester.

  • Replace the drive.
OI Snubber (92)

Snubber over-current
Cause:


Over-current condition detected in the rectifier snubber circuit.



Remedy:



  • Ensure the internal EMC Filter is installed.

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

  • Check for supply voltage imbalance.

  • Check for supply disturbance (e.g., notching from DC drive).

  • Check motor and cable insulation.

  • Fit an output line reactor or sinusoidal filter.

  • Adjust brake turn on threshold (Pr 06.074).
Option Disable (215)

Option module error
Cause:


Option module does not acknowledge drive mode changeover within the allowed time.



Remedy:



  • Reset the trip.

  • If the trip persists, replace the option module.
Out Phase Loss (98)

Output phase loss detected
Cause:


A phase loss has been detected at the drive output (U, V, or W phase disconnected).



Remedy:



  • Check motor and drive connections.

  • To disable the trip set Output Phase Loss Detection Enable (06.059) = 0.
Over Speed (7)

Motor speed exceeded threshold
Cause:


Motor speed has exceeded the Over Speed Threshold (03.008). Can be caused by control loop overshoot or mechanical driving.



Remedy:



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

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

  • If an SSI encoder is being used, set Pr 03.047 to 1.

  • Enable High Speed Mode (05.022) if flux weakening is required.
Over Volts (2)

DC bus voltage exceeded limit
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 minimum value).

  • Check nominal AC supply level.

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

  • Check motor insulation using an insulation tester.
32
Phase Loss (Supply phase loss)
Cause: Input phase loss or large supply imbalance detected. This can be detected directly from the supply or by monitoring the ripple in the DC bus voltage.



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.

  • Reduce the duty cycle.

  • Reduce the motor load.

  • Disable the phase loss detection, set Pr 06.047 to 2.

  • Check for mechanical resonance with the load.
198
Phasing error
Cause: The phase offset angle in Position Feedback Phase Angle (03.025 or 21.020) is incorrect, or position feedback is being used and the drive is unable to control the motor correctly.



Remedy:

  • Check the encoder wiring.

  • Check the encoder signals for noise with an oscilloscope.

  • Check encoder mechanical coupling.

  • Perform an auto-tune to measure the encoder phase angle or manually enter the correct phase angle into Pr 03.025.

  • Check if Over Speed Threshold (03.008) needs to be set greater than zero for dynamic applications.

  • Ensure motor parameters are set up correctly (if sensorless).

  • Reduce speed controller gains.
90
Power Comms
Cause: A communications problem within the power system of the drive (between Control system, Power module, or Rectifier module).



Remedy:

  • Hardware fault – Contact the supplier of the drive.
220
Power Data
Cause: Error in the configuration data stored in the power system. This can be due to missing data tables, size mismatch, CRC errors, or version mismatch between generator software and table.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
37
Power Down Save
Cause: 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 (Internal power supply fault)
Cause: One or more internal power supply rails are outside limits or overloaded (Control system overload or Rectifier internal overload).



Remedy:

  • Remove any option modules and perform a reset.

  • Remove encoder connection and perform a reset.

  • Hardware fault within the drive – return the drive to the supplier.
9
PSU 24V (24V internal power supply overload)
Cause: The total user load of the drive and option modules has exceeded the internal 24 V power supply limit (drive digital outputs and main encoder supply).



Remedy:

  • Reduce the load and reset.

  • Provide an external 24 V power supply on control terminal 2.

  • Remove all option modules.
223
Rating Mismatch
Cause: Voltage rating or current rating mismatch in a multi-module drive system. Modules connected in parallel must have the same frame size and rating.



Remedy:

  • Ensure that all modules in a multi-modular drive system are of the same frame size and rating (voltage and current).

  • Hardware fault – Contact the supplier of the drive.
94
Rectifier Set-up
Cause: A rectifier has not been set-up correctly in a multi-power module system.



Remedy:

  • Check the inter-power module wiring.
33
Resistance
Cause: Measured stator resistance is too high, or an attempt to measure it failed. Can be caused by values exceeding the VFS/Full Scale Current ratio.



Remedy:

  • Check that the value entered in stator resistance does not exceed 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 = Fixed) and verify output current waveforms.

  • Replace the motor.
216
Slot App Menu
Cause: Application menu Customization conflict error. More than one option slot has requested to customize application menus 18, 19, and 20.



Remedy:

  • Ensure that only one of the Application modules is configured to customize the application menus 18, 19 and 20.
204, 209, 214
SlotX Different
Cause: Option module in option slot X on the drive is a different type to that installed when parameters were last saved on the drive.



Remedy:

  • Turn off the power, ensure the correct option modules are installed in the correct option slots 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, 207, 212
SlotX Error
Cause: The option module in option slot X on the drive has detected an error.



Remedy:

  • See relevant Option Module User Guide for details of the trip.
200, 205, 210
SlotX HF
Cause: Option module X hardware fault. Possible causes include unidentified category, corrupt tables, insufficient memory, or communication failure.



Remedy:

  • Ensure the option module is installed correctly.

  • Replace the option module.

  • Replace the drive.
203, 208, 213
SlotX Not Fitted
Cause: The option module in option slot X 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, 206, 211
SlotX Watchdog
Cause: The option module installed in Slot X has started the option watchdog function and then failed to service the watchdog correctly.



Remedy:

  • Replace the option module.
226
Soft Start
Cause: The Soft Start trip indicates that the soft start relay in the drive failed to close or the soft start monitoring circuit has failed.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
221
Stored HF
Cause: The Stored HF trip indicates that a hardware trip (HF01 – HF19) has occurred and the drive has been power cycled. The sub-trip number identifies the HF trip.



Remedy:

  • Enter 1299 in Pr mm.000 and press reset to clear the trip.
227
Sub-array RAM
Cause: The Sub-array RAM trip indicates that an option module, derivative image or user program image has requested more parameter RAM than is allowed. The failure with the highest sub-trip number is given.



Remedy:

  • Check RAM allocation settings.

  • Review option module or user program requirements.
218
Temp Feedback
Cause: An internal thermistor has failed. The thermistor location can be identified by the sub-trip number (e.g., Control board thermistor, I/O board thermistor).



Remedy:

  • Hardware fault – Contact the supplier of the drive.
10
Th Brake Res
Cause: The Th Brake Res is initiated if hardware based braking resistor thermal monitoring is connected and the resistor overheats.



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: This trip indicates that a temperature sensor connected to an analogue input or terminal 15 has a low impedance (i.e. < 50 Ω).



Remedy:

  • Check thermistor continuity.

  • Replace motor / motor thermistor.
24
Thermistor
Cause: The motor thermistor connected to terminal 8 (analog input 3) or terminal 15 (encoder) has indicated a motor over temperature.



Remedy:

  • Check motor temperature.

  • Check threshold level (07.048).

  • Check thermistor continuity.
110
Undefined
Cause: The Undefined trip indicates that the power system has generated but did not identify the trip. The cause is unknown.



Remedy:

  • Hardware fault – return the drive to the supplier.
91
User 24V
Cause: A User 24 V trip is initiated if User Supply Select is set to 1 or Low Under Voltage Threshold Select = 1 and no user 24 V supply is present on control terminals 1 and 2.



Remedy:

  • Ensure the user 24 V supply is present on control terminals 1 (0V) and 2 (24 V).
249
User Program
Cause: An error has been detected in the onboard user program image. The reason can be identified by the sub-trip number (e.g., Divide by zero, Undefined trip, RAM allocation error).



Remedy:

  • Check the user program code for errors corresponding to the sub-trip.

  • Ensure option modules are compatible.
96
User Prog Trip
Cause: This trip can be initiated from within an onboard user program using a function call which defines the sub-trip number.



Remedy:

  • Check the user program.
36
User Save
Cause: An error has been detected in the user save parameters (e.g., power removed during save).



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.
41-89
112-159
User Trip
Cause: 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: The control word watchdog 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.

  • Re-enable if required when the trip is reset.
HF01 to HF20
Internal / Hardware trips
Cause: Internal faults that do not have trip numbers. The main drive processor has detected an irrecoverable error.


Remedy:

  • Power cycle the drive (if non-permanent trip).

  • On power up, if the drive trips on “Stored HF”: Enter 1299 in mm.000 to clear the Stored HF trip.
Error 1
Programming Error
Cause: There is not enough drive memory requested by all the option modules.


Remedy:

  • Power down drive and remove some of the option modules until the message disappears.
Error 2
Programming Error
Cause: At least one option module did not acknowledge the reset request.


Remedy:

  • Power cycle drive.
Error 3
Programming Error
Cause: The boot loader failed to erase the processor flash.


Remedy:

  • Power cycle drive and try again.

  • If problem persists, return drive.
Error 4
Programming Error
Cause: The boot loader failed to program the processor flash.


Remedy:

  • Power cycle drive and try again.

  • If problem persists, return drive.
Error 5
Programming Error
Cause: One option module did not initialize correctly. Option module did not set Ready to Run flag.


Remedy:

  • Remove faulty option module.
Motor Overload
Alarm
Cause: Motor Protection Accumulator (04.019) in the drive has reached 75.0 % of the value at which the drive will trip and the load on the drive is >100 %.


Remedy:

  • Check motor load and operating conditions to prevent a trip.
Drive Overload
Alarm
Cause: Drive over temperature. Percentage Of Drive Thermal Trip Level (07.036) in the drive is greater than 90 %.


Remedy:

  • Check drive cooling and ambient temperature.
Auto Tune
Alarm
Cause: The autotune procedure has been initialized and an autotune in progress.


Remedy:

  • Wait for the autotune process to complete.