Resources |
◎ COVESA Events |
Join/Sign Up |
◎ Join COVESA |
CVIS Meeting Topics and Meeting Notes
This page intends to contain the agenda for next CVIS meeting (Mondays 16.00-17.00 CET) and notes from previous meeting. Below is a template for the agenda. General agenda points like discussion on PRs and issues may be skipped if discussion on prioritized topics takes too long time.
See COVESA Common Meeting Schedule for meeting link. The meeting is open to anyone.
Policies
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.
Specification development page
The writing of the signal specifications are done at https://github.com/COVESA/commercial-vehicle-information-specifications.
Welcome and Compliance statement
Welcome to the COVESA CVIS Meeting!
Antitrust Note Well
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.
Contributing to COVESA Activities
Companies and individuals contributing to COVESA activities should understand the COVESA IP Policy and know that all COVESA work products, including software and documents, will be released under an open source license as described in the Public Policy for Open Source Licensing. Contributors must also follow COVESA’s Export Controls and Sanctions Compliance Policy. Before a contribution can be accepted, contributors must provide their name, contributing organization if the contribution is not personal, email address, and country.
COVESA is not a standards body. Any COVESA activity that requires a formal specification must first be approved by the Board of Directors and then moved to a formal standards development organization.
Please do not contribute ideas or code that may involve patents unless you disclose to other participants, through meeting minutes or pull requests, that use of the contribution could potentially infringe a patent.
Agenda Template
Welcome and Compliance statement
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 2026-6-29
Welcome and Compliance statement
Agenda discussion - anything that needs to be added?
Prioritized Topics:
Review of the updated Trailer vspec tree.
Meeting notes 2026-6-15
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Continued review of the updated Trailer data spreadsheet.
Excel sheet update concluded.
Will be saved at https://github.com/COVESA/commercial-vehicle-information-specifications/tree/main/spec/trees/Vehicle/Trailer/Proposal
Will be used to update the Trailer tree at https://github.com/COVESA/commercial-vehicle-information-specifications/tree/main/spec/trees/Vehicle/Trailer
Meeting notes 2026-6-01
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Continued review of the updated Trailer data spreadsheet.
Meeting notes 2026-3-23
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Continued review of the updated Trailer data spreadsheet.
Decision: Refactor “boolean type enums” to boolean. Add comment that it is an enum in J1939.
VISS v3.1 addition of Implementation Guidelines document
ACEA will write the chapter on “CAN Bus Specific Error Reporting”
AMM presentation
Completed and shared with Ted Guild who will present it as part of thwe CV presentation.
Meeting notes 2026-2-23
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Review of the updated Trailer data spreadsheet.
Restructuring of the Github repo?
Meeting notes 2026-2-9
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Trailer tree content development continued.
Trailer data input from Volvo:
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?
Dev of a tree/branch with trailer data is first prio
Same for truck is second prio
VISSv3.1 release candidate
VISSR update: support for multiple feeders
Meeting notes 2026-1-12
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.
Meeting notes 2025-12-1
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.
Meeting notes 2025-11-17
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
Meeting notes 2025-11-3
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
How to increase the attendance of these meetings?
Meeting notes 2025-10-20
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
https://covesa.github.io/commercial-vehicle-information-specifications/examples/truck_trailer_viss/
Meeting notes 2025-10-6
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.
Meeting notes 2025-09-22
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.
Meeting notes 2025-09-08
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
AMM - do we have anything relevant to present?
Ulf and Ted put something together, to be presented in the CV context.
Meeting notes 2025-08-25
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).
Meeting notes 2025-08-11
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
CVIS trailer tree proposal
ACEA-COVESA MoU
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
Meeting notes 2025-06-30
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:
Summer recess?
Cancelling the next two meetings, July 14 and 28. Next meeting will be Aug 11.
.png?version=1&modificationDate=1751295232019&cacheVersion=1&api=v2){kind=link}
Meeting notes 2025-06-16
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Truck specific data
Main branches in trailer tree?
Meeting notes 2025-06-02
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.
Meeting notes 2025-05-19
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?
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
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.
Meeting notes 2025-03-10
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.
Meeting notes 2025-02-24
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
VSS-core analysis
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
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Tree partition proposal
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