Cars Forum

Starting a thread to figure out Acura TLX support.

Currently does not work with the Vgate vLinker BM+.

Based on the log file you sent me, it looks like the Acura isn't responding to the standard 0902 (VIN) command unfortunately. Going to look into whether there are alternate ways of fetching the vin.

In the meantime, you can set the override vehicle to your car if you've already registered your offline vehicle in your garage. Make sure your make is "Acura" and your model is "TLX" so that it maps to the https://github.com/ElectricSidecar/Acura-TLX repo.

We can try seeing if maybe a different ECU will respond the VIN for us.

In Sidecar, once you're connected to your car, navigate to Settings > Your scanners > tap your connected scanner > Terminal.

What the commands do:

1. ATAL: Allow long messages.
2. ATST32: Set the timeout to the default length.

ATAL
ATST32
0902
ATSH7E0
0902

Please share the results of each of the above here and then we can decide next steps.

I've ordered a Vgate vLinker BM+ and will have it on Monday to test to see if the hardware itself is causing the issue.

One thing to confirm: make sure your scanner is plugged in firmly (within reason!) because loose connections can sometimes result in failure to speak to the car.

WIll try this tomorrow! The scanner was plugged in pretty firmly and the "Car Scanner" (https://www.carscanner.info) app was able to read data and display in carplay as well. I'll try to dig into that app more to see if I can find how it's pulling data.

Ahh based on the logs you just sent it seems like the car might be speaking protocol 7 (ISO 15765-4 CAN (29 bit ID, 500 kbaud)), which Sidecar doesn't support yet. I'll start looking into that now.

In the meantime because it might take me a couple days to get this support added, if you can try the following from the terminal that would help me confirm that the car is only speaking protocol 7:

Command meanings:

• ATZ: Reset the scanner state (the terminal sessions always pin to protocol 6 right now)
• ATDPN: Print the protocol number.

ATZ
ATDPN

If the response from ATDPN is A0 (meaning it's still searching), then run the following command sequence:

0100
ATDPN

Keep running this 0100/ATDPN sequence until you get a non-zero number. I have a feeling it's going to settle on A7.

To help with my testing of protocol 7, if you can also run the following:

ATSP7
0100
0120
0140

And share the results here, this should get the set of supported parameters on your vehicle. I'll use to write a test suite to make sure Sidecar's able to bootstrap your vehicle communication.

Alright we're cruising! 29 bit headers now supported and confirmed to decode packets correctly in CAN Decoder. Will send CAN Decoder out for review now and then start testing this functionality in Sidecar. I may need to make some adjustments to the OBD parameter signal definitions on GitHub to handle the new headers.

I've cut Sidecar/v1.16.3-179 for TestFlight. Will send you the invite to test within the next 24 hours once it's been approved by Apple.