Re: Acura TLX (1st gen)
Unfortunately donβt see a change Iβll send you logs later today
The community for drivers, technicians, owners, buyers, and enthusiasts
https://meta.cars.forum/
Unfortunately donβt see a change Iβll send you logs later today
Back from carting and augh I think I just noticed the problem. The handshake sequence doesn't include a warm start by default, so the previous ATSH from the protocol 6 handshake attempt wasn't getting cleared. I'm going to unwind the complexity of this 0902 polling and add a proper warm start new build inbound.
hahaha. Is that what caused the spamming of "0902"? Looked like that was being run every second or less.
I had put that in intentionally thinking that the ELM adapter maybe needed a moment to settle into the new protocol but I'm now realizing I just hadn't done the reset I thought I did when switching over to the new protocol. Some vehicles require an ATSH7E8 on protocol 6 (e.g. the Taycan) in order to respond to the VIN request, and I have a feeling that ATSH7E8 is messing with the protocol 7 vin request because ATSHhhh uses a zero-fill for the remaining 29 bit header.
New build uploading meow.
183 out!
IT CONNECTS! I don't see any values populating under parameters. Sent you the logs. Let me know if I need to send a different log
Awesome! Now the next layer of the onion to peel; need to update the header/response behavior to support 29 bit headers. This'll likely take me a bit longer to resolve as I think I'll need to make adjustments to the signalset definitions on GitHub as well.
Oh! To confirm: it's correctly reading your vehicle from the car now and enumerating the parameters in the UI?
No worries. I'll probably give it a try tomorrow morning if there's an update. Until then...interview prep
Thanks for your help today! Lots of progress