October 2022 All Member Meeting
April 2022 All Member Meeting
October 2021 All Member Meeting
May 2021 All Member Meeting
October 2020 All Member Meeting
May 2020 Virtual Technical Summit
November 2019 Technical Summit
May 2019 All Member Meeting
Looking at the CVII tech stack landscape (which includes input from multiple projects led by companies and organizations) I see a lot of diversity. Some diversity is good but it appears a bit disorganized.
Are current implementations too monolithic?
Can we build an ecosystem of pluggable components (as discussed many times), and in the process accelerate the creation of complete systems as well?
- Not a clear enough focus on reusable components.
- A wide diversity of programming languages and runtimes
- Not identifying what the requirements are for production-level code
- Not identifying where we have "formal" (defined/documented) interfaces as opposed to internal interfaces.
I'd like our community to start discussing some of these aspects to build a more homogeneous approach to the development.
(answer / discuss)
A) Have we agreed on the list of required components, their responsibilities and interfaces?
Tech Stack overview
B) What, in your view, are acceptable choices (and preferred choices)
for programming languages and runtimes:
|Today's ECUs||Next-stage ECUs (domain controllers, central computers)||Cloud (computers not in-vehicle)||Development tools, code-generators, converters etc.|
"Vehicle cloud computing"
(think about next-next gen)
|.NET, C#, ...|
|Haskell, Erlang, ...|
C) In existing architecture pictures (e.g. CCS), and framework implementations (e.g. iot-event-analytics/vehicle-edge/KUKSA.val, AOS) which interfaces:
- are documented ?
- need to be documented ?
- do NOT need to be documented (= internal / implementation detail) ?
Inspiration from these architecture pictures and other pages:
|Completion of technology definition / implementation|
|Component Name||Programming language / runtime||Required/consumed interfaces||Provided Interfaces|
|Kuksa.VAL:||Python||Uses various bindings, socketCAN, ...|
VISS-like interface also for writing data into KUKSA?
|VSS Feeder (multiple)||= StateStorage db interface||depends on input type (CAN, etc.)|
|State Storage||SQLite database||-||SQL|
|OVDS Client (ccs client)|
|Go||= StateStorage db interface|
|Go||Data in OVDS Database format|
|WAII:MQTT||Go||(internal, VISS-like communication)||-|
|WAII:WebSocket||Go||(internal, VISS-like communication)||-|
|WAII:HTTP||Go||(internal, VISS-like communication)||-|
|OVDS Database||SQLite. Probably should be production-level time series database|