RoadSurfaceContaminant
Full qualified VSS Path: Vehicle.Exterior.RoadSurfaceContaminant
Description: Detected non-weather surface contaminant on the road beneath or ahead of the vehicle.
Comment: Reports road surface contaminants that are distinct from weather-related surface state (covered by Vehicle.Exterior.RoadSurfaceCondition) and road obstruction objects (tree, rockfall, etc.). UNKNOWN (0) shall be used when the system cannot assess surface contamination. NONE (5) indicates no surface contaminant detected. MUD (1) indicates wet dirt. CHIPPINGS (2) indicates loose aggregate (tire damage risk, reduced road holding). OIL (3) and FUEL (4) indicate liquid hydrocarbon contamination (slip hazard and fire risk). Values 1-4 are aligned with SENSORIS v1.6 RoadSurfaceCondition.TypeAndConfidence. Determination method is implementation specific.
flowchart LR Vehicle-->Exterior Exterior-->RoadSurfaceContaminant

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.RoadSurfaceContaminant
[get]  OK
Vehicle.Exterior.RoadSurfaceContaminant: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.RoadSurfaceContaminant 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Exterior.RoadSurfaceContaminant

Data Type & Unit
Path Vehicle.Exterior.RoadSurfaceContaminant VSS: Addressing nodes
Data type uint8 VSS: Datatypes

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.Exterior.RoadSurfaceContaminant is a Sensor.

The vehicle signal Vehicle.Exterior.RoadSurfaceContaminant is a Signal.

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.