Hollywood_Evo

Trying to load my new maps up that i just got from my tuner, and now i can't read, write or access the ecu. We had it working a couple months ago, then my computer crashed so i got a new one and downloaded the newest versions of EcuFlash and EvoScan. I can log just fine with EvoScan, but can't do anything in EcuFlash. Car reads at well over 13 volts, using windows 7, and a tactrix cable thats not even a year old. Only thing that has chnaged was the versions of the software and the computer.

This is the error code that i get in the log.

[21:39:01.863] EcuFlash Version 1.42.2595
[21:39:01.863] OS Version Windows Vista
[21:39:01.863] Qt Version 4.5.0
[21:39:01.878] 56 memory models read.
[21:39:01.878] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[21:39:02.066] 351 ROM metadata models scanned.
[21:39:02.066] checksum module "subarudbw" loaded.
[21:39:02.066] checksum module "mitsucan" loaded.
[21:39:02.066] flashing tool "wrx02" loaded.
[21:39:02.066] flashing tool "wrx04" loaded.
[21:39:02.066] flashing tool "sti04" loaded.
[21:39:02.066] flashing tool "sti05" loaded.
[21:39:02.066] flashing tool "mitsukernel" loaded.
[21:39:02.066] flashing tool "mitsukernelocp" loaded.
[21:39:02.066] flashing tool "mitsubootloader" loaded.
[21:39:02.066] flashing tool "shbootmode" loaded.
[21:39:02.081] flashing tool "shaudmode" loaded.
[21:39:02.081] flashing tool "subarucan" loaded.
[21:39:02.081] flashing tool "mitsucan" loaded.
[21:39:38.608] Using interface OpenPort 1.3 Universal TX2BmGFM21eba5c56e09521525fbae862251f2348a5c479f
[21:39:40.802] sending init sequence 1 (0001)
[21:39:44.062] sending init sequence 1 (0003)
[21:39:47.322] sending init sequence 1 (FFFF)
[21:39:50.068] no response to any known code
[21:39:50.068] interface close
[21:42:34.166] Using interface OpenPort 1.3 Universal TX2BmGFM21eba5c56e09521525fbae862251f2348a5c479f
[21:42:36.344] sending init sequence 1 (0001)
[21:42:39.604] sending init sequence 1 (0003)
[21:42:42.865] sending init sequence 1 (FFFF)
[21:42:45.610] no response to any known code
[21:42:45.610] interface close

I'm hoping someone on here can offer some advice cause my tuner is out of ideas.

Cheers!

todd6027

iTrader: (10)

download unlocker from here

https://www.evolutionm.net/forums/ec...-unlocker.html

run it then open ecuflash

Hollywood_Evo

I mentioned that to my tuner but he said it shouldn't be locked in anyway. But regardless I will give that a shot. If that doesn't work, any oppinions on what to try next?

Cheers!

todd6027

iTrader: (10)

try with battery fully charged make sure both tactrix connectors are secure .

Raptord

iTrader: (10)

Try starting the car and letting it run for 30 seconds or so before trying to read, I have to do that when it's cold.

THUB

iTrader: (5)

I'm going to second (third?) low battery voltage. For a while I could only flash after driving the car for a bit, then I got a new battery.

Hollywood_Evo

It won't read, write or test write with the car running. But ill put a trickle charger on it while I do it next.

THUB

iTrader: (5)

It never will write while the car's running. it's currently using the information you're trying to flash. the battery will hold a higher voltage in the minute or so after you shut off the car after running it for a while, which can facilitate flashing.

Hollywood_Evo

Not sure if it really matters, but I'm using the older 1.3 cable and not the openport 2.0.

I also got the same error sequence last night using the older 1.28 version. Does anyone have a copy of 1.41 that could download?

I plan on running the 1.43 beta after uninstalling everything related to ecuflash and tactrix. During the install it automatically installs the drivers correct? Now everytime I plug in my cable windows updates the driver. Am I suppposed to let that update happen?

Cheers!

Cheers!

binky

iTrader: (11)

If all else fails, you can try the EcuFlash Beta:
http://www.tactrix.com/index.php?opt...d=44&Itemid=65


-Bink

Hollywood_Evo

I've tried the beta version as well. I've basically tried everything. I'm just wondering if the drivers aren't installing properly. It hasn't work on the two Asus laptops, so I'm gonna try and HP cause that's the last laptop it actually worked on.

Cheers.

Hollywood_Evo

I did a continuity test on the cable last night and it looks like ob2 portion of the cable transfers voltage from A to B. Which explains why EvoScan works. The reflash portion doesnt transfer any voltage as I couldn't get my multimeter to "beep" after numerous attempts.

As far as my knowledge goes, it sounds like that's my problem right there. Input?

Cheers!

GTijoejoe

iTrader: (25)

I have this exact same issue, also using a 1.3 openport cable. No solution ??

Raptord

iTrader: (10)

Does it do it only when the car is cold or at all times?

Since it's starting to get colder out I now can't reflash my car first thing in the morning, I have to start it first. That's the same error I get if I try to reflash.

escodotcarter

iTrader: (16)

Had the same problem after I got tuned. They locked my ecu but told me they didnt. Anyway, ecu unlocker worked perfectly. good luck