[Help] Can't connect to my E6

[AlexEvo]

Well, I can't connect to my E6 RS2 ecu.

Of course I use OP2.0 cable and Ecuflash 1.41
The log is very short, and I get "interface closed" at the end.

I plug the cable to the car, and to my laptop, run ecuflash, clic "read from ecu" select the E5/E6. The pop up appears, i turn ign on and click Ok.... doesn't work. Ithink to procedure I use is ok, is there any "timing" to deal with ?

I have downloaded the ecu unlocker 1.1 from activematrix forum but I'm pretty sure the car haven't been "Ecuteked" before.

I have no idea :blushing:

[SPAWN]

I have the same problem i thought it was my cable but E5 works just fine.

http://www.geekmapped.com/forums/showthread.php?t=152


is this also the same log you had??



cheers


Waleri

[AndyF]

Alex,
There is currently a problem with flashing some E5's/6's at the moment but a patch is being worked upon for ECUFlash.

Andy

[AlexEvo]

Spawn, yes I get exactly the same log.

Andy, thanks for the info. When you say "flashing" you mean "reading and flashing" I suppose ?

[GrayW]

If you pop the case from the ECU and see if you have a 7202F of 7203F processor, the later has issues flashing. Did you try the read/flash process more than once?

[AlexEvo]

Yes I tried to read from the ecu about 10 times, because I was suspecting i don't use the correct procedure...

I'll try to check the processor asap

[GrayW]

Also ensure the black flash connector is making a good connection with the white one on the car.

[AlexEvo]

Well, my processor is a MH7202F
I check the connection (with voltmeter) between the flash connector and the white plug of the car: there's only one wire, and it's OK.

I'm a bit disapointed ... How can I check if the OP2.0 cable is ok ?
Maybe it's not the car but the cable ...

[GrayW]

Do you know anyone near with an Evo you can try it on?

[AlexEvo]

I'll try in a couple of weeks on an E8, finally I hope the cable doesn't work because I'm out of ideas ....

BTW, is the "procedure" (lauch ecuflash, clic "read", select vehicule, connect obd plug, connect reflash plug, turn ign on, clic ok) is very important to do step by step ? I've tried different ways but no difference ...

[GrayW]

Clicky (http://www.geekmapped.com/forums/showthread.php?t=68)

[AlexEvo]

yes, that's the way I do

[AlexEvo]

Ok, I sum up all test I've done:

- Ecu : Processor is a MH7202F
- OP2.0 cable: continuity is ok between OP2.0 "box" and the only wire which is connected to the cable through the flashing plug
- Run ecu unlocker 1.1 backwards
- battery voltage checked 12.5 v
- tested on 2 laptops, with vista and XP
- tested with the car running: by clicking on "ok" the car turns off but still the same message "an error has occured".

So ....

I plan to test the cable asap, on a subaru and then Evo 8.
Maybe the car harness is in fault ? Where does the "flashing" wire go ?
I have a cobra alarm on the car: of course it's desactivated but ???
What are your com port settings ?

Thanks for your help

UPDATE
I've decided to check the car harness between ports and ECU, according to the Evo 6 pinout (picked up on limiteless page):
Connection between OP2.0 flashing plug and ecu pin # 79 "ecu ignit signal" is ok
Connection between OBD port pin # 1 and ecu pin # 56 is ok
Connection between OBD pin # 7 and ecu pin # 62 seems to be cut

Can some experts tell me how far is it wrong ??

[AlexEvo]

Ok, so I make some new tests....

The OP2.0 cable is proven to be OK on Evo VIII
I plug a new wire between obd pin 7 and ecu pin 62

I try about 10 times, rebooting my laptop, and get differents logs :confused1:

First: see attached file "test1". I think it was close to work ... but no ...:angry:

And then (2nd try):
[16:04:04.850] sending init sequence 2
[16:04:04.850] got 0x11 response
[16:04:04.850] sending init sequence 3
[16:04:05.224] entering bootloader
[16:04:05.224] sending kernel size (1905)
[16:04:05.224] sending kernel load address (0x0000F000)
[16:04:05.240] uploading kernel
[16:04:05.552] verifying kernel checksum response
[16:04:05.552] kernel valid
[16:04:05.755] kernel get version
[16:04:05.755] kernel version is : OpenEcu Mitsubishi H8/539F Kernel V1.05
[16:04:05.755] reading kernel comm buffer size
[16:04:05.770] comm buffer size set to 256
[16:04:05.770] reading kernel flash buffer size
[16:04:05.770] flash buffer size set to 1024
[16:04:05.770] -- dumping ECU memory --
[16:04:10.840] rkrv: kernel response incomplete
[16:04:10.840] ECU memory read CRC failure.
[16:04:10.840] can't read image.
[16:04:10.840] interface close

I'm thinking about a bad connection. I can't understand why it seems to be ok and than fail, and after why it doesn't seems to work at all :angry: