Project | Person reporting | Updates | Comments |
---|---|---|---|
| Thomas Spreckley | Improved unit-tests (especially on protocol gateway) Vehicle Edge repo improvements, hardware support (RPi4) | |
| Sebastian | Perfect. | |
| |||
| Gunnar Daniel W | GitHub actions VSS catalog now not using list-format, better consistency UUID no longer using an input file. Improved package dependency handling | |
| Daniel W | Short meeting → Plan deep-dive this week on format of TTL file (Turtle - Terse RDF Triple Language), and checking if conversion tools work, etc. | |
| Gunnar | ||
| |||
| Future: possibly split up parts into repos, prepare for proper "microservices" usage. | ||
| Stephen | Ongoing discussion about existing code becoming open-source, and identify new collaboration areas. |
Participants
Minutes
Subprojects / tracks updates
Bosch Framework
General
AUTOSAR
Project | Person reporting | Updates | Comments |
---|---|---|---|
| Thomas Spreckley | Technology transport abstraction (protocol gateway) C++ support Integration test framework + test suites Rust experiments starting (not visible yet) | |
| Sebastian | Paper describing working with Kuksa (gather data from exhaust system and analyze the values) | |
| Ulf | Support for Curve Logging. Implementation better verified now (connected and compared to Geotab Go-device implementation) | |
| Gunnar Daniel W | Travis broken... | |
| Daniel W | vss2vsso → ready to merge. | |
| Gunnar | PR open tweaks some concepts, nested namespaces, clarifies properties. Properties = VSS signals. Similar setup. Discussion on whether it can be done only "in VSS" instead. NOTE: Planning in parallel a "fundamental" discussion on the creation of the common services/interface language likely on July 1 workshop. | |
| Ulf | VISS version 2, process started to send it out as First Public Working Draft (first working group approves to go to this state). Discussion on if some features should be optional. Candidates for optionality are in the areas of filtering and access control. | |
| Ulf | Some smaller fixes after testing in new environment. Planning to have a tool to transform from Geotab collected data into VSS. The first step was implemented (to interpolate curve logging formatted data). | |
| Artem | Awaiting big-picture plan first (see below) |
Participants
Minutes
Participants
Minutes
Project | Person reporting | Updates | Comments |
---|---|---|---|
| Lars-Erich?, Jochen? | Waiting for the right people next week. | |
| Sebastian |
| |
| Ulf | Curve Logging implemented (Ulf can explain more later) | |
| Gunnar Daniel W | VSS: default should be only for attributes, fixed in tools and removed from non-attributes in VSS itself Documentation generation fixes vss-tools→new graphql schema generator | |
| Daniel W | vss to vsso converter still under review (PR) | |
| Gunnar | A VSC generation tool/framework exists. Templates still todo. Reconsidering the language definition (maybe use standard Franca IDL?) | |
| Ulf | ||
| Ulf | ||
AOS? |
Minutes
Project | Person reporting | Updates | Comments |
---|---|---|---|
| Lars-Erich?, Jochen? | ||
| Sebastian | VISS server - PR 190 - now apply default values if given in input catalog. | |
| Ulf | Full implementation of Curve Logging (see Tech Brief page) included now. | |
| Gunnar Daniel | vss-tools: Array size support (caused warnings before) Bug in instantiation code fixed. | |
| Daniel | ||
| Gunnar | ||
| Ulf | ||
| Ulf | ||
AOS? |
Minutes
Agenda
Notes
Notes
Cloud
Notes
... planning to build on VSC tooling
... Gunnar: Plan translation mapping and templates can start early
Notes
Notes
Agenda
Notes
Workshop preparation
Shortlist of working items:
MQTT (and general design) discussion
Open areas for getting started on implementation
Action: Collect more information from more companies about preferred technologies/implementations.
US friendly time 17:00 CET
Agenda
Participants
Piotr, Michal, Dariuz, Adam, Stefan, (TietoEVRY)
Notes
project scoping
review of CVII Tech Stack, updated on line
upcoming CVII workshop
US friendly time 17:00 CET
Agenda
Participants
Piotr, Michal, Dariuz, Adam, Stefan, (TietoEVRY)
Notes
Project scoping
discussion starts with MQT, discussion is based on the content of CVII Tech Stack
Sebastian: this is a preferred techno, but what should be the reference implementation for the mapping of VSS to MQTT ?
discussion on code vs specs
Christian K: code does not lie
Ted: but it can have bugs (as can specs)
Ted: a server in cloud could return VSS JSON or VSSo RDF (or other formats) through content negotiation from the same end points based on client preferences
Christian K: I am convinced there will other standards than CVII in the air, Sensoris for instance, we have already vehicles in development that use Sensoris and I would like to give an opportunity to sync with CVII in the future
TODO Christian K to contact Sensoris and make the liaison happen with them
Sebastian: we do not need to dig deeply into Adaptive Autosar, our interface point is rather someip for instance
Dirk: I would assume both data & service mapping with Autosar
Rex: signal-to-service mapping
Ted: back to SENSORiS, a mapping may be sufficient for this activity and translators can be created by those who need them. likely would be welcome in GENIVI repo if created, HERE previously showed me some mappings they maintain
Christian K: TSN, ARA::COM are deeply embedded when we go so deep, we will lose the opportunity to do any abstraction
TODO all to define what are the high level objectives of constructing an AUTOSAR connection
Christian K: AUTOSAR is so much in the safety world that it will be difficult to build cool things with them
Sebastian: we want the data from below, i.e. from the safety world, do we want to write safety critical applications on top of VSC ?
Gunnar: IMHO VSC can describe a safety critical application but will not implement it
Dirk: what is the targeted runtime environment ? is the vehicle computer or a deeply embedded ECU ?
short discussion between Christian K, Dirk and Gunnar
Gunnar: IMHO the model could apply to any system whatever it safe or not
Christian: we will take this offline
Michal: VSS to MQTT , what is the preferred language to implement the translation ?
Dariuz: I have some experience with MQTT and I am interesting in this translator but not familiar with C++ for instance
SebastianLet's all use RUST :)
Gunnar: we could start with python first and see where it goes, but if Tieto says we use Rust, please do it, you know the industry better
Michal and Dariuz: volunteer for the translator
Adam: we can bring some feedback on AUTOSAR for the next call