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

trigger problem 60-2 VR

Started by tonci, April 23, 2010, 12:00:05 AM

Previous topic - Next topic

tonci

I have a trigger problem. The setup is 1.8t vw engine with original 60-2 trigger wheel and VR sensor. During idle rpm signal goes to 0 every 60-70 sec and than it goes back to normal. It usually resets warmup and lambda reading. I have tried different firmwares, configs and even vems boxes. I have connected new shielded cable from sensor to vems connector but it didn't help. Now I believe the problem is in vr sensor. Since the engine has trigger wheel on crank inside the block I can't bring sensor closer, so my only option is to try to replace the sensor. Do you guys know how can I recognize faulty VR sensor without oscilloscope? What else could be the problem?

here is pic from log



end here is vemslog

http://free-st.t-com.hr/cmuzic/vems/v3.3_n002144-2010.04.18-17.59.54.vemslog

mattias

Disable fuel injection (either go WOT, flood-clear, or pull injector fuse) and crank the engine while recording a trigger log. Check the Tools menu in VemsTune. Crank until you have 100 bytes or more, save the file and get back to us with a screenshot or the actual file.

tonci

Hi Matias

Here is a smaller log file but you can see a lot of errors inside. What do you think, what could be the problem? Faulty sensor? I do not get trigger errors in vemstune...



http://free-st.t-com.hr/cmuzic/vems/log1.vemslog

tonci

Did some more testing today...I've tried triggering vems from my laptop sound card and here are results



http://free-st.t-com.hr/cmuzic/vems/log2.vemslog

http://free-st.t-com.hr/cmuzic/vems/log3.vemslog

It seems that the problem is in vems after all. I have 3.1 board with 1.1.70. firmware. Do you know what could be causing this behavior. Is there some mod that I could do to triggering hardware to fix this?

tonci

problem solved...engine_off_delay was set to 00....increased it to 02 and everything works ok now