Hi

I've just tried reading the rom from my car using ecuflash but it's not connecting to my ecu. Here's the log.

[01:09:38.047] Version 1.29.906
[01:09:38.057] 8 memory models read.
[01:09:42.013] 140 ROM metadata models read.
[01:09:42.013] checksum module "subarudbw" loaded.
[01:09:42.013] flashing tool "wrx02" loaded.
[01:09:42.013] flashing tool "wrx04" loaded.
[01:09:42.013] flashing tool "sti04" loaded.
[01:09:42.013] flashing tool "sti05" loaded.
[01:09:42.013] flashing tool "mitsukernel" loaded.
[01:09:42.013] flashing tool "mitsukernelocp" loaded.
[01:09:42.013] flashing tool "mitsubootloader" loaded.
[01:09:58.296] This vehicle interface does not support needed features.
[01:09:58.296] unable to connect to vehicle interface.

Any ideas?

Cheers,
Boon

 

Hi boony

In the options section, you sometimes have to de-select and reselect the port that ECUflash is connected to. Also has the car had an ECUtek? If so you will need the ECU unlocker software from activematrix, look for Malibujack on here and folow the link in his sig.

MB

 

Hi burgers

Car has no ECUtek - it's bog standard. I tried the ECU unlocker anyway just in cae but it made no difference.

I'm using v1.29a of ECUFlash which has no port option - it's auto detecting & displaying what appears to be the right thing in the bottom right hand status pane.

A few people seemed to have problems moving to v1.29 and I have v1.28 kicking around somewhere, I'm going to try that next. I've reinstalled the drivers/ecuflash about 5 times now to try to get it working but no luck as yet.

I'm sure it'll be worth all the grief when I finally get it working.

Cheers,
Boony

 

Hi

Thanks for the heads up about no port option in 1.29. I haven't actualy conected to the car with 1.29 yet so you may have saved me some headaches! It is worth the hasel and geting conected has not been one of them so far, usually getting the def file for a non USDM model is the hard bit, but if your a bit of a sad ba$tard like me you, might actualy like wading through a hex editor.

MB

 

No problem. What version of ecuflash are you using out of interest? I've tried 1.28 now but that doesn't work either. Nor do 1.28's drivers ontop of 1.29 of the software (which worked for someone on openecu) so i'm stumped for now.

I don't mind wading through hex, but how do you identify the maps? Is there a signature you're looking for or are you disassembling the code & reverse-engineering it?

 

Another thing, in Ecuflash, the cable is reported as a "FT232R USB UART A3001LCw" rather than an "OpenPort 1.3 Mitsubishi".... is this something to do with my problems?

 

You can't connect, correct?

That means you haven't been able to download your map, correct?

 

correct on both counts kapolani. can you help?

 

Sounds like you have a bad connection i would check pin 79 and make sure the wire is in good

 

Pin 79? Are you referring to the ECU here? I have the Tactrix OpenPort 1.3 cable - no pin 79 on there. It's new too - direct from Tactrix last week.

 

START UNLOCKER PROGRAM BEFORE YOU RUN ECUFLASH
LEAVE IT RUNNING! START ECUFLASH
DO NOT CLOSE OR EXIT THE PROGRAM UNTIL AFTER YOUR DONE WITH ECUFLASH

 

Cheers ant, I've already tried that but it made no difference.

 

Its pretty obvious the error your getting is due to the cable not being correctly recognized.

Yeah thats the OEM name reported by the chip..

Sounds like the drivers didn't install, and if you have the wrong hardware ID for the cable, the Tactrix driver wont install. E-mail Colby, its possible the chipset in the cable was not sucessfully updated with the id for the cable.

 

Pin 79 is the pin the ecu uses when you flash your ecu. Disconnect pin 79 and it tells you exactly the same error your getting now. The wire runs from the ecu through the harness to the obdII port.

 

Hi boony

I have used 1.27 and 1.28. Nothing as clever as diassenbly. I used the hex editor contanied in ECUedit. Yes I guess you could say I looked for a signature. I looked at the Hex for a known, similar map, then looked through mine for a smilar set of hex figures, I guess from your question, you'd worked that out already.

Where in the UK are you. I'm in Kent.

MB