DOCUMENTED DIAGNOSTIC CONTEXT

Diagnostic code articles — Page 14.

Understand what the recorded fault means, which findings change the diagnosis, and what the cited documentation can confirm. Each article states the system or vehicle scope it covers.

Some sources leave details unresolved. Those articles include a visible source note; a code match alone does not establish applicability to your vehicle.

A failed-on solenoid A result must be read against the intended state

Shift solenoid A electrical fault versus a stuck valve

Intermittent solenoid A circuitry needs an electrical event record

Solenoid B continuity and solenoid B function are separate questions

Solenoid B failed-off evidence is accumulated across control events

Solenoid B failed-on monitoring needs the requested state as context

Shift solenoid B circuit monitoring has its own qualification

Solenoid B intermittency should remain distinct from a sticking diagnosis

An open solenoid C path is not established by a poor shift alone

Solenoid C failed-off monitoring weighs unsuccessful and successful events

A solenoid C failed-on result is a functional-state contradiction

Shift solenoid C maps to number 3 in the CW6A-EL

Intermittent solenoid C circuitry needs the complete failure report

Solenoid D open-circuit evidence requires the exact reporting format

Solenoid D failed-off behavior is judged through eligible response events

Solenoid D failed-on evidence should not be renamed as a power short

Shift solenoid D electrical fault in Mazda’s CW6A-EL

An intermittent D-channel circuit result needs a different record from a failed shift

Seventh-gear ratio and unknown gear state are different documented uses

Solenoid E open-circuit monitoring is based on driver evidence

Solenoid E failed-off functionality can remain relevant after a good event

Solenoid E failed-on behavior is distinct from a high circuit signal

The CW6A-EL on/off solenoid electrical circuit

Intermittent E-channel circuitry needs its own event evidence

Quest solenoid B command and feedback must agree

CVT primary-pulley pressure fails to follow a high command

C2 release behavior behind the solenoid B stuck-on code

Solenoid B feedback current fails to follow its target

Output speed can have the right magnitude and the wrong direction

output-speed circuit voltage drops below its electrical boundary

output-speed sensor voltage is electrically too high

Quest shift performance requires more than an electrical code check

The second-to-third shift fails its speed plausibility check

the Jeep 3–4 shift did not produce the expected speed change

Shift-timing solenoid current error under a stable command

Timing solenoid feedback stays low when commanded on

Timing-solenoid circuit stays high under an off command

Intermediate-speed circuit A must not be confused with its plausibility checks

clutch-1 speed checked against independent references

Intermediate-speed A intermittency needs more than an averaged speed trace

Quest solenoid C links converter lockup and shift pressure

CVT line-pressure performance compares both pulley pressures

GR10 solenoid C stuck-on criteria differ from adjacent clutches

SLC2 current feedback differs persistently from demand

Clutch one slip is evaluated while the clutch is loaded and filled

Clutch two has a one-second loaded-slip criterion

Clutch three uses a lower slip threshold than C1 and C2

Clutch four is judged over a short slip interval

Clutch 5 slips despite a locked-state command

A clutch that should release can be detected by unexpectedly low slip

Mode-one clutch-two behavior distinguishes a stuck element

Clutch-three release is evaluated against mode-two torque behavior

Clutch four has different stuck-on tests in two hybrid modes

Clutch 5 does not develop the expected release slip

Park-button switch A reads below its allowed range

Park-button switch A high-signal qualification

Park switch A sits between valid button states

Parking-lock input A frequency and mismatch need separate attention from pulse level

Park-button channel B low-input detection

Park-button switch B exceeds the high-signal boundary

Park-button switch B has an unrecognized intermediate reading

Parking-lock input B has its own frequency or mismatch classification

two valid Park-button channels disagree

input-speed circuit low is distinct from low input RPM

input-speed sensor voltage exceeds the high-input limit

odd-clutch speed input voltage below range

Intermediate speed A high includes pulse-quality checks

Intermediate speed B low is an average signal-voltage check

Intermediate speed B high can also report implausible pulse encoding

tour-mode request remains asserted too long

comfort-mode switch input stays true beyond the monitor interval

normal-mode request remains active in the MYB monitor

eighth gear cannot be confirmed released

Eighth-gear engagement failure depends on speed and actuation progress

Eighth-gear ratio evidence requires a held gear and reliable speed inputs

Park is requested but the actual range does not agree

Drive selection and actual range remain out of agreement

park-lock release retries and unintended engagement

Ninth-gear ratio monitoring is a repeated operating-condition check

Tenth-gear ratio evidence must include stability and repeated failure