Nidec Control Techniques Digitax HD M751 Base Servo Drive

Nidec Control Techniques Digitax HD M751 Base Servo Drive Fault Codes:

Fault Code and MeaningCause and Remedy
217
App Menu Changed

Customization table for an application module has changed
Cause:


The App Menu Changed trip indicates that the customization table for an application menu has changed. The menu that has been changed can be identified by the sub-trip number. If more than one menu has changed the lowest menu has priority. Drive user parameters must be saved to prevent this trip on the next power-up.



Remedy:



  • Reset the trip and perform a parameter save to accept the new settings.
11
Autotune 1

Position feedback did not change or required speed could not be reached
Cause:


The drive has tripped during an autotune. The cause of the trip can be identified from the sub-trip number (e.g., motor did not reach required speed, commutation signal not found, etc.).



Remedy:



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

  • Ensure Pr 03.026 and Pr 03.038 are set correctly (or appropriate 2nd motor map parameters).

  • Check feedback device wiring is correct.

  • Check encoder mechanical coupling to the motor.
12
Autotune 2

Position feedback direction incorrect
Cause:


The drive has tripped during a rotating autotune. The position feedback direction is incorrect when position feedback is being used, or a SINCOS encoder comms position is rotating in the opposite direction to the sine wave.



Remedy:



  • Check motor cable wiring is correct.

  • Check feedback device wiring is correct.

  • Swap any two motor phases.
13
Autotune 3

Measured inertia has exceeded the parameter range or commutation signals changed in wrong direction
Cause:


The drive has tripped during a rotating autotune or mechanical load measurement test. Measured inertia may have exceeded parameter range, or commutation signals changed in the wrong direction.



Remedy:



  • Check motor cable wiring is correct.

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

  • Increase the test level.

  • If the test was carried out at standstill repeat the test with the motor rotating within the recommended speed range.
14
Autotune 4

Drive encoder U commutation signal fail
Cause:


A position feedback device with commutation signals is being used and the U commutation signal did not change during a rotating autotune.



Remedy:



  • Check feedback device U commutation signal wiring is correct (Encoder terminals 7 and 8).
15
Autotune 5

Drive encoder V commutation signal fail
Cause:


A position feedback device with commutation signals is being used and the V commutation signal did not change during a rotating autotune.



Remedy:



  • Check feedback device V commutation signal wiring is correct (Encoder terminals 9 and 10).
16
Autotune 6

Drive encoder W commutation signal fail
Cause:


A position feedback device with commutation signals is being used and the W commutation signal did not change during a rotating autotune.



Remedy:



  • Check feedback device W commutation signal wiring is correct (Encoder terminals 11 and 12).
17
Autotune 7

Motor number of poles / position feedback resolution set incorrectly
Cause:


An Autotune 7 trip is initiated during a rotating autotune, if the motor poles or the position feedback resolution have been set up incorrectly where position feedback is being used.



Remedy:



  • Check line per revolution for feedback device.

  • Check the number of poles in Pr 05.011.
18
Autotune Stopped

Autotune test stopped before completion
Cause:


The drive was prevented from completing an autotune test, because either the drive enable or the drive run were removed.



Remedy:



  • Check the drive enable signal (terminals 2 & 6) were 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 (I2t)
Cause:


The Brake R Too Hot indicates that braking resistor overload has timed out. The Brake R Too Hot 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 the braking resistor software overload protection is not required, set Pr 10.030, Pr 10.031 or Pr 10.061 to 0 to disable the trip.
99
CAM

Advanced motion controller CAM failure
Cause:


The CAM trip indicates that the advanced motion controller CAM has detected a problem. Causes include: Start Index > Cam Size, CAM Index change > 2 in one sample, or rate of change at segment boundary exceeded maximum.



Remedy:



  • Check CAM parameters and definitions (Pr 35.001, 35.002, 35.003, 35.007, 35.008).
185
Card Access

SD Card Write fail
Cause:


The drive was unable to access the SD Card. If a parameter file is transferred to the drive and this trip occurs during the transfer, the parameters are not saved to non-volatile memory.



Remedy:



  • Check SD Card is installed / located correctly.

  • Replace the SD Card.
177
Card Boot

The Menu 0 parameter modification cannot be saved to the SD Card
Cause:


A write to a Menu 0 parameter has been initiated via the keypad by exiting edit mode and Pr 11.042 is set for auto or boot mode, but the necessary boot file has not been created on the SD Card.



Remedy:



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

  • Re-attempt the parameter write to the Menu 0 parameter.
178
Card Busy

SD Card cannot be accessed as it is being accessed by an option module
Cause:


An attempt has been made to access a file on SD Card, but the SD Card is already being accessed by an Option Module. No data is transferred.



Remedy:



  • Wait for the option module to finish accessing the SD Card and re-attempt the required function.
188
Card Compare

SD Card file/data is different to the one in the drive
Cause:


A compare has been carried out between a file on the SD Card and the drive. A Card Compare trip is initiated if the parameters on the SD Card are different to the drive.



Remedy:



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

  • Check to ensure the correct data block on the SD Card has been used for the compare.
179
Card Data Exists

SD Card data location already contains data
Cause:


An attempt has been made to store data on an SD Card in a data block which already contains data. No data is transferred.



Remedy:



  • Erase the data in data location.

  • Write data to an alternative data location.
187
Card Drive Mode

SD Card parameter set not compatible with current drive mode
Cause:


Produced during a compare if the drive mode in the data block on the SD Card is different from the current drive mode. Also produced if transferring parameters from SD Card when the operating mode in the data block is outside the 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

SD Card data structure error
Cause:


An attempt has been made to access an SD Card but an error has been detected in the data structure on the card (e.g. required folder not present, file corrupted).



Remedy:



  • Erase all the data blocks and re-attempt the process.

  • Ensure the card is located correctly.

  • Replace the SD Card.
184
Card Full

SD Card full
Cause:


An attempt has been made to create a data block on an SD Card, but there is not enough space left on the card.



Remedy:



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

  • Use a different SD Card.
183
Card No Data

SD Card data not found
Cause:


An attempt has been made to access non-existent file or block on an SD Card. No data is transferred.



Remedy:



  • Ensure data block number is correct.
180
Card Option

SD Card trip; option modules installed are different between source drive and destination drive
Cause:


Parameter data or default difference data is being transferred from an SD Card to the drive, but the option module categories are different between source and destination drives. This acts as a warning.



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 that the parameters for one or more of the option modules 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

SD Card data blocks are not compatible with the drive derivative
Cause:


If Drive Derivative (11.028) or Product Type (11.063) are different between the source and target drives then this trip is initiated either at power-up or when the card is accessed.



Remedy:



  • Use a different SD Card.

  • This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
186
Card Rating

SD Card Trip; The voltage and / or current rating of the source and destination drives are different
Cause:


Parameter data is being transferred from an SD Card to the drive, but the current and / or voltage ratings are different between source and destination drives.



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

SD Card has the Read Only bit set
Cause:


An attempt has been made to modify a read-only SD Card or a read-only data block.



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 SD Card.
174
Card Slot

SD Card Trip; Option module application program transfer has failed
Cause:


Initiated if the transfer of an option module application program to or from an application module failed because the option module does not respond correctly.



Remedy:



  • Ensure the source / destination option module is installed on the correct slot.
35
Control Word

Trip initiated from the Control Word (06.042)
Cause:


The Control Word trip is initiated by setting bit 12 on the control word in Pr 06.042 when the control word is enabled (Pr 06.043 = On).



Remedy:



  • Check the value of Pr 06.042.

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

  • When the control word is enabled, the trip can only be cleared by setting bit 12 to zero.
225
Current Offset

Current feedback offset error
Cause:


The current feedback offset is too large to be trimmed correctly. The sub-trip relates to the output phase for which the offset error has been detected (1=U, 2=V, 3=W).



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

Drive parameters are being changed
Cause:


A user action or a file system write is active that is changing the drive parameters and the drive has been commanded to enable. This includes loading defaults, changing drive mode, or transferring data from SD 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 SD Card or position feedback device

    • Transferring user programs
247
Derivative identification error
Cause: There is a problem with the identifier associated with derivative image which customizes the drive. Sub-trips indicate: Image erased, Identifier out of range, or Image changed.



Remedy:

  • Contact the supplier of the drive.
248
Derivative Image error
Cause: An error has been detected in the derivative image. Sub-trip numbers indicate specific option module slot conflicts or missing modules required by the image.



Remedy:

  • Contact the supplier of the drive.
199
Destination parameters write conflict
Cause: Destination parameters of two or more functions (Menus 3, 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.
224
Power stage recognition: Unrecognized drive size
Cause: The control PCB has not recognized the drive size of the power circuit to which it is connected.



Remedy:

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

  • Hardware fault – return drive to supplier.
31
EEPROM Fail (Default parameters loaded)
Cause: Default parameters have been loaded. Possible causes include: Internal parameter database version changed, CRC failure, Mode restored from non-volatile memory outside allowed range, Hardware changes (I/O, Power stage), or EEPROM Checksum failure.



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.
189
Encoder 1: Drive position feedback interface power supply overload
Cause: The drive encoder power supply has been overloaded (Terminals 13 & 14). Maximum current exceeded (200 mA @ 15V or 300 mA @ 8V/5V).



Remedy:

  • Check encoder power supply wiring.

  • Disable the termination resistors (Pr 03.039 set to 0) to reduce current consumption.

  • For 5 V encoders with long cables, select 8 V (Pr 03.036) and install a 5 V voltage regulator close to the encoder.

  • Check the encoder specification to confirm if it is compatible with the encoder port power supply current capability.

  • Replace the encoder.

  • Use an external power supply with higher current capability.
190
Encoder 2: Drive encoder (Feedback) wire break
Cause: The drive has detected a wire break on the 15 way D-type connector. Sub-trips indicate specific input or channel (A, B, Z) failures.



Remedy:

  • Ensure that the position feedback device type selected in Pr 03.038 is correct for the position feedback device connected to the P1 interface.

  • If wire break detection is not required, set Pr 03.040 = XXX0 to disable the Encoder 2 trip.

  • Check cable continuity.

  • Check wiring of feedback signals is correct.

  • Check encoder power supply is set correctly (Pr 03.036).

  • Replace encoder.
191
Encoder 3: Phase offset incorrect while running
Cause: Incorrect UVW phase angle (RFC-S mode) or SINCOS phase error detected while running.



Remedy:

  • Check encoder shield connections.

  • Ensure the encoder cable is one uninterrupted cable.

  • Check the encoder signal for noise with an oscilloscope.

  • Check the integrity of the encoder mechanical mounting.

  • For a UVW servo encoder, ensure that the phase rotation of the UVW commutation signals is the same as the phase rotation of the motor.

  • For a SINCOS encoder, ensure that motor and incremental SINCOS connections are correct and that for forward rotation of the motor, the encoder rotates clockwise.

  • Repeat the offset measurement test.
192
Encoder 4: Feedback device comms failure
Cause: Encoder communications timed out or message transfer time is too long. Can be caused by wire break in comms channel.



Remedy:

  • Ensure the encoder power supply setting (Pr 03.036) is correct.

  • Complete encoder auto-configuration (Pr 03.041).

  • Check the encoder wiring.

  • Replace the feedback device.
193
Encoder 5: Checksum or CRC error
Cause: Checksum or CRC error, or the SSI encoder is not ready. Can also indicate a wire break to a communications based encoder.



Remedy:

  • Check the encoder cable shield connections.

  • Ensure the cable is one uninterrupted cable – remove any connector blocks or if unavoidable minimise the length of any shield pigtails.

  • Check the encoder signal for noise with an oscilloscope.

  • Check the comms resolution setting (Pr 03.035).

  • If using a Hiperface, EnDat encoder carry out an encoder auto-configuration (Pr 03.041 = Enabled).

  • Replace the encoder.
194
Encoder 6: Encoder has indicated an error
Cause: The encoder has indicated an error or the power supply has failed to an SSI encoder. Can also indicate a wire break to an SSI encoder.



Remedy:

  • For SSI encoders, check the wiring and encoder power supply setting (Pr 03.036).

  • Replace the encoder / contact the supplier of the encoder.
195
Encoder 7: Set-up parameters changed
Cause: The set-up parameters for position feedback device have changed.



Remedy:

  • Reset the trip and perform a save.

  • Ensure Pr 3.033 and Pr 03.035 are set correctly or carry out an encoder auto-configuration (Pr 03.041 = Enabled).
196
Encoder 8: Position feedback interface timed out
Cause: Position feedback interface communications time exceeds 250 µs.



Remedy:

  • Ensure the encoder is connected correctly.

  • Ensure that the encoder is compatible.

  • Increase baud rate.
197
Encoder 9: Invalid feedback source selection
Cause: Position feedback source selected in Pr 03.026 (or Pr 21.021) is not valid (option module slot does not have a feedback option module installed).



Remedy:

  • Check the setting of Pr 03.026 (or Pr 21.021 if the second motor parameters have been enabled).

  • Ensure that the option slot selected in Pr 03.026 has a feedback option module installed.
162
Encoder 12: Encoder type not recognized
Cause: The drive is communicating with the encoder but the encoder type is not recognized during auto-configuration.



Remedy:

  • Enter the encoder setup parameters manually.

  • Check to see the encoder supports auto-configuration.
163
Encoder 13: Data read out of range
Cause: Data read from the encoder is out of range during auto-configuration. Sub-trips indicate: Rotary lines error, comms pitch error, line pitch error, rotary turns bits error, comms bits error, or calculation/line delay time too long.



Remedy:

  • Enter the encoder setup parameters manually.

  • Check to see the encoder supports auto-configuration.
6
External Trip initiated
Cause: An External Trip has occurred. Can be initiated by Safe Torque Off inputs or by writing a value of 6 in Pr 10.038.



Remedy:

  • Check the Safe Torque Off signal voltage (on terminals 2 & 6) equals to 24 V.

  • Check the value of Pr 08.009 which indicates the digital state of terminals 2 & 6.

  • If external trip detection of STO input 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: A CPU address error has occurred. The control PCB on the drive has failed.



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 on the drive 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 on the drive 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 on the drive 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 on the drive 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 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. 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. 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: The HF09 trip indicates that 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.
HF10

Data processing error: Parameter routing system error
Cause: The HF10 trip indicates that a Parameter routing system error 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: Access to EEPROM failed
Cause: The HF11 trip indicates that access to the drive EEPROM has failed. This trip indicates that the control PCB on the drive has failed.



Remedy:

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

Data processing error: Main program stack overflow
Cause: The HF12 trip indicates that the main program stack overflow has occurred. The stack can be identified by the sub-trip number (1: Background, 2: Timed, 3: Main system).



Remedy:

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

Data processing error: Firmware incompatible with hardware
Cause: The HF13 trip indicates that the drive firmware is not compatible with the hardware.



Remedy:

  • Re-program the drive with the latest version of the drive firmware for Digitax HD M751.

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

Data processing error: CPU register bank error
Cause: The HF14 trip indicates that a CPU register bank error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:

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

Data processing error: CPU divide error
Cause: The HF15 trip indicates that a CPU divide error has occurred.



Remedy:

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

Data processing error: RTOS error
Cause: The HF16 trip indicates that a RTOS error has occurred.



Remedy:

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

Data processing error: Clock supplied to the control board is out of specification
Cause: The HF17 trip indicates that the clock supplied to the control board logic is out of specification.



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. Sub-trips: 1 (Programming error), 2 (Erase setup menu failed), 3 (Erase application menu failed).



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.



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.



Remedy:

  • If this trip occurs please consult the drive supplier.
Inductance
Trip 8

Inductance measurement out of range or motor saturation not detected
Cause: Occurs in RFC-S mode when motor inductances are not suitable or saturation characteristic cannot be measured.



Remedy:

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

  • Sub-trip 3: None. The trip acts as a warning regarding location of motor flux or small inductance.

  • Sub-trip 4: Stationary autotune is not possible. Perform a minimal movement or rotating autotune. Use a position feedback device with commutation signals or absolute position.
I/O Overload
Trip 26

Digital output overload
Cause: Total current drawn from 24 V user supply or from the digital output has exceeded the limit (>100 mA).



Remedy:

  • Check total loads on digital outputs.

  • Check control wiring is correct.

  • Check output wiring is undamaged.
Keypad Mode
Trip 34

Keypad has been removed when the drive is receiving the speed reference from the keypad
Cause: Drive is in keypad mode [Reference Selector = 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.
Motor Too Hot
Trip 20

Output current overload timed out (I²t)
Cause: Motor thermal overload based on Rated Current and Motor Thermal Time Constant. Drive trips when thermal 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 Rated Current is ≤ Heavy duty current rating.

  • Tune the Rated Speed (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 name plate transfer between drive and motor failed. Sub-trips: 1 (Not enough memory), 2 (Communication failed), 3 (Transfer failed), 4 (Checksum failed).



Remedy:

  • Ensure device encoder memory has at least 128 bytes to store nameplate data.

  • Ensure option slot has a feedback option module installed.

  • Check if the encoder has been initialized in 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 via thermistors on Control board or I/O board.



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
Trip 27

DC bus over temperature
Cause: DC bus component over temperature based on software thermal model. Causes include high output current or DC bus ripple.



Remedy:

  • Check the AC supply voltage balance and levels.

  • Check DC bus ripple level.

  • Reduce duty cycle or motor load.

  • Check output current stability.

  • Check motor map settings.

  • Disable slip compensation or dynamic V to F if necessary.

  • Check encoder signals for noise.
OHt Inverter
Trip 21

Inverter over temperature based on thermal model
Cause: IGBT junction over-temperature detected based on software thermal model.



Remedy:

  • Reduce the selected drive switching frequency.

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

  • Reduce duty cycle or motor load.

  • Increase acceleration / deceleration rates.

  • 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. The thermistor location indicating the over-temperature is identified by the sub-trip.



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 (Pr 02.006).

  • Reduce motor load.

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

  • Use a drive with larger current / power rating.
OI ac (3)

Instantaneous output over current detected
Cause:

The instantaneous drive output current has exceeded VM_DRIVE_CURRENT[MAX]. This trip cannot be reset until 10s after the trip was initiated.



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 the motor insulation using an insulation tester.

  • Check feedback device wiring and mechanical coupling.

  • Check feedback signals are free from noise.

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

  • Reduce the values in the speed loop gain parameters.

  • Has the phase angle autotune been completed? (RFC-S mode only).

  • Reduce the values in current loop gain parameters (RFC-A, RFC-S modes only).
OI Brake (4)

Braking IGBT over current detected
Cause:

Short circuit protection for the braking IGBT 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 detected from IGBT on state voltage monitoring
Cause:

The short circuit protection for the drive output stage has been activated. This trip cannot be reset until 10s after the trip was initiated.



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 detected
Cause:

An over-current condition has been detected in the rectifier snubber 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.

  • Install an output line reactor or sinusoidal filter.
Option Disable (215)

Option module does not acknowledge during drive mode changeover
Cause:

The option module did not acknowledge to the drive that communications with the drive has been stopped during the drive mode changeover within the allocated time.



Remedy:

  • Reset the trip.

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

Output phase loss detected
Cause:

Phase loss has been detected at the drive output.



Remedy:

  • Check motor and drive connections.

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

Motor speed has exceeded the over speed threshold
Cause:

The Output Frequency or Speed Feedback exceeds the threshold set in Over Speed Threshold.



Remedy:

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

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

  • If an SSI encoder is being used set Pr 03.047 to 1.
Over Volts (2)

DC bus voltage has exceeded the peak level or maximum continuous level
Cause:

The DC bus voltage has exceeded the VM_DC_VOLTAGE[MAX] limits.



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.
Phase Loss (32)

Supply phase loss
Cause:

Input phase loss or large supply imbalance detected from the supply or DC bus ripple monitoring.



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.
Phasing Error (198)

RFC-S mode phasing failure due to incorrect phase angle
Cause:

The phase offset angle in Pr 03.025 is incorrect, 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 the encoder mechanical coupling.

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

  • Ensure that the motor parameters are set-up correctly.

  • Reduce the speed controller gains.
Power Comms (90)

Communication has been lost / errors detected between power, control and rectifier
Cause:

A communications problem within the power system of the drive.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
Power Data (220)

Power system configuration data error
Cause:

There is an error in the configuration data stored in the power system.



Remedy:

  • Hardware fault – Contact the supplier of the drive.
Power Down Save (37)

Power down save error
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.
PSU (5)

Internal power supply fault
Cause:

One or more internal power supply rails are outside limits or overloaded.



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.
PSU 24V (9)

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.



Remedy:

  • Reduce the load and reset.

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

  • Remove all option modules.
Resistance (33)

Measured resistance has exceeded the parameter range
Cause:

Either the value being used for motor stator resistance is too high or an attempt to do a test involving measuring motor stator resistance has failed.



Remedy:

  • Check that the value that has been entered in the stator resistance does not exceed the allowed range.

  • Check the motor cable / connections.

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

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

  • Ensure the stator resistance of the motor falls within the range of the drive model.

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

  • Replace the motor.
216
Slot App Menu
Cause:

The Slot App Menu trip indicates that more than one option slot has requested to customize the application menus 18, 19 and 20. The sub-trip number indicates which option slot has been allowed to customize the menus.



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:

The SlotX Different trip indicates that the 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 SlotX Error trip indicates that the option module in option slot X on the drive has detected an error. The reason for the error can be identified by the sub-trip number.



Remedy:

  • See the relevant Option Module User Guide for details of the trip.
200, 205, 210
SlotX HF
Cause:

The SlotX HF trip indicates that the option module in option slot X cannot operate. The possible causes of the trip can be identified by the sub-trip number (e.g., module category not identified, tables corrupt, etc.).



Remedy:

  • Ensure the option module is installed correctly.

  • Replace the option module.

  • Replace the drive.
203, 208, 213
SlotX Not Fitted
Cause:

The SlotX Not Fitted trip indicates that the option module in option slot X on the drive 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 SlotX Watchdog trip indicates that 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 – HF20) has occurred and the drive has been power cycled. The sub-trip number identifies the HF trip i.e. stored HF.17.



Remedy:

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

The Sub-array RAM indicates that an option module, derivative image or user program image has requested more parameter RAM than is allowed. The failure is detailed by the sub-trip number.



Remedy:

  • Check parameter RAM allocation size and type requested by modules or programs.
218
Temp Feedback
Cause:

The Temp Feedback trip indicates that an internal thermistor has failed. The thermistor location can be identified by the sub-trip number.



Remedy:

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

Brake resistor over temperature. 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:

The Th Short Circuit trip indicates that the motor thermistor connected to the drive is short circuit or low impedance i.e. < 50 Ω.



Remedy:

  • Check thermistor continuity.

  • Replace motor / motor thermistor.
24
Thermistor
Cause:

The Thermistor trip indicates that the motor thermistor connected to the drive has indicated a motor over temperature.



Remedy:

  • Check motor temperature.

  • Check P1 Thermistor Trip Threshold (03.120).

  • Check thermistor continuity.
110
Undefined
Cause:

The Undefined trip indicates that the power system has generated but did not identify the trip from the power system. The cause of the trip is unknown.



Remedy:

  • Hardware fault – return the drive to the supplier.
249
User Program
Cause:

The User Program trip indicates that an error has been detected in the onboard user program image. The reason for the trip can be identified by the sub-trip number (e.g., Divide by zero, Undefined trip, Parameter access errors).



Remedy:

  • Check the user program code and parameters.
96
User Prog Trip
Cause:

Trip generated by an onboard user program. This trip can be initiated from within an onboard user program using a function call.



Remedy:

  • Check the user program.
36
User Save
Cause:

User Save error / not completed. The trip indicates an error detected in the user save parameters saved in non-volatile memory (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.
40-89, 112-159
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 1 s 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.
Error 1

Insufficient Drive Memory
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

Option Module Reset Failure
Cause: At least one option module did not acknowledge the reset request.



Remedy: Power cycle drive.
Error 3

Flash Erase Failed
Cause: The boot loader failed to erase the processor flash.



Remedy: Power cycle drive and try again. If problem persists, return drive.
Error 4

Flash Program Failed
Cause: The boot loader failed to program the processor flash.



Remedy: Power cycle drive and try again. If problem persists, return drive.
Error 5

Option Module Init Failed
Cause: One option module did not initialize correctly. Option module did not set Ready to Run flag.



Remedy: Remove faulty option module.
Brake Resistor

Brake resistor overload
Cause: Braking Resistor Thermal Accumulator (10.039) in the drive has reached 75.0 % of the value at which the drive will trip.



Remedy: Check braking cycle and load. (Alarm indicates impending trip).
Motor Overload

Motor protection warning
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 duty cycle.
Ind Overload

Regen inductor overload
Cause: Inductor 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: Reduce load on the drive.
Drive Overload

Drive over temperature
Cause: Percentage Of Drive Thermal Trip Level (07.036) in the drive is greater than 90 %.



Remedy: Check drive cooling and ambient temperature.
Auto Tune

Autotune in progress
Cause: The autotune procedure has been initialized and an autotune is in progress.



Remedy: Wait for autotune to complete.
Limit Switch

Limit switch active
Cause: Indicates that a limit switch is active and that is causing the motor to be stopped.



Remedy: Check system limit switches.
Inhibit

Drive Inhibited
Cause: The Safe Torque Off signal is not applied to Safe Torque Off terminals or Pr 06.015 is set to 0.



Remedy: Apply STO signal or check parameters to enable. (Output Stage: Disabled).
Ready

Drive Ready
Cause: The drive enable is active, but the drive inverter is not active because the final drive run is not active.



Remedy: Activate run command. (Output Stage: Disabled).
Stop

Stopped
Cause: The drive is stopped / holding zero speed.



Remedy: Normal operation. (Output Stage: Enabled).
Run

Running
Cause: The drive is active and running.



Remedy: Normal operation. (Output Stage: Enabled).
Scan

Regen Synchronization
Cause: The drive is enabled in Regen mode and is trying to synchronize to the supply.



Remedy: Wait for synchronization. (Output Stage: Enabled).
Supply Loss

Supply Loss Detected
Cause: Supply loss condition has been detected.



Remedy: Check input power supply. (Output Stage: Enabled).
Deceleration

Decelerating
Cause: The motor is being decelerated to zero speed / frequency because the final drive run has been deactivated.



Remedy: Normal operation. (Output Stage: Enabled).
dc injection

DC Injection Braking
Cause: The drive is applying dc injection braking.



Remedy: Normal operation. (Output Stage: Enabled).
Position

Position Control Active
Cause: Positioning / position control is active during an orientation stop.



Remedy: Normal operation. (Output Stage: Enabled).
Trip

Drive Tripped
Cause: The drive has tripped and no longer controlling the motor.



Remedy: Check the trip code appearing in the lower display. (Output Stage: Disabled).
Active

Regen Active
Cause: The regen unit is enabled and synchronized to the supply.



Remedy: Normal operation. (Output Stage: Enabled).
Under Voltage

Under Voltage State
Cause: The drive is in the under voltage state either in low voltage or high voltage mode.



Remedy: Check DC bus voltage and supply. (Output Stage: Disabled).
Heat

Pre-heat Active
Cause: The motor pre-heat function is active.



Remedy: Normal operation. (Output Stage: Enabled).
Phasing

Phasing Test
Cause: The drive is performing a ‘phasing test on enable’.



Remedy: Wait for test completion. (Output Stage: Enabled).