Cannot use VR2in with VR on cam b/c of transition offset

[Matt Cramer]

The new setup doesn't actually seem to have a missing tooth on it.

[adamv61243]

But it does have a missing tooth, as seen in the picture... I physically installed it:

triggerWheelConfiguration.12-1.png

Do you have any suggestions on what I should do?

Regards,
Adam

[adamv61243]

This is a close up of the trigger wheel from PE's website:

images-2_4_large_ID.jpg

GSXR600 trigger wheel close up from Performance Electronics

(50.58 KiB) Not downloaded yet

This is the guide we used to place it:

http://www.pe-ltd.com/Downloads%5CSuzuki%20App.pdf

Here's another Missing Tooth scope image, that also shows the cam pickup:

scope_8.png

Missing tooth trace, also showing cam pickup

(77.89 KiB) Not downloaded yet

[24c]

Excuse me, but you just have a crank trigger?
So you don't use VR2!
To get your set up to work with my Thunderace I used two diodes using 2.890 to get it to work.

[cornmander]

To clarify, we are not using VR2in right now. We have an 12-1 wheel setup with no cam trigger. See the above posts for more details. I've attached the .msq that we're using now that doesn't work.

I am not sure what your diode solution will do for us -- we don't have a noise problem right now.

Here are two pictures of a bad signal output and a good one. This is exactly the same signal that the microsquirt sees, before any signal conditioning or polarity inversion.

We have a hunch that our VR signal has some problems but we're not sure how to fix them. Notice that our VR signal is not what you'd expect to see with a 12-1 wheel. The signal looks as if there are several missing teeth.

Oscilloscope capture of CURRENT engine signal while cranking:


We have an engine with an identical setup and the signal on it looks much nicer. The time scales on the X-axis are different though and the cranking speed may be different, so take that into consideration:

Osilloscope capture of WORKING engine signal while cranking:

[adamv61243]

We've been debugging this further, and just ran the engine without spark plugs in... to avoid what appears to be the engine slowing down during compression strokes. We have installed higher compression pistons in this engine, so this could be causing issues... plus it's not broken in. I've also positioned the vr sensor closer to the trigger wheel, and it has increased the voltage.

Here's a trace WITH spark plugs in:

scope_19.png

WITH spark plugs

(137.59 KiB) Not downloaded yet

Here's a trace WITHOUT spark plugs in:

scope_16.png

WITHOUT spark plugs

(110.06 KiB) Not downloaded yet

Would you have any suggestions for making this work? I assume once the engine is broken in, the rpm wont vary as much during cranking, and it will approach the "without spark plugs" trace... but I would need the engine to run to do that, especially now that the trigger wheel is different from stock.

[Peter Florance]

It seems that the timing between teeth isn't much different than the time at the missing tooth.
It would be nice to capture the non working vr signal with a more expanded scale

[adamv61243]

Here's a closeup of the VR signal WITH sparkplugs:

scope_23.png

(33.39 KiB) Not downloaded yet

[24c]

That's a big difference with plugs in and plugs out, and I just wonder if you could phase the missing tooth away from the compression strokes, by say rotating the 12-1 wheel on the crank or moving the sensor. I don't know what TachRef sees? but I imagine the processor is having a hard time with this.

[Peter Florance]

That's a big difference with plugs in and plugs out, and I just wonder if you could phase the missing tooth away from the compression strokes, by say rotating the 12-1 wheel on the crank or moving the sensor. I don't know what TachRef sees? but I imagine the processor is having a hard time with this.

agreed. I could barely find the missing tooth by eye; I can't imagine the code is going to find it easily.