MR_evoX

Ok here's the story....

i just bought a new laptop and installed ecuflash beta on it. I wanted to pull my romid because my other laptop's in WA and i forgot to transfer it over. i plugged everything up thinking this should be a snap. i clicked "read" and it said interface closed. i'm like WTF. i did it two more times and it said the same thing. So I left for a bit to buy something and when i came back i thought maybe it'll work. That f***er worked for like the first 4 seconds and then said interface closed. But the car kept running though the cycles... you know that facial expression you get when everything goes wrong in front of you? that was me.....i said to myself." F*** i dont have any tools and everything was about to close. what the F** am i gonna do". So i ran to the nearest shoppette to see if they had some wire and tools. The only thing they had was an adjustable wrench. So i'm like maybe i'll just disconnect the battery and it'll be OK. NOPE! the car kept running though its cycles everytime i started it. So in desperation and panic i kept clicking "read ecu" in hopes of it fixing itself. i did that like 10 times before i said " i F***ing take care of you and this is how you treat me!!" i clicked it one more times but this time it was different. The initial part was the same like the others but after "unable to read ecu" it said" resetting ecu". Then i was able to start the car. i yelled " Thank you!!" and unplugged everything quickly. Once i finished unplugged i looked up and there were these guys looking at me thinking what is this crazy asian guy doing in his car. i'm just like whatever my car runs and i dont have to walk to work.

I just want to share this moment with you guys because i'm relieved the car worked without me doing the whole bench the ecu and puzzled why it just went back to normal.

cody92talon

iTrader: (6)

haha thats pretty funny. i guess the car has feelings too. it just wanted you to talk nice to it haha

itzwolf

iTrader: (9)

Next time slap her butt and tell her who is the boss....

But seriously, I am curious what caused it. Wonder if it was a driver issue causing communication issues. Did you reboot your computer after installing ECUflash or at any point during the panic state?

MR_evoX

i restarted at first but it keep doing the same thing. so i installed 1.42 but that couldn't read or see the ecu. The funny thing is that evoscan 2.8 worked just fine. Then i deleted both off my laptop and redownloaded it of the evoscan website. Thats when i went on the clicking spree and it worked.

i'll try connecting it again after work.

MR_evoX

This is what i got when i plugged it back in....


[15:03:16.502] J2534 API Version: 04.04
[15:03:16.502] J2534 DLL Version: 1.00.3210 Nov 22 2010 23:18:50
[15:03:16.502] Device Firmware Version: 1.11.3209
[15:03:16.502] Device Serial Number: TA1XR*iV
[15:03:18.253] -- loading kernel --
[15:03:18.253] -- connecting to kernel --
[15:03:18.253] kernel get version
[15:03:18.377] ECU HW part number : 1860A980
[15:03:18.409] ECU SW part number : 1860A98006
[15:03:18.424] -- unlocking ECU --
[15:03:18.424] starting session...
[15:03:18.440] requesting seed...
[15:03:18.455] sending key...
[15:03:18.736] -- uploading kernel --
[15:03:18.767] .
[15:03:18.783] .
[15:03:18.783] .
[15:03:18.799] .
[15:03:18.814] .
[15:03:18.830] .
[15:03:18.845] .
[15:03:18.861] .
[15:03:18.861] .
[15:03:18.877] .
[15:03:18.892] .
[15:03:18.908] .
[15:03:18.923] .
[15:03:18.939] .
[15:03:18.939] .
[15:03:18.955] .
[15:03:18.970] .
[15:03:18.986] .
[15:03:19.001] .
[15:03:19.001] .
[15:03:19.017] .
[15:03:19.017] -- connecting to kernel --
[15:03:19.017] kernel get version
[15:03:19.017] kernel version is : OpenECU Mitsubishi M32186 CAN Kernel V1.09
[15:03:19.017] reading kernel comm buffer size
[15:03:19.033] comm buffer size set to 1024
[15:03:19.033] reading kernel flash buffer size
[15:03:19.033] flash buffer size set to 4096
[15:03:19.048] -- dumping ECU memory --
[15:03:19.048] kernel read area: addr: 00000000 len: 0400
[15:03:19.111] invalid / no kernel response to read
[15:03:19.111] kernel read area: addr: 00000000 len: 0400
[15:03:21.123] invalid / no kernel response to read
[15:03:21.123] kernel read area: addr: 00000000 len: 0400
[15:03:21.170] invalid / no kernel response to read
[15:03:21.170] ECU memory read failure.
[15:03:21.170] can't read image.
[15:03:21.170] -- unloading kernel --
[15:03:21.170] kernel reset
[15:03:23.291] -- unlocking ECU --
[15:03:23.291] starting session...
[15:03:23.291] requesting seed...
[15:03:23.307] sending key...
[15:03:24.571] -- resetting ECU --
[15:03:26.006] -- reading ECU ID --
[15:03:26.131] ECU HW part number : 1860A980
[15:03:26.162] ECU SW part number : 1860A98006
[15:03:26.177] VIN :
[15:03:26.193] interface close
[15:03:26.209] interface close

is this a locked ECU? i'm going to get a new cable because it looks a little tweaked one end. if that doesn't work i'll have to bench the ecu.

anyone tried benching the ECU while still on the car?

MR_evoX

ok i benched my ecu and loaded a known good ROM and still i can't ecuflash to inferface through the obdII port. any suggestions why its doing that?

fostytou

iTrader: (15)

You can usually pull it out of programming mode with the option in the help menu. If that doesn't work you likely need to bench.

Did you remove the VIN from the log or was it never there? Is there any chance your battery is not in great shape and/or do you ever accidentally kick the OBD port / OP2.0?

MR_evoX

Thanks to Chris from mellon tuning for plugging in his laptop and verifying that it's not the OP2.0, cable or car.The problem is 1.43 beta that i downloaded. But everytime i delete everything and reinstall it does the same thing. i dont know how to fix it.

fostytou

iTrader: (15)

What operating system are you using? After uninstalling did you delete everything from your user directory/ecuflash and the program files/ecuflash directories and then restart?

Are you constantly adding the same modified definitions back in or are you using the included definitions?

MR_evoX

i'm running windows 7 64bit. I've deleted everything associated with ecuflash drivers and all. Restarted and then fresh install without antivirus active and without adding new definitions. I have no clue what it could be.

i've been searching the web about this problem for days straight. Some people tried installing into a different directory, but that didn't work. Made sure rommetadata folder was pointed to the right folder, nothing. i'm stumped.

Mellon Racing

iTrader: (38)

you're welcome, it was nice to meet you. My laptop we used on your op2.0 cable is windows 7 64 bit for what it's worth.

fostytou

iTrader: (15)

After clearing everything out right click the installer and select "run as administrator" so that it has superuser permissions when installing.

If that doesn't work change the shortcut that you use to start it to run as admin also.

MR_evoX

Ok this is what i've done so far...

-uninstalled ecuflash completely
-restarted
-reinstalled ecuflash under c:/ecuflash
-deleted all subaru and and non evo related files
-connected to car and now ecuflash just won't read the addresses but this time it doesn't get stuck.
-took out my ecu to bench but this time ecuflash won't connect, all is says is j2534 will not connect or ERR timeout every time

i swear it's my laptop. but there is nothing i can do its the only thing i got.

villero1834

iTrader: (1)

how do u know ur ecu is bricked or locked.
Mine came up with a check sign in the lcd ,im running thepra v1 , it happened at WOT , know the car wont crank again and the fans wont shut off whats weird is that the car went off while i was driving and never came back up

fostytou

iTrader: (15)

That order of ops is wrong:

-restart
-uninstalled ecuflash completely
-delete all (subaru and evo) related files in c:\program files and "my documents"
-restart
-right click installer for newest ecuflash - 1.43.3000 and select "run as administrator"
--complete install
-restart
-right click shortcut to start ecuflash and select "run as administrator"