When an Eaton H-Max on a supply fan or a chilled-water pump blinks a fault and drops the load, the name on the keypad is only half the story. Next to it is a fault code, an F-number, and that number points at one specific protection function inside the drive. Reading it first keeps you out of the two failure modes we clean up most in Central Florida mechanical rooms: condemning a healthy drive and swapping it (expensive, usually wrong), and hammering reset on a fault that is doing its job until the fan motor finally lets go (cheap, and it ends a motor early). This is a code-by-code field guide to the H-Max faults that actually show up on HVAC fans and pumps, with every meaning and first check traced to Eaton's H-Max HVAC Drives Application Manual (MN04008006E). If a code is not in Eaton's fault table, it is not in this guide.

For the why behind these drives being on the fans and pumps at all, the motor-control and energy fundamentals, start with our pillar explainer, Variable Frequency Drives in the HVAC Market. And if you run other drive lines on the same site, the companion pieces walk the same first-checks discipline: ABB ACH580 Fault Codes on HVAC Fans and Pumps, Danfoss FC-102 Fault Codes on HVAC Fans and Pumps, and Yaskawa Z1000 Fault Codes on HVAC Fans and Pumps. This post assumes you already know what a VFD does and need to get an H-Max running again.

How the H-Max reports a fault

The H-Max keypad shows the fault name and an F-code, and it stores the last 10 active faults plus the last 40 in fault history, each with time-stamped detail you reach by selecting the fault and pressing OK. Two things about the numbering are worth knowing cold. First, one F-code often covers both a hardware trip and a software trip: an overcurrent shows as F1 whether the internal fault ID is 1 (hardware) or 2 (software), and overvoltage is F1's neighbor F2 with IDs 10 and 11. Read the ID under the fault detail when you need to tell them apart. Second, the same fault code you read on the keypad is what lands on the BAS: on a BACnet MS/TP or Modbus job the H-Max exposes the last active fault as a monitor value, so your controls contractor and your service tech are looking at the same number.

One safety habit before you reset anything. Eaton's own caution in the Reset Faults menu is explicit: remove the external control signal before resetting the fault to prevent an unintentional restart of the drive. On a fan that is called by the BAS, clearing a fault while the run command is still present can spin the wheel up on you. Reset once to confirm; if the fault comes back, troubleshoot before you reset again.

Overcurrent and short circuit: F1 and F7

F1 Overcurrent is the one you will see most on fans. Per the manual, the drive has detected too high a current, more than four times the drive's rated current, in the motor cable, and it names the usual causes directly: a sudden heavy load increase, a short circuit in the motor cables, or an unsuitable (mis-sized) motor. That first cause fits a plenum fan wheel with a lot of rotating mass exactly. First checks, in the order Eaton lists them:

• Check the loading. Lock out and bar the shaft over by hand. On a fan, a seized bearing, a wheel packed with cottonwood, or a backdraft damper stuck closed spikes current on start. On a pump, a closed isolation valve or an air-bound casing does the same.
• Check the motor and check cables and connections. The manual calls out both. Disconnect the motor leads at the drive and megger the cable and the windings if you suspect a short before you re-energize.
• Make an identification run. Eaton lists the ID run as a first check for F1: it lets the drive re-learn the motor so its current model is right.
• Check the ramp times. Because a sudden load increase is a named cause, a gentler acceleration time is often the fix on a big fan that only trips F1 on start.

F7 Saturation is the harder cousin and the manual is blunt about it: the causes are a defective component or a brake-resistor short circuit or overload, it cannot be reset from the keypad, and the instruction is to switch off power and do not reconnect, contact the factory. There is one field-useful line: if F7 appears at the same time as F1, check the motor cables and motor. A dead short on the load side can drive both. Treat F7 as a hard stop, not a reset-and-run.

Ground faults: F3

F3 Earth (ground) fault is the code that finds moisture and insulation breakdown, which on roof-mounted AHU and cooling-tower fans in Florida is a matter of when, not if. The manual explains the mechanism plainly: current measurement has detected that the sum of the motor phase currents is not zero, which points at an insulation failure in the cables or the motor. Eaton's remedy is short and specific: check the motor cables and the motor. In the field that means locking out, then meggering the motor and the cable to ground; a reading that collapses when a rooftop curb is wet is the classic Florida F3. Do not defeat a ground fault to keep a fan running: a wet motor to ground is a shock and fire path.

Bus and supply: F2, F9, and F10

These three tell you about power quality on the DC bus and upstream of the drive, which matters in a climate where summer afternoon storms and utility switching hammer the grid.

• F2 Overvoltage. The DC-link voltage has exceeded its limit. Eaton names the causes in order: too short a deceleration time, the brake chopper disabled, high overvoltage spikes in the supply, or a start/stop sequence that is too fast. On a high-inertia fan decelerating quickly, the motor pumps energy back into the bus and pushes it over. The manual's fixes, in order: make the deceleration time longer, use a brake chopper or brake resistor (options), activate the overvoltage controller, and check the input voltage. If the fan must stop fast, the answer is a brake resistor, not just a longer ramp.
• F9 Undervoltage. The DC-link voltage is under its limit. Eaton lists the most probable cause first, too low a supply voltage, then an internal fault, a defective input fuse, or an external charge switch that did not close, and adds a detail techs miss: this fault is activated only when the drive is in the Run state. The remedy is to reset after a temporary supply break, then check the supply voltage; if it is adequate, the failure is internal. Same hunt as a dropped phase: incoming voltage, fuses, and the disconnect.
• F10 Input phase. The manual keeps it to one line: an input line phase is missing. Check the supply voltage, the fuses, and the cable. A corroded lug dropping one incoming phase is the usual Florida cause, and a drive that trips F10 under load but not at idle is telling you one input phase is intermittent.

Motor phase missing: F11

F11 Output phase supervision means the H-Max is watching its own output and found a problem: current measurement has detected that there is no current in one motor phase. Eaton's remedy is to check the motor cable and the motor. This shows up after a contactor swap, a bypass change, or a lug that vibrated loose on a rooftop unit, not on a system that ran fine for years. If you get F11 right after someone did panel work, suspect the connection they just touched.

Drive and motor temperature: F13, F14, F41, F32, F16

Florida runs these drives hot, and the H-Max splits temperature faults by which sensor is reporting. Reading the number tells you which enclosure to open and whether the problem is the drive or the motor.

• F14 AC drive overtemperature (heatsink). Too high a temperature measured in the power unit's heatsink or board, the heatsink is over 100 degrees C. This is the seasonal one. Eaton's checklist is the one to work: check the correct amount and flow of cooling air, check the heatsink for dust, check the ambient temperature, and make sure the switching frequency is not too high in relation to ambient temperature and motor load. In a mechanical room that reads 105 degrees F in August, a dust-caked heatsink is the number-one cause. Blow it out.
• F41 IGBT temperature. The manual defines this as the IGBT temperature (unit temperature plus an I squared T calculation) being too high, and its checks are load-focused: check the loading, check the motor size, and make an identification run. F41 is the drive telling you the switching devices are cooking under current, so it points at load and sizing more than at ambient.
• F13 AC drive undertemperature. The rare inverse: the heatsink is under minus 10 degrees C. You will not see this in Florida service, but it is worth recognizing on a drive that sat powered off in a cold shipment or an unconditioned space overnight.
• F32 Fan cooling. The drive's own cooling fan has reached the end of its rated life. Eaton's remedy is to change the fan and reset the fan lifetime counter. A failed heatsink fan is often what drives an F14 later, so an F32 is your early warning: replace it before the heatsink climbs.
• F16 Motor overtemperature. Different sensor, different fix. The motor is overloaded per the drive's thermal model. Eaton says to decrease the motor load, and if no motor overload actually exists, to check the temperature-model parameters. On a belt-drive fan held at low speed for long stretches, this is frequently a real condition, not a glitch (see the affinity-law note below).

Motor protection: F15, F16, and F17

These are the codes most tempting to reset away, and the ones most likely to be saving a motor.

• F15 Motor stalled. The manual's cause and remedy are as tight as they get: the motor is stalled, check the motor and load. This is the low-speed, high-torque version of an overcurrent: a fan or pump that cannot break away. Find the mechanical cause, a seized bearing, a jammed damper, a valve closed against a pump, before you widen any stall setting.
• F16 Motor overtemperature. Covered above, and it belongs here too: it is a genuine motor-protection trip. Before you assume a bad sensor, treat a repeat F16 as the drive protecting a motor that is running hotter than nameplate allows.
• F17 Motor underload. The opposite tell, and a useful one on pumps: the motor is underloaded, check the load. On a pump this often means a broken coupling, a snapped belt on a fan, a dry or de-primed pump, or a system that lost its load (a broken shaft or an open dump). Eaton's F17 is the code that catches a fan or pump that is spinning but no longer moving air or water.

F19 Power overload rounds out this group: drive power is too high, decrease the load. It comes in a short-time and a long-time supervision flavor and, like F16, points at a system asking the drive for more than it is rated to give.

Comms, inputs, and safety: F51, F52, F53, F66, and F101

These do not mean the drive is broken. They mean it lost a signal it needs, or a protection wired into it did its job.

• F51 External fault. A digital input programmed as an external fault has opened. This is the H-Max reporting something outside itself: a firestat, a smoke-detector relay, a vibration switch, or a starter-fault contact wired into the drive. Check the device that opened the input before you assume a drive problem.
• F52 Keypad communication fault. The connection between the control keypad and the drive is broken. Eaton's remedy is to check the keypad connection and the keypad cable. On a drive in local control, a loose keypad ribbon faults it rather than let it run blind. Reseat it.
• F53 Fieldbus communication fault. The data connection between the fieldbus master and the fieldbus board is broken. Check the installation and the fieldbus master. On a BACnet MS/TP or Modbus AHU, this is a lost BAS link, a daisy chain missing its terminating resistor or a dropped shield under electrical noise, not a drive defect.
• F66 Thermistor fault. The thermistor input has detected an increase in motor temperature. Eaton's checks: check the motor cooling and load, then check the thermistor connection, noting that if the thermistor input is not in use it has to be short circuited. A thermistor input left open reads as a fault on a perfectly cool motor, so an unused input that was never jumpered is a common false F66.
• F101 Process supervision fault (PID1). On an H-Max running its own PID loop for duct static or pump pressure, this trips when the feedback value stays outside the supervision limits past the set delay. It is not a drive defect: it means the process is not reaching setpoint, which points at a stuck damper, a failed sensor, or a system that cannot make the demand. F105 is the same trip on the second PID loop.

Why the low-speed motor faults matter: the affinity laws

Several checks above, a motor overheating at low speed (F16), a thermal-model trip, a stall at low Hz (F15), trace back to how these drives save energy in the first place. Fan and pump power follows the cube of speed. The U.S. Department of Energy's guide Variable Speed Pumping: A Guide to Successful Applications states that the power a pump draws varies with the cube of its speed, which is why matching speed to demand produces such large savings. Slow a fan to 80% speed and shaft power falls to roughly 0.8 cubed, about 51%, so you get four-fifths of the airflow for about half the draw. That cube law is the whole economic case for putting an H-Max on a constant-volume AHU in a Florida climate that runs 4,000-plus cooling hours a year. But the same physics means the drive spends much of its life at reduced speed, where a self-cooled TEFC motor gets less airflow over its own frame. That is exactly why motor-side codes like F16 and F19 deserve a real look instead of a reset: the drive is often reporting the predictable downside of the very thing that saves the energy.

A reset discipline for the field

One rule keeps you out of trouble on an H-Max: read the F-code, decide whether it is protecting something physical, and only then reset. Overcurrent (F1), saturation (F7), ground fault (F3), motor stall (F15), motor overtemperature (F16), and power overload (F19) all point at a real condition; find it first. The overvoltage, undervoltage, input-phase, temperature, and comms codes are usually a wiring or settings hunt you can work methodically. Log the code, the date, and what you found. On a fleet of rooftop units the pattern in those logs, every F14 on the same drive every August, or every F1 on the same fan on start, tells you more than any single trip. Remember Eaton's own caution to remove the external control signal before resetting so a called fan does not restart on you, and that F7 cannot be cleared from the keypad by design. If a fault re-trips after one confirming reset and the mechanical and electrical checks come back clean, that is the point to escalate to a drive-level diagnosis, not before.

Serving Orlando and Central Florida, we supply, program, and service Eaton H-Max HVAC drives on commercial AHUs, cooling towers, and chilled- and condenser-water pumps. If a code in this list is re-tripping on your equipment, we can walk the first checks with your team or come turn a wrench.