RAX Fast Logging
I finished up my Standalone -> Evoscan log file convertor. Sent a copy to Rich for initial testing and observations.
It parses the "time" column and turns that into valid "LogEntrySeconds"."LogEntryDate","LogEntryTime " columns and appends them to the log file.
It runs as a batch job on all the files one level above it's exe. Just toss the folder on the Tactrix and when the EXE is ran it will convert all the standalone logs without destroying the original. Then those will open up without any other work in Evoscan.
Once I get some feedback I'll consider release here. It's only 2.3mb.
It parses the "time" column and turns that into valid "LogEntrySeconds"."LogEntryDate","LogEntryTime " columns and appends them to the log file.
It runs as a batch job on all the files one level above it's exe. Just toss the folder on the Tactrix and when the EXE is ran it will convert all the standalone logs without destroying the original. Then those will open up without any other work in Evoscan.
Once I get some feedback I'll consider release here. It's only 2.3mb.
I finished up my Standalone -> Evoscan log file convertor. Sent a copy to Rich for initial testing and observations.
It parses the "time" column and turns that into valid "LogEntrySeconds"."LogEntryDate","LogEntryTime " columns and appends them to the log file.
It runs as a batch job on all the files one level above it's exe. Just toss the folder on the Tactrix and when the EXE is ran it will convert all the standalone logs without destroying the original. Then those will open up without any other work in Evoscan.
Once I get some feedback I'll consider release here. It's only 2.3mb.
It parses the "time" column and turns that into valid "LogEntrySeconds"."LogEntryDate","LogEntryTime " columns and appends them to the log file.
It runs as a batch job on all the files one level above it's exe. Just toss the folder on the Tactrix and when the EXE is ran it will convert all the standalone logs without destroying the original. Then those will open up without any other work in Evoscan.
Once I get some feedback I'll consider release here. It's only 2.3mb.
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Why don't you two swap email addys, swap notes, and combine the two projects!
That way, we'll have a single utility that "unpacks" RAX DAT packages into convenient .csv EvoScan-readable files... one click does the whole SD card.
Rich
That way, we'll have a single utility that "unpacks" RAX DAT packages into convenient .csv EvoScan-readable files... one click does the whole SD card.
Rich
I'm pretty much feature-complete with my first iteration of the LogFixer. Basically ready to release something here for you all to play with shortly.
It also allows rules to filter out logs into other folders when certain conditions are met. For example when "KnockSum > 1 and Load > 100" the rule will match and move a copy of that converted log into the rule's folder.
The rules are configurable and multiple rules are supported. So you can sort logs by various events pretty easily now. I use two rules personally, "Load > 270" (overboosting for my tune) and "KnockSum > 2 and Load > 100" which tells me about any 3 counts or higher above 100 load.
Now I can leave the Tactrix in the car for a week's worth of daily driving, bring it inside, plug it in, and in 2 minutes I'll know if any one of my 50+ new log files has something I should be looking at. If I *do* need to look at something, the EvoScan compatible file is already inside the rule's folder for my perusal.
My problem with logging all the time was accidentally missing a 4 count somewhere in boost or something...... I want to know about that without scanning the files manually one by one!
I'll write up a PDF and find somewhere to host it. Roughly 2-3 megs zipped up.
It also allows rules to filter out logs into other folders when certain conditions are met. For example when "KnockSum > 1 and Load > 100" the rule will match and move a copy of that converted log into the rule's folder.
The rules are configurable and multiple rules are supported. So you can sort logs by various events pretty easily now. I use two rules personally, "Load > 270" (overboosting for my tune) and "KnockSum > 2 and Load > 100" which tells me about any 3 counts or higher above 100 load.
Now I can leave the Tactrix in the car for a week's worth of daily driving, bring it inside, plug it in, and in 2 minutes I'll know if any one of my 50+ new log files has something I should be looking at. If I *do* need to look at something, the EvoScan compatible file is already inside the rule's folder for my perusal.
My problem with logging all the time was accidentally missing a 4 count somewhere in boost or something...... I want to know about that without scanning the files manually one by one!
I'll write up a PDF and find somewhere to host it. Roughly 2-3 megs zipped up.
Last edited by acidtonic; Dec 17, 2012 at 10:14 AM.
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Please see the important notice in the RAX Patch main thread.
Will update here when more is known. Right now, we don't know all that much.
UPDATE
In December, there was a worrying cluster of people with flashing issues. But it was simply a cluster - no single cause. So nothing to "fix" anywhere. All good.
Cheers,
Rich
Will update here when more is known. Right now, we don't know all that much.
UPDATE
In December, there was a worrying cluster of people with flashing issues. But it was simply a cluster - no single cause. So nothing to "fix" anywhere. All good.
Cheers,
Rich
Last edited by richardjh; Jan 22, 2013 at 08:54 PM.
Evolved Member
Joined: Jun 2009
Posts: 653
Likes: 12
From: Houston, TX
Somehow my IAT xml line disappeared. Apparently I underestimated the importance of Rich's back up statement. Can anyone paste up that xml line so I don't have to do a full re-install? I can't seem to locate just the RAX xml for evoscan anywhere. Thanks.
I just updated Ecuflash and the firmware on my OP device. The changelog shows tons of logging updates so I'm excited to see if I can grab the data packages faster or easier now. Hopefully I can do some testing in the next few days before I go back to work.
BTW I've had no issues with failed flashes but I never use Evoscan and Ecuflash at the same time. In fact I don't really use Evoscan at all except in simulation mode when I'm nowhere near my car.
BTW I've had no issues with failed flashes but I never use Evoscan and Ecuflash at the same time. In fact I don't really use Evoscan at all except in simulation mode when I'm nowhere near my car.
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Oh, that's cool. I saw that mention of better 32-bit logging in the EcuFlash release notes...
Are you getting faster 8 x 4-byte packages too, or is the rate about the same?
Rich
Are you getting faster 8 x 4-byte packages too, or is the rate about the same?
Rich
Would be nice if there was at least a little bit of documentation on all the options for the logcfg.txt file .. but there doesn't appear to be any whatsoever
Last edited by TravisF; Dec 30, 2012 at 10:39 PM.
