Power Vision Information Thread
#2261
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
Yes it was meant to refer to the Front Cylinder, not the rear
__________________
![](https://i.postimg.cc/wMMjxB1j/F140247926-1.jpg)
Jamie Long / Fuel Moto USA
The USA's Leader V-Twin EFI & Performance www.fuelmotousa.com
Contact 920-423-3309
Email jamie@fuelmotousa.com
![](https://i.postimg.cc/wMMjxB1j/F140247926-1.jpg)
Jamie Long / Fuel Moto USA
The USA's Leader V-Twin EFI & Performance www.fuelmotousa.com
Contact 920-423-3309
Email jamie@fuelmotousa.com
#2262
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
It is going to be fairly normal to see variances in the corrections, the key is to getting VE levelized and letting the O2 integrator and the rest of the closed loop system do its work as normal. Regular corrections for fuel quality, conditions, etc.. are all part of the big picture on how the system is designed. Remember, the data you are using with PV is populated by the ECM doing business as usual, any corrections populated in the PV Log tuner software are simply coming from the data bus itself and the ECM is already using these corrections in one way or another.
I can appreciate the forum let me talk in circles trying to learn. The bottom line is probably me and the way I am riding to collect the data. I am going to raise my hit count I had been using 30 and concentrate on quality. I will continue with my current tune and I will start one over with my original fuel moto map. I am not having any issues per se with the map I manually adjusted VEs on bike to me seems to run pretty good honestly its the best I have had the bike running since I put the cams in but my data logs are saying that the VEs are not leveled out. I get myself confused when a cell seems level then moves a lot.
#2263
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
For best overall performance it is crucial to get your spark timing with enough advance where while mild knock activity is normal and the retard corrects effectively, however the system does not need to apply excessive or large corrections that affect performance negatively.
#2264
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
I can appreciate the forum let me talk in circles trying to learn. The bottom line is probably me and the way I am riding to collect the data. I am going to raise my hit count I had been using 30 and concentrate on quality. I will continue with my current tune and I will start one over with my original fuel moto map. I am not having any issues per se with the map I manually adjusted VEs on bike to me seems to run pretty good honestly its the best I have had the bike running since I put the cams in but my data logs are saying that the VEs are not leveled out. I get myself confused when a cell seems level then moves a lot.
I am postulating that when the CLI and AFF tables both run 100 +/- 2-3, your VE tables are close.
Just curious if anyone else has tried this and I am wondering if this makes sense to others on the board...
#2265
#2267
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
I think that what I am doing is a little different. I am checking the VE table with the AFF Gauge. I think that if the AFF table is near 100 percent, the VE table is correct. From what I have seen, the CLI table will track towards 100 percent as the trim table adjusts the VE tables via the O2 sensors. I will not do a log run until the CLI is at or near 100 percent.
#2268
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
The map you are using is not a closed loop calibration. To use PV Log tuner closed loop is required, you will need to change the closed loop area in the AFR table to 14.6 and I recommend setting the Bias tables to 700. If you would like one of our Fuel Moto maps to start with you can send me an email to jamie@fuelmotousa.com
I'm a little confused on this point. Wont changing the bias tables to 700 increase the afr?
Thanks to everyone for all the great information being shared.
#2269
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
Yes, but not much. The O2mv scale is not linear, as seen in the attached graph. The chart gives a range of values showing Lambda, AFR, and O2mv--but not all of these are usable. I've heard 450 should be the minimum (14.68) and 780 the max (14.43). My stock '07 CLB table shows 500-600 in the cruise range, which is between 14.6 and 14.7. I'm not sure why you can't set O2mv higher, but it may be because of a lack of accuracy above a certain point. Note that in the graph the line begins to shift radically to the left in about the area we normally think of as the max.
Last edited by iclick; 04-20-2012 at 01:45 PM.
#2270
![Default](https://www.hdforums.com/forum/images/icons/icon1.gif)
Yes, but not much. The O2mv scale is not linear, as seen in the attached graph. The chart gives a range of values showing Lambda, AFR, and O2mv--but not all of these are usable. I've heard 450 should be the minimum (14.68) and 780 the max (14.43). My stock '07 CLB table shows 500-600 in the cruise range, which is between 14.6 and 14.7. I'm not sure why you can't set O2mv higher, but it may be because of a lack of accuracy above a certain point. Note that in the graph the line begins to shift radically to the left in about the area we normally think of as the max.
Last edited by fuelmoto; 04-20-2012 at 02:10 PM.