Nidec Control Techniques Digitax HD M754 MCi Servo Drive

Nidec Control Techniques Digitax HD M754 MCi Servo Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
217 App Menu Changed	Cause: The customization table for an application menu has changed. The menu that has changed can be identified by the sub-trip number: Sub-trip 1: Menu 18 Sub-trip 2: Menu 19 Sub-trip 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 during autotune. Sub-trip 1: Position feedback did not change during rotating auto-tune. Sub-trip 2: Motor did not reach required speed during mechanical load measurement. Sub-trip 3: Required commutation signal edge not found (Commutation Only device). Sub-trip 4: Required movement angle cannot be produced (minimal movement test). Sub-trip 5: Minimal movement test cannot locate motor flux position accurately. Sub-trip 6: Phasing offset angle results not within 30° during stationary auto-tune. Sub-trip 7: Motor is moving when phasing test on enable is selected. Sub-trip 8: Auto-tune attempted while AMC is selected. 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. Check feedback device wiring is correct. Check encoder mechanical coupling to the motor. For sub-trip 8: Set AMC Select (31.001) to zero to deselect AMC.
12 Autotune 2	Cause: Position feedback direction incorrect. Sub-trip 1: Position feedback direction incorrect during rotating autotune. Sub-trip 2: SINCOS encoder comms position rotating opposite to sine wave position. Remedy: Check motor cable wiring is correct. Check feedback device wiring is correct. Swap any two motor phases.
13 Autotune 3	Cause: Measured inertia exceeded parameter range or commutation signals changed in wrong direction. 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 at standstill, repeat with motor rotating within recommended speed range.
14 Autotune 4	Cause: Drive encoder U commutation signal fail. 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. 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. 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. 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. Either drive enable or drive run were removed. Remedy: Check the drive enable signal (terminal 2 & 6) were 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). Braking Resistor Thermal Accumulator (10.039) reached 100%. Remedy: Ensure values in Pr 10.030, Pr 10.031, and Pr 10.061 are correct. If external protection is used, set Pr 10.030, 10.031 or 10.061 to 0 to disable trip.
99 CAM	Cause: Advanced motion controller CAM failure. Sub-trip 1: AMC Cam Start Index > Cam Size or Table In > Start index. Sub-trip 2: AMC CAM Index changed by more than 2 in one sample. Sub-trip 3: Rate of change at segment boundary exceeded maximum. Sub-trip 4: Sum of Cam Position and master position change exceeded maximum. Remedy: Review CAM parameters and definitions.
185 Card Access	Cause: SD Card Write fail. Unable to access SD Card or data transfer corrupted. Remedy: Check SD Card is installed / located correctly. Replace the SD Card.
177 Card Boot	Cause: The Menu 0 parameter modification cannot be saved to the SD Card. Boot file not created to take new parameter value. Remedy: Ensure 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	Cause: SD Card cannot be accessed as it is being accessed by an option module. Remedy: Wait for the option module to finish accessing the SD Card and re-attempt the required function.
188 Card Compare	Cause: SD Card file/data is different to the one in 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	Cause: SD Card data location already contains data. Remedy: Erase the data in data location. Write data to an alternative data location.
187 Card Drive Mode	Cause: SD Card parameter set not compatible with 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: SD Card data structure error. Sub-trip 1: Required folder and file structure not present. Sub-trip 2: The <000> file is corrupted. Sub-trip 3: Two or more files in folder have same file identification number. Remedy: Erase all the data blocks and re-attempt the process. Ensure the card is located correctly. Replace the SD Card.
184 Card Full	Cause: SD Card full. 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	Cause: SD Card data not found. Attempted to access non-existent file or block. Remedy: Ensure data block number is correct.
180 Card Option	Cause: SD Card trip; option modules installed are different between source drive and destination drive. 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 red reset button to acknowledge parameters will be set to default.
175 Card Product	Cause: SD Card data blocks are not compatible with the drive derivative. Sub-trip 1: Drive Derivative (11.028) is different. Sub-trip 2: Product Type (11.063) is different. Sub-trip 3: A Unidrive SP parameter value has no equivalent on destination drive. 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	Cause: The voltage and / or current rating of the source and destination drives are different. Remedy: Reset the drive to clear the trip. Ensure that the drive rating dependent parameters have transferred correctly. This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
181 Card Read Only	Cause: SD Card has the Read Only bit set. Remedy: Clear the read only flag by setting Pr mm.000 to 9777 and reset the drive.
174 Card Slot	Cause: Option module application program transfer has failed. Remedy: Ensure the source / destination option module is installed on the correct slot.
35 Control Word	Cause: Trip initiated from the Control Word (06.042) by setting bit 12. Remedy: Check the value of Pr 06.042. Disable the control word in Control Word Enable (Pr 06.043). When enabled, clear by setting bit 12 to zero.
225 Current Offset	Cause: Current feedback offset error. Offset too large to be trimmed. Sub-trip 1: Phase U Sub-trip 2: Phase V Sub-trip 3: Phase 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	Cause: Drive parameters are being changed by user action or file system write while drive is enabled. Remedy: Ensure the drive is not enabled when loading defaults, changing drive mode, or transferring data/programs.
247 Derivative ID	Cause: Derivative identification error. Sub-trip 1: Derivative image erased. Sub-trip 2: Identifier out of range. Sub-trip 3: Derivative image changed. Remedy: Contact the supplier of the drive.
248 Derivative Image	Cause: Derivative Image error. Sub-trip 1-52: Error in derivative image. Sub-trip 61-64: Option module fitted in slot 1-4 not allowed. Sub-trip 70: Required option module not fitted. Sub-trip 71-73: Specific option module required in slot 1-3 not present. 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. Control PCB has not recognized power circuit size. 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. EEPROM failure or corruption. Sub-trip 1: Internal parameter database version changed. Sub-trip 2: CRCs invalid. Sub-trip 3: Drive mode restored is outside allowed range. Sub-trip 4: Derivative image changed. Sub-trip 5: Power stage hardware changed. Sub-trip 6: Internal I/O hardware changed. Sub-trip 7: Position feedback interface hardware changed. Sub-trip 9: Checksum on non-parameter area failed. Remedy: Default the drive and perform a reset. Allow sufficient time to perform a save before supply is removed. If trip persists – return drive to supplier.
189 Encoder 1	Cause: Drive position feedback interface power supply overload (Terminals 13 & 14). Remedy: Check encoder power supply wiring. Disable termination resistors (Pr 03.039) to reduce current. Check encoder specification for compatibility. Replace the encoder. Use an external power supply.
190 Encoder 2	Cause: Drive encoder (Feedback) wire break. Sub-trip 1: Feedback interface 1 on any input. Sub-trip 2: Feedback interface 2 on any input. Sub-trip 11-13: Feedback interface 1 on A, B, or Z channel. Remedy: Ensure position feedback device type (Pr 03.038) is correct. Check cable continuity. Check wiring of feedback signals. Replace encoder.
191 Encoder 3	Cause: Phase offset incorrect while running. 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. Repeat the offset measurement test.
192 Encoder 4	Cause: Feedback device comms failure. Encoder communications has timed out or the communications position message transfer time is too long. Can also be caused by a wire break. 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: Checksum or CRC error. There is a 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 minimize 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	Cause: Encoder has indicated an error. The encoder has indicated an error or the power supply has failed 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: 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	Cause: Position feedback interface has timed out. 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: 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 (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: Encoder could not be identified during auto-configuration. 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: Data read from the encoder is out of range during auto-configuration. Sub-trip Reason x1 Rotary lines per revolution error x2 Linear comms pitch error x3 Linear line pitch error x4 Rotary turns bits error x5 Communications bits error x6 Calculation time is too long x7 Line delay measured is longer than 5 μs Remedy: Enter the encoder setup parameters manually. Check to see the encoder supports auto-configuration.
6 External Trip	Cause: An External Trip has been initiated. This can be caused by digital input states (Safe Torque Off) 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, equates to ‘on’. If external trip detection of the Safe Torque Off 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 CPU address error	Cause: Data processing error: CPU address error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF02 DMAC address error	Cause: Data processing error: DMAC address error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF03 Illegal instruction	Cause: Data processing error: Illegal instruction. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF04 Illegal slot instruction	Cause: Data processing error: Illegal slot instruction. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF05 Undefined exception	Cause: Data processing error: Undefined exception error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF06 Reserved exception	Cause: Data processing error: Reserved exception error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF07 Watchdog failure	Cause: Data processing error: Watchdog failure. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF08 CPU Interrupt crash	Cause: Data processing error: CPU interrupt crash. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF09 Free store overflow	Cause: Data processing error: Free store overflow. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF10 Parameter routing system error	Cause: Data processing error: Parameter routing system error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF11 Access to EEPROM failed	Cause: Data processing error: Access to the drive EEPROM has failed. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF12 Main program stack overflow	Cause: Data processing error: Main program stack overflow. Remedy: Hardware fault – Contact the supplier of the drive.
HF13 Firmware incompatible with hardware	Cause: Data processing error: Drive firmware is not compatible with the hardware. Remedy: Re-program the drive with the latest version of the drive firmware for Digitax HD M754. Hardware fault – Contact the supplier of the drive.
HF14 CPU register bank error	Cause: Data processing error: CPU register bank error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF15 CPU divide error	Cause: Data processing error: CPU divide error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF16 RTOS error	Cause: Data processing error: RTOS error. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF17 Clock supplied to control board out of specification	Cause: Data processing error: Clock supplied to the control board logic is out of specification. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF18 Internal flash memory has failed	Cause: Data processing error: Internal flash memory failed when writing option module parameter data. Remedy: Hardware fault – Contact the supplier of the drive.
HF19 CRC check on the firmware has failed	Cause: Data processing error: CRC check on the drive firmware has failed. Remedy: Re-program the drive. Hardware fault – Contact the supplier of the drive.
HF20 ASIC is not compatible with the hardware	Cause: Data processing error: 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: Hardware fault. Remedy: If this trip occurs please consult the drive supplier.
8 Inductance	Cause: Inductance measurement out of range or motor saturation not detected. Occurs in RFC-S mode when motor inductances are not suitable or saturation cannot be measured. Sub-trip Reason 1 Inductance ratio/difference too small (sensorless start). 2 Saturation characteristic cannot be measured (sensorless start). 3 Ratio/difference too small during stationary auto-tune (RFC-S). 4 Direction of flux detected by inductance change with currents is invalid. 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. Sub-trip 4: Stationary autotune is not possible. Perform a minimal movement or rotating autotune. Phasing test on starting is not possible. Use a position feedback device with commutation signals or absolute position.
93 Inductor Too Hot	Cause: The regen inductor has overloaded. Thermal overload based on Rated Current and Inductor Thermal Time Constant. Trip occurs when temp reaches 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 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.
160 Island	Cause: Island condition detected in regen mode. AC mains is no longer present and the inverter would be an ‘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.
20 Motor Too Hot	Cause: Output current overload timed out (I2t). Motor thermal overload based on Rated Current and Motor Thermal Time Constant. Remedy: Ensure the load is not jammed / sticking. Check the load on the motor has not changed. If seen during an auto-tune test in RFC-S mode, ensure the motor Rated Current is ≤ Heavy duty current rating of the drive. Tune the Rated Speed (Pr 05.008) (RFC-A mode only). Check feedback signal for noise. Ensure the motor rated current is not zero. This trip can be disabled (Pr 04.016 to 1).
176 Name Plate	Cause: Electronic nameplate transfer has failed. Remedy: Ensure that the device encoder memory has at least 128 bytes to store the nameplate data. When writing the motor object (Pr mm.000 = 11000), ensure that the device encoder memory has at least 256 bytes to store all the nameplate data. When transferring between option module and encoder, ensure that the 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.
101 OHt Brake	Cause: Braking IGBT over-temperature. 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: 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: 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. If unstable: 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 (RFC-A, RFC-S). Check encoder signals for noise with an oscilloscope.
21 OHt Inverter (Inverter over temperature based on thermal model)	Cause: 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. 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).
22 OHt Power (Power stage over temperature)	Cause: 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. Use S ramp (Pr 02.006). Check the derating tables and confirm the drive is correctly sized.
3 OI ac (Instantaneous output over current detected)	Cause: The instantaneous drive output current has exceeded VM_DRIVE_CURRENT[MAX]. This trip cannot be reset until 10 s 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. 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.
4 OI Brake (Braking IGBT over current detected)	Cause: Over current has been detected in braking IGBT or braking IGBT protection has been activated. Short circuit protection for the braking IGBT 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 on state voltage monitoring)	Cause: The short circuit protection for the drive output stage has been activated. The table shows where the trip has been detected. 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: 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.
215 Option Disable	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.
98 Out Phase Loss (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.
7 Over Speed (Motor speed has exceeded the over speed threshold)	Cause: In open loop mode, Output Frequency exceeds the threshold. In RFC mode, Speed Feedback exceeds 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. If caused by flux weakening in RFC-S mode, ensure Enable High Speed Mode (05.022) is set to -1.
2 Over Volts (DC bus voltage has exceeded the peak level or maximum continuous level)	Cause: 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 an insulation tester.
32 Phase Loss (Supply phase loss)	Cause: Input phase loss or large supply imbalance detected. Can be detected via thyristor base charge system or DC bus voltage ripple. Remedy: Check the AC supply voltage balance and level at full load. Check the DC bus ripple level with an isolated oscilloscope. Check the output current stability. Check for mechanical resonance with the load. Reduce the duty cycle. Reduce the motor load. Disable the phase loss detection, set Pr 06.047 to 2.
198 Phasing Error (RFC-S mode phasing failure due to incorrect phase angle)	Cause: The phase offset angle in Pr 03.025 is incorrect if 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. Spurious Phasing Error trips can be disabled by setting the over-speed threshold in Pr 03.008 to a value greater than zero. Ensure that the motor parameters are set-up correctly. Reduce the speed controller gains.
90 Power Comms (Communication lost / errors detected between power, control and rectifier modules)	Cause: A communications problem within the power system of the drive. The reason for the trip can be identified by the sub-trip number. Remedy: Hardware fault – Contact the supplier of the drive.
220 Power Data (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.
37 Power Down Save (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.
5 PSU (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.
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. Remedy: Reduce the load and reset. Provide an external 24 V power supply on control terminal 2. Remove all option modules.
33 Resistance (Measured resistance has exceeded the parameter range)	Cause: 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.
254 Slot3 Different (Ethernet interface in slot 3 has changed)	Cause: The Ethernet interface in slot 3 has changed / not found. Remedy: Turn off the power, ensure that the correct option module is installed in the option slot and re-apply the power. Confirm that the currently installed option module is correct, ensure the option module parameters are set correctly and perform a User Save in Pr mm.000. If the trip persists – Contact the supplier of the drive.
252 Slot3 Error	Cause: The Ethernet interface in slot 3 on the drive has detected an error. The reason for the trip can be identified by the sub-trip number (see manual for full list 100-228). 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 Slot3 HF (Hardware Fault)	Cause: The Ethernet interface in slot 3 cannot operate. Common sub-trips: Sub-trip Reason 1 Module category cannot be identified 2 Required customized menu table not supplied or corrupt 3 Insufficient memory for comms buffers 8-9 Drive failed to read/upload menu tables Remedy: Ensure the Ethernet interface is installed correctly. Hardware fault – Contact the supplier of the drive.
253 Slot3 Not Fitted	Cause: The Ethernet interface in slot 3 on the drive has been removed since the last power-up. Remedy: Ensure the Ethernet interface is installed correctly. Hardware fault – Contact the supplier of the drive.
251 Slot3 Watchdog	Cause: The Ethernet interface installed in slot 3 has started the option watchdog function and then failed to service the watchdog correctly. Remedy: Hardware fault – Contact the supplier of the drive.
216 Slot App Menu	Cause: 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 option module in option slot X is a different type to that installed when parameters were last saved. Sub-trip identifies the original module. 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. The reason 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 (Hardware Fault)	Cause: The option module in option slot X cannot operate. Common sub-trips: 1: Module category unidentified 2: Menu table corrupt/missing 5: Module removed after power-up 10: Menu table CRC invalid 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 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 removal is intentional, 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 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: A hardware trip (HF01 – HF20) has occurred and the drive has been power cycled. The sub-trip number identifies the HF trip (e.g. stored HF.17). Remedy: Enter 1299 in Pr mm.000 and press reset to clear the trip.
227 Sub-array RAM	Cause: RAM allocation error. An option module, derivative image, or user program has requested more parameter RAM than allowed. Sub-trip = (parameter size) + (parameter type) + sub-array number. Remedy: Check option module/user program configurations reducing RAM usage. (No specific hardware action listed; implies configuration limit reached).
218 Temp Feedback	Cause: An internal thermistor has failed. Location identified by sub-trip (xx y zz). xx: 00=Control PCB, 01=Power system zz: 01-03=Specific thermistor IDs Remedy: Hardware fault – Contact the supplier of the drive.
10 Th Brake Res	Cause: Brake resistor over temperature. Hardware based braking resistor thermal monitoring is connected and the resistor 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: Motor thermistor short circuit. The motor thermistor is short circuit or low impedance (< 50 Ω). Sub-trip 4: Position feedback interface. Remedy: Check thermistor continuity. Replace motor / motor thermistor.
24 Thermistor	Cause: Motor thermistor over-temperature. The motor thermistor connected to the drive has indicated a motor over temperature. Remedy: Check motor temperature. Check Threshold Level (07.048). Check thermistor continuity.
110 Undefined	Cause: The power system has generated but did not identify the trip from the power system. The cause is unknown. Remedy: Hardware fault – return the drive to the supplier.
249 User Program	Cause: On board user program error. An error has been detected in the onboard user program image. Common Sub-trips: Sub-trip Reason 1 Divide by zero 2 Undefined trip 30-33 Image/CRC/RAM failure 40 Timed task suspended 200 Divide by zero (downloaded image) Remedy: Check and debug the Onboard User Program code. Check for parameter access errors or over-range writes (Sub-trips 3-7, 208).
96 User Prog Trip	Cause: Trip generated by an onboard user program using a function call which defines the sub-trip number. Remedy: Check the user program.
36 User Save	Cause: User Save error / not completed. Error detected in user save parameters or 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.
169 Voltage Range	Cause: Supply voltage out of range detected in Regen mode. Supply is outside the range defined by Regen Minimum/Maximum Voltage settings. 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	Cause: Control word watchdog has timed out. 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. Disable watchdog if not required.
32 Phase Loss	Cause: The drive has detected an input phase loss or large supply imbalance. Phase loss can be detected directly from the supply where the drive has a thyristor base charge system (Frame size 8 and above) 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. 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.
198 Phasing Error	Cause: RFC-S mode phasing failure due to incorrect phase angle. The phase offset angle in Pr 03.025 (or Pr 21.020) is incorrect if 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.
90 Power Comms	Cause: Communication has been lost or errors detected between power, control, and rectifier modules. A Power Comms trip indicates a communications problem within the power system of the drive. Remedy: Hardware fault – Contact the supplier of the drive.
220 Power Data	Cause: Power system configuration data error. The Power Data trip indicates that there is an error in the configuration data stored in the power system. This can occur if the control board data table does not match the power board hardware identifier, or if there are CRC errors. Remedy: Hardware fault – Contact the supplier of the drive.
37 Power Down Save	Cause: Power down save error. The trip indicates that an error has been detected in the power down save parameters saved in non-volatile memory. Remedy: Perform a 1001 save in Pr mm.000 to ensure that the trip doesn’t occur the next time the drive is powered up.
5 PSU	Cause: Internal power supply fault. 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 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.
33 Resistance	Cause: Measured resistance has exceeded the parameter range. Either the value being used for motor stator resistance is too high, or an attempt to measure it failed. Remedy: Check that the value 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 an 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 output current waveforms. Replace the motor.
254 Slot3 Different	Cause: Ethernet interface in slot 3 has changed. The interface was changed or not found. Remedy: Turn off the power, ensure that the correct option module is installed in the option slot and re-apply the power. Confirm that the currently installed option module is correct. Ensure the option module parameters are set correctly and perform a User Save in Pr mm.000. If the trip persists – Contact the supplier of the drive.
252 Slot3 Error	Cause: Ethernet interface in slot 3 has detected a fault. Reasons include Link Loss, E/IP Timeout, Modbus Timeout, Watchdog errors, Firmware invalid, etc. 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 Slot3 HF	Cause: Ethernet interface in slot 3 hardware fault. The interface cannot operate. Remedy: Ensure the Ethernet interface is installed correctly. Hardware fault – Contact the supplier of the drive.
253 Slot3 Not Fitted	Cause: Ethernet interface in slot 3 has been removed since the last power-up. Remedy: Ensure the Ethernet interface is installed correctly. Hardware fault – Contact the supplier of the drive.
251 Slot3 Watchdog	Cause: Ethernet interface watchdog service error. The interface started the watchdog function and then failed to service it correctly. Remedy: Hardware fault – Contact the supplier of the drive.
216 Slot App Menu	Cause: Application menu Customization conflict error. More than one option slot has requested to customize the 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 installed 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 an error. Remedy: See the relevant Option Module User Guide for details of the trip.
200, 205, 210 SlotX HF	Cause: Option module X hardware fault. The module cannot operate. Possible causes include module category identification failure, memory allocation issues, or drive failing to read menu tables. Remedy: Ensure the option module is installed correctly. Replace the option module. Replace the drive.
203, 208, 213 SlotX Not Fitted	Cause: 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: Option module watchdog function service error. The option module started the watchdog function and then failed to service it. Remedy: Replace the option module.
226 Soft Start	Cause: Soft start relay failed to close, soft start monitor failed. Remedy: Hardware fault – Contact the supplier of the drive.
221 Stored HF	Cause: Hardware trip has occurred during last power down. A hardware trip (HF01 – HF20) occurred and the drive has been power cycled. Remedy: Enter 1299 in Pr mm.000 and press reset to clear the trip.
227 Sub-array RAM allocation error	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 RAM allocation is checked in order of resulting sub-trip numbers. Remedy: Check option module configuration. Check user program image size. (No specific recommended actions listed in source; implies configuration/sizing error).
218 Internal thermistor has failed	Cause: The Temp Feedback trip indicates that an internal thermistor has failed. The thermistor location can be identified by the sub-trip number (e.g., Control PCB, Power system). Remedy: Hardware fault – Contact the supplier of the drive.
10 Brake resistor over temperature	Cause: Hardware based braking resistor thermal monitoring is connected and the resistor overheats. If the braking resistor is not used then this trip must be disabled with bit 3 of Action On Trip Detection (10.037). Remedy: Check brake resistor wiring. Check braking resistor value is greater than or equal to the minimum resistance value. Check braking resistor insulation.
25 Motor thermistor short circuit	Cause: 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 Motor thermistor over-temperature	Cause: The motor thermistor connected to the drive has indicated a motor over temperature. Remedy: Check motor temperature. Check Threshold Level (07.048). Check thermistor continuity.
110 Drive has tripped and the cause of the trip is Undefined	Cause: The power system has generated but did not identify the trip. The cause is unknown. Remedy: Hardware fault – return the drive to the supplier.
249 On board user program error	Cause: An error has been detected in the onboard user program image. The reason is identified by the sub-trip number (e.g., Divide by zero, Undefined trip, Array bounds violation, etc.). Remedy: Review sub-trip code in drive diagnostics. Debug user program logic (e.g. check for divide by zero, invalid pointers). Check if image is compatible with control board. Save parameters if “Customized menu table changed” (sub-trip 53) occurs.
96 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 error / not completed	Cause: An error has been detected in the user save parameters saved in non-volatile memory. Can happen if power is removed while parameters are being saved. Remedy: Perform a user save in Pr mm.000 to ensure that the trip doesn’t occur the next time the drive is powered up. Ensure that the drive has enough time to complete the save before removing the power to the drive.
40 – 89 112 – 159 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 Supply voltage out of range detected in Regen mode	Cause: Regen Minimum Voltage (03.026) is set to a non-zero value and the supply voltage is outside the range defined by Min/Max parameters 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 Control word watchdog has timed out	Cause: The control word has been enabled and has timed out. 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. Remedy: Ensure control word update signal is stable. Check communication timing. Disable watchdog if not required.
Error 1 Programming Memory 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 Option Module Error	Cause: At least one option module did not acknowledge the reset request. Remedy: Power cycle drive.
Error 3 Boot Loader 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 Boot Loader 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 Option Module Init Failure	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 resistor sizing or reduce braking duty cycle.
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 dwell times.
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 %.
Drive Overload Drive Over Temperature	Cause: Percentage Of Drive Thermal Trip Level (07.036) in the drive is greater than 90 %.
Auto Tune Autotune Active	Cause: The autotune procedure has been initialized and an autotune in progress.
Limit Switch Limit Switch Active	Cause: Indicates that a limit switch is active and that is causing the motor to be stopped.
Inhibit Drive Inhibited	Cause: The drive is inhibited and cannot be run. The Safe Torque Off signal is not applied to Safe Torque Off terminals or Pr 06.015 is set to 0. (Output Stage: Disabled)
Ready Drive Ready	Cause: The drive is ready to run. The drive enable is active, but the drive inverter is not active because the final drive run is not active. (Output Stage: Disabled)
Stop Stopped	Cause: The drive is stopped / holding zero speed. (Output Stage: Enabled)
Run Running	Cause: The drive is active and running. (Output Stage: Enabled)
Scan Synchronizing	Cause: The drive is enabled in Regen mode and is trying to synchronize to the supply. (Output Stage: Enabled)
Supply Loss Supply Loss Detected	Cause: Supply loss condition has been detected. (Output Stage: Enabled)
Deceleration Decelerating	Cause: The motor is being decelerated to zero speed / frequency because the final drive run has been deactivated. (Output Stage: Enabled)
dc injection DC Injection Braking	Cause: The drive is applying dc injection braking. (Output Stage: Enabled)
Position Position Control Active	Cause: Positioning / position control is active during an orientation stop. (Output Stage: Enabled)
Trip Drive Tripped	Cause: The drive has tripped and no longer controlling the motor. The trip code appears in the lower display. (Output Stage: Disabled)
Active Regen Active	Cause: The regen unit is enabled and synchronized to the supply. (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. (Output Stage: Disabled)
Heat Motor Pre-heat	Cause: The motor pre-heat function is active. (Output Stage: Enabled)
Phasing Phasing Test	Cause: The drive is performing a ‘phasing test on enable’. (Output Stage: Enabled)
Booting Parameters Loading Parameters	Cause: Parameters are being loaded. Drive parameters are being loaded from an SD Card.
Booting User Program Loading User Program	Cause: User program is being loaded from an SD Card to the drive.
Booting Option Program Loading Option Program	Cause: User program is being loaded from an SD Card to the option module in slot X.
Writing To NV Card Writing Data	Cause: Data is being written to an SD Card to ensure that its copy of the drive parameters is correct because the drive is in Auto or Boot mode.
Waiting For Power System Waiting for Power Stage	Cause: The drive is waiting for the processor in the power stage to respond after power-up.
Waiting For Options Waiting for Option Module	Cause: The drive is waiting for the Options Modules to respond after power-up.
Uploading From Options Updating Database	Cause: Loading parameter database. At power-up it may be necessary to update the parameter database held by the drive because an option module has changed.