Resources · Workshop knowledge base

ECU Solutions

Documented fault patterns from the Fiitech workshop floor, what we see, what actually causes it, and the procedure that fixes it. Written for technicians who already have a scan tool and a multimeter and want the next step.

12
Procedures
12
ECU families
12
Verified
  • P0299Standard

    Turbocharger underboost. VAG EDC17 diesel

    Engine management · Bosch EDC17C46 / EDC17CP14

    VW / Audi / Skoda / Seat 1.6 & 2.0 TDI (2008–2015)

    Symptoms

    • Loss of power above 2,500 rpm under load.
    • "EPC" warning light intermittent. Full power returns after restart.
    • P0299 stored, sometimes paired with P0234.

    Root causes. Ranked by frequency

    1. 01Vacuum hose to the turbo actuator perished. Most common.
    2. 02Turbo actuator (VNT vanes) seized from carbon build-up.
    3. 03MAP/boost-pressure sensor (G31) drifted out of spec.
    4. 04EGR cooler internal split causing boost loss into the intake.

    Procedure

    1. 01Scan, capture freeze-frame for the P0299 instance. Note rpm and load.
    2. 02Live data: command MAP pressure vs measured MAP. Deviation > 200 mbar at full load = a real boost shortfall, not a sensor fault.
    3. 03Pressure-test the intake system at 0.8 bar. Listen and look for leaks.
    4. 04Inspect the actuator vacuum line. Replace if cracked, brittle, or showing oil contamination.
    5. 05Actuate the turbo vanes with the scan tool (output test). Should sweep smoothly. Sticky sweep = carbon.
    6. 06If carbon: walnut-blast the actuator linkage, refit, re-test.
    7. 07If sensor: substitute a known-good G31 and re-test. Replace if confirmed.

    Tools required

    • VCDS / ODIS (or any EDC17-capable scan tool with output tests)
    • Hand pressure tester for the intake tract
    • Vacuum hand pump for actuator test
    2.5 hours typical · Last verified 2026-04 · Y.H.Workshop note
  • P0087Advanced

    Fuel rail pressure below threshold. Bosch CRD diesel

    Fuel system · Bosch EDC16 / EDC17 common-rail

    Toyota Hilux 2.5/3.0 D-4D, Ford Ranger 2.5 TDCi, many CRD diesels

    Symptoms

    • Loss of power, sometimes intermittent stalling under load.
    • Hard hot-start.
    • P0087 stored, often with P0093 (large fuel leak).

    Root causes. Ranked by frequency

    1. 01Worn injector return flow (back-leak too high). Most common at 200,000+ km.
    2. 02High-pressure pump worn. Second most common.
    3. 03Pressure regulator (DRV / MPROP) failure.
    4. 04Fuel filter clogged or wrong filter installed.

    Procedure

    1. 01Replace the fuel filter. If recent, skip but inspect.
    2. 02Measure injector back-leak at cranking with the manufacturer's return-flow kit. Anything outside ±50% of average = bad injector.
    3. 03Live data: commanded vs actual rail pressure during a stall event.
    4. 04If commanded pressure is fine but actual is low: pump or regulator. Bench-test the regulator first (cheaper).
    5. 05If commanded pressure tracks actual but both are low: pump output insufficient. Pump replacement.
    6. 06After repair: prime the system, run for 15 minutes, re-check fuel trims and run a 30 km road test.

    Tools required

    • Common-rail injector back-leak measurement kit
    • High-pressure-rated fuel pressure gauge (1800 bar)
    • Scan tool with diesel-specific live data
    4 hours diagnosis + repair time per part · Last verified 2026-03 · I.M.Workshop note
  • P0420Standard

    Catalyst efficiency below threshold. Petrol vehicles

    Emissions · Universal. Any OBD-II petrol ECU

    Most petrol vehicles 1996+

    Symptoms

    • Check engine light steady.
    • No driveability symptoms. Vehicle runs normally.
    • Fails roadworthy emissions test.

    Root causes. Ranked by frequency

    1. 01Genuine catalyst failure. Typically after 200,000 km, after oil-burning episode, or after running rich for long.
    2. 02Failing downstream O2 sensor (B1S2) reporting incorrectly.
    3. 03Small exhaust leak between catalyst and downstream sensor introducing oxygen.
    4. 04Engine running rich for unrelated reasons (vacuum leak, dirty MAF). Catalyst is healthy but is being asked to do too much.

    Procedure

    1. 01Read O2 sensor live data: upstream should oscillate quickly (0.1–0.9V), downstream should be slow and steady around 0.6–0.7V.
    2. 02If downstream mirrors upstream: catalyst no longer storing/releasing oxygen. Replace catalyst.
    3. 03If downstream stays high or shows weird patterns: replace downstream sensor first, clear codes, drive 100 km, re-test.
    4. 04Check for exhaust leaks between catalyst and downstream sensor with a smoke machine or visual + soapy water.
    5. 05Confirm short and long-term fuel trims are within ±10% before condemning the catalyst.

    Tools required

    • Scan tool with O2 sensor graphing
    • Smoke machine (optional)
    1 hour diagnosis · Last verified 2026-02 · S.O.Workshop note
  • P0171Standard

    System too lean (Bank 1). Petrol vehicles

    Engine management · Universal

    Most petrol vehicles 1996+

    Symptoms

    • Check engine light.
    • Rough idle, occasional misfire.
    • Slightly elevated fuel consumption.

    Root causes. Ranked by frequency

    1. 01Vacuum leak. Intake gasket, PCV hose, brake booster hose.
    2. 02Mass airflow sensor (MAF) dirty or drifted low.
    3. 03Weak fuel pump or clogged fuel filter.
    4. 04Leaking fuel injector underdelivering on Bank 1.
    5. 05Exhaust leak upstream of the O2 sensor (false-lean reading).

    Procedure

    1. 01Live data fuel trims: STFT + LTFT > +15% at idle confirms a true lean condition.
    2. 02Smoke-test the intake from the throttle body backward. Visible smoke = vacuum leak.
    3. 03Compare MAF live reading (g/sec at idle) to known-good range for the engine. Most 2.0L petrols sit at 3–5 g/sec.
    4. 04Measure fuel pressure at idle, then snap-throttle. Pressure should hold or rise slightly; drop = pump or regulator.
    5. 05If all the above are clean, swap injectors between cylinders and see if the lean condition follows.

    Tools required

    • Smoke machine
    • Fuel pressure gauge
    1.5–3 hours depending on root cause · Last verified 2026-04 · S.O.Workshop note
  • IMMO-EDC17Specialist

    Immobiliser PIN extraction for replacement ECU

    Immobiliser / coding · Bosch EDC17 (all variants)

    VAG group (Golf, Polo, Passat, Octavia, A3 etc. 2008+)

    Symptoms

    • Replacement ECU installed; engine cranks but does not start.
    • Immobiliser warning on cluster.
    • Scan shows "key not learned" / "immobiliser not matched".

    Root causes. Ranked by frequency

    1. 01Replacement ECU has a virgin immo state and needs the chassis PIN + CS to pair with the cluster.
    2. 02Used ECU pulled from a different car. Needs full virginisation before pairing.

    Procedure

    1. 01Open the ECU and identify the bench-mode pinout (KESS V2 can do this OBD on most pre-2014; K-TAG bench on later units).
    2. 02Read the full flash + EEPROM. Back up both before any write.
    3. 03Use the appropriate PIN-extraction tool (e.g. VVDI2, Xhorse Mini Prog) on the EEPROM dump to extract the immobiliser data (PIN, CS, MAC).
    4. 04Write the chassis-correct immo data into the new ECU via K-TAG bench.
    5. 05Refit the ECU, perform "adapt component" via VCDS. Engine should start.
    6. 06Always document the PIN + CS in the customer file for future reference.

    Tools required

    • KESS V2 Master OR K-TAG Master
    • PIN extraction tool (VVDI2 / Xhorse Mini Prog)
    • VCDS or ODIS for adaptation step
    3–5 hours (heavy on bench setup) · Last verified 2026-05 · Y.H.Workshop note
  • EZS-DESYNCSpecialist

    EZS/EIS de-sync after dead battery. Mercedes ME9.7

    Immobiliser / coding · Mercedes ME9.7 / EZS (Electronic Ignition Switch)

    Mercedes W211 / W219 / W251 / R230 SL

    Symptoms

    • After a dead battery: key in, ignition turns, but engine doesn't start.
    • EZS module shows fault about "ME control unit not authorised".
    • Sometimes only one of the two keys works.

    Root causes. Ranked by frequency

    1. 01Rolling code between EZS and ME (engine ECU) lost sync due to extended low-voltage state.
    2. 02On some W211: SBC (brake module) faulted into safe mode and is holding the bus.

    Procedure

    1. 01Confirm battery voltage > 12.4V before any further work.
    2. 02Use SDConnect/Vediamo (or Xentry passthrough) to do "SCN coding" on the ME. Push current rolling code from EZS into ME.
    3. 03If that fails: read both EZS and ME EEPROMs on the bench, manually realign the rolling code.
    4. 04On W211 with SBC fault: clear SBC fault first, drive 50 metres, then re-attempt the sync. SBC often blocks the sync if active.
    5. 05After successful sync: replace the battery if it cannot hold > 12.6V at rest. Repeat fault otherwise.

    Tools required

    • Xentry / Vediamo (Mercedes diagnostic)
    • K-TAG with Mercedes adapters (for EEPROM access if SCN fails)
    2 hours typical, 6+ if EEPROM realignment required · Last verified 2026-01 · I.M.Workshop note
  • DPF-STUCKAdvanced

    DPF stuck in regen. PSA HDi (SID201/202)

    Emissions · Siemens SID 201 / SID 202

    Peugeot/Citroen 1.6 & 2.0 HDi (2007–2015)

    Symptoms

    • High idle, fan running at full speed, smell of fuel from exhaust.
    • Customer reports the car "trying to regenerate constantly".
    • P1448 / P1435 stored.

    Root causes. Ranked by frequency

    1. 01DPF differential pressure sensor drifted out of spec.
    2. 02EOLYS additive tank empty (vehicles fitted with FAP system specifically).
    3. 03DPF saturated beyond active regen capability. Needs forced regen + Eolys top-up.

    Procedure

    1. 01Scan: read DPF soot loading. > 45 g = forced regen is no longer safe, must remove DPF.
    2. 02< 45 g: top up Eolys to factory level, perform forced regen via scan tool, drive at motorway speed for 30 minutes.
    3. 03After forced regen: reset soot accumulation counter AND Eolys consumption counter.
    4. 04If DP sensor is suspect: substitute, clear codes, road-test 50 km.
    5. 05Document the regen completion in the customer file. Repeat customers usually = an upstream injector issue dumping fuel.

    Tools required

    • Lexia (PSA-specific) or compatible scan tool with forced regen
    • Eolys top-up fluid
    2 hours including the road test · Last verified 2026-03 · I.M.Workshop note
  • ADAPT-PCR21Standard

    Throttle body adaptation lost after replacement

    Sensor / actuator · Continental Simos PCR2.1

    VW Polo / Skoda Fabia / Seat Ibiza 1.0 / 1.2 TSI (2014+)

    Symptoms

    • After throttle body replacement: rough idle, sometimes stalls.
    • "EPC" warning intermittent.
    • P2100 / P2101 in some cases.

    Root causes. Ranked by frequency

    1. 01Throttle adaptation not performed after installation. The PCR2.1 needs an explicit adaptation procedure.

    Procedure

    1. 01Confirm battery voltage > 12.8V. Adaptation aborts below this.
    2. 02Cycle ignition: off > on (do NOT crank) > wait 30 seconds.
    3. 03Via scan tool with PCR2.1 support: run "Basic Settings" group 060 (throttle adaptation).
    4. 04Watch live data: throttle position moves to several stops. Procedure typically completes in 60 seconds.
    5. 05Crank engine, idle for 2 minutes, verify smooth idle and no faults.

    Tools required

    • VCDS or compatible scan tool with PCR2.1 basic settings access
    20 minutes · Last verified 2026-04 · S.O.Workshop note
  • SID-DEADBATTAdvanced

    Module wake failure after dead battery. Siemens SID 803/206

    ECU recovery · Siemens SID 803 / SID 206

    BMW / Mini 1.6D & 2.0D (N47 / N57 engines)

    Symptoms

    • Battery went dead, was jumped, now car will crank but not start.
    • Scan: "no comms with DDE" (the Siemens engine ECU).
    • No fault codes accessible.

    Root causes. Ranked by frequency

    1. 01Voltage dropped low enough during jump-start that the DDE's EEPROM half-wrote a state. Module is in a protected lock.
    2. 02CAS module also affected. Won't enable DME power.

    Procedure

    1. 01Replace or fully charge the battery to > 12.6V at rest first.
    2. 02Read the CAS module via bench mode (KESS / K-TAG depending on year).
    3. 03If CAS is corrupted: extract ISN from a known-good EEPROM dump, write back. Re-test comms.
    4. 04If DDE is the locked module: read EEPROM on the bench, restore from a backup of the same chassis (we keep templates for common N47/N57).
    5. 05After both modules recover: clear all adaptive values, do a 30 km drive cycle to relearn.

    Tools required

    • K-TAG with BMW adapters
    • Known-good EEPROM templates (workshop library)
    4–6 hours · Last verified 2026-02 · Y.H.Workshop note
  • P0011/P0014Standard

    VVT phase angle out of range. Hyundai/Kia Theta

    Engine management · Bosch ME17.9.x

    Hyundai/Kia 2.0 & 2.4L Theta II engines

    Symptoms

    • Loss of power at low rpm, knocking sound from valve cover area.
    • P0011 (Bank 1 intake) or P0014 (Bank 1 exhaust).
    • On cold start: faint rattle for 1–2 seconds.

    Root causes. Ranked by frequency

    1. 01OCV (oil control valve) screen blocked with sludge.
    2. 02CVVT actuator (phaser) worn. Clicking visible with rocker cover off, engine running.
    3. 03Low oil level or wrong oil viscosity (very common. Use 5W-30 or 5W-40, not 10W-40).
    4. 04Timing chain stretched (older units with > 200,000 km).

    Procedure

    1. 01Check oil level + condition. Drain a sample. Sludge in the sample = service the OCVs.
    2. 02Live data: command intake phase from 0° to 25° via scan tool output test. Slow or non-responsive = OCV or actuator.
    3. 03Remove OCV, inspect screen. Clean and refit if mildly contaminated, replace if heavily blocked.
    4. 04Re-test phase response. If still slow, condemn the actuator and replace.
    5. 05After repair: change oil + filter with correct grade. Verify codes don't return after 200 km.

    Tools required

    • Scan tool with VVT output tests
    • Standard hand tools
    2 hours (OCV) / 5 hours (actuator) · Last verified 2026-04 · S.O.Workshop note
  • ECU-WATERDMGSpecialist

    Water-damaged ECU recovery. Delphi DCM3.7

    ECU recovery · Delphi DCM3.7 / DCM3.5

    Ford / Mazda / Volvo 1.5D & 2.0D (TDCi family)

    Symptoms

    • After flooding: engine cranks but doesn't start.
    • Customer mentions car drove through deep water.
    • Scan: comms work intermittently or fail entirely.

    Root causes. Ranked by frequency

    1. 01Water ingress through the ECU connector seal. Copper traces corrode, board fails progressively.

    Procedure

    1. 01Remove ECU. Open immediately. Do not let it dry sealed (corrosion accelerates).
    2. 02Inspect board under microscope for visible green corrosion. Photograph for the customer file.
    3. 03Ultrasonic clean in isopropanol > 95% for 10 minutes. Dry at 60°C for 2 hours.
    4. 04Inspect again. If traces are eaten through, microsolder repair to bridge.
    5. 05Read flash + EEPROM on the bench. If readable: confirm checksum, write back. If not: source matching virgin ECU and clone.
    6. 06After board work: refit, attempt start. If no-start, expect to repeat. Water damage is rarely a one-pass fix.

    Tools required

    • JBC soldering station
    • Microscope
    • Ultrasonic cleaner
    • K-TAG bench for read/write
    6–10 hours typical · Last verified 2026-05 · Y.H.Workshop note
  • P2138Standard

    ETCS-i accelerator pedal sensor mismatch. Toyota 2GR-FE

    Sensor / actuator · Toyota 76-pin engine ECU (2GR application)

    Toyota Camry V6, Lexus ES350, Toyota Sienna (2007–2017)

    Symptoms

    • Engine drops to limp mode (no rpm above 2000).
    • P2138 stored. Accelerator pedal position sensors 1 & 2 correlation.
    • Sometimes triggered by aftermarket throttle controllers.

    Root causes. Ranked by frequency

    1. 01Faulty pedal assembly. Internal track wear.
    2. 02Aftermarket throttle controller introducing signal interference.
    3. 03Damaged pedal wiring loom (corrosion at the connector).

    Procedure

    1. 01Live data: APP1 + APP2 should track in a 2:1 ratio across full pedal travel. Either signal jumping = bad pedal or wiring.
    2. 02Disconnect any aftermarket throttle controller, clear codes, road test.
    3. 03Inspect the pedal connector for water or corrosion. Clean with contact cleaner.
    4. 04If signals still don't track: replace the pedal assembly (not user-serviceable).
    5. 05After repair: clear codes, idle for 30 seconds, road-test through full pedal range.

    Tools required

    • Scan tool with live pedal graphing
    1.5 hours · Last verified 2026-03 · S.O.Workshop note
Stuck on an ECU?

Bring it in or send a photo.

The procedures here are the ones we run regularly. For anything more involved. Bricked modules, water-damaged boards, locked immo. Bring the ECU to the workshop or message us photos and a scan dump. We diagnose ECUs daily.