EcuFlash Error - called/emailed Tactrix w/ no response

User topics relating to software that reflashes or modifes ECU code and data

Moderator: Freon

EcuFlash Error - called/emailed Tactrix w/ no response

Postby mirage4g93 » Wed Jul 14, 2010 2:03 pm

Hello,

I am using EcuFlash version 1.35.1650 and a 1.3u cable. I am using it to connect to my 1998 Mitsubishi Mirage ecu. I can successfully upload the ROM to EcuFlash as well as edit and save my edited ROM. However, when I attempt to "Write to ECU" I consistantly get the same error when the process reaches 93% completion.

This is the error message that appears. I have also attached the log file as well. Any insight would be great.
ScreenShot005.jpg
ScreenShot005.jpg (19.34 KiB) Viewed 3920 times


log file: http://mirageinfo.net/pictures/error7_12_10.log


Thanks
mirage4g93 (Mike)
mirage4g93
 
Posts: 2
Joined: Mon Jul 12, 2010 10:44 am

Re: EcuFlash Error - called/emailed Tactrix w/ no response

Postby radsdau » Wed Jul 14, 2010 3:27 pm

Try using the latest ECUFlash, which is 1.43 Beta.
radsdau
 
Posts: 674
Joined: Wed Feb 08, 2006 6:56 pm

Re: EcuFlash Error - called/emailed Tactrix w/ no response

Postby mirage4g93 » Wed Jul 14, 2010 4:41 pm

Unfortunately that won't work. I have already had to roll back to this version because the newest version would not even communicate with my ECU. I have been working with another Mirage owner who has successfullly flashed using this version and he too was not able to read his ecu using the newest version. 1.35 was the latest version that was confirmed to work of us Mirage owners. That is those using the 1.3u cable. I can't speak for the 2.0 folks, but either way I know that this version with the cable I have has worked for others.
mirage4g93
 
Posts: 2
Joined: Mon Jul 12, 2010 10:44 am

Re: EcuFlash Error - called/emailed Tactrix w/ no response

Postby radsdau » Thu Jul 15, 2010 3:40 pm

Hmmm, sorry I can't help any further. My next best guess is that the micro in the ECU you have is a variant of those in other Mirage ECUs- close but not identical, which might explain being able to read but not write (similar to EVO 5-6.5). That is why I suggested 1.43B because it handles those 2 differences.
It could be that the OP2 cable is required, but I wouldn't have thought so.
Might be one for Colby.
Good luck!
radsdau
 
Posts: 674
Joined: Wed Feb 08, 2006 6:56 pm


Return to Reflashing Software

Who is online

Users browsing this forum: No registered users and 3 guests