Urgent Loan Of Auto Gts4 Ecu For Five Min. In Melb.

[TurboX]

Can someone in Melb loan me their HR 32 RB20DET Automatic ECU so I can try on the spot to see if mine is faulty?

Get error code 34 - Knock sensor - but have replaced them and checked continuity from new sensors to ECU connector pins all OK. The voltage on the pins is also correct as per the service manual.

So the only thing left to do is just swap the ECU and see if another one says error 34 as well.

Tune on ROM probably does not matter as I think it will show error just trying to start it anyway.

But if you have a chiped ROM anyway we could just swap mine in for the test if you agree, but wont matter if not as I think just trying to start will do the job.

I can drive the GTS4 if I dont put it into boost much as the computer seems to dump the boost and shut the revs down when gets near 6 PSI.

HELP! This is driving me CRAZY!!

Anyone with any other suggestions please post here now! - THANKS!

[paulr33]

unplug the knock sensors, see if anything changes

[blind_elk]

I've still got my original, but it's for a manual. Will that make any difference in terms of getting the error?

Have you reset the ECU to clear any residual errors (they are persistant for something like 50 "start" cycles).

[TurboX]

Thanks Greg, manual may not make any diff as I prob dont need to drive it, just start it and see if the error comes up.

It's strange as the other day I went for a test with Glenn and we started it about five times and Newkleers LCD Consult box said that it was <0> since error read each time even though not cleared for those five times.

You clear it and it comes straight back but does not increment as it should.

Have solved the cutting out problem by datalogging the problem on the road and exporting to excel graphs and found that at the point of dying the revs hit 3000 and the timing skyrockets to 60' BTDC.

This was with ECU ROM from SA Tuner mod by Dr Drift.

But then replaced with latest ROM from Dr Drift just before engine bearings blew from no oil pressure because of screws coming out in back of oil pump.

Latest ROM has solved the cutting out problem and datalogged a clean run to 7000 RPM all OK.

The reason I had swaped ROMs was the car was running like a dog for some reason which I eventually traced to the ECU Daughter PCB positioning in the ECU case.

Still has the error 34 showing so would like to try your ECU sometime soon.

Six years of trouble free punishing it has sure caught up to me over the last four years!!

[NewKleer]

the start count is the number of times engine has started since it last saw the code. 0 means its a current issue.

start count isnt the number of times the ecu has seen the code

[TurboX]

Thanks for clarifying that Peter, I was wondering if your box was faulty but KNEW that could not be the case.

This issue of the ECU Error 34 is frustrating the hell out of me.

Do you know of the implications of this fault effecting Timing etc.?

I am assuming it will switch to a different map to retard in case of overboost/detonation condition with no knock sensor working.

I want to get the car dynoed but can't till I sort this error out.

[NewKleer]

if u can post a datalog of driving around (with a bit of full throttle/load) that might show a bit.

basically youd be looking as to whether ignition timing is retarded more than it should be (i think this is the standard anti-knock protection?)

i also have code 34 on my sr20det, which seems to be common. u can trick the ECU into thinking its ok with some resistor mod i think