I'm no expert on the subject, but I think that as long as the VE tables were correctly set up for your bike + mods on a Dyno that the value you put in the AFR table (within the working range of the Narrow Band O2 sensors) is what the bike will try to target as the AFR while in closed-loop. Don't forget that if your closed-loop bias values have been increased/decreased the actual AFR will be richer/leaner than the AFR value you input into the table.

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.

 

I'm really confused here. Below is my AFR table that doesn't look anything like yours. I need some tutoring on how the AFR table relates to the VE table, as I'm not clear on it. Anyone care to give us all a tutorial? I volunteer Jamie for this job.

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 only thing I noticed was that the table posted is a comparison of two tables showing the differences while yours is just the one table.

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.

 

iclick, I think your table vs. ratbob's table are 2 different tables....ratbob's looks like a comparison of 2 AFR tables where yours is just an AFR table. I agree a tutorial would be nice.

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.

 

Okay, I got, and it would've helped if I had read the poster's explanation.

At first I was getting 7-10% low on fuel-used and 10-15% high on MPG, so I had DJ change my MPG Calibration manually before a 1500-mile trip to AR recently. I had to send them my tune and they changed it. The result was a big improvement, with MPG showing 5.8% low and fuel-used 1.2% high. The distance shown by the PV was 2.4% low.

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.

 

Let me ask another dumb question. Do you guys think that I could pull my stock map from my ECM with my PCIII connected. Then do my merging of my stock and import my PCIII tune together and then download my ECM? Then diconnect my PCIII.

 

Need some help with EITMS. I found the switch in the switches and limits section. What I don't seem to have in my calibration is the environment section where the on and off temperatures are set. Anybody played with this? This is on an 07 Street Glide. 103, FM map.

 

You won't have the temp calibration in your '07, and even if you set EITMS to "1" (enabled) it won't do work unless you have the factory download (Calibration ID 34412-07D) that enables it. I don't, so EITMS won't work for me regardless of this setting. To find out which Cal. ID you have I assume you'd need to take it in to the dealer and connect to the Digital Technician. They may upgrade for you without charge, as my dealer always has.

 

Talked to my dealer and they will flash it in for 30.00. Seems reasonable. I take it I then reflash with the cal from FM?

 

You will need to remove the PC III first as you cannot retrieve or send calibrations to the ECM with a Power Commander installed. In most cases it will scramble the Power Commander map and the data will be corrupted