AutoLogicTools

OBD-II trouble code

P0769: Shift Solenoid "D" Intermittent

The first question on this code is whether your transmission has a solenoid D at all — the SAE letter space runs further than most gearboxes do. The second is where the fault hides: a solenoid serving the upper gears will not misbehave on a road test around town.

High severityPowertrainTransmission / Shift ControlDrivable short-term

Quick facts

System
Powertrain
Category
Transmission / Shift Control
Severity
High severity
Drivable
Usually safe to drive short-term
Repair cost range
$150$900
DIY difficulty
Advanced DIY

What does P0769 mean?

P0769 reports that the module briefly lost and regained a valid electrical picture of whatever it designates as shift solenoid D. Both halves of that sentence need attention, and neither is about the solenoid winding.

Start with the word "whatever". The SAE code list allocates letters well beyond the number of shift solenoids a typical transmission actually contains. A four-speed automatic may have two or three; the alphabet keeps going regardless. So the existence of a code for solenoid D is not evidence that your vehicle has a fourth shift solenoid, and on a good number of applications there is no discrete component you can point at, order or replace under that name. What the module calls D may be an output mapped to a valve that is not scheduling gear changes at all — pressure control, torque converter clutch application, or a function specific to that design. Establishing what the letter refers to on your particular transmission is not a preliminary formality here; it is the step that determines whether a part exists to buy.

That is a materially different starting point from the earlier letters. Solenoid A and solenoid B are near-universal and unambiguous, so their codes lead straight to a component. This one leads to a service manual first, and the number of people who have bought a "shift solenoid D" that does not correspond to anything in their gearbox is not small.

The second thing that separates this code is where the fault can be caught. Where later-letter solenoids do schedule shifts, they generally serve the upper gears — the shifts that only happen once the vehicle has been at road speed for a while. That has a direct and often-missed consequence for testing. A twenty-minute road test around town, with the transmission cycling through its lower gears at every junction, may never command this solenoid at all. The technician returns, reports no fault found, and is entirely correct about what was observed. Reproducing this code requires a sustained run at cruising speed, long enough for the transmission to reach and hold top gear, with data logging running throughout. That is a different test protocol from the one used on the lower-gear solenoids, it takes longer, and it needs a road that permits it.

Both of those points push in the same direction: this is a code where the preparation matters more than the measurement. Confirm the component exists and what it physically is; then design a drive that will actually operate it. Testing before doing either produces a clean result that means nothing, and clean results that mean nothing are how these complaints end up unresolved across several visits.

Common causes

  • No discrete solenoid D on the transmission, with the designation mapped to another controlled output
  • Winding or connector fault on an upper-gear solenoid that is only commanded at sustained road speed
  • Wrong part previously fitted after a parts lookup that did not match the specific transmission
  • Individual conductor to the solenoid intermittently open under vibration
  • Degraded terminal in the case pass-through connector on that channel
  • Contaminated fluid preventing a valve from responding cleanly at the pressures used in the upper gears
  • Control module output driver fault on a channel that is rarely exercised

Symptoms

  • Fault appearing only after extended highway driving and never in town
  • Repeated no-fault-found results after short road tests
  • Erratic behaviour confined to the upper gears or to torque converter lock-up
  • Occasional limp mode during a long trip that clears on the next restart
  • Cruising rpm that occasionally sits higher than normal for the road speed
  • Check engine light appearing at the end of a journey rather than at the start
  • No obvious complaint at all, with the code found during unrelated servicing
  • A previously fitted solenoid that turned out not to match the transmission

Diagnostic steps

  1. 1.Confirm the component exists before anything else. Look up the solenoid complement for your exact transmission and find out what the module designates as D. On a number of applications there is no discrete shift solenoid under that name, and the output is mapped to a different function entirely.
  2. 2.Identify what that output physically controls. Later-letter designations are frequently pressure control or torque converter clutch related rather than shift scheduling, and that changes both the symptom you should expect and the part you would order.
  3. 3.Design a road test that actually commands it. If the solenoid serves the upper gears, a short drive around town will never operate it, and a no-fault-found result from such a test tells you nothing. Plan a sustained run at cruising speed with the transmission held in top gear.
  4. 4.Log throughout the drive rather than reading a snapshot afterwards. You want solenoid command state, gear, road speed and fluid temperature on one trace so the drop-out can be tied to a condition instead of merely noted as having happened.
  5. 5.Check the individual conductor and its pin at the case pass-through for that channel. A rarely exercised circuit can sit corroded for a long time without ever being asked to conduct, so absence of past symptoms is not evidence of a healthy connection.
  6. 6.Verify fluid condition before deciding it is electrical. Upper-gear engagement uses different line pressures from the lower gears, and contaminated fluid can prevent a valve responding cleanly in that range while leaving the rest of the shift schedule unaffected.

Repair cost

$150$900

Diagnosis is $150 to $300 on this code rather than the usual $100, and the reason is honest: an extended highway drive with data logging takes longer than a lap of the industrial estate, and it is the only test that will reproduce the fault. A fluid and filter service is $150 to $350. Where a discrete solenoid does exist and is at fault, it is $350 to $650 fitted on transmissions with valve body access from the pan, and up to $900 where the unit has to be lowered. Do not authorise a part until someone has confirmed, from service data for your transmission, that the component the code names actually exists on it.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with transmission shift solenoid replacement preselected. Adjust labor rate and vehicle category to fit your situation.

DIY vs shop

This is an advanced DIY job. It typically requires specialty tools, scan-tool access, lifting equipment, or careful sequencing to avoid causing new failures. Plan for extended downtime and have a backup vehicle. Most owners are better served by a shop that has done this repair before.

Related codes

Frequently asked questions

Does my transmission even have a solenoid D?

It may well not, and this is the first thing to establish. The SAE code list allocates letters far beyond the number of shift solenoids a typical gearbox contains — a four-speed automatic might have two or three, while the alphabet carries on regardless. On many applications there is no discrete component sold under that name, and what the module designates as D is an output mapped to a valve doing something else, such as pressure control or torque converter clutch application. Look it up for your specific transmission before ordering anything.

My shop road-tested it and found nothing. Why?

Very likely because the drive never commanded the solenoid. Where later-letter solenoids do schedule shifts, they usually serve the upper gears, and a road test around town keeps the transmission cycling through its lower ratios at every junction. The solenoid is never operated, so it never fails, and the report of no fault found is an accurate description of what happened. Reproducing this code needs a sustained run at cruising speed with the transmission holding top gear, and data logging running the whole time.

Why would a rarely used circuit fail at all?

Because sitting idle is its own kind of stress. A connection that is seldom asked to carry current can corrode quietly for years without anyone noticing, since nothing depends on it most of the time. When it finally is commanded, the contact is no longer sound. That is why the absence of any previous symptom on this channel is not evidence that the wiring is healthy, and why the individual pin at the case connector deserves inspection even on a vehicle that has never had a transmission complaint.

Is it safe to keep driving?

The vehicle is driveable and, because the fault is intermittent and confined to the upper gears, it may behave completely normally for most of your driving. The risk is not sudden failure but slow accumulation: erratic engagement puts uneven loading on the clutch packs, and repeated limp-mode entries on the highway are unpleasant and best avoided. Have it looked at while the likely repair is still a connector or a single component rather than internal damage — but there is no need to stop driving it in the meantime.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.