Full qualified VSS Path: | Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline |
Description: | Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline. |
Comment: | Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline. |
Navigation
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline 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.Cabin.Seat.Row2.Pos1.Backrest.Recline |
Data Type & Unit
Path | Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline |
VSS: Addressing nodes |
Data type | float |
VSS: Datatypes |
Unit | degrees |
VSS: Units |
Label | degree | |
Description | Angle measured in degrees | VSS: Sensors & Actuators |
Domain | angle |
Note: The float
datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
Signal Information
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline
is 4e793f7e663558b29130989024763680
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.