Nidec & Control Technique Pump Drive F600 Drive

Nidec & Control Technique Pump Drive F600 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) Ensure 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) Ensure current signal is present and greater than 3 mA
219 An Output Calib	Cause: The zero offset calibration of one or both of the analogue outputs has failed. Indicates hardware failure or voltage applied via 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 wiring 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 (Menu 18, 19, or 20). If more than one menu changed, the lowest menu has priority. Remedy: Reset the trip and perform a parameter save to accept the new settings
121 Assist 1 Cycle	Cause: Soft Starter Assist 1 started too many times in an hour as defined by Assist Starts Per Hour (29.120). Only active when Assist Over-cycle Mode = Trip and Pump Control Mode = Cascade. Remedy: Check system configuration and Assist Starts parameters.
122 Assist 2 Cycle	Cause: Soft Starter Assist 2 started too many times in an hour as defined by Assist Starts Per Hour (29.120). Only active when Assist Over-cycle Mode = Trip and Pump Control Mode = Cascade. Remedy: Check system configuration and Assist Starts parameters.
11 Autotune 1	Cause: Position feedback did not change or required speed could not be reached during autotune. Sub-trip 1: Position feedback did not change. Sub-trip 2: Required speed not reached. Sub-trip 3: Commutation signal edge not found. Sub-trip 4: Required movement angle not produced. Sub-trip 5: Motor flux position not located. Sub-trip 6: Phasing offset angle mismatch. Sub-trip 7: Motor moving on enable. Sub-trip 9: Minimal movement phasing test failed. Remedy: Ensure motor is free to turn (mechanical brake released). Check position feedback selection and wiring. Ensure static load plus inertia is not too large. Check commutation signal connections. Reduce the angular movement required (for sub-trips 4, 5, 9). Ensure motor is stationary before drive enable (for sub-trip 7).
12 Autotune 2	Cause: Position feedback direction incorrect. Sub-trip 1: Direction incorrect during rotating autotune. Sub-trip 2: SINCOS encoder with comms 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 exceeded parameter range or commutation signals changed in wrong direction. Sub-trip 1: Measured inertia exceeded range. Sub-trip 2: Commutation signals changed wrong direction. Sub-trip 3: Mechanical load test unable to identify inertia. Remedy: Check motor cable wiring is correct Check feedback device U, V, W commutation signal wiring Increase the test level (Sub-trip 3) If tested at standstill, repeat with motor rotating within recommended speed range
14 Autotune 4	Cause: U commutation signal did not change during a rotating auto-tune. Remedy: Check feedback device U commutation signal wiring is correct (Encoder terminals 7 and 8)
15 Autotune 5	Cause: V commutation signal did not change during a rotating auto-tune. Remedy: Check feedback device V commutation signal wiring is correct (Encoder terminals 9 and 10)
16 Autotune 6	Cause: W commutation signal did not change during a rotating auto-tune. Remedy: Check feedback device W commutation signal wiring is correct (Encoder terminals 11 and 12)
17 Autotune 7	Cause: Motor number of poles or position feedback resolution set incorrectly. Remedy: Check line per revolution for feedback device Check the number of poles in Pr 05.011
18 Autotune Stopped	Cause: The drive was prevented from completing an autotune test because the drive enable or drive run were removed. Remedy: Check the drive enable signal (Terminal 31) was active during the autotune Check the run command was active in Pr 08.005 during autotune
123 Bkground Watchdg	Cause: Background task taking longer than 15s to execute. Remedy: Contact supplier or check for firmware updates (System error).
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, set Pr 10.030, 10.031 or 10.061 to 0 to disable the trip
185 Card File Error	Cause: Information in the card header is out of range, or file system header information is incorrect. Remedy: Check card compatibility and file format.
177 Card User Prog	Cause: Attempt to read a write-only user program, or transfer a program from drive to card when no program is present in drive. Remedy: Ensure valid user program exists before transfer.
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 Derivative	Cause: A parameter difference file is being written to the drive, but the Drive Derivative value in the file header differs from the drive. Remedy: Verify file source and drive compatibility.
179 Card Data Exists	Cause: An attempt is being made to write to a file that already exists. Remedy: Delete existing file or use different file name/location.
187 Card File Data	Cause: The drive mode, required defaults, or product type in a parameter difference file are not compatible with the drive. Remedy: Ensure parameter set matches drive type and mode.
182 Card Error	Cause: NV Media Card data structure error. Missing or corrupt folders/files. Sub-trip 1: Required folder structure missing. Sub-trip 2: <000> file corrupted. Sub-trip 3: Duplicate file identification numbers. Remedy: Erase all the data block and re-attempt the process Ensure the card is located correctly Replace the NV Media Card
184 Card Full	Cause: Not enough space left on the NV Media Card to create a data block. 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: Attempt to access non-existent file or block on NV Media Card. Remedy: Ensure data block number is correct
180 Card Option	Cause: Option modules installed are different between source drive and destination drive. Warning that data for option modules will be set to defaults. Remedy: Ensure the correct option modules are installed Press the red reset button to acknowledge parameters will be set to defaults 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-trips: 1: Drive Derivative different between source and target. 2: Product Type different or corruption detected. 3: Unidrive SP parameter value found with no equivalent. 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 during parameter transfer from NV Media Card. 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 trip can be suppressed by setting Pr mm.000 to 9666 and resetting the drive.
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.
120 Clean Over-cycle	Cause: Pump cleaning cycle running too many times as defined by Clean Per Hour Limit (29.100). Only active if Clean Per Hour Limit Mode (29.101) = Trip. Remedy: Check the Clean Per Hour Limit (29.100) settings. Check pump conditions causing frequent cleaning cycles.
102 Cloning	Cause: Cloning system backup or restore of drive/option modules failed. The sub-trip value indicates the specific reason. Remedy: Check parameter mm.000 values entered (40001-40999 for backup, 60001-60999 for restore). Retry the operation.
111 Configuration	Cause: The number of power modules installed is different from the modules expected (11.071), or external rectifiers connected are less than expected (11.096). Remedy: Ensure that all the power modules are correctly connected and powered up. 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 (if applicable). 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 the control word is enabled. Remedy: Check the value of Pr 06.042. Disable the control word in Control Word Enable (Pr 06.043). To clear, set bit 12 to zero.
124 Ctrl Wrd Watchdg	Cause: Watchdog bit 15 not being toggled for Watchdog Time (29.150) seconds. Protects system when HMI or PLC disconnects. Remedy: Check connection to HMI or PLC. Verify Control Input Mode (29.012) settings.
225 Current Offset	Cause: The current feedback offset is too large to be trimmed correctly. Sub-trips: 1 (Phase U), 2 (Phase V), 3 (Phase W). Remedy: Ensure that there is no possibility of current flowing in the output phases of the drive when the drive is not enabled. Hardware fault – Contact the supplier of the drive.
97 Data Changing	Cause: Drive parameters are being changed by a user action or file system write while the drive has been commanded to enable. Remedy: Ensure the drive is not enabled when loading defaults. Ensure the drive is not enabled when changing drive mode. Ensure the drive is not enabled when transferring data from NV Media Card or position feedback device. Ensure the drive is not enabled when transferring user programs.
247 Derivative ID	Cause: There is a problem with the identifier associated with derivative image which customizes the drive. Sub-trips: 1: Derivative image erased. 2: Identifier out of range. 3: Derivative image changed. Remedy: Contact the supplier of the drive.
248 Derivative Image	Cause: Error detected in the derivative image. Common Sub-trips: 1: Divide by zero. 30: CRC incorrect / image header error. 53: Customisable menu table changed. 80/81: Image not compatible with control board. Remedy: Contact the supplier of the drive.
199 Destination	Cause: Two or more parameters are writing to the same destination parameter (Menus 5, 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: The control PCB has not recognized the drive size of the power circuit to which it is connected. Remedy: Ensure the drive is programmed to the latest firmware version. Hardware fault – return drive to supplier.
115 Dry Well	Cause: Dry Well Low Load detection triggered when Dry Well Low Load Mode (29.059) = Trip. Remedy: Check pump suction conditions. Verify settings for Dry Well Low Load parameters.
31 EEPROM Fail	Cause: Default parameters have been loaded. This occurs if saved parameters are corrupted, power down save fails, or checksum fails. 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.
162 Encoder 12	Cause: Drive is communicating with the encoder but the encoder type is not recognised. Remedy: Enter the encoder setup parameters manually. Check to see if the encoder supports auto-configuration.
163 Encoder 13: Drive is communicating with the encoder	Cause: Data read from the encoder was out of range during auto-configuration. No parameters will be modified. The tens in the sub-trip indicate the interface (1 for P1, 2 for P2). Sub-trip Reasons: x1: Rotary lines per revolution error x2: Linear comms pitch error x3: Linear line pitch error x4: Rotary turns bits error x5: Communications bits error x6: Calculation time is too long x7: Line delay measured is longer than 5us Remedy: Enter the encoder setup parameters manually. Check to see if the encoder supports auto-configuration.
164 Encoder 14: Drive is communicating with the encoder	Cause: Data given in the additional configuration parameter for a position feedback interface is out of range. P1 Additional Configuration (03.074) or P2 Additional Configuration (03.174) is out of range. BiSS: Range checking is applied to turns padding (digits 5-3) and position padding (digits 2-0). If padding value is outside +/- 16, trip is initiated. Remedy: Check configuration parameters 03.074 or 03.174. Verify padding settings for BiSS devices.
116 Ext Pump Fault: External Pump Fault Input	Cause: This trip is called by the Pump software in the event of the External Pump Fault Input (29.085) being set to On(1). Remedy: Check the external pump fault input signal. Investigate the external pump condition.
6 External Trip: An External trip is initiated	Cause: An External Trip has occurred. Can be initiated by writing a value of 6 in Pr 10.038. Sub-trip Reasons: 1: External Trip Mode (08.010) = 1 or 3 and Safe Torque Off input 1 is low 2: External Trip Mode (08.010) = 2 or 3 and Safe Torque Off input 2 is low 3: External Trip (10.032) = 1 Remedy: Check the Safe Torque Off signal voltage on terminal 29 equals to 24 V. Check the value of Pr 08.009 which indicates the digital state of terminal 29, 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: A CPU address error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF02 Data processing error: DMAC address error	Cause: A DMAC address error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF03 Data processing error: Illegal instruction	Cause: An illegal instruction has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF04 Data processing error: Illegal slot instruction	Cause: An illegal slot instruction has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF05 Data processing error: Undefined exception	Cause: An undefined exception error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF06 Data processing error: Reserved exception	Cause: A reserved exception error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF07 Data processing error: Watchdog failure	Cause: A watchdog failure has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF08 Data processing error: CPU Interrupt crash	Cause: A CPU interrupt crash has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF09 Data processing error: Free store overflow	Cause: A free store overflow has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF10 Data processing error: Parameter routing system error	Cause: A Parameter routing system error has occurred. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF11 Data processing error: Access to EEPROM failed	Cause: Access to the drive EEPROM has failed. This trip indicates that the control PCB on the drive has failed. Remedy: Hardware fault – Contact the supplier of the drive.
HF12 Data processing error: Main program stack overflow	Cause: The main program stack overflow has occurred. Control PCB has failed. Sub-trip Stack ID: 1: Background tasks 2: Timed tasks 3: Main system interrupts Remedy: Hardware fault – Contact the supplier of the drive.
HF13 Data processing error: Firmware incompatible with hardware	Cause: Drive firmware is not compatible with the hardware. The sub-trip number gives the actual ID code of the control board hardware. Remedy: Re-program the drive with the latest version of the drive firmware. Hardware fault – Contact the supplier of the drive.
HF14 Data processing error: CPU register bank error	Cause: A CPU register bank error has occurred. 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: 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: 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 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: Internal flash memory has failed when writing option module parameter data. Sub-trip Reasons: 1: Programming error while writing menu in flash 2: Erase flash block containing setup menus failed 3: Erase flash block containing application menus failed Remedy: Hardware fault – Contact the supplier of the drive.
HF19 Data processing error: CRC check on the firmware has failed	Cause: 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 ASIC version is not compatible with the drive firmware. The ASIC version can be identified from the sub-trip number. Remedy: Hardware fault – Contact the supplier of the drive.
HF23 to HF25 Hardware fault	Cause: Internal hardware fault occurred. Remedy: Hardware fault – Contact the supplier of the drive.
26 I/O Overload: Digital output overload	Cause: Total current drawn from 24 V user supply or from the digital output has exceeded the limit. Conditions: Maximum output current from one digital output is 100 mA. The combined maximum output current from outputs 1 and 2 is 100 mA. The combined maximum output current from output 3 and +24 V output is 100 mA. Remedy: Check total loads on digital outputs. Check control wiring is correct. Check output wiring is undamaged.
8 Inductance	Cause: This trip occurs in RFC-S mode when the drive has detected that the motor inductances are not suitable for the operation being attempted. The trip is either caused because the ratio or difference between Ld and Lq is too small or because the saturation characteristic of the motor cannot be measured. Remedy: For 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). For Sub-trip 3: None. The trip acts as a warning. For Sub-trip 4: Stationary autotune is not possible. Perform a minimal movement or rotating autotune. For Sub-trip 4: Phasing test on starting is not possible. Use a position feedback device with commutation signals or absolute position.
20 Motor Too Hot	Cause: The Motor Too Hot trip indicates a motor thermal overload based on the rated current (Pr 05.007) and motor thermal time constant (Pr 04.015). Pr 04.019 displays the motor temperature as a percentage of the maximum value. The drive will trip when Pr 04.019 gets to 100%. Remedy: Ensure the load is not jammed / sticking. Check the load on the motor has not changed. If seen during an auto-tune test in RFC-S mode, ensure the motor rated current in Pr 05.007 is ≤ Heavy duty current rating of the drive. Tune the rated speed parameter (RFC-A mode only). Check feedback signal for noise. Ensure the motor rated current is not zero.
21 OHt Inverter	Cause: Inverter over temperature based on thermal model. This trip indicates that an IGBT junction over-temperature has been detected based on a firmware 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.
23 OHt Control	Cause: Control stage over temperature. This trip indicates that a control stage over-temperature has been detected (Control board thermistors or I/O board thermistor). 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	Cause: DC bus over temperature. The trip indicates a DC bus component over temperature based on a software thermal model, or power stage detection in multi-power module systems. Remedy: Check the AC supply voltage balance and levels. Check DC bus ripple level. Reduce duty cycle. Reduce motor load. Check the output current stability. If unstable: Check motor map settings (05.006 – 05.011). Disable slip compensation (05.027 = 0). Disable dynamic V to F operation (05.013 = 0). Select fixed boost (05.014 = Fixed). Select high stability space vector modulation (05.020 = 1). Disconnect load and complete rotating autotune. Reduce speed loop gains (03.010 – 03.012).
34 Keypad Mode	Cause: Keypad has been removed when the drive is receiving the speed reference from the keypad. Remedy: Not applicable.
38 Low Load	Cause: Low load detector is set up to produce a trip on low load detection. This trip is initiated if the low load detector is set up to produce a trip on low load detection and this condition occurs. Remedy: See Enable Trip On Low Load (04.029).
39 Line Sync	Cause: Line Sync error. Remedy: Not applicable.
93 Inductor Too Hot	Cause: Inductor Too Hot. Remedy: Not applicable.
101 OHt Brake	Cause: Braking IGBT over-temperature. The trip indicates that braking IGBT over-temperature has been detected based on software thermal model. Remedy: Check braking resistor value is greater than or equal to the minimum resistance value.
103 Inter-connect	Cause: Multi-power module drive interconnection cable error. Indicates which power module has detected the fault or if communication fails. Remedy: Check interconnection cables between power modules. Check for rectifier faults.
118 Motor Over Temp	Cause: This trip is called by the Pump software in the event of the Motor Thermal Protection Input (29.086) being set to Off(0) when Motor Thermal Protection Enable (29.087) = On(1). Remedy: Check motor thermal protection settings.
160 Island	Cause: System is connected to an island supply. Remedy: Not applicable.
176 Name Plate	Cause: Electronic nameplate transfer has failed. Sub-trip 1: Communication error with encoder. Incorrect data in nameplate. Sub-trip 2: Data error detected (entries out of range or CRC mismatch). No valid nameplate. Sub-trip 3: Exchange with encoder timed out. Encoder not connected, not initialized, or incorrect option module. Remedy: Ensure that the device encoder memory has at least 128 bytes to store the nameplate data. When writing the motor object, ensure the device encoder memory has at least 256 bytes. When transferring between option module and encoder, ensure that the option slot has a feedback option module installed. Check if the encoder has been initialized, Position Feedback Initialized (03.076). Verify the encoder wiring.
Network Loss Ethernet RTMoE Loss	Cause: Event of a loss Ethernet RTMoE comms from this drive to its Leader in a Multi-leader system. Remedy: Check network cables and connections. This trip is enabled when Multi-leader Network Loss Mode (29.133) = Trip. Trip may be disabled by setting mode to Run Single Pump.
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 (located on power board or rectifier). Remedy: Check enclosure / drive fans are still functioning correctly. Force the heatsink fans to run at maximum speed. Check enclosure ventilation paths. Check enclosure door filters. Increase ventilation. Reduce the drive switching frequency. Reduce duty cycle. Decrease acceleration / deceleration rates. Reduce motor load. Check the derating tables and confirm the drive is correctly sized for the application. Use a drive with larger current / power rating.
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 10 s after the trip was initiated. Remedy: Acceleration/deceleration rate is too short. If seen during auto-tune reduce the voltage boost. Check for short circuit on the output cabling. Check integrity of the motor insulation using an insulation tester. Check feedback device wiring. Check feedback device mechanical coupling. Check feedback signals are free from noise. Is motor cable length within limits for the frame size? Reduce the values in the speed loop gain parameters. 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 (4) Braking IGBT over current detected	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: Check brake resistor wiring. Check braking resistor value is greater than or equal to the minimum resistance value. Check braking resistor insulation.
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. This trip cannot be reset until 10 s after the trip was initiated. Remedy: Disconnect the motor cable at the drive end and check the motor and cable insulation with an insulation tester. Replace the drive.
OI Snubber (92) Snubber over-current detected	Cause: An over-current condition has been detected in the rectifier snubber circuit. Remedy: Ensure the internal EMC Filter is installed. Ensure the motor cable length does not exceed the maximum for selected switching frequency. Check for supply voltage imbalance. Check for supply disturbance such as notching from a DC drive. Check the motor and motor cable insulation with an insulation tester. Fit an output line reactor or sinusoidal filter.
Option Disable (215) Option module does not acknowledge during drive mode changeover	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: Reset the trip. If the trip persists replace the option module.
Out Phase Loss (98) Output phase loss detected	Cause: A phase loss has been detected at the drive output. Sub-trips indicate specifically which phase (U, V, or W) was detected as disconnected or if an IGBT failure was detected. Remedy: Check motor and drive connections. To disable the trip set Output Phase Loss Detection Enable (06.059) = 0.
Over-Cycle (117) Over-cycle	Cause: This trip is called by the Pump software in the event of the over-cycle protection scheme counting too many starts per hour when Over-cycle Mode (29.127) = Trip. Remedy: Check system configuration and requirements for starts per hour. Review Over-cycle Mode parameter (29.127).
Over Speed (7) Motor speed has exceeded the over speed threshold	Cause: In open loop mode, Output Frequency exceeds the threshold set in 03.008. In RFC-A/S mode, Speed Feedback exceeds the threshold. Can also be caused by SSI encoder settings or flux weakening configurations. 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. Check Enable High Speed Mode (05.022) is set to -1 if flux weakening is required.
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 15 s. The threshold varies depending on the voltage rating of the drive. Remedy: Increase deceleration ramp. Decrease the braking resistor value (staying above the minimum value). Check nominal AC supply level. Check for supply disturbances which could cause the DC bus to rise. Check motor insulation using an insulation tester.
32 Phase Loss: Supply phase loss	Cause: Input phase loss, large supply imbalance, or high ripple in the DC bus voltage detected. Remedy: Check the AC supply voltage balance and level at full load. Check the DC bus ripple level with an isolated oscilloscope. Check the output current stability. Reduce the duty cycle. Reduce the motor load. Disable the phase loss detection, set Pr 06.047 to 2. Check for mechanical resonance with the load.
198 Phasing error: Phase offset angle is incorrect	Cause: The phase offset angle in Position Feedback Phase Angle (03.025) is incorrect, incorrect encoder wiring, noise, or instability in sensorless control. Remedy: Check the encoder wiring. Check the encoder signals for noise with an oscilloscope. Check encoder mechanical coupling. Perform an auto-tune to measure the encoder phase angle or manually enter the correct phase angle (03.025). Ensure that the motor parameters are set-up correctly. Reduce the speed controller gains. If high saliency control is used, ensure Low Speed Sensorless Mode Current (05.071) is set low enough. Disable trip by setting Over Speed Threshold (03.008) > 0.
113 PID Feedbk High: PID1 feedback above high threshold	Cause: The main process PID1 feedback has gone above the PID Feedback High Trip Threshold (29.041). Remedy: Check process feedback levels. Adjust threshold in Pr 29.041 if required. This trip can be disabled by setting Pr 29.041 = 0.
112 PID Feedbk Loss: PID1 feedback loss detected	Cause: Loss of main process PID1 feedback when PID Feedback Loss Action (29.048) is set to Trip. Remedy: Check PID feedback wiring and sensors. Check Analog Input 1 Current Loop Loss (07.028) status.
114 PID Feedbk Low: PID1 feedback below low threshold	Cause: The main process PID1 feedback has gone below the PID Feedback Low Threshold (29.044). Remedy: Check process feedback levels. This trip can be disabled by setting PID Feedback Low Mode (29.043) to Disabled.
90 Power Comms: Communications problem within power system	Cause: Excessive communications errors detected by the rectifier module or between control/power systems. Remedy: Hardware fault – Contact the supplier of the drive.
220 Power Data: Power system configuration data error	Cause: Error in configuration data stored in the power system (e.g., table missing, table too big, CRC error, version mismatch). Remedy: Hardware fault – Contact the supplier of the drive.
37 Power Down Save: Power down save error	Cause: An error has been detected in the power down save parameters saved in non-volatile memory. Remedy: Perform a 1001 save in Pr mm.000 to ensure that the trip doesn’t occur the next time the drive is powered up.
5 PSU: Internal power supply fault	Cause: One or more internal power supply rails are outside limits or overloaded. Remedy: Remove any option modules and perform a reset. Remove encoder connection and perform a reset. Hardware fault within the drive – return the drive to the supplier.
9 PSU 24V: 24V internal power supply overload	Cause: The total user load of the drive and option modules has exceeded the internal 24V power supply limit. Remedy: Reduce the load and reset. Provide an external 24V power supply on control terminal 2. Remove all option modules.
94 Rectifier Set-up: Rectifier incorrectly set up	Cause: A rectifier has not been set-up correctly in a multi-power module system. Remedy: Check the inter-power module wiring.
100 Reset	Cause: This is not a valid trip number. Remedy: Used in User Trip (10.038) to reset the drive.
255 Reset Logs	Cause: This is not a valid trip number. Remedy: Used in User Trip (10.038) to reset the trip logs.
223 Rating Mismatch: Multi module voltage or current rating mismatch	Cause: A mixture of power modules with different voltage or current ratings detected in a parallel 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.
33 Resistance: Measured resistance exceeded parameter range	Cause: Stator resistance too high, measurement failed during auto-tune, or motor parameters changed by user. Remedy: Check that the value entered in stator resistance does not exceed the allowed range. Check the motor cable / connections. Check the integrity of the motor stator winding using an insulation tester. Check the motor phase to phase resistance at the drive terminals. Ensure the stator resistance falls within the range of the drive model. Select fixed boost mode (Pr 05.014 = Fixed) and verify output current waveforms. Replace the motor.
216 Slot App Menu: Customization conflict error	Cause: More than one option slot has requested to customize the application menus 18, 19, and 20. Remedy: Ensure that only one of the Application modules is configured to customize the application menus 18, 19 and 20.
204, 209, 214, 254 SlotX Different: Option module in slot X has changed	Cause: The option module in slot X is a different type than what was previously installed and saved. Remedy: Turn off the power, ensure the correct option modules are installed in the correct slots and re-apply power. Confirm current module is correct, ensure parameters are set correctly. Perform a user save in Pr mm.000.
202, 207, 212, 252 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 relevant Option Module User Guide for details of the trip.
200, 205, 210, 250 SlotX HF	Cause: The option module in option slot X on the drive has indicated a hardware fault. Possible causes (Sub-trips): 1: Module category unidentified. 2: Table information corrupt/missing. 3: Insufficient memory for comms buffers. 4-10: Various initialization or communication failures. Remedy: Ensure the option module is installed correctly. If the option module has been reprogrammed check that this process was followed correctly. Replace the option module.
203, 208, 213, 253 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, 251 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 – HF19) has occurred and the drive has been power cycled. The sub-trip number identifies the HF trip (e.g. stored HF.17). Remedy: Enter 1299 in Pr mm.000 and press reset to clear the trip.
227 Sub-array RAM	Cause: RAM allocation error. An option module, derivative image or user program image has requested more parameter RAM than is allowed. The failure with the highest sub-trip number is given. Remedy: Check menu customization provided by option modules/derivative images. Review RAM allocation based on sub-trip calculation (parameter size x 1000 + parameter type x 100 + sub-array number).
218 Temp Feedback	Cause: 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: Hardware fault – Contact the supplier of the drive.
10 Th Brake Res	Cause: Brake resistor over temperature. If hardware based braking resistor thermal monitoring is connected and the resistor overheats. If the resistor is not used, this trip must be disabled (bit 3 of Action On Trip Detection 10.037). Remedy: Check brake resistor wiring. Check brake resistor value is greater than or equal to the minimum resistance value. Check braking resistor insulation.
25 Th Short Circuit	Cause: Motor thermistor short circuit. A temperature sensor connected to an analogue input or terminal 15 on the position feedback interface has a low impedance (i.e. < 50 Ω). Remedy: Check temperature feedback connection. Replace sensor.
24 Thermistor	Cause: Motor thermistor over-temperature. The motor thermistor connected to terminal 8 (analog input 3) or terminal 15 (encoder) has indicated a motor over temperature. Remedy: Check why the temperature measured by the sensor is too high. Check temperature sensor connection.
110 Undefined	Cause: The drive has tripped and the cause of the trip is Undefined. The power system generated a trip but did not identify the trip type. Remedy: Hardware fault – return the drive to the supplier.
91 User 24V	Cause: User 24 V supply is not present on control terminals (1,2). Initiated if User Supply Select (Pr 06.072) is set to 1 or Low Under Voltage Threshold Select (06.067) = 1. Remedy: Ensure the user 24 V supply is present on control terminals 1 (0 V) and 2 (24 V).
249 (Cont) User Program	Cause: On board user program error. Sub-trips indicate specifics: 40,41: Enable reset to zero. 51, 6x, 7x: Customization/Module restrictions. 100-104: Pointer/Array access violations or Type conversion errors. 200: Divide by zero. Remedy: Check and debug the Onboard User Program logic based on the sub-trip code.
96 User Prog Trip	Cause: Trip generated by an onboard user program using a function call which defines the sub-trip number. Remedy: Check the user program.
36 User Save	Cause: User Save error / not completed. Error detected in user save parameters 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, 125-159 User Trip	Cause: User generated trip. These trips are not generated by the drive and are to be used by the user to trip the drive through an application program. Remedy: Check the user program.
169 Voltage Range	Cause: Not Applicable. Remedy: (No action listed in manual).
30 Watchdog	Cause: Control word watchdog has timed out. The control word has been enabled and has timed out. Remedy: Once Pr 06.042 bit 14 has been changed from 0 to 1 to enable the watchdog, this must be repeated every 1s or a Watchdog trip will be initiated. The watchdog is disabled when the trip occurs and must be re-enabled if required when the trip is reset.
HF01 – HF20 Internal / Hardware trips	Cause: The main drive processor has detected an irrecoverable error. Internal faults that do not have trip numbers. Remedy: Power cycle the drive (turn off and on). If the drive trips on “Stored HF” after power up, enter 1299 in parameter mm.000 to clear the trip. If the problem persists, the hardware may be faulty.
Brake Resistor Brake resistor overload	Cause: Braking Resistor Thermal Accumulator (10.039) in the drive has reached 75.0 % of the value at which the drive will trip. Remedy: Check braking resistor sizing and load. Reduce braking duty cycle.
Motor Overload Motor protection warning	Cause: Motor Protection Accumulator (04.019) in the drive has reached 75.0 % of the value at which the drive will trip and the load on the drive is > 100 %. Remedy: Check motor load and current. Ensure motor is not stalled or obstructed.
Drive Overload Drive over temperature	Cause: Percentage Of Drive Thermal Trip Level (07.036) in the drive is greater than 90 %. Remedy: Check cooling fans and air flow. Check ambient temperature. Reduce load on the drive.
Auto Tune Autotune in progress	Cause: The autotune procedure has been initialized. Remedy: Wait for autotune to complete. No action required unless process hangs.
Error 1 Insufficient Memory	Cause: There is not enough drive memory requested by all the option modules. Remedy: Power down drive and remove some of the option modules until the message disappears.
Error 2 Module Reset 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 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.