This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
MotionManagement
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement |
| Description: |
Motion Management Information. |
Navigation
flowchart LR
Vehicle-->MotionManagement
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement is 4e254d1020e35bf18f1ba6c252ee035b
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1 - Steering
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering |
| Description: |
MotionManagement related to steering. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Steering is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering is 6eb2d5f15cf951429d61e28eb6e4f3f0
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1.1 - Axle
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle |
| Description: |
MotionManagement related to a specific axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Steering.Axle is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle is 440ce4d999b25fb8b52e9906b46454fd
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1.1.1 - Row1
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1 |
| Description: |
MotionManagement related to front axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1 is 018d6d9d7d88521fa7e0be8a57449d16
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1.1.1.1 - PositionOffsetTargetMode
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.PositionOffsetTargetMode |
| Description: |
Mode used for controlling position offset interface of axle steering actuator. 0 indicates interface disabled. Other values activate vehicle specific modes. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->PositionOffsetTargetMode
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.Axle.Row1.PositionOffsetTargetMode
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.PositionOffsetTargetMode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.PositionOffsetTargetMode 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.PositionOffsetTargetMode is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.PositionOffsetTargetMode is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.PositionOffsetTargetMode is cda22482d4a95bf597fb53020b1b60eb
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.2 - PositionTargetMode
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.PositionTargetMode |
| Description: |
Mode used for controlling position interface of axle steering actuator. 0 indicates interface disabled. Other values activate vehicle specific modes. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->PositionTargetMode
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.Axle.Row1.PositionTargetMode
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.PositionTargetMode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.PositionTargetMode 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.PositionTargetMode is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.PositionTargetMode is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.PositionTargetMode is 7be07512f5ed5906ac11b61f6ac1d02d
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.3 - RackPosition
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.RackPosition |
| Description: |
Represents the current position of the steering rack on axle steering actuator. Positive values leads to a left turn of the vehicle (based on ISO8855). |
| Comment: |
Alternative signal to SteerAngle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->RackPosition
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.Axle.Row1.RackPosition
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.RackPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.RackPosition 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.RackPosition is a Sensor.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.RackPosition is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.RackPosition is 572b4e13a1995482abe792b451b2a068
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.4 - RackPositionOffsetTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionOffsetTarget |
| Description: |
Rack position offset request to the axle steering actuator (for steer-by-wire), added to the actuator internal calculated set-point. Positive values without internal calculated set point change lead to a left movement of the vehicle (based on ISO8855). |
| Comment: |
Alternative signal to SteerAngleOffsetTarget. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->RackPositionOffsetTarget
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.Axle.Row1.RackPositionOffsetTarget
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionOffsetTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionOffsetTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionOffsetTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionOffsetTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionOffsetTarget is 6d217376af7f5c36a1cb156f8ea94f68
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.5 - RackPositionTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionTarget |
| Description: |
Rack position request to the axle steering actuator (external set-point). Positive values lead to a left turn of the vehicle (based on ISO8855). |
| Comment: |
Alternative signal to SteerAngleTarget. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->RackPositionTarget
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.Axle.Row1.RackPositionTarget
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.RackPositionTarget is 169bc22c80b852968158ea679c03322b
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.6 - SteerAngle
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngle |
| Description: |
Represents the current actuated steering angle of the steered wheels. Signal orientation according ISO8855, single track model. |
| Comment: |
Alternative signal to RackPosition. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->SteerAngle
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.Axle.Row1.SteerAngle
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngle 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngle is a Sensor.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngle is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngle is cf011df2817655c5b0ed79d5f052b7bb
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.7 - SteerAngleOffsetTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleOffsetTarget |
| Description: |
Steer angle offset request to the axle steering actuator (for steer-by-wire), added to the actuator internal calculated set-point. Signal orientation according ISO8855, single track model. |
| Comment: |
Alternative signal to RackPositionOffsetTarget. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->SteerAngleOffsetTarget
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.Axle.Row1.SteerAngleOffsetTarget
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleOffsetTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleOffsetTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleOffsetTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleOffsetTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleOffsetTarget is bd3b1d6e203a5c5f93bddbafb056c02d
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.8 - SteerAngleTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleTarget |
| Description: |
Steer angle request to the axle steering actuator (external set-point). Signal orientation according ISO8855, single track model. |
| Comment: |
Alternative signal to RackPositionTarget. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row1
Row1-->SteerAngleTarget
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.Axle.Row1.SteerAngleTarget
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row1.SteerAngleTarget is 008601df214b536c953bc210181ad0eb
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.2 - Row2
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row2 |
| Description: |
MotionManagement related to rear axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row2
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row2 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row2 is 0382036275a0528f806d0c511be3cb3b
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1.1.2.1 - SteerAngle
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngle |
| Description: |
Represents the current actuated steering angle of the steered wheels on rear axle. Signal orientation according ISO8855, single track model. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row2
Row2-->SteerAngle
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.Axle.Row2.SteerAngle
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngle 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngle is a Sensor.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngle is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngle is b3edde725e3459daa290588b2bcaa866
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.2.2 - SteerAngleTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleTarget |
| Description: |
Steer angle request to the rear axle steering actuator (external set-point). Signal orientation according ISO8855, single track model. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row2
Row2-->SteerAngleTarget
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.Axle.Row2.SteerAngleTarget
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleTarget is 9d838b667a3553848bf599e8b399e615
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.2.3 - SteerAngleVelocityTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleVelocityTarget |
| Description: |
Requested velocity for steer angle change. Signal orientation according ISO8855. Optional signal to adapt rear wheel steering closed loop control gain. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Steering
Steering-->Axle
Axle-->Row2
Row2-->SteerAngleVelocityTarget
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.Axle.Row2.SteerAngleVelocityTarget
[get] OK
Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleVelocityTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleVelocityTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleVelocityTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleVelocityTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Steering.Axle.Row2.SteerAngleVelocityTarget is 3660e1e22c1d50899f762a574dc830f6
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.2 - SteeringWheel
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Steering.SteeringWheel |
| Description: |
MotionManagement related to steering wheel. |
Navigation
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.
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:
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.2.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). |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.
1.2.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). |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.
1.2.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. |
Navigation
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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.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:
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.
1.2.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). |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.
1.2.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). |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.
1.2.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. |
Navigation
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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.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:
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.
1.2.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). |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.
1.2.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. |
Navigation
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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.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:
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 - Suspension
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension |
| Description: |
MotionManagement related to suspension. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Suspension is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension is e25dbc8776465914b1e87a15ffdf6df0
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.1 - Axle
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle |
| Description: |
MotionManagement for suspension for a specific axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.Axle is a428e831a26b51258b55ab26032ac78f
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.1.1 - Row1
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1 |
| Description: |
MotionManagement for suspension for a specific axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.Axle.Row1 is 2928df3761745fc7bf63e24461c1e603
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.1.1.1 - RollTorque
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.RollTorque |
| Description: |
Actuated roll torque on this axle by anti-roll actuator. Signal orientation according to ISO8855. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.RollTorque
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.RollTorque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.RollTorque 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.RollTorque is a Sensor.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.RollTorque is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.Axle.Row1.RollTorque is 997343bcaf065d7993b01a80594c31b9
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2 - Wheel
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->Wheel
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel is 0833c19934cc56f3a187ca15826186b5
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.1.1.2.1 - Left
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Left
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left is e6ba3626aae5556e9de2f0b4ab11ed33
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.1.1.2.1.1 - DampingForce
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.DampingForce
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingForce: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingForce is a Sensor.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Left.DampingForce is 89cbca9bf9e355d495b885073978127e
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2.1.2 - DampingForceTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.DampingForceTarget
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingForceTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingForceTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Left.DampingForceTarget is dea80d4c5b1154bda0fce9d24952393a
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2.1.3 - DampingRate
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.DampingRate
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingRate: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingRate is a Sensor.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Left.DampingRate is db5a8f4f3653550191b45f4560d01eed
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2.1.4 - DampingRateTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.DampingRateTarget
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingRateTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Left.DampingRateTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Left.DampingRateTarget is 8049fd7d31d85c3e87d2d2068f7cdee0
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2.2 - Right
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right is 4a047e4600e15da8bde112a25007fc20
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.1.1.2.2.1 - DampingForce
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Right.DampingForce
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingForce: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingForce is a Sensor.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Right.DampingForce is 70ed7cb54214592da7bc4b1d2ae46a18
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2.2.2 - DampingForceTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Right.DampingForceTarget
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingForceTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingForceTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Right.DampingForceTarget is 0918d5b285b952e684867e77ad62b3a6
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2.2.3 - DampingRate
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Right.DampingRate
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingRate: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingRate is a Sensor.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Right.DampingRate is a4caed0988e158ea8964b16dbbe4e817
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.1.2.2.4 - DampingRateTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row1.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. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Right.DampingRateTarget
[get] OK
Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingRateTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.Axle.Row1.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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.Wheel.Right.DampingRateTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.Axle.Row1.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.Row1.Wheel.Right.DampingRateTarget is dce7290fa25852198fba9ae809ed77d6
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.1.2 - Row2
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row2 |
| Description: |
MotionManagement for suspension for a specific axle. |
Navigation
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.
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:
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.2.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.2 - Wheel
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
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.
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:
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.2.2.1 - Left
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Left |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
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.
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:
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.2.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.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:
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.2.2 - Right
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.Axle.Row2.Wheel.Right |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
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.
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:
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.2.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.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:
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.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. |
Navigation
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.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.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:
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 - DampingPrioTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.DampingPrioTarget |
| Description: |
Prioritization target for damping control 0% = damping control by damping actuator (e.g. base functions) 100% = damping control by VMM system (e.g. vehicle dynamics) |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->DampingPrioTarget
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.DampingPrioTarget
[get] OK
Vehicle.MotionManagement.Suspension.DampingPrioTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.DampingPrioTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.DampingPrioTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.DampingPrioTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.DampingPrioTarget is a59b894978a15b7a95397d2e5c2acd29
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.3 - RollPrioTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.RollPrioTarget |
| Description: |
Prioritization target for anti-roll control 0% = anti-roll control by anti-roll actuator (e.g. base function) 100% = anti-roll control by VMM system (e.g. vehicle dynamics) |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->RollPrioTarget
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.RollPrioTarget
[get] OK
Vehicle.MotionManagement.Suspension.RollPrioTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.RollPrioTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.RollPrioTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.RollPrioTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.RollPrioTarget is b2d96461e5c350c68ed555864c848d71
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.4 - RollTorqueDistributionFrontMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMaximum |
| Description: |
Maximum distribution range request of roll torque to front axle. 0% = Complete roll torque shall be shifted to rear axle 100% = Complete roll torque may be shifted to front axle |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->RollTorqueDistributionFrontMaximum
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.RollTorqueDistributionFrontMaximum
[get] OK
Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMaximum is 035d967a45f35d03b32c517e5b4c370b
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.5 - RollTorqueDistributionFrontMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMinimum |
| Description: |
Minimum distribution range request of roll torque to front axle. 0% = Complete roll torque may be shifted to rear axle 100% = Complete roll torque shall be shifted to front axle |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->RollTorqueDistributionFrontMinimum
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.RollTorqueDistributionFrontMinimum
[get] OK
Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.RollTorqueDistributionFrontMinimum is c174a64379ab57bcaf82b1c66650be8c
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.6 - RollTorqueTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Suspension.RollTorqueTarget |
| Description: |
Roll torque request on vehicle level. Signal orientation according to ISO8855. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Suspension
Suspension-->RollTorqueTarget
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.RollTorqueTarget
[get] OK
Vehicle.MotionManagement.Suspension.RollTorqueTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Suspension.RollTorqueTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Suspension.RollTorqueTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.Suspension.RollTorqueTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Suspension.RollTorqueTarget is e1aee15e51d35a6fb8969b6dc7cfd1fd
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3 - Brake
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake |
| Description: |
MotionManagement related to braking (both frictions brakes and contribution from electric axles). |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake is c589f6eeff005455b7012314913bdfd2
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1 - Axle
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle |
| Description: |
MotionManagement for brake actuation for a specific electric axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle is 3ef2bcb3d76b571687e8c913097b4614
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.1 - Row2
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2 |
| Description: |
MotionManagement for brake actuation for a specific electric axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2 is b38be1e7c1465622841b40c20a14312b
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.1.1 - TorqueDistributionFrictionRightMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMaximum |
| Description: |
Maximum distribution range of the friction brake request on the axle to the right wheel. 0% = Complete friction torque shall be shifted to the left wheel. 50% = At most 50% friction torque may be shifted to the right wheel. 100% = Complete friction torque may be shifted to the right wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->TorqueDistributionFrictionRightMaximum
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.TorqueDistributionFrictionRightMaximum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMaximum is 2b63a8062de556ef813699ee8eff17b1
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.2 - TorqueDistributionFrictionRightMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMinimum |
| Description: |
Minimum distribution range of the friction brake request on the axle to the right wheel. 0% = Complete friction torque may be shifted to the left wheel. 50% = At least 50% friction torque shall be shifted to the right wheel. 100% = Complete friction torque shall be shifted to the right wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->TorqueDistributionFrictionRightMinimum
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.TorqueDistributionFrictionRightMinimum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.TorqueDistributionFrictionRightMinimum is 0c78813468205bd19814d9d0f947b19e
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.3 - TorqueElectricMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueElectricMinimum |
| Description: |
Limit for regenerative brake torque at given axle. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->TorqueElectricMinimum
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.TorqueElectricMinimum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueElectricMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.TorqueElectricMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueElectricMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueElectricMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.TorqueElectricMinimum is fc4e035d73645b48818afe459c02111f
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.4 - TorqueFrictionDifferenceMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueFrictionDifferenceMaximum |
| Description: |
Maximum absolute wheel torque difference between left and right wheel for friction brake. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->TorqueFrictionDifferenceMaximum
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.TorqueFrictionDifferenceMaximum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.TorqueFrictionDifferenceMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.TorqueFrictionDifferenceMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueFrictionDifferenceMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.TorqueFrictionDifferenceMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.TorqueFrictionDifferenceMaximum is 7e6229a44c085f6295436634c9096a58
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5 - Wheel
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel is e495362e0f2d5e36884f9309fd8d24bd
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.1.5.1 - Left
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
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.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left is 9d3ba47771e75041b8dfb3b28057d77a
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.1.5.1.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. |
Navigation
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.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaLower is 9cdf38476ef65cfd801ca1b0a1dbea52
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.1.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. |
Navigation
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.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.OmegaUpper is 69f94ef7f6e557cc8ecdb92c1a1d4f86
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.1.3 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque |
| Description: |
Estimated friction brake torque. Brake Torque < 0Nm. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.Torque is e81d98f9e5825271805bcb5f25b72c03
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.1.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueArbitrated is 5550b34168a55793b5582d4ef76e599f
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.1.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMaximum is 9d0e855220115e23b4379b33de67a3da
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.1.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. |
Navigation
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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Left.TorqueFrictionMinimum is 4b6609b7ed8b5b08985bd56f31826526
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.2 - Right
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right is 20621c745e7b5139a14608e814e64a6f
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.1.5.2.1 - OmegaLower
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaLower |
| Description: |
Lower wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.OmegaLower
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaLower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaLower 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaLower is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaLower is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaLower is 584dda897880511db9bbed6cb8829857
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.2.2 - OmegaUpper
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaUpper |
| Description: |
Upper wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.OmegaUpper
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaUpper: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaUpper 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaUpper is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaUpper is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.OmegaUpper is 58c45ddb010f5d39abc832ce02fe1460
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.2.3 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.Torque |
| Description: |
Estimated friction brake torque. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->Torque
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.Torque
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.Torque 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.Torque is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.Torque is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.Torque is af057afeb33b5128a492d8712e3cc4c4
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.2.4 - TorqueArbitrated
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueArbitrated |
| Description: |
Brake system internally calculated friction brake torque target. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.TorqueArbitrated
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueArbitrated: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueArbitrated 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueArbitrated is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueArbitrated is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueArbitrated is 56018ac4d8f852599aed9ae9fb247266
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.2.5 - TorqueFrictionMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMaximum |
| Description: |
Maximum wheel torque request for friction brake. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.TorqueFrictionMaximum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMaximum is 8f4a00c3a7885497839531107eadf11d
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.1.5.2.6 - TorqueFrictionMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMinimum |
| Description: |
Minimum wheel torque request for friction brake. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row2
Row2-->Wheel
Wheel-->Right
Right-->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.Right.TorqueFrictionMinimum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row2.Wheel.Right.TorqueFrictionMinimum is 5c20f588cf695ce29692e050e0783896
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2 - Row1
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1 |
| Description: |
MotionManagement for brake actuation for a specific electric axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1 is 2a8510bfc2de5c14ae2f4797a9d3a4c1
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.2.1 - TorqueDistributionFrictionRightMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMaximum |
| Description: |
Maximum distribution range of the friction brake request on the axle to the right wheel. 0% = Complete friction torque shall be shifted to the left wheel. 50% = At most 50% friction torque may be shifted to the right wheel. 100% = Complete friction torque may be shifted to the right wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->TorqueDistributionFrictionRightMaximum
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.Row1.TorqueDistributionFrictionRightMaximum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMaximum is f81323a6dc01570a86e881fb4e5133a9
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.2 - TorqueDistributionFrictionRightMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMinimum |
| Description: |
Minimum distribution range of the friction brake request on the axle to the right wheel. 0% = Complete friction torque may be shifted to the left wheel. 50% = At least 50% friction torque shall be shifted to the right wheel. 100% = Complete friction torque shall be shifted to the right wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->TorqueDistributionFrictionRightMinimum
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.Row1.TorqueDistributionFrictionRightMinimum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.TorqueDistributionFrictionRightMinimum is a8592e71d2e1568bbd4d44171ed69dcc
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.3 - TorqueElectricMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueElectricMinimum |
| Description: |
Limit for regenerative brake torque at given axle. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->TorqueElectricMinimum
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.Row1.TorqueElectricMinimum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueElectricMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.TorqueElectricMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueElectricMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueElectricMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.TorqueElectricMinimum is 24a5a00e6dec5372ba7a39a9dacb7eaf
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.4 - TorqueFrictionDifferenceMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueFrictionDifferenceMaximum |
| Description: |
Maximum absolute wheel torque difference between left and right wheel for friction brake. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->TorqueFrictionDifferenceMaximum
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.Row1.TorqueFrictionDifferenceMaximum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.TorqueFrictionDifferenceMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.TorqueFrictionDifferenceMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueFrictionDifferenceMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.TorqueFrictionDifferenceMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.TorqueFrictionDifferenceMaximum is daa8ce945e7b5b98881ca1ae504ef0a9
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5 - Wheel
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel is 19054cb58875518d8a3aa1fa92468663
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.2.5.1 - Left
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Left
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left is 3c3dad483e73543b80b647db5ab3b952
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.2.5.1.1 - OmegaLower
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaLower |
| Description: |
Lower wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.OmegaLower
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaLower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.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.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaLower is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaLower is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaLower is fac6dea617d25770830d4aa82a049be4
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.1.2 - OmegaUpper
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaUpper |
| Description: |
Upper wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.OmegaUpper
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaUpper: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.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.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaUpper is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaUpper is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.OmegaUpper is 9ee49eee2ed052bc83471077c94b1034
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.1.3 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.Torque |
| Description: |
Estimated friction brake torque. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.Torque
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.Torque 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.Torque is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.Torque is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.Torque is 62bbfd22932b5740afeb5ff33c202e98
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.1.4 - TorqueArbitrated
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueArbitrated |
| Description: |
Brake system internally calculated friction brake torque target. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.TorqueArbitrated
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueArbitrated: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueArbitrated is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueArbitrated is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueArbitrated is 1f8186ad720c55b9a6e03de839f66b19
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.1.5 - TorqueFrictionMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMaximum |
| Description: |
Maximum wheel torque request for friction brake. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.TorqueFrictionMaximum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMaximum is c3807c24c46756a49c191b9ab5162ae1
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.1.6 - TorqueFrictionMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMinimum |
| Description: |
Minimum wheel torque request for friction brake. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->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.Row1.Wheel.Left.TorqueFrictionMinimum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.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.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Left.TorqueFrictionMinimum is c5469d25bb005cbebbfa1d1011f7c474
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.2 - Right
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right |
| Description: |
MotionManagement signals for a specific wheel. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right is dc1af9d2458a581583f5788674e5499c
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
3.1.2.5.2.1 - OmegaLower
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaLower |
| Description: |
Lower wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Right-->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.Row1.Wheel.Right.OmegaLower
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaLower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaLower 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaLower is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaLower is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaLower is ef5fe25bc7345c6fb8a9477c2dde9265
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.2.2 - OmegaUpper
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaUpper |
| Description: |
Upper wheel speed limit request controlled by friction brake. ISO 8855 wheel-spin velocity. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Right-->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.Row1.Wheel.Right.OmegaUpper
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaUpper: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaUpper 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaUpper is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaUpper is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.OmegaUpper is f09b6d3da3f55e358f934ac92fe6780f
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.2.3 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.Torque |
| Description: |
Estimated friction brake torque. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Right-->Torque
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.Torque
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.Torque 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.Torque is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.Torque is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.Torque is ccb181ab97d15095b0cbace5ebf7fcf7
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.2.4 - TorqueArbitrated
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueArbitrated |
| Description: |
Brake system internally calculated friction brake torque target. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Right-->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.Row1.Wheel.Right.TorqueArbitrated
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueArbitrated: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueArbitrated 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueArbitrated is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueArbitrated is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueArbitrated is 681874dcf6de5168944a723e5e95de82
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.2.5 - TorqueFrictionMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMaximum |
| Description: |
Maximum wheel torque request for friction brake. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Right-->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.Row1.Wheel.Right.TorqueFrictionMaximum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMaximum is 4179ab905ca65f8dbdd3836d255d1ef1
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.1.2.5.2.6 - TorqueFrictionMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMinimum |
| Description: |
Minimum wheel torque request for friction brake. Brake Torque < 0Nm. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->Axle
Axle-->Row1
Row1-->Wheel
Wheel-->Right
Right-->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.Row1.Wheel.Right.TorqueFrictionMinimum
[get] OK
Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.Axle.Row1.Wheel.Right.TorqueFrictionMinimum is ba390d0337cb542e95e2d4f0fc67de84
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.2 - VehicleForceDistributionFrontMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMaximum |
| Description: |
Maximum distribution range request of FxWhlSum to front axle. 0% = Complete longitudinal brake force shall be shifted to rear axle. 50% = At most 50% shall be shifted to front axle. 100% = Complete longitudinal brake force may be shifted to front axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->VehicleForceDistributionFrontMaximum
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.VehicleForceDistributionFrontMaximum
[get] OK
Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMaximum is b54a9477c025504ba8011129efcf8dc9
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.3 - VehicleForceDistributionFrontMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMinimum |
| Description: |
Minimum distribution range request of FxWhlSum to front axle. 0% = Complete longitudinal brake force may be shifted to rear axle. 50% = At least 50% shall be shifted to front axle. 100% = Complete longitudinal brake force shall be shifted to front axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->VehicleForceDistributionFrontMinimum
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.VehicleForceDistributionFrontMinimum
[get] OK
Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMinimum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.VehicleForceDistributionFrontMinimum is 7a0b14dcde5655a690f4365611bd6d82
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.4 - VehicleForceElectric
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.VehicleForceElectric |
| Description: |
Regenerative brake force request (FxWhlSum). Sum of all tyre longitudinal forces. Brake Force < 0N. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->VehicleForceElectric
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.VehicleForceElectric
[get] OK
Vehicle.MotionManagement.Brake.VehicleForceElectric: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.VehicleForceElectric 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceElectric is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceElectric is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.VehicleForceElectric is 654778859416526294b34298b5bc039c
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.5 - VehicleForceElectricMinimumArbitrated
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.VehicleForceElectricMinimumArbitrated |
| Description: |
Brake system internally calculated regenerative force limit at vehicle level for eAxle actuation. Brake Force < 0N. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->VehicleForceElectricMinimumArbitrated
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.VehicleForceElectricMinimumArbitrated
[get] OK
Vehicle.MotionManagement.Brake.VehicleForceElectricMinimumArbitrated: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.VehicleForceElectricMinimumArbitrated 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceElectricMinimumArbitrated is a Sensor.
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceElectricMinimumArbitrated is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.VehicleForceElectricMinimumArbitrated is 175ac6e8c3ec5f44b1a989bd9a677678
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3.6 - VehicleForceMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.Brake.VehicleForceMaximum |
| Description: |
Maximum longitudinal brake force request (FxWhlSum). Sum of all tyre longitudinal forces. Brake Force < 0N. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->Brake
Brake-->VehicleForceMaximum
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.VehicleForceMaximum
[get] OK
Vehicle.MotionManagement.Brake.VehicleForceMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.Brake.VehicleForceMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceMaximum is an Actuator.
The vehicle signal Vehicle.MotionManagement.Brake.VehicleForceMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.Brake.VehicleForceMaximum is 8b271fc2448151b2bdef1f5e08b1ef11
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4 - ElectricAxle
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle |
| Description: |
MotionManagement for a specific electric axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.ElectricAxle is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle is 8e68b27f815759fdaf80c6190ebf8847
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
4.1 - Row1
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1 |
| Description: |
MotionManagement for a specific electric axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1 is 5b7d73d2bc485eabbce3a93d9704a982
Children
This vehicle signal is a branch or structure and thus has sub-pages:
- Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed (Rotational speed for the specified axle, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit (Maximum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit (Minimum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget (Target axle rotational speed in rotation speed control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row1.Torque (Axle torque, positive sign for torque in forward direction, negative sign for torque in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum (Maximum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit (Maximum allowed eAxle torque in rotation speed control mode, positive sign for torque in forward direction, negative sign unused.)
- Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum (Minimum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit (Minimum allowed axle torque in rotation speed control mode, positive sign unused, negative sign for torque in backward direction (ISO8855).)
- Vehicle.MotionManagement.ElectricAxle.Row1.TorqueTarget (Target axle torque in torque control mode, positive sign for torque in forward direction, negative sign for torque in backward direction (ISO8855).)
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.1 - RotationalSpeed
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed |
| Description: |
Rotational speed for the specified axle, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->RotationalSpeed
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeed is d29a8a8b5abb54b1969134f18d772a3e
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.2 - RotationalSpeedMaximumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit |
| Description: |
Maximum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->RotationalSpeedMaximumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMaximumLimit is 0e0a05d4f4355e919d9a920b08b07943
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.3 - RotationalSpeedMinimumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit |
| Description: |
Minimum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->RotationalSpeedMinimumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedMinimumLimit is c24c82bd2ca05df4acdb26f149926d0f
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.4 - RotationalSpeedTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget |
| Description: |
Target axle rotational speed in rotation speed control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->RotationalSpeedTarget
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.RotationalSpeedTarget is 64815a9bf8ab546282fea1c8c46d7be8
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.5 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.Torque |
| Description: |
Axle torque, positive sign for torque in forward direction, negative sign for torque in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->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.ElectricAxle.Row1.Torque
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.Torque 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.Torque is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.Torque is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.Torque is d28dce62900b514ea13a28a6f376cdc1
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.6 - TorqueMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum |
| Description: |
Maximum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->TorqueMaximum
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximum is fa0e0639b7ca5521b992b712651c8108
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.7 - TorqueMaximumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit |
| Description: |
Maximum allowed eAxle torque in rotation speed control mode, positive sign for torque in forward direction, negative sign unused. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->TorqueMaximumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMaximumLimit is 9ce9a99c1bde5b29a31cdf883b4a9898
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.8 - TorqueMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum |
| Description: |
Minimum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->TorqueMinimum
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimum is 232fba4ad49b56a194478c7e8b8b73ef
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.9 - TorqueMinimumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit |
| Description: |
Minimum allowed axle torque in rotation speed control mode, positive sign unused, negative sign for torque in backward direction (ISO8855). |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->TorqueMinimumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.TorqueMinimumLimit is 62107f0a57ea512896c3f47ff0924f2a
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.1.10 - TorqueTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueTarget |
| Description: |
Target axle torque in torque control mode, positive sign for torque in forward direction, negative sign for torque in backward direction (ISO8855). |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row1
Row1-->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.ElectricAxle.Row1.TorqueTarget
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row1.TorqueTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row1.TorqueTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row1.TorqueTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row1.TorqueTarget is 9e04b5c33f875d51904fc57aa50f7a85
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2 - Row2
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2 |
| Description: |
MotionManagement for a specific electric axle. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2 is f48a236daac751d59e73ce0c0281583c
Children
This vehicle signal is a branch or structure and thus has sub-pages:
- Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed (Rotational speed for the specified axle, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit (Maximum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit (Minimum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget (Target axle rotational speed in rotation speed control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row2.Torque (Axle torque, positive sign for torque in forward direction, negative sign for torque in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum (Maximum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit (Maximum allowed eAxle torque in rotation speed control mode, positive sign for torque in forward direction, negative sign unused.)
- Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum (Minimum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction.)
- Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit (Minimum allowed axle torque in rotation speed control mode, positive sign unused, negative sign for torque in backward direction (ISO8855).)
- Vehicle.MotionManagement.ElectricAxle.Row2.TorqueTarget (Target axle torque in torque control mode, positive sign for torque in forward direction, negative sign for torque in backward direction (ISO8855).)
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.2.1 - RotationalSpeed
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed |
| Description: |
Rotational speed for the specified axle, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->RotationalSpeed
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeed is 8814e9975dc65f9882752f39cc86260b
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.2 - RotationalSpeedMaximumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit |
| Description: |
Maximum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->RotationalSpeedMaximumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMaximumLimit is 566f39f9850851c7894dc17790dffc68
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.3 - RotationalSpeedMinimumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit |
| Description: |
Minimum allowed axle rotational speed in torque control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->RotationalSpeedMinimumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedMinimumLimit is 75c5fa81e67655b0aeb8be4e13c5639d
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.4 - RotationalSpeedTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget |
| Description: |
Target axle rotational speed in rotation speed control mode, positive sign for rotation in forward direction, negative sign for rotation in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->RotationalSpeedTarget
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.RotationalSpeedTarget is b0745eb905235361a7df9672db7095ec
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.5 - Torque
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.Torque |
| Description: |
Axle torque, positive sign for torque in forward direction, negative sign for torque in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->Torque
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.Torque
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.Torque 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.Torque is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.Torque is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.Torque is 8fa19b6049a0525389e64ce8df833dde
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.6 - TorqueMaximum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum |
| Description: |
Maximum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->TorqueMaximum
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximum is 1c24767632975076833b636dd39812f3
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.7 - TorqueMaximumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit |
| Description: |
Maximum allowed eAxle torque in rotation speed control mode, positive sign for torque in forward direction, negative sign unused. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->TorqueMaximumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMaximumLimit is f8459db28a7356ee951ac28722ca9e59
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.8 - TorqueMinimum
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum |
| Description: |
Minimum momentarily available eAxle torque, positive sign for torque in forward direction, negative sign for torque in backward direction. |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->TorqueMinimum
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum is a Sensor.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimum is 651ac3a406555f4f86b630b33ae8c2fb
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.9 - TorqueMinimumLimit
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit |
| Description: |
Minimum allowed axle torque in rotation speed control mode, positive sign unused, negative sign for torque in backward direction (ISO8855). |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->TorqueMinimumLimit
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.TorqueMinimumLimit is 05bfad5f16f2516cb65dd901210d33fe
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
4.2.10 - TorqueTarget
|
|
| Full qualified VSS Path: |
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueTarget |
| Description: |
Target axle torque in torque control mode, positive sign for torque in forward direction, negative sign for torque in backward direction (ISO8855). |
Navigation
flowchart LR
Vehicle-->MotionManagement
MotionManagement-->ElectricAxle
ElectricAxle-->Row2
Row2-->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.ElectricAxle.Row2.TorqueTarget
[get] OK
Vehicle.MotionManagement.ElectricAxle.Row2.TorqueTarget: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.MotionManagement.ElectricAxle.Row2.TorqueTarget 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueTarget is an Actuator.
The vehicle signal Vehicle.MotionManagement.ElectricAxle.Row2.TorqueTarget is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.MotionManagement.ElectricAxle.Row2.TorqueTarget is 6cf572308b005ab9a3299ba721c796a7
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.