Page History

LINKS:  [Tech stack meeting minutes]

...

The Technology Stack development is one of three main tracks of  the Common Vehicle Interface Initiative

...

1. To get consensus around terminology and parts to develop we need to revise this in diagram and text form.  2
2. This page outlines the goal, as well as some and challenges to reach pluggable software components, to be used in a shared reference architecture , as well as reuse into various companies own systems, that seem to vary somewhat.but also possible to use in different variants that companies may come up with.
3. Agree on and then use Use the CVII Tech Stack Terminology to understand these component namesdesigns.  Of course, these terms are open to additional input.

A1)  Partial system diagram (primarily representing an in-vehicle, possibly a single ECU, but

...

terms are generic

...

and components could be reused in a different setup)

Source file for this diagram is here:  It can be imported into https://app.diagrams.net/ and edited again.

...

• VISS – Specification
                   WAII implementation (Go lang),
                   also (partially) implemented in KUKSA.VAL, and other?...
• SOME/IP () – ( via Franca IDL and CommonAPI).  Likely additional ways to implement a more direct VSS ↔ SOME/IP connection.
  
  • (Also WAMP exists, also via Franca+CommonAPI)
• MQTT – There exists VISS over MQTT defined in VISS specification, but not a plain usage where you use simple MQTT-subscription (with topics = VSS signals). 
  → see separate analysis page

Runtimes and Frameworks

This is a list of software projects that do somewhat more than just a "data protocol" but are still involved in defining data exchange.
Note: Some of these define their own protocols, or the protocol is hidden (abstract) behind the framework APIs.

...

• C++ seems to be requested.   There is also some mild interest in Rust in the industry, but so far it seems not strong enough to supplant C/C++ as the main choice.
• KUKSA has both done VISS implementations in C++, based on VISS v1 - needs to be updated to v2
• AOS includes a VIS(S) implementation in Go, based on VISS v1

   Details:

• VISS v2 server Planning / Work Breakdown page

2. Demonstration of VSC-based development

...

      A)  For individual message updates through protocols (VISS? MQTT, etc.)
      B)  For in-memory storage of multiple data points and possibly subsequent batch (image) transfer.

• Volunteers needed – see Planning / Work Breakdown page

Project Backlog – development project candidates

• VSS to Android Properties implementation (Code Generator).   It should likely introduce jinja2 template based generation, similar to the vsc-tools.  → Work breakdown page.
• VSS over MQTT (Starting point exists in IoTea impl. Develop full implementation, include access-control/security, and as a reusable component separated out from IoTea framework) → Work breakdown page
• VSS to/from Autosar ARA:COM XML format
• VSC to/from Autosar ARA:COM XML format
• Proper VSS to Franca IDL converter.  Status and remaining steps are in vss-tools/PR#6.

...