Nidec & Control Technique Unidrive M700 Drive

Nidec & Control Technique Unidrive M700 Drive Fault Codes:

Fault Code and Meaning	Cause and Remedy
28 An Input 1 Loss	Cause: Current loss detected in current mode on Analog input 1 (Terminal 5, 6). In 4-20 mA and 20-4 mA modes, loss of input is detected if the current falls below 3 mA. Remedy: Check control wiring is correct. Check control wiring is undamaged. Check the Analog Input 1 Mode (07.007). Current signal is present and greater than 3 mA.
29 An Input 2 Loss	Cause: Current loss detected in current mode on Analog input 2 (Terminal 7). In 4-20 mA and 20-4 mA modes, loss of input is detected if the current falls below 3 mA. Remedy: Check control wiring is correct. Check control wiring is undamaged. Check the Analog Input 2 Mode (07.011). Current signal is present and greater than 3 mA.
219 An Output Calib	Cause: The zero offset calibration of one or both of the analog outputs has failed. This indicates that the drive hardware has failed or a voltage is applied to the output via a low impedance. Sub-trip 1: Output 1 failed (Terminal 9) Sub-trip 2: Output 2 failed (Terminal 10) Remedy: Check the wiring associated with analog outputs. Remove all the wiring that is connected to analog outputs and perform a re-calibration by power cycling the drive. If trip persists replace the drive.
217 App Menu Changed	Cause: The customization table for an application menu has changed. The menu that has been changed can be identified by the sub-trip number (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 during an autotune. Common causes based on Sub-trips: – Position feedback did not change. – Motor did not reach required speed. – Required commutation signal edge not found. – Phasing offset angle measured twice not within 30°. 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 during rotating autotune. Sub-trip 1: Direction incorrect when position feedback is being used. Sub-trip 2: SINCOS encoder comms position rotating opposite to sine wave. 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 during rotating autotune or mechanical load measurement. Remedy: Check motor cable wiring is correct. Check feedback device U,V and W commutation signal wiring is correct. Increase the test level. If the test was carried out at standstill repeat the test with the motor rotating within the recommended speed range.
14 Autotune 4	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. Initiated during rotating autotune if setup is incorrect. 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 because either the drive enable or the drive run were removed. Remedy: Check the drive enable signal (terminal 31 on Unidrive M700/M701 and terminal 11 & 13 on Unidrive M702) 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 (I2t). The Braking Resistor Thermal Accumulator (10.039) reached 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. Sub-trip 1: Start Index > Cam Size or Start Position > Table In. Sub-trip 2: 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 change of master position exceeded maximum. Remedy: Review CAM configuration and parameters (No specific actions listed in manual).
185 Card Access	Cause: NV Media Card Write fail. Drive was unable to access the NV Media Card. If during data transfer, file may be corrupted. 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. Occurs when Pr 11.042 is set for auto/boot mode but necessary boot file is not created or drive not reset. Remedy: Ensure that Pr 11.042 is correctly set, and then reset the drive to create the necessary file on the NV Media Card. Re-attempt the parameter write to the Menu 0 parameter.
178 Card Busy	Cause: NV Media Card cannot be accessed as it is being accessed by an option module. Remedy: Wait for the option module to finish accessing the NV Media Card and re-attempt the required function.
188 Card Compare	Cause: NV Media Card file/data is different to the one in the drive. Compare initiated if parameters on card differ from drive. Remedy: Set Pr mm.000 to 0 and reset the trip. Check to ensure the correct data block on the NV Media Card has been used for the compare.
179 Card Data Exists	Cause: NV Media Card data location already contains data. Attempt made to store data in a block which already contains data. Remedy: Erase the data in data location. Write data to an alternative data location.
187 Card Drive Mode	Cause: NV Media Card parameter set not compatible with current drive mode. Data block on card is different from 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. Error detected in data structure (missing folder, corrupted file, or duplicate IDs). Remedy: Erase all the data blocks and re-attempt the process. Ensure the card is located correctly. Replace the NV Media Card.
184 Card Full	Cause: NV Media Card full. Attempt made to create data block but not enough space. 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. Attempt made to access non-existent file or block. Remedy: Ensure data block number is correct.
180 Card Option	Cause: Option modules installed are different between source drive and destination drive. Parameter data is being transferred from a NV Media Card, but the option module categories differ. Data for different modules will be set 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. Sub-trip 1: Drive Derivative is different (Warning trip). Sub-trip 2: Product Type is different or corruption detected (No data transferred). Sub-trip 3: Unidrive SP parameter found with no equivalent (Warning trip). 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: The voltage and/or current rating of the source and destination drives are different. This is a warning that rating specific parameters (RA attribute) may not be transferred. Remedy: Reset the drive to clear the trip. Ensure that the drive rating dependent parameters have transferred correctly. This trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
181 Card Read Only	Cause: 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: Option module application program transfer has failed because the option module does not respond correctly. The sub-trip indicates the slot number. Remedy: Ensure the source / destination option module is installed on the correct slot.
111 Configuration	Cause: The number of power modules installed is different from the modules expected (Pr 11.071). Or, the number of external rectifiers connected is less than expected (Pr 11.096). Remedy: Ensure that all the power modules are correctly connected. Ensure all the power modules have powered up correctly. Ensure that the value in Pr 11.071 is set to the number of power modules connected. Set Pr 11.035 to 0 to disable the trip if it is not required. Ensure that all the external rectifiers are connected correctly. Ensure that the value in Number Of Rectifiers Expected (11.096) is correct.
35 Control Word	Cause: Trip initiated from the Control Word (06.042) by setting bit 12 when Control Word Enable (06.043) is 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 on Control Word. When the control word is enabled, the trip can only be cleared by setting bit 12 to zero.
225 Current Offset	Cause: Current feedback offset error. The offset is too large to be trimmed. Sub-trip identifies phase: 1 (U), 2 (V), 3 (W). Remedy: Ensure that there is no possibility of current flowing in the output phases of the drive when the drive is not enabled. Hardware fault – Contact the supplier of the drive.
97 Data Changing	Cause: Drive parameters are being changed while the drive is active/enabled. This includes loading defaults, changing drive mode, or transferring data from NV memory/feedback devices. 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: Derivative identification error. Problem with the identifier associated with the derivative image. Sub-trip 1: Image should exist but has been erased. Sub-trip 2: Identifier out of range. Sub-trip 3: Image has been changed. Remedy: Contact the supplier of the drive.
248 Derivative Image	Cause: An error has been detected in the derivative image. Sub-trips 1-52: Error detected in image. Sub-trips 61-64: Option module in slot 1-4 not allowed with derivative image. Sub-trips 70-74: Required option module missing. Remedy: Contact the supplier of the drive.
199 Destination	Cause: Two or more parameters are writing to the same destination parameter (Menus 3, 7, 8, 9, 12 or 14). Remedy: Set Pr mm.000 to ‘Destinations’ or 12001 and check all visible parameters in all menus for parameter write conflicts.
224 Drive Size	Cause: Power stage recognition: Unrecognized drive size. The control PCB has not recognized the drive size of the power circuit connected. 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 due to an issue with non-volatile memory. Sub-trip 1: Database version changed. Sub-trip 2: CRC Check failed. Sub-trip 9: 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: Drive position feedback interface power supply overload. Terminals 13 & 14 max current exceeded. 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: Drive encoder (Feedback) wire break detected on the 15 way D-type connector. Remedy: Ensure that the position feedback device type selected in Pr 03.038 is correct for the position feedback device connected to the P1 interface on the drive. 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 Phase offset incorrect while running	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. The feedback device which has caused the trip can be identified by the sub-trip number. Remedy: Check encoder shield connections. Ensure the encoder cable is one uninterrupted cable. Check the encoder signal for noise with an oscilloscope. Check the integrity of the encoder mechanical mounting. For a UVW servo encoder, ensure that the phase rotation of the UVW commutation signals is the same as the phase rotation of the motor. For a SINCOS encoder, ensure that motor and incremental SINCOS connections are correct and that for forward rotation of the motor, the encoder rotates clockwise. Repeat the offset measurement test.
192 Encoder 4 Feedback device comms failure	Cause: 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 Checksum or CRC error	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 carry out an encoder auto-configuration (Pr 03.041 = Enabled). Replace the encoder.
194 Encoder 6 Encoder has indicated an error	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 Set-up parameters for position feedback device have changed	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 Position feedback interface has timed out	Cause: The Encoder 8 trip indicates that Position feedback interface communications time exceeds 250 μs. The feedback device which has caused the trip can be identified by the sub-trip number. Remedy: Ensure the encoder is connected correctly. Ensure that the encoder is compatible. Increase baud rate.
197 Encoder 9 Position feedback is selected from a option module slot which does not have a feedback option module installed	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 Encoder could not be identified during auto-configuration	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 Data read from the encoder is out of range during auto-configuration	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.
164 Encoder 14 The data given in the additional configuration parameter for a position feedback interface is out of range	Cause: The Encoder 14 trip indicates that the data given in the additional configuration parameter for a position feedback interface is out of range. If the sub-trip number is one then the data is out of range in P1 Additional Configuration (03.074). Remedy: Check range checking settings for BiSS turns padding and position padding. Ensure configuration values do not exceed +/-16 padding value limits.
6 External Trip	Cause: An External Trip has occurred. The cause of the trip can be identified from the sub trip number displayed after the trip string. An external trip can also be initiated by writing a value of 6 in Pr 10.038. Remedy: Check the Safe Torque Off signal voltage (on terminal 31 on Unidrive M700 / M701 and terminal 11 & 13 on Unidrive M702) equals to 24 V. Check the value of Pr 08.009 which indicates the digital state of terminal 31 on Unidrive M700 / M701 and terminal 11 & 13 on Unidrive M702, 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 Data processing error: CPU address error	Cause: The HF01 trip indicates that 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: The HF02 trip indicates that 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: The HF03 trip indicates that 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: The HF04 trip indicates that 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: The HF05 trip indicates that 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: The HF06 trip indicates that 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: The HF07 trip indicates that 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: The HF08 trip indicates that 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: The HF09 trip indicates that a free store overflow has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF10 Data processing error: Parameter routing system error	Cause: The HF10 trip indicates that a Parameter routing system error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF11 Data processing error: Access to EEPROM failed	Cause: The HF11 trip indicates that access to the drive EEPROM has failed. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF12 Data processing error: Main program stack overflow	Cause: The HF12 trip indicates that the main program stack overflow has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF13 Data processing error: Firmware incompatible with hardware	Cause: The HF13 trip indicates that the drive firmware is not compatible with the hardware. This trip indicates that the control PCB on the drive has failed. Remedy: Re-program the drive with the latest version of the drive firmware for Unidrive M700 / M701 / M702. Hardware fault – Contact the supplier of the drive.
HF14 Data processing error: CPU register bank error	Cause: The HF14 trip indicates that a CPU register bank error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF15 Data processing error: CPU divide error	Cause: The HF15 trip indicates that a CPU divide error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF16 Data processing error: RTOS error	Cause: The HF16 trip indicates that a RTOS error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF17 Data processing error: Clock supplied to the control board is out of specification	Cause: The HF17 trip indicates that the clock supplied to the control board logic is out of specification. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF18 Data processing error: Internal flash memory has failed	Cause: The HF18 trip indicates that the internal flash memory has failed when writing option module parameter data. Remedy: Hardware fault – Contact the supplier of the drive.
HF19 Data processing error: CRC check on the firmware has failed	Cause: The HF19 trip indicates that the CRC check on the drive firmware has failed. Remedy: Re-program the drive. Hardware fault – Contact the supplier of the drive.
HF20 Data processing error: ASIC is not compatible with the hardware	Cause: The HF20 trip indicates that 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: A hardware fault has occurred. Remedy: If this trip occurs please consult the drive supplier.
8 Inductance Inductance measurement out of range or motor saturation not detected	Cause: Occurs in RFC-S mode. The drive detected that motor inductances are not suitable for the operation, the ratio/difference between Ld and Lq is too small, or the saturation characteristic cannot be measured. Remedy: Sub-trip 1 & 2: Ensure that RFC Low Speed Mode (05.064) is set to Non-salient (1), Current (2) or Current No test (3). Sub-trip 3: None. The trip acts as a warning. 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 The regen inductor has overloaded	Cause: In Regen mode, thermal overload detected based on Rated Current and Thermal Time Constant. The drive trips when the thermal accumulator reaches 100%. Remedy: Check the load / current through the inductor has not changed. Ensure the Rated Current (Pr 05.007) is not zero.
103 Inter-connect Multi-Power module drive interconnection cable error	Cause: Multi-power module drive interconnection cable error. Indicates which power module detected the fault. Also initiated if communication fails when a rectifier signals a fault or a trip is reset. Remedy: Check inter-connection cables between modules. Check communication status between power modules.
26 I/O Overload Digital output overload	Cause: Total current drawn from 24 V user supply or digital output has exceeded the limit. Max output per digital output is 100 mA, or combined limits exceeded. Remedy: Check total loads on digital outputs. Check control wiring is correct. Check output wiring is undamaged.
160 Island Island condition detected in regen mode	Cause: AC mains is no longer present and the inverter would be an ‘islanded’ power supply if it continued to operate. Remedy: Check the supply / supply connections to the regen drive.
34 Keypad Mode Keypad has been removed when the drive is receiving the speed reference from the keypad	Cause: Drive is in keypad mode and the keypad has been removed or disconnected. Remedy: Re-install keypad and reset. Change Reference Selector (01.014) to select the reference from another source.
39 Line Sync Synchronization to the power supply has been lost	Cause: The inverter has lost synchronization with the AC supply in Regen mode. Remedy: Check the supply / supply connections to the regen drive.
38 Low Load The load on the drive has fallen below the low load detection level	Cause: Percentage Load falls below the Low Load Detection Level while low load detector is active. Remedy: Check the load on the motor has not changed.
20 Motor Too Hot Output current overload timed out (I²t)	Cause: Motor thermal overload based on Rated Current and Motor Thermal Time Constant. Drive trips when accumulator reaches 100%. Remedy: Ensure the load is not jammed / sticking. Check the load on the motor has not changed. If seen during auto-tune in RFC-S mode, ensure motor Rated Current is ≤ Heavy duty current rating of drive. Tune the Rated Speed (RFC-A mode only). Check feedback signal for noise. Ensure the motor rated current is not zero. This trip can be disabled by setting thermal protection mode Pr 04.016 to 1.
176 Name Plate Electronic nameplate transfer has failed	Cause: Electronic nameplate transfer between drive and motor failed (Memory space, Communication, Transfer failure, or Checksum error). Remedy: Ensure that the device encoder memory has at least 128 bytes to store nameplate data. When writing motor object, ensure encoder memory has at least 256 bytes. Ensure feedback option module is installed if transferring between option module and encoder. Check if encoder has been initialized in Position Feedback Initialized. Verify the encoder wiring.
101 OHt Brake Braking IGBT over-temperature	Cause: Braking IGBT over-temperature detected based on software thermal model. Remedy: Check braking resistor value is greater than or equal to the minimum resistance value.
23 OHt Control Control stage over temperature	Cause: Control stage over-temperature detected via thermistors (Control board or I/O board). Remedy: Check enclosure / drive fans are still functioning correctly. Check enclosure ventilation paths. Check enclosure door filters. Increase ventilation. Reduce the drive switching frequency. Check ambient temperature.
27 OHt dc bus DC bus over temperature	Cause: DC bus component over temperature based on software thermal model (includes effects of output current and DC bus ripple). Remedy: Check the AC supply voltage balance and levels. Check DC bus ripple level. Reduce duty cycle or motor load. Check output current stability. If unstable: Check motor map settings. Disable slip compensation or dynamic V to F. Select fixed boost or high stability space vector modulation. Perform rotating auto-tune (disconnect load). Check encoder signals for noise or mechanical coupling.
21 OHt Inverter Inverter over temperature based on thermal model	Cause: IGBT junction over-temperature detected based on software thermal model (Inverter thermal model or Braking IGBT 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.
OHt Power (Trip 22) Power stage over temperature	Cause: A power stage over-temperature has been detected. The thermistor location is identified by the sub-trip. Remedy: Check enclosure / drive fans are still functioning correctly. Force the heatsink fans to run at maximum speed. Check enclosure ventilation paths. Check enclosure door filters. Increase ventilation. Reduce the drive switching frequency. Reduce duty cycle. Increase acceleration / deceleration rates. Use S ramp (Pr 02.006). Reduce motor load. Check the derating tables and confirm the drive is correctly sized for the application. Use a drive with larger current / power rating.
OI ac (Trip 3) Instantaneous output over current detected	Cause: The instantaneous drive output current has exceeded VM_DRIVE_CURRENT[MAX]. This trip cannot be reset until 10s after the trip was initiated. Remedy: Acceleration/deceleration rate is too short. If seen during auto-tune reduce the voltage boost. Check for short circuit on the output cabling. Check integrity of the motor insulation using an insulation tester. Check feedback device wiring. 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).
OI Brake (Trip 4) Braking IGBT over current detected	Cause: Over current has been detected in braking IGBT or braking IGBT protection has been activated. Cannot be reset until 10s after trip. Remedy: Check brake resistor wiring. Check braking resistor value is greater than or equal to the minimum resistance value. Check braking resistor insulation.
OI dc (Trip 109) Power module over current detected from IGBT on state voltage monitoring	Cause: Short circuit protection for the drive output stage has been activated. Cannot be reset until 10s after trip. Remedy: Disconnect the motor cable at the drive end and check the motor and cable insulation with an insulation tester. Replace the drive.
Option Disable (Trip 215) Option module does not acknowledge during drive mode changeover	Cause: The option module did not acknowledge to the drive that communications with the drive has been stopped during the drive mode changeover within the allocated time. Remedy: Reset the trip. If the trip persists, replace the option module.
Out Phase Loss (Trip 98) Output phase loss detected	Cause: Phase loss has been detected at the drive output. Remedy: Check motor and drive connections. To disable the trip set Output Phase Loss Detection Enable (06.059) = 0.
Over Speed (Trip 7) Motor speed has exceeded the over speed threshold	Cause: The motor speed (or Output Frequency in open loop) has exceeded the threshold set in Over Speed Threshold (03.008). 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 (RFC-A, RFC-S modes only). If an SSI encoder is being used set Pr 03.047 to 1.
Over Volts (Trip 2) DC bus voltage has exceeded the peak level or maximum continuous level	Cause: The DC bus voltage has exceeded the instantaneous over voltage threshold or the maximum DC bus setpoint for 15s. Remedy: Increase deceleration ramp (Pr 00.004). Decrease the braking resistor value (staying above the minimum value). Check nominal AC supply level. Check for supply disturbances which could cause the DC bus to rise. Check motor insulation using an insulation tester.
Phase Loss (Trip 32) Supply phase loss	Cause: The drive has detected an input phase loss or large supply imbalance from the supply or DC bus ripple monitoring. Remedy: Check the AC supply voltage balance and level at full load. Check the DC bus ripple level with an isolated oscilloscope. Check the output current stability. Check for mechanical resonance with the load. Reduce the duty cycle. Reduce the motor load. Disable the phase loss detection, set Pr 06.047 to 2.
Phasing Error (Trip 198) RFC-S mode phasing failure due to incorrect phase angle	Cause: The phase offset angle is incorrect, position feedback is being used and the drive is unable to control the motor correctly. Remedy: Check the encoder wiring. Check the encoder signals for noise with an oscilloscope. Check the encoder mechanical coupling. Perform an auto-tune to measure the encoder phase angle or manually enter the correct phase angle into Pr 03.025. Ensure that the motor parameters are set-up correctly. Reduce the speed controller gains.
Power Comms (Trip 90) Communication has been lost / errors detected	Cause: A communications problem within the power system of the drive (between power, control, and rectifier modules). Remedy: Hardware fault – Contact the supplier of the drive.
Power Data (Trip 220) Power system configuration data error	Cause: There is an error in the configuration data stored in the power system. Remedy: Hardware fault – Contact the supplier of the drive.
Power Down Save (Trip 37) Power down save error	Cause: An error has been detected in the power down save parameters saved in non-volatile memory. Remedy: Perform a 1001 save in Pr mm.000 to ensure that the trip doesn’t occur the next time the drive is powered up.
PSU (Trip 5) Internal power supply fault	Cause: One or more internal power supply rails are outside limits or overloaded. Remedy: Remove any option modules and perform a reset. Remove encoder connection and perform a reset. Hardware fault within the drive – return the drive to the supplier.
PSU 24V (Trip 9) 24V internal power supply overload	Cause: The total user load of the drive and option modules has exceeded the internal 24 V power supply limit. Remedy: Reduce the load and reset. Provide an external 24 V power supply on control terminal 2. Remove all option modules.
Rating Mismatch (Trip 223) Power stage recognition: Multi module voltage or current rating mismatch	Cause: There is a voltage rating or current rating mismatch in a multi-module drive system. 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.
Rectifier Set-up (Trip 94) A rectifier has not been set-up correctly in a multi-power module system	Cause: A rectifier has not been set-up correctly in a multi-power module system. Remedy: Check the inter-power module wiring.
Resistance (Trip 33) Measured resistance has exceeded the parameter range	Cause: Either the value being used for motor stator resistance is too high or that 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 (for the presently selected motor map). 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 the output current waveforms with an oscilloscope. Replace the motor.
Slot4 Different (Trip 254) Ethernet interface in slot 4 has changed	Cause: The Ethernet interface in slot 4 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 Slot4 Error	Cause: The Ethernet interface in slot 4 on the drive has detected an error. The reason for the trip can be identified by the sub-trip number (e.g., Link Loss, Timeout, Init 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: The Ethernet interface in slot 4 cannot operate. The reason for the error can be identified by the sub-trip number. Remedy: Ensure the Ethernet interface is installed correctly. Hardware fault – Contact the supplier of the drive.
253 Slot4 Not Fitted	Cause: The Ethernet interface in slot 4 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 Slot4 Watchdog	Cause: The Ethernet interface installed in slot 4 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 on the drive is a different type to that installed when parameters were last saved on the drive. Remedy: Turn off the power, ensure the correct option modules are installed in the correct option slots and re-apply the power. Confirm that the currently installed option module is correct, ensure option module parameters are set correctly and perform a user save in Pr mm.000.
202, 207, 212 SlotX Error	Cause: The option module in option slot X on the drive has detected an error. The reason for the error can be identified by the sub-trip number. Remedy: See the relevant Option Module User Guide for details of the trip.
200, 205, 210 SlotX HF	Cause: The option module in option slot X cannot operate. The possible causes of the trip 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	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	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 i.e. stored HF.17. Remedy: Enter 1299 in Pr mm.000 and press reset to clear the trip.
227 Sub-array RAM	Cause: 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 parameters and configuration. Check user program image size.
218 Temp Feedback	Cause: An internal thermistor has failed. The thermistor location can be identified by the sub-trip number (e.g., Control PCB, I/O PCB, Power System). Remedy: Hardware fault – Contact the supplier of the drive.
10 Th Brake Res	Cause: The brake 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 Th Short Circuit (Motor thermistor short circuit)	Cause: The motor thermistor connected to the drive is short circuit or low impedance i.e. < 50 Ω. The location of the trip can be identified by the sub-trip number: 3: Analog input 3 4: Position feedback interface 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. The location of the trip can be identified by the sub-trip number: 3: Analog input 3 4: Position feedback interface Remedy: Check motor temperature. Check Threshold Level (07.048). Check thermistor continuity.
110 Undefined (Drive has tripped and the cause is Undefined)	Cause: The power system has generated but did not identify the trip from the power system. The cause of the trip is unknown. Remedy: Hardware fault – return the drive to the supplier.
91 User 24V (User 24 V supply is not present)	Cause: Initiated if User Supply Select (Pr 06.072) = 1, or Low Under Voltage Threshold Select (06.067) = 1, or Backup Supply Mode Enable (06.068) = 1, AND no user 24 V supply is present on control terminals 1 and 2. Remedy: Ensure the user 24 V supply is present on control terminals 1 (0V) and 2 (24V).
249 User Program (On board user program error)	Cause: An error has been detected in the onboard user program image. The reason can be identified by the sub-trip number: 1: Divide by zero 2: Undefined trip 3: Attempted fast parameter access set-up with non-existent parameter 4: Attempted access to non-existent parameter 5: Attempted write to read-only parameter 6: Attempted an over-range write 7: Attempted read from write-only parameter 30-33: Image failure (CRC, length, RAM, OS function, ID code) 40: Timed task not completed in time 53: Customized menu table changed 80/81: Image not compatible with control board/serial number 100-102: Pointer/Array access violations 200: Divide by zero (denominator zero) 201-204: Parameter access errors Remedy: Review sub-trip code to identify specific coding error. If sub-trip 53: Save parameters to stop trip occurring. If sub-trip 40: Check loop times in user code. Reload valid user program image.
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: Error detected in the user save parameters saved in non-volatile memory (e.g., power removed while saving). 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 Voltage Range (Supply voltage out of range in Regen mode)	Cause: Regen Minimum Voltage (03.026) is set to non-zero and supply voltage is outside range defined by Regen Maximum Voltage (03.027) and Minimum (03.026) for > 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 has been enabled and has timed out. Once Pr 06.042 bit 14 is changed from 0 to 1, it must be repeated every 1s. Remedy: Update the watchdog bit (Pr 06.042 bit 14) repeatedly (every 1s) to prevent tripping. Watchdog is disabled when trip occurs and must be re-enabled if required when trip is reset.
Error 1 Insufficient Drive Memory	Cause: There is not enough drive memory requested by all the option modules. Remedy: Power down drive and remove some of the option modules until the message disappears.
Error 2 Option Module 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 Option Module Initialization 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.
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 %.
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 in progress	Cause: The autotune procedure has been initialized and an autotune is 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	Description: 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. Drive Output Stage: Disabled
Ready	Description: 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. Drive Output Stage: Disabled
Stop	Description: The drive is stopped / holding zero speed. Drive Output Stage: Enabled
Run	Description: The drive is active and running. Drive Output Stage: Enabled
Scan	Description: The drive is enabled in Regen mode and is trying to synchronize to the supply. Drive Output Stage: Enabled
Supply Loss	Description: Supply loss condition has been detected. Drive Output Stage: Enabled
Deceleration	Description: The motor is being decelerated to zero speed / frequency because the final drive run has been deactivated. Drive Output Stage: Enabled
dc injection	Description: The drive is applying dc injection braking. Drive Output Stage: Enabled
Position	Description: Positioning / position control is active during an orientation stop. Drive Output Stage: Enabled
Trip	Description: The drive has tripped and no longer controlling the motor. The trip code appears in the lower display. Drive Output Stage: Disabled
Active	Description: The regen unit is enabled and synchronized to the supply. Drive Output Stage: Enabled
Under Voltage	Description: The drive is in the under voltage state either in low voltage or high voltage mode. Drive Output Stage: Disabled
Heat	Description: The motor pre-heat function is active. Drive Output Stage: Enabled
Phasing	Description: The drive is performing a ‘phasing test on enable’. Drive Output Stage: Enabled
Booting Parameters	Status: Parameters are being loaded. Description: Drive parameters are being loaded from a NV Media Card.
Booting User Program	Status: User program being loaded. Description: User program is being loaded from a NV Media Card to the drive.
Booting Option Program	Status: User program being loaded. Description: User program is being loaded from a NV Media Card to the option module in slot X.
Writing To NV Card	Status: Data being written to NV Media Card. Description: Data is being written to a NV Media 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	Status: Waiting for power stage. Description: The drive is waiting for the processor in the power stage to respond after power-up.
Waiting For Options	Status: Waiting for an option module. Description: The drive is waiting for the Options Modules to respond after power-up.
Uploading From Options	Status: Loading parameter database. Description: At power-up it may be necessary to update the parameter database held by the drive because an option module has changed or because an applications module has requested changes to the parameter structure. This may involve data transfer between the drive an option modules.