This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Exterior
Full qualified VSS Path: Vehicle.Exterior
Description: Information about exterior measured by vehicle.
flowchart LR Vehicle-->Exterior

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

Signal Information

The vehicle signal Vehicle.Exterior is a Branch.

Children

This vehicle signal is a branch or structure and thus has sub-pages:

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.

1 - AirPressure
Full qualified VSS Path: Vehicle.Exterior.AirPressure
Description: Atmospheric air pressure outside the vehicle.
Comment: Static ambient air pressure measured by the vehicle’s barometric sensor. May be used for altitude estimation, weather trend detection, and HVAC pressurization management. Related to SENSORIS v1.6 AtmosphereCondition.static_air_pressure.
flowchart LR Vehicle-->Exterior Exterior-->AirPressure

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirPressure
[get]  OK
Vehicle.Exterior.AirPressure: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirPressure 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.AirPressure

Data Type & Unit
Path Vehicle.Exterior.AirPressure VSS: Addressing nodes
Data type float VSS: Datatypes
Unit hPa VSS: Units

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.AirPressure 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.

2 - AirQuality
Full qualified VSS Path: Vehicle.Exterior.AirQuality
Description: Signals describing the composition of the ambient air outside the vehicle.
flowchart LR Vehicle-->Exterior Exterior-->AirQuality

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

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality is a Branch.

Children

This vehicle signal is a branch or structure and thus has sub-pages:

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.

2.1 - CO2
Full qualified VSS Path: Vehicle.Exterior.AirQuality.CO2
Description: Carbon dioxide (CO2) concentration.
Comment: If the sensor reports an estimated CO2 level (eCO2/CO2eq) derived from other gas measurements rather than a direct CO2 measurement, the estimated value may be reported here.
flowchart LR Vehicle-->Exterior Exterior-->AirQuality AirQuality-->CO2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirQuality.CO2
[get]  OK
Vehicle.Exterior.AirQuality.CO2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirQuality.CO2 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.AirQuality.CO2

Data Type & Unit
Path Vehicle.Exterior.AirQuality.CO2 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit ppm VSS: Units
Label parts per million
Description Concentration measured in parts per million VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality.CO2 is a Sensor.

The vehicle signal Vehicle.Exterior.AirQuality.CO2 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.

2.2 - NO2
Full qualified VSS Path: Vehicle.Exterior.AirQuality.NO2
Description: Nitrogen dioxide (NO2) concentration.
flowchart LR Vehicle-->Exterior Exterior-->AirQuality AirQuality-->NO2

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirQuality.NO2
[get]  OK
Vehicle.Exterior.AirQuality.NO2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirQuality.NO2 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.AirQuality.NO2

Data Type & Unit
Path Vehicle.Exterior.AirQuality.NO2 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit ppb VSS: Units
Label parts per billion
Description Concentration measured in parts per billion VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality.NO2 is a Sensor.

The vehicle signal Vehicle.Exterior.AirQuality.NO2 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.

2.3 - Ozone
Full qualified VSS Path: Vehicle.Exterior.AirQuality.Ozone
Description: Ozone (O3) concentration.
flowchart LR Vehicle-->Exterior Exterior-->AirQuality AirQuality-->Ozone

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirQuality.Ozone
[get]  OK
Vehicle.Exterior.AirQuality.Ozone: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirQuality.Ozone 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.AirQuality.Ozone

Data Type & Unit
Path Vehicle.Exterior.AirQuality.Ozone VSS: Addressing nodes
Data type float VSS: Datatypes
Unit ppb VSS: Units
Label parts per billion
Description Concentration measured in parts per billion VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality.Ozone is a Sensor.

The vehicle signal Vehicle.Exterior.AirQuality.Ozone 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.

2.4 - PM1
Full qualified VSS Path: Vehicle.Exterior.AirQuality.PM1
Description: Mass concentration of particulate matter with aerodynamic diameter of 1 micrometer or less (PM1.0).
flowchart LR Vehicle-->Exterior Exterior-->AirQuality AirQuality-->PM1

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirQuality.PM1
[get]  OK
Vehicle.Exterior.AirQuality.PM1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirQuality.PM1 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.AirQuality.PM1

Data Type & Unit
Path Vehicle.Exterior.AirQuality.PM1 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit ug/m^3 VSS: Units
Label microgram per cubic meter
Description Mass concentration measured in micrograms per cubic meter VSS: Sensors & Actuators
Domain mass-per-volume
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality.PM1 is a Sensor.

The vehicle signal Vehicle.Exterior.AirQuality.PM1 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.

2.5 - PM10
Full qualified VSS Path: Vehicle.Exterior.AirQuality.PM10
Description: Mass concentration of particulate matter with aerodynamic diameter of 10 micrometers or less (PM10).
flowchart LR Vehicle-->Exterior Exterior-->AirQuality AirQuality-->PM10

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirQuality.PM10
[get]  OK
Vehicle.Exterior.AirQuality.PM10: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirQuality.PM10 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.AirQuality.PM10

Data Type & Unit
Path Vehicle.Exterior.AirQuality.PM10 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit ug/m^3 VSS: Units
Label microgram per cubic meter
Description Mass concentration measured in micrograms per cubic meter VSS: Sensors & Actuators
Domain mass-per-volume
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality.PM10 is a Sensor.

The vehicle signal Vehicle.Exterior.AirQuality.PM10 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.

2.6 - PM25
Full qualified VSS Path: Vehicle.Exterior.AirQuality.PM25
Description: Mass concentration of particulate matter with aerodynamic diameter of 2.5 micrometers or less (PM2.5).
flowchart LR Vehicle-->Exterior Exterior-->AirQuality AirQuality-->PM25

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirQuality.PM25
[get]  OK
Vehicle.Exterior.AirQuality.PM25: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirQuality.PM25 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.AirQuality.PM25

Data Type & Unit
Path Vehicle.Exterior.AirQuality.PM25 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit ug/m^3 VSS: Units
Label microgram per cubic meter
Description Mass concentration measured in micrograms per cubic meter VSS: Sensors & Actuators
Domain mass-per-volume
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality.PM25 is a Sensor.

The vehicle signal Vehicle.Exterior.AirQuality.PM25 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.

2.7 - TVOC
Full qualified VSS Path: Vehicle.Exterior.AirQuality.TVOC
Description: Total volatile organic compounds (TVOC) concentration.
flowchart LR Vehicle-->Exterior Exterior-->AirQuality AirQuality-->TVOC

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirQuality.TVOC
[get]  OK
Vehicle.Exterior.AirQuality.TVOC: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirQuality.TVOC 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.AirQuality.TVOC

Data Type & Unit
Path Vehicle.Exterior.AirQuality.TVOC VSS: Addressing nodes
Data type float VSS: Datatypes
Unit ppb VSS: Units
Label parts per billion
Description Concentration measured in parts per billion VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Exterior.AirQuality.TVOC is a Sensor.

The vehicle signal Vehicle.Exterior.AirQuality.TVOC 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.

3 - AirTemperature
Full qualified VSS Path: Vehicle.Exterior.AirTemperature
Description: Air temperature outside the vehicle.
flowchart LR Vehicle-->Exterior Exterior-->AirTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.AirTemperature
[get]  OK
Vehicle.Exterior.AirTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.AirTemperature 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.AirTemperature

Data Type & Unit
Path Vehicle.Exterior.AirTemperature VSS: Addressing nodes
Data type float VSS: Datatypes
Unit Celsius VSS: Units

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.AirTemperature 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.

4 - Humidity
Full qualified VSS Path: Vehicle.Exterior.Humidity
Description: Relative humidity outside the vehicle. 0 = Dry, 100 = Air fully saturated.
flowchart LR Vehicle-->Exterior Exterior-->Humidity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.Humidity
[get]  OK
Vehicle.Exterior.Humidity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.Humidity 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.Humidity

Data Type & Unit
Path Vehicle.Exterior.Humidity VSS: Addressing nodes
Data type float VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.Humidity 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.

5 - LightIntensity
Full qualified VSS Path: Vehicle.Exterior.LightIntensity
Description: Light intensity outside the vehicle. 0 = No light detected, 100 = Fully lit.
Comment: Mapping to physical units and calculation method is sensor specific.
flowchart LR Vehicle-->Exterior Exterior-->LightIntensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.LightIntensity
[get]  OK
Vehicle.Exterior.LightIntensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.LightIntensity 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.LightIntensity

Data Type & Unit
Path Vehicle.Exterior.LightIntensity VSS: Addressing nodes
Data type float VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.LightIntensity 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.

6 - PrecipitationIntensity
Full qualified VSS Path: Vehicle.Exterior.PrecipitationIntensity
Description: Precipitation intensity in millimeters per hour.
Comment: Provides an absolute intensity measurement complementing Vehicle.Body.Raindetection.Intensity (which is a relative 0-100 percent scale). Applies to all precipitation types reported by Vehicle.Exterior.PrecipitationType; value is 0 when PrecipitationType is NONE. Measurement method is sensor specific.
flowchart LR Vehicle-->Exterior Exterior-->PrecipitationIntensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.PrecipitationIntensity
[get]  OK
Vehicle.Exterior.PrecipitationIntensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.PrecipitationIntensity 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.PrecipitationIntensity

Data Type & Unit
Path Vehicle.Exterior.PrecipitationIntensity VSS: Addressing nodes
Data type float VSS: Datatypes
Unit mm/h VSS: Units
Label millimeter per hour
Description Precipitation intensity measured in millimeters per hour VSS: Sensors & Actuators
Domain precipitation-rate
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.PrecipitationIntensity 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.

7 - PrecipitationType
Full qualified VSS Path: Vehicle.Exterior.PrecipitationType
Description: Type of precipitation currently detected outside the vehicle.
Comment: Discriminates precipitation type from Vehicle.Body.Raindetection.Intensity, which reports intensity for rain only. UNKNOWN (0) shall be used when precipitation type cannot be assessed. NONE (1) indicates no precipitation detected. HAIL (5) includes sleet and freezing rain as a precipitation type (distinct from black ice formation on the road surface, which is reported by Vehicle.Safety.RoadIcingState when available). Values are aligned with SENSORIS v1.6 Precipitation.TypeAndConfidence. Determination method is implementation specific.
flowchart LR Vehicle-->Exterior Exterior-->PrecipitationType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.PrecipitationType
[get]  OK
Vehicle.Exterior.PrecipitationType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.PrecipitationType 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.PrecipitationType

Data Type & Unit
Path Vehicle.Exterior.PrecipitationType 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.PrecipitationType is a Sensor.

The vehicle signal Vehicle.Exterior.PrecipitationType 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.

8 - RoadObstruction
Full qualified VSS Path: Vehicle.Exterior.RoadObstruction
Description: Type of road obstruction detected ahead of the vehicle.
Comment: Reports the category of road obstruction detected by the vehicle’s perception systems. UNKNOWN (0) shall be used when obstruction type cannot be classified. NONE (9) indicates no obstruction detected. SHED_LOAD (4) covers cargo fallen from another vehicle. LAND_SLIP (5) or landslide is ground material that has slid down slope into road. ANIMAL (6) covers small animals (cat, dog); ANIMAL_LARGE (7) covers large animals (deer, horse, livestock); ANIMAL_HERD (8) covers groups of animals on road. FLOODING (10) indicates standing water sufficient to obstruct passage (distinct from WET surface state in Vehicle.Exterior.RoadSurfaceCondition). Values 1-8 are aligned with SENSORIS v1.6 RoadObstructionCondition.TypeAndConfidence and TPEG-TEC road obstruction taxonomy. Determination method is implementation specific (camera, radar, lidar). Primary consumers: navigation systems (dynamic re-routing), ADAS safety systems, and emergency dispatch systems.
flowchart LR Vehicle-->Exterior Exterior-->RoadObstruction

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.RoadObstruction
[get]  OK
Vehicle.Exterior.RoadObstruction: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.RoadObstruction 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.RoadObstruction

Data Type & Unit
Path Vehicle.Exterior.RoadObstruction 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.RoadObstruction is a Sensor.

The vehicle signal Vehicle.Exterior.RoadObstruction 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.

9 - RoadSurfaceCondition
Full qualified VSS Path: Vehicle.Exterior.RoadSurfaceCondition
Description: Assessed condition of the road surface beneath or ahead of the vehicle.
Comment: Determination method is implementation specific. May be derived from sensor fusion of Vehicle.ADAS.ESC.RoadFriction.MostProbable, Vehicle.Exterior.AirTemperature, Vehicle.Body.Raindetection.Intensity, and optional camera-based road surface classification. UNKNOWN (0) shall be used when the system cannot assess the road surface condition. Primary consumers: navigation and ADAS safety systems. Related to VSS issue #877 (Connected Safety signals).
flowchart LR Vehicle-->Exterior Exterior-->RoadSurfaceCondition

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.RoadSurfaceCondition
[get]  OK
Vehicle.Exterior.RoadSurfaceCondition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.RoadSurfaceCondition 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.RoadSurfaceCondition

Data Type & Unit
Path Vehicle.Exterior.RoadSurfaceCondition 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.RoadSurfaceCondition is a Sensor.

The vehicle signal Vehicle.Exterior.RoadSurfaceCondition 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.

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

11 - RoadSurfaceTemperature
Full qualified VSS Path: Vehicle.Exterior.RoadSurfaceTemperature
Description: Temperature of the road surface beneath or ahead of the vehicle.
Comment: Distinct from Vehicle.Exterior.AirTemperature: the road surface can sit several degrees below the air, most notably on bridge decks and in shaded cuttings, so surface temperature is the determining input for icing risk when the air reads above freezing while the road is still frozen. A natural fusion input to Vehicle.Exterior.RoadSurfaceCondition alongside air temperature and Vehicle.ADAS.ESC.RoadFriction.MostProbable, and to Vehicle.Safety.RoadIcingState where available. Measurement method is implementation specific (typically infrared pyrometer) and the value may also originate from external road-weather infrastructure. Related to VSS issue #877 (Connected Safety signals).
flowchart LR Vehicle-->Exterior Exterior-->RoadSurfaceTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.RoadSurfaceTemperature
[get]  OK
Vehicle.Exterior.RoadSurfaceTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.RoadSurfaceTemperature 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.RoadSurfaceTemperature

Data Type & Unit
Path Vehicle.Exterior.RoadSurfaceTemperature VSS: Addressing nodes
Data type float VSS: Datatypes
Unit Celsius VSS: Units

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.RoadSurfaceTemperature 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.

12 - VisibilityCondition
Full qualified VSS Path: Vehicle.Exterior.VisibilityCondition
Description: Assessed visibility condition outside the vehicle.
Comment: Reports the dominant cause of reduced visibility. UNKNOWN (0) shall be used when visibility condition cannot be assessed (e.g., camera unavailable or confidence below threshold). CLEAR (1) indicates no significant visibility reduction. LOW_* values indicate conditions that materially reduce driver or sensor visibility range. Values are aligned with SENSORIS v1.6 VisibilityCondition.TypeAndConfidence. Determination method is implementation specific. May be derived from camera-based classification, Vehicle.Body.Raindetection.Intensity, Vehicle.Exterior.AirTemperature, and Vehicle.Body.Windshield.Wiping.Mode. Complements Vehicle.Exterior.VisibilityDistance for quantitative range. Primary consumers: ADAS systems, navigation (dynamic re-routing), and emergency dispatch systems.
flowchart LR Vehicle-->Exterior Exterior-->VisibilityCondition

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.VisibilityCondition
[get]  OK
Vehicle.Exterior.VisibilityCondition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.VisibilityCondition 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.VisibilityCondition

Data Type & Unit
Path Vehicle.Exterior.VisibilityCondition 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.VisibilityCondition is a Sensor.

The vehicle signal Vehicle.Exterior.VisibilityCondition 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.

13 - VisibilityDistance
Full qualified VSS Path: Vehicle.Exterior.VisibilityDistance
Description: Estimated visible distance ahead of the vehicle in current conditions.
Comment: Forward visibility range in meters as assessed by the vehicle’s sensing systems. 0 indicates near-zero visibility. Value may be limited by sensor range rather than actual atmospheric visibility; see VisibilityCondition for the qualitative assessment. Determination method is implementation specific. May be derived from camera-based visibility estimation, lidar range reduction, or radar clutter analysis.
flowchart LR Vehicle-->Exterior Exterior-->VisibilityDistance

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.VisibilityDistance
[get]  OK
Vehicle.Exterior.VisibilityDistance: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.VisibilityDistance 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.VisibilityDistance

Data Type & Unit
Path Vehicle.Exterior.VisibilityDistance VSS: Addressing nodes
Data type float VSS: Datatypes
Unit m VSS: Units
Label meter
Description Length measured in meters VSS: Sensors & Actuators
Domain length
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.VisibilityDistance 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.

14 - WindDirection
Full qualified VSS Path: Vehicle.Exterior.WindDirection
Description: Wind direction in degrees (meteorological convention, 0 = North, 90 = East).
Comment: Wind direction from which wind is blowing, using meteorological convention (0 = from North, 90 = from East, 180 = from South, 270 = from West). Only meaningful when WindSpeed is above a minimum threshold; value when WindSpeed is near 0 is implementation specific.
flowchart LR Vehicle-->Exterior Exterior-->WindDirection

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.WindDirection
[get]  OK
Vehicle.Exterior.WindDirection: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.WindDirection 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.WindDirection

Data Type & Unit
Path Vehicle.Exterior.WindDirection VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle
Minimum value 0 VSS: Sensors & Actuators
Maximum value 360 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.WindDirection 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.

15 - WindSpeed
Full qualified VSS Path: Vehicle.Exterior.WindSpeed
Description: Surface wind speed outside the vehicle.
Comment: Measured or estimated wind speed in meters per second. May be derived from anemometer sensors, aerodynamic load estimation, or external weather service input.
flowchart LR Vehicle-->Exterior Exterior-->WindSpeed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Exterior.WindSpeed
[get]  OK
Vehicle.Exterior.WindSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Exterior.WindSpeed 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.WindSpeed

Data Type & Unit
Path Vehicle.Exterior.WindSpeed VSS: Addressing nodes
Data type float VSS: Datatypes
Unit m/s VSS: Units
Label meters per second
Description Speed measured in meters per second VSS: Sensors & Actuators
Domain velocity
Minimum value 0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

The vehicle signal Vehicle.Exterior.WindSpeed 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.