Page 1 of 1

2004 DC5 K-Pro - Engine Check Light - ECU Fault

Posted: Fri Oct 16, 2009 3:21 am
by zani
Hi guys,


( I am currently running an oem ecu now as the kpro is just so un-drivable, unfortunately, i did not get time or have accessibility to get it data-logged, but by the sounds of it, daughter-board error most likely will be the diagnosis )

I've got a problem which has started to occur 8 months ago... as time went by this issue has gradually got so much worse. - Meaning it used to happen once a month and now it could happen every time i start the car.


It is very intermittent, one day it may happen once, the next maybe every time i start the car.


The problem:

- Ignition on, (whether the engine is running or not does not matter)

- After around 10 seconds of ignition on, the engine check light will appear and the car will go into safe mode. (if the error occurs, the engine check light will come on after the same waiting time each time the ignition is turned on)

- Some times when the car is idling, it will rev up to 2000 rpm by itself and then either stay there or go back down to 1000.

- If the engine check light does not come on, it will Not appear through out the entire drive whether it be 10 min or 2 hours.

- Resetting the ecu, will normally get you 2 to 3 engine on/off sessions before the engine check light makes an appearance.

- On some occasions I am driving along with the engine check light on as the error has happened... from no actions of my own the engine check light will then disappear for 5 or so seconds then come back - I can now turn the ignition off then on again and have no error for the remaining time of that journey!



What do you think? It is something that can be fixed or has the ecu been converted to kpro in a non professional way causing these problems?

I fear that if i get the ecu sent away to be checked and not put in a DC5, as it will be reset from unplugging it - it will come up as absolutely fine?

Thank you for spending the time reading this post any comments appreciated!

Regards
Mark

Posted: Fri Oct 16, 2009 9:46 am
by Spunkster
Impossible to diagnose without an error code.

Posted: Fri Nov 13, 2009 1:39 am
by zani
Update:

2 Problems now resolved... I have had another ecu socketed to take my original kpro...

I had a pin resolded on my kpro was was nearly going to break away.

Also my oem ecu was socketed in a bad way, you could say cowboy style.

Car now runs great!

Posted: Tue Dec 01, 2009 10:09 am
by VT-Doo
Are you even connecting a laptop to the ecu to see what it's doing?
What's the error code?

Sounds to me like you have an O2 error.

:roll:

Posted: Tue Dec 01, 2009 11:16 am
by zani
Did you read my above post?

I had sent my ecu away for diagnostics... The problem was with my oem ecu and a connector on my kpro.

Nothing was adjusted on my kpro, only a pin connector re soldered.

Like I said, the car now runs great