| Full qualified VSS Path: | Vehicle.Body.Mirrors.PassengerSide.Yaw |
| Description: | Relative mirror yaw angle, measured from the vehicle sprung mass X-axis as defined by ISO 23150:2023 to the mirror X-axis, around the vehicle Z-axis (right-hand rule). 0 = Mirror in default position. Exact position (yaw relative to vehicle X-axis) is vehicle dependent. 100 = Maximum yaw. Mirror rotated clockwise as much as possible around Z-axis. -100 = Minimum yaw. Mirror rotated counter-clockwise as much as possible around Z-axis. |
| Comment: | A positive yaw indicates that the mirror has been adjusted to get a better view on objects on the right side of the vehicle. |
Navigation
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Mirrors.PassengerSide.Yaw
[get] OK
Vehicle.Body.Mirrors.PassengerSide.Yaw: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Mirrors.PassengerSide.Yaw 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
| Vehicle Model | Direct link to Vehicle Signal |
|---|---|
| ACME Car (EV) v0.1 | Vehicle.Body.Mirrors.PassengerSide.Yaw |
Data Type & Unit
| Path | Vehicle.Body.Mirrors.PassengerSide.Yaw |
VSS: Addressing nodes |
| Data type | int8 |
VSS: Datatypes |
| Unit | percent |
VSS: Units |
| Label | percent | |
| Description | Relation measured in percent | VSS: Sensors & Actuators |
| Domain | relation | |
| Minimum value | -100 |
VSS: Sensors & Actuators |
| Maximum value | 100 |
VSS: Sensors & Actuators |
Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
Signal Information
The vehicle signal Vehicle.Body.Mirrors.PassengerSide.Yaw is an Actuator.
The vehicle signal Vehicle.Body.Mirrors.PassengerSide.Yaw 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:
| Enhancement request | Create COVESA GitHub Issue |
| Join COVESA | www.covesa.global |
| Discuss VSS on Slack | w3cauto.slack.com |
| VSS Data Experts on Google Groups | covesa.global data-expert-group |
About VSS
The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name | Type | Min | Max |
|---|---|---|---|
| uint8 | unsigned 8-bit integer | 0 | 255 |
| int8 | signed 8-bit integer | -128 | 127 |
| uint16 | unsigned 16-bit integer | 0 | 65535 |
| int16 | signed 16-bit integer | -32768 | 32767 |
| uint32 | unsigned 32-bit integer | 0 | 4294967295 |
| int32 | signed 32-bit integer | -2147483648 | 2147483647 |
| uint64 | unsigned 64-bit integer | 0 | 2^64 - 1 |
| int64 | signed 64-bit integer | -2^63 | 2^63 - 1 |
| boolean | boolean value | 0/false | 1/true |
| float | floating point number | -3.4e -38 | 3.4e 38 |
| double | double precision floating point number | -1.7e -300 | 1.7e 300 |
| string | character string | n/a | n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.