The Subaru SVX World Network   SVX Network Forums
Live Chat!
SVX or Subaru Links
Old Lockers
Photo Post
How-To Documents
Message Archive
SVX Shop Search
IRC users:

Go Back   The Subaru SVX World Network > SVX Main Forums > General SVX Babble

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 08-23-2012, 08:19 AM
Huskymaniac's Avatar
Huskymaniac Huskymaniac is offline
Uses the ignore feature
 
Join Date: Jul 2010
Location: Corning, NY
Posts: 1,872
Registered SVX
SSM for OBD1 and OBD2 SVXs

There were bit of this on two different threads and I have an update so I figured I would just start a dedicated thread to make this easier for people to find later.

As mentioned previously, I bought two cables from the evoscan folks. One cable is a two-headed usb to both OBD1 and OBD2. This cable is meant to communicate only over the SSM pins using the SSM1 protocol. What we verified was that the OBD2 cars built from 1996-1998 use the SSM1 protocol, not SSM2. However, the memory addresses for the parameters were all different. I also bought an usb to OBD2 cable for my Tribeca which is supposed to be able to communicate over either the SSM pins or the OBD2 pins. I have not tested if it can use either SSM1 or SSM2 protocol or just SSM2 protocol over those SSM pins.

Thanks to information provided by Phil I have been able to determine most, if not all, of the memory addresses for communicating with OBD2 SVXs using SSM1. I have both the ECU and TCU addresses now and will eventually work on the climate control unit too.

On software, I have only played with my SVX so I can't say anything about how well any of them work on either newer OBD2, non-SVX, cars or OBD1, including SVX, cars. However, many people have played around with these packages for these cars and I assume the work fairly well. The gray area was with OBD2 cars from 1996-1998, including and especially SVXs.

The evoscan software is really nice BUT it can't communicate with the TCU or any other unit besides the ECU. What is can do is communicate using SSM1, SSM2 and OBD2. It has a variety of memory definitions for OBD1 and OBD2 cars and I have updated that file with the definitions for OBD2 SVXs.

JECScan is pretty bare bones and appears to be meant for communicating only with SSM1 protocol. BUT, it CAN communicate with the TCU and, hopefully, the climate control as well as other controllers. It looks like this software might be able to also communicate using SSM2 but I haven't tried it.

The released version of FreeSSM can only communicate using SSM2 so it only covers Subarus built after 1998. HOWEVER, I am working with the author to obtain a development version of the software that can communicate using SSM1. This is a major undertaking for me as I am not up on the new compilers and development servers. It may take some time to get a version of this working on OBD2 SVXs but the software appears to be better than JECScan and has the ability to talk to the TCU and possibly other controllers as well.

As far as the definitions for the memory addresses of the various parameters, here is what I believe is currently working for OBD2 SVXs:

ECU: Battery voltage, speed, RPMs, coolant temperature, ignition advance, MAF, TPS, engine load, injector pulse width left and right, idle control valve duty cycle, all three O2 sensor readings (average, max and min), air/fuel correction left and right, knock correction, atmospheric pressure and manifold relative pressure. I think I also have all three O2 heater signals too but I'm not entirely sure.

TCU: Battery voltage, both speed sensors, RPMs, ATF temperature, TPS, current gear, line pressure solenoid duty, torque converter lockup solenoid duty, center diff solenoid duty, MAF, TPS source voltage and two digital IO bytes that I haven't completely figured out yet.

I have the definition files for both the evoscan and JECScan software if anyone wants them. I hope to eventually have the definition files for FreeSSM too. And one other note about software is that these programs have other capabilities besides just reading ecu and/or tcu data. The evoscan program, with the appropriate cable, can flash some of the newer ECUs. It looks like JECScan can get a ROM dump. But all I really wanted was an SSM reader for my OBD2 car and it appears as though I am well on my way to that goal. And all you really need is a $57 cable and, maybe, a $20 software package and you can get an SSM reader for any SVX.
__________________
Tony

1996 Polo Green Subaru SVX LSi, 168,XXX miles, Redline D4 ATF, Redline 75W90 gear oil, K&N HP-4001 Oil Filter, Mobil 1 5W50 FS (3qt) and 5W30 High Mileage (4qt) Oil Blend, Motul RBF600 Brake Fluid, AC Delco A975C Air Filter, NGK BKR6EIX-11 plugs, Centric Rotors, Power Stop Evolution Carbon Fiber Ceramic Brake Pads
2005 Gray Acura RL, 165,XXX miles, Redline D4 ATF with Lubegard Platinum Protectant, Mobil 1 5W20 High Mileage Extended Performance Oil
2009 Red Toyota Venza, 123,XXX, Mobil 1 5W30 High Mileage Oil
1992 Red Ferrari 348 ts, 82,XXX, Redline everything
Reply With Quote
 

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 01:29 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
© 2001-2015 SVX World Network
(208)-906-1122