Versions Compared

Old Version 23

changes.mady.by.user Ulf Bjorkengren

Saved on

compared with

New Version Current

changes.mady.by.user Ulf Bjorkengren

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

See COVESA Common Meeting Schedule for meeting link. The meeting is open to anyone.

Policies

  • CVIS-status-2024-fall.pptx It is expected that all meeting participants have read the compliance statement. Every meeting will start with a reminder.Every meeting will start with appointment of note taker. Notes can be on-line, or off-line and if so mailed to moderator within 24 hours. Fair scheduling, i. CVIS-file-repoe. all should take turn. A reason for not taking it is if one expect to speak much at the meeting.

  • Strive for making signal objects reusable by other signal specifications. 

...

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • xxx
  • General topics:
    • Open Pull Requests CVIS
    • Issues CVIS
    • Discussions CVIS
  • Other
  • Prioritized topics for next meeting


Meeting notes  2025-05-05

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • HIM configurator updates
      • Supports calling the vspec tool from both Linux and Windows
      • vspec tool overlays supported
      • overlays on instantiated nodes supported
    • Overlays creator tool added
      • Pick parts of tree from a YAML tree, apply to another tre using HIM configurator overlays.
    • VSS-core2 added. Uses overlays/instantiation overlays.
      • VSS-core uses Global / Local variation points.
    • AMM short f2f meeting?
      • Can we identify a suitable time?
        • We meet Wednesday 13.30 at the room where Ulf will present "An Automotive API and Data Model that caters to all types of vehicles" at 14.00.

Meeting notes  2025-04-23

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:

    • Traton presents ACEA PoC

      • Postponed for next meeting

    • HIM configurator update

      • Overlays support

      • Make file usage removed

Meeting notes  2025-04-07

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Continue the Truck tree analysis.
      • The discussion led to the understanding that any single signal is a potential candidate to be removed, and that there must be a practical solution to that. The VariationPoint feature can do it, but it is not a scalable solution if large numbers of signals needs to be removed.
        • Different options were discussed, both subtractive (removal from VSS-core) and additive (pick from VSS-core).
        • The discussion will continue, and hopefully different solutions will be proposed.
    • Overview HIM configurator features.
    • Review of the CVIS status AMM presentation (draft version).
    • Ted: Regulatory signals

Meeting notes  2025-03-24

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • HIM configurator  generated Truck tree analysis
    • AMM presentations
      • "Status update of the Commercial Vehicle Information Specifications (CVIS) project" is scheduled 04:20 - 4:40pm on May 14
      • "An Automotive API and Data Model that caters to all types of vehicles" is scheduled 02:00 - 2:25pm on May 14
      • Paul: It is possible to have additional break-out meetings. Please consider the need for this until next meeting.
    • Overview HIM configurator features
      • Moved to next meeting.
    • HIM configurator syntax
      • Sergej proposed that the vspec2 syntax is extended to support Google template syntax, thus enabling logic operations.
      • Ulf proposed that this logic is implemented using any computer language in a tool that generates the JSON based input files to the HIM configurator, and keeps the "simpler" syntax in the vspec2 files.
      • Both proposals can exist in parallel, they will lead to the same end result - configured signal trees in the formats set by the used VSS-tools exporters.

Meeting notes  2025-03-10

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Him configurator on Windows
    • HIM configurator road map
    • AMM presentation
    • VSS-core - no compromises
      • The VSS-core tree is vehicle type agnostic. The HIM configurator configures it into a vehicle specific tree.
      • This concept is applicable to most vehicle types like Car, Truck, Bus, Van, etc.

Meeting notes  2025-02-24

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • VSS-core analysis
      • VSS-core analysis.pptx
      • cvis.yaml
      • Look at the cvis.yaml file for ideas on what can be "pruned". Create a PR directly on Github, or a list that we can discuss at next meeting.

Meeting notes  2025-02-10

Meeting notes  2025-01-27

Meeting notes  2025-01-13

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Continue the planning from last meeting
      • Revisited the presentation from last meeting.
      • Cut meeting short due to low participation.

Meeting notes  2024-12-02

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Retrospective and planning
      • Focus on one trailer type initially?
      • Align with existing trailer interface standards
      • Leverage existing J1939 VSS mapping
    • System design
    • Experimentation
    • Presentation of the above: CVIS-retrospect-design-experimentation.pptx
      • Discussion to be continued at next meeting in January.
    • Christmas recess
      • Dec16 and Dec 30, back Jan 13

Meeting notes  2024-11-18

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Meeting cut short due to low participation

Meeting notes  2024-11-04

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • VSS car tree vs CVIS truck tree.
      • Arguments for a separate truck tree
        • The HIM model supports to rename the root node so that selected parts of the tree can have identical paths with the VSS tree.
        • The objects branch in CVIS facilitates a structured model for sharing common branches.
        • Parts of the VSS tree does not relate well to Trucks, e.g. Axle/Wheel configuration.
        • The HIM configurator provides features not available in VSS-tools, such as the assymmetric matrix configuration.
      • Decision: We will continue the development of a separate Truck tree.
        • The scenario where an app developed for passenger cars should also be deployable on a truck will be supported.

Meeting notes  2024-10-21

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Future of the meeting 
      • Volvo: sees interest in defining trees and also in using VISS. Still internal discussion.
      • GM going through reorg, currently monitoring this group.
      • Initial conclusion: We will continue the meeting series.
    • use vsspathlist.json to vet the content of the Truck tree.
      • Maybe not the right path forward, see question below.
    • Should a truck use the VSS tree (Vehicle tree) instead of defining a separate tree?
      • Trailer, Driver, etc. could be separate trees, but Truck should use the Vehicle tree (at least as much as is feasible).
        • How to resolve major differencies, e. g. the axle/tire location definitions?
    • Plan for how to create a first version Truck tree (trailer/bus?).
    • VISSR updated with VISSv3.0 features now supports multiple trees, e. g. Truck tree plus Trailer tree(s).

Meeting notes  2024-09-09

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • use vsspathlist.json to vet the content of the Truck tree.
    • Cargo location - to be continued.
      • Example scenario of a truck being loaded?
    • Next meeting sept 23 is cancelled as it is the same week as the AMM.
    • Todays meeting was cut short due to low participation.

Meeting notes  2024-08-26

  • Other
    • Review AMM presentation draft

Meeting notes  2024-08-12

...