putting my car back together...will definently be using this program! Have before a few times and I bricked my pcm 1 time but it was due to bad aldl cable NOT the program! Love the software you developed, thanks for spending your time man!...side note. Where can I get a reliable cable for a 16 pin 95?!

 

any chance you want to part with one of those 200 cables? lol

 

I just tried writing to the PCM after a slight speedo correction tweak. The program called out a risk of it being a patched bin. Is this a reference to a region used by the 128 BLM locker and a couple other patches I applied from EEHack? In the past, I always got to the point of applying VPP voltage just before the write and that would fail. I even tried an Apollo 13 exercise to drop the KOEO load to nothing but PCM to see if that helped but it never worked, just got used to pulling the PCM to program it.

 

are you running the latest version? please do update and try again.

no reasonable patches should affect that, but maybe a version of eehack patch that i haven't tested (which really shouldn't be in your bin, those were supposed to be transparently inserted during flash write only...). what it's doing is comparing very critical segments of communication and boot code to a reference bin to ensure that everything looks normal for when we modify your bin so it'll be able to boot after only a few blocks are written.

if you have an EEB bin the eside recovery patch wont work but older versions didn't detect that case properly.

worst case is just go to parameters to disable the 'hardware recovery logic' for just the e-side... that logic is only for cases where ecm power is totally lost during a flash.

edit: if this persists can you send me a copy of that bin? my email address is in the about menu.

 

Problems are, they're all RS232, and none have OBD connectors (OBD1 or OBDII). I used to do a trade-in program for RS232 cables to upgrade folks to USB. I collected all these trade in units with the intent to sell them... never did. Now I don't have time to do it. I went back to school in 2011 and wound down the cable business in 2012 (sold all my stuff to Tunercat). Started school again in 2015, hopefully finishing the PhD this year. But short answer, naah, it's not worth it for either of us to buy one from me at this point. Thanks for asking tho.

 

go buy some 5 dollar ttl to usb board

throw rx and tx together for data to a paperclip
jam paper clip in aldl port

do the same with ground

you could put it in a fancy box but thats all an aldl cable is

reliable enough to do hundreds of reflashes with me hitting and disconnecting and abusing it on purpose

of course with flashhack your cable could catch fire and you could just go make another one

 

you make it sound so easy! too bad the cable I had would disconnect if the wind blew.

 

this should be really obvious but there'd be no problem with wind if you just left the windows rolled up and the doors closed

one other very solid way to go is to solder the thing in parallel with your aldl port (or in place of it) and mount a female usb port in your dash.

 

Sorry to comment and disappear, stuff came up and I was on the road. I'll double check on version but I downloaded whatever was on your site the day I posted. I'd be happy to send you the bin. I discovered how crappy it was a year or two ago and have started doing all the things a real tuner would do. Not to rant off topic but the sum of the tune was "make it fat and dial up the timing until it knocks and then pull it one or two back." I always thought I should have dynoed a tad higher than I did in 2009. There's more to do and it's a lot better now but again off topic...

I'll check the version I have and get newer if released since last week/ week before and try again and let you know. Meantime I'm sure you have contact info on your site and I'll get the bin to you if for nothing more than sake of curiosity.

 

if you need....there is a menu item in flashhack that opens a new email to me

 

Very late, but bin file sent a few minutes ago. Apologies for the delay.

 

i did get your bin and there is an anomaly for sure in the comms code. i have no idea why and no idea where your base bin came from. i wonder if it's been messed with by some odd tool i haven't played with like read back from a hypertech programmer or something. i did compare against a stock calibration. i'm unsure if the recovery patch will be safe to apply. if i were you i'd start with a new virgin bin and copy the relevant tables over, but otherwise just uncheck 'apply hardware recovery logic for the e-side' like i mentioned earlier and it should be fine.

 

i did find the problem with your bin and it's eehack's old e-side comms patch that we never really used.

things like this were why i made eehack's internal patches apply on write and never modify the bin on disk, so we could make more drastic changes to the bin as it's written and other tools you work with would never have to deal with the modified bin. it was pretty clear that when you use eehack's patches, you shouldn't read that bin back and play with it, which obviously you ended up doing.

anyway things have changed

you can unapply that patch in the latest EEX definition on my site if you want, it's called 'E-Side Diagnostic Comms"

 

the latest version now fixes the above issue (as far as i can tell)

 

So, I can just get rid of that patch and continue on? Or should I really start with the latest mask for a 94 M6 and merge the current bin, minus the EEHack patches? Perhaps I don't understand how to apply the patches like the BLM Lock 128@WOT. I may have been light on 'reading' and heavy on blindly 'doing' back when I applied the patches this bin has. I'll have a look at the newest version of EEHack. I'm going to guess the options are there for the flash routine to apply the desired patches during flashing without committing them to the .bin file uploaded to the PCM, if I understand you correctly.

 

nowadays eehack doesn’t flash or patch anything itself, and the patches are in my EEX tunerpro definition. this way all the tools can do what they do best. your bin is fine to use

 

there's a new version up with some bug fixes and ui improvements for anyone interested

 

if you're flashing the ECM and it fails, here's some tips to ensure you don't end up with a bricked ECM

http://fbodytech.com/flashhack-lt1-p66-error-recovery/