My new trim analyzer tool is ready for testing
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:
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
Apparently some of the B/D-body bins in the factory bin archive were incorrect.
Affected bins: 16207111, 16230221, 16230221, 16239511, 16243011, 16243021, 16243171, 16243931, 16243941.
These are fairly uncommon bins, but if yo’re a bin collector, you might want to check your list and download them again.
Not sure how, but the executable became corrupt for the automatic tuning service.
After a long wait, it’s fixed now. Thanks for your patience.
Released the latest version as 4.7 (forget that minor version stuff!)
More stable, better tooltips, more settings, etc.
- Fix bug that prevented ‘silence extra modules’ setting from working
- Fix bug that sometimes prevented ‘dump ram’ setting from working
- Stop counting errors during initial connection (unnatural serial events may be normal…)
- Allow crazy values in linear voltage to AFR mapping (for lambada or edge cases)
- Seperate left and right BLM values in the closed loop performance analyzer
- Fix some tooltips and stuff
- Parameter selector now defaults to ‘Extended’
- Add option to always draw the dashboard
- Tabs in settings to make room for more settings in the future
New beta version is out with a few small bug fixes and enhancements. Please help me test it!
Fix bug that prevented 'silence extra modules' setting from working
Fix bug that sometimes prevented 'dump ram' setting from working
Stop counting errors during initial connection (unnatural serial events may be normal...)
Allow crazy values in linear voltage to AFR mapping (for lambada or edge cases)
Seperate left and right BLM values in the closed loop performance analyzer
The big news is it connects to corvettes properly, and controls transmission line pressure and EGR duty cycle.
We need B-Body owners to help test connectivity on those cars (especially caddies)
Controls are now done in an ‘expert’ and ‘basic’ mode, so new users don’t have to be afraid of accidentally modifying line pressure while driving and breaking their car…
I’m sorry if I’ve deleted your account on this blog, please remake it. There were too many spammers to keep up with. I’ve added some basic GM-related questions to the registration form, hope it keeps the spammers away …
Things EEHack needs from beta testers right now:
– Review of the definition file for any other typos, mistakes, oversights, or things that could be re-labelled to make more sense
– Testing of B-Body connection stability, especially with a caddy
– Testing of EGR actuation
– More ideas for new swag!
You can help keep the project alive by contributing comments or ideas.
The new version will be out soon…