I've tried 1.34 and 1.35 with the same results. It doesn't seem to be triggered by any particular action, the program will crash while completely idle and not even touching the laptop. It took 3 tries but I was able to download a ROM from my EVO IX with it. I sure won't be using it to try and write anything until I have this worked out. It doesn't give any error messages, Windows doesn't complain, nothing. The ECUFlash window just disappears and thats it.

Has anyone seen this? I'm sure it's something that I am running on this stupid laptop that is interfering but short of a complete format I'm hosed. I'm hoping someone has seen this before, although I did quite a bit of searching and came up empty. I'm hoping to save myself the frustration of a fresh Windows install.

 

for some reason sometimes during only the first logging the WB will register a stuck #. you stop the scan and rescan and it works. I havent' experienced a complete crash but maybe its the voltage or something. I know I had to start the car up becasue the voltage was to low for the ecuflash to work.
Maybe your connector is loose?

 

For Evo's you want 1.30 or less it seems.

 

I have very limited flashing experience but every flash that I have dont has been within the past month is with 1.35. I just got the cable at that time. I downloaded 1.35 casue that is what was available from OpenECU at that time. It has (knock on wood) worked for my everytime so far. I got an error the first time I tried to pull a ROM cause Ididnt click on the 2001-2005 EVO icon. I quess Im just lucky?

PS. John Bradley

If I were to send you my ROM would you do the Knock SES etc and disable the P0300 code in my ROM if I dont want a tune? I would pay of course. the ID is 9642008. IF you dont see this Ill Email you. Thanks

 

I grabbed 1.29 from a link in another thread here and it seems to work perfectly. The weird thing is that even if I didn't load an EVO specific ROM, or have my Tactrix cable connected it would still crash if I started it and walked away from the computer for a few minutes. I guess problem solved, unless there is something from 1.30-35 that is groundbreaking and cool.

 

The newer ecuflashes crash for me as well. It will lock up when trying to read from the ecu. I am and have been running 1.29 since it came out and it works great.