Glad it worked out for ya. That hit screen sure makes things easier. Just make sure you watch the road every so often I think you'll notice spark knock events each time you datalog, at least I did. Each time it takes out just a little bit. At some point you'll have to determine if they are real or not; and, not include them when you make a new map off the pvv and pvt file. If I don't hear pinging on that run I ignore the recommended change.

You didn't happen to have the HD Stage I map on your new bike did you?

 

No stage 1. Bike only has about 1500 miles on it. I put dresser duals and a heavy breather on it and Jaime sent me a map to get started.

The map he sent is very close. I Just did another log run, this time I pulled 4 degrees of timing out of the upper range and increased my narrow band field to catch more cells. VE delta is around 1 or less in most of the cells. I'll do a few more tunes like that then return the AF and timing back to where it was and then go for some log runs strictly for knock events.

Thanks for your suggestion earlier.... it really paid off!

 

I've read through so much of this thread as well as Dennis's great writeup and it's still not clear to me..Seems like CLB should be set as close to 14.6 in the tune you use for logging and then adjusted richer after you have the VE's set & the tune is ready for "production"? Otherwise the VE's would reflect the bias. For now I'll be using a closed loop tune when done.

Thx

 

i was doing a basic log tune to try to resolve the occasional Knocking on front and rear cylinder after some adjustments to my AFR and timing... i was wondering, if the bike goes into EITMS, can the log still be used to adjust VE tables in PV log tuner or will it mess it up ? I noticed when in EITMS, the MAP sits at 40-50% when at idle instead of the 20% when not in EITMS mode...

 

Hello All

If anyone is feeling adventurous today, DynoJet has released a new BETA version of the PV software. I am sure several of us will be testing it out and reporting back. DJ has said it is OK for the “high level enthusiasts / forum members” to give it a try.

The features included are:

1. AutoTune – fully integrated / embedded (you don't need a laptop to tune)
2. Quick Tune
3. Update Tune
4. Misc. WinPV and PV features

More to come on the testing. If interested shoot me a PM or send an email to DynoJet at PVtech@dynojet.com.

AGAIN, this is BETA software and while it is normally pretty good, sometimes there are a few bugs. I would only recommend this to those who are already pretty familiar with how PV and Log Tuner works.

 

Any consensus on whether smoothing the VE tables helps or not?

 

I believe it does help and here is why. The "calculations" within the ECM use data that is more of a flow rather than just the points of data we see represented within the tables. I look at my VE tables and smooth any obvious peaks or valleys between cells to provide a smoother transition. I don't use the smoothing functions but do it manually.

 

Updated to the new versions without a glitch and as soon as possible will run some collections and compare those to what using Log Tuner produces. This newer version seems nice has it indicated that it will setup the tune for collections on the device so you don't need to plan for a "tuning calibration" on your PC. I've enquired what those adjustments are, but presume its turning off features like PE, AE, DE, Adaptive Fuel, etc...

 

I do both...manually smooth the peaks and valleys and then use the smoothing function to finish the VE tune. It is hard to determine the overall benefit but I like the way the bike runs.

 

How do you use the smooth function? Do you highlight the entire table or only those areas you manually adjusted. I'm assuming you manually adjust first.