RWD_cossie_wil

iTrader: (9)

Does anyone know how to reset a small turbo ECU? Keep getting a 511 internal ROM failure code. It happened before and my mate cleared it using his snap-on scanner, but this time it won't reset and just aborts as soon as you press clear faults ... Doing my head in now .

It has happened both times the battery has gone flat, tried disconnecting the ECU for 24hrs but still won't clear . Tried it with and without the chip module as well, fuck all

RWD_cossie_wil

iTrader: (9)

Billabong

From what I can gather, the error relates to:

'511 O Read Only Memory (ROM) test failure'

Doesn't relate directly to Cossie EEC-IV ecu, but would strongly expect the error codes to be std on any Ford EECIV variants.

If you're still stuck Will, I can type up the reset procedure from the Workshop Manual.

RWD_cossie_wil

iTrader: (9)

Mate that would be fucking legendry

Billabong

Here you go Will, found it on here (save my fingers, lol)

https://passionford.com/forum/ford-escort-rs-cosworth/206472-escort-cosworth-over-fueling-problems.html

See Gav's post.

Fuelling has to be re-learnt following this, which suggests a full reset - BUT not 100% sure if this IS the full reset procedure, or just for the KAM, as I (very vaguely, so probably thinking of something else) remember Stu put up a slightly different procedure at some point. I'm confusing myself now so probably worth a quick call tomorrow...

RWD_cossie_wil

iTrader: (9)

Stu dosn't know, was my first port of call

RWD_cossie_wil

iTrader: (9)

Doh, is for a P8 not EEC IV thanks anyway though

Billabong

Just checked the manual Will as thought maybe I was confusing P8 (which myself and Gavin have) with EECIV, but there's nothing 'extra' in the EECIV section of my manuals.

Maybe there was a slightly different procedure for EECIV which is what I was 'vaguely remembering' in my post above, as thinking about it the keep alive memory on P8 only holds whilst there's power to ECU - don't know if EECIV is the same with regards to 'saving' errors?

RWD_cossie_wil

iTrader: (9)

Stu said try disconnecting it for 24hrs, but it has made no difference. It might be worth a go anyway though, cheers

Is odd, the fault code would clear with the snap on scanner before, but won't now?

Billabong

Yep, does seem odd.

Have to say though, whilst error codes can sometimes be vauge at best, that one does sound ominous...

Good luck with it Will.

Turbosystems

iTrader: (5)

the eec4 does suffer with pmt

RWD_cossie_wil

iTrader: (9)

Thing is Tony, had the same problem before when the battry went flat , so mate came round with snap-on scanner and cleared it, but now even though its the same fault code etc, the machine won't clear it just goes "Aborting" as soon as you press Y to clear the codes .. Any ideas?

Turbosystems

iTrader: (5)

it has pmt

RWD_cossie_wil

iTrader: (9)

cheers for that helpful...

Billabong

Pre-Mapping Tension?

RWD_cossie_wil

iTrader: (9)

Probably mostly trashed

Turbosystems

iTrader: (5)

does your car have a run fault if it runs fine stop messing
eec4 often has stored fault codes that won't clear but the car runs fine others run like poo and have no errors recorded.
there were rumours that microsoft helped develop the eec4 lol
the eec4 issues and moods were cured by the development of the eec5
the most common code we see is automatic transmissin not in park and egr valve the esc cossie doesn't have either of these
like I said your ecu has pmt are you married if so asking your eec4 what is wrong is like asking your wife whats wrong when she has pmt

RWD_cossie_wil

iTrader: (9)

won't start, no spark on any cylinder. Exactly what happened before when it wouldn't start after the batt went flat. Not just "messing" , car has been fully rebuilt and has been running ok, but batt gone flat again in mates workshop now has same fault code. Won't clear with or without chip module in. Everything else is ok, the snap-on scanner does a full communication test, press throttle down etc, passes all that fine. Just refuses to clear the fault code.

Yeah, Stu told me about the EGR valve issues etc, not showing up at the moment though.

Turbosystems

iTrader: (5)

have you checked you haven't blown a fuse the eec4 has two power supplies

RWD_cossie_wil

iTrader: (9)

might be worth a check, which fuses are they? In the main box or on the loom?

Turbosystems

iTrader: (5)

they are in the main box ,kat fuse fuse 3 ? i think

RWD_cossie_wil

iTrader: (9)

Cheers, will have a look next time i'm home

pa_sjo

Is it chipped? If so, the module might not be seated properly in the back of the ECU.

Dave Henshall

the eeciv reset procedure is simple, just unplug it for 10 mins or disconnect the battery.

then reconnect, let it idle for 2 mins, then hold it at fast idle for 2 mins , then drive it for a few miles and it will re learn its idle and drive values.

RWD_cossie_wil

iTrader: (9)

All of which would be great, if the fucking thing actually started in the first place

Getting no spark at all, so it just turns over and over slowly filling with fuel .... Need to clear the fault codes, it worked last time but won't clear now for some reason?

Robski

Have you tried sending a pm to sailorbob from this forum? He was pretty clued up on the eec4 if i remember correctly,worth a try anyway.

RWD_cossie_wil

iTrader: (9)

Ahh, good plan

Jim Galbally

also yuo have to consider the possibility that the fault code is genuine and there is indeed a fault with the ECU itself as it's being reported

RWD_cossie_wil

iTrader: (9)

It is a possibility. but as it was exactly the same before, and the codes cleared, I recon it is not a genuine fault. I might try and get hold of a small turbo ecu and see if I can get it running.