This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Wheel
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel |
Description: |
Wheel signals for axle |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Chassis.Axle.Row2.Wheel
is 87b119ed6de254159877b24047fd3026
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:
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 - Right
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right |
Description: |
Wheel signals for axle |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Right
is f59f6ce66b1454498f5dc71be581732a
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:
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.1 - Brake
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake |
Description: |
Brake signals for wheel |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->Brake
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake
is 5c33ec4bd8a15d3590f59e7257bf4d25
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:
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.1.1 - FluidLevel
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.FluidLevel |
Description: |
Brake fluid level as percent. 0 = Empty. 100 = Full. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Brake.FluidLevel
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.FluidLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The uint8
datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.FluidLevel
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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.Right.Brake.FluidLevel
is 83e5e261302d5ab38c9ee4dddc18c8ae
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:
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.
1.1.2 - IsBrakesWorn
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.IsBrakesWorn |
Description: |
Brake pad wear status. True = Worn. False = Not Worn. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Brake.IsBrakesWorn
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.IsBrakesWorn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.IsBrakesWorn
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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.Right.Brake.IsBrakesWorn
is 9b5963e98a9c5b229a61df76ef5c86e0
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:
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.
1.1.3 - IsFluidLevelLow
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.IsFluidLevelLow |
Description: |
Brake fluid level status. True = Brake fluid level low. False = Brake fluid level OK. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Brake.IsFluidLevelLow
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.IsFluidLevelLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.IsFluidLevelLow
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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.Right.Brake.IsFluidLevelLow
is 727823c7e0d551f48f26a5dd4f0578bd
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:
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.
1.1.4 - PadWear
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.PadWear |
Description: |
Brake pad wear as percent. 0 = No Wear. 100 = Worn. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Brake.PadWear
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.PadWear: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The uint8
datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Brake.PadWear
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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.Right.Brake.PadWear
is 63a564bca18a5b1fabd7d3cff1af0e6d
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:
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.
1.2 - Speed
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Speed |
Description: |
Rotational speed of a vehicle’s wheel. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Speed
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Speed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.Speed 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Speed
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Speed
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Right.Speed
is 85b41a82f4775fcea57dcc6218fb6d7b
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:
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.
1.3 - Tire
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire |
Description: |
Tire signals for wheel. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->Tire
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire
is d855fe9ffb4e52be83ebfc7967c1c3ee
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:
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.3.1 - IsPressureLow
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.IsPressureLow |
Description: |
Tire Pressure Status. True = Low tire pressure. False = Good tire pressure. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Tire.IsPressureLow
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.IsPressureLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.IsPressureLow
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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.Right.Tire.IsPressureLow
is da2f63312a455d92abd5edc405f01903
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:
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.
1.3.2 - Pressure
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Pressure |
Description: |
Tire pressure in kilo-Pascal. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Tire.Pressure
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Pressure: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The uint16
datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Pressure
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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.Right.Tire.Pressure
is 0cd3dd4be36c5fcda49d6360556ba7c8
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:
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.
1.3.3 - Temperature
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Temperature |
Description: |
Tire temperature in Celsius. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Tire.Temperature
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Temperature
is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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.Right.Tire.Temperature
is 7c08b5778bc05265bb8d4e08fdca29cf
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:
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 - Left
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left |
Description: |
Wheel signals for axle |
Navigation
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.
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:
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 - Speed
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Speed |
Description: |
Rotational speed of a vehicle’s wheel. |
Navigation
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.
Data Type & Unit
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
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:
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 - Tire
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire |
Description: |
Tire signals for wheel. |
Navigation
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.
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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.2 - Pressure
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Pressure |
Description: |
Tire pressure in kilo-Pascal. |
Navigation
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.
Data Type & Unit
Note: The uint16
datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
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:
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.3 - Temperature
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.Temperature |
Description: |
Tire temperature in Celsius. |
Navigation
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.
Data Type & Unit
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
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:
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 - Brake
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake |
Description: |
Brake signals for wheel |
Navigation
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.
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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The uint8
datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
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:
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.2 - IsBrakesWorn
|
|
Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Brake.IsBrakesWorn |
Description: |
Brake pad wear status. True = Worn. False = Not Worn. |
Navigation
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.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The uint8
datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
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:
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.