Nidec & Control Technique Powerdrive F300 Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 28 An Input 1 Loss | Cause: An Input 1 Loss trip indicates that a current loss was detected in current mode on Analog input 1 (Terminal 5, 6). In 4-20 mA and 20-4 mA modes loss of input is detected if the current falls below 3 mA. Remedy:
|
|||||||||
| 29 An Input 2 Loss | Cause: An Input 2 Loss indicates that a current loss was detected in current mode on Analog input 2 (Terminal 7). In 4-20 mA and 20-4 mA modes loss of input is detected if the current falls below 3 mA. Remedy:
|
|||||||||
| 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, possibly due to a wiring error. Sub-trip 1: Output 1 failed (Terminal 9) Sub-trip 2: Output 2 failed (Terminal 10) Remedy:
|
|||||||||
| 217 App Menu Changed | Cause: The App Menu Changed trip indicates that the customization table for an application menu has changed. The menu that has been changed can be identified by the sub-trip number (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: The drive has tripped during an autotune. The cause of the trip can be identified from the sub-trip number. 1: The position feedback did not change when position feedback is being used during rotating autotune. 2: The motor did not reach the required speed during rotating autotune or mechanical load measurement. Remedy:
|
|||||||||
| 12 Autotune 2 | Cause: The drive has tripped during a rotating autotune (Position feedback direction incorrect). 1: Position feedback direction is incorrect when position feedback is being used. 2: A SINCOS encoder with comms is being used and comms position is rotating in opposite direction to sine wave. Remedy:
|
|||||||||
| 13 Autotune 3 | Cause: Measured inertia has exceeded the parameter range or commutation signals changed in wrong direction during autotune. 1: Measured inertia exceeded parameter range. 2: Commutation signals changed in wrong direction. 3: Mechanical load test unable to identify motor inertia. Remedy:
|
|||||||||
| 17 Autotune 7 | Cause: An Autotune 7 trip is initiated during a rotating autotune, if the motor poles or the position feedback resolution have been set up incorrectly where position feedback is being used. Remedy:
|
|||||||||
| 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: The Brake R Too Hot indicates that braking resistor overload has timed out. Calculated using Braking Resistor Thermal Accumulator (10.039) when it reaches 100%. Remedy:
|
|||||||||
| 185 Card Access | Cause: The Card Access trip indicates that the drive was unable to access the NV Media Card. If the trip occurs during data transfer, the file being written may be corrupted. Remedy:
|
|||||||||
| 177 Card Boot | Cause: The Menu 0 parameter modification cannot be saved to the NV Media Card. This occurs when Pr 11.042 is set for auto/boot mode, but the necessary boot file has not been created on the card. Remedy:
|
|||||||||
| 178 Card Busy | Cause: The Card Busy trip indicates that an attempt has been made to access a file on NV Media Card, but the NV Media Card is already being accessed by an option module. Remedy:
|
|||||||||
| 188 Card Compare | Cause: A compare has been carried out between a file on the NV Media Card and the drive; the parameters are different. Remedy:
|
|||||||||
| 179 Card Data Exists | Cause: The Card Data Exists trip indicates that an attempt has been made to store data on a NV Media Card in a data block which already contains data. Remedy:
|
|||||||||
| 187 Card Drive Mode | Cause: The drive mode in the data block on the NV Media Card is different from the current drive mode, or the operating mode in the data block is outside the allowed range. Remedy:
|
|||||||||
| 182 Card Error | Cause: An error has been detected in the data structure on the card. 1: Required folder/file structure not present. 2: The <000> file is corrupted. 3: Two or more files in the Remedy:
|
|||||||||
| 184 Card Full | Cause: The Card Full trip indicates that an attempt has been made to create a data block on a NV Media Card, but there is not enough space left on the card. Remedy:
|
|||||||||
| 183 Card No Data | Cause: The Card No Data trip indicates that an attempt has been made to access non-existent file or block on a NV Media Card. Remedy:
|
|||||||||
| 180 Card Option | Cause: Parameter data or default difference data is being transferred from a NV Media Card to the drive, but the option module categories are different. This is a warning that data for option modules different will be set to default. Remedy:
|
|||||||||
| 175 Card Product | Cause: NV Media Card data blocks are not compatible with the drive derivative. If Drive Derivative (11.028) or Product Type (11.063) are different between the source and target drives. Remedy:
|
|||||||||
| 186 Card Rating | Cause: Parameter data is being transferred, but the current and/or voltage ratings are different between source and destination drives. This is a warning that rating specific parameters may not be transferred. Remedy:
|
|||||||||
| 181 Card Read Only | Cause: Attempt made to modify a read-only NV Media Card or a read-only data block. Remedy:
|
|||||||||
| 174 Card Slot | Cause: Transfer of an option module application program to or from an application module failed because the option module does not respond correctly. Remedy:
|
|||||||||
| 111 Configuration | Cause: The number of power modules installed is different from the modules expected. The Number Of Power Modules Detected (11.071) does not match the previous value stored. Or, the number of external rectifiers connected is less than defined by Number Of Rectifiers Expected (11.096). Remedy:
|
|||||||||
| 35 Control Word | Cause: Trip initiated from the Control Word (06.042). 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: Current feedback offset error. The current feedback offset is too large to be trimmed correctly. Remedy:
|
|||||||||
| 97 Data Changing | Cause: Drive parameters are being changed. A user action or file system write is active that is changing drive parameters while the drive has been commanded to enable (Drive Active 10.002 = 1). Actions include loading defaults, changing drive mode, or transferring data from NV media card. Remedy:
|
|||||||||
| 247 Derivative ID | Cause: There is a problem with the identifier associated with derivative image which customizes the drive. Sub-trip 1: Derivative image erased. Sub-trip 2: Identifier out of range. Sub-trip 3: Derivative image changed. Remedy:
|
|||||||||
| 248 Derivative Image | Cause: Derivative Image error. An error has been detected in the derivative image. The sub-trip number indicates the reason. (Sub-trips 1-52, 61-64, 70-74, 80-81 involve errors or option module incompatibilities). Remedy:
|
|||||||||
| 199 Destination | Cause: Two or more parameters are writing to the same destination parameter. Destination output parameters of two or more logic functions (Menus 5, 7, 8, 9, 12 or 14) within the drive are writing to the same parameter. Remedy:
|
|||||||||
| 224 Drive Size | Cause: Power stage recognition: Unrecognized drive size. 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. Data loss or corruption in non-volatile memory. Sub-trips indicate specifics (e.g., parameter database version changed, CRC failure, power stage hardware changed). Remedy:
|
|||||||||
| 197 Encoder 9 | Cause: Position feedback is selected from an option module slot which does not have a feedback option module installed. Position feedback source selected in Pr 03.026 is not valid. Remedy:
|
|||||||||
| 6 External Trip | Cause: An External trip is initiated. External Trip Mode (08.010) settings or Safe Torque Off input states. Can be initiated by writing a value of 6 in Pr 10.038. Remedy:
|
|||||||||
| HF01 Data processing error: CPU address error | Cause: A CPU address error has occurred. Control PCB failure. 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. 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. 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. Remedy:
|
|||||||||
HF23 to HF25 Hardware fault | Cause: General hardware fault detected. Remedy:
|
|||||||||
26 I/O Overload: Digital output overload | Cause: Total current drawn from 24 V user supply or digital output exceeded limit (Max 100mA per output or combined). Remedy:
|
|||||||||
8 Inductance: Motor inductances not suitable (RFC-S mode) | Cause: Drive detected motor inductances are not suitable for operation. Ratio/difference between Ld and Lq is too small or saturation characteristic cannot be measured. Remedy:
|
|||||||||
103 Inter-connect: Multi-power module drive interconnection cable error | Cause: Communication failure detected between power modules. A rectifier may have signaled a fault or a trip reset. Remedy:
|
|||||||||
34 Keypad Mode: Keypad removed while receiving speed reference | Cause: Drive is in keypad mode [Reference Selector = 4 or 6] and the keypad has been removed or disconnected. Remedy:
|
|||||||||
20 Motor Too Hot: Output current overload timed out (I²t) | Cause: Motor thermal overload based on rated current (Pr 05.007) and thermal time constant. Motor temperature reached 100%. Remedy:
|
|||||||||
176 Name Plate: Electronic nameplate transfer has failed | Cause: Transfer between drive and motor failed (Not enough memory, communication fail, transfer fail, or checksum fail). Remedy:
|
|||||||||
101 OHt Brake: Braking IGBT over-temperature | Cause: Braking IGBT over-temperature detected based on software thermal model. Remedy:
|
|||||||||
23 OHt Control: Control stage over temperature | Cause: Control stage over-temperature detected on control board thermistors or I/O board thermistor. Remedy:
|
|||||||||
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 ripple). Remedy:
|
|||||||||
21 OHt Inverter: Inverter over temperature based on thermal model | Cause: IGBT junction over-temperature detected based on firmware thermal model. Remedy:
|
|||||||||
| OHt dc bus (27) DC bus over temperature | Cause: A DC bus component over temperature has been detected based on a software thermal model. This includes the effects of the output current and DC bus ripple. Remedy:
|
|||||||||
| OHt Inverter (21) Inverter over temperature based on thermal model | Cause: An IGBT junction over-temperature has been detected based on a firmware thermal model. Sub-trip 100 indicates Inverter thermal model; Sub-trip 300 indicates Braking IGBT thermal model. Remedy:
|
|||||||||
| OHt Power (22) Power stage over temperature | Cause: A power stage over-temperature has been detected. The sub-trip “xxyzz” indicates which thermistor is indicating the over-temperature. Remedy:
|
|||||||||
| OI ac (3) Instantaneous output over current detected | Cause: The instantaneous drive output current has exceeded VM_DRIVE_CURRENT_MAX. This trip cannot be reset until 10s after the trip was initiated. Remedy:
|
|||||||||
| OI Brake (4) Braking IGBT over current detected | Cause: Over current has been detected in braking IGBT or braking IGBT protection has been activated (short circuit protection). Remedy:
|
|||||||||
| OI dc (109) Power module over current detected from IGBT on state voltage monitoring | Cause: The short circuit protection for the drive output stage has been activated. Remedy:
|
|||||||||
| OI Snubber (92) Snubber over-current detected | Cause: An over-current condition has been detected in the rectifier snubber circuit. Remedy:
|
|||||||||
| Option Disable (215) Option module does not acknowledge during drive mode changeover | Cause: Option modules must acknowledge that they have stopped accessing the communications system between the option slots and the drive during mode changeover. If they do not, this trip is produced. Remedy:
|
|||||||||
| Out Phase Loss (98) Output phase loss detected | Cause: A phase loss has been detected at the drive output. Sub-trips indicate if it is U, V, or W phase disconnected. Remedy:
|
|||||||||
| Over Speed (7) Motor speed has exceeded the over speed threshold | Cause: The Output Frequency or Speed Feedback exceeds the threshold set in Over Speed Threshold (03.008). Can be caused by flux weakening settings in RFC-S mode or high P1 gains. Remedy:
|
|||||||||
| Over Volts (2) DC bus voltage has exceeded the peak level or maximum continuous level | Cause: The DC bus voltage has exceeded the VM_DC_VOLTAGE[MAX] or VM_DC_VOLTAGE_SET[MAX] for 15s. Remedy:
|
|||||||||
| 32 Supply phase loss | Cause: The drive has detected an input phase loss or large supply imbalance. This can be detected directly from the supply (Frame size 7+) or by monitoring the ripple in the DC bus voltage. Remedy:
|
|||||||||
| 198 Phasing error | Cause: The phase offset angle is incorrect. The drive is unable to control the motor correctly due to incorrect position feedback angle. Remedy:
|
|||||||||
| 90 Power Comms | 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:
|
|||||||||
| 220 Power Data | Cause: There is an error in the configuration data stored in the power system (e.g., CRC error, table size mismatch, or version mismatch). Remedy:
|
|||||||||
| 37 Power Down Save | Cause: An error has been detected in the power down save parameters saved in non-volatile memory. Remedy:
|
|||||||||
| 5 Internal power supply fault (PSU) | Cause: One or more internal power supply rails are outside limits or overloaded. Remedy:
|
|||||||||
| 9 24V internal power supply overload (PSU 24V) | Cause: The total user load of the drive and option modules has exceeded the internal 24 V power supply limit. Remedy:
|
|||||||||
| 223 Rating Mismatch | Cause: There is a voltage rating or current rating mismatch in a multi-module drive system. A mixture of power modules with different 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: Measured resistance has exceeded the parameter range. The value for motor stator resistance is too high, or the measurement attempt failed. Remedy:
|
|||||||||
| 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:
|
|||||||||
| 204, 209, 214 SlotX Different | Cause: Option module in option slot X has changed. The module is a different type to that installed when parameters were last saved. Remedy:
|
|||||||||
| 202, 207, 212 SlotX Error | Cause: Option module in option slot X has detected a fault. Remedy:
|
|||||||||
| 200, 205, 210 SlotX HF | Cause: Option module X hardware fault. Remedy:
|
|||||||||
| 203, 208, 213 SlotX Not Fitted | Cause: Option module in option slot X has been removed since the last power up. Remedy:
|
|||||||||
| 201, 206, 211 SlotX Watchdog | Cause: Option module watchdog function service error. The module started the watchdog function but failed to service it. Remedy:
|
|||||||||
| 226 Soft start relay failed to close, soft start monitor failed | 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 Hardware trip has occurred during last power down | 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 RAM allocation error | Cause: An option module, derivative image or user program image has requested more parameter RAM than is allowed. The sub-trip is calculated as (parameter size) + (parameter type) + sub-array number. Remedy:
|
|||||||||
| 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:
Remedy:
|
|||||||||
| 10 Brake resistor over temperature | Cause: The Th Brake Res is initiated if hardware based braking resistor thermal monitoring is connected and the resistor overheats. Remedy:
|
|||||||||
| 25 Motor thermistor short circuit | Cause: A temperature sensor connected to an analogue input or terminal 15 has a low impedance (i.e. < 50 Ω). Sub-trip 3: Analog Input 3 Mode. Sub-trip 4: P1 Thermistor Short Circuit Detect. Remedy:
|
|||||||||
| 24 Motor thermistor over-temperature | Cause: The motor thermistor connected to terminal 8 (analog input 3) or terminal 15 (encoder) has indicated a motor over temperature. Remedy:
|
|||||||||
| 110 Drive has tripped and the cause of the trip is Undefined | Cause: The power system has generated a trip but did not identify it. The cause is unknown. Remedy:
|
|||||||||
| 91 User 24 V supply is not present on control terminals (1,2) | Cause: User Supply Select is set to 1 or Low Under Voltage Threshold Select is set to 1, but no user 24 V supply is detected. Remedy:
|
|||||||||
| 249 On board user program error | Cause: An error has been detected in the onboard user program image. Common sub-trips: 1: Divide by zero 2: Undefined trip 3-7: Parameter access/write errors 30-33: Image CRC/RAM/OS errors 40: Timed task suspended 52-53: Menu table CRC/Changed 61-74: Option module slot conflicts 80-81: Image compatibility errors Remedy:
|
|||||||||
| 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:
|
|||||||||
| 36 User Save error / not completed | Cause: An error has been detected in the user save parameters saved in non-volatile memory. Example: Power removed during save. Remedy:
|
|||||||||
| 41 – 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:
|
|||||||||
| 40 Motor Rated Current or Speed not recognized (Dyneo LSRPM) | Cause: The motor rated current or motor rated speed was not recognized as being a valid value for a Dyneo LSRPM motor. Remedy:
|
|||||||||
| 30 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, this must be repeated every 1s or a Watchdog trip occurs. Remedy:
|
|||||||||
| HF01 – HF20 Internal / Hardware trips | Cause: Internal faults that do not have trip numbers. The main drive processor has detected an irrecoverable error. Remedy:
|