does this software support ssm3

[yipperr]

hello

The car i am working on (subaru legacy edm 2011) with the ej204 2.0 cvt is a a canbus car that runs ssm3 version of the protocol , i got romraider to work on can mode and was able to use the logger portion to log a very limited set of parameters (it doesn't have the ignition retard or knock correction parameters that i am interested in to monitor). When i change the protocol in the romraider logger to "ssm over can" from "Can only" the software will not connect to the ecu and show some error, i also have to mention i am using a j2534 adapter with the romraider Software (the j2534 adapter is the one manufacturerd by setek called the "dice" popularly used with the vida software of volvo)

I downloaded a compiled binary of the freessm software from the Sourceforge website and it does not detect the j2534 device , even under the preference tab of the software there is no dropdown for j2534 adapters

so the questions are does this software support logging via j2534 adapters on windows 10 and does it support a 2011 subaru legacy edm with the ej204 engine , i have read that the engine ecu is a hitachi unit

also can you also explain what this software is based upon ? as in the origin of the source

thank you for your time

[Comer352L]

Don't use sourceforge, it's totally outdated and unmaintained. [*] Github is the official place where FreeSSM is hosted/developed.

The old version v1.2.5 doesn't support SAE-J2534-interfaces and SSM via CAN. You will have to compile the latest development code for that (see README.TXT). If your interface is not detected or the communication with the car doesn't work, compile as debug and send me the debugging output.

[*]: Initially FreeSSM was hosted at Berlios.de, which has been closed a long time ago. FreeSSM has been moved to Github, but Sourceforge took over the last version of the Berlios.de page. It is neither authorized nor maintained by me and so far I wasn't able to delete it. :/

[yipperr]

Don't use sourceforge, it's totally outdated and unmaintained. [*] Github is the official place where FreeSSM is hosted/developed.

The old version v1.2.5 doesn't support SAE-J2534-interfaces and SSM via CAN. You will have to compile the latest development code for that (see README.TXT). If your interface is not detected or the communication with the car doesn't work, compile as debug and send me the debugging output.

[*]: Initially FreeSSM was hosted at Berlios.de, which has been closed a long time ago. FreeSSM has been moved to Github, but Sourceforge took over the last version of the Berlios.de page. It is neither authorized nor maintained by me and so far I wasn't able to delete it. :/

thank you for your reply ,if it isn't to much trouble can you provide the latest binary of the file with debug enabled with j2534 support, i haven't really build anything in windows and never used QT before , so i wanted to save the pain of trying to figure it all out ,through a lot of build fails and error .

also do you have any source on what ssm really is ? is itsubaru specific obd2 pid ? or some sort of different protocol? , how has ssm changed from ssm3 to ssm 4 software?

thank you for your time much appreciated

[Comer352L]

If you are not able to compile the software, you will very likely also not be able to help debugging any problems that might show up. And what if you need to test patches ? Do you really expect me to compile the whole software for you each time ? Sorry, but that's not how it works.

[yipperr]

Thanks for the previous reply I finally compiled and ran the application with a clone dice unit (setek dice clone used by volvo vida diagnostic) and the software complained that the j2534 devices does not support ssm2 or ssm3 , there was a test in the software for testing the device and it failed saying no support for ssm2 and ssm3 and pretty much the whole software wouldn't communicate

A few question , i was under the impression SSM was just over CAN so why does this need a specific hardware support ? i don't think even the openport 2.0 is specifically advertised for ssm as its all just over the can protocol ISO15765 , so i am confused of how the freessm software is handling this

the unit is manufacturered by setek called the dice , the function libary is TSDiCE64.dll .Find below the logs from running the binary in debug mode

libpng warning: iCCP: too many profiles Found 1 registered J2534-libraries:

Name:        DiCE-206751
 Path:        C:\Program Files\DiCE\Tools\TSDiCE64.dll
 API-version: 04.04
 Protocols:   CAN ISO15765 ISO9141

Interface information:
  Firmware version: 5.6.2-Aug 22 2011 09:03:43
  DLL version:      6, 1, 0, 0
  API version:      04.04
Found 1 registered J2534-libraries:

 Name:        DiCE-206751
 Path:        C:\Program Files\DiCE\Tools\TSDiCE64.dll
 API-version: 04.04
 Protocols:   CAN ISO15765 ISO9141

libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
PassThruIoctl() for parameter LOOPBACK failed: error 7: Undefined error.
PassThruIoctl() for parameter LOOPBACK failed: error 7: Undefined error.
Error: selected protocol is not supported
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Found 1 registered J2534-libraries:

 Name:        DiCE-206751
 Path:        C:\Program Files\DiCE\Tools\TSDiCE64.dll
 API-version: 04.04
 Protocols:   CAN ISO15765 ISO9141

Interface information:
  Firmware version: 5.6.2-Aug 22 2011 09:03:43
  DLL version:      6, 1, 0, 0
  API version:      04.04
Found 1 registered J2534-libraries:

 Name:        DiCE-206751
 Path:        C:\Program Files\DiCE\Tools\TSDiCE64.dll
 API-version: 04.04
 Protocols:   CAN ISO15765 ISO9141

PassThruIoctl() for parameter LOOPBACK failed: error 7: Undefined error.
PassThruIoctl() for parameter LOOPBACK failed: error 7: Undefined error.
Error: selected protocol is not supported

[yipperr]

I should also add i used the same dice unit with the romraider logger , it works fine in default "obd over can" protocol which is default , but when you change the protocol in the logger to "ssm over can" and try to log more than one parameter the software complains about "ecu init failed Request type not supported. Command: A8 unsupported parameter"

note it only complains when i try to log more than 1 parameter , if only 1 parameter is sampled there are no errors and the values logged seem accurate , also to repeat the car is a subaru 2011 legacy European market (EDM) 2.0 NA with the CVT transmission with a hitachi ecu , i am looking to log for knock and ignition timing as from what i heard these cars are plauged with false knock issues from rattling avcs which causes timing to be retarded

thank you

[yipperr]

i think it is better to close this issue and start a new regarding the j2534 devices being reported as not supported