EEHack 2019 update

[JackOfAllDaves]

Hi Steve, Im brand new to this forum only minutes after downloading your $EEHack software. I am a semi retired old guy, closed my shop in 1986. Since building my dream shop two years ago, ive attracted a few customers, this one a 1996 Camaro SS Z28 with a 16214399 ECU. We had to rebuild his stock LT1 motor into a 383 Stroker kit by Eagle. Consequently, I had to furnish it with PaceSetter headers, thus a myriad of changes to displacement, fuel management, o2 sensors, and deletion of Air Pump, etc.

I am expecting to spark it up first time tomorrow. I almost ordered in a HP Tuning kit for $399 from Summit, but I may never see one of these again, who knows? Can you help me? Is your $EE software compatible with reprogramming, flashing the EEPROM on this unit? I was a network analyst computer guy for 25 years, so I would enjoy doing this. I don't have any ALDL cables or anything yet, so some direction would be helpful. Look forward to hearing from you or anyone else on this thread. Cheers!

[steveo]

nope. you’d need to swap to a 1994-1995 16188051 ecm

[NomakeWan]

That sounds awesome! Especially being able to apply the changes to the bin directly for MAF stuff. VE is already easy as heck, if MAF were that easy...WEW.

[steveo]

here's a new beta. the analyzer ui is getting better. i've matched the ve analyzer to the actual ve table size (a common request) which will make this bin changing thing a lot easier.

http://fbodytech.com/eehack-beta-4-8-4/

implementing the changes directly to the bin is sketchy for sure. still not sure if i'm going to do kur4o's maf thing in this release or not. i'm not sure how much babysitting to do. i'll get a prototype and you guys will have to see how it works out....

[steveo]

i've come to a decision, no more new features in this beta. there are too many important improvements in here to wait for release any longer, such as checksum calcs.

if you guys are okay with it (PLEASE FIND MORE BUGS) i'll make it the new 'official' version while i start the next version.

the next version will have some more serious changes that'll need more testing...

first off i'll add tuning functionality including kur4o's MAF patch along with a user interface and automatic bin tuning (but a bit different than he's been thinking, i think i will only enable it in my alternate 'speed logging' datastream message).

the goal will be to allow someone to log a bunch of driving, click a button, and instantly have their MAF recalibration complete outside of power enrichment range with no playing around (assuming healthy engine and o2 sensors). i think new tuners will really appreciate this one. i'll force a bit of curvature in the result and reject delta TPS events as suggested to ensure accuracy. automatic VE tuning will also be done and it'll be smart enough to know if we're in speed density not to tune the maf (or tune VE if we're using maf metering)

this stuff wont be hard to pull off but i need to spend quite a bit of time testing it thoroughly as one wrong move and i'm writing crap outside the table in question and silently borking the bin. the VE table is split too so i need to figure out the best way to manage that 2000rpm shared border.

even bigger than that is i've been looking at the flash routine and i have some ideas. i can make it much more safe and recover more gracefully with all of the things i've learned since i've written it. i'll add an advanced mode so the user can manually control the procedure, do better tracking of the current ECM state and handle responses from the flash kernel better, and guarantee continued execution of the flash kernel until successful or quit, so unless we drop power from the ECM or the chips wont erase anymore, persistence will eventually succeed. right now in some error states, it goes to reset the ECM which is a really dumb thing for me to have done in hindsight. i'll have to add some controls in eehack to allow jumping into an already executing flash kernel, right now it wont do that and that's a huge limitation.

the other thing i want to do (probably need kur4o's help....) is to write a recovery image that's as small as possible, that allows us to get the flash routine up and nothing else. that way if a flash becomes sketchy and the entire bin can't be written, we have something to write in as few blocks as possible so the ECM isn't bricked and can be repaired once we figure out what's wrong. another alternative idea although not sure how well it'll work would be to write things in a very specific sequence so executable code gets written first, and tables and 'engine running only' code get written last to increase chances of a brick being recoverable if we just bail out.

i will need to rebuild my test bench and find a (maybe socketed) working ECM to develop the flashing functions. actually something with fried injector or fan drivers would be idea since it'll never go into a car. anyone have a loaner i can borrow for a few months? otherwise i'll just buy something on ebay and sell it later.

[Terminal_Crazy]

Evening Stevo

Just downloaded v4.84
On the front page it shows v4.80 (Pre-release)

Also, I guess it's a QT issue, Is it possible to be able to Copy & Paste data from the Analyzer tables as I track & record changes.
or save the Analyzer pages out into a text file, similar to the way notes are saved ?
or saved out with the notes.

Requests for the next version:
Additional Wideband display on the main page as you have left a space for it.
Wideband display AFR / Lamda toggle.

Does the Knock warning button work? I've never seen the screen flash.

Oh yeah, and the secret 100HP boost code button... I need that for Christmas to upset the LS fanboys.

Pretty damned sweet otherwise my friend.

Thanks
Mitch

[steveo]

i can work on copy paste tables for next version

knock warning has been broken for a long time

dual wideband display could happen but low priority

[NomakeWan]

Tested 4.84 on the way to work. Fixed the speedlog bugs from the previous version, both on the dash and in the analyzer! Honestly it looks great. Thank you again.

Can’t wait to test out the new flash routine once you figure it out. I look forward to being able to flash troublemakers like my ‘94. Keep on keepin’ on!

[kur4o]

Nice ideas Steveo.

The best improvement will be to keep the flash routine indefinite in the pcm and continue from there with new aldl cable and PC in case some of these fail midflash.

For a mini bin version you need the last 64 bytes programmed correctly for anything to work. These are the pointers for reset and some of the other interrupts. We can change them all to point to mode 5 loop, but have no idea if it will work. The pcm might need some of the config routines executed at reset.

[steveo]

i really like the idea of a nonvolatile recovery image we write first. i wonder if we can temporarily create a rebootable failsafe loop with an exit by jumping to a 16 bit address ending in FF and the last thing we do is write that ff to the new address...? or is there a better way? test for a byte we set last and loop if its FF ?

[NomakeWan]

Not sure if it's my end or something else, but figure I'll point it out. In 4.84 (and possibly older versions, I haven't tested yet) with the latest patch, if I try to snapshot E-Side I get an error. If I try to stream E-Side the error counts just pile up. No Data is all that gets displayed. This happens whether the car is running or not. Is this expected behavior? I've never bothered with any E-Side stuff, but I poked at it while sitting in my driveway and noticed this, so I figure better to bring it up than not.

[steveo]

if patched it should work with engine not running however the error might be because there's no actual datastream definition for the e-side yet.

[steveo]

alright screw it i'll just release this new version so everyone can roll with it

i'll throw the hammer down on the next version once i reassemble my test bench

i'll call it 4.9 because it' been so damn long since the last release!

http://fbodytech.com/eehack-4-9-release/

[steveo]

4.9.1 is now on the download page and fixes a small bug i missed in the new VE analyzer

[NomakeWan]

Found another bug today. If you attempt to run the cylinder balance test while Speedlog is enabled, EEHack crashes completely.