ABB VFD Fault 73F0 Over Frequency

Getting the 73F0 Over Frequency fault on your ABB ACS880 or ACS580 drive? Learn how to adjust speed limits and verify voltage parameters to clear this error.

 

If you are working with modern ABB industrial drives (like the ACS880, ACS580, or ACS380) and your production stops with Fault 73F0, the drive has activated its speed-limit protection. Specifically, 73F0 stands for Over Frequency.

In simple terms, the drive has detected that the output frequency going to the motor has exceeded the safety limits programmed into the software. This is a critical safety trip designed to prevent mechanical damage to the motor bearings, couplings, or the driven machine. Here is a human-made guide to help you find the root cause and get your motor back within safe limits.

Why Does Fault 73F0 Occur?

The drive doesn't just "go fast" on its own. The 73F0 fault is usually triggered when the actual output frequency overshoots the maximum threshold defined in the drive's parameter settings. This can happen due to poor tuning, an incorrect reference signal from a PLC, or a mismatch in voltage settings.

Step-by-Step Troubleshooting Guide

1. Check Frequency Limits (Parameter Group 30)

The first place to look is the "safety fence" you have built around your motor. If these limits are set lower than what the process requires, the drive will trip as soon as it tries to reach full speed.

• Parameter 30.13 (Minimum frequency): Ensure this is not set to a value higher than your intended operating range.
• Parameter 30.14 (Maximum frequency): This is the most common culprit. If your motor is rated for 60Hz, but this parameter is accidentally set to 50Hz, any command to run at full speed will trigger a 73F0 fault.
• The Fix: Verify the motor nameplate frequency and ensure 30.14 is set to that value (or slightly above to allow for minor overshoots during acceleration).

2. Verify Supply Voltage Settings (Parameter 95.01)

Frequency limits and voltage are closely linked in the drive's internal mathematical model. If the drive "thinks" it has more or less voltage than it actually does, the flux calculations can become unstable, leading to a frequency spike.

• Check Parameter 95.01 (Supply voltage): Ensure this setting matches your physical incoming AC power (e.g., 380V, 400V, or 480V).
• Measurement: Use a multimeter to measure the actual voltage at the L1, L2, and L3 terminals. If the measured voltage is significantly different from the 95.01 setting, correct the parameter.

3. Analyze the Reference Signal (PLC/HMI)

If you are controlling the drive via a PLC or an external potentiometer, the "Speed Reference" might be sending a value that is too high.

• Check the incoming reference signal in Parameter 01.01 (Used motor speed) and 01.06 (Output frequency).
• If the PLC sends a reference of 70Hz while the drive is capped at 60Hz, a sudden load change could cause the frequency to "flicker" above the limit, triggering 73F0.

4. Check for "Overhauling" Loads

In applications like conveyors or cranes, gravity can sometimes pull the load faster than the motor wants to go. This forces the motor to act as a generator and can cause a momentary surge in frequency.

• The Fix: If you have an overhauling load, ensure your Braking Resistor is functioning correctly and that Deceleration Ramp times are not too short.

Summary Checklist for 73F0

Checkpoint	Action Required
Parameter 30.14	Increase the Maximum Frequency to match the motor nameplate.
Parameter 95.01	Confirm the supply voltage selection matches the grid.
PID Tuning	If the frequency oscillates, reduce the Gain on your speed controller.
Braking	Check for regenerative energy from high-inertia loads.

Technician's Tip: If the 73F0 fault occurs immediately upon starting the drive (even before the motor turns), you likely have a corruption in the drive's internal "Motor Model." Try performing a new ID Run (Identification Run) to let the drive relearn the motor's electrical characteristics.