This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.