Tuning

Github phase-out

by

I’ve decided maintaining revision control on Github for the four open-source projects on this site (EEHack, Trimalyzer, ALDLIO, and ListDB) isn’t worth the effort.

These projects will certainly remain open source forever, perhaps even more open, as Microsoft’s ownership of Github and their questionable motives related to open source software could complicate things in the future.

When my Github page is gone, I’ll list current source tarballs on the download pages for each software package, and source code for past revisions will be available on request only.

Trimalyzer updated

by

I recently went and fixed (the totally broken) arbitrary input mode for trimalyzer.

What arbitrary input mode does is take a tool designed to analyze BLM trims and allow it to analyze ‘whatever’ vs rpm vs map.  I’d originally added it so people could analyze their wideband AFRs against their VE table, but you could really use it for a lot of things..

Willing to add other stuff to trimalyzer if anyone has any suggestions..

The EEHack user community

by

EEHack is still going strong, with nearly 10,000 downloads.

If you use EEHack or want to use it (if you have an LT1 and an aldl cable, it’s a no brainer), you’re likely to have questions or problems of some kind….

Need help?  Have questions?  The best thing you’ll ever do as an LT1 tuner is register for the forum at gearhead-efi.com.

That’s where the most experienced EEHack users and LT1 hackers hang out these days, and it’s a great forum.  There’s a lot going on there.

I’m still around to help with EEHack, but there’s an entire community of people over there that might be able to take care of you.

Posting replies to posts on here isn’t likely to get an immediate response, as I have a lot going on these days and don’t have much time to deal with problems personally.

Forum phase-out

by

The small forum I created to help with EEHack support was never intended to generate much traffic… but it did, and it was mostly spammers and data harvesters.

Keeping spam out takes too much time, so I’m going to phase out the forum.

If you need support for EEHack, Trimalyzer, or other stuff on this site, I’m only too happy to help, email me.  My email address is in the about screens of my programs.

Or better yet, just talk to the guys on gearhead-efi.com (I frequent that forum too)

I’ll move all of the EEHack FAQ questions somewhere else on the site.

2017 Status

by

Just a note to say hi to those who visit this site, and use all of the tools I’ve written such as EEHack and Trimalyzer, so you know I haven’t given up on you.

I haven’t owned a GM fuel injected vehicle in some time now, I drive an old bone stock Toyota these days, and focus my tuning on my bikes, but I’m definitely interested in maintaining the resources on this site, and making small updates and bug fixes to the software.

I’d also like to express my appreciation for the continuing donations made by the loyal users of my software, who have validated my original model of totally free software for LT1 hobbyists.

A voluntary donation model does actually result in some reasonable income, there’s no need to charge for software.  I feel good that nobody has ever had to steal EEHack from a torrent site and maybe get a virus, and that all users are able to access it regardless of whether they can afford it or not, while many people who feel I deserve it definitely end up paying their share to compensate me for my time, and after the few years I’ve been working on this stuff, I do feel that I’ve been more than fairly compensated for all of the time (many hundreds of OCD programming/testing hours) I’ve put in.  So thank you!

People tuning LT1s definitely should join gearhead-efi.com, as that’s where most of the decent antique GM tuners still hang out.

Thanks everyone for your support, flying the LT1 flag, and good luck with your projects.

If there’s anything I can ever do, just ask.

scan9495 and Trimalyzer

by

scan9495 users may have noticed that their logs couldn’t be loaded into trimalyzer.

This was due to a scan9495 (probably accidently) using an odd line ending char that is generally only used on old mac operating systems.

I’d emailed GaryDoug (the author) and he fixed it promptly with an update.  What a guy!  Users of scan9495 please download the updated version.

Integrator Bug in Trimalyzer

by

Previous versions of Trimalyzer didn’t really work with INT values very well, since I completely botched a conversion (missed a move from 100% to 0%)

The latest version (1.0b+) fixes this issue.

Users of previous versions should open the ‘advanced settings’ dialog and ‘reset to defaults’ to fully correct the issue as well…

Trimalyzer Evolving

by

Trimalyzer is working very well these days.

It supports multiple trim input and output formats, alters tables copied to the clipboard, has custom table definitions, diverse dictionary support, and can even analyze non-trim log data such as wideband AFR.

Might be time for you to give it a shot