On Mon, 28 Apr 2025 at 09:51, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Yes, hence my questions, are all of those hw interfaces used?
Mostly. I2C/I2S not as standard (although available for expansion modules). ETH, IR, PWM, Temperature, Touch, DAC, all no.
Thanks. I'll see if I can sketch out (my understanding) of the system I use Mac and Linux myself. I think the developers here are pretty mixes
amongst the three platforms.
Thanks.
Good to know :-)
Regarding data sets, I presume you mean CAN bus dumps? I have some for Tesla cars (roadster, S, X). Others typically maintain them for their own cars. People may be reluctant to share as the dumps may contain personally identifiable information (not just VINs, but also things like latitude and longitude coordinates of charging, parking, etc).
Ouch, fair point. Is there any glossary of ODB terms? Is it worth providing something to strip out such data (which begs the question how easy to locate it) for testing purposes? I've an ODBeleven, but I don't (normally) get to see raw data. I'm guessing prior to emailing it from my phone, the data is converted to some 'visual' format?
Having problems understanding you here. When you say ODBeleven do you mean OBDII (OBD 2)?
https://obdeleven.com/ Another ODB interface (bluetooth and phone)
Understood. That's down at the ("I've no screen space") level. I was thinking higher level? I'll ask Google.
If you are looking at vehicle support, the article on that developer page is the best starting point we have:
My thoughts, an opening? Give me a data set (cleaned or not) for an unknown car and I'll try to decode it to some (existing?) intermediate | display format. I'm quite happy bit twiddling at a low level. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.