Re: Quick tune, I never used it because it changes whole blocks of cells instead of the one or two that may need a tweak. Also can't be sure but I seem to recall something about Quicktune being temporary. Like if you add some fuel or pull some timing, It will just be overlaid on the tune your riding. If you try to then load that tune into AT it will only load the base tune without the QT changes, I'm not sure if you try to load copy of current tune with QT changes into a slot and and save it. Then Get Tune in WinPV and compare to original if the changes will be there either. (too much hassle)Anyway the changes have to be saved to a .pvt file and flashed to ECM for them to be permanent, AFAIK. I could be wrong thats just the way I remember it. If one of y'all try it let us know.

 

And I wonder why the Spark table from the tune that came from PV exactly matches the one that came on the bike stock ( 2011 48), given that there are so many variables to determine the timing.

 

How do you guys feel about using the smoothing feature? I've done 4 auto tunes and have most the areas I can hit to less than 5% change. So should I leave it as is or try smoothing it? Bike is running good but I'm seeing some knock retard on the highway while watching the gauges. once I get the ve's sorted I'll start playing with the timing a little. Still gotta figure that part out.

 

no one but yourself or your tuning pro should adjust the timing/spark tables specific to you bike and in reality, you should adjust everything yourself or by your tuning pro. These canned calibrations and emailed calibrations are NOTHING more than a starting point for you and usually not even close to what the final tune will be.

 

True- I had a long call with lead tech @ DJ and he;s the guy that also teaches Dyno tuning instructions on the DJ equipment. Very nice guy and very smart. In short, the canned tunes are mild and "safe" from a liability perspective, from a business standpoint this makes sense. It sucks, but at least you've been informed. These canned tunes may give you some more accurate VE tables for your specific combo of intake / pipe / whatever, but, the overall tuning parameters are not much different than stock, on purpose.

On that note, the stock HD tunes on stock bikes are purposefully "safe-a-fied" for new riders. For example, all power is removed from the lug zones of map. This prevents new "green" riders from messing up the motor during break in- too much power in this zone combined with excessive lugging can cause things like flywheel shift. With power removed from this zone, lugging will not have enough bang to cause harm. But this also makes the bike feel slow on take off and roll-on from cruise in the lower rpm's - So this is what I'm just repeating, if you don't agree then don't shoot me ok?

But all this leads me to firmly understand that if you want a decent tune, work with a decent tuner or learn the system and tune yourself. the AT basic is only going to help with things like economy, idle and cruise. It will not help with performance gain or things like decel cracking / pop. Using AT basic with a good working performance-oriented tune can actually un-do the performance aspects of the tune.

The "Adaptive" setting can also tame a performance tune by changing the fuel trims to a more economical value- that is mainly what it does. To stop this from happening, run the tune in open loop only by setting AFR table values outside the Closed Loop Lambda range. This will allow you to leave "Adaptive" enabled in the ECM, and Adaptive Spark will still work as a safety measure against spark knock. But Adaptive will no longer alter the fuel trims due to preventing Closed Loop operation. Again just repeating what I was told.

 

I was told you can save AT to a new separate tune- Have not tried but this is the instruction: On your running tune, go to AT and enable, select your currently loaded tune and let it complete. Then do a AT enabled ride. When done, save the results to a new empty slot. The saved tune will be your starting tune with the AT changes applied. The original tune will not be changed. From here you can open both of these tunes on WinPV for a compare session to see what AT wanted to change and by how much.

I was told this as well- If you do not want to save AT yet but just want to see the changes AT wants to make within the PV2, go to the "More" screen after the AT session. Select LCORF and LCORR to see AT's suggested VE changes for front and rear cyls.

FWIW - i was going to try this out over the weekend / no time yet.

 

This question is for Jamie, or whoever can have an educated answer.
There is (ET) engine temp reading, as I have been told this sensor is front left by the cylinder.
There is also Head Temp I believe this labeled (HeadT). Where would this sensor be located?

 

Jamie- Sorry I missed this but also got the same instruction from DJ on this. I installed the Powercore suite and ran the CS3 Data Center program, imported a saved log file csv from the PV2. The log file never actually displays data. It takes some time for the import to convert (relatively short 5 min log file), but when it's done importing there is no visual data displayed in any of the views. I tried this with several log files (now that I know how to log).

How are you getting csv log files created in PV to view in CS3 Data Center? I'm tech guy so I do understand the csv format and using Excel, but I have no idea what to really look for as far as tuning from logged data in the Excel views. Lots of data in lots of columns. What's important to you in these log files when tightening up a tune for performance?

 

Yes thats exactly right, The way to build on one tune to the next and view the progression of changes in VE values by %age.
What I was trying say was using the Quick-Tune option on the fly has its uses but doesn't actually Flash the ECM with the changes. They'll reset If/When that 'base' tune is selected to AT or pulled out of the PV to compare in WinPV. The QT adjustments will persist in the buffer until another tune is flashed or adjusted +/- with QT again. I wish I could explain the way I think but I confuse myself sometimes lol.

 

or you can save a copy of current tune after making quick tune adjustments and that will save them. I don't use QT but this is my understanding of how to save those changes.