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

Return to the regular view of this page.

Tire
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire
Description: Tire signals for wheel.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Tire

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.Chassis.Axle.Row2.Wheel.Left.Tire

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire 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 - AirTemperature
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.AirTemperature
Description: Air temperature inside the tire in Celsius.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Tire Tire-->AirTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.AirTemperature
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.AirTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.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.Chassis.Axle.Row2.Wheel.Left.Tire.AirTemperature

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.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.Chassis.Axle.Row2.Wheel.Left.Tire.AirTemperature is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.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.

2 - IsPressureLow
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow
Description: Tire Pressure Status. True = Low tire pressure. False = Good tire pressure.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Tire Tire-->IsPressureLow

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow false
[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.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow 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 - Pressure
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure
Description: Tire pressure in kilo-Pascal.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Tire Tire-->Pressure

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure 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.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit kPa VSS: Units

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure 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 - RubberTemperature
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature
Description: Rubber temperature of the tire in Celsius.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Tire Tire-->RubberTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature 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.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature 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.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature 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 - Temperature
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature
Description: Tire temperature in Celsius.
Deprecation v6.0 - use RubberTemperature or AirTemperature instead.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Tire Tire-->Temperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature 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.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature 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.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature 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 - WinterStatus
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus
Description: Winter (cold-weather / snow) capability class of the tire currently fitted to this wheel.
Comment: Describes the cold-weather grip capability of the fitted tire, which is the primary determinant of available traction on snow and ice. Modelled as an attribute because it is a property of the mounted equipment that changes only when tires are swapped, not a continuously varying measurement. WINTER indicates a dedicated winter / snow tire (e.g. carrying the three-peak-mountain-snowflake 3PMSF marking), designed for cold-weather rubber compounds and tread patterns that retain grip below approximately 7 degrees Celsius and on snow / ice. NON_WINTER covers summer and all-season tires alike: neither is a dedicated winter tire, and from a snow-traction standpoint both leave the vehicle with materially reduced cold-weather grip. The summer-vs-all-season distinction is a longevity / comfort property that does not change the snow-safety answer and is therefore intentionally not split here. UNKNOWN shall be used when the fitted-tire winter capability cannot be determined (e.g. no tire-identification data available, or input confidence below threshold). Primary consumers: driver-warning systems and navigation systems that adapt snow / mountain-pass routing and advisory thresholds to the grip the vehicle actually has. Combined with per-wheel placement, allows detection of mismatched or partially-fitted winter tire sets. Criteria for each state may be OEM-, market-, or jurisdiction-specific (e.g. national winter-tire regulations differ). Related to VSS issue #877 (Connected Safety signals).
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Tire Tire-->WinterStatus

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus UNKNOWN
[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.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus VSS: Addressing nodes
Data type string VSS: Datatypes
Default value UNKNOWN VSS: Sensors & Actuators
Allowed values ['UNKNOWN', 'NON_WINTER', 'WINTER'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus is an Attribute.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.WinterStatus 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.