ok cool got idc working who knew it be so easy lol i had it above puslewidth
and i did do that to locate the logs and but when i got to the folder they arent there so when i try to cut and copy the logs from map tracer it say its cant find them and i did notice that the logs have a lil lock on them but the sample ones dont

 

Searched and couldnt really find an answer. Having an issue with EvoScan and reading DTC's. It will log fine, actuator tests work fine, but displaying and clearing DTC's works once maybe every 30 times. Yeah not kidding! If it displays DTC's it will clear them. I get a "no response from ecu" as the last line in the comm window. Any ideas? Is a setting somewhere getting tweaked?

BTW this is an 03 EVO VIII Ecu, in a 1g. Running 9653 SD. No other issues with anything else. Flashes and reads fine. Pretty sure this is either a software setting or a bug.

 

Hello all,

I have read and read and searched and searched and the person above is the only one that has a similar problem to mine. I understand that he fixed his issue by not using the beta version of the software, but 1.42 seems to not be beta anymore. Stats:

03 Evo 8
AsusEEE 1005ha super hybrid engine and power settings cranked all the way up
Win 7 Ultimate
OP2.0 with ecu flash cable
ECUFlash 1.42.2595
Evoscan 2.8

The battery on the car is fully charged. I have tried uninstalling and reinstalling the ecu flash software. Continuity on the ecuflash cable checks out fine. Evoscan DOES connect and log. I have tried the ecu unlocker even though that shouldn't be an issue. I had a friend tune on it in April with a 1.3 cable with no problem. When I start up ecuflash I am getting NOTHING. All buttons remain greyed out so I can't read the rom. I don't even get an error and it doesn't show the OP2.0 cable at the bottom of the list like I have seen on other peoples posts.

Any help is greatly appreciated.

 

I having the exact same problem. Got an OP2 for Christmas and cant get it to work. Bump for some help.

 

Guys.... If you have intalled a beta version maybe the bootrom of the tactrix cable is also overwritten... The only way is to deinstall the software "AND" deinstall the driver for the taxtric cable... Really everything... You will find the driver also in hardware manager where you can deinstall all installed programms.

After that you take a look the folder is also deleted... if not... do it

Restart

And new install of a "NON" Beta version with the old driver... After all connect your tactrix to the notebook (not the car) and "BING BING" New hardware found and the rest will do the computer.

Never use a "BETA" Version for a flash... That's just for developer and they know how to reactivate a bricked ECU.

Try this...

Peter

 

Thanks for the help peter, I will be sure to try this.

 

okay I got it to connect at least but now im getting the standard:

[20:39:11.013] EcuFlash Version 1.42.2595
[20:39:11.013] OS Version Windows Vista
[20:39:11.013] Qt Version 4.5.0
[20:39:11.023] 56 memory models read.
[20:39:11.024] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[20:39:11.292] 343 ROM metadata models scanned.
[20:39:11.293] checksum module "subarudbw" loaded.
[20:39:11.293] checksum module "mitsucan" loaded.
[20:39:11.293] flashing tool "wrx02" loaded.
[20:39:11.293] flashing tool "wrx04" loaded.
[20:39:11.293] flashing tool "sti04" loaded.
[20:39:11.294] flashing tool "sti05" loaded.
[20:39:11.294] flashing tool "mitsukernel" loaded.
[20:39:11.294] flashing tool "mitsukernelocp" loaded.
[20:39:11.294] flashing tool "mitsubootloader" loaded.
[20:39:11.294] flashing tool "shbootmode" loaded.
[20:39:11.296] flashing tool "shaudmode" loaded.
[20:39:11.296] flashing tool "subarucan" loaded.
[20:39:11.296] flashing tool "mitsucan" loaded.
[20:39:27.466] J2534 API Version: 04.04
[20:39:27.466] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29
[20:39:27.466] Device Firmware Version: 1.10.3020
[20:39:29.863] sending init sequence 1 (0001)
[20:39:33.095] sending init sequence 1 (0003)
[20:39:36.326] sending init sequence 1 (FFFF)
[20:39:39.556] sending init sequence 1 (F0F0)
[20:39:42.273] no response to any known code
[20:39:42.277] interface close

My battery is charged, and Ive tried the ECU unlocker. I did have to download the unlocker here ( http://www.aktivematrix.com/forum/dl...ile&file_id=13 ) cause I couldnt get the one on evom to work. they seem to be the same thing. My car does have a tune from the previous owner.

Computer is running vista. Any help is appreciated.

 

Bump for new years eve help.

 

New Years bump

 

okay, I got my ROM to upload but now I am getting a "unknown ROM image" message. I am guessing this is because it has a tune on it already. Not sure what to do now. I attached a pic of the error message. I also saved the log if that helps.

 

did you save the rom image? if so look in the ROM section you can see in the left section and it'll tell you the ID then you just need the right xml file

 

that error is because you dont have the xml file.

 

lol my bad. you already said it.

put xml in here: Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

 

You need your definition file for your rom.... This XML must be copied in your "OpenEcu" directory.... After this you can see all your necessary details from you rom.

You need to read more about this buddy.... x-times talked about in this forum. You can use "GOLDEN" def files.

 

Well Thanks for the help guys. I figured it out, apparently my car has the tephra mod v7 flashed so now I have a ton of reading and logging to do.

Thanks again.