need help reading ecu
Well maybe next time
BTW: I also tried to read without turning ignition on the first time ecuflash surgested it. Then i read again this time with the ignition on, and then it worked.
I have no idea if it works, I am just throwing ideas that worked for me.
BTW: I also tried to read without turning ignition on the first time ecuflash surgested it. Then i read again this time with the ignition on, and then it worked.
I have no idea if it works, I am just throwing ideas that worked for me.
try instaling, uninstalling, then reinstalling many times on three different computers. they all give the same code. the only thing i havent been able to do is revert back to 1.28 what i was origanaly running. i dont have that caopy nor can i find it for download
"no response to and known code"
"no response to and known code"
Start laptop
Hook up the cable to the car and then the USB (make sure the cable is on the whole way and the white plug is in as well)
Open Ecuflash
Read ECU
Make sure the key is to the on position with the car off. Make sure that EvoScan isnt trying to run (if it is you wont have the read from ECU button highlighted in blue in ECUflash).
If the ECU is possibly locked, open ECU Unlocker before ECUflash then go through the steps.
The last step is take it to a local who has experience with ECUflash and see if there is anything that you arent doing. It sounds like you have the process down, but why its not working is not directly obvious. You are using the correct inherited ROM type for your car as well to download...right? In this case when it sends the prompt screen, you are using the 2006 Evo IX Evo9Base?
its worth a try incase the pin in the white connector has come loose or something.
thanks for al your help guys, but none of your suggestions are seeming to work. im going to send my ecu to TTP and have them try reading and loading the tune there. thanks again for all the help.
Thanks
TTP
I have this exact problem! Nothing I do is working! I grabbed my flash once after downgrading from 1.34 to 1.29a. Haven't used it for a week and now it's spitting those same error codes out. Weird thing was I started the car, then read my ROM (which immediately shut the car off) and it started downloading the ROM then, but then ran into an error and timed out. What the heck is going on here?
Can somebody please help? This cable has barely any use on it. Is this not a widely documented problem? One person has an issue is just a blip on the radar, but 2+ one should start taking notice! OP, did you ever fix this problem?
I think there were issues between the old and new cable. just go back to 1.34... ive been using it without any problems.
did you make sure that you completely uninstalled all the parts of the ecuflash you had prior? I had problems with taht, but not like what it sounds like you are having.
why the jump back in versions? dll?
p.s. there is always the big/little endian issues between the 2 as well...
its wierd. I neverhad problems with 1.3, then 1.31 came out and i tried that, problem city...1.34 out and i havent had any problems whatsoever.
did you make sure that you completely uninstalled all the parts of the ecuflash you had prior? I had problems with taht, but not like what it sounds like you are having.
why the jump back in versions? dll?
p.s. there is always the big/little endian issues between the 2 as well...
its wierd. I neverhad problems with 1.3, then 1.31 came out and i tried that, problem city...1.34 out and i havent had any problems whatsoever.
I believe I have an older Tactrix cable and was told that it only works up to 1.29a. I had 1.34 installed at the time and once I downgraded it worked great to download the ROM that was on there. With 1.34, it would just give me a "can not connect error." This was about 2 weeks ago. Fast forward to a few days ago and I'm throwing the hex codes above on 1.28, 1.29a, and 1.30. I uninstalled and deleted the OpenECU folder each time and used the drivers associated with the proper versions. All cables look secure and I can use OBD Scan Tech to view parameters. I am throwing a P0122 (low TPS voltage) CEL that I can't seem to delete now though. I think that's unrelated to this though. More related to the BISS screw in the TB.
Last edited by silex; Mar 20, 2008 at 11:03 AM.
^hmmm...
i dunno, man, it sounds like your ECU is just not allowing the init sequence. you have 8859013, right? can you flash at all? maybe try putting -15 on there? ...you think that would even help?
p.s., you might also want to check the continuity on the MUT plug... thats where the Init sequence starts, iirc.
i dunno, man, it sounds like your ECU is just not allowing the init sequence. you have 8859013, right? can you flash at all? maybe try putting -15 on there? ...you think that would even help?
p.s., you might also want to check the continuity on the MUT plug... thats where the Init sequence starts, iirc.
HAHA. We'll see what tonight brings me. I can't do anything...I have a nice flash waiting to be uploaded, but it's doing me no good since I can't download, upload, read, write....blah.








