It’s possible to use a VAG-COM cable with Subaru FreeSSM software?
Probably yes if you have good luck!
Look here: reviews of FreeSSM working with VAG-COM
Vag-Com cable (FTDI) and FreeSSM: Worked
Working on a 2011 Outback. I have a Vag-Com cable (FTDI) and FreeSSM. I can connect to the ECU but not the TCU. I am trying to trouble shoot the problematic CVT. It has a hesitation when you take off in D. When you are in Manual mode no hesitation.
VAG-Com Cable with FTDI chip and FreeSSM: Worked
I’ve ordered a VAG-Com Cable with FTDI chip to use FreeSSM. After some researches, I’ve found the following compatible models:
Legacy®/Liberty®/Outback®/Baja®, Impreza® (incl. WRX + STi), Forester®, Exiga® and Tribeca® starting with model year 1999 up to model year 2009.
Model year 2010 is already supported, too, but some Measuring Blocks may be missing and some Diagnostic Codes may not be displayed as plaintext.
KKL VAG-COM 409.1 interface and FreeSSM: Worked
FreeSSM Works for me with a KKL VAG-COM 409.1 interface. Windows 7 & 64bit Dell i7
I found the code the dealer missed.
So far no luck connecting with ECUFLASH or Rom Raider.
It ran about 30 miles before going into limp mode. ( S).
It was amazed that Subaru program can be reprogram in so many ways. And in so many steps on each of the ways.
My goal is to tune this engine via Program tweaking.
I have Noted that ECU Flash show many features that can be disabled for off road use. ( One has to wonder what gains or losses you might get by doing that on a stock setup.)
VAG-COM cables with a CH340 chip and FreeSSM: NOT work
I purchased a VAG-COM 409.1 cable and have wasted many hours trying to get this to work using FreeSSM within Wine ( virtual Windows ) on my MacBook Pro running Sierra OSX.
Unscrewed the VAG-COM adapter to verify the chipset with a magnifying glass and sure enough… its a CH340 chipset inside and NOT FTDI.
I cannot see the chip (serial number) from the Terminal command ( ls tty* )
As freessm_user indicated on Page 50 of this thread:
… you definitely need a VAG-COM cable that uses the FTDI chip for FreeSSM to work. When buying a cable, make sure the vendor guarantees that it’s the FTDI chipset. Many VAG-COM cables now come with a CH340 chipset, which will NOT work.
Hoping to read fault codes from my UK model Subaru Outback 2010 2.0 Diesel
KKL VAG-COM 409.1 OBD2 cable and FreeSSM: No success!
I bought a “KKL VAG-COM 409.1 OBD2 II OBD” cable from eBay UK here: Auto Diagnostic Tool USB Cable KKL VAG-COM 409.1 OBD2 II OBD VW/Audi/Seat/Skoda | eBay
and have tried to use it with FreeSSM (and romraider logger, but don’t know if i’m using that right) with no success – test connection fails, and trying to read from ecu results in the message “No or invalid answer from ECU”. All that happens when i plug it into the car is the red light on the dongle lights up, but nothing else.
The FTDI driver deems to have installed ok on my windows 10 laptop, and i am using the correct COM port in FreeSSM.
K-line or kkl line and FreeSSM: should work!
I have a simple K-line or kkl line vag-com cable. Which has a USB connection (though being cheap it still has an official FTDI usb to serial chip). It worked on my 99 impreza and on my 2009 (CAN) OBW using FreeSSM. I think the CAN bus cars still use the SSM for their own protocol.
I think the sampling interval on the SSM channel is higher than on a CAN bus, though CAN bus can have a higher through bitrate.
So honestly any VAG-com kkl-line or k-line cable should work.
KKL with CAN bus cars: Works
In mine 2009 EURO OBW it does, I can use FreeSSM and ECUedit and Romraider with the KKL line cable from deal extreme. (the same for my non-CAN, non-OBD2 1999 euro impreza.
Subaru decided to light up the dash like a Christmas tree on the newer models with even a non critical P-code CEL is detected by the ECM.
You can use FreeSSM / Romraider / TorquePro / or any other basic OBDII scanner to pull the codes.
Unless that is a manufacturer specific engine code, you will find out when you try to scan.
Anyway on the topic of a good Vag-Com cable:
Yes they are listed as VW/Audi – hence the nam VAG (Volkswagen Aktiengesellschaft)
A: Aktien “shares”
G: Gesellschaft “society”
Regardless they work on Subaru as well, but only for scanning, not flashing.
Of course there are exceptions to this rule depending on year of Subaru but that’s besides the point.
The trick is to find a cable with a authentic FTDI chip.
Find one with the real FTDI FT232RL chipset. (not fake copy)
Most of the cables out there now do not have the real FT232RL chip anymore.
See what you can find near you.
Here is a cheap cable with FTDI FT232 in the USA that is confirmed to well with FreeSSM:
It works for Subaru from year 2000 to 2009 incl. Impreza, Forester, Tribeca, Liberty, Baja, Outback
Working with FreeSSM 1.2.5, the cable has the possibility to execute TCU resets (e.g. for the check engine lights), as well as to display real-time data for various measuring blocks and to perform all sorts of system tests for various components of the engine: the fuel pump, the radiator fan or the air suction valve, to name a few.
The functionality of the software can be truly evaluated by professional mechanics and car engineers, but it is said that it can easily replace more complex monitoring tools e.g. the Subaru Select Monitor. While the latter is a paid option, FreeSSM is an open-source project and can be used commercially free of charge.
And more introduction and images I found on their blog: http://blog.obdii365.com/2016/06/09/review-on-subaru-freessm-v125/
Just trying plug and play or using the drivers that come with the CD is a waste of time. Decide ahead of time which USB port you will use and don’t try moving around to another port later. Connect the cable to your computer only and you will get the standard Windows is looking for drivers… message without any ultimate success. Let that run its course then restart.
Hold down the Windows key and press Break while you are on the desktop to open the option to manage devices at the top left. With any luck, you should see FT232 USB UART listed. The 232 chip is apparently one of the few that work with the software. If you don’t see it, your cable is probably not compatible. Of course, you still don’t have a workable driver installed yet.