Login -

What defines a "GOOD" log ??

I would say that a "Good" data log is one that covers the range of the maps that you are targeting for the tune. Its best if you get multiple data logs in each cell as the outlying values will be excluded or have reduced impact on the AutoTune. The AutoTune will make changes outside the logged data range as it applies map smoothing which impacts un logged sections. You can open several .wrl files in the "File"=>"Open Log File" window, just select all of the .wrl files you would like to open in the "Open FIle" dialog, use the ctrl key with the mouse to select multiple files.

Forgive me if this has already been discussed, but since I was unable to find anything.... I.ve only just begun at the bottom of the learning curve so bear with me, I'd like to know just what is considered a 'GOOD" data log, or more precisely, what sort of data am I looking for in the log. IE- should I be looking for a minimum log time, and therefore file size/data count, or is it more important to ensure the entire rev range is captured rather than time, and is it relevant in which gear it is recorded? I've managed to successfully complete my first log and Auto tune, albeit with what appears to be a limited data set from a "normal" ride in traffic logged over 20-39 min. Am I correct in assuming that, since there was little or no data logged above 6,000 rpm, that Auto tune will not make any changes in that area? Can several logs be combined to create a larger data set in any way, and would it improve results in Auto tune?

View Topic on the Woolich Racing Forums