hi guys, i'm trying to remap a 2.0R

The 2.0R is the esquivalent as your RS but it's a european version with a 2L (no turbo). It's one of 2006-2007.

So i'm trying to dump the Eprom via the tatrix cable + ecuflash. The problem is that the car is not recognized. i tried with ecuflash new defs but no result. The interface closes before i succeed. I can try whatever you want, i got some knowledge.


see below what it writes:

http://img524.imageshack.us/img524/2730/sanstitrecq3.jpg (http://imageshack.us)

Thanks for your help.Math

Either you are not in test mode or you did not select the correct read method. You can use the 2005-2006 DBW FXT/OBXT/LGT/Baja read method. If you are entering test mode, then the radiator fans will cycle after a short period of time (when NOT reading/flashing). If it's not, then you need to make sure the green test mode connectors under the dash and possibly also in the passenger's footwell (by the ecu OR by the kick panel) are connected. Then you would disconnect one of the set after you are done reading (or flashing).

It also doesn't look like you are using the latest defs in that SS, although this would not cause a read to fail.

there's something i'm wondering: the defs are for reading the bin file (decoding) but not for changing reflashing method no? I did it with the green connector. I remenber that when i tried one of the car type (i tried all), the fans cycled but for the other, nothing happened. I'll retry. Thanks

The fans will not cycle if you are sucessfully reading/flashing with Ecuflash. So, disconnect the tactrix cable and turn the ignition to on with the test mode connectors connected. The fans will cycle if you enter test mode.

Yes, the defs are for tuning and the only other difference they would make are when flashing (the flash method). They make no difference when reading (other than at the end it will open for tuning), so you need to make sure you are selecting the correct read method. Another thing is that you should wait until the dialog box comes up indicating to turn the ignition to on before doing so and then you should immediately hit the ok button.

yes it's what i always do and it works for my sti 2006.I'll retry with new defs and will tell you if it works.

new defs won't solve your problem

ah ok. Can you explain how the reflashing process works? Cause i can't edit the reflashing method in ecuflash. What does ecuflash send to the ecu to make it be in reflashing mode?

Are you trying to read from the ECU or write (i.e. flash) the ECU? Read this:
http://www.scoobypedia.co.uk/index.php/Knowledge/EnginuityAndReflashingFAQ#toc10

If it can help.........

http://img248.imageshack.us/img248/5371/codebarrefj4.th.jpg (http://img248.imageshack.us/my.php?image=codebarrefj4.jpg)

http://img174.imageshack.us/img174/6835/procei6.th.jpg (http://img174.imageshack.us/my.php?image=procei6.jpg)

http://img209.imageshack.us/img209/9914/ext2vk5.th.jpg (http://img209.imageshack.us/my.php?image=ext2vk5.jpg)

http://img84.imageshack.us/img84/7497/ext3ci1.th.jpg (http://img84.imageshack.us/my.php?image=ext3ci1.jpg)

You shouldn't have an issue reading any DBW 05-07 impreza, even a Euro model, as far as I know. Problem is, there are many ways you can cause a read/flash to fail that is due to the user not following the proper procedure. They are listed in the link I gave you a few posts back. Since you did not respond to this, nor did you mention if you tried any of the recommended steps, there's not much I can do to help you. 99% of the issues can be solved by following the troubleshooting steps in the FAQ.

i can ensure you i know the procedure and did well. I also read your link and know it by heart. i've reflashed hundred times european subarus. I can't understand.

See below all the trial with different types. The last one gave a different result: but at least, the fans becomes ON

http://img441.imageshack.us/img441/8916/martyhu7.jpg (http://imageshack.us)

The radiator fans will NOT come on during a successful read/flash. They will come on when you are NOT in the process of reading/flashing as an indication that you are in test mode. The reason they did with the last try was probably because of the incorrect read method used. Regardless, if you've flashed hundreds of Subarus before and you've tried all the troubleshooting steps, then there's not much more to do that I can think of except maybe installing an older version of Ecuflash (1.29a) after uninstalling the current version and all tactrix drivers which seems to have worked for some issues for some users. You won't be able to use the new defs with the older version, though, but that ROM isn't supported right now anyway, so maybe you can at least pull it.

was probably because of the incorrect read method used.

yes i think so. I don't remenber the one i chose for this try. but Fans didn't come ON at the begining. It wrote 5 times "denso02......start" but finally they came ON..........so it may be a pb of reading.

I looked in engenuity defs and the ID 4344304006 is unknown. But these numbers are near WRX 2006......so maybe it's near.

4342584006: A8DH200Y WRX 2006 EDM SH7058 sti05 flash
4342594006: A8DH200Z EDM 06 SH7058 sti05 flash

However, can someone explain the difference for flashing methods according to each processor? How does it work? Can i help to find a solution? Who works on these defs?

Thanks

It makes no difference what defs you use since you can't even READ the ROM. The only defs that matter for reading are those contained in the "read templates" folder. There's nothing that can be added/changed to these defs that will do anything (there are only two valid read (flash) methods for the ECU you are trying to read: sti04 and sti05, with sti05 being the correct one for your ECU).

So, since you've tried the sti05 read method already, there are two possibilities remaining:

1. For some reason, your ECU is unique and cannot be read with Ecuflash (highly unlikely unless it is some early CanBUS implementation)

2. Something is wrong with your install, cable, or procedure for reading (have you used the same laptop/cable to read/flash other Subarus before?)

Is this an Impreza (you said it was equivalent to our RS)? If it is an 07+ legacy or forester then it cannot be read or flashed by Ecuflash currently.

yes it's an impreza, exactly the same as the WRX2006 with a different hood and no turbo (and other details). I'm thinking about a detail: It's a denso ecu on most cars but here it's an HITACHI!!!

No, it is supposed to be -> all the DBW Subarus use Hitachi (Renesas) hardware.

hello error is because the definitions need to read and programmed with ecuflash need your ecu appears on the list of definitions of the file "C: \ Program Files \ OpenECU \ EcuFlash \ rommetadata \ subaru ... .. and the folder: subaru 2.0r
if not ... 2.0r subaru folder. Most likely, there is no definition to read your ecu.
I have a subaru 2.0r Europe and have the same problem as you, the identity of my ecu is: 4344307006 my ecu data are AL241-6202.


You and I need to file for the definitions of our ECU
And are located in the xml files, greetings.

Actually the problem is we do not know the memory address where the maps of the ecu ecuflash when trying to access the ecu to read the data, memory addresses of the locations of the maps on file in xml definitions if not in our archive ecu definitions ecuflash can not read maps of the ECU and not write them, we can not take any other example of similar model, the memory addresses are unique and specific to the identity of the ecu greetings.
If someone finds something, please tell it,

The ROM doesn't need to defined in the table defs in order to read a copy of the ROM with Ecuflash (you just need to select the correct read method). If that were the case, we would have zero ROM support - sort of a chicken-egg deal. It is possible that this 2.0R uses an ECU that isn't supported by Ecuflash. Defs also would not help in that case.

The problem is that the car is not recognized. i tried with ecuflash new defs but no result.

The screenshot begs to differ. You are using ECUFlash version 1.33 - the latest version is 1.40 ;)

Uninstall the old version of ECUFlash you have as well as the tactrix drivers. Delete any left over ecuflash or openecu folders in your program files directory, then reboot and reinstall the latest 1.40 version.

The screenshot begs to differ. You are using ECUFlash version 1.33 - the latest version is 1.40 ;)

Uninstall the old version of ECUFlash you have as well as the tactrix drivers. Delete any left over ecuflash or openecu folders in your program files directory, then reboot and reinstall the latest 1.40 version.
The version of Ecuflash he was using wouldn't make any difference for reading/flashing pre-CAN models. Updating the defs would do nothing for connection issues. This is also a year old post that someone bumped.

lol my bad.

i didn't retry to read the 2.0r. I think its reading is not supported yet.
Finding defs once read is not a problem, i can do it.

I just had another thought - has this car had ECUTEK before?

never