This does get asked a lot, so please check the FAQ topic out before contacting me about connection issues.
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 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.
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…
I’m writing a new fueling analyzer, similar to the one used in EEHack.
Such an analyzer allows you to load massive amounts of log data, and generate a map of reasonable fueling corrections to be applied to a VE or MAF table.
Right now, this is commonly done on hand-made spreadsheets, which lack advanced filtering and are difficult for people not familiar with spreadsheets.
Basically, a good BLM analyzer will almost ‘auto-tune’ most regular driving ranges. EEHack users already benefit from this, and my new program will allow everyone else to do it.
- … be a standalone program
- Work with CSV log files from ANY sane datalogging software, including tunerpro, scan9495, and datamaster.
- Be a one-click solution for common configurations, or very easy to adapt to uncommon masks and logs
Stand by as I get a beta ready, and watch this thread:
EEHack is written on top of a C++ library called QT, allowing me to develop new features rapidly, support Linux and Mac OSX, and program things in new and interesting ways. It’s also a great way for people to develop programs that aren’t accustomed to writing GUI software.
Almost by accident, I’ve found that Windows XP is not supported by versions of QT later than 5.6.
This means that if I use the newest QT library, and I do like to keep things updated, EEHack will stop working with Windows XP entirely. The new beta, for example, is built against QT 5.8, and refuses to start on Windows XP.
On one hand, Windows XP is now over 15 years old, and EEHack is a fairly modern program, so part of me doesn’t care, but I personally have an XP netbook I use for tuning, so I do feel the pain of people with old hardware. Hell, you can’t even get a decent web browser for XP anymore.
I have several options I’m considering:
- Drop support for Windows XP and stick with current QT versions, also dropping some of the specialized compiler flags necessary to be compatible with XP. This may result in a more stable EEHack? Or maybe not…
- Stick with QT 5.6 forever, and any improvements in QT be damned. This is the safest option…
- Release builds against BOTH versions of QT. This is more work for me, but it’s possible for me to automate the process:
- In one gigantic installer that selects the correct version itself. This would be a fairly large package and irritate both users since fbodytech.com’s upload speed is not awesome
- In separate installers and make the user choose. I’m sure to get weekly inquiries about which version to download despite me labelling them clearly.
If we do choose option one, all hope is not lost. Anyone can download QT with QT creator and compile EEHack themselves. This is kind of what my Linux user base is doing since I stopped releasing binaries for Linux, and it works alright.
Any opinions, please do comment.
Does this matter to you? Do you still use XP? Why?
Not many changes, mostly some fixed up tooltips, but now we dump the results of the flash log to the debug window.
When a flash write goes bad, it would be nice for me to be able to get those logs so I can help figure out what happened, but most users find the window is closed with no way to get that information back.
Also added a help button that directs you to the support forum.
Would appreciate some people testing flash write in this beta and ensuring everything shows up in the debug log…
EDIT: Now on second beta, compiled against a new version of QT