Nidec & Control Technique Unidrive HS70 Drive

Nidec & Control Technique Unidrive HS70 Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
28 An Input 1 Loss	Cause: Analog input 1 current loss (Unidrive HS70 / HS71). This trip indicates that a current loss was 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). Current signal is present and greater than 3 mA.
29 An Input 2 Loss	Cause: Analog input 2 current loss (Unidrive HS70 / HS71). This trip indicates that a current loss was 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). Current signal is present and greater than 3 mA.
219 An Output Calib	Cause: Analog output calibration failed (Unidrive HS70 / HS71). One or both of the Analog outputs have failed during the zero offset calibration. Sub-trip Reason 1 Output 1 failed (Terminal 9) 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 the calibration. If trip persists replace the drive.
217 App Menu Changed	Cause: Customization table for an application module has changed. The menu that has been changed can be identified by the sub-trip number. Sub-trip Reason 1 Menu 18 2 Menu 19 3 Menu 20 Remedy: Reset the trip and perform a parameter save to accept the new settings.
11 Autotune 1	Cause: Position feedback did not change or required speed could not be reached. The drive has tripped during an autotune. Sub-trip Reason 1 The position feedback did not change when position feedback is being used during rotating autotune. 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 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	Cause: Position feedback direction incorrect. The drive has tripped during a rotating autotune. Sub-trip Reason 1 The position feedback direction is incorrect when position feedback is being used during a rotating autotune. 2 The motor did not reach the required speed during rotating autotune or mechanical load measurement. Remedy: Check motor cable wiring is correct. Check feedback device wiring is correct. Swap any two motor phases.
13 Autotune 3	Cause: Measured inertia has exceeded the parameter range or commutation signals changed in wrong direction. The drive has tripped during a rotating autotune or mechanical load measurement test. Sub-trip Reason 1 Measured inertia has exceeded the parameter range during a mechanical load measurement. 2 The commutation signals changed in the wrong direction during a rotating autotune. 3 The mechanical load test has been unable to identify the motor inertia. Remedy: Check motor cable wiring is correct. Check feedback device U,V and W commutation signal wiring is correct.
14 Autotune 4	Cause: Drive encoder U commutation signal fail. 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	Cause: Drive encoder V commutation signal fail. 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	Cause: Drive encoder W commutation signal fail. 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	Cause: Motor number of poles / position feedback resolution set incorrectly. 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	Cause: Autotune test stopped before completion. 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 (terminal 31 on Unidrive HS70 / HS71 and terminal 11 & 13 on Unidrive HS72) was active during the autotune. Check the run command was active in Pr 08.005 during autotune.
19 Brake R Too Hot	Cause: Braking resistor overload timed out (I²t). The 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	Cause: Advanced motion controller CAM failure. The advanced motion controller CAM has detected a problem. Sub-trip Reason 1 CAM index or segment is out of range. 2 AMC CAM Index (35.007) has been made to change by more than 2 in one sample. Remedy: Refer to specific CAM troubleshooting documentation.
185 Card Access	Cause: NV Media Card Write fail. The drive was unable to access the NV Media Card. If the trip occurs during data transfer, the file may be corrupted or incomplete. Remedy: Check NV Media Card is installed / located correctly. Replace the NV Media Card.
177 Card Boot	Cause: The Menu 0 parameter modification cannot be saved to the NV Media Card. This occurs when Pr 11.042 is changed to Auto (3) or Boot (4) mode, but the drive is not subsequently 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	Cause: NV Media Card cannot be accessed as it is being accessed by an option module. No data is transferred. Remedy: Wait for the option module to finish accessing the NV Media Card and re-attempt the required function.
179 Card Data Exists	Cause: NV Media Card data location already contains data. An attempt has been made to store data on a 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.
188 Card Compare	Cause: NV Media Card file/data is different to the one in the drive. A compare has been carried out and 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.
187 Card Drive Mode	Cause: NV Media Card parameter set not compatible with current drive mode. The drive mode in the data block on the NV Media Card 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. An error has been detected in the data structure on the card. Sub-trip Reason 1 The required folder and file structure is not present. 2 The HEADER.DAT file is corrupted. 3 Two or more files in the GT8DATA\DRIVE folder have the same file identification number. 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. An attempt has been made to create a data block on a NV Media Card, but there is 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. An attempt has been made to access non-existent file or block on a NV Media Card. Remedy: Ensure data block number is correct.
180 Card Option	Cause: NV Media Card trip; option modules installed are different between source drive and destination drive. The option module categories are different, or option module data values are different to default values. 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	Cause: NV Media Card data blocks are not compatible with the drive derivative. The Drive Derivative (11.028) is different between the source and target drives. 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	Cause: NV Media Card Trip; 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.
181 Card Read Only	Cause: NV Media Card has the Read Only bit set. An attempt has been made to modify a read-only NV Media 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 NV Media Card.
174 Card Slot	Cause: The Card Slot trip is 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. If this happens this trip is produced with the sub-trip indicating the option module slot number. Remedy: Ensure the source / destination option module is installed on the correct slot
111 Configuration	Cause: The Configuration trip indicates that the Number Of Power Modules Detected (11.071) does not match the previous value stored. Remedy: Ensure that all the power modules are correctly connected / simultaneously 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
35 Control Word	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). Bit 12 of the control word set to a one causes the drive to trip. When the control word is enabled, the trip can only be cleared by setting bit 12 to zero.
225 Current Offset	Cause: The Current Offset trip indicates that 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: A user action or a file system write is active that is changing the drive parameters and the drive has been commanded to enable, i.e. Drive Active (10.002) = 1. 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: The derivative image which customizes the drive has been changed for an image with a different identifier. Remedy: Contact the supplier of the drive
248 Derivative Image	Cause: The Derivative Image trip indicates that an error has been detected in the derivative image. Remedy: Contact the supplier of the drive
199 Destination	Cause: The Destination trip indicates that destination output parameters of two or more logic 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 Drive Size	Cause: The Drive Size trip indicates that 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	Cause: The EEPROM Fail trip indicates that default parameters have been loaded. The exact cause/reason of the trip can be identified from the sub-trip number (e.g., parameter database version changed, CRC error, drive mode outside allowed range, derivative image changed, hardware changes, checksum failed). 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	Cause: The Encoder 1 trip indicates that the drive encoder power supply has been overloaded. Terminals 13 & 14 of the 15 way D type connector can supply a maximum current of 200 mA @ 15 V or 300 mA @ 8 V and 5 V. 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	Cause: The Encoder 2 trip indicates that the drive has detected a wire break on the 15 way D-type connector on the drive. The exact cause can be identified from the sub-trip number (Break on input, A/B/Z channel). Remedy: If wire break detection on the drive encoder input 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	Cause: The Encoder 3 trip indicates that the drive has detected an incorrect UVW phase angle while running (RFC-S mode only) or SINCOS phase error. 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 (when looking at the shaft of the encoder) Repeat the offset measurement test
192 Encoder 4	Cause: The Encoder 4 trip indicates that the encoder communications has timed out or the communications position message transfer time is too long. This trip can also be caused due to wire break in the communication channel between the drive and the encoder. 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	Cause: The Encoder 5 trip indicates that there is a checksum or CRC error, or the SSI encoder is not ready. The Encoder 5 trip 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 to the connector block Check the encoder signal for noise with an oscilloscope Check the comms resolution setting (Pr 03.035) If using a Hiperface, EnDat encoder or BiSS encoder carry out an encoder auto-configuration (Pr 03.041 = Enabled) Replace the encoder
194 Encoder 6	Cause: The Encoder 6 trip indicates that the encoder has indicated an error or that the power supply has failed to an SSI encoder. The Encoder 6 trip 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	Cause: The Encoder 7 trip indicates that the set-up parameters for position feedback device has changed. The feedback device which has caused the trip can be identified by the sub-trip number. 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	Cause: The Encoder 8 trip indicates that 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	Cause: The Encoder 9 trip indicates that position feedback source selected in Pr 03.026 (or Pr 21.021 for the second motor map) is not valid. 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	Cause: The Encoder 12 trip indicates that the drive is communicating with the encoder but the encoder type is not recognized. Remedy: Enter the encoder setup parameters manually Check to see the encoder supports auto-configuration
163 Encoder 13	Cause: The Encoder 13 trip indicates that the data read from the encoder was out of the range during auto-configuration. No parameters will be modified with the data read from the encoder as a result of auto configuration. Remedy: Enter the encoder setup parameters manually Check to see the encoder supports auto-configuration
6 External Trip	Cause: An External Trip has occurred. The cause can be identified by the sub-trip: 1: External Trip Mode = 1 or 3 and SAFE TORQUE OFF input 1 is low. 2: External Trip Mode = 2 or 3 and SAFE TORQUE OFF input 2 is low. 3: External Trip (10.032) = 1. Remedy: Check the SAFE TORQUE OFF signal voltage (terminals 31, 11, or 13 depending on model) equals 24 V. Check the value of Pr 08.009 (digital state of terminals). If external trip detection 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.
168 Frequency Range	Cause: Out of range of frequency has been detected in regen mode. Supply frequency is outside the range defined by Regen Minimum/Maximum Frequency for more than 100 ms. Remedy: Ensure the supply is operating within the drive specification. Ensure Pr 03.024 and Pr 03.025 are set correctly. Check the supply voltage waveform using an oscilloscope. Reduce the level of supply disturbance.
HF01 Data processing error: CPU address error	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: DMAC address error	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: Illegal instruction	Cause: An illegal instruction 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: Illegal slot instruction	Cause: An illegal slot instruction has occurred. This trip indicates that 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. This trip indicates that 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. 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.
HF10 Data processing error: Parameter routing system error	Cause: 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: 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: Main program stack overflow. Sub-trips: 1=Freewheeling tasks, 2=Clock tasks, 3=Main system interrupts. 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. 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. 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. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF16 Data processing error: RTOS error	Cause: A RTOS error has occurred. 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: Clock supplied to the control board logic is out of specification. 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-trips indicate specific reason (e.g., Timeout, CRC error, Erase failure). Remedy: Hardware fault – Contact the supplier of the drive.
HF19 Data processing error: CRC check on firmware failed	Cause: 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 not compatible with hardware	Cause: The ASIC version is not compatible with the drive firmware. Remedy: Hardware fault – Contact the supplier of the drive.
8 Inductance	Cause: Inductance measurement out of range or motor saturation not detected. Sub-trip 1: Difference between Ld and No-load Lq is too small. Sub-trip 2: Motor saturation change not detected during direction test. Sub-trip 3: Flux axis location change not detected during stationary auto-tuning. Remedy: Ensure motor inductance and parameters are suitable for the control algorithm. Check Drive rated voltage vs K values (e.g. 200V = 0.037). Note: This type of failure is unlikely in most normal motors.
93 Inductor Too Hot	Cause: The regen inductor has overloaded. Thermal overload based on Rated Current and Thermal Time Constant. Trip occurs when Pr 04.019 gets to 100%. Remedy: Check the load / current through the inductor has not changed. Ensure the Rated Current (Pr 05.007) is not zero.
26 I/O Overload	Cause: Digital output overload. Total current drawn from 24V supply or digital outputs exceeded limits (e.g. >100mA on single output, or combined limits). Remedy: Check total loads on digital outputs. Check control wiring is correct. Check output wiring is undamaged.
160 Island	Cause: Island condition detected in regen mode. AC mains no longer present and inverter would be on ‘islanded’ power supply. Remedy: Check the supply / supply connections to the regen drive.
34 Keypad Mode	Cause: Keypad has been removed when the drive is receiving the speed reference from the keypad. Remedy: Re-install keypad and reset. Change Reference Selector (01.014) to select the reference from another source.
39 Line Sync	Cause: Synchronization to the power supply has been lost in Regen mode. Remedy: Check the supply / supply connections to the regen drive.
38 Low Load	Cause: The load on the drive has fallen below the low load detection level (Pr 04.020 falls below Pr 04.027). Remedy: Check the load on the motor has not changed.
20 Motor Too Hot	Cause: Output current overload timed out (I2t). Motor thermal overload based on output current and thermal time constant. 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 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.
176 Name Plate	Cause: Electronic nameplate transfer has failed. Sub-trips: 1: Not enough memory. 2: Communication failed. 3: Transfer failed. 4: Checksum failed. Remedy: Ensure that the device encoder memory has at least 128 bytes to store the nameplate data. When writing motor object (Pr mm.000 = 11000), ensure device encoder memory has at least 256 bytes. When transferring between option module and encoder, ensure option slot has feedback module installed. Check if the encoder has been initialized in Position Feedback Initialized (03.076). Verify the encoder wiring.
101 OHt Brake (Braking IGBT over-temperature)	Cause: The OHt Brake over-temperature trip indicates that braking IGBT over-temperature has been detected based on software thermal model. Remedy: Check braking resistor value is greater than or equal to the minimum resistance value.
23 OHt Control (Control stage over temperature)	Cause: This OHt Control trip indicates that a control stage over-temperature has been detected. From the sub-trip ‘xxyzz’, the Thermistor location is identified by ‘zz’. 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.
27 OHt dc bus (DC bus over temperature)	Cause: The OHt dc bus trip indicates a DC bus component over temperature based on a software thermal model. The drive includes a thermal protection system to protect the DC bus components within the drive. 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 the motor map settings with motor nameplate. Disable slip compensation (Pr 05.027 = 0) (Open loop). Disable dynamic V to F operation (Pr 05.013 = 0) (Open loop). Select fixed boost (Pr 05.014 = Fixed) (Open loop). Select high stability space vector modulation (Pr 05.020 = 1) (Open loop). Disconnect the load and complete a rotating auto-tune (Pr 05.012). Reduce speed loop gains (Pr 03.010, 03.011, 03.012). Check encoder signals for noise with an oscilloscope.
21 OHt Inverter (Inverter over temperature based on thermal model)	Cause: This trip indicates that an IGBT junction over-temperature has been detected based on a 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. Decrease acceleration / deceleration rates. Reduce motor load. Check DC bus ripple. Ensure all three input phases are present and balanced.
22 OHt Power (Power stage over temperature)	Cause: This trip indicates that a power stage over-temperature has been detected. From the sub-trip ‘xxyzz’, the Thermistor location is identified by ‘zz’. Remedy: Check enclosure / drive fans are still functioning correctly. Force the heatsink fans to run at maximum speed. Check enclosure ventilation paths. Check enclosure door filters. Increase ventilation. Reduce the drive switching frequency. Reduce duty cycle. Decrease acceleration / deceleration rates. 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.
102 OHt Rectifier (Rectifier over temperature)	Cause: The OHt Rectifier indicates that a rectifier over-temperature has been detected. The thermistor location can be identified from the sub-trip number. Remedy: Check the motor and motor cable insulation with an insulation tester. Install an output line reactor or sinusoidal filter. Force the heatsink fans to run at maximum speeds by setting Pr 06.045 = 11. Check enclosure / drive fans are still functioning correctly. Check enclosure ventilation paths. Check enclosure door filters. Increase ventilation. Decrease acceleration / deceleration rates. Reduce duty cycle. Reduce motor load.
3 OI ac (Instantaneous output over current detected)	Cause: The instantaneous drive output current has exceeded above 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 the motor insulation using an insulation tester. Check feedback device wiring. Check feedback device 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).
4 OI Brake (Braking IGBT over current detected)	Cause: The OI Brake trip indicates that over current has been 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.
109 OI dc (Power module over current detected from IGBT)	Cause: The OI dc trip indicates that the short circuit protection for the drive output stage has been activated. Remedy: Disconnect the motor cable at the drive end and check the motor and cable insulation with an insulation tester. Replace the drive.
92 OI Snubber (Snubber over-current detected)	Cause: The OI Snubber trip indicates that an over-current condition has been detected in the rectifier snubber circuit. The reason for the trip can be identified by the sub-trip number. 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.
215 Option Disable (Option module does not acknowledge)	Cause: The Option Disable trip indicates that the option module did not acknowledge notifying the drive that communications with the drive has been stopped during the drive mode changeover with in the allocated time. Remedy: Reset the trip. If the trip persists replace the option module.
98 Out Phase Loss (Output phase loss detected)	Cause: The Out Phase Loss trip indicates that phase loss has been detected at the drive output. (Sub-trips: 1=U phase, 2=V phase, 3=W phase, 4=Output phase loss). Remedy: Check motor and drive connections. To disable the trip set Output Phase Loss Detection Enable (06.059) = 0.
222 Over Frequency	Cause: The Over Frequency trip indicates that the output frequency has exceeded 560 Hz for more than 4 ms. Remedy: (No remedy listed in reference text).
7 Over Speed (Motor speed has exceeded over speed threshold)	Cause: In open loop mode, if the Output Frequency (05.001) exceeds the threshold set in Over Speed Threshold (03.008). In RFC-A/S mode, if Speed Feedback exceeds threshold. Remedy: Reduce the Speed Controller Proportional Gain (03.010) to reduce the speed overshoot (RFC-A, RFC-S modes only). If an SSI encoder is being used set Pr 03.047 to 1.
2 Over Volts (DC bus voltage exceeded peak level)	Cause: The Over Volts trip indicates that the DC bus voltage has exceeded the VM_DC_VOLTAGE[MAX] or VM_DC_VOLTAGE_SET[MAX] for 15 s. 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 a insulation tester.
32 Phase Loss (Supply phase loss)	Cause: The Phase Loss trip indicates that the drive has detected an input phase loss or large supply imbalance. The drive will attempt to stop the motor before this trip is initiated. 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.
198 Phasing Error	Cause: The phase offset angle in Pr 03.025 (or Pr 21.020) is incorrect and the drive is unable to control the motor correctly. If sensorless control is used, significant instability has occurred. 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 motor parameters are set up correctly. Reduce speed controller gains. Disable trip by setting over-speed threshold in Pr 03.008 to > 0 (for spurious trips in dynamic apps).
90 Power Comms	Cause: Communication has been lost or excessive errors detected between power, control, and rectifier modules. Remedy: Hardware fault – Contact the supplier of the drive.
220 Power Data	Cause: There is an error in the configuration data stored in the power system (e.g., CRC error, version mismatch, or no data obtained). 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	Cause: Internal power supply fault. 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.
9 PSU 24V	Cause: 24V internal power supply overload. The total user load of the drive and option modules has exceeded the internal limit. 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 match. 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.
01, 94-95, 103-108, 170-173, 228-247 Reserved	Cause: These trip numbers are reserved for future use. Remedy: These trips should not be used by the user application programs.
33 Resistance	Cause: Measured stator resistance during an auto-tune test has exceeded the maximum possible value of Stator Resistance (05.017), or motor is very small compared to drive rating. Remedy: 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. 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 output current waveforms with an oscilloscope. Replace the motor.
254 Slot4 Different	Cause: The Ethernet interface in slot 4 has changed or was not found (e.g., new module ID, different setup menu). Remedy: To confirm that the parameter changes detected are acceptable, reset the trip and perform a parameter save. If the trip persists – Contact the supplier of the drive.
252 Slot4 Error	Cause: The Ethernet interface in slot 4 has detected an error (e.g., Link Loss, Timeout, File System Init, Config Save error). Remedy: Identify the reason for the trip from the trip string or from sub-trip number and resolve the error. Reset the trip. If the trip persists, Hardware fault – Contact the supplier of the drive.
250 Slot4 HF	Cause: Ethernet interface in slot 4 hardware fault. The module may not have indicated it is running correctly, or memory tables are corrupt. Remedy: Hardware fault – Contact the supplier of the drive.
253 Slot4 Not Fitted	Cause: The Ethernet interface in slot 4 has been removed since the last power-up. Remedy: Hardware fault – Contact the supplier of the drive.
251 Slot4 Watchdog	Cause: Ethernet interface watchdog service error. The interface started the watchdog function but failed to service it correctly. Remedy: Hardware fault – Contact the supplier of the drive.
216 Slot App Menu	Cause: 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 has changed. The module is a different type to that installed when parameters were last saved. 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: Option module in option slot X has detected a fault. Remedy: See relevant Option Module User Guide for details of the trip.
200, 205, 210 SlotX HF – Option module X hardware fault	Cause: The option module in option slot X on the drive has indicated a hardware fault. The possible causes can be identified by the sub-trip number. Remedy: Ensure the option module is installed correctly. Replace the option module. Replace the drive.
203, 208, 213 SlotX Not Fitted – Option module in option slot X has been removed	Cause: 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 – Option module watchdog function service error	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 – Soft start relay failed to close, soft start monitor failed	Cause: 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 – Hardware trip has occurred during last power down	Cause: A hardware trip (HF01 – HF17) 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 – RAM allocation error	Cause: An option module, derivative image or user program image has requested more parameter RAM than is allowed. Remedy: Check RAM allocation requirements for installed modules/images.
218 Temp Feedback – Internal thermistor has failed	Cause: 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 – Brake resistor over temperature	Cause: 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 – Motor thermistor short circuit	Cause: The motor thermistor connected to the drive is short circuit or low impedance. Remedy: Check thermistor continuity. Replace motor / motor thermistor.
24 Thermistor – Motor thermistor over-temperature	Cause: The motor thermistor connected to the drive has indicated a motor over temperature. Remedy: Check motor temperature. Check thermistor continuity.
110 Undefined – Drive has tripped and the cause of the trip is Undefined	Cause: The power system has generated a trip but did not identify it. The cause is unknown. Remedy: Hardware fault – return the drive to the supplier.
91 User 24V – User 24 V supply is not present on control terminals (1,2)	Cause: Initiated if User Supply Select (Pr 06.072) is set to 1 or Low Under Voltage Threshold Select (06.067) = 1 and no user 24 V supply is present. Remedy: Ensure the user 24 V supply is present on control terminals 1 (0 V) and 2 (24 V).
249 User Program – On board user program error	Cause: 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). Remedy: Check the user program code logic. Check for valid ID codes and compatibility. Verify memory usage (RAM/Stack).
96 User Prog Trip – Trip generated by an onboard user program	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 – User Save error / not completed	Cause: An error has been 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 – User generated 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.
169 Volts Range – Supply voltage out of range detected in Regen mode	Cause: Initiated if the Regen Minimum Voltage is set to a non-zero value and the supply voltage is outside the defined range for more than 100 ms. Remedy: Ensure the supply voltage is operating within the drive specification. Ensure Pr 03.026 and Pr 03.027 are set correctly. Check the supply voltage waveform using an oscilloscope. Reduce the level of supply disturbance. Set Maximum Voltage (03.027) to zero to disable the trip.
30 Watchdog – Control word watchdog has timed out	Cause: The control word watchdog has been enabled and has timed out. Remedy: Check control system communication and timing.
Error 1 Insufficient 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 Reset Acknowledge Failure	Cause: At least one option module did not acknowledge the reset request. Remedy: Power cycle drive.
Error 3 Flash Erase Failure	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 Failure	Cause: The boot loader failed to program the processor flash. Remedy: Power cycle drive and try again. If problem persists, return drive.
Error 5 Initialization Failure	Cause: One option module did not initialize correctly. Option module did not set Ready to Run flag. Remedy: Remove faulty option module.