Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: draft 4/5/22 minutes
Quick links: [ CVII home page ] [ Tech Stack components ]

2022-05-04

Minutes:

  • AMM feedback
    • Paul
      • Workshop
        • ROS/DDS to/from VSS,  input from Ricardo/NNG
          • Reached out waiting for reply to advance discussion
        • BMW / Adnan input about big tech company links
          • Meeting needed to scope out
      • Next time
        • Need input on what ppl want to do
    • Sebastian
      • Workshops
        • Ppl coming to expect 'readout' rather than workshop
        • Positive: good attendance
        • Flip is less 'workshopping'
    • Christian
      • Good discussions
      • Mixed expectations of new members/visitors vs old stagers
      • Good attendance of workshops despite at being the end
      • It was cool
    • Florian
      • Good balance between panels, biz/tech track and workshops
    • Ted
      • Attended virtually
      • Enjoyed BMW presentation on VISS integration
  • Workshop
    • SomeIP / Autosar
    • BMW, Major: VISS + Android VHAL feeder, Minor: GraphQL backend.
    • ROS / ADAS DDS to VSS
    • VSS Feeders
      • Seb: kuksa.val CAN
        • Loosely coupled, i.e. easily reusable
        • CAN feeder in python. Nice for prototype but for production likely look C++, Rust
        • CANOPI
      • Abstraction
        • CCS Component
    • Deep dive next
      • Seb: Dig into what BMW needed/took from VISS protocol to understand their needs. Input towards to VISS v3.
      • Ted will maintain OSS roadmap discussion. Schedule meeting with Adnan about above when code available.

2022-04-20

Agenda:

  1. Project Status
  2. AMM Sessions


ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  

Refactor Subscription Manager and fixes race condition in Websocket interface:
https://github.com/eclipse/kuksa.val/pull/264
https://github.com/eclipse/kuksa.val/pull/266
 
GO client library added for first time to access kuksa.val:

https://github.com/eclipse/kuksa.val/pull/265

  • W3C VISS specification (v2)


Ulf 
Ted as backup (both Geotab)

See last update
  • WAII VISS server implementation in Go
Ulf See last update

Daniel Wilms (BMW)
(Erik J or Sebastian S as backup)

No update
  • VSSo
Daniel W  
Ted  
See last update
  • VSC & Tools
VSC team membersNo call this week due to national holidays
  • CCS-components
Ulf  No update
  • AOS
Artem (EPAM)
See update in minutes for last week
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Added wiki page to gather issues/opportunities for Minutes:
  • Covesa GraphQL components
Alexander Domin (BMW)No update
(proposed.  worth tracking in CVII call?)(Thomas S) Presentation from Kanto introduction posted in "2022-03-28" heading below.


Steve (Renesas)No update


Minutes:

  • AMM workshop Thursday afternoon: 2-3 hours (Updated working list from last week) 
    • Discussion of what the group wants to work on and discuss in near-term
    • Currently the sessions are split into the two related topics VSS Data Storage, including feeders and VSS Data Servers
    • Topic brainstorming:
      • VSS Data Storage (including VSS Data Feeders) (Southbound)
        • Data Storage implementations:
          • DBs: redis, timeseries etc
        • Architecture: Single central vs distributed vs direct sensor connect (bypass store)
        • Feeders: CAN (kuksa.val have closed some gaps), some/ip,
        • Timeseries vs last/single value
        • Interfacing into data servers
      • VSS Data Servers (Northbound)
        • VISS v3? (Duplicate: Will be brought up in prior VISS session so likely handled there)
        • Are VISS backend abstractions possible: storage, feeders?
        • GraphQL - in-vehicle?
          • BMW VISS→Android abstraction/interface/data server
        • VSS Data Servers to cloud
        • Data processing
          • Ted explains they see issues with OEM cloud data. Time slice not short enough for some forms of h/w maintenance wear tracking so have to do their own. Possible need for some in-vehicle processing. Also issues with in-vehicle caching with insufficent IO.
            • In-vehicle vs cloud
            • In-memory vs storage

...