This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Row2
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2 |
| Description: |
Axle signals |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
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 is a Branch.
Children
This vehicle signal is a branch or structure and thus has sub-pages:
- Vehicle.Chassis.Axle.Row2.AxleWidth (The lateral distance between the wheel mounting faces, measured along the spindle axis.)
- Vehicle.Chassis.Axle.Row2.SteeringAngle (Single track two-axle model steering angle. Angle according to ISO 8855. Positive = degrees to the left. Negative = degrees to the right.)
- Vehicle.Chassis.Axle.Row2.TireAspectRatio (Aspect ratio between tire section height and tire section width, as per ETRTO / TRA standard.)
- Vehicle.Chassis.Axle.Row2.TireDiameter (Outer diameter of tires, in inches, as per ETRTO / TRA standard.)
- Vehicle.Chassis.Axle.Row2.TireWidth (Nominal section width of tires, in mm, as per ETRTO / TRA standard.)
- Vehicle.Chassis.Axle.Row2.Torque (Incoming axle torque to differential. Negative values indicate regen mode.)
- Vehicle.Chassis.Axle.Row2.TrackWidth (The lateral distance between the centers of the wheels, measured along the spindle, or axle axis. If there are dual rear wheels, measure from the midway points between the inner and outer tires.)
- Vehicle.Chassis.Axle.Row2.TreadWidth (The lateral distance between the centerlines of the base tires at ground, including camber angle. If there are dual rear wheels, measure from the midway points between the inner and outer tires.)
- Vehicle.Chassis.Axle.Row2.Wheel (Wheel signals for axle)
- Vehicle.Chassis.Axle.Row2.WheelCount (Number of wheels on the axle)
- Vehicle.Chassis.Axle.Row2.WheelDiameter (Diameter of wheels (rims without tires), in inches, as per ETRTO / TRA standard.)
- Vehicle.Chassis.Axle.Row2.WheelWidth (Width of wheels (rims without tires), in inches, as per ETRTO / TRA standard.)
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 - AxleWidth
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.AxleWidth |
| Description: |
The lateral distance between the wheel mounting faces, measured along the spindle axis. |
| Comment: |
Corresponds to SAE J1100-2009 W113. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->AxleWidth
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.AxleWidth
[get] OK
Vehicle.Chassis.Axle.Row2.AxleWidth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.AxleWidth 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.AxleWidth is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.AxleWidth 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:
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 - SteeringAngle
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.SteeringAngle |
| Description: |
Single track two-axle model steering angle. Angle according to ISO 8855. Positive = degrees to the left. Negative = degrees to the right. |
| Comment: |
Single track two-axle model steering angle refers to the angle that a centrally mounted wheel would have. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->SteeringAngle
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.SteeringAngle
[get] OK
Vehicle.Chassis.Axle.Row2.SteeringAngle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.SteeringAngle 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.SteeringAngle is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.SteeringAngle 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:
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 - TireAspectRatio
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.TireAspectRatio |
| Description: |
Aspect ratio between tire section height and tire section width, as per ETRTO / TRA standard. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->TireAspectRatio
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.TireAspectRatio
[get] OK
Vehicle.Chassis.Axle.Row2.TireAspectRatio: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.TireAspectRatio 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.TireAspectRatio is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.TireAspectRatio 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:
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 - TireDiameter
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.TireDiameter |
| Description: |
Outer diameter of tires, in inches, as per ETRTO / TRA standard. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->TireDiameter
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.TireDiameter
[get] OK
Vehicle.Chassis.Axle.Row2.TireDiameter: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.TireDiameter 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.TireDiameter is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.TireDiameter 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:
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 - TireWidth
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.TireWidth |
| Description: |
Nominal section width of tires, in mm, as per ETRTO / TRA standard. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->TireWidth
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.TireWidth
[get] OK
Vehicle.Chassis.Axle.Row2.TireWidth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.TireWidth 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.TireWidth is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.TireWidth 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:
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 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Torque |
| Description: |
Incoming axle torque to differential. Negative values indicate regen mode. |
| Comment: |
For combustion engine this typically corresponds to the output torque of the multi-speed gearbox. For electrical motor this typically corresponds to the output torque of the single-speed reduction-gear. This signal is typically not used if there is separate electrical motors for left and right wheels. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Torque
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.Torque
[get] OK
Vehicle.Chassis.Axle.Row2.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Torque 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 int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.Chassis.Axle.Row2.Torque is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Torque 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
7 - TrackWidth
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.TrackWidth |
| Description: |
The lateral distance between the centers of the wheels, measured along the spindle, or axle axis. If there are dual rear wheels, measure from the midway points between the inner and outer tires. |
| Comment: |
Corresponds to SAE J1100-2009 W102. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->TrackWidth
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.TrackWidth
[get] OK
Vehicle.Chassis.Axle.Row2.TrackWidth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.TrackWidth 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.TrackWidth is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.TrackWidth 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
8 - TreadWidth
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.TreadWidth |
| Description: |
The lateral distance between the centerlines of the base tires at ground, including camber angle. If there are dual rear wheels, measure from the midway points between the inner and outer tires. |
| Comment: |
Corresponds to SAE J1100-2009 W101. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->TreadWidth
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.TreadWidth
[get] OK
Vehicle.Chassis.Axle.Row2.TreadWidth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.TreadWidth 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.TreadWidth is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.TreadWidth 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9 - 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.
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.
9.1 - 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.
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.
9.1.1 - AngularSpeed
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.AngularSpeed |
| Description: |
Angular (Rotational) speed of a vehicle’s wheel. |
| Comment: |
Positive if wheel is trying to drive vehicle forward. Negative if wheel is trying to drive vehicle backward. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Left
Left-->AngularSpeed
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.AngularSpeed
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.AngularSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.AngularSpeed 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.AngularSpeed is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.AngularSpeed 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.1.2 - 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.
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.
9.1.2.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.
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.
9.1.2.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.
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.
9.1.2.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.
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.
9.1.2.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.
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.
9.1.3 - Speed
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Speed |
| Description: |
Linear 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.
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.
9.1.4 - 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.
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.
9.1.4.1 - AirTemperature
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.AirTemperature |
| Description: |
Air temperature inside the tire in Celsius. |
Navigation
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.
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.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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.1.4.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. |
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.
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.
9.1.4.3 - 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.
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.
9.1.4.4 - RubberTemperature
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Tire.RubberTemperature |
| Description: |
Rubber temperature of the tire in Celsius. |
Navigation
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.
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.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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.1.4.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. |
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.
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.
9.1.4.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). |
|
|
Navigation
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.
Data Type & Unit
Note: The string datatype is a character string.
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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.1.5 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Left.Torque |
| Description: |
Torque provided by drivetrain, excluding torque provided by friction brakes. Negative values indicate regen mode. |
| Comment: |
This is typically the torque provided by the differential, or by a motor dedicated for this wheel, after reduction gear if present. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Left
Left-->Torque
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.Torque
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Left.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Left.Torque 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 int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Torque is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Left.Torque 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.2 - 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.
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.
9.2.1 - AngularSpeed
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.AngularSpeed |
| Description: |
Angular (Rotational) speed of a vehicle’s wheel. |
| Comment: |
Positive if wheel is trying to drive vehicle forward. Negative if wheel is trying to drive vehicle backward. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->AngularSpeed
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.AngularSpeed
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.AngularSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.AngularSpeed 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.AngularSpeed is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.AngularSpeed 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.2.2 - Speed
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Speed |
| Description: |
Linear 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.
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.
9.2.3 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Torque |
| Description: |
Torque provided by drivetrain, excluding torque provided by friction brakes. Negative values indicate regen mode. |
| Comment: |
This is typically the torque provided by the differential, or by a motor dedicated for this wheel, after reduction gear if present. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->Torque
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.Torque
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.Torque 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 int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Torque is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Torque 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.2.4 - 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.
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.
9.2.4.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.
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.
9.2.4.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.
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.
9.2.4.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.
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.
9.2.4.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.
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.
9.2.5 - 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.
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.
9.2.5.1 - WinterStatus
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.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). |
|
|
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Tire.WinterStatus
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.WinterStatus: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
Data Type & Unit
Note: The string datatype is a character string.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.WinterStatus is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.2.5.2 - AirTemperature
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.AirTemperature |
| Description: |
Air temperature inside the tire in Celsius. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Tire.AirTemperature
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.AirTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
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.AirTemperature is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.2.5.3 - 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.
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.
9.2.5.4 - 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.
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.
9.2.5.5 - RubberTemperature
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.RubberTemperature |
| Description: |
Rubber temperature of the tire in Celsius. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.Tire.RubberTemperature
[get] OK
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.RubberTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.Wheel.Right.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.
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.RubberTemperature is a Sensor.
The vehicle signal Vehicle.Chassis.Axle.Row2.Wheel.Right.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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
9.2.5.6 - Temperature
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.Wheel.Right.Tire.Temperature |
| Description: |
Tire temperature in Celsius. |
| Deprecation |
v6.0 - use RubberTemperature or AirTemperature instead. |
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.
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.
10 - WheelCount
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.WheelCount |
| Description: |
Number of wheels on the axle |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->WheelCount
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.WheelCount
[get] OK
Vehicle.Chassis.Axle.Row2.WheelCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.WheelCount 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.WheelCount is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.WheelCount 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
11 - WheelDiameter
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.WheelDiameter |
| Description: |
Diameter of wheels (rims without tires), in inches, as per ETRTO / TRA standard. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->WheelDiameter
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.WheelDiameter
[get] OK
Vehicle.Chassis.Axle.Row2.WheelDiameter: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.WheelDiameter 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.WheelDiameter is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.WheelDiameter 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:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
12 - WheelWidth
|
|
| Full qualified VSS Path: |
Vehicle.Chassis.Axle.Row2.WheelWidth |
| Description: |
Width of wheels (rims without tires), in inches, as per ETRTO / TRA standard. |
Navigation
flowchart LR
Vehicle-->Chassis
Chassis-->Axle
Axle-->Row2
Row2-->WheelWidth
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.WheelWidth
[get] OK
Vehicle.Chassis.Axle.Row2.WheelWidth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row2.WheelWidth 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.WheelWidth is an Attribute.
The vehicle signal Vehicle.Chassis.Axle.Row2.WheelWidth 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:
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.