Resources |
◎ COVESA Events |
Join/Sign Up |
◎ Join COVESA |
VSS Meeting Topics and Meeting Notes
This page intends to contain the agenda for next VSS meeting (Tuesdays 16.00-17.00 CET) and notes from previous meeting. At the bottom 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.
Notes from previous years can be found in subpages!
General Agenda
Welcome and Compliance statement
Welcome to the COVESA VSS 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.
Agenda discussion - anything that needs to be added
Prioritized Topics:
Decision on old open PRs
Open Pull Requests VSS
Open Pull Requests VSS-Tools
Issues VSS
Issues VSS-Tools
Prioritized topics for next meeting
Meeting notes 2026-05-12
Vlad:
D. We have mirror version of vdm, no full consensus yet, keep them separated for now. VDM moving away to graph repr
D. No agreement to make a full migration to VDM, simply copying'
D. We have regular meetings, normally on Thursdays, but not this week due to holiday in Europe. Feel free to join
D. Could we enable a catalog explorer on coves web site
E: We have a graphic representation at
Introduction :: Vehicle Signal Specification Do not know status of Digital auto - VSS collaboration
Still alive @Paul Boyes ?
Old version here: playground.digital.auto
We could leverage LLM to produce descriptions
Meeting notes 2026-05-05
Paul - Anything we want to say related to VSS roadmap
E: One topics is defining guidelines/rules for the catalog. They exist sometimes today but only in our heads.
E: Tooling side - VDM prepareness
D. Intends to have a continuous integration VSS to VDM
D. Specification registry, future proof entries
D. Semi-automating concepts, make it easier to create draft proposals
D. Enable reuse of other vocubalarities
P: Export Control - you have to be verified to commit
D. Sometimes final users wants a somewhat different output. We could have a generic mapping engine. Can configure if they want a partially different output.
How does people want to use LLMs together with VSS
Natural language exploration, like analyze requirements like “I want to analyze a crash, what VSS signal could be useful for this purpose?”
Meeting notes 2026-04-28
AMM
OCX - Anyone was there?
s-core -
Automotive world in Japan, September, COVESA technical sessions planned
Fall COVESA AMM in October in Novi, Michigan
Jaspar
Especially interesting for us is https://github.com/yoriito/yoriito-vss
See https://github.com/yoriito/yoriito-vss/blob/main/scripts/create_vspec.sh for how they build their VSS (overlay plus VSS)
Noticed changes - using numbers for batteries and electric motors.
How to get started:
git clone https://github.com/yoriito/yoriito-vss cd yoriito-vss python3 -m venv .venv source .venv/bin/activate pip install -r requirements.txt scripts/create_vspec.sh
Meeting notes 2026-04-14
No meeting next week (AMM)
@Paul Boyes - please remove it from calendar unless you already have done so
Meeting notes 2026-04-07
AMM
Introduction to VSS: A Deeper Dive
Erik to present
Data Expert Group - VSS Next and VDM Next
Adnan to sync with Daniel if he could lead
E: General VSS going forward without anything really revolutionary. We have interesting collaborations w ACEA/FMS, Jaspar
Stephen: Governance
Adnan: Lets not confuse people
E: isnt it decided that VSS will remain supported, used and not changing drastically
Joint Vehicle Signal Specification/Commercial and Fleet Vehicle Expert Group Working Session
Meeting notes 2026-03-31
AMM
P: There is a slot for VSS/VDM
Agenda:
COVESA All Member Meeting l April 22-23, 2026 | Porto, Portugal
TODO: Next week - synch on VSS slots
FMS discussion as well
PRs discussed
Meeting notes 2026-03-24
AP @Erik.Jaegervall@se.bosch.com to create synatx proposal for
enums revisited · Issue #873 · COVESA/vehicle_signal_specification
Meeting notes 2026-03-17
FMS/ACEA branch/maintainers
New branch “acea-namespace”
Abdelkadar (Volvo Trucks) and Sergej (Traton) new collaborators in repo on triage level
Jeremy/Michelin - https://github.com/COVESA/vehicle_signal_specification/issues/883
Meeting notes 2026-03-10
FMS/ACEA Enum topic
See
enums revisited · Issue #873 · COVESA/vehicle_signal_specification Ted: FMS/ACEA wants enum
Ted: In J1939 often use as enum for boolean values
T: Ford proposed some time ago extra metadata for datapoints, like e.g. error.
T: I think we should avoid enums just to represent J1939 errors in boolean values
Segej: Has looked in velocitas broker and have seen error handling, but not part of VISS so our broker does not do the error handling
S: if we have a boolean we want to handle it as a boolean. If API can handle error it would be great. If we cannot rely on API for error handling we need to handle it on signal level.
S: Can we have error handling mentioned in VISS
Ulf: Would say VISS already handle this. But could extend if we see problems
Ulf: We should maybe not discuss here, lets discuss offline.
E: AP to check what VSS spec says on error handling. Think we say that VSS does not specify it, but refer to the API
S: VSS signals are logical signals. For J1939 do we state somewhere that a specific J1939 error code corresponds to a particular (VISS) error code
U: VISS should potentially not mention J1939
E: But adding a supplement that specifies J1939-VISS mapping would not be a problem
U: Yes
S: We have standardized error codes. Our implementation should know how to do the mapping.
U: Seems to be an implementation issue to me. VISS have bi-weekly meetings
E: better be discussed in VISS meeting, if it mainly concern VISS error codes
Daniel: Sees similarities with other protocols, like in the past OBD
As of today we do not support enum, we have alowed values
E: presented https://github.com/COVESA/vehicle_signal_specification/pull/885 as example for possibly syntax
D : Finds this complex. What could be done is have two different types of allowed values. One as today. Instead of type string pass “enum”.
E: Way forward if some changes are to be implemented
Someone to continue refining syntax
The testing it out in vss-tools, implement support
D : We lack method to reuse existing standards
E: Please continue discuss issue and PR.
Meeting notes 2026-03-03
FMS - enum topic
- enums revisited · Issue #873 · COVESA/vehicle_signal_specification
Ted: Could bring them to this call
T: API aspect
U: Both text or value representation would be usable in VISS
E: Way forward if we are going to implement/extend VSS
Syntax proposal PR
Analysis how it impact vss-tools and exporters
PR for exporters
Impact on downstream projects (VISS, VISSR, Kuksa, …)
T: Some prefer enum instead of boolean as it is enum in FMS
Armin Keller will visit AMM, and Abdul Sellami from Volvo
AMM
Schedule up - 1 hour for VSS
Meeting notes 2026-02-23
AMM VSS Topics
Jeremy - VSS catalog for trucks
Erik part of FMS/ACEA discussion
Ted: ACEA and COVESA has a liasion agreement for fleet management, J1939, …
Ted: Scania/Volvo may present at AMM
Erik: VSS Governance if we have additions from FMS/ACEA and Jaspar
Changed meeting times (sometimes Asian friendly?)
Daniel: Workshop - allowed values as separate set of definitions, e.g. for enum
Ted: Working on enum PR/issue together with Scania
Jeremy presented issue https://github.com/COVESA/vehicle_signal_specification/issues/883
Meeting notes 2026-02-17
Erik: Suggestion that we discuss AMM topics next week
Paul: FMS will present, possibly joint working session with VSS
Paul: Jaspar will also be there, wants to announce what is going on
P: VDM call for models, check post on slack
P: Encourage participants to check out how VDM fit their needs
E: Some ideas to discuss
VDM collaboration/sync implications (roundtrip?)
Collaboration model with FMS/Jaspar - how is VSS project affected. Changed meeting schedule?
P: Have started a schedule draft
P: up to 3 hours available for VSS workshops
P: Use of AI, Fleet mgmt, …., could be interesting talks. Many topics proposed
Meeting notes 2026-02-10
Daniel: Uniqueness of branch names -
Modify the vspec to guarantee uniqueness for the {branch_name} · Issue #798 · COVESA/vehicle_signal_specification Connected safety BoF -
Support for Connected Safety · Issue #877 · COVESA/vehicle_signal_specification Tim VanGoethem gave a presentation
Where/how to store ACEA/FMS signals -
ACEA/FMS signal tree · Issue #880 · COVESA/vehicle_signal_specification
Meeting notes 2026-02-03
Paul presenting issue
Support for Connected Safety · Issue #877 · COVESA/vehicle_signal_specification No objections during the meeting.
It is necessary to complete the list of signals for the PR.
@Paul Boyes will go into second round to complete list of signals.
Adnan have sent notification to David about PR
added mikro seconds (us) and nano seconds (ns) as durations in units.yaml by DavidMatzek · Pull Request #855 · COVESA/vehicle_signal_specification S2DM PR from Daniel Alvarez, merged.
Meeting notes 2026-01-27
SD2M: Daniel presented
Refactor/s2dm exporter by jdacoello · Pull Request #475 · COVESA/vss-tools Erik on business trip next week
Can @adnan.bekan@bmwgroup.com or @Paul Boyes host it?
Meeting notes 2026-01-20
VSS 6.0
6.0 released and set as “latest release”
Erik intends to merge back changes from the release branches later this week and make master branches “ready” for continue development
FMS branches
E: There have not been any detailed discussion on where to put FMS additions (customization/addition for commercial vehicles).
E: Alternatives:
Overlay within std catalog (master branch)
Separate branch in covesa vss repo
Fork of vss within covesa
Separate repo within covesa (if starting tree from scratch)
Repo outside covesa
AMM Porto
Submissions welcome, registration open
Meeting notes 2026-01-13
VSS 6.0 release decision
RC available since Dec 18th
No comments/remarks received
OK to release
AMM Porto
Registration open at
Contact Paul if you are interested in presenting something
Start thinking if there are some VSS-specific topics you want us to discuss
VDM-VSS co-existence is one topic
FMS “own branch”
Fleet Management, ACEA
Wants a branch for themselves, maybe in own github
Ted: Some differences, how to handle variations. either branch or own tree
E: Placeholder for fuel systemdiscussion at
FuelSystem Refactoring · Issue #875 · COVESA/vehicle_signal_specification Stephen: Opportunity to discuss how to tackle this in general.
Enum -
enums revisited · Issue #873 · COVESA/vehicle_signal_specification UDS discussion (in slack)
T: How do we reconcile diagnostics and services. E.g. single data point in VSS that refer to diagnostics server address.
T: May need to be discussed in TST
CES
A lot of interest in VSS
Sensors/actuators -
