RomRaider

hello guys and gals

pls help
i have a wrx 06
it has gone to a tuner , who is less than helpful to complete his task he was paid and assigned to do

anyway

now when i try pull my rom i get msg on pc saying
ecu id 14761539ff not found
my ecu is currently not supported

is there a way to undo his relableling /renaming


thanks
doug

It has a MerpMod tune applied if you are using Learning View
Should be easy enough to remove

hello
thank you for the reply and help .

what is morph mod and how or where do i find it ?

thank u again

hello
thank you for the help

i am still trying to understand what morph mod is ?
and how do i use it

sorry for the stupid questions .
i come from a bike back ground
this car stuff is quite new
thank u again

where do i down load morph mod , i cant find anything about it using google or the likes

the car is a 2006 wrx sadm
A8DH200O


thanks for the help in advance

Geez.

Well looking for merpmod instead of morph mod would definitely help your search (which dschultz did for you already).

viewtopic.php?f=37&t=10276

hello guys

this is the response i get from the ecu when i try read, or test write.
it wont allow me to "pull" a rom , so we can see whats been done or changed
any ideas ??


thank you
regards
doug
[12:48:51.168] Requesting Seed...
[12:48:51.213] Sending Key...
[12:48:51.258] interface close
[12:48:51.260] interface close
[12:49:13.106] using metadata XML ID A8DH200O from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Impreza WRX/A8DH200O.xml
which inherits XML ID 32BITBASE from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml
[12:49:13.106] ---notes for 32BITBASE---
2014/06/20 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
---notes for A8DH200O---
2014/05/22 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
[12:49:13.770] J2534 API Version: 04.04
[12:49:13.770] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[12:49:13.770] Device Firmware Version: 1.16.4769
[12:49:13.770] Device Serial Number: TAWWcohR
[12:49:17.036] kernel get version
[12:49:17.239] interface close
[12:49:17.253] J2534 API Version: 04.04
[12:49:17.253] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[12:49:17.253] Device Firmware Version: 1.16.4769
[12:49:17.253] Device Serial Number: TAWWcohR
[12:49:17.589] VIN read not supported
[12:49:17.701] interface close
[12:49:17.718] J2534 API Version: 04.04
[12:49:17.718] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[12:49:17.718] Device Firmware Version: 1.16.4769
[12:49:17.718] Device Serial Number: TAWWcohR
[12:49:17.879] SSM2 init
[12:49:18.026] SSM2 ECU ID is 14761539FF
[12:49:18.108] Requesting Seed...
[12:49:18.153] Sending Key...
[12:49:18.199] interface close
[12:49:18.201] interface close

Have you connected the green "test" connectors under the dash of your steering wheel before the read attempt?
It might be useful to create a switch instead of it if you plan to write the ecu frequently.

Ok so went to help out Doug and I could even pull the rom. Same issue.

Car in test mode successfully(green plugs) and the green connectors in the passenger side foot well(RHD). Still not luck. Even with software that can pull and wright over EcuTek'd roms didn't have success (this was my suspicion).

Can retrieve ecuid info but cannot pull or flash. My only other suspicion is that there is an issue with the odb2 port and not all the pins are making contact. I have had previously the same issue with guys who use Bluetooth dongles which mess up the pins on occasion. By reseating the ports pins has resolved this issue in the past.

Unless there is some other software(subauredit as eg) which can lock or mate to your tactrix to your Vin or ecuid ? But still then we should be able to pull rom with def or not and change from there..

Doug when your tuner is in town I would be interested to see if he's successful.

Regards

thank you guys for your input

kingchett i will look at my pins and try again

failing that , i will wait till and see if he can

thank u

doug

Try this...

Make a backup copy of the ECU definition XML for your old rom id.
Replace the ecuid in the XML file with the ID that EcuFlash is reporting.
See if you can pull the ROM and view the tables in it.

You might also need to change the internalidstring value in the XML to match what's on the car now.

I'm not certain this will work, but it's worth trying.