openecu.org

by **saintspall** » Sat Apr 25, 2009 4:45 am

car was a 2005 jdm auto rex,i tried to retrive the rom file but keep getting error,could it be the previos tuner was using ecutek?

by **saintspall** » Sun Apr 26, 2009 4:42 am

Anyone?Could it be locked by ecutek?It keep showing error when i'm tryin to retrive the rom

by **radsdau** » Sun Apr 26, 2009 3:59 pm

I presume this is not DBW? If it is, the hookup method is incorrect.
Otherwise, ensure your car is going into test mode correctly; if fans do not cycle with key on, there may be a second set of green connectors to find and connect.
Also make sure the Line End Check connector has the jumper block connected; these will not reflash or read without it.

by **saintspall** » Sun Apr 26, 2009 6:56 pm

not dbw,there's only one set of green connector and i connect them.

by **saintspall** » Tue Apr 28, 2009 5:34 am

what happen when the car has been tuned before by ecutek?what will the log shows?

by **saintspall** » Wed Apr 29, 2009 7:17 pm

anyone?I tried again and i make sure all connection are there,even reset the batt,used a batt charger to make sure the voltage is there but it just cant work.Can the open ecu be lock?

by **jarencibia** » Mon May 11, 2009 3:27 pm

It could be locked by ecutek, I have the same problem in my 2004 usdm wrx. I just bought a 2005 wrx ecu, installed it today, and read the rom file with no problem. If I were a betting man, I would bet it's locked by ecutek. Here's what my ecuflash log looks like trying to read from ecutek.....

You can tell by the ecu id if it starts with 2E it's ecutek I believe.

17:42:50.281] Version 1.38.2080
[17:42:50.296] 11 memory models read.
[17:42:50.296] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[17:42:52.859] 320 ROM metadata models scanned.
[17:42:52.859] checksum module "subarudbw" loaded.
[17:42:52.859] flashing tool "wrx02" loaded.
[17:42:52.859] flashing tool "wrx04" loaded.
[17:42:52.859] flashing tool "sti04" loaded.
[17:42:52.859] flashing tool "sti05" loaded.
[17:42:52.859] flashing tool "mitsukernel" loaded.
[17:42:52.859] flashing tool "mitsukernelocp" loaded.
[17:42:52.859] flashing tool "shbootmode" loaded.
[17:42:53.015] flashing tool "shaudmode" loaded.
[17:42:53.031] flashing tool "subarucan" loaded.
[17:43:06.750] kernel get version
[17:43:07.312] SSM2 init
[17:43:07.515] SSM2 ECU ID is 2E 14 48 60 06
[17:43:07.687] Requesting Seed...
[17:43:07.812] Sending Key...
[17:43:07.906] interface close
[17:43:08.000] interface close

by **turbosetch** » Tue Jun 09, 2009 3:19 pm

All early WRX seem to have this issue I find with latest version of ecuflash and 1.3 universal cable, maybe others.

The trick that always works for me is as soon as you turn the key on start your read or test write. You will notice the fans won't come on etc once your reading/writting. If you wait even a second to long you will get the problem of not being able to read/write.

by **WAYNE WRX** » Wed Jun 10, 2009 1:16 pm

I have the 2.0 cable and the above post is the way it only works on mine too, and mines a WRX STI WR1

You have to be quick

openecu.org

can't retrive rom file

can't retrive rom file

Re: can't retrive rom file

Re: can't retrive rom file

Re: can't retrive rom file

Re: can't retrive rom file

Re: can't retrive rom file

Re: can't retrive rom file

Re: can't retrive rom file

Re: can't retrive rom file

Who is online