Can't flash or read the ROM from your ECU - Start Here! - Page 7 - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community

Notices
EcuFlash
Sponsored by:
Sponsored by:

Can't flash or read the ROM from your ECU - Start Here!

Reply

 
 
 
Old Dec 1, 2016, 10:13 PM
  #91  
Evolving Member
iTrader: (14)
 
seven10's Avatar
 
Join Date: Feb 2009
Location: Los Angeles
Posts: 130
Thanked 4 Times in 4 Posts
Originally Posted by seven10 View Post
Charged the battery and was seeing 13.1v with the ignition in the 'On' position, but still can't read from my ECU. Anyone heard of anything like this? I'm not sure what to diagnose at this point.
I'm suspecting a driver or cable issue now, I was able to read and write to my ECU when using my MacBook and Ecuflash 1.38. I was also able to read and write from my Windows laptop when using 1.444503, but still can't log actual data from Evoscan.
seven10 is offline  
Reply With Quote
Old Dec 2, 2016, 05:11 PM
  #92  
Newbie
 
MrCollyns's Avatar
 
Join Date: Mar 2014
Location: Chicago
Posts: 26
Thanks: 0
Thanked 1 Time in 1 Post
I just went through this for a couple weeks. I'm not sure if they changed the driver or they changed windows but i could not get evoscan running on a 1.3U cable at all... only ECUFlash.

I spent the money on the 2.0 cable and EvoScan came right to life...
MrCollyns is offline  
Reply With Quote
Old Dec 2, 2016, 07:28 PM
  #93  
Evolving Member
iTrader: (14)
 
seven10's Avatar
 
Join Date: Feb 2009
Location: Los Angeles
Posts: 130
Thanked 4 Times in 4 Posts
Originally Posted by MrCollyns View Post
I just went through this for a couple weeks. I'm not sure if they changed the driver or they changed windows but i could not get evoscan running on a 1.3U cable at all... only ECUFlash.

I spent the money on the 2.0 cable and EvoScan came right to life...
I'm wondering if that's it, I have a support email in to Evoscan to see if they can let me know what else I might be missing.
seven10 is offline  
Reply With Quote
Old Dec 14, 2016, 08:09 PM
  #94  
Evolving Member
iTrader: (14)
 
seven10's Avatar
 
Join Date: Feb 2009
Location: Los Angeles
Posts: 130
Thanked 4 Times in 4 Posts
Originally Posted by MrCollyns View Post
I just went through this for a couple weeks. I'm not sure if they changed the driver or they changed windows but i could not get evoscan running on a 1.3U cable at all... only ECUFlash.

I spent the money on the 2.0 cable and EvoScan came right to life...
I ended up trying a 2.0 cable and it worked no problem. Now just trying to find another local person with a 1.3U that they know works so I can can verify if the issue is with my cable or computer.

EvoScan never got back to me on my support ticket though
seven10 is offline  
Reply With Quote
Old Feb 9, 2017, 04:37 PM
  #95  
Newbie
 
Join Date: Nov 2006
Location: LONDON
Posts: 19
Thanked 0 Times in 0 Posts
hi having problems reading rom from 2004 jdm evo 8 ecu

have attached the log

[23:24:52.543] FTDI Driver Version 2.12.12
[23:24:52.559] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.559] interface close
[23:24:52.628] FTDI Driver Version 2.12.12
[23:24:52.643] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.643] interface close
[23:24:52.697] FTDI Driver Version 2.12.12
[23:24:52.712] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.712] interface close
[23:24:52.779] FTDI Driver Version 2.12.12
[23:24:52.781] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.781] interface close
[23:24:52.844] FTDI Driver Version 2.12.12
[23:24:52.859] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.859] interface close
[23:24:52.913] FTDI Driver Version 2.12.12
[23:24:52.928] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:52.928] interface close
[23:24:56.635] using metadata XML ID read_evo7 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml
[23:24:56.651] FTDI Driver Version 2.12.12
[23:24:56.667] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:24:58.721] sending init sequence 1 (F0F0)
[23:24:58.923] interface close
[23:25:27.659] using metadata XML ID read_evo7 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml
[23:25:27.675] FTDI Driver Version 2.12.12
[23:25:27.690] Using interface OpenPort 1.3 Universal TX2EdI1Pe85f74c55f8dd1247f574d6791c9b1e6016fa72e
[23:25:29.669] sending init sequence 1 (F0F0)
[23:25:29.870] interface close

any ideas please(have tried everything on this thread)
SH0F is offline  
Reply With Quote
Old Apr 9, 2017, 11:55 PM
  #96  
Newbie
 
Join Date: Apr 2017
Location: puerto rico
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
new with ecuflash

I just read my ecu with openport 2.0 and I think a don't have the right definition file yet im running a lancer 2006 with a mirage ecu md351551 at first it downloaded a readimage.srf file I saved it as a .bin but it wont open any hel help will be thank full
Attached Files
File Type: bin
jay basemep.bin (128.0 KB, 0 views)
jayjay2892 is offline  
Reply With Quote
Old Jun 23, 2018, 02:58 PM
  #97  
Evolving Member
iTrader: (7)
 
Thugline's Avatar
 
Join Date: Dec 2005
Location: Riverside,CA
Posts: 444
Thanked 0 Times in 0 Posts
My1.3u cable isn't able to read jack! Can anyone tell me where to go to get my Rom ID so evoscan and ecuflash can get read that the cable is connected?

[14:41:35.933] Logging to file C:/Users/topgun/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20180623t144135.txt [14:41:35.933] EcuFlash Version 1.44.4799

[14:41:35.933] OS Version Windows 10

[14:41:35.933] Kernel Type winnt

[14:41:35.933] Kernel Version 10.0.16299

[14:41:35.933] CPU x86_64

[14:41:35.933] Product Name Windows 10

[14:41:35.933] Product Type windows

[14:41:35.933] Product Version 10

[14:41:35.933] Qt Version 5.6.0

[14:41:35.933] Qwt Version 6.1.2

[14:41:35.933] QwtPlot3D Version 0.2.6

[14:41:35.933] Boost Version 1.60

[14:41:35.933] FTDI Library Version 3.02.11

[14:41:35.933] Openport J2534 Library Version 1.02.4798

[14:41:35.940] 67 memory models read.

[14:41:35.940] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata

[14:41:36.072] 745 ROM metadata models scanned.

[14:41:36.072] checksum module "subarudbw" loaded.

[14:41:36.072] checksum module "subarudiesel" loaded.

[14:41:36.072] checksum module "subaruhitachi" loaded.

[14:41:36.072] checksum module "mitsucan" loaded.

[14:41:36.072] checksum module "mitsuh8" loaded.

[14:41:36.072] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.

[14:41:36.072] patch module "Mitsu CAN RAM Parameter Logging" loaded.

[14:41:36.222] flashing tool "wrx02" loaded.

[14:41:36.238] flashing tool "wrx04" loaded.

[14:41:36.239] flashing tool "sti04" loaded.

[14:41:36.239] flashing tool "sti05" loaded.

[14:41:36.255] flashing tool "mitsucan" loaded.

[14:41:36.255] flashing tool "mitsukernel" loaded.

[14:41:36.255] flashing tool "mitsukernelocp" loaded.

[14:41:36.255] flashing tool "mitsubootloader" loaded.

[14:41:36.255] flashing tool "shbootmode" loaded.

[14:41:36.255] flashing tool "shaudmode" loaded.

[14:41:36.255] flashing tool "subarucan" loaded.

[14:41:36.255] flashing tool "subarucand" loaded.

[14:41:36.255] flashing tool "subarubrz" loaded.

[14:41:36.271] flashing tool "subaruhitachi" loaded.

[14:41:36.294] FTDI Driver Version 2.12.12

[14:41:36.325] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7

[14:41:36.327] interface close

[14:41:36.644] FTDI Driver Version 2.12.12

[14:41:36.664] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7

[14:41:36.666] interface close

[14:41:36.723] FTDI Driver Version 2.12.12

[14:41:36.741] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7

[14:41:36.742] interface close

[14:41:36.801] FTDI Driver Version 2.12.12

[14:41:36.818] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7

[14:41:36.820] interface close

[14:41:36.881] FTDI Driver Version 2.12.12

[14:41:36.898] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7

[14:41:36.900] interface close

[14:41:36.957] FTDI Driver Version 2.12.12

[14:41:36.975] Using interface OpenPort 1.3 Universal TX2NmCuyeb1e13594038652e2949551ff4f69a13886d87f7

[14:41:36.977] interface close
Thugline is offline  
Reply With Quote
Old Jun 24, 2018, 05:34 AM
  #98  
Newbie
 
MrCollyns's Avatar
 
Join Date: Mar 2014
Location: Chicago
Posts: 26
Thanks: 0
Thanked 1 Time in 1 Post
Uninstall all openport drivers and install only 1. Then try again sounds like a driver conflict.
MrCollyns is offline  
Reply With Quote
Old Jun 24, 2018, 08:54 AM
  #99  
Evolving Member
iTrader: (7)
 
Thugline's Avatar
 
Join Date: Dec 2005
Location: Riverside,CA
Posts: 444
Thanked 0 Times in 0 Posts
Originally Posted by MrCollyns View Post
Uninstall all openport drivers and install only 1. Then try again sounds like a driver conflict.
Thx for the response brother. But what driver do I install?
Thugline is offline  
Reply With Quote
Old Jun 24, 2018, 08:57 AM
  #100  
Newbie
 
jingalalahoe's Avatar
 
Join Date: Jul 2016
Location: Zzz
Posts: 38
Thanked 7 Times in 7 Posts
Originally Posted by Thugline View Post

Thx for the response brother. But what driver do I install?
This is their latest driver. I had bad issues and the same driver solved everything for me

http://www.evoscan.com/drivers/openport1.3drivers.zip
jingalalahoe is offline  
Reply With Quote
Old Jun 24, 2018, 12:17 PM
  #101  
Evolving Member
iTrader: (7)
 
Thugline's Avatar
 
Join Date: Dec 2005
Location: Riverside,CA
Posts: 444
Thanked 0 Times in 0 Posts
Originally Posted by jingalalahoe View Post
This is their latest driver. I had bad issues and the same driver solved everything for me

http://www.evoscan.com/drivers/openport1.3drivers.zip
still didnít work
Thugline is offline  
Reply With Quote
Old Jun 25, 2018, 06:46 AM
  #102  
Newbie
 
MrCollyns's Avatar
 
Join Date: Mar 2014
Location: Chicago
Posts: 26
Thanks: 0
Thanked 1 Time in 1 Post
You have to go into device manager and manually in-install the drivers then unplug the 1.3u cable, then reboot. Then install the 1.3u driver and then plug the cable back in. Open the device manager and make sure windows isnt try to install an internet driver over the 1.3u.

its tricky but it will work with the right process.. also remember to disable the firewall or allow ecu flash and evo scan through.
MrCollyns is offline  
Reply With Quote
 
 
 
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Hiram6g74
EcuFlash
2
Feb 22, 2018 03:00 PM
evoscan
Evo X Engine Management / Tuning Forums
52
Jun 20, 2017 01:46 AM
city
EcuFlash
5
Jun 2, 2017 08:34 PM
FFEMT
EcuFlash
5
Aug 1, 2016 04:45 AM
GrabbinGears
General Engine Management / Tuning Forum
2
Jul 7, 2016 02:19 PM


Thread Tools
Search this Thread
Quick Reply: Can't flash or read the ROM from your ECU - Start Here!


Contact Us Archive Advertising Cookie Policy Privacy Statement Terms of Service

We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.