Changing from 14.5 to 14.6 would not require any spark changes, that is a very minimal change. The biggest thing that will do is put the bike in closed loop. If you decide to change the AFRs above 4500 to 14.6, you should pull 4 degrees or timing but I normally don't recommend narrow band tuning in the upper ranges like that. 13.8 to 14.2 should be a good range.

 

I run an open loop map at 13.0 for wideband tuning and at that AFR my mileage suffers as well, so that I understand. However, when I run at 14.2, performance and mileage improves as compared to closed loop 14.6. As they say, results may vary.

 

Just a observation. My base fuel moto map in the upper RPM when looking at the data logs seems right on the money I have many data logs now and have had the bike to 5858 RPM. and the new and old VEs are right on.

 

Thanx man, Ill be givin this a shot.

 

Tuning procedure question
Do you guys get multiple logs and then use the log tuner?
Or do you do one run at a time, run the log tuner then repeat?

Thanks in advance

 

I do multiple logs. Example I took a ride to Ocean shores that day I did 9 logs. When I did logs closer around home I was doing 5-6 logs at a time. I personaly am able to get better map coverage in multiple runs.

 

If you want to run at 14.6 in the cruise range I see no reason to run open-loop. I'm only doing it because I tune with the WB sensors and running CL would mean pulling the WB's and re-installing the NB's, which is a hassle. The ideal, of course, is to have two 18mm bungs on each pipe, but getting that done would be a hassle too.

The only way to tune and run with the PV and WB sensors is to use open loop, as the stock ECM can't communicate with them in any way. The process is to log the 11 parameters from the ECM plus Lambda 1 and 2 from the WB sensors. PV Tune then takes the datalogs and looks at the set AFR (ECM AFR table) and compares that value to the actual AFR reported by the WB sensors, then adjusts the VE tables accordingly using some sort of algorith. At no time does the ECM even know the WB sensors are players either during tuning or running.

When running normally and not datalogging the WB sensors can only display Lambda readings on the LCD display, which I find very useful.

 

I get emails when updates are released, and they contain download links.

 

Thanks. I pulled the latest firmware. I tried another run using just the AutoTune - working off of the previous .pvv it generated. It was even farther off. Seems they need to work on the algorithm a bit more. I'll stay with Log Tuner for now, but will give AT a few more shots once they sort it out.

 

Along these same lines. Are we to assume that if we're using multiple logs that the minimum hit count we set in options is for those logs combined or per individual log. If the latter, there is some value in longer log runs.