Cylinder Power Balance Testing: Finding the Weak Cylinder

The short version — You kill one cylinder at a time and watch how much RPM drops; a cylinder that barely changes the idle speed when disabled is the one that wasn't pulling its weight in the first place.

Why this test exists and what it tells you

The whole idea behind a cylinder power balance test is comparing engine speed drop as each cylinder is momentarily disabled in turn, one after another. You're not trying to fix anything with this test — you're trying to point your finger at the right cylinder before you start pulling parts.

The purpose is to localize a mechanical or ignition/fuel problem to one specific cylinder without tearing the engine apart. Once you know which cylinder is weak, you send it on to the real diagnostic tools — compression test, leak-down test, injector checks, ignition checks. The balance test doesn't tell you what's wrong with the cylinder. It just tells you which cylinder to investigate further.

How the test is actually run

The sequence is simple and always the same:

• Run the engine at idle or at a specified test speed.
• Disable one cylinder at a time — cut its spark, ground its coil, or command injector shutoff through the scan tool.
• Record the RPM drop that results.
• Move to the next cylinder and repeat, one at a time, until every cylinder has been tested.

You can do this with a scan tool that has a cylinder-balance or power-balance function, or the older-school way with a tachometer/DVOM and a manual cylinder-disabling method. Either way the logic is identical — the equipment just automates the disabling and the math for you.

Reading the results

Here's the core logic you need to lock in:

• A healthy cylinder, when shut off, causes a measurable, roughly equal RPM drop compared to the other good cylinders. Makes sense — it was doing its share of the work, so taking it away costs you a chunk of RPM.
• A weak or dead cylinder causes little or no RPM drop when disabled, because it wasn't contributing much power to begin with. You can't lose what wasn't there.
• So the cylinder that shows a noticeably smaller RPM drop (or lower calculated power percentage) than the rest is the one contributing less power — that's your flag for further diagnosis.

If the drops are uneven across multiple cylinders, that pattern can point toward different root causes: mechanical issues (worn rings, valve problems), ignition faults (weak coil, fouled plug), or fuel delivery faults (clogged injector, low injector resistance). But be careful here — the pattern only narrows the search. It does not by itself identify the exact cause. You still need the pinpoint test (compression, leak-down, ignition, fuel) to nail it down.

Safety and limits of the test

Two things to keep straight before you touch a live engine:

• On engines with individual ignition coils, grounding a spark output the wrong way (instead of disabling the coil's primary control) can damage the ignition module or the coil driver circuit. Always disable through primary control or scan tool command when the system uses individual coils — don't just ground the secondary output.
• A passing balance test does not clear the engine of all mechanical problems — specifically, it can't catch something affecting all cylinders evenly, like uniform low compression across the board. If every cylinder is down by the same amount, disabling each one in turn will still show even RPM drops, because they're all equally weak. The test only exposes unevenness between cylinders, not a uniform shortfall shared by all of them.
• The balance test result only tells you what action is needed when you correlate it with other tests. By itself it's a pointer, not a diagnosis.

Easy to mix up

• "No RPM drop" vs. "even RPM drop" — a healthy cylinder gives you a drop when disabled; a weak cylinder gives you little or none. Don't confuse a small drop (bad cylinder) with a normal drop (healthy cylinder) — you're comparing the weak one against the pattern of the rest.
• Pattern narrows, doesn't diagnose — uneven drops across several cylinders suggest mechanical, ignition, or fuel causes, but that pattern alone never tells you which of the three it is. You still need compression, leak-down, or injector/ignition testing to close the loop.
• Grounding the coil output vs. disabling primary control — on individual-coil systems, grounding the wrong point can fry the module or driver circuit. Disable through primary control or scan tool command instead.

Check yourself

Question: During a power balance test, cylinder #3 shows almost no RPM drop when disabled, while the other cylinders all drop about the same amount. What does this tell you?

Cylinder #3 was already contributing very little power before it was disabled — that's why killing it didn't change the idle speed much. This flags #3 for further pinpoint testing (compression, leak-down, ignition/fuel checks) to find out why it's weak.

Question: Technician A says a passing (even) power balance test proves there's no compression problem anywhere in the engine. Technician B says a power balance test can miss a compression problem if it affects all cylinders equally. Who is right?

Technician B is right. The balance test only exposes differences between cylinders. If every cylinder has the same low compression, disabling each one in turn still produces even RPM drops, so the test can pass even though a uniform mechanical problem exists across all cylinders.

Question: On an engine with individual ignition coils, what's the risk if you disable a cylinder by grounding the coil's spark output instead of controlling the coil primary?

Grounding the spark output the wrong way (rather than disabling through primary control) can damage the ignition module or the coil driver circuit. Always disable via primary control or scan tool command on these systems.