Power Vision Information Thread
In my case the AFR values are set to 14.5 (in the area where they were previously 14.6 in the stock map) so the bike is running in open loop in this area instead of closed loop. My VE table values in these same areas were increased, so Jamie says the bike is really running an AFR of approx. 14.3 rather than the 14.5 that is in the AFR table. I really don't understand how this works, but I have faith in Jamie.
We really need autotune so that each individual can use the O2 sensors and data logging to populate the VE tables. I think it will then be much easier to accurately set up the AFR tables.
My tables (AFR and VE) were created from my PCV map, and I've made no changes to the AFR and only a few minor changes to the VE tables so far. I will be using the PV Tune once I figure out how to use it, but for now I'm happy with the way the bike is running.
Last edited by iclick; May 23, 2011 at 09:52 AM.
Also I finally did some mileage checks and as others have stated the PV is optimistic by about 15 to 20%. This will be nice to be able to correct.
My tables (AFR and VE) were created from my PCV map, and I've made no changes to the AFR and only a few minor changes to the VE tables so far. I will be using the PV Tune once I figure out how to use it, but for now I'm happy with the way the bike is running.
The way that I understand things the VE tables should be set-up initially by tuning the whole RPM/KPA range to a certain AFR such as 14.5 (either via O2 sensors+data-logging+autotune software) or using a Dyno, then the AFR table should be set up to run the exact AFR you want it to run in each particular area of the map (within the range of your O2 sensors).
I know that the DJ PC import PV map for my set-up is open-loop only and is very different (AFR and VE tables) when compared to the "custom" map that Jamie provided me with when I bought the PV. I do not understand why the 2 maps are so different for the same set-up (especially the VE values). The FM map does seem to run better than the DJ map and is definately more fuel-efficient.
I just loaded a beta version of the FW that will allow me to change the Fuel-Used parameter from the PV's edit mode. MPG (instant, TripA avg., and TripB avg.) keys on this and the VSS calibration (distance) in WinPV, but I'm not real clear on the latter parameter since I don't have it in my WinPV array. I think it is the Speedometer Calibration, but I'm awaiting a clarification from DJ.
I'm not sure how all this will pan-out, but I think I will be able to get the Fuel-Used calibration dead-on with this new parameter. OTOH if it uses the Speedometer Calibration to figure distance I won't be changing that, as I want the speedometer to stay accurate like it is now. Unfortunately the speedometer in the fairing doesn't jibe with the one in the ECM, so that may account for the accuracy inconsistencies that I saw on this trip. Oddly, the ECM odometer also doesn't jibe with the fairing odometer.
If this is confusing to you, you're not alone. It seems that with the setup they've come up with, getting the MPG and distance parameters to become accurate may cause the speedometer and odometer in the fairing to be off. I'll post when I learn more, but I do have the new beta FW in the PV as well as the beta WinPV required and will be testing it.
The Best of Harley-Davidson for Lifelong Riders

Jamie Long / Fuel Moto USA
The USA's Leader V-Twin EFI & Performance www.fuelmotousa.com
Contact 920-423-3309
Email jamie@fuelmotousa.com







