Gear Ratio Codes: What P0730 Actually Measures and How to Read It

A gear ratio code is one of the most misread DTCs in the trade. It gets treated as a verdict — the transmission is slipping, pull it — when it is nothing of the kind. It is an arithmetic complaint: the controller divided one speed by another, compared the answer to what it expected for the gear it commanded, and the two did not agree. That is the entire content of the code.

Everything that matters comes after that. A ratio wrong because a clutch is slipping, a ratio wrong because a reluctor is spinning on its hub, a ratio wrong because a solenoid never stroked, a ratio wrong because a bore plug is dumping line pressure to the sump — four different repairs, one code. The job is to figure out which one you have before anything comes apart.

---

What the Ratio Number Actually Is

The controller has two speed inputs it trusts: input shaft speed (ISS) and output shaft speed (OSS). It divides one by the other:

That is it. Put 2,400 rpm on the input and read 1,475 rpm on the output and the calculated ratio is 1.627. Read 785 rpm out instead and it is 3.06. On a 4L60E those are second gear and first gear, and the controller knows which one it asked for, so it knows immediately whether it got what it ordered.

Every step-gear transmission works this way. The published ratios for the 4L60E family run roughly 3.06, 1.63, 1.00 and 0.70. Third is the easy one to check on any unit with a 1:1 gear, because the answer should be 1.000 and any deviation is obvious without a reference chart. On a 09D the first-gear PID should read 4.148, per a GEARS case write-up by Rob Faucett. Know the number for the unit in front of you before you start reading data.

What Wrong Means to the Computer

Controllers do not flag a ratio the instant it drifts; they use a window and a timer, and the values are published in OEM diagnostic tables. Ed Lee, writing in Transmission Digest, gives the GM threshold plainly: for P0730 to set, the PCM must see a gear ratio off by more than 5% for more than seven seconds. Both halves matter. A brief flare during a shift will not set it, and a 4% error will not set it no matter how long it runs.

The per-solenoid codes are tighter and more specific. Per GM diagnostic document 2005trans6_4L60E, the PCM uses these exact windows to accuse Shift Solenoid A:

Code / condition	Gear commanded	Calculated ratio seen	What that means
P0751, SSA stuck OFF (2-2-3-3 pattern)	1st, for ≥ 2.0 sec	1.2 to 1.8	Asked for 1st, got 2nd
P0751, SSA stuck OFF	4th, for ≥ 1.0 sec	0.95 to 1.15	Asked for 4th, got 3rd
P0752, SSA stuck ON (1-1-4-4 pattern)	2nd, for ≥ 1.0 sec	3.0 to 3.3	Asked for 2nd, got 1st
P0752, SSA stuck ON	3rd, for ≥ 1.0 sec	0.65 to 0.9	Asked for 3rd, got 4th

Read those windows sideways and they are a ratio chart: 3.0–3.3 brackets first, 1.2–1.8 second, 0.95–1.15 third, 0.65–0.9 fourth. GM is not looking for slip in the abstract; it is looking for the ratio of a specific wrong gear, which is why these codes point at a solenoid rather than the unit generally. The fail counter must also reach 2 before the code stores, so a single event does not do it.

Why the Code Sometimes Refuses to Set

If a customer describes a dead-obvious problem and nothing stores, check the enabling conditions before you doubt the complaint. The same GM table requires all of the following before it will even run the shift solenoid performance diagnostic: engine speed above 450 rpm for 5 seconds and not in fuel cutoff, gear range D4, ignition voltage 10 to 18 volts, transmission output speed at or above 150 rpm, transmission temperature between 20°C and 130°C, and no TP, VSS, solenoid electrical or pressure switch DTCs already set.

That last one is the trap. A stored output speed sensor code suppresses the ratio diagnostics entirely, because the controller knows its own math is unreliable. Fix the sensor code first and the ratio codes will show up on the next drive cycle — or they will not, which tells you something too. P0730 also does not command the MIL on some GM applications, so the only clue the customer gets is shift feel.

The First Fork: One Gear Wrong, or All of Them

This is the single most useful question you can ask, and it costs nothing but a scan tool and a road test. Scroll to the gear ratio PID and check the calculated ratio in every gear.

• One gear off, the rest correct. The fault is inside that gear apply path — the clutch or band that holds that ratio, the solenoid that commands it, or the valve and circuit that feed it.
• Every gear off by the same percentage. The fault is in the signal, not the gearset. A clutch pack cannot slip an identical amount in four different gears.

The Transmission Digest write-up by Ed Lee on a 2001 Buick Century with a 4T65E is the textbook version of the second case. The complaint was harsh shifts, the code was P0730, and the technician found third gear — which should be 1:1 — reading low by 10%. First, second and fourth were all low by 10% as well. Ten percent is double the 5% needed to set the code, and an identical error across all four gears rules out component slip on arithmetic alone.

The ISS signal tracked engine speed correctly, the PCM had the correct axle ratio programmed, and the final drive ratio and reluctor tooth count both checked out. The fault turned out to be a 0.120-inch gap between the reluctor and the differential, where it should have been butted flush. Heated with a torch, the reluctor fell off instantly and spun freely on the differential when cold, then gripped again after about ten minutes as operating temperature expanded it. A new reluctor fixed the P0730. That unit could easily have been replaced for nothing.

Output speed sensor mounting deserves the same suspicion. Many applications use shims under the OSS to set air gap between the sensor tip and the signal gear. Leave them out, or stack them in the wrong place, and the tip rides the rotating gear, gets destroyed, and takes the signal with it — and that ratio error looks exactly like a slipping transmission on a scan tool.

The PID Most Techs Never Open: Steady State Adapts

On later GM units there is a data list that will tell you about a slip you cannot feel. The Steady State Adapts are separate from the 1-2, 2-3 and 3-4 shift adapts: shift adapts trim pressure during a ratio change, while the Steady State Adapts trim pressure the rest of the time, to hold a ratio already made.

The rule Sonnax gives is blunt and easy to use: on a healthy unit every Steady State Adapt should read 0 psi. Anything above 0 means the PCM has detected slip in that gear and is raising line pressure to stop it. The computer found the problem before you did.

Two cases from that Sonnax article show why this is worth opening. In the first, a vehicle came in for a harsh 3-4 shift with no slip the technician could feel. The Steady State Adapt for third was running 59 psi above normal. The PCM had detected a third-gear slip, corrected it with line pressure, then went into the 3-4 carrying that extra pressure — which is what made the shift harsh. Teardown found the rubber blown off the third clutch piston.

In the second, a unit with no second gear showed a Steady State Adapt of 249.94 psi in second, with third and fourth normal. The PCM was pushing everything it had at the second clutch and the unit stayed in first. Because that clutch was applied and holding in third and fourth, a hydraulic leak was ruled out and the plates themselves were suspect. Teardown found a failed needle bearing between the second clutch drum and the input drum, with loose needles that had chewed the lining off the second frictions.

Two practical notes. These adapts can raise line pressure 200 psi or more, so a fresh rebuild that whines at the pump or bangs a shift may just be carrying stale adapts — do not chase it until they have had a chance to return to zero. And there is no scanner reset on most applications; the 4T80E is the exception. A long battery disconnect usually walks them back, and they typically zero out after one complete shift cycle on the road.

When the Code Names a Solenoid but the Clutch Is the Fault

Ratio-derived codes that carry a solenoid name are the easiest way to buy an expensive part you did not need. Sonnax technical specialist Jim Dial describes the pattern on the Toyota/Lexus A761, AB60 and A960 six-speeds, which throw P0751 (S1 performance), P0756 (S2), P0761 (S3) and P0766 (S4). These set when the TCM commands a gear and the speed sensors report the wrong ratio. The TCM names the solenoid responsible for that gear as a diagnostic aid — but, as Dial puts it, the identical code sets when the clutch holding that ratio is slipping or neutralling out. The code names a suspect, not a culprit.

On those three units the real fault often is not the solenoid at all. Unusually, the on-off solenoids are fed regulated, non-orificed line pressure straight from the manual valve. A bore plug behind the SR solenoid separates that solenoid feed circuit from a circuit charged in first through fourth. When the plug leaks, line pressure dumps out the exhaust port into the sump — found on a valve body test machine by Jeff Parlee at Valve Body Xpress, who watched oil pour out as soon as the line pressure circuit was charged. The result is low solenoid feed and low line pressure, from a part with no code of its own. Replacing four solenoids would not have touched it.

Mike Brown, writing in ATRA GEARS, narrows the whole class of performance codes to three causes worth remembering: a solenoid stuck open or closed, a blocked valve body or stuck shift valve, or a failed clutch, brake or gear. Only one of those three is a solenoid.

Checking the Electrical Side Properly

Before condemning anything hydraulic, prove the signals. Compare ISS against engine rpm with the converter locked; they should track closely, and a mismatch indicts the input sensor or its reluctor. Compare OSS against a known-good road speed reference. Then confirm the correct final drive ratio and tire size are programmed, because the PCM compares a known axle ratio against a calculated one for each range, and a wrong programmed value skews every gear equally.

Speed sensors are current devices on many European applications, and the draw itself is diagnostic. On the 09D case Rob Faucett documents in GEARS, the spec was less than 0.1 amp in first through fourth and close to 1 amp in fifth and sixth. That unit stored OE code 17115, gear ratio error in first, and the cause was a sticking armature in the N92 solenoid controlling the K1 clutches — cleaned rather than replaced, after which it worked normally.

Checking the Hydraulic Side Properly

If the signals are honest and only one gear is wrong, the next step is pressure, not disassembly. Brown's advice on a Toyota AB60E that stored P2714 and P0776 with no fifth or sixth was to run a line pressure test first, precisely because solenoids on that unit go $250 to $300 each and guessing is expensive. On the bench, air checking tells you whether a circuit holds — use 25 to 30 psi, not full shop air, which can force a seal and give a false pass on a circuit that would never hold in service.

A Diagnostic Order That Works

1. Read all codes and note what is missing. A stored speed sensor or electrical code suppresses the ratio diagnostics. Clear those first.
2. Check fluid level and condition. Low fluid and a restricted filter produce ratio errors no amount of data will explain.
3. Road test with ratio, ISS, OSS and commanded gear graphed. Record it.
4. Apply the fork. One gear off means that gear apply path. All gears off equally means a signal, reluctor or programmed ratio problem.
5. On GM, open the Steady State Adapts. Anything above 0 psi names the slipping gear for you.
6. Line pressure test before parts, especially on units with expensive solenoids.
7. Valve body and circuit inspection. Stuck valves, worn bores and leaking bore plugs mimic both solenoid faults and clutch failure.
8. Teardown last, with the data already telling you which clutch pack to look at first.

Preventing the Comeback

Most ratio-code comebacks trace to three things: reluctors and speed sensors disturbed during the job and not reseated correctly, so verify a reluctor is butted flush and OSS shims went back as they came out; adapts never given a drive cycle to normalize, which makes a good rebuild feel harsh; and a valve body cleaned but not inspected, so the bore wear or leaking plug that caused the original failure goes back in behind new frictions.

The code told you the math was wrong. It never told you why. That part is still the job.