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

Return to the regular view of this page.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left is 4c32a1c722a45ea09a52c389e8a8a618

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 - Speed
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Speed
Description: Rotational speed of a vehicle’s wheel.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Speed

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

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Speed VSS: Addressing nodes
Data type float VSS: Datatypes
Unit km/h VSS: Units
Label kilometer per hour
Description Speed measured in kilometers per hours VSS: Sensors & Actuators
Domain speed

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.Speed is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Speed is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Speed is 427abdd04fc355769697d998a47d3f58

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire is edfee87117dc5a6f9d970167f26ec090

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.IsPressureLow is d895b1e23a4f59ec92735fc317e44769

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

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

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 - Temperature
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature
Description: Tire temperature in Celsius.
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
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.Row2.Wheel.Left.Tire.Temperature is a Sensor.

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

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 - Brake
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake
Description: Brake signals for wheel
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Brake

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

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake is a Branch.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake is 774d0a5771d35975872870cf71ea1487

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.

3.1 - FluidLevel
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.FluidLevel
Description: Brake fluid level as percent. 0 = Empty. 100 = Full.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Brake Brake-->FluidLevel

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.Brake.FluidLevel
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.FluidLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.FluidLevel 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.Brake.FluidLevel

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.FluidLevel VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Maximum value 100 VSS: Sensors & Actuators

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.Chassis.Axle.Row2.Wheel.Left.Brake.FluidLevel is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.FluidLevel is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.FluidLevel is 4b0d4f80b8855973a55ffee80fdfc4ba

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.2 - IsBrakesWorn
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsBrakesWorn
Description: Brake pad wear status. True = Worn. False = Not Worn.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Brake Brake-->IsBrakesWorn

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.Brake.IsBrakesWorn
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsBrakesWorn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsBrakesWorn 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.Brake.IsBrakesWorn

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

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsBrakesWorn is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsBrakesWorn is 3d9bae5bf0705de99789ecea26b99a5c

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.3 - IsFluidLevelLow
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsFluidLevelLow
Description: Brake fluid level status. True = Brake fluid level low. False = Brake fluid level OK.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Brake Brake-->IsFluidLevelLow

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.Brake.IsFluidLevelLow
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsFluidLevelLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsFluidLevelLow 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.Brake.IsFluidLevelLow

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

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsFluidLevelLow is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsFluidLevelLow is 01f57161b0bf539fad1d2bfa9d9a9fc4

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.4 - PadWear
Full qualified VSS Path: Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.PadWear
Description: Brake pad wear as percent. 0 = No Wear. 100 = Worn.
flowchart LR Vehicle-->Chassis Chassis-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->Brake Brake-->PadWear

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.Brake.PadWear
[get]  OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.PadWear: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.PadWear 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.Brake.PadWear

Data Type & Unit
Path Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.PadWear VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Maximum value 100 VSS: Sensors & Actuators

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.Chassis.Axle.Row2.Wheel.Left.Brake.PadWear is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.PadWear is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.PadWear is 8eff72d583015e1e94eab98bf8f0497e

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.