A less serious topic. Last spring I took 10 readings to dial in my Trip A MPG calc on the PV, and got it so it would be pretty accurate. After running a couple of tanks of gas through this spring, which I pretty much ignore MPG, I noticed on my 4th tank fill up that PV said I was only getting about 33 mpg, when my "gas station" fill up said I was getting a bit over 40, which is about average for me. Did something change in the last PV update to make it necessary to recalibrate my mpg calc again. Is this going to happen every time PV gets an update. The reason I care is I use the PV mpg calc to make sure I am not losing mpg quickly, which might point to a problem. Thanks for any feedback.

TedMan

 

I bought my PV a few months ago from FM primarily because I have an 07 Road King and I wanted some gauges. They sent me a map that I felt works great but I understand that it can be improved upon by doing some data logging.

Tried a data log run for the first time yesterday for 50 minutes. I finally was able to figure out how to compare the maps and the results have me confused.

The only changes are in the 750 and 3500 RPM cells from 27 to 70 KPa. The delta is -0.1 in all of these cells.

I thought the FM map was very good but shouldn't there be more changes to this map? Obviously I am a novice at this but would like to hear your thoughts.

Thanks

 

The only thing I can think of is that you are in open loop for most if not all of your map. That doesn't explain the two groups of cells you had changes in, I've never had changes in any 750 rpm cell now that I think about it. When you compared the two tunes was it in log tuner or win pv?

 

I did the comparison in WinPV. My O2 sensors are plugged in so shouldn't that be closed loop? All my gauges were working before and after I did my run. I spent 50 minutes cruising with quite a few hard pulls through the gears.

 

Just cause you have O2 plugged in does not mean it is running in closed loop, there is a satting to turn closed loop off or on and if you have your afr set outside of the narrow bands range it is automatically open loop (i believe it is open loop if set at anything other than 14.7 but not 100% on that).

In your previous post you said you did a log run, if this is true you should go into winpv and select "get log" select the log # you just ran and save it, next you need to open the tune you were running the log on and check the boxes for front and back VE's, afr, and front and rear spark advance. Go to file select "save selected values", this will save the selected values as a .pvv file. You can now go into log tuner and click to open the pvv file you you just saved, after you open the .pvv file log tuner will now let you open your log. Once you open your log select calc. tune and you should now be able to view ve deltas, spark knock, what cells you got hits in ect..

If you ran a AT run did you select "export changes" when you were done? I really can't think of anything else to check, the only other thing i could recomend is to try a couple more runs today and see if this was a fluke. If nothing works give FM a call tomorrom and I'm sure they can figure it out.

 

Thank you very much for your reply and advice. I'll check my settings and try to do what you said in WinPV & log tuner. I did export my changes previously. Thanks again.

 

You might want to run the update process (pv update client with the PV connected to the computer and the computer on the internet) and then try the onboard auto-tune.

It sounds like you are trying to use onboard logging with the log tuner software.

Using the off-board method, _you_ need to setup a number of logging channels, create a modified map (retart timing, changing lamda or AFR, etc) flash the tuning load and then log.

Much easier to use the on-board AT function, where the PV will create and load the modified map for you, etc.

I did my first 2 via logtuner (factory cam and Andrews 26), then as a test re-did the A26 map via the on-board (as a test for the late beta releases) and came up with a map +/- 1% of the logtuner method. Currently dialing things in fore the new A48s using the onboard. Much simpler to use, I just pull the updated map into winpv every few revisions to compare.

 

I did the latest update from DynoJet. I just got back from another data log run, exported the learned values into the map and flashed the ECU. I ran it hard, hitting the rev limiter in 1st & 2nd and really strong pulls in 3rd, 4th & 5th. I hooked the PV up to my computer and looked at the map and compared it to the FM map and it shows no changes. Obviously I am doing something incorrectly. Would someone please write and publish "PV Basic Tune for Dummies"?

 

Start with your FM map in say slot 1 and the others open. With key and run switch on but bike not running going into "Vehicle Program" (top left), then AT.

Should say AT not active.

Hit "Enable AT" then select your base map.

Select "Basic"

PV will generate a modified tuning version of tune and flash to ECM.

WAIT until it tells you to turn the key off for 10 seconds (do not power off when it talks about ECU reset, too early).

After turning key back on, let PV boot and go back unter program, AT.

"Enable AT" will be greyed out.

Start bike, let it warm up....

Select "Datalog", it will go into the AT screen.

The "Log Start" button is for creating an extra log for review by log tuner, is not required.

The "Mode" button will cycle through various screens.

Once in datalog under AT it will be logging data and will auto-save every so often and whenever you come to a stop.

Ride for 15 - 30 minutes, get some good fill in the center.

Stop, exit datalog.

You will see min/max /avg change values, etc...

Kill the engine (run/stop switch), flip switch back on.

Hit export learned and save to open slot.

Hit "Disable AT". This will stop AT but leaves the tuning map loaded.

Hit "Enable AT", this time select the map you just exported...

Lather, rinse, repeat.

I start with at least 4 15 - 30 minute sessions just running around town easy to get solid fill for most of the regular riding range.

After that, I move to much longer and multi-session (you can put in AT mode, go riding a couple hourse, park for the night, ride a few hours the next day, etc. before exporting).

The point of the later long session is to try and get 50+ hits everywhere I can reasonably hit, so my last cycle tends to be riding a couple hours a day in varied conditions for multiple days.

You can always download the created maps and compare step by step in WinPV.

In general, you _should_ see minor changes in eny cell where there are enough hits. A good run on a well mapped bike would see semi-random shifting of many/most of the hit cells by < +/- 2%.

Check out <http://www.youtube.com/watch?v=l1fppB5rSYo> posted by DJ.

 

Thank you very much for taking the time to post those instructions. I have watched the video in the link from DJ at least 3 times. I have been exporting the learned values while the bike was still running. Maybe that was the problem. It would tell me ECU not responding (or something to that effect) and then I shut it off and restarted. I was afraid I would lose the new map if I turned off the bike. I will follow your instructions the next run which probably won't be until next weekend and take it from there. Thanks again!!!!