96-99 Legacy 2.5L DOHC ECU Discussion

[b3lha]

I've been looking at the later model SSM protocol posted by Calvin Cestari along with ecuexplorer. I'm confident that I can write a simple program to query the ECU. Do you have a computer with linux installed, or a knoppix cd or pendrivelinux or something like that?

Actually, before I write anything, do a couple of tests with the Hex Com Tool to find out what protocols your ECU speaks. See here for details: http://www.alcyone.org.uk/ssm/troubleshooting.html

First try OBD1, set the program to "1953 Baud, Even parity, 8 Data bits, 1 Stop bit, No flow control". Turn the ignition key to the run position and then send the hex command: 78123400 and see what happens.

Then try OBD2. set the program to "4800 Baud, No Parity, 8 Data bits, 1 Stop bit, No flow control". Turn the key off and then on again. Send the hex command: 8010F001BF40 and see what happens.

[bubba2533]

I've been looking at the later model SSM protocol posted by Calvin Cestari along with ecuexplorer. I'm confident that I can write a simple program to query the ECU. Do you have a computer with linux installed, or a knoppix cd or pendrivelinux or something like that?

Actually, before I write anything, do a couple of tests with the Hex Com Tool to find out what protocols your ECU speaks. See here for details: http://www.alcyone.org.uk/ssm/troubleshooting.html

First try OBD1, set the program to "1953 Baud, Even parity, 8 Data bits, 1 Stop bit, No flow control". Turn the ignition key to the run position and then send the hex command: 78123400 and see what happens.

Then try OBD2. set the program to "4800 Baud, No Parity, 8 Data bits, 1 Stop bit, No flow control". Turn the key off and then on again. Send the hex command: 8010F001BF40 and see what happens.

No, I don't have any type of linux.

I tried both of those with the Hex Com Tool and got nothing.

I sent what you told me to and how you told me and I got something like this:
TX>8010F001BF40<TX
8010F001BF40

I tried to get sawmill to work, but after I changed the Com port to the correct one it failed and did not work. I get this message "Is the Tactrix cable connected? Timeout expired, packet incomlpete."

And Lumber jack is unable to connect also.

EcuExplorer shows the Com port I am connected to, but the ecuQuery option is grayed out.

[b3lha]

Well, now we know what doesn't work! That's the trouble with being a pioneer.

I reckon your ECU can speak OBD2 protocol to this interface through the OBD2 K-Line (Pin 93). Or it can speak SSM to the old style interface through (pins 91&92).

I think the problem is that we are currently trying to speak SSM protocol to the OBD2 pin.

So for this OBD2 cable you need some software that speaks ISO OBD2. Have a try with the software on these sites, particularly the first one.

http://techdiag.co.uk/obdscantech/web/home.html

http://obddiagnostics.com/ProgWin.html
http://www.obd-diag.de
http://jdash.ludicrous-speed.com

The alternative, maybe more useful in the long run, is to put this cable aside for now and build an SSM cable instead. Then we can use software that speaks the SSM protocol. The "Version 2 USB cable" on my site should work, but you would put a 16 pin OBD2 plug on the end instead of a 9 pin Legacy Radio Harness.

[bubba2533]

Ok, I will try those programs next.

I believe my car still has the SSM connector also, I will think about getting a cable for that.

[bubba2533]

IT WORKS!

The first program you posted works. I downloaded the generic OBD-2 version. It displays things like:
-TPS %
-Load as a %
-MAF g/sec
-o2 Sensor Voltage For both sensors
-Speed MPH (I don't think it will work with my car cause it has a mechanical speed-o)

And a few other things I can't remember. I think I might try the Nissan specific one to see if it gives me more options. I know there are similarities between Subaru and Nissan so I hope it works for us on this.

Thanks,
Branden

[b3lha]

Fantastic. Good work. I guess that makes you our resident OBD2 expert.

[bubba2533]

Now we know that the cable I have can communicate with my car through OBD-2 Protocol.

What is the next step?

[b3lha]

To start with, why not make a list of what OBD2 software works and what doesn't. The ones already listed here and any other free ones that you find on the net. That would be good information to have.

What parameters can you read?

Can you read/reset error codes etc?

Can you take some screenshots of anything that looks cool?

Ultimately I guess we want to find some software that will allow us to download the ROM.

[bubba2533]

I am in the process of making a list of all the programs I have tried with the cable I got off of ebay.

Program List:

VWRX - Not work
EvoScan - Not Work (still looking into that)
OBDScanTech - Works
-Shows live data
-Clears DTC's
Diagnose - Not Work
JDash - Not Work
SawMill - Not Work
LumberJack - Not Work
EcuExplorer - Not Work (Displays the correct COM port the cable is connected to)
EcuFlash - Not Work
RomRaider - Not Work
Hex Com Tool - Not Work
Learning View - Not Work

[tecnicatech]

this was just posted on nasioc
http://forums.nasioc.com/forums/showthread.php?t=1736906
the guy over clocked the ecu to get the rev limmiter up higher

[bubba2533]

Ok, I am out of ideas now. I cannot find anymore information on my ECU. I have looked for hours to find something that relates and I have come up empty handed. If anyone has a lead on information or and idea where to look next I could use it.

Thanks,
Branden

[b3lha]

It's a shame that you haven't had more success. I expected more software to work.

I think the next step is to try a different type of cable. Your cable is standard OBD2 and is presumably communicating using the ISO 9141 K-Line pin. The next thing to try is a Subaru specific cable using the SSM pins.

Refer to this thread for the Subaru OBD2 pinout:
http://www.subiesmart.com/forum/index.php/topic,50.0.html

I suggest building the simple USB cable shown on my website. Just buy the FTDI cable and connect an OBD2 plug on the end rather than the old style Legacy Audio Connector. If you don't want to make it yourself, the Evoscan cable might work, I don't know what pinout they are using.

[bubba2533]

Ok, I found someone that goes to my college that has a Open Port 1.3 cable. I am going to try it out with EvoScan, and maybe all the other programs I have if he lets me keep it for a few days.

Wish me luck

[b3lha]

Good Luck. Can't wait to hear how it turns out.

[tecnicatech]

good luck I hope this works