Is it the last EEX version and is recommended to use instead of steveos's from his website?
Printable View
Is it the last EEX version and is recommended to use instead of steveos's from his website?
they're the same now
i can't join the 60 degree v6 forum to try to get some new testers, it seems i never get a verification email.
if anyone has a membership over there can you make a post to try to find some more testers for the P66 flash tool?
does the set vin and calibration id thing work for the V6? i assumed the commands are the same..
Hey steveo, just wanted to let you know that I tested 0.5.9 on my '95 and yes, it fixed the T-Side recovery patch bug. Flashed without any issues. So that being the case, I tried it on my '94. Didn't change any settings, just loaded the new BIN and hit write. Worked absolutely perfectly. There was a weird repetetive clicking noise somewhere in the engine bay after the fans kicked back down that I couldn't trace because I was in the car with the door closed and wanted to stay that way, so I'm not sure what it was, but it didn't affect the process any. Despite the noisy bus, Flashhack had no issues flashing the car, and she fired right up afterwards. Now I have speedlogging on the '94 finally!
Congratulations, flashhack is amazing work. I hope the OBDII stuff works out too, it'd be amazing to be able to support the 96-97 LT1/LT4 cars!
the kernel does cycle the CCP solenoid
thats probably your clicking
been meaning to find out why
oh, is it stored on the eside or tside, though?
new version, played with the ui a bit. i realized that if you click the flash write button 10 times it tries to write 10 times, so now the ui handles the context of 'operation in progress' or 'operation finished' which has been built in from the start... no need to display any progress stuff it things aren't happening, right?
also bigger buttons for touchscreens etc.
set vin/calid imports existing values from the loaded bin too
like it or don't you know where to get it.
Tested it out on my '94, had to make some minor changes to my tune anyway. Worked perfectly, and I like the new interface a lot. Only tiny oops is that the title screen still says 0.5.9 but I mean...that doesn't affect functionality at all.
Being able to flash my troublemaker Corvette is awesome. Speedlogging has been great too!
yeah glad you got that working. higher sample rates were a great thing to attain for doing blm/wideband logging. i dont think a lot of people use it.
i did notice that i forgot to bump the version number...
im glad you like the interface, i feel like i know how to make a nice one but it takes a long time to figure out how to implement it so certain people can find the important stuff. i try to put myself in the mindset of a total computer illiterate person and put the most important buttons right there. it can lead to uglyness but way less support needed on my end.
Reporting back on my success with Flashhack_b0.5.9 on 95 B and F body LT1s.
Did full reads and writes as well as a selective T/E write - no issues.
Had a few minor suggestions - I see that two of them are already covered by b0.6.0 - pre-populating VIN and Cal ids. Still have to test changing these parameters.
For selective writes, an option to let the user specify the reference bin when the autosave doesn't match the PCM could be useful when the user knows the last bin that was loaded to this PCM.
Noticed this was in the $EEhack flash routine.
Took a quick look at b0.6.0 - nice clean interface. I will run some tests with it over the weekend.
Jim
thanks for the feedback and giving it a shot
can you explain when would this realistically happen, when it was flashed with a tool other than flashhack? or maybe a different computer? need a good use case to add yet another user input that could potentially screw something up if people don't use it properlyQuote:
For selective writes, an option to let the user specify the reference bin when the autosave doesn't match the PCM could be useful when the user knows the last bin that was loaded to this PCM.
the next version will fingerprint people with more than one LT1 to tune to allow the selective write function to work well
there is also a bug with the old eehack eside comms patch (disables the recovery rom) the next version will take care of.
will also remember last selected ECM type and allow user to switch at runtime instead of closing the program.
the code is done just need more testing
alright new version is up
- Remember last selected ECM as default because most people dont use it for more than one ecm
- Provide some fixes and a menu option to select a new ECM (so you don't have to restart the program)
- Add a workaround for the E-Side comms patch so the recovery rom works
- Add unique vehicle identifier to EE because nomakewan actually owns two LT1s for some reason
- Use .bin extension properly in save/load dialogs