Check Engine light

[Craig_CD9A]

Hi all,
After recently replacing my stuffed engine with a new one and running in the new clutch and flywheel gently for the first 1000km, I finally gave the new engine a bit of a squirt in first and second gear, whoa, much better! But.. After slowing down I noticed the check engine light come on and then disappear. Since then the check engine light has been coming on and staying on after driving for a minute or so. I hooked a buzzer up to the obd plug and I got two errors, the first being code 24 (vehicle speed sensor) and the second was code 31 (knock sensor). The new engine is gutless now since the check engine fault. The ABS hasn't been working since I swapped out the suspension a while back, would this be the cause of the vehicle speed sensor fault? And the knock sensor fault is caused by a faulty knock sensor, correct? I think I remember having read somewhere that knock won't light up the check engine light.

 

[blackvr]

It is likely the knock sensor is unserviceable, damaged , or the wiring damaged since you installed the engine . I assume you have checked that it is plugged in ?

Re the VSS... it is taken from the speedo unit , not from the ABS AFAIK for the GSR/CC Lancer . Is the speedo working ? If so, I wonder if some one has done the speed limiter mod like the do in the VR4 ie removed a screw from the back of the speedo/instrument binnacle. Otherwise, better start checking continuity from the instrument binnacle to ECU , and a labscope to check signal .

Cheers Mike

 

[Craig_CD9A]

Yeah the wiring and plug for the knock sensor are fine, I'll try swapping to my old knock sensor tomorrow and see how that goes. Ah yes, the screw has been removed for the speed limiter sometime in the cars past, is this the cause of the vss fault?

 

[blackvr]

Yeah the wiring and plug for the knock sensor are fine, I'll try swapping to my old knock sensor tomorrow and see how that goes. Ah yes, the screw has been removed for the speed limiter sometime in the cars past, is this the cause of the vss fault?

That will create the error code for sure. I've fitted/tuned many ECM tuning chips for VR4/GSR/EVO and remember being stumped as to why the engine rev limiter was coming on at 4500 rpm in a VR4 earlier this year. Quickly worked out that the Launch control routine is activated at 4500 rpm.... As its operation is controlled by the VSS, I checked the data . MMM , no speed signal. I pulled the dash, and some one at some stage had removed the screw to beat the speed limiter. I put it back in, so we could use the Launch control routine, and ECM chips remove the speed limiter anyway..

With the knock sensor, I can view the activity on the ECM datalogging. Even with a properly working sensor, you would be very surprised at how active they are, especially when its obvious there is no knock happening !! Its pretty common with built motors and big exhausts. Maybe call me if you need a bit of help in sorting the knock sensor sensitivity out ?? Cheers Mike mob 0417 083 682.

 

[Craig_CD9A]

Thanks for the informative post Mike
I'll see how I go with my other knock sensor tonight, it was operating fine on the old engine, so I am hoping that cures my current issues.

 

[Craig_CD9A]

Yup CEL sorted with chucking in my other knock sensor I think I might shorten (cut) my 27mm spanner if I'm going to remove/install one of those again!

 

[gsr093]

Yup CEL sorted with chucking in my other knock sensor I think I might shorten (cut) my 27mm spanner if I'm going to remove/install one of those again!

I've had the same issue for the past few months.

Anyone got a spare knock sensor they want to sell?

 

[Craig_CD9A]

I've had the same issue for the past few months.

Anyone got a spare knock sensor they want to sell?

Have you checked the diagnostic codes to make sure that the fault is indeed the knock sensor?

 

[gsr093]

Have you checked the diagnostic codes to make sure that the fault is indeed the knock sensor?

Yep. Its the knock sensor

 

[Richard]

How did you check for the codes? is there a chart of them all someplace? just interested to know and feel this would make this post more usefull...

 

[Craig_CD9A]

Best way is with a data logger plugged into your OBDI port. Another way is with a 12 v buzzer. See this link: http://www.vfaq.com/mods/wayback/BradBauer/electrical/code.html

 

[evo-gsr]

What ecu does your car have to enable you to use the data logger ??
E1,2or 3..?
Is it chipped or factory??
Can you give us the numbers on the lid of it please?

 

[Craig_CD9A]

I used a 12 v buzzer I got from Jaycar to get the diagnostic codes, I haven't hooked up a datalogger to my ODBI port. Wont a palm datalogger work with Evo 1-3 ? I know Evoscan won't work with Evo 1-3, but ECMLink chipped ecus can be logged and DTC's pulled with the supplied software.

 

[evo-gsr]

The palm logger apparently only works with certain ecu's - hence my above questions...Unsure if it works on E1-3 or chipped Ecu's Im yet to attempt that!!
I have been told that the palm works with GSR Ecus which is useless to those of us with Evos....That's why I was interrogating you :lol:

Maybe someone else can shed some light on the questions raised??

 

[blackvr]

I've yet too suss out what the drama is with GSR's and Evo OBD1 datalogging. Cant get any sense out of Hamish with Evoscans lack of comms ( He says it "should" work), my SnapOn scan tool talks to it fine and display data... I regularly have issues connecting ECMLink thru the 12 pin OBD1 port. Even though the wires pin out fine with an ohm meter ( from ECU to 12 pin plug, it still wont work... The loom must connect somewhere internally with other wires that create issues ?? In the end, I gave up and hard wired into the loom by the ECU plug a Magna 12 pin OBD1 plug, and snip the original TX/RX comm wires off. Wallah... all is good and I can communicate fine. One day when the opportunity arises, i will pull apart the under dash loom and see what is going on !!

 

[4piknup]

I've yet too suss out what the drama is with GSR's and Evo OBD1 datalogging. Cant get any sense out of Hamish with Evoscans lack of comms ( He says it "should" work), my SnapOn scan tool talks to it fine and display data... I regularly have issues connecting ECMLink thru the 12 pin OBD1 port. Even though the wires pin out fine with an ohm meter ( from ECU to 12 pin plug, it still wont work... The loom must connect somewhere internally with other wires that create issues ?? In the end, I gave up and hard wired into the loom by the ECU plug a Magna 12 pin OBD1 plug, and snip the original TX/RX comm wires off. Wallah... all is good and I can communicate fine. One day when the opportunity arises, i will pull apart the under dash loom and see what is going on !!

Yea, i did that too. there was no OBD1 plug on the jummy to run my ecmlink. so i wired a magna one straight into the ecu and put it above the glovebox. tidy and out of the way. i never have had issues with ecmlink connectivity

 

[Richard]

Best way is with a data logger plugged into your OBDI port. Another way is with a 12 v buzzer. See this link: http://www.vfaq.com/mods/wayback/BradBauer/electrical/code.html

Thanks. that was what I was after.