All Brands · ECM Diagnostic StrategyMedium

Companion Codes Root Cause Diagnosis Order: Diagnosis and Fix Order

Guide Code-Order (FMI N/A) — Diagnostic guide for diagnosing companion fault codes in correct root-cause order on heavy-duty diesel

4.8/5· 128 reviews

Quick Answer

Companion codes share one root cause. Fix upstream first: power supply (FMI 3/4) before sensors, fuel supply before injection, DEF quality before SCR efficiency. Repair the first code in the chain — companions should clear on the next drive cycle.

Overview: All Brands Guide Code-Order

A single failure cascades into multiple codes. Water in fuel sets rail pressure low, which sets misfire, which sets exhaust temp high. Replacing the misfiring injector fixes nothing if water is still in the tank. Companion code diagnosis means finding the first domino, not replacing every part each code names.

Repair Snapshot

Time

1 - 4 Hours

Difficulty

Advanced

Parts Cost

$50 - $3,000

Dealer Labor

$300+

Tools Required

  • Noregon JPRO
  • Cummins INSITE
  • Detroit DDDL
  • OEM Fault Code Tree Chart

What Guide Code-Order Means

Companion codes share a root cause — fix upstream faults first. Example order: SPN 97 (water in fuel) before SPN 157 (rail pressure low) before SPN 1323 (misfire). SCR chain: SPN 4334 (DEF quality) before SPN 3361 (SCR efficiency) before SPN 3226 (outlet NOx). Use OEM code trees and fix power/supply codes before component codes.

Symptoms Drivers Notice

  • 5–15 codes active simultaneously after single event
  • Codes across multiple systems — fuel, engine, aftertreatment
  • Repairing one code causes two new codes to appear
  • Same code family recurring after component replacement
  • Voltage supply codes (FMI 3/4) present with sensor codes (FMI 2/9)

Most Likely Root Causes

Fuel contamination cascading to injection codes

Common

SPN 97 water in fuel leads to SPN 157 rail pressure low and SPN 1323 misfire — fix fuel, injection codes clear.

DEF quality failure cascading to SCR codes

Common

SPN 4334 DEF quality triggers SPN 3361 SCR efficiency and SPN 3226 outlet NOx — fix DEF before sensors or catalyst.

Battery or ground supply affecting multiple sensor circuits

Common

Low supply voltage sets FMI 4 on multiple sensors simultaneously — one ground strap fix clears 5+ codes.

Common Misdiagnoses (Don't Waste Parts)

Replacing every component each code names

Why it happens: Code list looks like a parts order.

Do this instead: Group codes by system and find upstream fault — one fuel filter fixes SPN 1209, 157, and 1323 together.

Fixing SCR catalyst for efficiency codes with bad DEF

Why it happens: SPN 3361 points at SCR component.

Do this instead: Parts-cannon trap — verify DEF at 32.5% and dosing pressure at 130–145 PSI before any catalyst work.

Clearing all codes after partial repair

Why it happens: Some companions cleared, screen looks clean.

Do this instead: Drive cycle first — unfixe upstream fault repopulates entire code chain within one trip.

Master Tech Commentary

Mechanic's Notes

Ten codes on the screen is usually two problems, not ten. Water in fuel (SPN 97) creates rail pressure (SPN 157) creates misfire (SPN 1323) — fix the water, the other two clear. Start at the beginning of the chain.

Step-by-Step Diagnostic Procedure

  1. Step 1: Snapshot all active codes with timestamps in JPRO or INSITE — group by system: power/supply, fuel, engine, aftertreatment, chassis.
  2. Step 2: Fix FMI 3 (voltage high) and FMI 4 (voltage low) supply codes first — sensor codes downstream are often symptoms of bad power.
  3. Step 3: Follow OEM code tree: fuel supply (SPN 1209, SPN 157) before injection (SPN 1323); DEF quality (SPN 4334) before SCR efficiency (SPN 3361, SPN 4364).
  4. Step 4: Repair highest-upstream code in each chain, then clear codes and drive cycle — companion codes should drop without separate repair.
  5. Step 5: If companion codes return after upstream fix, the root cause repair was incomplete — recheck supply voltage at 12.0–12.6 V and component operation.

Professional service / OEM-level scan tools are recommended before clearing this fault for good.

Live Data & Freeze-Frame Tips

Group active codes by timestamp in JPRO or INSITE — codes setting within same second are companions. Check supply voltage (12.0–12.6 V), fuel rail pressure (5,000–26,000 PSI), DEF quality (32.5%), and oil pressure (40–70 PSI) as upstream health indicators before component-level diagnosis.

Safety Warnings

  • Do not clear companion codes without fixing upstream root cause — derate timers may reset but fault returns.
  • Fuel system companions from water contamination can cause injector damage — address SPN 97 before cranking extensively.
  • Multiple active stop-engine codes require shutdown — prioritize SPN 100 (oil pressure) and SPN 110 (coolant temp).

When to Limp In vs Tow

Tow when companion codes include active derate with upstream fuel or DEF fault that cannot be resolved roadside.

Prevention Tips for Fleets & Owner-Operators

  • Use OEM fault code trees for your engine platform — Cummins INSITE and DDDL include diagnostic flowcharts.
  • Address first-occurrence pending codes before they cascade into active companion sets.
  • Maintain fuel and DEF quality to prevent multi-code cascade events.
  • Document code groups in repair orders — pattern recognition speeds future diagnosis.

Related Fault Codes

SPN 97 FMI 1 — Water in Fuel Sensor / Separator

Upstream fuel companion — causes SPN 157 and SPN 1323 downstream.

SPN 4334 FMI 18

Upstream SCR companion — causes SPN 3361 and SPN 4364 downstream.

SPN 168 FMI 3 — Battery / Charging System Circuit

Supply voltage high — check before any FMI 2/9 sensor companion codes.

Frequently Asked Questions

What are companion fault codes?

Codes that share a root cause and set together. Fixing the upstream fault clears downstream companions without separate repairs.

What order should I diagnose fault codes?

Power supply (FMI 3/4) first, then fuel supply, then injection, then aftertreatment. DEF quality before SCR efficiency.

Why do new codes appear after I fix one?

The original root cause is still present — downstream systems now report faults that were masked. Keep tracing upstream.

How do I find the root cause code?

Use OEM code trees, group by timestamp, and identify the highest-upstream fault in the chain. Supply and quality codes precede component codes.

Will companion codes clear automatically?

Yes — after upstream repair and 1–2 drive cycles, downstream companions typically go inactive without separate component replacement.

More All Brands codes on this system

All All Brands fault codes

Guides that go deeper