96-99 Legacy 2.5L DOHC ECU Discussion

[bubba2533]

Could you point me in the right direction for those pieces?

Like this?
http://cgi.ebay.com/RS232-Serial-Port-To-TTL-Converter-Module-MAX3232_W0QQitemZ290288859240QQcmdZViewItemQQptZBI_Electronic_Components?hash=item290288859240&_trksid=p3286.c0.m14&_trkparms=72%3A1205|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A1|293%3A1|294%3A50

[log1call]

Something like that.
 
As far as I know that ecu may be readable by ssm as well as pbd2. Which software you read it with will dictate which adaptor you use.

That circuit may do the job. If it doesn't, we can adapt it to usb and then use other software. The other option is to build or buy something complex and then simplify/modify it to connect to your ecu on a bench.

 If you do not feel competent to make an adaptor then you should buy an adaptor cable that goes with the software you are planning to use.

See Phil's site, he has free software and links to cables I think.

[b3lha]

Given the age of your ECU, I suspect it will be OBD2, so that is the first thing to try.

The guys on the UKLegacy forum use this type of cable for OBD2 cars. It's a OBD2 cable for Volkswagens and Audis. The software that comes with it won't work for Subaru, but you should be able to download EcuExplorer instead.

FIXED LINK:
http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?ViewItem&item=230321771131

[bubba2533]

It is OBD2, anything that is 96 and newer is OBD2 in the States.

That link is dead.

 I would like to use the OBD2 port because 100% of the cars 96 and up have it, so I am sure the ecu I have should work in that way.

I have attached the wiring diagram for my ECU. It shows a few things that my list does not.

If someone could help me find all of the pins that need addressed when setting up my ECU on the bench that would help me out a bunch. I need to find out what pins need +12V and Ground and which ones that are going to be connected to the OBD2 port and so on.

Branden

[b3lha]

That link is dead.

sorry. fixed it now.

[bubba2533]

I read up a little bit on EcuExplorer and it says that it doesn't work with JECS ECU's. I'm guessing that is not true? To get EcuExplorer to work with my ecu would we have to find the parameters for my ecu first? Could EcuFlash flash a new ROM onto my ecu? Or is that still unknown?

[b3lha]

I read up a little bit on EcuExplorer and it says that it doesn't work with JECS ECU's. I'm guessing that is not true?

I don't know. All my experience so far is with older generation ECUs than yours.

To get EcuExplorer to work with my ecu would we have to find the parameters for my ecu first?

The first and most important thing to do is to find some combination of cable and software that will allow your PC to talk to your ECU. This may involve a lot of trial and error. Only when we can talk to the ECU, can we start to figure out what can be done with it.

Could EcuFlash flash a new ROM onto my ecu? Or is that still unknown?

There is a huge amount of investigation to be done before you can even think about reflashing anything.

[bubba2533]

Ok, so I am going to buy the cable from ebay that is for VW's. I am going to use my girlfriends laptop, because I don't have the money to buy one just for this right now.

I most likely will get EvoScan (I have looked at uklegacy.com and it seems like they have had success with it and the ebay cable so I will try that.)

I have already downloaded EcuExplorer and EcuFlash just tp play around with it a little.

I am really hoping one of these will work with this cable as I don't have the money to blow on a expensive tractrix cable.

If anyone has more information that will be helpful I could use it.

Thanks,
Branden

[b3lha]

I think you are on the right track. You've done the research and identified what is most likely to work. Now you have to bite the bullet and try it. Please be sure to come back here and document everything you do. What works and what doesn't.

[bubba2533]

Ok, so I just got my obd-2 cable in today. I am going to try to play around with a bunch of programs that read, flash, and such to see if any of them can communicate with my ecu. So far my list is as follows:
-RomRaider
-VWRX.com
-EcuFlash
-EcuExplorer
-LearningView

If you know any others please post a links so that I can check it out.

I hope that I will be posting some useful information after a weekend of fiddling, but we will just have to wait and see.

-Branden

[b3lha]

If you know any others please post a links so that I can check it out.

Also try this one for OBD2 ECUs: http://www.codeplex.com/ssm
And this for OBD1 ECUs: http://www.alcyone.org.uk/ssm/troubleshooting.html

[bubba2533]

Ok, I got the ROM ID = 464849

I really don't know how to get anything else. If anyone can give me a step by step of how to get a whole ROM dump off my ecu with what programs to use then I can do it.

Thanks,
Branden

[b3lha]

I don't think that's the ROM ID. 46 48 49 is ascii code for "FHI" Fuji Heavy Industries. It's what the OBD1 software sends to the ECU to instruct the ECU to send back the ROM ID.

What sort of cable are you using and what software?

[bubba2533]

I got that cable off of ebay, just like the one you posted. And i used the VWRX Select monitor dump to get the ID. Was that software made just for OBD-1?

I am not really sure where I should go from here. I would like to get something going on this as quick as possible. If you have an ideas of what I should try next please let me know.

Even if that is not the ROM ID then at least I know that the ECU is talking to my computer through the cable I bought. And right now that is a good stepping stone.

Branden

[b3lha]

See if you can get anything sensible from this software: http://www.codeplex.com/ssm

Also try ecuexplorer.

In the meantime, I'll read up on the later version of SSM protocol and see what I can figure out.