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

• It is expected that all meeting participants have read the compliance statement. Every meeting will start with a reminder.

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

The writing of the signal specifications are done at https://github.com/COVESA/commercial-vehicle-information-specifications.

Welcome to the COVESA CVIS Meeting!

Antitrust



Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

Open and Royalty-Free



Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

• 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

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • Trailer tree content development continued.

    • Ted: Talk about UDS discussion that has been started at the Slack #vss channel.

    • AMM presentation: CVIS Status and Roadmap

      • What shall the roadmap contain?

    • VISSR update: support for multiple feeders

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • Proposal on how J1939 PGNs and SPNs can be represented in a technology neutral syntax.

      • Exemplified using VISS/HIM/VSS.

    • Trailer tree content development continued.

      • Moved to next meeting due to lack of time.

    • Ted: Talk about UDS discussion that has been started at the Slack #vss channel.

      • Moved to next meeting due to lack of time.

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • VspecPreprocessor feedback

      • Doing its job to a level where we can now focus on what content should go into the trees.

    • Trailer tree content development

      • Cargo sub-domain will be added. Wally and Abdel will look into what signals may go there.

    • Winter recess

      • Meetings cancelled Dec 15 and Dec 29. Next meeting Jan 12.

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • Presentation of the new tool vspecPreprocessor

    • Roadmap development

      • Abdel:We should try to create a roadmap document. It will help us to prioritize what to work on and it will also provide transparency.

    • Wally: info on discussions to make the J1939 DA more consumable by all parties

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • Multiple tree trailer example

      • From tree creation to data access using VISS demo

    • Trailer doman tree proposal by Volvo

      • GitHub - abdelkadersellami/Trailer_Signal_Specifications

    • How to increase the attendance of these meetings?

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • Multiple tree trailer example

      • From tree creation to data access using VISS

      • Truck and trailer trees used in VISS access scenario :: Commercial Vehicle Information Specifications (CVIS)

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • CVIS trailer tree initialization, see Trailer feedback below.

      • Solution needs to be developed at som point whether it is for single or multiple tree solutions.

    • Single tree / multiple tree model?

      • Trailer data.

        • Will look at Volvo’s trailer tree proposal at next meeting to try to advance it.

      • FMS data.

        • Try to create a separate tree staying with FMS data definitions (of unit, datatype etc).

    • We will revisit the CVIS vehicle type agnostic tree model at next meeting.

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • CVIS trailer tree initialization, see Trailer feedback below.

    • FMS data representation.

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • CVIS trailer tree proposal continued

    • VAPI – A connectivity agnostic Vehicle API for access to signals and services

      • https://raw.githack.com/UlfBj/vehicle-api/main/spec/VAPIv1.0.html

    • AMM - do we have anything relevant to present?

      • Ulf and Ted put something together, to be presented in the CV context.

•  

  • Compliance statement

  • Welcome and agenda discussion - anything that needs to be added?

  • Prioritized Topics:

    • Meeting cancelled due to confusion on the new meeting time. It starts every other Monday at 15.00 CET (previously at 16.00).

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • CVIS trailer tree proposal

    • CVIS-trailer-tree-proposal.pptx

  • ACEA-COVESA MoU

    • https://www.acea.auto/press-release/auto-makers-and-covesa-sign-memorandum-of-understanding-to-advance-interoperability-in-commercial-vehicles/

  • VAPI – A connectivity agnostic Vehicle API for access to signals and services ← Will be presented at the next meeting

  • Ted: Moving the meeting one hour earlier, to 15-16 CET time?

    • Proposal to move it one hour earlier. 

  • Wally: TMC

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • Trailer proposal by Volvo Group

    • https://github.com/KAVeenashree/vehicle_signal_specification/tree/features/vehicle/trailerdata

    • The naming scheme for wheel positions was discussed, one model is shown here:

      • iso-11992.png

  • Summer recess?

    • Cancelling the next two meetings, July 14 and 28. Next meeting will be Aug 11.

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • Truck specific data

  • Main branches in trailer tree?

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • Truck specific data

  • Main branches in trailer tree?

  • Meeting clash with ACEA FMS. Meeting cancelled.

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • AMM reflections

  • Next steps

    • Focus on truck specific data

    • Propose via PRs to our Github repo

      • Get access to the Github repo

        • Github account

        • COVESA specific permission needed?

• 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.

• 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

• 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).

    • Spring AMM 2025 - Day1_420_Bjorkengren_Status-update-of-the-Commercial-Vehicle-Information-Specifications-(CVIS)-project.pptx

  • Ted: Regulatory signals

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • HIM configurator  generated Truck tree analysis

    • Analysis-by-Volvo.xlsx

    • VSS-core-truck-configured.yaml

    • FuelTank-config.txt

    • Participants asked to look into solutions for the different findings in the list from Volvo.

  • 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.

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • Him configurator on Windows

    • The setup solution from Traton is found in the Win-setup directory in the CVIS repo.

  • 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.

• 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.

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • Tree partition proposal

    • CVIS-multiple-tree-VSS-alignment.pptx

    • COVESA EU Data Act Charter

      • Meeting on Wednesday, link found at https://covesa.atlassian.net/wiki/display/WIK4/COVESA+Common+Meeting+Schedule

    • Decided to try out the idea of a VSS Core tree

  • AMM presentation: PoC possible?

    • Requires that any CVIS participant takes it on.

    • The VISSR tech stack supports a setup like shown in the presented PPT requiring minimal additions.

  • Paul: Links from FMS discussion with ACEA

    • https://www.fms-standard.com/Truck/down_load/Technical_Specification_rFMS_vehicle_data_V4.0.0_17.09.2021.pdf

    • https://github.com/eclipse-sdv-blueprints/fleet-management/blob/main/spec/mapping-fms4-to-vss.md

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • Continue the planning from meeting 241202

  • AMM presentation? Deadline for draft/abstract March 15. 

  • Niklas: Will present some ideas on required signals: Commercial Vehicle data 20250127.pptx

    • FMS/r-FMS: https://www.fms-standard.com/Truck/down_load/download_ok.htm?

• 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.

• 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

• Compliance statement

• Welcome and agenda discussion - anything that needs to be added?

• Prioritized Topics:

  • Meeting cut short due to low participation

• 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.