new Uprev log analysis tool
01-11-2011, 11:51 AM
#1
new Uprev log analysis tool
So now that I'm due for a new tune (upgraded injectors) I took some time to write a little app that helps fill in a big gap with Uprev -- **** poor log analysis.
The goal is to take tons of log data (driving around with the laptop left logging and unattended) and present it in a useful way that facilitates non-live tuning which is great for street tuning and even startup trims. WAY more possibilities than could be handled with the crappy built in trace and graphing tools...
http://djlab.com/uprev/maf.php
The goal is to take tons of log data (driving around with the laptop left logging and unattended) and present it in a useful way that facilitates non-live tuning which is great for street tuning and even startup trims. WAY more possibilities than could be handled with the crappy built in trace and graphing tools...
http://djlab.com/uprev/maf.php
Last edited by djamps; 04-26-2011 at 03:26 PM.
The following users liked this post:
trusovici (07-06-2018)
01-13-2011, 06:56 AM
#5
Even though they have the RTT and logging through Rom Editor now... I still us Cipher to do my logging so i can see how everything lays out in a Graph format.. it allow you to see peaks and valleys that numerical values make it hard to see...
01-14-2011, 01:12 PM
#6
I'm making a few changes before I email you guys the link to use it. The main goal of this tool is automatically dialing in long term trims (startup, normal driving, ect) which is pretty much impossible to do with the built in graphs and you can never be 100% spot on in every fuel trim cell by doing it manually...I want to see exactly what is happening in each cell averaged out over time, then have the software suggest subtle changes to be made for individual cells.
The other idea was having a way to dial in the PMAS quickly (MAF voltage) since it's a PITA to have to reflash the ECU for each adjustment, I think last time it took 12 flashes, this time I'm hoping for 2 or 3. For street tuning I've found it far easier to leave most of the fuel table near 100% (+/- 5 throughout) and make most of the changes to the K and MAF table instead, even for boost...without deep log analysis this is very time consuming. The less you mess with the fuel tables the more stock-like our VQ's behave..
The other idea was having a way to dial in the PMAS quickly (MAF voltage) since it's a PITA to have to reflash the ECU for each adjustment, I think last time it took 12 flashes, this time I'm hoping for 2 or 3. For street tuning I've found it far easier to leave most of the fuel table near 100% (+/- 5 throughout) and make most of the changes to the K and MAF table instead, even for boost...without deep log analysis this is very time consuming. The less you mess with the fuel tables the more stock-like our VQ's behave..
Last edited by djamps; 01-14-2011 at 03:42 PM.
Trending Topics
01-14-2011, 06:11 PM
#9
I'm making a few changes before I email you guys the link to use it. The main goal of this tool is automatically dialing in long term trims (startup, normal driving, ect) which is pretty much impossible to do with the built in graphs and you can never be 100% spot on in every fuel trim cell by doing it manually...I want to see exactly what is happening in each cell averaged out over time, then have the software suggest subtle changes to be made for individual cells.
The other idea was having a way to dial in the PMAS quickly (MAF voltage) since it's a PITA to have to reflash the ECU for each adjustment, I think last time it took 12 flashes, this time I'm hoping for 2 or 3. For street tuning I've found it far easier to leave most of the fuel table near 100% (+/- 5 throughout) and make most of the changes to the K and MAF table instead, even for boost...without deep log analysis this is very time consuming. The less you mess with the fuel tables the more stock-like our VQ's behave..
The other idea was having a way to dial in the PMAS quickly (MAF voltage) since it's a PITA to have to reflash the ECU for each adjustment, I think last time it took 12 flashes, this time I'm hoping for 2 or 3. For street tuning I've found it far easier to leave most of the fuel table near 100% (+/- 5 throughout) and make most of the changes to the K and MAF table instead, even for boost...without deep log analysis this is very time consuming. The less you mess with the fuel tables the more stock-like our VQ's behave..
I see, that explanation is a lil more clear. I actually set all my cells at 100 and only tune on k multiplier and MAF tables. Fuel comp is the last thing that the ECU looks at to trim fuel. Once I stated doing that air fuels were smoother and trim in quicker. I have a few drive cycles that i run through the MAF volatge to get all the ST trims within 5%.
I like his though....lil autotune feture and would def help alot of end users out!!
01-15-2011, 05:42 AM
#10
^^ Exactly... I started out with the tool to help 'autotune' the MAF.... which is still the main thing I'm using it for.
But since I was already parsing all that other data just to get to the little bits I needed, why not have a 2D table as well that lines up with the fuel/timing tables and cram all kinds of data into it. I need to separate some data (timing, A/F, cams, ect) into different tabs, it's getting pretty 'busy' as it is now all on one table.
And as soon as uprev starts logging Knock, the 2D representation will show exactly where it's happening on the timing table, ect.
But since I was already parsing all that other data just to get to the little bits I needed, why not have a 2D table as well that lines up with the fuel/timing tables and cram all kinds of data into it. I need to separate some data (timing, A/F, cams, ect) into different tabs, it's getting pretty 'busy' as it is now all on one table.
And as soon as uprev starts logging Knock, the 2D representation will show exactly where it's happening on the timing table, ect.
Last edited by djamps; 01-15-2011 at 05:44 AM.
01-15-2011, 10:23 AM
#13
Pretty much... and by adjusting the filters you can see short or long term or anything else you want to see averaged out over the course of the log file. For example, I could set tps-v minimum at 4v and it will show only WOT data averaged.
Last edited by djamps; 01-15-2011 at 10:27 AM.
01-15-2011, 03:59 PM
#14
New Member
Fantastic!
Being in a place were no one has heard of Osiris means I do all my own tuning.
I had talked about something like this to a friend who is a software engineer a few months back and ive done nothing about it since, props to you for being a
Do'er and not a talker lol
Well done!
Being in a place were no one has heard of Osiris means I do all my own tuning.
I had talked about something like this to a friend who is a software engineer a few months back and ive done nothing about it since, props to you for being a
Do'er and not a talker lol
Well done!
01-17-2011, 08:57 PM
#18
I am using the Haltech currently but I do have Osiris tuner on the backburner, just in case it ever improves to the point where I feel like trying to use it again.
Props to you for doing something that Uprev should have done long ago.
01-18-2011, 08:19 AM
#19
Although UTI was part of my inspiration, I have to say that UTI is a pile of crap and almost useless because of bugs/instability. The author also never once responded to my concerns either on the forums or by email.
By the way, this tool could easily be adjusted to work with any platform's log file, all I would have to do is adjust the regex array and delimiter that parses the csv header to find what it wants. Some extra work would be needed in the case of Haltech, since I don't think it works on MAF voltage or fuel schedule.
By the way, this tool could easily be adjusted to work with any platform's log file, all I would have to do is adjust the regex array and delimiter that parses the csv header to find what it wants. Some extra work would be needed in the case of Haltech, since I don't think it works on MAF voltage or fuel schedule.
Last edited by djamps; 01-18-2011 at 08:22 AM.
01-18-2011, 09:12 AM
#20
Although UTI was part of my inspiration, I have to say that UTI is a pile of crap and almost useless because of bugs/instability. The author also never once responded to my concerns either on the forums or by email.
By the way, this tool could easily be adjusted to work with any platform's log file, all I would have to do is adjust the regex array and delimiter that parses the csv header to find what it wants. Some extra work would be needed in the case of Haltech, since I don't think it works on MAF voltage or fuel schedule.
By the way, this tool could easily be adjusted to work with any platform's log file, all I would have to do is adjust the regex array and delimiter that parses the csv header to find what it wants. Some extra work would be needed in the case of Haltech, since I don't think it works on MAF voltage or fuel schedule.
In my limited experience, the Haltech GUI and Datalog viewer are the best I have ever used.
In most cases (including mine) the Haltech load reference is MAP. I have always been curious about getting a PMAS and changing the load reference to MAF though...
Last edited by mx594; 01-18-2011 at 09:13 AM.
