Trimalizer

Just wanted to say that trimalizer is an awesome program! With it I am able to combine multiple logs and filter data. I even figured out how to use it with HP tuners. I could not find another way to combine logs. I can't believe that as nice as HP tuners is, and can filter and all that, there is no way to combine logs together. While it takes a little time and effort to ready my .csv exports from HP Tuners, it is way better than trying to tune after each log. And gives a better average of conditions to the logs to tune to.

Any way, Thanks it is appreciated!

Only if I didn't have to mess around with the exported files.

glad you like it. it's one of those things i wrote without ever really using it myself, just because i figured it needed to be done.

so for your particular csv files, is it just column names you have to 'mess around with'? i did think that out and it's easy to customize the autodetected field names by creating a simple custom dictionary.

http://fbodytech.com/trimalyzer/trim...220enabled8221

you can get the dictionary file from the source code (see trimalyzer download page)


if it's something else let me know and i can probably fix it for you. or fix it yourself, it's open source and builds with QT (totally free)

Steavo,

I don't know if it is anything that can be changed on your end or not. I certanly am not qualified, I just learned how to use spread sheets almost enough to get by in the last year. I think it's more of a deal with HP tuners, but if you could make a change that would help, I would be extremely grateful!

Any one who is not using Trimalizer is missing out in my opinion, including you Steavo.

Hear is what I have to do to use my HP tuners Logs with it.

First I have to delete a bunch of lines so it sees the channel names I would expect to see. If I don't it either doesn't recognize it, or just shows the channel number. Thats not a big deal, easy enough to delete a few lines. The main part I don't like is the fact that HP tuners does not put out math perimeters in the CSV file. I have my Wide Band Connected to my egr signal and use a math perimeter to define it. And another math for AFR error. So I can use the spread sheet to do the math from the voltage info in the log, just takes a while to do it for each log. Nice thing is if I call the AFR error "BLM" trimalizer sees it as fuel trim.

Another thing I have to do, I don't know if it is just because I'm working with a Vortec Black Box, or HP Tuners in general, But the CSV only has manifold pressure as PSI. So I have to set up a math for That in the spreadsheet for each log. Again I call it "MAP" and trimalizer sees it.

With all that Monkeying Around, I still rather use Trimalizer than The "Built IN Filtering" of Hp tuners. And it is worth a lot to me to be able to compile logs. Something I can't believe isn't more important to others.

Steavo, Thanks again. I might pay for a few beers for you on your website.

IF there was a way to add a few math equations in trimalizer, I think it would be a 100% truly universal tuning tool.

i kind of wanted to make it work for most common ECMs without actually having to worry about math or anything

it's supposed to be kind of automatic but when you load a CSV log that is weird like that obviously it wont know what's going on.

the first line should be column names ,and all others should be data

do all hptuners logs look like that or are they different depending on export options or different ECMs?

the easiest solution might be to detect its format and just do a quick conversion when you are loading the files. i did the same thing for ALDLDroid and scan9495 as they did not have normal csv exports either

I just reviewed a few log I had from a 2004 Silverado. Looks pretty much the same in the csv. Still no kpa exported, only psi for the manifold pressure. Same line spacing with the header. Seems kinda weird to me that the MAP is exported that way, in VCM Scanner, it shows up as KPA.

Wish I could just log with tunerpro, but I haven't found any thread with a working ADX for black boxes, or even XDF's. Seen a few XDF's for 0411 and such, but I haven't seen any ADX's. I would buy an ELM327, if I knew where to get an ADX.

Thanks

I tried to up load a couple of logs I had, but the forum didn't let me. Don't know if anyone has worked with hp much, but log files are .hpl

VCM Suite is a free download from them, I think you can view someone else's logs without a license, you just cant log your own, or tune.

Let me know if I need to figure out how to get a log to you if that would help. I might be able to upload one on Google Drive and use link sharing or something.

Quote:

---

Originally Posted by steveo

glad you like it. it's one of those things i wrote without ever really using it myself, just because i figured it needed to be done.

so for your particular csv files, is it just column names you have to 'mess around with'? i did think that out and it's easy to customize the autodetected field names by creating a simple custom dictionary.

http://fbodytech.com/trimalyzer/trim...220enabled8221

you can get the dictionary file from the source code (see trimalyzer download page)


if it's something else let me know and i can probably fix it for you. or fix it yourself, it's open source and builds with QT (totally free)

---

Knowing almost nothing about computer language or coding, I decided to see if I could understand anything with the source files. The links to github on fbodytech don't seem to work.

its on the trimalyzer download page. i took my github page down years ago.

if you're interested in writing for trimalyzer or any other project on fbodytech you would also want QT Creator (open source version) it's free and has everything you'd need to edit and build anything on there. it's a really great free package.

but if you don't know any C or c-derived languages it would probably be more efficient for both of us if you documented in total detail the changes that need to be made to make the files work with trimalyzer, and then i make the changes to spec

the first log that's loaded is considered the 'master' log, and all further logs are required to be in the same format.

the code that gets the header is really weak and simply assumes the first line is the header. i put a workaround in there so if there are less than three columns in the first line, it uses the second line instead. it's not very smart because most logging tools would output in a sane format so we don't have to worry about it.

in your case i'd say the log format would be unique enough where we could 'detect' that we're working with one of these logs and then run a slightly different loading routine.

for starters so we can get some 'detection' working, can you confirm that all hp tuners log files start with the following text:

"HP Tuners CSV Log File"

and then two lines past "[Channel Information]" is where the column header is?

i can assume that from your screenshot but i need to make sure they're all like that. is 'channel information' always there in that location?

Quote:

---

Originally Posted by steveo

for starters so we can get some 'detection' working, can you confirm that all hp tuners log files start with the following text:

"HP Tuners CSV Log File"

and then two lines past "[Channel Information]" is where the column header is?

i can assume that from your screenshot but i need to make sure they're all like that. is 'channel information' always there in that location?

---

All HP Tuners CSV logs that I have been able to export do have that in line 1 - HP Tuners CSV Log File

Line 15 Is the OBD2 Channel number
Line 16 is the Channel Name
Line 17 is the unit measured

Log information starts on line 20.

The main "time waster" is that HP Tuners does not export any math perimeters created from info in channels, like tuner pro does, and for some reason Manifold Pressure is in Psi
I don't know if its just the OBD standard that only use psi, or not. Hp tuners scanner shows kpa, tunes are wrote in kpa.
If there was some way to use the user math formulas used in hp tuners, without opening each csv log file, and adding in the equation, that would be tremendous.



The options in Trimalyzer are top notch

Was just wondering if there was any piticular reason modify clip board doesn't work for the MAF table?


Thanks ��

i felt there were too many variables in how maf tables work (unlike VE tables which are pretty much all the same) and also smoothing to a certain curve takes a certain amount of manual intervention, so best done manually.

Quote:

---

Originally Posted by steveo

i felt there were too many variables in how maf tables work (unlike VE tables which are pretty much all the same) and also smoothing to a certain curve takes a certain amount of manual intervention, so best done manually.

---

Gotcha.

Anything going with header roconization?

Thanks ��

with who what now?

Quote:

---

Originally Posted by steveo

for starters so we can get some 'detection' working, can you confirm that all hp tuners log files start with the following text:

"HP Tuners CSV Log File"

and then two lines past "[Channel Information]" is where the column header is?

i can assume that from your screenshot but i need to make sure they're all like that. is 'channel information' always there in that location?

---

Sorry typo.
I was asking if there was any progress with the detecting of hp tuners logs.

Thanks

I should proof read.

i did get halfway there but am working on other things as well

can you email me a complete hptuners log to play with for testing

Email sent. :popcorn: