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