MicroSquirt.com read only forum (Jan.15,2018)

All of my previous testing and data was run at 1450 RPM. This was the reading in TS and I also verified it by looking at the dt between the t1 signals of a full revolution.

I wanted to make sure I was understanding all of this correctly, so I marked up the picture I took of the scope at 135 offset ...

Tonight I verified that I get the same jumps in timing when I use the VR1 input instead of the optin inputs.

I am changing the base timing table when I see it jump. I get the same results when I change the timing offset though.

I have long ago set my cold advance, IAT advance and all other timing modifieres to 0 to eliminate the problem of irratic or drifting temperature sensors. The timing value on the ...

When you say triggering, I assume you mean the trigger on the scope? In the pictures above I was using the tach output signal to trigger the data capture on the scope. I have also used the spark output, with similar results showing that it will jump ahead a tooth.

As a side note, I've also used an ...

Sounds like it must be a problem with my setup then. I have been scratching my head for a while now without any ideas . I've attached two pictures of my scope with the same msq that you tested. The first picture is 5 degrees timing advance and the second picture is 4 degrees. You can clearly see ...

I am using an optical sensor that generates a square wave Verified with the scope, so I don't think it is the polarity issue. The data was collected at a constant speed (1450 RPM), so the VR delay might explain the +10 error, but it doesn't explain the sudden shift in timing accuracy as requested ...

I've got my uS running on my bench for testing purposes and noticed that occasonally the timing would jump around. I decided to investigate this a little bit and hooked up a scope to the crank signal and the timing output from the uS. What I found was that depending on the trigger offset, timing can ...

This is 2.0 version of microsquirt with black board.

I'm using a 5v signal from an optical sensor as an input to my uS, but I've recently had problems trying to pick up a signal on VR2. I can successfully pick up the signal on optin 1, but not vr2. I decided to check the signal to the cpu using tooth analyzer and verified that the signal is being seen ...

I see that the MS recently got updated to handle a USB connection and also an adapter for a flash drive for data logging. Are there any plans to update the uS with the same features?