I noticed after the latest PV software update that now using the"319245" code the PV will store log data even if you don't hit "Stop Log".


The last two times I have gone on short trips and didn't care about the data I just turned the ignition off and when pulling logs later noticed that there was a log file for these trips anyways.

This is great in my opinion because I was losing data with incorrect shutdown before.

Has anyone else noticed this?

 

Typo alert. I just edited with the correction.

 

For me the PV has always yielded a good log file even when I don't hit "End Log." I do it all the time and if I've lost any data I wasn't aware of it.

 

Same here data was always there when I did not hit stop. Wish the start/stop was a little bigger and easier to fat finger.

 

This thread has taken on issues far more sophisticated than my question, but hoping you can bear with me as I work my way through this.

I am in the stage of doing log runs. I am using Log Tuner Pro, AutoTune and the DJ (Bosch) wideband O2 sensors.

My question is: What is the purpose of steps 11 - 13 below?

According to the PV user manual, here are the steps to refine the tune (for me, base tune from FuelMoto) with the Log Tuner software:

1. Open the original tune, which, to stay consistent with the manaul, I named OriginalTuneFile.pvt, and disable certain features before doing a log run (ie, power enrichment, adaptive control), and set AFR to 13.0 across the table.

2. Create a value file for VE, Spark Advance and AFR, named LogTunerValueFile.pvv.

3. Save the tune file as LogTunerTuneFile.pvt, send it to the PV and then flash the ECM.

4. Set up the channels to log (which I did manually but can now be done by entering a code), and then do a log run.

5. Save the log run to the computer.

6. Open Log Tuner software and set "Options" figures.

7. Open value file LogTunerValueFile.pvv.

8. Open log run from nos. 4-5 above.

9. Calculate Tune, then Apply Tune.

10. Resave LogTunerValueFile.pvv, which overwrites the original LogTunerValueFile.pvv with the new values created in no. 9 above.

11. Open WinPV software, and then open LogTunerTuneFile.pvt (created in no. 3 above).

12. Click File/Load All Values and open LogTunerValueFile.pvv (created in no. 10 above).

13. Resave tune file LogTunerTuneFile.pvt, which overwrites the original LogTunerTuneFile.pvt with the new value file.

14. Open OriginalTuneFile.pvt.

15. Select Tune Items in tree for VE and Spark Advance.

16. Click File/Load Selected Values and open LogTunerValueFile.pvv

17. Save tune file with new name, send it to the PV and flash the ECM.

What is the purpose of steps 11 -13? The revised LogTunerTuneFile.pvt (step 13) is never flashed to the ECM after the log run, so what's the point? Only OriginalTuneFile.pvt is flahsed to the ECM after modifying with the revised LogTunerValueFile.pvv. Do steps 11 - 13 somehow change LogTunerValueFile.pvv before that value file is added to OriginalTuneFile.pvt in steps 14-16?

Hopefull my question isn't clear as mud. I'm not just trying to go through the process, but to understand the process as well. If LogTunerTuneFile.pvt is never flashed to the ECM after the log run, what is the point of steps 11 - 13?

Thanks much for your help with the first of likely many questions...

 

Those steps place the new values into the tune.

 

I think 11-13 are redundant. When you calculate tune, the values are updated in the file you're working in. You can then save and overwrite, or save a new value file. I always save a new value file and then apply it to the current tune, save as a new tune, upload to PV, then flash.

I have all my value files from the original HD tune to my latest, and all the tune files that have resulted from all those value changes. I can walk through my entire tuning history any time and see how things have progressed. I use file naming conventions that reference the change I made for that tuning run. It's easy to go back and remember the effect a part or setting change had on things.

Maybe I'm nuts??

*Edit - Just read that closer (been up since 5am...) 11-13 update the tune with the new values that you got when you calculated the tune and saved the new value file. The rest of the steps seem like more work than is necessary.

1. Generate value file from original tune
2. Do a logging run
3. Get logs from tuner
4. Open value file in the log tuner
5. open log file from tuning run in the log tuner
6. calculate tune
7. save new value file
8. Go back to WinPV, load all values from that new value file
9. Save the tune as a new tune (why overwrite the original?)
10. Send to the PV
11. Flash new tune to the ECM

You now have the original tune, original value file, new value file (reflecting changes from logging run), new tune file (reflecting the new values imported from new value file). Rinse and repeat.

 

Thanks for the quick response. In my list of steps, should I be flashing my ECM with LogTunerTuneFile (created in steps 11-13) or OriginalTuneFile (created in steps 14+)? Wouldn't they be the same since they both were revised with the same value file? Thanks, and then get some sleep!

 

Yes. But like I said, I would never overwrite any tune or value file. If you use a new file in each circumstance every time, it will start to make more sense because you won't get tripped up on file names.

 

I just noticed on my map I downloaded that the EITMS was set at 0 so I put it to 1. I wanted to know how do you know what range it is set at. Just go by what is said in the owners manual. Or is there somewhere were I can see and adjust when it comes on/off. Right now on my Ultra it will activate at 287 then disable at 275. Anywhere in the PV were I can make a adjustment or should I leave as is.