Cadillac CTS
Treat it like any modern GM platform: separate mixture control from ignition/mechanical, validate sensors with live data, and avoid parts-darting when a generic code pops up.
Quick triage (5 minutes)
What to capture
- Codes + freeze-frame
- STFT/LTFT at idle and cruise
- Misfire counters (if available)
- Boost request/actual (if turbo) or load/MAF if NA
- Coolant temp + IAT plausibility
What it usually means
- Lean trims -> unmetered air, MAF bias, fuel delivery, or purge influence.
- Misfire with normal trims -> ignition or mechanical, not mixture.
- Underboost/hesitation -> boost leak, wastegate/actuator issues, or charge-air sensor plausibility.
- Overheat symptoms -> cooling system control or airflow (fans) before blaming the engine.
Common CTS complaints (honest starting point)
- Intermittent misfire: confirm cylinder and conditions; don't replace multiple coils without evidence.
- Surge/hesitation: treat as mixture/airflow first (trims, MAF, leaks), then look at boost control if turbo.
- Rough idle after refuel: EVAP purge/vent behaviour can mimic an ignition problem.
- P0420 after drivability issues: stabilise trims/misfire first; then reassess catalyst efficiency.
Usually is / usually isn't
- Usually is: air/fuel control problems, ignition weakness, or EVAP influence.
- Usually isn't: a "bad ECU" or needing a catalyst without upstream proof.
Typical OBD2 codes you will see
P0171
Lean mixture: trims-first plan that stops guessing.
P0300
Random misfire: use counters + mixture logic to narrow it.
P0456
EVAP small leak: smoke-test logic and simple checks.
P0420
Catalyst efficiency: upstream faults that masquerade as a bad cat.
Confirmatory tests (quick wins)
- Trims split test: compare idle vs 2,000 rpm trims to distinguish air leaks from fuel delivery.
- Smoke test when lean at idle or underboost symptoms are present.
- Misfire move test: only swap coils/plugs after confirming trims are stable.
Trust note: CTS drivability faults are usually solvable quickly when you prove mixture control and misfire behaviour with data first, then confirm with simple tests before replacing sensors.