Here is a video of the presentation James (one of the original authors of ms1/extra) and I did at the MS meet last weekend.

http://video.google.com/videoplay?do...2237&hl=en

It's mainly just us talking about the past (MS1/extra) the present (MS2/extra 1.0.x) and the future (MS2/extra v2 and a couple of brief mentions of ms3).

Ken

 

Ken,
Watching the video, you guys mention a significant amount of spark timing loss due to hardware. Can you detail that a bit here?

If people are running a max of 27 deg advance from 3000 through 8k, what kind of timing is really happening? I might have to break out the timing light to see what you speak of.

Thanks
Pete

 

Nevermind, I found the thread on MSExtra.

http://www.msextra.com/viewtopic.php?t=24388

 

Yeah, it was just a couple degrees... but it's enough, and we noticed it, so we added a setting to allow the user to fix it. Use the following procedure to set it:

1) Set fixed timing to something you can measure... -5 on an rx7 works well.
2) Check the timing at idle
3) Rev the engine to around 2000-3000 rpms (if you can... might not be able to with -5 timing)
4) Adjust the new setting up from 0 in increments of 10-20 usec until you can rev the engine slowly without the timing moving.

The latency is really combined from the VR sensor conditioner itself, some software latency, and some other hardware latency.

Ken

 

I just tried the 029y1 code in my v3 ms1 molded cas, and it doesn't seam to make any difference, i still get about -5 degrees with the fixed angle at -5 (tested from 10-255), but the one thing i cant figure out is after i set the fixed angle to -5(verified -5 with light) to test and then set it back to -10 (use map) it dont use the map, on the main display in megatune it is at 10 deg advanced, if i go to the spark tuning menu it is at the same as the spark map and if i check with my timing light (2cycle light) its at 20 take away 5 degress for the mark and i have 15 at idle? any idea before i put the 029w code back in it?

 

I'm not sure from reading your description what you've done. I did the procedure I described above and was able to get rid of all timing change due to latency in the hardware. Meaning my timing would stay locked on -5 even while I revved it.

 

Ok i must have loaded the code wrong or something. Can u after updating the code from 029w to 029y1 just reload you're msq from the 029w to ms ecu with the 029y1 in it?And what latency did u end up with to give me a better idea!
thanks

 

I think my latency was around 30 usec. I don't remember for sure off the top of my head. It also depends on some other factors, like what your pots are set to for example.

Another thing I did to help me find the answer was I hooked up my oscilloscope to the VR sensors, and to the output of the conditioner, and measured the time between zero crossing on the VR input and the rise (or fall, depending on where you scope it) of the +5v square wave on the output of the conditioner.

I'll have to find my settings and confirm at one point or another.

Ken

 

Well I figured out what I did lol I forgot I was messing with idle advance ops I for got to put the -10 in, it was at 10 , so when I took the fixed angle away it was stuck at the idle advance witch was 10!!I came up with 40 for the latency @3000 it seemed to help putting the fixed angle at 20 then setting the light up for the timing mark witch smoothed thing's out a bit!
Thanks for you’re help ken

 

Sorry for the stupid question, but I am not sure from reading around how you are actually supposed to go about adjusting the latency. I made the firmware update and activated the new ini in the configurator. However, I am kinda confused as to how I might actually change the latency. Sorry I'm kinda out of it.

dpf22

 

If you mean were it is at in megatune, go to advanced then to advanced code options, it is at the very bottom of that page.

 

holy cow, I'm freaking blind. Thanks tons dude.

dpf22