They must've pulled it, as it isn't there anymore. I definitely saw it the other day with a "latest update" shown as 03/02/12. The version up there now is 1.0447, which dates back to August.

 

Yep. Maybe they weren't ready for the next version. I will be installing cams this weekend and after that I will be doing some data log runs. After reading all the threads and asking a couple questions I think I have it down with the exception of setting retarding the spark tables. if the cells has 45.00 and I set it to 42.00 would that be retarding the timing 3*.

 

Yes, you've got it right.

 

So do you subtract 3 from the whole table or just above a set RPM?

 

I would think you would subtract 3 degrees in the cells where you have your lambda set at 0.981, closed loop.

FWIW, my map from Fuel Moto had lambda set at 0.981 from 20-80Kpa, 750-4000 rpm's. Jamie said that I did not need to reduce timing with this current map but if i wanted to extend it out further then I would need to reduce timing.....

 

I think it's easier to reduce for the entire table, via the upper left hand corner, and then you can easily add it back in via the same method once you've got your VE's close and you re-enable knock detection. From there, continue on to fine tune VE's and spark advance.

 

Jamie's timing maps are very good and close. After several runs, I've only had to reduce timing in one cell so far. Once I get my VE's finalized, I may start increasing the timing a little to see how much it will actually take. I'll add 2 - 3 degrees for the entire map, and then see where it reduces after data logging; continuing this trend until I start introducing pinging in multiple cells. Once I get a good feel for what it tolerates, then reduce timing a 2-3 degrees across the board for a safety margin.

 

You should be a little bit carefull with this stategy, as common as it is. There are a lot of places in the timing tables that are not spark limited. You will still be adding timing and the only thing that is happening is your power is going down.

 

Good point - thanks!

 

I am just running the fuelmoto map provided and doing multiple log runs with it in various ridding conditions. I dont plan on getting very deep into the tuning (adjusting timing). Should i be? Or am i ok just data logging the fuelmoto map and then leave the tuning alone? Thanks