The Yaskawa Z1000 is a purpose-built HVAC drive, not an industrial drive pressed into fan duty, and it tells you exactly what tripped it if you can read its two-and-three-character codes. When a Z1000 on a supply fan or a chilled-water pump trips, the ALM indicator lights, the fault code appears on the Hand-Off-Auto (HOA) keypad, and the MA-MB-MC fault relay changes state so the building automation system sees it too. That short code, something like oC or GF or oV, points at one specific protection function. Reading it correctly is the whole game. The two mistakes we clean up most in Central Florida mechanical rooms are the same on any drive line: condemning a healthy drive and swapping it (expensive, usually wrong), and hammering reset on a fault that is doing its job right up until the motor lets go (cheap, and it ends a fan motor early). This is a code-by-code field guide to the Z1000 faults that actually show up on HVAC fans and pumps, with every meaning traced to Yaskawa's own alarm and fault list for the Z1000 and the shared HVAC-drive fault definitions. If a code is not in Yaskawa's table, it is not in this guide.

If you need 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. If you also run other drive lines, the companion pieces walk the same first-checks discipline: ABB ACH580 Fault Codes on HVAC Fans and Pumps and Danfoss FC-102 Fault Codes on HVAC Fans and Pumps. This post assumes you already know what a VFD does and need to get a Z1000 running again.

How the Z1000 reports a fault, and the fault history that tells you why

The Z1000 separates minor faults and alarms from faults. An alarm (a minor fault) lets the fan or pump keep running while the drive flags a condition it does not like; the ALM LED blinks and the code shows, but the load stays on. A fault stops the output immediately to protect the drive, motor, or cable, the ALM LED goes solid, and the MA-MB-MC fault contact trips. On a BACnet MS/TP, Metasys N2, APOGEE FLN, or Modbus job (the Z1000 and its bypass sibling speak all of these), the same code you read on the HOA keypad is what your controls contractor sees in the BAS. Faults latch until reset, and a fault that re-trips on reset is almost always reporting a real condition, not a nuisance. Reset once to confirm; if it comes back, troubleshoot before you reset again.

Before you touch anything, use the drive's own memory. The Z1000 keeps a fault history and a set of monitors that snapshot conditions at the moment of the trip. The U2 monitors show the output frequency, output current, and DC bus voltage at the fault, and the U3 group holds the last several faults with the elapsed operating time on each. That fault trace is the difference between guessing and knowing: an oC logged at 2 Hz on a start is a jammed load or a short, while the same code logged at full speed on a hot afternoon is a different hunt. Read U2 and U3 first, every time.

The overcurrent and short-circuit family: oC and SC

oC, Overcurrent is the single most common fault we clear in the field. Yaskawa defines it as drive output current exceeded the overcurrent detection level. It is not always a "too much load" problem; a short or a ground on the output side shows up here too. First checks, in order:

• Mechanical load first. On a fan, a seized bearing, a bird screen or coil packed with cottonwood, or a backdraft damper that failed closed will spike current on acceleration. On a pump, a closed isolation valve or an air-bound casing does the same. Lock out and bar the shaft over by hand.
• Acceleration time. A ramp too aggressive for the connected inertia (a big plenum fan wheel carries a lot of rotating mass) trips oC on start. Lengthen the acceleration time (parameter C1-01) and re-test.
• Output short or ground. Lock out, disconnect the motor leads at the drive, and megger the cable and windings to ground and phase-to-phase. A nicked cable in a wet Florida roof curb reads fine until it rains, then trips oC or GF.
• Motor data and sizing. Confirm the motor rated current (E2-01) matches the nameplate and that the drive is rated for the motor. A drive dropped a size to save cost trips on any real load.

SC, IGBT Short Circuit or Ground Fault is the hard-fault cousin. Yaskawa attributes it to an IGBT failure or a short on the output, and the manual's own guidance is to cycle power to the drive and check whether the fault returns. This is not a reset-and-run-in-Auto condition. Lock out, disconnect the motor leads, and megger the cable and motor before you re-energize. If SC returns with the motor leads disconnected, the power section is suspect and the drive needs bench-level diagnosis.

Ground fault: GF

GF, 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. Yaskawa's definition is specific: a current short to ground exceeded roughly 50% of the rated output current. First checks: remove power and megger the motor and cable to ground (a reading trending toward the low megohms on a running motor is suspect), inspect the leads where they pass through the roof curb or a flex connector, and confirm no power-factor-correction capacitors sit between the drive and motor (they belong on the line side only). Do not defeat GF to keep a fan running: a ground fault on a wet motor is a shock and fire path.

DC bus and mains: oV, Uv1, and PF

These tell you about power quality upstream of the drive, which matters in Florida where summer afternoon thunderstorms and utility switching hit the grid hard.

• oV, DC Bus Overvoltage. Yaskawa: the DC bus voltage exceeded its trip level, typically because deceleration time is too short and regenerative energy is flowing from the motor back into the drive. On a high-inertia fan decelerating, the wheel drives the motor as a generator and pushes the bus over. The fixes, in order: lengthen the deceleration time (C1-02), enable stall prevention during deceleration (L3-04) so the drive stretches the ramp on its own, and confirm the supply voltage matches the drive rating. If the fan must stop fast, the real answer is a dynamic braking resistor, not just a longer ramp.
• Uv1, DC Bus Undervoltage. The DC bus dropped below its undervoltage level (set by L2-05). Yaskawa ties it to low incoming voltage or an input phase loss. Check the incoming three-phase, the input fuses, and the disconnect. A single dropped phase from a corroded lug is the usual Florida culprit, and it often shows up as Uv1 under load but not at idle.
• PF, Input Phase Loss. Yaskawa: drive input power has an open phase or a large voltage imbalance. Same hunt as Uv1: input fuses, the disconnect, loose or corroded power lugs, and supply imbalance. PF and Uv1 frequently travel together because they share a root cause on the line side.

Output phase loss: LF

LF, Output Phase Loss means a phase is missing on the output side of the drive, between the drive and the motor. Check that all three output leads are landed and tight, look for an open winding, and inspect any output contactor or bypass contactor that may have opened under power. LF 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 LF right after panel work, suspect the connection someone just touched.

Over-temperature: the drive (oH1) versus the motor (oH3 and oH4)

Florida runs these drives hard, and Yaskawa splits over-temperature into two groups that are easy to confuse. Reading the code tells you which enclosure to open. In an unconditioned rooftop AHU section or a mechanical mezzanine that hits 105 degrees F in August, the drive-side fault is a seasonal event, not a defect.

• oH1, Heatsink Overheat is the drive's own power section running hot: the heatsink temperature exceeded its limit. Checks: verify airflow and cooling-fan operation, clear the fine dust that coats every Florida mechanical room off the heatsink fins (the number-one cause, blow it out), confirm ambient is within the drive rating and the clearances above and below the drive are open, and consider lowering the carrier frequency (C6-02) since a higher carrier makes the IGBTs run hotter. If the drive's own cooling fan has failed, replace it; a Z1000 will keep tripping oH1 every hot afternoon until the fan moves air again.
• oH3, Motor Overheat Alarm and oH4, Motor Overheat Fault are your motor temperature protection when a motor PTC thermistor is wired to the drive's analog input. oH3 is the warning stage and oH4 is the trip. On a belt-drive fan held at low speed for long stretches, a self-cooled TEFC motor loses much of its own shaft-fan airflow, so oH3 and oH4 are often reporting a real motor condition, not a sensor glitch. Confirm the PTC is landed on the correct terminal and the input is configured for it before you assume the motor is actually hot, but do not widen a limit to make the code go away without checking the motor first (see the affinity-law note below).

Overload: oL1 (motor) and oL2 (drive)

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

• oL1, Motor Overload is Yaskawa's electronic thermal protection: the drive's thermal model integrated enough over-nameplate current to protect the motor. It is governed by the motor overload protection selection (L1-01) and the correct motor rated current (E2-01). This is the one people most want to reset. Before you touch a parameter, find out why the motor draws more than nameplate: a fan pushing against a dirty filter bank, a pump with a failed check valve short-circuiting flow, or a motor simply undersized for the static it now sees after a duct change. Confirm E2-01 matches the nameplate FLA; a wrong value throws off the whole thermal model.
• oL2, Drive Overload is the drive protecting itself: the output current stayed above the drive's own overload rating long enough to trip. Same discipline as oL1, plus check that the drive is not undersized for the connected motor and that a long low-speed operating point is not asking for high torque the drive cannot deliver continuously. Lengthening the accel or decel time helps when oL2 is a start-transient problem; a chronic oL2 at steady state means the load, the sizing, or the setup is wrong.

Comms and external faults: CE, bUS, and EF

These do not mean the drive is broken. They mean it lost a signal it needs, or something outside the drive told it to stop.

• CE, MEMOBUS/Modbus Communication Error means the drive stopped receiving valid Modbus data within its timeout. Yaskawa points at faulty communications wiring or a short. On a Modbus RTU job, check the R+, R-, S+, S- terminals, the shield and termination, and the master. A daisy chain missing its terminating resistor drops out under the electrical noise of a busy mechanical room.
• bUS, Option Communication Error is the fieldbus option card's version of the same problem: no signal was received from the master (PLC) over the option, which on the Z1000 carries BACnet, Metasys N2, or APOGEE FLN. Check the option card seating and its network wiring before you suspect the drive.
• EF, External Fault. An external device wired to a digital input told the drive to fault. The code identifies which terminal (for example EF1 through the numbered terminal faults). This is often a firestat, a smoke-detector relay, a freezestat, or a duct high-limit doing its job. Trace the external contact and clear its cause before you reset; the drive is the messenger, not the problem.

Why the low-speed faults matter: the affinity laws

Several of the checks above (long low-speed running that overheats a TEFC motor, a fan that draws over nameplate against a fouled coil) 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 or fan needs varies with the cube of motor 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 entire economic case for putting a Z1000 on a constant-volume AHU in a Florida climate that runs 4,000 or more cooling hours a year. But the same physics means the drive spends much of its life at reduced speed, where a self-cooled motor gets less airflow over its own frame. That is exactly why motor-side codes like oL1, oH3, and oH4 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 a Z1000: read the code, read U2 and U3 for the conditions at the trip, decide whether the fault is protecting something physical, and only then reset. Overcurrent (oC), short circuit (SC), ground fault (GF), motor overload (oL1), and motor overheat (oH3, oH4) all point at a real condition; find it first. The DC bus, mains, over-temperature, and comms codes are usually a wiring or settings hunt you can work methodically. Log the code, the date, the U2 snapshot, and what you found. On a fleet of rooftop units the pattern in those logs, every oC on the same fan every August, tells you more than any single trip. If a fault re-trips after one confirming reset and the mechanical and electrical checks above 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 Yaskawa Z1000 and Z1000 Bypass 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.