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

Return to the regular view of this page.

Left
Full qualified VSS Path: Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left
Description: MotionManagement signals for a specific wheel.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Brake Brake-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left

Signal Information

The vehicle signal Vehicle.MotionManagement.Brake.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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

1 - OmegaLower
Full qualified VSS Path: Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower
Description: Lower wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Brake Brake-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->OmegaLower

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower
[get]  OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower

Data Type & Unit
Path Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit rad/s VSS: Units
Label radians per second
Description Angular speed measured in radians per second VSS: Sensors & Actuators
Domain angular-speed

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.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower is an Actuator.

The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower 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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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

2 - OmegaUpper
Full qualified VSS Path: Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper
Description: Upper wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Brake Brake-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->OmegaUpper

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper
[get]  OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper

Data Type & Unit
Path Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit rad/s VSS: Units
Label radians per second
Description Angular speed measured in radians per second VSS: Sensors & Actuators
Domain angular-speed

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.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper is an Actuator.

The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper 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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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

3 - Torque
Full qualified VSS Path: Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque
Description: Estimated friction brake torque. Brake Torque < 0Nm.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Brake Brake-->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.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque
[get]  OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque

Data Type & Unit
Path Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit Nm VSS: Units
Maximum value 0 VSS: Sensors & Actuators

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

The vehicle signal Vehicle.MotionManagement.Brake.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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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

4 - TorqueArbitrated
Full qualified VSS Path: Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated
Description: Brake system internally calculated friction brake torque target. Brake Torque < 0Nm.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Brake Brake-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->TorqueArbitrated

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated
[get]  OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated

Data Type & Unit
Path Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit Nm VSS: Units
Maximum value 0 VSS: Sensors & Actuators

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

The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated 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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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

5 - TorqueFrictionMaximum
Full qualified VSS Path: Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum
Description: Maximum wheel torque request for friction brake. Brake Torque < 0Nm.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Brake Brake-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->TorqueFrictionMaximum

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum
[get]  OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum

Data Type & Unit
Path Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit Nm VSS: Units
Maximum value 0 VSS: Sensors & Actuators

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.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum is an Actuator.

The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum 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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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

6 - TorqueFrictionMinimum
Full qualified VSS Path: Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum
Description: Minimum wheel torque request for friction brake. Brake Torque < 0Nm.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Brake Brake-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->TorqueFrictionMinimum

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum
[get]  OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum

Data Type & Unit
Path Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit Nm VSS: Units
Maximum value 0 VSS: Sensors & Actuators

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.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum is an Actuator.

The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum 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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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