Open jmpolom opened 6 years ago
As the SSM1 support is in beta state it's unfortunalety not well documented yet. Also the differences between SSM1 and SSM2
In short: SSM2 vehicles (mostly from 1998 and upwards) use the commonly used K-Line / OBDII / ... adapters via CARB-Plug (common for OBD-II vehicles).
SSM1 vehicles are the older ones. You communicate by a TTL serial adapter with the yellow SSM plug. While there isn't an ordinary documentation you can get the pinout and more information about the interface at http://www.alcyone.org.uk/ssm/ports.html
If you're not sure which protocol you're using let me know about the car and the control unit you want to communicate with.
Pins 12+13 in the OBD2 connector are used for SSM1 RX+TX.
Checking the OBD2-connector of the car usually helps to find out which protocols are used (unused pins are missing).
I am using FreeSSM on a raspberry Pi (compiled for small screens) with the VAG KKL 409.1 USB adapter. It successfully connects to the ECU of my 05 Impreza STi and allows me to read codes, monitor variables, and reset memory, etc. However, it fails to connect to any of the other systems, specifically the ABS system (it gives a communication error).
On the wiring diagrams I see that SAE J1850 protocol is supported on pins 2 and 10. Do I need a connector that reads these pins to connect to the ABS?
Is it necessary to put the car into diagnostic mode (connect the green plugs) or some other trick to read these subsystems?
(Apologies for using the issue tracking for this question, but it was unclear where else I could ask the question)
am using FreeSSM on a raspberry Pi (compiled for small screens) with the VAG KKL 409.1 USB adapter. It successfully connects to the ECU of my 05 Impreza STi and allows me to read codes, monitor variables, and reset memory, etc. However, it fails to connect to any of the other systems, specifically the ABS system (it gives a communication error).
That's no surprise, because the software currently only supports communication with ABS controllers using the old SSM1 protocol. You will need a different interface for that (see above). Later models are using ISO-14230 (KWP2000) (pin 7) instead, which is a different story... Between ~ 2000 and 2006 both protocols were in use (depending on model, year, market, system manufacturer etc.), but KWP2000 is much more likely to be used in a 2005 model. Are pins 12+13 present in your OBD-connector ? If they are missing, you can be sure your ABS uses the new protocol.
On the wiring diagrams I see that SAE J1850 protocol is supported on pins 2 and 10. Do I need a connector that reads these pins to connect to the ABS?
I have never seen SAE-J1850 beeing used. Are you sure the pin numbering is correct ? Using a a mirror, pin 2 becomes 7 and 10 becomes 15, which would be ISO9141/14230 K/L-Line pins...
Is it necessary to put the car into diagnostic mode (connect the green plugs) or some other trick to read these subsystems?
No, that's not required. It doesn't affect the ABS and communication with the controller(s) should always work.
Hi. Do you think this adapter would work: http://www.obdii365.com/wholesale/mini-vci-for-toyota-with-toyota-tis.html (it says it supports "K-Line ISO 9141/KWP 2000 ISO 14230-4/SAE J1850 PWM/SAE J1850 VPW/CAN 2.0B ISO 11898 /CAN ISO 15765-4") If not, do you have a recommended adapter? Also can I confirm that I should be able to read airbag codes using the SSM1 pins and a FTDI FT232 TTL adapter and FreeSSM (2006 Outback)? Thanks.
Look on Amazon or eBay for FT232RL K DCAN, any of those will work.
Update: I guess it's actually VAG-COM
Found one, fast shipping too
Do not know about one you've found.
https://www.ebay.com/itm/303978194439 this one will work.
https://www.ebay.com/itm/303978194439 this one will work.
Much too expensive. You also didn't write which model/year etc. you have.
I also have a similar question, but the protocols are different.
2011 subaru outback cvt. Attached is the screenshot. I haven't yet compiled the sw, so cannot comment on that. I made my own cable (obdii to bb-elec usb2329m). SP210x at the db9. FTDI at the usb. I also have a two channel vector cancard xl, if needed. Thanks
The description of your interface design is vague / incomplete.
How is the interface connected to your PC and how does the software interface look like ?
Which diagnostic protocols does it support ? For a 2011 CVT, you need an interface with ISO-15765-CAN support.
Agreed. But you are light years ahead of me. As mentioned before. My son has totalled two cars in the last year and I'm just worn out. Basically What I'm trying to do is simply this:
As a side note, I appreciate your help trying to decrypt my scribbling and mess. Either way, I have taken your deiect source code and trying to build/comoile/install it for my application. All I can say is thank you for dealing with my zero knowledge of the subject matter.
Regards,
Kris BTW, after working in various aspects of vehicle development, validation, diagnostis, and manufacturing ( including EVs: Rivian & Bollinger Motors). Honestly, I was never a car guy and just recently switched to the defense industry. Somehow, tanks and armored vehicles seems more fun.
From: Comer352L @.> Sent: Sunday, August 13, 2023 8:42:49 AM To: Comer352L/FreeSSM @.> Cc: KrisK63 @.>; Comment @.> Subject: Re: [Comer352L/FreeSSM] Adapter to be used with FreeSSM (#20)
The description of your interface design is vague / incomplete.
How is the interface connected to your PC and how does the software interface look like ?
Which diagnostic protocols does it support ? For a 2011 CVT, you need an interface with ISO-15765-CAN support.
— Reply to this email directly, view it on GitHubhttps://github.com/Comer352L/FreeSSM/issues/20#issuecomment-1676348884, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBUCVU2OCTR3ATKAGMEL3UDXVDDUTANCNFSM4EMBWMCA. You are receiving this because you commented.Message ID: @.***>
Thank you, @Comer352L , for putting in the work to maintain a tool like this. I've done some tool dev for hardware-interfacing software and it can be a really monumental task.
I don't have a question. This thread answered it already. I bought a VAG-COM ("Generic OBD2 USB VAG-COM Scan Tool Cable FTDI FT232RL- Subaru Sk...") on ebay for ~$36. It arrives Monday. Then we'll see how well it works.
I have to clone an existing ECM for my 2003 Outback, which we apparently toasted while swapping engines? We're getting <=3V to a few sensors which should have 5V, and it seems to be causing the injectors not to fire.
A mechanic recommended FreeSSM to do the cloning. If this works, it will put an ends of a month long process of replacing the engine my kids let run out of oil. Praying for the best.
But I wanted to say thank you.
I read through the readme and a previous issue regarding the type of cable to be used between the PC running FreeSSM and the vehicle. Will one of the commonly available USB to OBDII type adapters work for FreeSSM? Help with SSM1 adapter seems to suggest you need a TTL serial adapter to communicate with the vehicle but doesn't really explain the pinout of the OBDII connector that you'd have to attach this to. What kind of cable is required?