My first question is:
When tune logging, am I supposed to calculate tune with a value file from the original tune, or the tune setup for logging (14.6 AFR...-4 degrees Spark...etc.) in other words, do I save the value file in its original form or save it after I have set the tune up for logging?

Otto[/QUOTE]

You create your pvv file from the tune you will have flashed to your ecm before your logging runs. When you calculate tune in the PV Log Tuner software it uses the pvv file that you created to calculate the tune. Once you calculate tune you save that pvv file then import it in the WinPV software, save as pvt as your new tune map.....

 

Not sure if some take time to review log files in excel but I find it very useful in looking at what’s going on in different areas of the MAP. One thing I do is highlight the row with the entire channels I’m logging and select Filter. As an example if I want to see what the engine is doing in the 50KPa area of the MAP I would click the dropdown button deselect all and then check 50-59KPa, this will show everything that was logged in a particular area, i.e. Throttle Pos., RPM, VE, Spark knock, etc. Another example is if you had Spark Knock, you can select only those Spark Knock events and see what the engine was doing when it occurred. You can do this to any of the channels logged....Just thought I would through this out for those interested…..

 

I'm still not following.

Okay. I have a tune from dynojet.

1. I load it into WPV
2. Change the afr table, -4 on spark tables, etc.
3. Save it as a different version of that tune for logging.

So I now have a different tune....correct? Does this logging tune have an effect on how the bike runs or will it run the same as the original Dynojet tune?

You said save the values from the tune loaded in ecm before logging.

Are you talking about the original tune or the tune with modified values?

Does the software use the tables from the original tune + logging data,
Or the modified logging tune + logging data?

In the downloaded guide I have, it lays out everything and then it says, before you do any of this you need to go back and modify your tune for logging.

Maybe I am confused between open and closed loop tuning.

Please explain this to me

At risk of being redundant, which one of these do I do:

1. open dynojet tune in winPV
2. save values,
3. modify tables for logging.
4. save as logging tune.
5. export to PV
6. flash ecm
7. log ride
8. load log in WinPV
9. open value file
10. use software to adjust tune.
11. Save newest version of tune
12 export to PV,
13. Flash ECM

or

1. open dynojet tune in WinPV
2. modify tables for logging.
3. save values,
4. save as logging tune.
5. export to PV
6. flash ecm
7. log ride
8. load log in WinPV
9. open value file
10. use software to adjust tune.
11. Save newest version of tune
12 export to PV,
13. Flash ECM

Thanks,
Otto

 

1. open dynojet tune in WinPV
2. modify tables for logging
Remember with the Narrow Band O2 Sensors Closed Loop (14.6 AFR or 0.981 Lambda) is the only area of the MAP that the PV Log Tuner will calculate the tune.
3. save values as pvv file
4. save as logging tune.
5. export to PV
6. flash ecm
7. log ride
8. Import log files with WinPV
9. Open PV Log Tuner
10. open pvv file that you saved.
11. Open log(s), you can open more than one at a time.
12. Calculate Tune
13. Apply tune
14. Save as pvv file.
15. Open tune file in WinPV (the one that you saved the original pvv file from)
16. Import pvv calculated tune file
17. Save newest version of tune
18 export to PV,
19. Flash ECM

If you still do not understand PM me and I will give you my cell number and you give me a call, i will be glade to step you through the process.

 

Yes that clears things up.

Thanks.

 

Ok talk to me like you would a 6 year old now , but why won't the update tune via PV work for me. I know how to datalog and create the pvv calc tune and all that,but for some reason when I try to update my tune for the new software/firmware I always get "error loading" ? Unless the current beta is only for autotune,I dunno.

EDIT= Sorry guys, I went back and upon re-reading the info on the beta software have now understood how it works and I'm quite happy! You can now datalog and apply the learned tune directly on your bike's powervisionand then try the new map immediately without ever going home to your computer! Just try not to do it all on the fly, although possible at least wait for a red light or pull over point! Saftey First!

 

Yes, do the tuning first to set the VEs. You should do that even if you don't make any other changes. The Tuning basics will walk you thru that. The colors on the Map and other tables just help give a visual of the values. No special meaning other than showing contrast.

 

The autotune module just gives you wideband O2 sensors which allows you to tune even when you are not in closed loop. So it makes it easier to tune the higher RPM and Throttle opening areas of the map. I have tuned both ways - with stock O2 sensors and with the autotune modules. Tuning with the stock sensors is fine and works well. The wideband sensors give a little more flexibility. Since I run an open loop map, the AT module allowed me to tune with richer AFR settings.

 

I tested the BETA software this weekend. I tuned using my existing map using the new integrated Autotune feature (dont confuse with autotune modules with wide band sensors). The autotune feature will setup your map for tuning, do datalogging and then apply the log to the map to create a tuned version for you - all on the PowerVision. No downloads or running other programs on the PC. I made several runs and will compare the changes the autoune feature made today. It was easy to do, now just need to check out the results!

Note: The BETA AutoTune will tune in Basic (stock O2 sensors) or Pro (wideband AT module sensors) mode.

EDIT: Just reviewed the changes made by BETA Autotune. Very minor VE changes, which is what I would have expected since my VE tables have been tuned pretty well before. Looks like everything is working, no surprises using the Autotune integrated tuning function on the PowerVision with BETA software. So far so good! The software setups the tune you select for tuning, logs all the needed data and applies the changes for you. It is very easy to do.

 

I've had the new betas (FW and WinPV) for over a week but haven't loaded them yet. Wanted to get some feedback first to avoid the major issues I had the last time (big problems with 176 calibrations).

Did you look at the new gauge setup in FW 1142? They supposedly made some changes as per our long-time complaints about how the gauge array worked. There is now a "Themes" button that allows you to select "All" (same as always), "Digital Day," and "Digital Night." The last two provide only two 4x and two 6x digital gauges giving the same data between day and night. IOW if you set day 6x to specific gauges the night version will be the same.

I'll probably load both WinPV and FW 1142 today.

Edit: Did a ride with the 1142 FW and the gauge change was just what the doctor ordered, for me anyway. No more scrolling through analog gauges that I don't ever use. Haven't tried AT-Pro yet, and will likely only do so for testing purposes, as I will probably use the old-fangled procedure with PV Tune. I don't import the spark-knock values and assume in AT you can't pick the values you use for the final tune like you can with the old multi-step method.

FWIW, those using the MPG gauges will see a change when moving to the beta FW. The Fuel-Used value was altered by 20%, so you'll need to lower the correction value by that amount. To start off with I changed mine from 1.12 to .92 and will start to tweak it again. It doesn't look quite right yet, but it'll get there.