Chassis

• 1: Accelerator
• 1.1: PedalPosition
• 2: AxleCount
• 3: Brake
• 3.1: IsDriverEmergencyBrakingDetected
• 3.2: PedalPosition
• 4: ParkingBrake
• 4.1: IsEngaged
• 5: SteeringWheel
• 5.1: Angle
• 5.2: Extension
• 5.3: Position
• 5.4: Tilt
• 6: Axle
• 6.1: Row1
• 6.1.1: SteeringAngle
• 6.1.2: TireAspectRatio
• 6.1.3: TireDiameter
• 6.1.4: TireWidth
• 6.1.5: Wheel
• 6.1.5.1: Left
• 6.1.5.1.1: Brake
• 6.1.5.1.1.1: FluidLevel
• 6.1.5.1.1.2: IsBrakesWorn
• 6.1.5.1.1.3: IsFluidLevelLow
• 6.1.5.1.1.4: PadWear
• 6.1.5.1.2: Speed
• 6.1.5.1.3: Tire
• 6.1.5.1.3.1: IsPressureLow
• 6.1.5.1.3.2: Pressure
• 6.1.5.1.3.3: Temperature
• 6.1.5.2: Right
• 6.1.5.2.1: Brake
• 6.1.5.2.1.1: FluidLevel
• 6.1.5.2.1.2: IsBrakesWorn
• 6.1.5.2.1.3: IsFluidLevelLow
• 6.1.5.2.1.4: PadWear
• 6.1.5.2.2: Speed
• 6.1.5.2.3: Tire
• 6.1.5.2.3.1: IsPressureLow
• 6.1.5.2.3.2: Pressure
• 6.1.5.2.3.3: Temperature
• 6.1.6: WheelCount
• 6.1.7: WheelDiameter
• 6.1.8: WheelWidth
• 6.2: Row2
• 6.2.1: SteeringAngle
• 6.2.2: TireAspectRatio
• 6.2.3: TireDiameter
• 6.2.4: TireWidth
• 6.2.5: Wheel
• 6.2.5.1: Right
• 6.2.5.1.1: Brake
• 6.2.5.1.1.1: FluidLevel
• 6.2.5.1.1.2: IsBrakesWorn
• 6.2.5.1.1.3: IsFluidLevelLow
• 6.2.5.1.1.4: PadWear
• 6.2.5.1.2: Speed
• 6.2.5.1.3: Tire
• 6.2.5.1.3.1: IsPressureLow
• 6.2.5.1.3.2: Pressure
• 6.2.5.1.3.3: Temperature
• 6.2.5.2: Left
• 6.2.5.2.1: Speed
• 6.2.5.2.2: Tire
• 6.2.5.2.2.1: IsPressureLow
• 6.2.5.2.2.2: Pressure
• 6.2.5.2.2.3: Temperature
• 6.2.5.2.3: Brake
• 6.2.5.2.3.1: FluidLevel
• 6.2.5.2.3.2: IsBrakesWorn
• 6.2.5.2.3.3: IsFluidLevelLow
• 6.2.5.2.3.4: PadWear
• 6.2.6: WheelCount
• 6.2.7: WheelDiameter
• 6.2.8: WheelWidth
• 7: Track
• 8: Wheelbase

1 - Accelerator

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

The vehicle signal Vehicle.Chassis.Accelerator is a Branch.

UUID

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

The UUID for Vehicle.Chassis.Accelerator is 3b2b562086a45eb29c55186f3b710621

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.Accelerator.PedalPosition (Accelerator pedal position as percent. 0 = Not depressed. 100 = Fully depressed.)

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

1.1 - PedalPosition

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Accelerator.PedalPosition
[get]  OK
Vehicle.Chassis.Accelerator.PedalPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Accelerator.PedalPosition 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).

Signal Information

The vehicle signal Vehicle.Chassis.Accelerator.PedalPosition is a Sensor.

The vehicle signal Vehicle.Chassis.Accelerator.PedalPosition is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Accelerator.PedalPosition is 2fabd8b61db45f62b4e97e7a612b4a73

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2 - AxleCount

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.AxleCount
[get]  OK
Vehicle.Chassis.AxleCount: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.AxleCount 2
[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).

Signal Information

The vehicle signal Vehicle.Chassis.AxleCount is an Attribute.

The vehicle signal Vehicle.Chassis.AxleCount is a Signal.

UUID

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

The UUID for Vehicle.Chassis.AxleCount is 86d084c9148d5f22b5402a030413ed79

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

3 - Brake

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

The vehicle signal Vehicle.Chassis.Brake is a Branch.

UUID

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

The UUID for Vehicle.Chassis.Brake is 38df972e5c6b558e93839a5e97238c5a

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.Brake.IsDriverEmergencyBrakingDetected (Indicates if emergency braking initiated by driver is detected. True = Emergency braking detected. False = Emergency braking not detected.)
• Vehicle.Chassis.Brake.PedalPosition (Brake pedal position as percent. 0 = Not depressed. 100 = Fully depressed.)

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.

3.1 - IsDriverEmergencyBrakingDetected

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Brake.IsDriverEmergencyBrakingDetected
[get]  OK
Vehicle.Chassis.Brake.IsDriverEmergencyBrakingDetected: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Brake.IsDriverEmergencyBrakingDetected 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.

Signal Information

The vehicle signal Vehicle.Chassis.Brake.IsDriverEmergencyBrakingDetected is a Sensor.

The vehicle signal Vehicle.Chassis.Brake.IsDriverEmergencyBrakingDetected is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Brake.IsDriverEmergencyBrakingDetected is 0d462892aeac5062a62ee7d07306f6a6

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

3.2 - PedalPosition

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Brake.PedalPosition
[get]  OK
Vehicle.Chassis.Brake.PedalPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Brake.PedalPosition 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).

Signal Information

The vehicle signal Vehicle.Chassis.Brake.PedalPosition is a Sensor.

The vehicle signal Vehicle.Chassis.Brake.PedalPosition is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Brake.PedalPosition is 0477d3a4a831564ea473976cf34374f2

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

4 - ParkingBrake

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

The vehicle signal Vehicle.Chassis.ParkingBrake is a Branch.

UUID

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

The UUID for Vehicle.Chassis.ParkingBrake is 3849d42292f4551590fa4bf716fc90f7

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.ParkingBrake.IsEngaged (Parking brake status. True = Parking Brake is Engaged. False = Parking Brake is not Engaged.)

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.

4.1 - IsEngaged

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.ParkingBrake.IsEngaged
[get]  OK
Vehicle.Chassis.ParkingBrake.IsEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.ParkingBrake.IsEngaged 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.

Signal Information

The vehicle signal Vehicle.Chassis.ParkingBrake.IsEngaged is an Actuator.

The vehicle signal Vehicle.Chassis.ParkingBrake.IsEngaged is a Signal.

UUID

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

The UUID for Vehicle.Chassis.ParkingBrake.IsEngaged is faa7f94e6a5555c6b2d62e3328520ce0

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

5 - SteeringWheel

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

The vehicle signal Vehicle.Chassis.SteeringWheel is a Branch.

UUID

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

The UUID for Vehicle.Chassis.SteeringWheel is 8c759072791e5986ac4efe9df0c2b751

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.SteeringWheel.Angle (Steering wheel angle. Positive = degrees to the left. Negative = degrees to the right.)
• Vehicle.Chassis.SteeringWheel.Extension (Steering wheel column extension from dashboard. 0 = Closest to dashboard. 100 = Furthest from dashboard.)
• Vehicle.Chassis.SteeringWheel.Position (Position of the steering wheel on the left or right side of the vehicle.)
• Vehicle.Chassis.SteeringWheel.Tilt (Steering wheel column tilt. 0 = Lowest position. 100 = Highest position.)

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.

5.1 - Angle

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.SteeringWheel.Angle
[get]  OK
Vehicle.Chassis.SteeringWheel.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.SteeringWheel.Angle 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).

Signal Information

The vehicle signal Vehicle.Chassis.SteeringWheel.Angle is a Sensor.

The vehicle signal Vehicle.Chassis.SteeringWheel.Angle is a Signal.

UUID

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

The UUID for Vehicle.Chassis.SteeringWheel.Angle is 92cd3b3d37585b2291806fe5127d9393

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

5.2 - Extension

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.SteeringWheel.Extension
[get]  OK
Vehicle.Chassis.SteeringWheel.Extension: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.SteeringWheel.Extension 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).

Signal Information

The vehicle signal Vehicle.Chassis.SteeringWheel.Extension is an Actuator.

The vehicle signal Vehicle.Chassis.SteeringWheel.Extension is a Signal.

UUID

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

The UUID for Vehicle.Chassis.SteeringWheel.Extension is 6a84cc3604fc5960a1fb384fe63fae72

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

5.3 - Position

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.SteeringWheel.Position
[get]  OK
Vehicle.Chassis.SteeringWheel.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.SteeringWheel.Position FRONT_LEFT
[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.

Signal Information

The vehicle signal Vehicle.Chassis.SteeringWheel.Position is an Attribute.

The vehicle signal Vehicle.Chassis.SteeringWheel.Position is a Signal.

UUID

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

The UUID for Vehicle.Chassis.SteeringWheel.Position is 314d6eeeba195098b36ae7f476d27824

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

5.4 - Tilt

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.SteeringWheel.Tilt
[get]  OK
Vehicle.Chassis.SteeringWheel.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.SteeringWheel.Tilt 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).

Signal Information

The vehicle signal Vehicle.Chassis.SteeringWheel.Tilt is an Actuator.

The vehicle signal Vehicle.Chassis.SteeringWheel.Tilt is a Signal.

UUID

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

The UUID for Vehicle.Chassis.SteeringWheel.Tilt is 33e979769f91521d8080384447d06c00

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6 - Axle

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

The vehicle signal Vehicle.Chassis.Axle is a Branch.

UUID

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

The UUID for Vehicle.Chassis.Axle is 0a3ebde7efa85c04ac6c29b5676fec5d

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.Axle.Row1 (Axle signals)
• Vehicle.Chassis.Axle.Row2 (Axle signals)

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.

6.1 - Row1

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1 is a Branch.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1 is d7e93a94af0752aaab36819f6be4f67a

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.Axle.Row1.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.Row1.TireAspectRatio (Aspect ratio between tire section height and tire section width, as per ETRTO / TRA standard.)
• Vehicle.Chassis.Axle.Row1.TireDiameter (Outer diameter of tires, in inches, as per ETRTO / TRA standard.)
• Vehicle.Chassis.Axle.Row1.TireWidth (Nominal section width of tires, in mm, as per ETRTO / TRA standard.)
• Vehicle.Chassis.Axle.Row1.Wheel (Wheel signals for axle)
• Vehicle.Chassis.Axle.Row1.WheelCount (Number of wheels on the axle)
• Vehicle.Chassis.Axle.Row1.WheelDiameter (Diameter of wheels (rims without tires), in inches, as per ETRTO / TRA standard.)
• Vehicle.Chassis.Axle.Row1.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.

6.1.1 - SteeringAngle

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row1.SteeringAngle
[get]  OK
Vehicle.Chassis.Axle.Row1.SteeringAngle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.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

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.SteeringAngle is a Sensor.

The vehicle signal Vehicle.Chassis.Axle.Row1.SteeringAngle is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.SteeringAngle is 91310e9ef88450c68791fbb07d83f104

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.2 - TireAspectRatio

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row1.TireAspectRatio
[get]  OK
Vehicle.Chassis.Axle.Row1.TireAspectRatio: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.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).

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.TireAspectRatio is an Attribute.

The vehicle signal Vehicle.Chassis.Axle.Row1.TireAspectRatio is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.TireAspectRatio is 716fec24167e5c36b2b97daaf091f911

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.3 - TireDiameter

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row1.TireDiameter
[get]  OK
Vehicle.Chassis.Axle.Row1.TireDiameter: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.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

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.TireDiameter is an Attribute.

The vehicle signal Vehicle.Chassis.Axle.Row1.TireDiameter is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.TireDiameter is ed9f037c1b5d53c78c90b71179db1f4f

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.4 - TireWidth

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row1.TireWidth
[get]  OK
Vehicle.Chassis.Axle.Row1.TireWidth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.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).

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.TireWidth is an Attribute.

The vehicle signal Vehicle.Chassis.Axle.Row1.TireWidth is a Signal.

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.TireWidth is 3444d8773c215cd7a076d688eb7f1afc

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.5 - Wheel

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.Wheel is 8ed02c02eee0502ba6d94a5d5f1fb789

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.Axle.Row1.Wheel.Left (Wheel signals for axle)
• Vehicle.Chassis.Axle.Row1.Wheel.Right (Wheel signals for axle)

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.

6.1.5.1 - Left

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left is 0cd478c6e72b55c6be6d3d9df9624545

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake (Brake signals for wheel)
• Vehicle.Chassis.Axle.Row1.Wheel.Left.Speed (Rotational speed of a vehicle’s wheel.)
• Vehicle.Chassis.Axle.Row1.Wheel.Left.Tire (Tire signals for wheel.)

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.

6.1.5.1.1 - Brake

Navigation

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Signal Information

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake is 162dab13d5815ec4bc22888b0bc59cbf

Children

This vehicle signal is a branch or structure and thus has sub-pages:

• Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.FluidLevel (Brake fluid level as percent. 0 = Empty. 100 = Full.)
• Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.IsBrakesWorn (Brake pad wear status. True = Worn. False = Not Worn.)
• Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.IsFluidLevelLow (Brake fluid level status. True = Brake fluid level low. False = Brake fluid level OK.)
• Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.PadWear (Brake pad wear as percent. 0 = No Wear. 100 = Worn.)

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.

6.1.5.1.1.1 - FluidLevel

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.FluidLevel is a Sensor.

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.FluidLevel is 63aa9c4973ef50b18bd7214c9f2634c5

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.5.1.1.2 - IsBrakesWorn

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.IsBrakesWorn is a Sensor.

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.IsBrakesWorn is 901771088eb35dec9e69b56a8cb3e8f5

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.5.1.1.3 - IsFluidLevelLow

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.IsFluidLevelLow is a Sensor.

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.IsFluidLevelLow is 713da56818e55714ac441e10870b3753

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.5.1.1.4 - PadWear

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Signal Information

The vehicle signal Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.PadWear is a Sensor.

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

UUID

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

The UUID for Vehicle.Chassis.Axle.Row1.Wheel.Left.Brake.PadWear is b4ed36f8143d512fadaca3e641739ee2

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:

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6.1.5.1.2 - Speed

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Chassis.Axle.Row1.Wheel.Left.Speed
[get]  OK
Vehicle.Chassis.Axle.Row1.Wheel.Left.Speed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Chassis.Axle.Row1.Wheel.Left.Speed 0
[set]  OK