Support for Outback 2011 TCU?

[Stumblinbear]

Is the lack of support for TCU on this software a limitation of the protocol, or because nobody has yet to work on support? I'm hoping to reset my AT learning using this, but connecting to the TCU doesn't appear to be possible. I'm a dev, so if this is something I can work on, I'd just need someone to point me in the right direction.

[Comer352L]

Details please.
Which model (year) do you have ? What kind of transmission do you have ? Which interface do you use ?

[Stumblinbear]

Uh. 2011 Outback. I'm using a Aidixun OBD2 KKL 409.1 VAG-COM. As for the transmission model, I'm not exactly sure.

[Comer352L]

Ah sorry, now I see you mentioned Outback 2011 in the title...

Your 2011 TCU very likely supports access via ISO-15765 CAN (only).
Your interface is a (K)KL serial pass-through interface. This interface type generally doesn't support CAN.
I recommend using a J2534-compatible interface with ISO-15765 support, such as the Tactrix OpenPort 2.0.
Most professional / expensive testers also provide a J2534 library.
In theory AT-command controlled interfaces with ISO-15765 support should work, too, and are cheaper.
Unfortunately they very often do NOT work as expected, because their firmware is usually not tested with anything else than OBD2...

[Stumblinbear]

Ah darn. I was afraid of that. Hoping I don't have to spend THAT MUCH on a cable (the Tactrix OpenPort 2.0), but it's probably cheaper than the mechanic would charge me. I'll have a look around. Thanks for the information!

[Stumblinbear]

I've got a Tactrix OpenPort 2.0, with the OpenPort 2.0 drivers installed (Showing as "Tactrix Openport 2.0 J2534 Vehicle Interface" in Device Manager), with the repo built from source, and it's not showing in the interface. If I uninstall the driver, it shows as a COM port (though it doesn't work).

Any idea as to why it might not be detecting it?

[Stumblinbear]

Update: I installed an older 32-bit version of Qt, built from source, and it recognized it properly. However, it's saying it doesn't support SSM1-protocol, nor SSM2-protocol via ISO-15765. Weird, because the product page explicitly says it supports ISO-15765. I can connect to the ECU, but not the TCU. Thoughts?

[Comer352L]

Which protocol is used for the connection to the Engine controller (using the OpenPort 2.0 interface) ? (see control unit dialog, bottom right)

Please create a debugging log:

• compile as "debug"
• start program from command line with "FreeSSM > debug.log"
• try to connect to the TCU
• exit program (on MS Windows, debug.log content will not appear before the program has finished)
  Then send me the log directly as email attachment (address: see "About").

Again, what transmission do you have (E-4AT, E-5AT, CVT) ?

[Stumblinbear]

I'll get that data as soon as I can, it might be a couple days. I've got a CVT.

[InsideLine21]

Any update on the Tactrix cable working with this vehicle? About to perform CVT work on the same vehicle and assessing options for connecting to the TCU.

Thanks!

[Stumblinbear]

I haven't been able to get that information, as my car had to go to the shop for a brake line replacement (sigh).