This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
AngularVelocity
|
|
Full qualified VSS Path: |
Vehicle.AngularVelocity |
Description: |
Spatial rotation. Axis definitions according to ISO 8855. |
Navigation
flowchart LR
Vehicle-->AngularVelocity
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.AngularVelocity
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.AngularVelocity
is 1eef530a43de56aab665d2766483cde2
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 - Pitch
|
|
Full qualified VSS Path: |
Vehicle.AngularVelocity.Pitch |
Description: |
Vehicle rotation rate along Y (lateral). |
Navigation
flowchart LR
Vehicle-->AngularVelocity
AngularVelocity-->Pitch
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.AngularVelocity.Pitch
[get] OK
Vehicle.AngularVelocity.Pitch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.AngularVelocity.Pitch 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 float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.AngularVelocity.Pitch
is a Sensor.
The vehicle signal Vehicle.AngularVelocity.Pitch
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.AngularVelocity.Pitch
is 42236f4a01f45313a97fdd9b6848ce4f
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 - Roll
|
|
Full qualified VSS Path: |
Vehicle.AngularVelocity.Roll |
Description: |
Vehicle rotation rate along X (longitudinal). |
Navigation
flowchart LR
Vehicle-->AngularVelocity
AngularVelocity-->Roll
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.AngularVelocity.Roll
[get] OK
Vehicle.AngularVelocity.Roll: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.AngularVelocity.Roll 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 float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.AngularVelocity.Roll
is a Sensor.
The vehicle signal Vehicle.AngularVelocity.Roll
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.AngularVelocity.Roll
is 221e6b93881e5771bcbd03e0849e0075
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3 - Yaw
|
|
Full qualified VSS Path: |
Vehicle.AngularVelocity.Yaw |
Description: |
Vehicle rotation rate along Z (vertical). |
Navigation
flowchart LR
Vehicle-->AngularVelocity
AngularVelocity-->Yaw
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.AngularVelocity.Yaw
[get] OK
Vehicle.AngularVelocity.Yaw: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.AngularVelocity.Yaw 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 float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.AngularVelocity.Yaw
is a Sensor.
The vehicle signal Vehicle.AngularVelocity.Yaw
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.AngularVelocity.Yaw
is 4114c41552565c1f9035670cabe2a611
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.