News:

New Users: Send [email protected] an email with your account name. I've turned off auto-approve to reduce the 100 new spam accounts a day. Thanks, -Jason

Main Menu

Audi RS2 with 7A flywheel trigger error

Started by billman, October 01, 2011, 02:27:26 PM

Previous topic - Next topic

billman

#15
the crankshaft plate looks like this





GintsK

This will give imprecise advance. Especially in dynamics. Try to 60-2 from 1.8T, Vr6 or similar VAG engine. It might fit in same place.

billman

sounds like an engine out job......maybe not yet....

so, what can cause Less Pr. Trigger error now? Distance to the Pin, it cant be. This is right. Can it be the engine speed sensor also?

GintsK

Most effective way here would be check all signals with oscilloscope.

billman

Unfortunately I dont have any....nor know how to use it.

About the diesel trigger wheel I was thinking if it is possible to use it instead of the flywheel pin signal.why would it give imprecise advance? It has 4 points and the original just one.

billman

Can someone please explain me something:

The engine timing works as follow: VEMS sees the crankshaft pin through the G4 sensor and tha hall windows so that it knows when the 1 piston is on top. After that though the G28 sensor it knows/calculates the engine RPM and crankshaft angle correct??

Till now I just concentrated to the flywheel pin but maybe the problem is on the other sensor that reds the 135 tooth.

billman

any ideas? Is it the Sensor G4 sensor with the Pin or the G28 that reads the 135 tooth?

http://vems.hu/vemstune/sharingcenter/reports.php?cmd=view&key=dZJ1jf

billman

Grinded the bracket for the G28 sensor that reads the 135 tooth wheel for about 0.5mm  and it seems to have cured the problem.

http://vems.hu/vemstune/sharingcenter/reports.php?cmd=view&key=gU8YOo


billman

A couple of days ago i washed the car engine. I run fine around town.

Today i went for a run and had all the time misfires like run at many different RPM points. After opening the hood i saw water boiling there where the pipes are.

this is how the log looks like. Seems like a trigger error but no error is recorded.

http://vems.hu/vemstune/sharingcenter/reports.php?cmd=view&key=aFagrB