Wanted: Dead, dying, or spare LT1 ecms for eehack development. Please email me (address in EEHack credits) if you have anything laying around…
Looks like the version of my old aldl-io console aldl program for linux was broken. I’ve uploaded a new version that should build properly and updated the instructions, please let me know if that works.
The analyzer in 4.9 had a glitch related to the new size of the VE analyzer. 4.9.1 is on the download page and fixes that bug. Thanks to all that reported it
Well it might not be perfect, but it’s better than what we had before (and it’s been AGES since I’ve released a new version) so here’s a fresh new official “somewhat stable” version of EEHack.
I really want to get it out there so I can start working on more dramatic features for the next version, and also prove that EEHack development is not dead.
I’d highly recommend updating to this new version for higher connection stability, better analysis, and better adapting to modern operating systems with different pixel densities and user interfaces.
Download it here: http://fbodytech.com/eehack-2/download-eehack/
Another new beta version of EEHack. Still a little bit to do, but we’re getting closer…
Download here: http://fbodytech.com/files/eehack-beta4.84.zip
If you’d like to try my next attempt at EEHack’s new version, this one plays around with the user interface a bit more (the last one didn’t scale very nicely). Added a small button near the ‘about’ button that enlarges the dashboard and main interface for full screen while driving (a bad idea, of course). Also rewrote some old code related to log playback that could cause crashing in some circumstances. As a bonus, playback speed is now variable.
Please let me know how it works for you!
Another quick update, this one makes the graphing work properly again, makes the UI look a bit nicer (missed a library in the last release..) but I also re-implemented the dashboard’s caching engine so processor use should be reduced dramatically. Thanks to Mitch for the quick testing. Please let me know how it works for you!
If you’d like to preview the next version of EEHack, here you go. Includes source. I think it’s quite an improvement over the last version both in interface and stability
Here are some of the changes
Combine the launcher and datalog window as the primary window, I always liked it better that way
Major UI overhaul to fix scaling and performance issues with dashboard and other modules
.. Use more dynamic layouts in most areas
.. Analyzer and autospark not done yet, but still functional
Ensure packet checksums are actually checked everywhere
Allow multiple graphing windows to be opened at once (just click the graph button again)
Add timestamp to moouseover of each knock event in analyzer
Fix a bug that prevented the ‘bad checksum’ override for bin reading to fail
Fix colored field indicator operation in dashboard for high/low conditions in the definition file
Fix hard crash when selecting custom dashboard parameter with no parameter selected
Code cleanup to fix compliation with newer QT versions
Maybe fix a bug that causes flash write to fail sometimes (initial connect timer)
Allow multiple log selections in the load log dialog
Dropping github RCS so remove references to it in ‘about’ dialog
Fix minor bug that prevented settings from propogating to the dashboard
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.
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..