Issues connecting EcuFlash to Evo 9
monitor the voltage through evoscan! what 90zcrex is saying is a good way of determining the life of your battery also when load is put to it.
it will still log even though you cant read/write into the ecu flash.
also it has nothing to do with the ecuflash version Raziel. its the actual evo 9 ecu is very finicky with locking you out when the voltage is not high enough. happens on a lot of cars.
it will still log even though you cant read/write into the ecu flash.
also it has nothing to do with the ecuflash version Raziel. its the actual evo 9 ecu is very finicky with locking you out when the voltage is not high enough. happens on a lot of cars.
Thread Starter
Newbie
Joined: Apr 2004
Posts: 41
Likes: 0
From: Boston, MA USA
monitor the voltage through evoscan! what 90zcrex is saying is a good way of determining the life of your battery also when load is put to it.
it will still log even though you cant read/write into the ecu flash.
also it has nothing to do with the ecuflash version Raziel. its the actual evo 9 ecu is very finicky with locking you out when the voltage is not high enough. happens on a lot of cars.
it will still log even though you cant read/write into the ecu flash.
also it has nothing to do with the ecuflash version Raziel. its the actual evo 9 ecu is very finicky with locking you out when the voltage is not high enough. happens on a lot of cars.
Thread Starter
Newbie
Joined: Apr 2004
Posts: 41
Likes: 0
From: Boston, MA USA
*Update*
Ok so I tried my friends car and I was getting over 13 volts of power and it worked. Read my ECU and that was as far as I could get unfortunately. When I made an attempt to edit the ROM and write it into the ECU I got the same error once again;
[20:01:08.440] using metadata XML ID read_evo9 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[20:01:08.471] Using interface OpenPort 1.3 Universal TX2I2IXh0caea4c535d9b68f63ab24f3df87b15a869a1df6
[20:01:10.274] sending init sequence 1 (0001)
[20:01:13.540] sending init sequence 1 (0003)
[20:01:16.806] sending init sequence 1 (FFFF)
[20:01:19.556] no response to any known code
[20:01:19.556] interface close
I was still pulling over 13 volts as my friend's vehicle was still hooked to mine. Only worked once! What gives?!
Ok so I tried my friends car and I was getting over 13 volts of power and it worked. Read my ECU and that was as far as I could get unfortunately. When I made an attempt to edit the ROM and write it into the ECU I got the same error once again;
[20:01:08.440] using metadata XML ID read_evo9 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml
[20:01:08.471] Using interface OpenPort 1.3 Universal TX2I2IXh0caea4c535d9b68f63ab24f3df87b15a869a1df6
[20:01:10.274] sending init sequence 1 (0001)
[20:01:13.540] sending init sequence 1 (0003)
[20:01:16.806] sending init sequence 1 (FFFF)
[20:01:19.556] no response to any known code
[20:01:19.556] interface close
I was still pulling over 13 volts as my friend's vehicle was still hooked to mine. Only worked once! What gives?!
Thread Starter
Newbie
Joined: Apr 2004
Posts: 41
Likes: 0
From: Boston, MA USA
*Final Update*
This will be my final update to this topic.
Conclusion:
Had my Evo IX towed to the nearest Mitsubishi dealer and had them reprogram my keys into the ECU. It worked and I am back on the road again. Cost me $42.50 and 5 minutes of my time to get that done. That's excluding the towing charge I had to pay which was $90.00 but at least it only took 5 minutes.
Conclusion:
Had my Evo IX towed to the nearest Mitsubishi dealer and had them reprogram my keys into the ECU. It worked and I am back on the road again. Cost me $42.50 and 5 minutes of my time to get that done. That's excluding the towing charge I had to pay which was $90.00 but at least it only took 5 minutes.
Thread
Thread Starter
Forum
Replies
Last Post