search

Comer352L / FreeSSM

GNU General Public License v3.0
207 stars 68 forks source link

ECU / TCU Communication Unsuccessful #68

Open seankowski-g opened 9 months ago

seankowski-g commented 9 months ago

First of all, thank you so much for your effort in creating this program.

My setup is a 2014 Subaru Outback with the VAG COM 409.1 KKL Cable. The cable uses the FTDI FT232RL chip with a virtual COM port. I have this setup running on a macbook pro with bootcamp dual-boot Windows 10. The cable is connected to my computer using a USB-C hub as those are the only ports it has. I am using debugging in MinGW to run the program.

I'm trying to figure out what the issue is that is preventing me from seeing the TCU data. I just want to see the transmission temperature as I perform a CVT fluid change.

I'm able to have a succesful interface test with a caveat message, but I am unable to connect to the ECU or TCU. Let me know if anything about my setup rings alarms for you.

image

MichaelWoodc commented 9 months ago

nothing rings an alarm bell so to speak, but, if you have another adapter, can you sniff the communication? Are you sure the USB hub can supply enough power that it isn't causing any issues? First I'd get a basic OBD program that works on a windows PC with your adapter. Move it to the MAC, test it with the adapter in the mix. Should take no longer than 10 minutes to do this "troubleshooting", it won't fix your problem, just help narrow it down.

You'll never know unless you can see the communication (or lack thereof) with your own eyes.

NOTE: Some macs have their own chips, right? We have tons of software that doesn't work with them. Older intel based macs were much more compatible with all of the windows things. This makes things even more complicated since someone else might have a mac and have everything working, and you'll have no luck.

in my IT program, every student who had a mac wound up buying a windows PC because they couldn't even help eachother out with some of the software and stuff we were using, since it was compatible on some and not on others. Its evidently confusing having arm in some and intel in others.

you could very well be dealing with the lack of drivers for the processor. I don't want to speak to soon and disuade you from getting everything working, but if you have apple's own chip see if there's the appropriate driver for that specific processor architecture.

What mac are you running? What processor?

Comer352L commented 7 months ago

My setup is a 2014 Subaru Outback with the VAG COM 409.1 KKL Cable. The cable uses the FTDI FT232RL chip with a virtual COM port.

Your TCU almost certainly talks via ISO-15765 CAN only. KKL passthrough interfaces do not support ISO-15765 (as the dialog explains). So you'll need a SAE-J2534 interface with support for this protocol.