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

Return to the regular view of this page.

SteeringWheel
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel
Description: MotionManagement related to steering wheel.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel

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.Steering.SteeringWheel

Signal Information

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel is a Branch.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel is 34f152e517e8594c9180d52777b83782

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 - Angle
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.Angle
Description: Represents the current input angle of the steering system, typically corresponds to angle applied by driver on the steering-wheel. Positive for angle in counterclockwise direction (based on ISO8855).
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->Angle

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.MotionManagement.Steering.SteeringWheel.Angle

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.Angle VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

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.Steering.SteeringWheel.Angle is a Sensor.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.Angle is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.Angle is 98030b8cca965107bcebf4266ef797fa

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 - AngleTarget
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.AngleTarget
Description: Steering-wheel angle request to the steering actuator (external set-point for steer-by-wire). Positive sign for angle in counterclockwise direction (based on ISO8855).
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->AngleTarget

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.AngleTarget VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

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.Steering.SteeringWheel.AngleTarget is an Actuator.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.AngleTarget is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.AngleTarget is 0d50dfdd61185a1783634f525b41cc72

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 - AngleTargetMode
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.AngleTargetMode
Description: Mode used for controlling Steering-wheel angle interface. 0 indicates interface disabled. Other values activate vehicle specific modes.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->AngleTargetMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.AngleTargetMode VSS: Addressing nodes
Data type uint8 VSS: Datatypes

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.Steering.SteeringWheel.AngleTargetMode is an Actuator.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.AngleTargetMode is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.AngleTargetMode is 378f305cc6cd5b46b86047492a4a6182

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 - Torque
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.Torque
Description: Represents the current input torque for steering system, typically corresponds to torque applied by driver on the steering wheel. Positive for torque in counterclockwise direction (based on ISO8855).
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->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.Steering.SteeringWheel.Torque
[get]  OK
Vehicle.MotionManagement.Steering.SteeringWheel.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.SteeringWheel.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.Steering.SteeringWheel.Torque

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.Torque 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.Steering.SteeringWheel.Torque is a Sensor.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.Torque is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.Torque is 4f2cfb8e853456cbb15d7ac21200b8a4

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 - TorqueOffsetTarget
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTarget
Description: Steering-wheel torque offset request to the steering actuator, added to the actuator internal calculated target value. Positive sign for torque in counterclockwise direction (based on ISO8855).
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->TorqueOffsetTarget

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTarget 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.Steering.SteeringWheel.TorqueOffsetTarget is an Actuator.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTarget is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTarget is 914b81953ae85fd89099a68b467e2922

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 - TorqueOffsetTargetMode
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTargetMode
Description: Mode used for controlling steering-wheel torque offset interface. 0 indicates interface disabled. Other values activate vehicle specific modes.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->TorqueOffsetTargetMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTargetMode VSS: Addressing nodes
Data type uint8 VSS: Datatypes

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.Steering.SteeringWheel.TorqueOffsetTargetMode is an Actuator.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTargetMode is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.TorqueOffsetTargetMode is 3694edd53aaf59cfa93f9ea15e2a2630

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.

7 - TorqueTarget
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTarget
Description: Steering-wheel torque request to the steering actuator (external set-point for steer-by-wire). Positive sign for torque in counterclockwise direction (based on ISO8855).
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->TorqueTarget

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTarget 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.Steering.SteeringWheel.TorqueTarget is an Actuator.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTarget is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTarget is 79f3e4fb26f25971b0d07ef40bf3db15

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.

8 - TorqueTargetMode
Full qualified VSS Path: Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTargetMode
Description: Mode used for controlling Steering-wheel torque interface. 0 indicates interface disabled. Other values activate vehicle specific modes.
flowchart LR Vehicle-->MotionManagement MotionManagement-->Steering Steering-->SteeringWheel SteeringWheel-->TorqueTargetMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTargetMode VSS: Addressing nodes
Data type uint8 VSS: Datatypes

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.Steering.SteeringWheel.TorqueTargetMode is an Actuator.

The vehicle signal Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTargetMode is a Signal.

UUID

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

The UUID for Vehicle.MotionManagement.Steering.SteeringWheel.TorqueTargetMode is 2a092c151fe05626a30d79556f6c3593

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.