problem reading ecu "no response to any known code"

[lefty]

fwiw ive read a p0420 code from my cat off of a obdII scanner before, so im pretty sure the port works.

Just ran to auto zone:thumbsup: to hook up their odbII scanner and see if my port was ok. Everything came back OK, no codes hehe. The scanner initialized and worked perfectly so I dont think its my wiring or port. If you see some dude in chicago on the side of the road waving a cable and a laptop around stop and let me borrow your evo maybe ill take a trip to devotuning or ams and see if they can help a brotha out
thx again for all your help boys, this blows

[DarkECU]

Hi cboles!

Does it possible to send any init code with you ecuflash software?

[MalibuJack]

hmm I know a couple evo owners, not well enough to have their numbers tho. will have to see if I can find one of em and ask to use their ecu hehe. weird
also, another weird one, I tried the mitsubishi logger from MJ 1 beta 3 and it gives me weird error too
Starting Logger in Live Mode
Sending 0x00 at 5 baud
Initializing.....
Initializing.....
Initializing.....
Initializing.....
Initializing.....
Initialization Timeout....

it sits there and doesnt do anything. My evo is broke lol
edit2* I also tried resetting my ecu to no avail, same problems

Thats actually interesting.. That indicates to me that there may actually be something wrong with the cable. The logger works for almost everyone with or without the white plug connected. Additionally it works with other OBD-II cables that use the FTDI chip (that isnt elm based)

What this means to me is the cable is either not sending the init correctly, or the ECU isnt processing it. Since OBD-II scanners work.. then you REALLY need to test your cable on another car, and even on another computer.

And yes, its possible to use different init codes, only the one used by the unlocker will work with any Mitsubishi (Evo for certain) that has an unexpected init code or an ECU with a bad flash that would have been discarded as bad in the past.

[lefty]

Colby is going to send me a new cable out tomorrow so I can make sure its not the problem. How is that for customer service? Thanks man I owe you a big one! If youre ever in the chicago area beers on me :cheers:

[JoeBee]

I have had also problems to connect with Jacks logger.
For me, it was the driver from Colbys 1.29 Version.
What I have done:
Installing Ecuflash 1.28, Copy the "driver" Subdir to have a Backup.
Install Ecuflash 1.29, uninstall the driver with the uninstall programm located in the driver subdir.
Install the driver from the backup copy of Version 1.28

After that pocedure you can check Jacks logger. For me the logger works after that. (EVO 7)
If this works, you can ckeck the unlocker again.

I you need more support I can do some screenshots.

Sorry for my English. It is not my native language. (Native: German)

[lefty]

thx joe, I will give that a shot right now. er, I dont have 1.28 and cant find a link. Can you send version 1.28 to my email. Thanks

[JoeBee]

Mail send.

[JoeBee]

Sorry, Mail was not deliverd. Did your Mailserver block attachments?

Code: Select all

<leftyc**@gmail.com>:
64.233.185.** failed after I sent the message.
Remote host said: 552 5.7.0 Illegal Attachment 45si2904891wri


Attachment was a zip file.

I put it here for a while:
http://mitglied.lycos.de/joebee/ecuflash_setup128.zip
This is NOT the original file from Colby. I have include the driver subdir from 1.28 separately in the zip.
The driver subdir can be used to downgrade the driver without the reinstall of the 1.28 Version.

[lefty]

thx bud, Ill give it a shot
no luck:
[00:03:49.937] Version 1.28.716
[00:03:49.937] 8 memory models read.
[00:03:50.265] 71 ROM metadata models read.
[00:03:50.265] checksum module "subarudbw" loaded.
[00:03:50.265] flashing tool "wrx02" loaded.
[00:03:50.265] flashing tool "wrx04" loaded.
[00:03:50.265] flashing tool "sti04" loaded.
[00:03:50.265] flashing tool "sti05" loaded.
[00:03:50.265] flashing tool "mitsukernel" loaded.
[00:03:50.265] flashing tool "mitsukernelocp" loaded.
[00:03:50.265] flashing tool "mitsubootloader" loaded.
[00:04:05.031] unable to connect to vehicle interface.
[00:04:19.890] unable to connect to vehicle interface.
[00:04:26.906] unable to connect to vehicle interface.
[00:04:44.359] sending init sequence 1 (0001)
[00:04:47.593] sending init sequence 1 (0003)
[00:04:50.843] sending init sequence 1 (FFFF)

[haha]

Hi
I have an evo 8 and the same problem occurs
I have started a thread specifically under Evo 8 for this exact problem
I am using ecuflash 1.29 and a 1.3 mitsu cable
My cars obd port works 100%
My ecu has however been ecutek reflashed more than 18 months ago so I would imagine that has no effect as it seems to be only recent ecutek flashes that do "silly things"

Help !!! Help !!!

edit: Another point thats important is that when the software sends the FFFF command to the ecu I hear "kathunk" almost like a central locking solenoid so the car is definetly doing something !

[lefty]

Update*
Hey Colby I recieved the cable today, it works! Thats all it was, it worked perfectly the first time. haha, drop colby an email he will fix you up, send back your old cable. Thanks bud!

[laakness]

So I have been using my laptop and cable on many friends cars but a I have a buddy with a IX and I can't read his ECU. I have the exact problem mentioned on the first page of this post.

Cable works fine, I flash and log all the time. This is the first car I've had an issue with.

Dynoflash had a similar issue when he did a custom tune just this past summer and ended up taking the ECU out of the car and hooked to what was explained as a bench harness he had brought with him. Al suggested that he had a bad car battery but it is at the right voltage (IX MR gauges)

Any ideas?

[lefty]

Hey sorry for the late response, however its not going to be of any help. The only way I was able to resolve this was with a new cable. It seems you may be in a bit of a different situation seeing as your cable works on a different car. The only thing I can think of has already been discussed low battery voltage. Double check the cable works in the other car still, maybe a wire came loose in the ride. Wish I could be more help, good luck bud

[gear head]

I'm having a similar problem as well. The first time I read with ecuflash was with v1.27 & had absolutly no problems. Currently I can't read from ecu, however I can flash & compare to ecu. When the read button is pushed a popup screen appears with 2 buttons @ the bottom (read & cancel). The read button already seems to be pressed when the screen comes up, nothing happens & no error codes are present. I have had this problem ever since I downloaded the stock rom. ???????

[KenYong3671]

Hi Colby,

i have similliar problems with reading from ecu too...
before that i ve been using it for sometimes and there's no such issue.
i've tried on three different cars ...same issue....but Logging is no problem..

please help

P/s: had tried all the mentioned solutions stated in the forum..not work!!

Also can i remove the ecu from the car and do a direct read adn write ???
if yes, how should i go about it...