scan9495 and Trimalyzer

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

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…

New Analyzer

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.

This will…

  • … 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:

http://www.gearhead-efi.com/Fuel-Injection/showthread.php?6303-Narrowband-Tuning-Tool

EEHack 4.8 Beta

New beta version..

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

EEHack 4.7 Release

Released the latest version as 4.7 (forget that minor version stuff!)

More stable, better tooltips, more settings, etc.

Download it now!

  • 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