Just brought the car a month ago. Replaced the ignition coil packs, plug leads and spark plugs as engine originally lacked power and I could see that the plug leads were breaking down as I could see the leads arcing at night. Also replaced exhaust downpipe gaskets as they were blowing. Once I fixed these problems it highlighted a problem with the engine ECU. Replaced engine ECU due to fault that was causing multiple misfires and lambda readings to go to a static level some time after startup. Engine is now running fine but dashboard is now displaying the hill descent control (HDC) and the traction control (TC) lights immediately after startup. According to the workshop manual this equates to one of the following faults:-
Sticking throttle pot.
Loss of signal.
Data corruption.
Took car for 10 mile test run and engine run fine and no engine fault codes came up when I plugged in the Hawkeye tester.
Connected an oscilloscope to pin 6 (grey wire with purple stripe) of connector C0203 in the engine bay (grey connector near the fuse box and brake servo) and a PWM signal switching between 0 and 12V was being displayed and the mark - space ratio changed when the throttle position was altered.
I have checked that all of the brake lights work correctly.
Could the engine ECU be incorrectly programmed so that the SLABs ECU does not recognise the signal?
Any suggestions as to what could be causing this fault?
Sticking throttle pot.
Loss of signal.
Data corruption.
Took car for 10 mile test run and engine run fine and no engine fault codes came up when I plugged in the Hawkeye tester.
Connected an oscilloscope to pin 6 (grey wire with purple stripe) of connector C0203 in the engine bay (grey connector near the fuse box and brake servo) and a PWM signal switching between 0 and 12V was being displayed and the mark - space ratio changed when the throttle position was altered.
I have checked that all of the brake lights work correctly.
Could the engine ECU be incorrectly programmed so that the SLABs ECU does not recognise the signal?
Any suggestions as to what could be causing this fault?
Last edited: