Nidec & Control Technique Unidrive M600 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:
|
| 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:
|
| 219 An Output Calib | Cause: The zero offset calibration of one or both of the analogue 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/Term 9; Sub-trip 2: Output 2/Term 10). Remedy:
|
| 217 App Menu Changed | Cause: The customization table for an application menu has changed (Sub-trips: 1=Menu 18, 2=Menu 19, 3=Menu 20). If more than one menu has changed the lowest menu has priority. Remedy:
|
| 11 Autotune 1 | Cause: Position feedback did not change or required speed could not be reached. Sub-trip 1: Position feedback did not change during rotating autotune. Sub-trip 2: Motor did not reach required speed. Remedy:
|
| 12 Autotune 2 | Cause: Position feedback direction incorrect. Sub-trip 1: Direction incorrect during rotating autotune. Sub-trip 2: SINCOS encoder comms position rotating opposite to sine wave. Remedy:
|
| 13 Autotune 3 | Cause: Measured inertia has exceeded the parameter range or commutation signals changed in wrong direction. (Sub-trip 1: Inertia exceeded range; Sub-trip 2: Commutation signals wrong direction; Sub-trip 3: Load test unable to identify inertia). Remedy:
|
| 17 Autotune 7 | Cause: Motor number of poles or position feedback resolution have been set up incorrectly where position feedback is being used. Remedy:
|
| 18 Autotune Stopped | Cause: The drive was prevented from completing an autotune test because either the drive enable or the drive run were removed. Remedy:
|
| 19 Brake R Too Hot | Cause: Braking resistor overload timed out (I²t). The Braking Resistor Thermal Accumulator (10.039) has reached 100%. Remedy:
|
| 185 Card Access | Cause: NV Media Card Write fail. The drive was unable to access the NV Media Card, or file corruption occurred during data transfer. Remedy:
|
| 177 Card Boot | Cause: The Menu 0 parameter modification cannot be saved to the NV Media Card. Occurs if a write is initiated (exiting edit mode) and Pr 11.042 is set to Auto or Boot, but the necessary boot file does not exist. Remedy:
|
| 178 Card Busy | Cause: NV Media Card cannot be accessed as it is being accessed by an option module. No data is transferred. Remedy:
|
| 188 Card Compare | Cause: NV Media Card file/data is different to the one in the drive. A compare trip is initiated if the parameters on the NV Media Card are different to the drive. Remedy:
|
| 179 Card Data Exists | Cause: Attempt made to store data on a NV Media Card in a data block which already contains data. Remedy:
|
| 187 Card Drive Mode | Cause: NV Media Card parameter set not compatible with current drive mode. The operating mode in the data block is outside the allowed range of operating modes. Remedy:
|
| 182 Card Error | Cause: NV Media Card data structure error. (Sub-trip 1: Required folder/structure missing; Sub-trip 2: File corrupted; Sub-trip 3: Duplicate file IDs). Remedy:
|
| 184 Card Full | Cause: NV Media Card full. There is not enough space left on the card to create a data block. Remedy:
|
| 183 Card No Data | Cause: An attempt has been made to access non-existent file or block on a NV Media Card. Remedy:
|
| 180 Card Option | Cause: Option modules installed are different between source and destination drive. The data for the option modules that are different will be set to default. Remedy:
|
| 175 Card Product | Cause: NV Media Card data blocks are not compatible with the drive derivative (11.028) or Product Type (11.063). (Sub-trips 1, 2, and 3 detail specific mismatches or corruption). Remedy:
|
| 186 Card Rating | Cause: The voltage and / or current rating of the source and destination drives are different. Specific parameters with the RA attribute may not be transferred. Remedy:
|
| 181 Card Read Only | Cause: NV Media Card has the Read Only bit set. An attempt was made to modify a read-only card or block. Remedy:
|
| 174 Card Slot | Cause: Option module application program transfer has failed. The option module did not respond correctly, possibly due to wrong slot. Remedy:
|
| 111 Configuration | Cause: The Number Of Power Modules Detected (11.071) does not match the previous value stored, or the number of external rectifiers does not match the expected count. Remedy:
|
| 35 Control Word | Cause: Trip initiated by setting bit 12 on the control word in Pr 06.042 when the control word is enabled (Pr 06.043 = On). Remedy:
|
| 225 Current Offset | Cause: The current feedback offset is too large to be trimmed correctly. Remedy:
|
| 97 Data Changing | Cause: A user action or file system write is active that is changing drive parameters while the drive is enabled. (e.g., loading defaults, changing drive mode, transferring data). Remedy:
|
| 247 Derivative ID | Cause: There is a problem with the identifier associated with derivative image which customizes the drive (Image erased, ID out of range, or image changed). Remedy:
|
| 248 Derivative Image | Cause: An error has been detected in the derivative image. Sub-trips indicate specific reason (e.g., Option module not allowed, required option module missing). Remedy:
|
| 199 Destination | Cause: Destination output parameters of two or more logic functions are writing to the same parameter. Remedy:
|
| 224 Drive Size | Cause: The control PCB has not recognized the drive size of the power circuit to which it is connected. Remedy:
|
| 31 EEPROM Fail | Cause: Default parameters have been loaded due to corrupted save data (User Save or Power Down Save). Sub-trips indicate CRC failure or hardware changes. Remedy:
|
| 197 Encoder 9 | Cause: Position feedback source selected in Pr 03.026 (or Pr 21.021) is not valid or the option slot does not have a feedback option module installed. Remedy:
|
| 6 External Trip | Cause: Initiated by writing a value of 6 in Pr 10.038, or Safe Torque Off input is low when expected high (based on Trip Mode). Remedy:
|
| HF01 Data processing error: CPU address error | Cause: A CPU address error has occurred on the control PCB. Remedy:
|
| HF02 Data processing error: DMAC address error | Cause: A DMAC address error has occurred. Control PCB failure. Remedy:
|
| HF03 Data processing error: Illegal instruction | Cause: An illegal instruction has occurred. Control PCB failure. Remedy:
|
| HF04 Data processing error: Illegal slot instruction | Cause: An illegal slot instruction has occurred. Control PCB failure. Remedy:
|
| HF05 Data processing error: Undefined exception | Cause: An undefined exception error has occurred. Control PCB failure. Remedy:
|
| HF06 Data processing error: Reserved exception | Cause: A reserved exception error has occurred. Control PCB failure. Remedy:
|
| HF07 Data processing error: Watchdog failure | Cause: A watchdog failure has occurred. Control PCB failure. Remedy:
|
| HF08 Data processing error: CPU Interrupt crash | Cause: A CPU interrupt crash has occurred. Control PCB failure. Remedy:
|
| HF09 Data processing error: Free store overflow | Cause: A free store overflow has occurred. Control PCB failure. Remedy:
|
| HF10 Data processing error: Parameter routing system error | Cause: A Parameter routing system error has occurred. Control PCB failure. Remedy:
|
| HF11 Data processing error: Access to EEPROM failed | Cause: Access to the drive EEPROM has failed. Control PCB failure. Remedy:
|
| HF12 Data processing error: Main program stack overflow | Cause: The main program stack overflow has occurred. The stack can be identified by the sub-trip number. This trip indicates that the control PCB on the drive has failed. Remedy:
|
| HF13 Data processing error: Firmware incompatible with hardware | Cause: The drive firmware is not compatible with the hardware. This trip indicates that the control PCB on the drive has failed. Remedy:
|
| HF14 Data processing error: CPU register bank error | Cause: A CPU register bank error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy:
|
| HF15 Data processing error: CPU divide error | Cause: A CPU divide error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy:
|
| HF16 Data processing error: RTOS error | Cause: A RTOS error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy:
|
| HF17 Data processing error: Clock supplied to the control board is out of specification | Cause: 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:
|
| HF18 Data processing error: Internal flash memory has failed | Cause: The internal flash memory has failed when writing option module parameter data. The reason for the trip can be identified by the sub-trip number. Remedy:
|
| HF19 Data processing error: CRC check on the firmware has failed | Cause: The CRC check on the drive firmware has failed. Remedy:
|
| HF20 Data processing error: ASIC is not compatible with the hardware | Cause: The ASIC version is not compatible with the drive firmware. The ASIC version can be identified from the sub-trip number. Remedy:
|
| HF23 to HF25 Hardware fault | Cause: Unspecified hardware fault (HF23, HF24, or HF25). Remedy:
|
| 26 I/O Overload: Digital output overload | Cause: The total current drawn from 24 V user supply or from the digital output has exceeded the limit. Conditions include max output from one digital output > 100 mA, or combined outputs exceeding 100 mA. Remedy:
|
| 8 Inductance: Motor inductances are not suitable | Cause: Occurs in RFC-S mode when the drive has detected that the motor inductances are not suitable for the operation being attempted (ratio or difference between Ld and Lq is too small or saturation characteristic cannot be measured). Remedy:
|
| 93 Inductor Too Hot: The regen inductor has overloaded | Cause: In Regen mode, this trip indicates a regen inductor thermal overload based on the Rated Current (Pr 05.007) and the Inductor Thermal Time Constant (Pr 04.015). Remedy:
|
| 103 Inter-connect: Multi-power module drive interconnection cable error | Cause: A power module has detected a fault (identified by sub-trip xx.0.00). Also initiated if communication fails either when a rectifier signals a fault or a trip is reset. Remedy:
|
| 160 Island: Island condition detected in regen mode | Cause: The AC mains is no longer present and the inverter would be on ‘islanded’ power supply if it continued to operate. Remedy:
|
| 34 Keypad Mode: Keypad has been removed | Cause: The drive is in keypad mode and the keypad has been removed or disconnected from the drive. Remedy:
|
| 39 Line Sync: Synchronization to the power supply has been lost | Cause: The inverter has lost the synchronization with the ac supply in Regen mode. Remedy:
|
| 20 Motor Too Hot: Output current overload timed out (I²t) | Cause: Motor thermal overload based on the rated current (Pr 05.007) and motor thermal time constant. The drive trips when Motor Too Hot accumulator reaches 100%. Remedy:
|
| 176 Name Plate: Electronic nameplate transfer has failed | Cause: An electronic name plate transfer between the drive and the motor has failed. Reasons include not enough memory, communication failure, or checksum failure. Remedy:
|
| 101 OHt Brake: Braking IGBT over-temperature | Cause: Braking IGBT over-temperature has been detected based on software thermal model. Remedy:
|
| 23 OHt Control: Control stage over temperature | Cause: Control stage over-temperature has been detected. The sub-trip identifies the specific location (Control board thermistors or I/O board thermistor). Remedy:
|
| 27 OHt dc bus (DC bus over temperature) | Cause: A DC bus component over temperature based on a software thermal model has been detected. This includes the effects of output current and DC bus ripple. Remedy:
|
| 21 OHt Inverter (Inverter over temperature) | Cause: An IGBT junction over-temperature has been detected based on a firmware thermal model. Remedy:
|
| 22 OHt Power (Power stage over temperature) | Cause: A power stage over-temperature has been detected. The sub-trip indicates which thermistor is indicating the over-temperature. Remedy:
|
| 3 OI ac (Instantaneous output over current) | 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:
|
| 4 OI Brake (Braking IGBT over current) | Cause: Over current has been detected in braking IGBT or braking IGBT protection has been activated. This trip cannot be reset until 10 s after the trip was initiated. Remedy:
|
| 109 OI dc (Power module over current) | Cause: Short circuit protection for the drive output stage has been activated. Detected from IGBT on state voltage monitoring. Remedy:
|
| 92 OI Snubber (Snubber over-current detected) | Cause: An over-current condition has been detected in the rectifier snubber circuit. Remedy:
|
| 215 Option Disable (Option module error) | Cause: During drive mode changeover option modules must acknowledge that they have stopped accessing the communications system; if an option module does not do this in the allowed time then this trip is produced. Remedy:
|
| 98 Out Phase Loss (Output phase loss detected) | Cause: A phase loss has been detected at the drive output. Sub-trips (1, 2, 3) indicate which phase (U, V, W) is disconnected. Remedy:
|
| 7 Over Speed (Motor speed limit exceeded) | Cause: Motor speed has exceeded the threshold set in Over Speed Threshold (03.008) or Pr 01.006. Remedy:
|
| 2 Over Volts (DC bus voltage exceeded) | Cause: The DC bus voltage has exceeded the peak level or maximum continuous level for 15 seconds. Remedy:
|
| 32 Phase Loss | Cause: This trip indicates that the drive has detected an input phase loss or large supply imbalance. Phase loss can be detected directly from the supply or by monitoring DC bus ripple. Remedy:
|
| 198 Phasing error | Cause: This indicates that the phase offset angle in Position Feedback Phase Angle (03.025) is incorrect if position feedback is being used and the drive is unable to control the motor correctly. Remedy:
|
| 90 Power Comms | Cause: A Power Comms trip indicates a communications problem within the power system of the drive. The reason for the trip can be identified by the sub-trip number (often excessive communications errors detected by the rectifier module). Remedy:
|
| 220 Power Data | Cause: The Power Data trip indicates that there is an error in the configuration data stored in the power system (e.g., no data table, table size incorrect, CRC error, or version mismatch). Remedy:
|
| 37 Power Down Save | Cause: The Power Down Save trip indicates that an error has been detected in the power down save parameters saved in non-volatile memory. Remedy:
|
| 5 PSU | Cause: The PSU trip indicates that one or more internal power supply rails are outside limits or overloaded (Internal power supply overload). Remedy:
|
| 9 PSU 24V | Cause: The total user load of the drive and option modules has exceeded the internal 24 V power supply limit. The user load consists of the drive digital outputs and main encoder supply. Remedy:
|
| 223 Rating Mismatch | Cause: The Rating Mismatch trip indicates that there is a voltage rating or current rating mismatch in a multi-module drive system. A mixture of power modules with different voltage or current ratings is not allowed. Remedy:
|
| 94 Rectifier Set-up | Cause: A rectifier has not been set-up correctly in a multi-power module system. Remedy:
|
| 33 Resistance | Cause: This trip indicates that 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:
|
| 216 Slot App Menu | Cause: The Slot App Menu trip indicates that more than one option slot has requested to customize the application menus 18, 19 and 20. Remedy:
|
| 204, 209, 214 SlotX Different | Cause: The SlotX Different trip indicates that the option module in option slot X on the drive is a different type to that installed when parameters were last saved on the drive. Remedy:
|
| 202, 207, 212 SlotX Error | Cause: The SlotX Error trip indicates that the option module in option slot X on the drive has detected an error. Remedy:
|
| 200, 205, 210 SlotX HF | Cause: The SlotX HF trip indicates that the option module in option slot X on the drive has indicated a hardware fault. Remedy:
|
| 203, 208, 213 SlotX Not Fitted | Cause: The SlotX Not Fitted trip indicates that the option module in option slot X on the drive has been removed since the last power up. Remedy:
|
| 201, 206, 211 SlotX Watchdog | Cause: The SlotX Watchdog trip indicates that the option module installed in Slot X has started the option watchdog function and then failed to service the watchdog correctly. Remedy:
|
| 226 Soft Start | Cause: The Soft Start trip indicates that the soft start relay in the drive failed to close or the soft start monitoring circuit has failed. Remedy:
|
| 221 Stored HF | Cause: The Stored HF trip indicates that a hardware trip (HF01 – HF19) has occurred and the drive has been power cycled. The sub-trip number identifies the HF trip (i.e. stored HF.17). Remedy:
|
| 227 Sub-array RAM | Cause: The Sub-array RAM trip indicates that an option module, derivative image or user program image has requested more parameter RAM than is allowed. The RAM allocation is checked in order of resulting sub-trip numbers. Remedy:
|
| 218 Temp Feedback | Cause: The Temp Feedback trip indicates that an internal thermistor has failed. The thermistor location can be identified by the sub-trip number (01: Control board thermistor 1, 02: Control board thermistor 2, 03: I/O board thermistor). Remedy:
|
| 10 Th Brake Res | Cause: The Th Brake Res is initiated if 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:
|
| 25 Th Short Circuit | Cause: This trip indicates that a temperature sensor connected to an analogue input or terminal 15 on the position feedback interface has a low impedance (i.e. < 50 Ω). Remedy:
|
| 24 Thermistor | Cause: The Thermistor trip indicates that the motor thermistor connected to terminal 8 (analog input 3) or terminal 15 (encoder terminal) has indicated a motor over temperature. Remedy:
|
| 110 Undefined | Cause: The Undefined trip indicates that the power system has generated but did not identify the trip the power system. The cause of the trip is unknown. Remedy:
|
| 91 User 24V | Cause: A User 24 V trip is initiated if User Supply Select (Pr 06.072) is set to 1 or Low Under Voltage Threshold Select (06.067) = 1 and no user 24 V supply is present on control terminals 1 and 2. Remedy:
|
| 249 User Program | Cause: The User Program trip indicates that an error has been detected in the onboard user program image. The reason for the trip can be identified by the sub-trip number (e.g., 1: Divide by zero, 2: Undefined trip, 30: Image CRC failed). Remedy:
|
| 96 User Prog Trip | Cause: This trip can be initiated from within an onboard user program using a function call which defines the sub-trip number. Remedy:
|
| 36 User Save | Cause: The User Save trip indicates that an error has been detected in the user save parameters saved in non-volatile memory (e.g., power removed during save). Remedy:
|
| 41-89 112-159 User Trip | Cause: These trips are not generated by the drive and are to be used by the user to trip the drive through an application program. Remedy:
|
| 40 User Trip 40 | Cause: Indicates that the motor rated current (Pr 05.007) or motor rated speed (Pr 05.008) was not recognized as being a valid value for a Dyneo LSRPM motor. Remedy:
|
| 169 Voltage Range | Cause: The Voltage Range trip is initiated if the Regen Minimum Voltage (03.026) is set to a non-zero value and the supply voltage is outside the range defined by Regen Maximum/Minimum Voltage for more than 100 ms. Remedy:
|
| 30 Watchdog | Cause: The Watchdog trip indicates that the control word has been enabled and has timed out. Remedy:
|
| Brake Resistor Alarm Indication | Cause: Brake resistor overload. Braking Resistor Thermal Accumulator (10.039) in the drive has reached 75.0 % of the value at which the drive will trip. |
| Motor Overload Alarm Indication | 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 Alarm Indication | Cause: Regen inductor overload. 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 Alarm Indication | Cause: Drive over temperature. Percentage Of Drive Thermal Trip Level (07.036) in the drive is greater than 90 %. |
| Auto Tune Alarm Indication | Cause: The autotune procedure has been initialized and an autotune in progress. |
| Limit Switch Alarm Indication | Cause: Limit switch active. Indicates that a limit switch is active and that is causing the motor to be stopped. |
| Error 1 Programming Error | Cause: There is not enough drive memory requested by all the option modules. Remedy:
|
| Error 2 Programming Error | Cause: At least one option module did not acknowledge the reset request. Remedy:
|
| Error 3 Programming Error | Cause: The boot loader failed to erase the processor flash. Remedy:
|
| Error 4 Programming Error | Cause: The boot loader failed to program the processor flash. Remedy:
|
| Error 5 Programming Error | Cause: One option module did not initialize correctly. Option module did not set Ready to Run flag. Remedy:
|