On Mon, 28 Apr 2025 at 03:35, Mark Webb-Johnson < mark.johnson@network-box.com> wrote:
Dave,
We have:
https://www.openvehicles.com/developers
as a starting point,
which provides a basic system hardware diagram, though it's rather heavy on acronyms! Are all parts used? A-D & D-A, encryption, touch sensor - I'm guessing this diagram is from the makers literature?
and the developer’s guide:
https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi...
has detailed information on each hardware component.
But I’m not aware of any system / software architecture diagrams.
I had hoped for a modular structure to see how the sw interfaced, perhaps to pick up on some lesser parts to get into it. I worked with low level stuff 40 years ago, asm and C. More recently Python and scripting on my Fedora box. What sort of development environment do you use please? Are there data sets available for different cars for testing? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.
Dave, Answers inline below. Regards, Mark
On Mon, 28 Apr 2025 at 03:35, Mark Webb-Johnson <mark.johnson@network-box.com <mailto:mark.johnson@network-box.com>> wrote:
Dave,
We have:
https://www.openvehicles.com/developers
as a starting point,
which provides a basic system hardware diagram, though it's rather heavy on acronyms! Are all parts used? A-D & D-A, encryption, touch sensor - I'm guessing this diagram is from the makers literature?
The diagram you refer to is the ESP32 microcontroller we use. I was referring more to the other links on that page (Developer Guide, Source Code, Getting Started Vehicle).
and the developer’s guide:
https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWEi...
has detailed information on each hardware component.
But I’m not aware of any system / software architecture diagrams.
I had hoped for a modular structure to see how the sw interfaced, perhaps to pick up on some lesser parts to get into it. I worked with low level stuff 40 years ago, asm and C. More recently Python and scripting on my Fedora box. What sort of development environment do you use please? Are there data sets available for different cars for testing? Are all the devs working on Windows please? All the docs seem to imply a windows environment?
Windows toolchain is on page #6 of the developer guide. Linux and Mac OSX is page #13. I use Mac and Linux myself. I think the developers here are pretty mixes amongst the three platforms. 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).
regards
-- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.
On Mon, 28 Apr 2025 at 09:18, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
The diagram you refer to is the ESP32 microcontroller we use.
I was referring more to the other links on that page (Developer Guide, Source Code, Getting Started Vehicle).
Yes, hence my questions, are all of those hw interfaces used?
Are all the devs working on Windows please? All the docs seem to imply a windows environment?
Windows toolchain is on page #6 of the developer guide. Linux and Mac OSX is page #13.
I use Mac and Linux myself. I think the developers here are pretty mixes amongst the three platforms.
Thanks.
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? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.
On 28 Apr 2025, at 4:38 PM, Dave Pawson <dave.pawson@gmail.com> wrote:
On Mon, 28 Apr 2025 at 09:18, Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@webb-johnson.net>> wrote:
The diagram you refer to is the ESP32 microcontroller we use.
I was referring more to the other links on that page (Developer Guide, Source Code, Getting Started Vehicle).
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. All the rest, yes to a greater or lesser extent.
Are all the devs working on Windows please? All the docs seem to imply a windows environment?
Windows toolchain is on page #6 of the developer guide. Linux and Mac OSX is page #13.
I use Mac and Linux myself. I think the developers here are pretty mixes amongst the three platforms. Thanks.
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)? We don’t have any specific glossary of terms for these, but there are plenty on the Internet. The wikipedia article on OBD-II PIDs and accessing it CAN is a good starting point. https://en.wikipedia.org/wiki/OBD-II_PIDs If you are looking at vehicle support, the article on that developer page is the best starting point we have: https://www.openvehicles.com/developers (Getting Started Vehicle)
regards
-- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.
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.
Attached, markdown format plain text, a starter for ten glossary. HTH -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.
participants (2)
-
Dave Pawson -
Mark Webb-Johnson