Your fleet running reports

User avatar
MikeHunt
Posts: 1164
Joined: Fri Apr 13, 2018 11:34 am

Re: Your fleet running reports

Post by MikeHunt »

Matty wrote: Mon Sep 28, 2026 10:37 am
MikeHunt wrote: Sat Sep 26, 2026 3:57 pm Had the Z4 mapped and the OPF removed. 431bhp and 633Nm, which feels about right for what I wanted mechanical sympathy to the gearbox and clutch rather than chasing numbers.
Is that up from 360ish? It's a decent bump. Out of interest, did you feel it was lacking before, or is this just the fact the gains Vs cost means its rude not to?
Officially 335bhp, although I suspect it was north of 350. It certainly wasn’t lacking in power and, if anything, one of the reasons for selling the V8 was having too much of it, you could barely accelerate for more than a few seconds without getting into licence losing territory.

I could probably have achieved 80% of what I wanted just by removing the OPF, which gave me the noise and some of the gains, but now that its finally possible to tune a BMW without sending the ECU off to Finland, I thought, why not?
User avatar
Alex88
Posts: 506
Joined: Thu Apr 12, 2018 8:36 pm

Re: Your fleet running reports

Post by Alex88 »

I knew the Mustang wasn't right following its 'repair' with Modurstang. I told them it had a rough start-up, intermittent bad idle, stunk of fumes. Felt like it was misfiring.

Their position was that everything was fine. They drove it extensively and concluded it was tip-top.

I've just got back from having the cats inspected (they appear to be fine). Plugged my OBD2 Scanner in and got the codes below.

Fuck knows what this points to, but I'm guessing it supports my theory that the car wasn't healthy and that they hadn't correctly diagnosed and repaired it...

----------------------------
P0420 [0x0420]
Catalytic converter system, bank 1 - efficiency below threshold
Catalyst System Efficiency Below Threshold (Bank 1)
Status: Confirmed
----------------------------
P0430 [0x0430]
Catalytic converter system, bank 2 - efficiency below threshold
Catalyst System Efficiency Below Threshold (Bank 2)
Status: Confirmed
----------------------------
P0606 [0x0606]
Engine control module (ECM)/powertrain control module (PCM) - processor fault
PCM Processor Fault
Status: Confirmed
----------------------------
P0316 [0x0316]
Misfire detected during start-up - first 1000 revolutions
Status: Pending fault present, Pending fault present during this driving cycle, Test conditions are met, Test is inhibited by other DTC, Test has not been completed, Validated and stored in non volatile memory, Validated fault present at time of request, Validated fault has been present during this drive cycle
----------------------------
P1000 [0x1000]
OBD Systems Readiness Test Not Complete
Check of all OBDII Systems Not Complete Ford Manufacturer Codes; OBD-II Monitor Testing Incomplete
Status: Pending fault present, Pending fault present during this driving cycle, Test conditions are met, Test is inhibited by other DTC, Test has not been completed, Validated and stored in non volatile memory, Validated fault present at time of request, Validated fault has been present during this drive cycle
============================
Engine control unitEngine control unit
DTCs: 5
----------------------------
P0316 [0x0316]
Misfire detected during start-up - first 1000 revolutions
Status: Pending fault present, Pending fault present during this driving cycle, Test conditions are met, Test is inhibited by other DTC, Test has not been completed, Validated and stored in non volatile memory, Validated fault present at time of request, Validated fault has been present during this drive cycle
----------------------------
P0420 [0x0420]
Catalytic converter system, bank 1 - efficiency below threshold
Catalyst System Efficiency Below Threshold (Bank 1)
Status: Pending fault present, Pending fault present during this driving cycle, Test conditions are met, Test is inhibited by other DTC, Test has not been completed, Validated and stored in non volatile memory, Validated fault present at time of request, Validated fault has been present during this drive cycle
----------------------------
P0430 [0x0430]
Catalytic converter system, bank 2 - efficiency below threshold
Catalyst System Efficiency Below Threshold (Bank 2)
Status: Pending fault present, Pending fault present during this driving cycle, Test conditions are met, Test is inhibited by other DTC, Test has not been completed, Validated and stored in non volatile memory, Validated fault present at time of request, Validated fault has been present during this drive cycle
----------------------------
P0606 [0x0606]
Engine control module (ECM)/powertrain control module (PCM) - processor fault
PCM Processor Fault
Status: Pending fault present, Pending fault present during this driving cycle, Test conditions are met, Test is inhibited by other DTC, Test has not been completed, Validated and stored in non volatile memory, Validated fault present at time of request, Validated fault has been present during this drive cycle
----------------------------
P1000 [0x1000]
OBD Systems Readiness Test Not Complete
Check of all OBDII Systems Not Complete Ford Manufacturer Codes; OBD-II Monitor Testing Incomplete
Status: Pending fault present, Pending fault present during this driving cycle, Test conditions are met, Test is inhibited by other DTC, Test has not been completed, Validated and stored in non volatile memory, Validated fault present at time of request, Validated fault has been present during this drive cycle
============================
ABS/ESPABS/ESP
DTCs: 2
----------------------------
U1900 [0xD900] Archive (inactive)
CAN Communication Bus Fault; CAN COMMUNICATION BUS FAULT - RECEIVE ERROR
Status: Validated and stored in non volatile memory
----------------------------
U2011 [0xE011] Archive (inactive)
Module Transmitted Invalid Data (Non SCP)
Module Transmitted Invalid Data (Non SCP)
Status: Validated and stored in non volatile memory
============================
DashboardDashboard
DTCs: 3
----------------------------
B1318 [0x9318] Archive (inactive)
Battery Voltage Low; BATTERY VOLTAGE LOW
Status: Validated and stored in non volatile memory
----------------------------
B1353 [0x9353] Archive (inactive)
Ignition Key-In Circuit Open
Status: Validated and stored in non volatile memory
----------------------------
U1900 [0xD900] Archive (inactive)
CAN Communication Bus Fault; CAN COMMUNICATION BUS FAULT - RECEIVE ERROR
Status: Validated and stored in non volatile memory
User avatar
Beany
Posts: 8645
Joined: Wed Apr 11, 2018 5:27 pm

Re: Your fleet running reports

Post by Beany »

Clear them all, then take it for a 30 mile run, then scan again.

I'm assuming you've not cleared them yet, but some of those could be from, or tangentially related to, the work that was done etc.

Low voltage will throw all sorts of codes at random, too...
User avatar
Sundayjumper
Posts: 8417
Joined: Wed Apr 11, 2018 4:04 pm

Re: Your fleet running reports

Post by Sundayjumper »

Agreed. Clear them and see which ones come back.

All the “inactive” ones can be ignored. The ECU ones are curious. I’m not really sure what they mean. Kinda sounds like they’re nothing and are just flagging that something else has prevented the ECU doing a self-check.
User avatar
Beany
Posts: 8645
Joined: Wed Apr 11, 2018 5:27 pm

Re: Your fleet running reports

Post by Beany »

Speaking of low voltage, no sign of my battery yet.

If I'd known Tayna/DX Delivery were going to fuck the delivery up (it arrived in their warehouse in Manchester last night, and never got put on a van today), I'd have ordered it from ECP and bribed my neighbour to help collect it instead.
User avatar
Alex88
Posts: 506
Joined: Thu Apr 12, 2018 8:36 pm

Re: Your fleet running reports

Post by Alex88 »

Thanks guys. When I collected the car from them, all codes had been cleared.

The EML came up on the journey home. My scanner said cat efficiency both sides.

A further check today revealed the additional codes, which make sense based on the symptoms on getting from it.

But I will clear them regardless and give the car a drive (tricky as it has no MOT).
User avatar
16vCento
Posts: 1281
Joined: Wed Apr 11, 2018 6:06 pm
Currently Driving: Golf GTE
Kuga ST Line X PHEV

Re: Your fleet running reports

Post by 16vCento »

Has it got high flow cats fitted? Might need lambda spacers if so.

P1000 just means it's not completed a full drive cycle to check for issues ignore that.
User avatar
Mito Man
Posts: 13194
Joined: Wed Apr 11, 2018 4:27 pm

Re: Your fleet running reports

Post by Mito Man »

There's a fault preventing it from correctly going through all the other tests. Presumably its the P0606 control module that's screwing everything.
Is the battery in good condition?

Could all stem from the ECU though. If that's causing a misfire then the cats will be below normal efficiency.
How about not having a sig at all?
User avatar
Alex88
Posts: 506
Joined: Thu Apr 12, 2018 8:36 pm

Re: Your fleet running reports

Post by Alex88 »

Yeah, the battery's fine. It does have high flow cats, too.

I can't really join the dots together on this. Feels like it could be anything.
User avatar
16vCento
Posts: 1281
Joined: Wed Apr 11, 2018 6:06 pm
Currently Driving: Golf GTE
Kuga ST Line X PHEV

Re: Your fleet running reports

Post by 16vCento »

P0606 can be thrown if the ECM has low voltage, wouldn't read too much into that until battery confirmed as good and charged.

Also can be logged if there's voltage drops or spikes, definitely worth checking alternator output.
User avatar
Sundayjumper
Posts: 8417
Joined: Wed Apr 11, 2018 4:04 pm

Re: Your fleet running reports

Post by Sundayjumper »

Or even earthing points. Bad battery / engine earths can cause sluggish starting & voltage drops even if the battery itself is healthy.
Shlergen
Posts: 373
Joined: Mon Apr 30, 2018 8:22 pm

Re: Your fleet running reports

Post by Shlergen »

Ai says:
The root cause of these codes breaks down into three distinct issues: exhaust flow changes, an underlying misfire/electrical problem, and historic low-voltage artifacts.
​1. P0420 & P0430 (Directly Related to the Exhaust)
​What it means: Catalyst System Efficiency Below Threshold on both Bank 1 and Bank 2.
​Why it happened: High-flow cats (or cat-delete/off-road pipes) allow exhaust gas to pass through much faster and with less scrubbing than factory catalytic converters. The downstream (rear) O_2 sensors monitor the delta between pre- and post-cat exhaust; because the downstream sensors are seeing fluctuating, active readings similar to the upstream sensors, the PCM flags the converters as degraded or missing.
​Fix:
​If the car has not been custom tuned for the exhaust, this is standard behavior. A tuner typically adjusts the rear O_2 monitor parameters, or you can fit angled O_2 sensor spacers (foulers) on the downstream sensors to pull them slightly out of the direct exhaust stream.
​Check for physical exhaust leaks near the header collectors or O_2 bungs, as ambient air pulled in by the Venturi effect will also trigger both codes.
​2. P0316 (Misfire at Startup)
​What it means: Engine misfire detected within the first 1,000 engine revolutions upon startup.
​Why it matters: Raw, unburned fuel entering the exhaust during cold start will degrade or overheat catalytic converters and trigger efficiency codes.
​Fix:
​Pull specific cylinder misfire counts with a live scanner (look for Mode 06 or individual cylinder misfire P0300–P0308 pending codes).
​Inspect the spark plugs and ignition coil boots on the affected cylinders. Plugs fouled with fuel, incorrect gaps, or weak coil boots breaking down under cold-start enrichment are the most common culprits.
​Check for intake/vacuum leaks around the manifold or PCV lines that cause a lean stumble on cold idle.
​3. P0606, B1318, & Inactive U-Codes (PCM Fault & Voltage Drop)
​What it means: P0606 indicates a PCM internal processor check failure, while B1318 flags low battery voltage, and U1900/U2011 are CAN communication dropouts.
​Why it happened: On Ford PCMs, P0606 is frequently triggered by low system voltage during cranking, bad engine/chassis ground straps, or an incomplete flash if the car was recently tuned. A battery dipping below ~9.6V while cranking causes the microprocessors in the PCM and dash cluster to reset asynchronously, generating both P0606 and CAN communication errors (U1900).
​Fix:
​Test battery health, cold cranking amps (CCA), and state of charge. Clean the battery terminals.
​Ensure the heavy chassis-to-engine ground straps were properly re-secured if they were loosened or moved during the exhaust installation.
​If a handheld tuner (SCT, nGauge, etc.) was plugged in or flashed recently, re-flash the stock tune and reload to verify the file was not corrupted during writing.
​4. P1000 (System Status)
​What it means: OBD-II monitor testing incomplete.
​Why it is there: This is an informational flag indicating that drive cycles have not completed (usually because codes were recently cleared, battery disconnected, or monitor tests are inhibited by P0420/P0430). It clears itself once all readiness tests run and pass.
​Recommended Next Steps
​Address battery voltage and grounds first: Check resting voltage (should be ≥12.6V) and cranking voltage (must stay above 10V). Clean terminals and inspect engine block ground connections around the headers.
​Clear the codes and verify if P0606 returns immediately. If it does not return after a clean startup on a healthy battery, it was a transient low-voltage artifact.
​Trace the cold-start misfire (P0316) using live cylinder data before prolonged driving.
​Tune or space rear O_2 sensors once the ignition and electrical systems are verified clean.
User avatar
Sundayjumper
Posts: 8417
Joined: Wed Apr 11, 2018 4:04 pm

Re: Your fleet running reports

Post by Sundayjumper »

Well, that's interesting:
Shlergen wrote: Tue Sep 29, 2026 7:21 am On Ford PCMs, P0606 is frequently triggered by low system voltage during cranking, bad engine/chassis ground straps, or an incomplete flash if the car was recently tuned.
Ground straps is exactly what I posted just before this, and in the meantime I was pondering Alex's previous post:
Alex88 wrote: Wed Aug 19, 2026 3:41 pm Also, when it went back in the second time, I mentioned the cats and aftermarket air filter and they said they could adjust the car's map to suit the basic mods. Not for power, but to optimise it. On collection they said they'd made a few adjustments to the fuel trims. That now makes me wonder why that adjustment was necessary?
Do we know exactly what they did to the ECU ? This isn't an old carburettor engine where you just tweak a screw.

How feasible is it to swap in a different, known good ECU ?
User avatar
DeskJockey
Posts: 6525
Joined: Thu Apr 12, 2018 8:58 am

Re: Your fleet running reports

Post by DeskJockey »

Zoe failed the MOT on a nearside front ball joint being excessively worn. Advisories on both rear tyres.

First is annoying, second is reasonable as they've done nearly 40k miles.

Booking it in with the mechanic, and ordering new tyres.
---
Driving a Galaxy far far away
User avatar
Matty
Posts: 3474
Joined: Wed Apr 11, 2018 3:50 pm
Currently Driving: Up! GTi, Evora Sport 410

Re: Your fleet running reports

Post by Matty »

Little Honda continues to impress me, and everyone else. Biggest comments from others (other than the interior) is the overall ride quality for a small car, along with how quiet and refined it is for it's size....guess it explains why it weighs 1.6tons. Stuffed full of sound deadening.

Got the Evora out for the first time in about 4 weeks, and it's just an incredible car......yet, the seats are *still* are my biggest issue, maybe I still yearn for the old Recaros. Insane how much of a downgrade these Sparco's are. I need to be about 3-4" lower.

I've also got an issue I've been chatting to Mik about with creaky doors. I think they're moving around slightly - driving down the M54 (for which I think they used railway sleepers as a base) they sound like an arthritic mouse at a rave. I thought Gummi Pfledge would fix it, but apparently not, as it has that rubber-on-plastic kinda noise. Maybe I didn't lather it on enough....another suggestion was fairy liquid as a test.
Post Reply