tunerpro datalog help
- Thread starter Matteson
- Start date
Help Support Buellxb Forum:
You can reference the log values under the "Runtime Data for DDFI-III ECM Types" section of the Runtime Information page on ECMSpy.com. Just search for the terms you're interested in, such as "EGO1 Corr", which when clicked has a description of "Exhaust gas O2 fuel adjustment for the front cylinder".
Be aware when searching because the page has two tables, and the first is for DDFI1/2. You want the second table.
Be aware when searching because the page has two tables, and the first is for DDFI1/2. You want the second table.
I take it you have done your research? I logged earlier and I am getting ready to adjust my cells. Just need figure out an easy way to find my closed loop areas. Its not like spy where I just click it and it graphs it out for me. Ugh.
If you have ECMSpy for Mono, I would use it! "Live & Log Data" -> Logfile Analysis !
There are many ways to skin a cat, so to speak.
Yet another way is MegaLogViewer MS edition, which has a "VE Analyzer" function that takes the fuel maps (you provide), averages EGO correction from all samples, and updates the maps .
There are many ways to skin a cat, so to speak.
Yet another way is MegaLogViewer MS edition, which has a "VE Analyzer" function that takes the fuel maps (you provide), averages EGO correction from all samples, and updates the maps .
Above should say '...change "View" to "Running Average" ' instead of History Average.
I had increased the history size in my .adx but forgot that it defaults to 10!
If you want to be thorough, look at the "History Sample Count" for the cells that have been history averaged to see if the full count was reached. Just depends on your end goal; go with Running Average unless you know you want to do otherwise.
I had increased the history size in my .adx but forgot that it defaults to 10!
If you want to be thorough, look at the "History Sample Count" for the cells that have been history averaged to see if the full count was reached. Just depends on your end goal; go with Running Average unless you know you want to do otherwise.
@Matteson
What kind of mobile phone do you use? If it's an Android, you can use ECMDroid to do datalogging and it can convert logs to Megalog Viewer format on saving.
What kind of mobile phone do you use? If it's an Android, you can use ECMDroid to do datalogging and it can convert logs to Megalog Viewer format on saving.
s0dhi, do you know if ECMDroid will create MLV tune files? That's cool if it does! I believe a tune file would be needed to take advantage of the VE analyzer to analyze the EGO corrections. I imagine someone else with an 1125 may already have the .msq and can share. And there is a standalone tool to create them but I think it only works with v4 XDFs. I have also hand-coded them which is a load of fun, lol.
Matteson, ECMSpy has all this logging and analyzing -integrated-, btw, but you may know that already.
Matteson, ECMSpy has all this logging and analyzing -integrated-, btw, but you may know that already.
@ReadyXB
It does create MLV log files. I use a template .msq file to create my tune files - it's a little tedious but it works. I copy the maps from TunerProRT into a text editor and replace the 'tab' characters with a single space. Once done, that can be pasted into the section for that map.
Once the tune file is created, I use the MLV VE analyzer to alter the tune, then reverse the process to get the maps back into TunerProRT. Like I said, it's a little tedious, but it works.
It does create MLV log files. I use a template .msq file to create my tune files - it's a little tedious but it works. I copy the maps from TunerProRT into a text editor and replace the 'tab' characters with a single space. Once done, that can be pasted into the section for that map.
Once the tune file is created, I use the MLV VE analyzer to alter the tune, then reverse the process to get the maps back into TunerProRT. Like I said, it's a little tedious, but it works.
need to post so I don't loose this thread, this is good stuff 
