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.MotionManagement.Suspension.Axle.Row2
Description: MotionManagement for suspension for a specific axle.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2

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.Suspension.Axle.Row2

Signal Information

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2 is a Branch.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2 is 306830dd13bd55ba850c967936b885d5

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 - RollTorque
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.RollTorque
Description: Actuated roll torque on this axle by anti-roll actuator. Signal orientation according to ISO8855.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->RollTorque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.RollTorque
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.RollTorque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.RollTorque 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.Suspension.Axle.Row2.RollTorque

Data Type & Unit
Path Vehicle.MotionManagement.Suspension.Axle.Row2.RollTorque VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit Nm VSS: Units
Label newton meter
Description Torque measured in newton meters VSS: Sensors & Actuators
Domain torque

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.Suspension.Axle.Row2.RollTorque is a Sensor.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.RollTorque is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.RollTorque is 73f030e062d3512a99b31e13173ea465

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 - Wheel
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel
Description: MotionManagement signals for a specific wheel.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->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.

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

Signal Information

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel is a Branch.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel is dc4736439ef35ceeba1d0b42138b92c5

Children

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

2.1 - Left
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left
Description: MotionManagement signals for a specific wheel.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->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.Suspension.Axle.Row2.Wheel.Left

Signal Information

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

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left is 17c664e19d3554f8bd5ef454f73f6e13

Children

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

2.1.1 - DampingForce
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForce
Description: Actuated damping force at given wheel. Signal orientation according ISO8855, meaning positive force is pointing upwards.
Comment: Alternative signal to DampingRate.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->DampingForce

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForce
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForce: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForce 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.Suspension.Axle.Row2.Wheel.Left.DampingForce

Data Type & Unit
Path Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForce VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit N VSS: Units
Label newton
Description Force measured in newton VSS: Sensors & Actuators
Domain force

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.Suspension.Axle.Row2.Wheel.Left.DampingForce is a Sensor.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForce is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForce is be5f74e2081850a59e45926582b61614

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.1.2 - DampingForceTarget
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget
Description: Damping force request at given wheel. Signal orientation according ISO8855, meaning positive force is pointing upwards.
Comment: Alternative signal to DampingRateTarget.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->DampingForceTarget

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget 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.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget

Data Type & Unit
Path Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit N VSS: Units
Label newton
Description Force measured in newton VSS: Sensors & Actuators
Domain force

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.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget is an Actuator.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingForceTarget is a92cb43608a85ba18c111376b8c520cc

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.1.3 - DampingRate
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRate
Description: Actuated damping rate at given wheel. 0% = lowest possible damping rate 100% = highest possible damping rate
Comment: Alternative signal to DampingForce.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->DampingRate

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRate
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRate: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRate 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.Suspension.Axle.Row2.Wheel.Left.DampingRate

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

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRate is a Sensor.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRate is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRate is 2595ed8521f45251b505665673358185

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.1.4 - DampingRateTarget
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget
Description: Damping rate request at given wheel. 0% = lowest possible damping rate 100% = highest possible damping rate
Comment: Alternative signal to DampingForceTarget.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Left Left-->DampingRateTarget

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget 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.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget

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

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget is an Actuator.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left.DampingRateTarget is 58bfbfdba76d58a59ff0ae07870a30a0

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

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

2.2 - Right
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right
Description: MotionManagement signals for a specific wheel.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->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.

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

Signal Information

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right is a Branch.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right is c0068f52335c50f7a1be8560643cfeaa

Children

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

2.2.1 - DampingForce
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForce
Description: Actuated damping force at given wheel. Signal orientation according ISO8855, meaning positive force is pointing upwards.
Comment: Alternative signal to DampingRate.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Right Right-->DampingForce

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForce
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForce: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForce 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.Suspension.Axle.Row2.Wheel.Right.DampingForce

Data Type & Unit
Path Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForce VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit N VSS: Units
Label newton
Description Force measured in newton VSS: Sensors & Actuators
Domain force

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.Suspension.Axle.Row2.Wheel.Right.DampingForce is a Sensor.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForce is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForce is 2e2ee07d1c3f55f5a4666b1bf0ed2d0d

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

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

2.2.2 - DampingForceTarget
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget
Description: Damping force request at given wheel. Signal orientation according ISO8855, meaning positive force is pointing upwards.
Comment: Alternative signal to DampingRateTarget.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Right Right-->DampingForceTarget

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget 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.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget

Data Type & Unit
Path Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit N VSS: Units
Label newton
Description Force measured in newton VSS: Sensors & Actuators
Domain force

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.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget is an Actuator.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingForceTarget is 776346ee48535ff2bb831cb811f78964

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

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

2.2.3 - DampingRate
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate
Description: Actuated damping rate at given wheel. 0% = lowest possible damping rate 100% = highest possible damping rate
Comment: Alternative signal to DampingForce.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Right Right-->DampingRate

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate 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.Suspension.Axle.Row2.Wheel.Right.DampingRate

Data Type & Unit
Path Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate is a Sensor.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRate is 7467db21c7c85b149dc00cb9e264b429

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

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

2.2.4 - DampingRateTarget
Full qualified VSS Path: Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget
Description: Damping rate request at given wheel. 0% = lowest possible damping rate 100% = highest possible damping rate
Comment: Alternative signal to DampingForceTarget.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Suspension Suspension-->Axle Axle-->Row2 Row2-->Wheel Wheel-->Right Right-->DampingRateTarget

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget
[get]  OK
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget 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.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget

Data Type & Unit
Path Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget is an Actuator.

The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right.DampingRateTarget is 7e7e4c2a52715e30bfe02597cbf679b7

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.