Hi, glad you like the program!

SSM isn’t an OBD2 protocol, so is not directly supported by Torque, however having learned that OBDKey supports talking, I did have a look around and managed to find a protocol document for SSM, so I have the information to be able to have a go at it.

Subaru now support OBD2, at least in later models from what I have read, which would imply that SSM is going to be a dying/sidelined protocol. I’m not actively going to persue developing it due to not having access to a Subaru for any continuous length of time (I wish it was as simple as looking at a document, writing some code, and publishing software!!)

At the moment, you’re out of luck I’m afraid, but I am not ruling out support for SSM or other protocols if the situation changes.

Regards,

Ian

Hi Ian, I think this may be related to the OP’s question but there is a very strong open source community that supports ECU reverse engineering for Subarus.

Refer to Romraider.com for more information.

The result of all their work is a very efficient logger that uses XML ECU definitions to build logging profiles for each supported ECU. These definitions are available here -> http://www.romraider.com/forum/viewtopic.php?f=8&t=1642

These definitions provide several things, but not the PID unfortunately. I suspect the logger uses a different protocol to communicate over OBD2.

Here is an example:

parameter id=”P2″ name=”Coolant Temperature” desc=”” ecubyteindex=”8″ ecubit=”6″
Address 0x000008
conversion units=”C” expr=”x-40″ format=”0″ gauge_min=”-20″ gauge_max=”120″ gauge_step=”20″

The Address is what concerns me as this looks like a memory address rather than a PID.

Is this something that Torque could include or is the protocol/method of logging this just completely incompatible (or too much work)?

Thanks,
Mike
Melbourne

To be honest, I don’t mind implementing the protocol – thats not much of an issue (though I don’t like poking around in ‘memory addresses’ in an ECU).

The main problem is testing – I don’t have a Subaru to develop on so the ‘getting it to work’ is going to be somewhat difficult initally 😉

I might release a test app, seperate to Torque to begin with, purely for SSM so I can release it to a few people that are ok with testing, as long as it’s understood by the tester that it is at own risk – ‘It broke my Subaru’ (which is unlikely but can’t be ruled out happening)

At the moment, for at least a month, I can’t work on this as I have a fair amount of other things to do in Torque, and the New website(s) supporting it. Once they are out of the way and I have the next update out of the way with, then I will be able to think about extra protocols (it would be cool to support SSM)

Ian

Please please please support SSM. Your app is by far the best of its kind but I can’t use it because of the SSM barrier. I even bought the paid version and a transmitter only to figure out my car is ssm (nothing an obdkey and your app cant fix!)

I’m in the same boat.
Ive got the Australian 2001 Subaru Liberty RX 2.5 and still waiting for some sort of SSM Support.

I’ve got OBDKey (which cost a fair bit I might add) and the best I get is ‘Connected’ and a few random sensors that are clearly wrong.
(constant 40 deg c exhaust temp for example, and -40 deg c coolant temp)

I’m aware SSM is in beta status, but as far as I can tell it’s got nothing. Beta implies there is something to test does it not ? NOTHING works, period.
I guess what I’m trying to understand is what was expected to be accomplished by adding SSM when nothing in it works?
It seems quite a few of us went out and bought the OBDKey adapter (as specified in the app) and now have nothing to show for it (except being a little shorter on cash).

Frustrations aside, I really do love the app, and I really hope someone gets it working (hell, at this point I’d settle for a tachometer).

Thanks for the quick response!

So here’s what I’ve done:
1) Issued the appropriate command to initiate SSM mode on my OBDKey (via Telnet on a laptop – can’t remember the exact command)

2)Set SSM as the protocol in the Vehicle Profile

Now when I start Torque, it loads with the Tachometer reading 0, though sometimes randomly jumps to 16 or something like that every now and then (definitely not in response to actual revs).

In the realtime information:
Revs: 0
Throttle: no data
Speed: no data
Boost Sometimes randomly sits on -29.9 (which is interesting considering I have no turbo)
Coolant: -40deg c
And the figure I pulled in my previous post: 40 deg c Exhaust temperature

So from what you’ve said, SSM must be completely different in the PIDs that it uses?

This is all with the car on (running), and i’ve tried most of the workarounds and fixes in Torque (although I assume they mostly are all designed to work for OBDII – just thought id try)

I’m willing to be a Guinea Pig if you need, though my understanding of PIDs and ECU protocols is pretty much non-existent.

Oh and I should also mention in “Adapter Status”, there are no errors.

Again thanks,
Derryn

Ok, done.

Awesome, will do!

Ok, done!

I believe I used the commands on this page: http://www.mympgtracker.com/support/lbf/topic/9/ It was a while ago but im pretty sure thats what I did.

So ATZ then press ENTER then ATSPC and press enter again.
Before that Torque wouldn’t communicate with the device full stop so it must’ve been right.