Re: Acura TLX (1st gen)
Wow that’s fast. Here are the Acura and Honda connection profiles the Car Scanner app. With your new update, lots of cars should be supported
Screenshot | Screenshot |
---|---|
The community for drivers, technicians, owners, buyers, and enthusiasts
https://meta.cars.forum/
Wow that’s fast. Here are the Acura and Honda connection profiles the Car Scanner app. With your new update, lots of cars should be supported
Screenshot | Screenshot |
---|---|
Ran all the commands you sent. It does use protocol 7! Car Scanner uses that protocol and shows that it’s using 29 bit headers. Since it defaults to 11 bit, it should work on BMW’s (in theory)?
Is there a way to export the terminal session? Let me know if there’s anything else you’d like me to run.
I’m learning so much
Screenshot | Screenshot | Screenshot |
---|---|---|
. | . |
Waiting for the TestFlight build to be approved. Does your Apple ID email match your forum email?
A command sequence we can test in the meantime to confirm the TestFlight build will work. In a fresh terminal session (let it do its normal bootstrap; don't reset with an ATZ):
Code: Select all
ATSP7
0100
0120
0140
0904
And then either send me your scan logs db to support@clutch.engineering, or attach screenshots of the results of these commands here.
https://sidecar.clutch.engineering/help ... -scan-logs for how to export OBD scan logs from Sidecar.
Yes my email matches my forum email. Sent you the logs via email.
Also, out of curiosity, tried connecting to the BMW and it connects! Don’t think I saw any values populate but problem for another day
Screenshot | Screenshot |
---|---|
@sidbmw I've added you to the TestFlight build: 1.16.3 (179). Please accept the TestFlight invite via your email and install the app from TestFlight. Let me know if you're able to pull any parameters with this build!
Still don’t seem to be able to pull parameters. Also I see the app complain about subscription for scanpass expiring after 30s. Tried re-redeeming the subscription from the link you sent before. Doesn’t seem like that made an effect.
Looks like it’s defaulting to protocol 6. Sent you the logs via email.
Screenshot | Screenshot |
---|---|
Ah interesting, so the initial handshake is setting the protocol but it's maybe not getting a chance to latch fully. Here's what I'm seeing in the startup sequence:
Code: Select all
> ATSP7
OK
> 0902
NO DATA
> 0902
NO DATA
But I see later on you were able to poll 0902 and get the response as expected, so we might just need to give the scanner a chance to settle before giving up.
Oh! It's probably the header. Let me try that...new TestFlight build inbound.
Starbucks internet is slowwwwwww