Parker AC30 Drive

Parker AC30 Drive Fault Codes:

Fault Code	Cause & Solution
1 OVER VOLTAGE	Cause: The drive internal dc link voltage is too high: – The supply voltage is too high – Trying to decelerate a large inertia load too quickly; DECEL TIME time too short – The brake resistor is open circuit – To help prevent this trip, enable the DC Link Volts Limit feature Solution: Internal dc link voltage has reached midway between the over voltage trip level and the dynamic braking resistor control voltage.
2 UNDER VOLTAGE	Cause: DC link low trip: – Supply is too low/power down. Solution: Internal dc link voltage has reached midway between the lowest expected instantaneous voltage and the under voltage trip level.
3 OVER CURRENT	Cause & Solution: The motor current being drawn from the drive is too high: – Trying to accelerate a large inertia load too quickly; ACCEL TIME time too short – Trying to decelerate a large inertia load too quickly; DECEL TIME time too short – Application of shock load to motor – Short circuit between motor phases – Short circuit between motor phase and earth – Motor output cables too long or too many parallel motors connected to the drive – FIXED BOOST level set too high – The over current trip makes up of a multiple-attempt strategy. The warning is triggered if two or more consecutive overcurrent events are encountered (whereas five consecutive events are required for a Trip to occur).
4 STACK FAULT	Cause & Solution: Stack self protection: – Instantaneous overcurrent detected by the power stack. Refer to OVERCURRENT in this table. – Instantaneous over voltage event. Refer to OVER VOLTAGE in this table
5 STACK OVER CURRENT	Cause & Solution: The motor current exceeded the capabilities of the power stack. – Instantaneous overcurrent detected by the power stack. Refer to OVERCURRENT in this table.
6 CURRENT LIMIT	Cause & Solution: V/Hz mode only: If the current exceeds 200% of stack rated current for a period of 1 second, the drive will trip. This is caused by shock loads
7 MOTOR STALL	Cause & Solution: The motor has stalled (not rotating) Drive in current limit >200 seconds: – Motor loading too great – FIXED BOOST level set too high The stall condition has been detected for more than one tenth of the configured Stall Time.
8 INVERSE TIME	Cause & Solution: A prolonged overload condition, exceeding the Inverse Time allowance, has caused the trip: – Remove the overload condition An overload condition has exceeded one half of the Inverse Time allowance.
9 MOTOR I2T	Cause & Solution: Only for PMAC Motor: A prolonged load condition, exceeding the motor rated current, has caused the trip. The estimated motor load has reached a value of 105% – An overload condition has exceeded one half of the motor Inverse Time allowance.
10 LOW SPEED I	Cause & Solution: The motor is drawing too much current (>100%) at zero output frequency: – FIXED BOOST level set too high
11 HEATSINK OVERTEMP	Cause & Solution: Drive heatsink temperature too high – The ambient air temperature is too high – Poor ventilation or spacing between drives – Check heatsink fan is rotating The drive heatsink has exceeded the warning temperature level (which is approx. 10 °C below the trip temperature).
12 INTERNAL OVERTEMP	Cause & Solution: Processor temperature or ambient temperature within the power stage too high – The ambient temperature in the drive is too high The drive processor temperature has exceeded the warning temperature level (which is approx. 10 °C below the trip temperature).
13 MOTOR OVERTEMP	Cause & Solution: The motor temperature is too high, (required IO Option card) – Excessive load – Motor voltage rating incorrect – FIXED BOOST level set too high – Prolonged operation of the motor at low speed without forced cooling – Break in motor thermistor connection The motor has been over temperature for 7.5 seconds.
14 EXTERNAL TRIP	Cause & Solution: The external (application) trip input is high: – Refer to the application description to identify the source of the signal.
15 BRAKE SHORT	Cause & Solution: CCT External dynamic brake resistor has been overloaded: – The external dynamic brake has developed a short circuit. – Wiring fault
16 BRAKE RESISTOR	Cause & Solution: External dynamic brake resistor has been overloaded: – Trying to decelerate a large inertia too quickly or too often The power calculation for the external resistor has exceeded one half of the Brake Overrating allowance.
17 BRAKE SWITCH	Cause & Solution: Internal dynamic braking switch has been overloaded: – Trying to decelerate a large inertia too quickly or too often The power calculation for the internal dynamic braking switch has exceeded one half of the its overrating allowance.
18 LOCAL CONTROL	Cause & Solution: Keypad has been disconnected from drive whilst drive is running in Local Control: – GKP accidentally disconnected from drive
19 COMMS BREAK	Cause & Solution: Lost option communications: – A break in option communications has been detected. Refer to option communications manual.
20 LINE CONTACTOR	Cause & Solution: DC Link failed to reach the undervoltage trip level within the contactor feedback time. – The Line contactor failed to connect. – Missing 3-phase line supply
21 PHASE FAIL	Cause & Solution: Indicates a missing input phase, for Frame K drives.
22 VDC RIPPLE	Cause & Solution: The DC link ripple voltage is too high: – Check for a missing input phase – Repetitive start / stop or forward reverse action. The dc link ripple has exceeded 75% of the trip level.
23 BASE MODBUS	Cause & Solution: BREAK Lost Base Modbus communications: – A break in the Base Modbus communications has been detected. Refer to “Appendix A Modbus TCP”.
24 24V OVERLOAD	Cause & Solution: 24V rail is low – Output overload due to excess current being drawn from the 24v terminal.
25 PMAC SPEED ERROR	Cause & Solution: Only for PMAC motor : When using the Start feature in Sensorless Vector Control, the real speed hasn’t reached the speed setpoint after 5 seconds to move from open to closed loop control or to move from closed to open loop
26 OVERSPEED	Cause & Solution: Overspeed: – >150% base speed when in Sensorless Vector mode.
27 STO ACTIVE	Cause & Solution: Attempt to run the motor with the Safe Torque Off active – Check the STO wiring. It may be necessary to power the drive off and on to completely clear this event.
28 FEEDBACK MISSING	Cause & Solution: The drive has been configured to run in Closed Loop Vector control mode with a Pulse Encoder IO Option, but the IO Option has not been correctly configured. The drive has been configured to run in Closed Loop Vector control mode with a System Board and/or a Pulse Encoder IO Option (using one of the 3 possible encoder inputs), but the system board or the IO option has not been declared as required.
29 INTERNAL FAN FAIL	Cause & Solution: An internal cooling fan has failed. This will reduce the lifetime of the power electronics. – Return the power stack to a Parker Hannifin repair centre.
30 CURRENT SENSOR	Cause & Solution: Current feedback phase missing. – Check motor phase connections.
31 POWER LOSS STOP	Cause & Solution: A Power Loss Ride Through sequence has occurred and either 1650 Pwrl Time Limit has been exceeded or the motor speed has reached a zero speed during the sequence.
32 SPEED SENSOR FAULT	Cause & Solution: Not applicable. Encoder has failed whilst operating in vector control of induction motor. The drive switches to sensorless operation automatically (if this feature is enabled), and provides a warning to the user.
33 A1	Cause & Solution: Application trip 1. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 1.
34 A2	Cause & Solution: Application trip 2. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 2.
35 A3	Cause & Solution: Application trip 3. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 3.
36 A4	Cause & Solution: Application trip 4. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 4.
37 A5	Cause & Solution: Application trip 5. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 5.
38 A6	Cause & Solution: Application trip 6. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 6.
39 A7	Cause & Solution: Application trip 7. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 7.
40 A8	Cause & Solution: Application trip 8. – The application trips are controlled by the Application_Trips block in the configuration. The text associated with each trip can be re-defined by the Application_Trips_Text block in the configuration. – Application warning 8.
41 SPEED ERROR FAULT	Cause & Solution: Difference between actual motor speed and the speed setpoint is greater than a threshold for a period of time. – Difference between actual motor speed and the speed setpoint has been greater than the trip threshold for more than half the trip delay time.
42 PEER TO PEER OVERRUN	Cause & Solution: Configuration error on Master and/or Slave(s) side PTP or Peer to Peer are OFF on one drive Destination IP or Destination Port incompatible between Master and Slave(s) Peer to Peer is not useable – Multiple delayed Peer To Peer messages have occurred. This may cause incorrect phase alignment if phase control is being used.
43 PHASE CONFIG	Cause & Solution: Something is wrong in the phase configuration : one or more of the encoders set up for speed control, master and/or slave are wrongly declared. See Phase Ctrl Config : – Error Number for a detailed description of the error (Only applicable if phase control is enabled)
44 ETHERNET IP BREAK	Cause & Solution: Lost Base EtherNet IP communications: – A break in the Base EtherNet IP communications has been detected. Refer to “Appendix A EtherNet IP Adapter”.
45 RESOLVER ERROR	Cause & Solution: An error has been detected on the resolver signals – Error type is available by looking at 1820 Resolver Trip Type
46 PMAC ALIGN ERROR	Cause & Solution: If 1796 Alignment on Power On has been set to TRUE, the drive should run a successful Pos Alignment sequence, at power up before being run safely. or Something wrong occurred during the last Pos Alignment sequence. Error type is available by looking at 1807 Alignment error
Runtime Alerts 1 to 255 Internal exception	Details: VCM not secured to power stack – Option not secured correctly to VCM control card – Earth bonding failure. – Fault during firmware upgrade
Runtime Alerts 12 Memory access	Details: – Attempt to read or write to protected memory. Most likely this will be due to a configuration error. Press OK several times until the drive resets correctly, then replace the configuration using PDQ. – Record the error message and contact Technical Support
Runtime Alerts 1001 to 1003 Processor overload	• Select a lower switching frequency, (Parameters::Motor Control::Pattern Generator::Stack Frequency) • Record the error message and contact Technical Support
Runtime Alerts 1006 Memory overflow	• Reduce the complexity of the application • Reduce the number of parameters being accessed via the on board Modbus TCP protocol • Reduce the number of parameters being accessed by the fieldbus communications option.
Runtime Alerts 1007 Uninitialized pointer	Record the error message and contact Technical Support
Runtime Alerts 1010, 1101 to 1113 Initialization error	Record the error message and contact Technical Support
Runtime Alerts 1200 to 1299 Communications option error	• Ensure the communications option is correctly fitted • Update the firmware in the inverter. • Replace the communications option
1300 Ethernet fault	Record the error message and contact Technical Support
1301 Modbus server	Record the error message and contact Technical Support
1302 HTTP server fault	Record the error message and contact Technical Support
1303 DCT server fault	Record the error message and contact Technical Support
1311 Ethernet PHY	Record the error message and contact Technical Support
1312 Precision Time Protocol	Record the error message and contact Technical Support
1313 EtherNet IP	Record the error message and contact Technical Support
1401 1402 Control Module test	Control module self-test error
1403 1404 Power stack test	VCM not secured to power stack • Power stack self-test error
1501 1502 1503 IO Option identity IO Option processor Unknown IO Option	• Ensure the IO option is correctly fitted • Update the firmware in the inverter. • Replace the IO option
1504 IO Option watchdog	• The IO Option has become disconnected • Option reset problem. Upgrade drive firmware to 1.11 or greater to improve the option reset control.
1601 Stack internal fault	• Return the power stack to repair center.
1602 Incompatible stack	• Return the power stack to repair center.
1801 Heatsink thermsistor unplugged	• Return the power stack to repair center.
1901 System Board Data	• The identifying data on the system board is corrupt
1902 System Board Type	• The system board type is not recognized by this version of drive firmware. Update the firmware to the latest version.
2002 Memory allocation error	Record the error message and contact Technical Support
LEAKAGE L TIMEOUT	Cause & Solution: The autotune has attempted to determine the leakage inductance of the motor, but cannot make the required test current. – Problem with motor connection.
MOTOR TURNING ERROR	Cause & Solution: The autotune is trying to find the encoder direction by spinning the motor, but the motor is already spinning. – Wait till the motor stops.
NEGATIVE SLIP FREQ	Cause & Solution: Autotune has calculated a negative slip frequency, which is not valid. Nameplate rpm may have been set to a value higher than the base speed of the motor. – Check nameplate rpm, base frequency, and pole pairs are correct.
TR TOO LARGE	Cause & Solution: The calculated value of rotor time constant is too large. – Check the values of Nameplate Speed and Base Frequency.
TR TOO SMALL	Cause & Solution: The calculated value of rotor time constant is too small. – Check the values of Nameplate Speed and Base Frequency.
MAX SPEED TOO LOW	Cause & Solution: During Autotune the motor is required to run at the nameplate speed of the motor. If 100% Speed in RPM parameter limits the speed to less than this value, an error will be reported. – Increase the value of 100% Speed in RPM parameter up to the nameplate rpm of the motor (as a minimum). – It may be reduced, if required, after the Autotune is complete.
SUPPLY VOLTS LOW	Cause & Solution: The autotune will compensate for low supply volts, down to 70% of motor rated volts. Below this value it will stop the autotune and raise an alert. – Re-try when mains volts are within specification.
NOT AT SPEED	Cause & Solution: The motor was unable to reach the required speed to carry out the Autotune. – Possible reasons include: motor shaft not free to turn; the motor data is incorrect.
MAG CURRENT ERROR	Cause: It was not possible to find a suitable value of magnetising current to achieve the required operating condition for the motor. Solution: – Check the motor data is correct, especially nameplate rpm and motor volts. – Also check that the motor is correctly rated for the drive.
KE TOO LARGE	Cause: Ke value calculated during the autotune (stationary) is too large (the max value is 840V) Solution: – Check the motor data is correct, especially nameplate rpm, rated amps and motor volts. – If low speed motor with a Ke value higher than 840V, enter by hand the corresponding value after the autotune completion.
KE TOO SMALL	Cause: Ke value calculated during the autotune (stationary) is too small (the min value is 1V). Solution: Check the motor data is correct, especially nameplate rpm, rated amps and motor volts.
ALL TESTS DISABLED	Cause: All auto tune tests are disabled. Solution: – Check parameter 0257: Autotune Test Disable.
DEFAULTS LOADED	First power up with new control module Initialise all parameters using the GKP setup wizard or PDQ
APPLICATION MISSING	Cause: – Fault during application download. – Application deleted by the drive Solution: – Re-install the application from PDQ or PDD – Custom applications only: check the application for any delays or loops that may cause the application task to “hang”.
POWER STACK MISMATCH	Cause: Parameter 0987 “Power Stack Required” does not equal the ID of the stack. Solution: Change “Power Stack Required” to match “Power Stack Fitted”. After doing this it may be necessary to restore parameters to default and reconfigure the drive. This is to ensure that all parameters have appropriate values.
APPLICATION DELETED	Cause: Application deleted by the drive. Solution: Custom applications only: check the application for any delays or loops that may cause the application task to “hang”.
FIRE MODE	Cause: Fire Mode has been activated. Solution: If this message is not expected, use PDD to check if the Fire Mode block is in the configuration.
COAST TO STOP	Cause: Attempting to start the drive in local mode with Coast To Stop active. Solution: – The Coast To Stop input is active low. This input needs to be driven high. – The input may be ignored in the standard application by setting “Disable Coast Stop”.
ENABLE VOLTAGE	Cause: Attempting to start the drive in local mode with the Enable input is inactive Solution: The Enable input needs to be driven high. This is done in the default application.
QUICKSTOP ACTIVE	Cause: Attempting to start the drive in local mode with Quick Stop active. Solution: – The Quick Stop input is active low. This input needs to be driven high. – The input may be ignored in the standard application by setting “Disable Quick Stop”.
OPERATION ENABLED	Cause: Attempting to change from Local control to Remote control with the Run signal true. Solution: To change to Remote control, (terminals), ensure that the Run input is false.
MAX SPD GT ATN SPD	Cause: Parameter 0464 “100% Speed in RPM” has been increased since auto-tune. Solution: – Check the value of “100% Speed in RPM”. – It may be necessary to repeat the auto tune with the higher value of max speed.
UNKNOWN STACK	Cause: The stack is understood by the firmware. Solution: Upgraded the drive firmware.
APPLICATION LOAD FAILED	Cause: – Fault during application download. – Application deleted by the drive Solution: – Re-install the application from PDQ or PDD – Custom applications only: check the application for any delays or loops that may cause the application task to “hang”.
COMMS OPTION HARDWARE MISMATCH	Cause: Parameter 0044 “Comms Required” is not compatible with the fitted communications option Solution: – Fit the correct communications option. – Change the application to be compatible with the fitted option, (setting “Comms Required” to NONE will avoid this alert).
COMMS OPTION CONFIGURATION ERROR	Cause: The configuration settings are not compatible with the selected option. Solution: Refer to the communications option manual, “Troubleshooting”.
IO OPTION HARDWARE MISMATCH	Cause: Parameter 1178 “Option IO Required” is not compatible with the fitted IO option Solution: – Fit the correct IO option. – Change the application to be compatible with the fitted option, (setting “Option IO Required” to NONE will avoid this alert).
FEEDBACK MISSING	Cause: Attempt to run in Encoder Feedback control mode with no feedback device fitted, (or configured). Solution: – Change the control mode to VHz or Sensorless – Fit the correct feedback option – Check parameter 1178 “Option IO Required”
IO OPTION CHANGED	Cause: The IO Option has been changed. Solution: IO Option removed, IO Option attached or different IO Option fitted. This alert is for information only and occurs just once following the change.
COMMS OPTION CHANGED	Cause: The Communications Option has been changed. Solution: Comms Option removed, Comms Option attached or different Comms Option fitted. This alert is for information only and occurs just once following the change.
UPDATING LANGUAGE	Cause: Updating the translations held in the GKP. This may happen the first time a language is selected. Solution: – No action required. – The language update should complete within one minute.
PCR NOT CLOSED	Cause: The pre-charge relay is not closed, (probably due to low DC Link volts) Solution: Check the 3-phase input or common supply.
SYSTEM BOARD HARDWARE MISMATCH	Cause: Parameter 1739 “System Board Required” not correctly set. Solution: This indicates that the drive has never been commissioned. It is advised to reset all parameters to their default values.
SYSTEM BOARD CHANGED	Cause: Unreliable connection to the system board Solution: – Power off / on then verify that the system board is functioning correctly. – If this message occurs more than once contact the service department for assistance.