Page History

[ Permanent link:  Tech stack overview ] 

Minutes are now stored in COVESA Wiki

...

Wednesday 2021-10-13

From now on, refer to COVESA Wiki

...

• VSS-tools,  A bit of additional progress in Android Automotive Vehicle Properties  (VHAL code-generation)  (Follow along in code_generation branch in vss-tools (and Manu's fork))
• Discuss possible automatic unit/scaling 
• Time-series database implementation, see CVII Tech Stack
  • Discussion with Stephen/Renesas about this point. 
• Stephen: There is a dataset that exists from previous demos.  (Values and timestamps) that could be used as data (after aligning it to VSS standards)
• Stephen (sharing screen): Many values look like Snapshots ( according to this definition), i.e. several signals measured the same time.
  
  • Gunnar:  Yeah, the snapshot format suggests to only store the timestamp once, if it is measured at the same time. 
  • Gunnar; Note "same time"/simultaneous might include a short time interval since the meaning of simultaneous is a bit sketchy in a discrete system.
• Tom: You can also reduce size of time stamps by transferring a delta-time compared to some reference.  
• Gunnar: Good point, worthy of adding a note to Data serialization / value formats page.
• Reminder: Register for AMM if you haven't. 

...

• Several vacation/apologies this week from Bosch, BMW, ...
• Project updates above, for those that are available
• Catch up with Artem regarding AOS issues
  • See above
  • Also working on modularity - identifying components for reuse.
• VSC and tools
  • → synergy opportunities with gRPC support in KUKSA.VAL?
  • Let's discuss "decisions" taken during this development → how to find consistency with the VSC-related work (which intends to integrate gRPC and other technologies as needed).
• Awareness:  CVII-TS: Binary encoding for VSS-based data transfer
  • → synergy opportunities with gRPC impl. also here?
  • Artem: We have seen some problems with binary encodings, so JSON mostly for now, which is adequate for a lot of the needs at the moment.  We see potential need (for binary efficient encoding) however.
  • Sebastian:  For gRPC we replace some of the JSON protocol parts of course, but data encoding is often still using strings for simplicity at the moment.
  • Gunnar: OK, I conclude this is still important and interesting to together define one or two canonical binary encodings for VSS.
• Updates/discussion on other priority-list projects:  
  • VISS v2 server Planning / Work Breakdown page
  • Needs a proper "need"/request for resource allocation.  Discussion on if current development frameworks (using python, NodeJS and other) are acceptable in in-vehicle embedded space or if this need actually does  exist already.
• Android AAASIG update
  • Plan to start implementing VSS to AOSP translation - WBS using a combination of VSS-tools examples for reading VSS and VSC-tools examples for code generation using jinja2.  Bittium is  leading.

...

• Introductions (Artem's first meeting)
• Brief discussion on AOS (principles, not the technology).  Embedded parts are planned to be open-source.  Process ongoing (outlook - a few months).
• Artem to give AOS architecture/tech overview next week
• Artem mentioned Android HAL using a VISS-protocol external server was implemented and shown by EPAM a few years ago.  
  • Gunnar:  So this was before AASIG was started...  It is good input, although current work has considered GraphQL as the protocol for the internal VSS-data server.
  • => Artem to provide a link to the published code.
• New table-based tracking of wanted/expected/missing tech stack components was added to the CVII Tech Stack overview page   Feedback/changes welcome!
  • This could drive priority discussions also
• Sub-topics moved to separate pages for deeper analysis, e.g. protobuf (already existed), mqtt (new), etc.
• Eclipse: short discussion on the liaison with Eclipse, to be followed up with the Bosch team

...