Map an in-vehicle signal, such as a CAN/DBC signal, to a standardized COVESA Vehicle Signal Specification (VSS) path.
domain: covesa.github.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Browse the VSS catalog to find the closest matching standard signal path, such as Vehicle.Speed or Vehicle.Powertrain.TractionBattery.StateOfCharge.Current.
Confirm the VSS branch/leaf's defined datatype, unit, and min/max range match what your source signal actually provides before mapping.
Where no existing VSS signal fits, follow VSS's extension/customization rules to add a private or OEM-specific branch rather than repurposing an unrelated standard signal.
Use the vss-tools project to generate exportable formats (JSON, C/C++ headers, protobuf) from the .vspec catalog for your target runtime.
Version-pin the VSS release you map against, since signal paths and structure change across major VSS versions.
Known gotchas
VSS defines a semantic naming and structure standard, not a wire protocol — mapping a CAN signal to VSS does not by itself define how it's transported (e.g., via KUKSA Databroker or VISS).
Unit and range mismatches between a raw signal and its VSS definition are a common silent-data-corruption source if not explicitly converted at mapping time.
VSS has undergone breaking structural changes across major versions, so a mapping built against one release may not resolve cleanly against another without re-validation.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?