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.Row1.Wheel.Left.Tire
Description: Tire signals for wheel.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row1 Row1-->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.Row1.Wheel.Left.Tire

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire is 17c60ec3c02054b4951c975156375d9a

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 - IsPressureLow
Full qualified VSS Path: Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.IsPressureLow
Description: Tire Pressure Status. True = Low tire pressure. False = Good tire pressure.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row1 Row1-->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.Row1.Wheel.Left.Tire.IsPressureLow
[get]  OK
Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.IsPressureLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.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.Row1.Wheel.Left.Tire.IsPressureLow

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

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.IsPressureLow is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.IsPressureLow is 4088315cfaa05c28b51c3d3462c65339

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 - Pressure
Full qualified VSS Path: Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Pressure
Description: Tire pressure in kilo-Pascal.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row1 Row1-->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.Row1.Wheel.Left.Tire.Pressure
[get]  OK
Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Pressure: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.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.Row1.Wheel.Left.Tire.Pressure

Data Type & Unit
Path Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Pressure VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit kPa VSS: Units
Label kilopascal
Description Pressure measured in kilopascal VSS: Sensors & Actuators
Domain pressure

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.Row1.Wheel.Left.Tire.Pressure is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Pressure is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Pressure is 9fa3f176fd975d28a68f70c7d72e370f

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 - Temperature
Full qualified VSS Path: Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Temperature
Description: Tire temperature in Celsius.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row1 Row1-->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.Row1.Wheel.Left.Tire.Temperature
[get]  OK
Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.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.Row1.Wheel.Left.Tire.Temperature

Data Type & Unit
Path Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Temperature VSS: Addressing nodes
Data type float VSS: Datatypes
Unit celsius VSS: Units
Label degree celsius
Description Temperature measured in degree celsius VSS: Sensors & Actuators
Domain temperature

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.Row1.Wheel.Left.Tire.Temperature is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Temperature is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire.Temperature is 093d8fb119755f6bafa979e4eae201a0

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.