openecu.org

by **lefty** » Wed Oct 04, 2006 10:03 pm

Im having a little problem, I was hoping you could help me out? Ive searched through the forums, couldnt find any specific post to this. This is the most basic step and I dont think Im missing anything? I reinstalled the program twice, installed drivers for the cable myself, and let the program do it too. Ive changed com ports from 1-6 with a reboot in between. Im really at a loss, whenever I go to read from ecu I get a "no response to any known code" error message. Is this something small im missing? I feel so dumb right now. I have a evo IX follow instructions to the letter, and also tried a couple ways that were incorrect on purpose to see if that worked. I am attaching the log file. Thanks for the help,

by **MalibuJack** » Thu Oct 05, 2006 12:24 pm

What kind of car? By the log it looks like a mitsubishi.

It can be due to two reasons..

1) You have something like an ECU+ hooked up that is intercepting the OBD-II before it gets to the openport cable.

2) You have a locked ECU. If its locked and its a mitsubishi ECU, I have a tool that should fix your problem and you can get it on my website.

by **MalibuJack** » Thu Oct 05, 2006 12:26 pm

there are other possibilities, but these are the most common reasons besides the cable not being connected to the port, or the PC.

by **lefty** » Thu Oct 05, 2006 12:39 pm

Thanks for the reply MJ,
Sorry I should have specified, its an evo9 mr. The software cable was installed just fine on the laptop, it is seen in the device manager under ports. Seems to be functioning well. I was surprised noone else came upon this problem. I spent a couple(ya 2) hours trying to get this to work. No ecu+ no safc or anything of the like. I looked at all the pins on the cable and they seem to be seated just fine. I have another laptop I am going to try this on. The ignition just has to be turned "on" right? I even tried it turning it all the way to on and starting the car. Steps I took:
Plug usb into laptop, open ecuflash, connect white, then obdII, click ctrl-r , selected evo9, clicked read, turned ignition to on, then clicked "ok". Then ecuflash came up withthe no response error. I will take a look at your page and try the unlock program.
Thanks for your time in helping me, I really want to use this program its awesome. The guys that made it are amazing, big props to them

by **lefty** » Thu Oct 05, 2006 1:44 pm

Well, I tried the unlocking program. It didn't work but it did add a init sequence(FOFO) I will post the log. I also tried it on my work laptop, same thing happenes with both

In the unlocker it says its for ecuflash 1.8 would that be a problem, Im using 1.9?
Heres what happens without the unlocker running:
[00:23:21.093] Version 1.29.906
[00:23:21.109] 8 memory models read.
[00:23:22.062] 140 ROM metadata models read.
[00:23:22.062] checksum module "subarudbw" loaded.
[00:23:22.062] flashing tool "wrx02" loaded.
[00:23:22.062] flashing tool "wrx04" loaded.
[00:23:22.062] flashing tool "sti04" loaded.
[00:23:22.062] flashing tool "sti05" loaded.
[00:23:22.062] flashing tool "mitsukernel" loaded.
[00:23:22.062] flashing tool "mitsukernelocp" loaded.
[00:23:22.062] flashing tool "mitsubootloader" loaded.
[00:23:35.734] sending init sequence 1 (0001)
[00:23:38.968] sending init sequence 1 (0003)
[00:23:42.203] sending init sequence 1 (FFFF)
[00:23:44.921] no response to any known code

And here is what happend when I tried it with ecuunlocker running:

[00:01:02.375] Version 1.29.906
[00:01:02.375] 8 memory models read.
[00:01:03.437] 140 ROM metadata models read.
[00:01:03.437] checksum module "subarudbw" loaded.
[00:01:03.437] flashing tool "wrx02" loaded.
[00:01:03.437] flashing tool "wrx04" loaded.
[00:01:03.437] flashing tool "sti04" loaded.
[00:01:03.437] flashing tool "sti05" loaded.
[00:01:03.437] flashing tool "mitsukernel" loaded.
[00:01:03.437] flashing tool "mitsukernelocp" loaded.
[00:01:03.437] flashing tool "mitsubootloader" loaded.
[00:01:16.625] sending init sequence 1 (0001)
[00:01:19.859] sending init sequence 1 (0003)
[00:01:23.093] sending init sequence 1 (FFFF)
[00:01:26.343] sending init sequence 1 (F0F0)
[00:01:29.078] no response to any known code

notice the extra init sequence. Im happy it made a little progress but it seems far from working. Crazy stuff I wonder if the cable is messed up? I know it would be one in a hundred chances but I really dont think Im missing anything. Thx again for the help MJ

by **cboles** » Thu Oct 05, 2006 2:36 pm

The cable verifies that is correctly transmitting bytes via the self loopback nature of the K-line, so you can be pretty sure it is transmitting what it says it is without error. The only other place where things could go wrong is in the boot signal on the white connector. This should be pulsing to ~16V during each code that is attempted. You might tap into this wire somewhere to verify that that is happening, although we do test every cable in house be they are shipped.

by **lefty** » Thu Oct 05, 2006 2:42 pm

thx colby Ill break out my Multimeter and get back toyou

by **lefty** » Thu Oct 05, 2006 2:50 pm

spot on colby although it was ~-16 then went to ~-4 im assuming I just tapped the wrong one on the white connector. it fluctuated every second or so. I grounded my neg terminal. Hmm

by **cboles** » Thu Oct 05, 2006 2:54 pm

it goes back down to 4.5V that's normal. it really seems like everything is functioning correctly.

by **lefty** » Thu Oct 05, 2006 2:57 pm

lol thats not what I wanted to hear hehe. Does the openecu 1.8 version support evo IX? If so would you do me a favor and send it to my email or link? I would like to give the ecuunlocker a try on version 1.8. Thanks agian friend for the help you rock

by **cboles** » Thu Oct 05, 2006 3:10 pm

what is "1.8" - never heard of such a version. the Evo 9 has been supported for a while now.

by **lefty** » Thu Oct 05, 2006 3:21 pm

Malubujacks ecu unlcker says it is compatible with version 1.8 IIRC.
Ill stop cluttering up your boards and send you a pm

edit* I misread it says ecuflash 1.28 sorry

by **MalibuJack** » Thu Oct 05, 2006 3:31 pm

Sadly it doesn't look like anything is wrong with the cable, software, etc.. Is there another Evo you can at least test it with to be certain it can read ANY ecu? This way you can rule out your laptop and cable.

From the inits, its definitely working, and obviously 1.29 still responds to the unlocker, so thats okay too.

by **lefty** » Thu Oct 05, 2006 3:39 pm

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

by **cboles** » Thu Oct 05, 2006 4:01 pm

either there is still some trouble with the K-line on your cable or in the car wiring, i think. it would be good to try it on another car, or also try someone else's cable, if you have access to one, figure out where the problem lies.

colby

openecu.org

problem reading ecu "no response to any known code"

problem reading ecu "no response to any known code"

Who is online