This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
PassengerSide
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide |
| Description: |
All seats. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide is 8cd32cb3e2d157b39af57d9cfe2e128c
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 - Airbag
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag |
| Description: |
Airbag signals. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Airbag
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag is d16d61dc474f514fb10d1c8ecbeb9179
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 - IsDeployed
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsDeployed |
| Description: |
Airbag deployment status. True = Airbag deployed. False = Airbag not deployed. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Airbag
Airbag-->IsDeployed
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.PassengerSide.Airbag.IsDeployed
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsDeployed false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsDeployed is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsDeployed is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsDeployed is a73fecde42375d07834a6670209228f4
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 - IsEnabled
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsEnabled |
| Description: |
Airbag enabled status. True = Airbag enabled. False = Airbag not enabled. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Airbag
Airbag-->IsEnabled
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.PassengerSide.Airbag.IsEnabled
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsEnabled false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsEnabled is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsEnabled is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Airbag.IsEnabled is 2ccd0ac017e95713b8243099ce831372
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 - Headrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest |
| Description: |
Headrest settings. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Headrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest is a5449c4df2955aac981992fcbb581b84
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 - Angle
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Angle |
| Description: |
Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Headrest
Headrest-->Angle
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.PassengerSide.Headrest.Angle
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Angle 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.Cabin.Seat.Row2.PassengerSide.Headrest.Angle is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Angle is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Angle is 13f6bb21aa64545c97257c2b614622cb
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 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Height |
| Description: |
Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Headrest
Headrest-->Height
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.PassengerSide.Headrest.Height
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Height 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.Cabin.Seat.Row2.PassengerSide.Headrest.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.Height is a82bd9a0a9745ef68dae31474a095294
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 - IsBackwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsBackwardSwitchEngaged |
| Description: |
Headrest backward switch engaged. |
| Comment: |
Affects the property (Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Headrest
Headrest-->IsBackwardSwitchEngaged
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.PassengerSide.Headrest.IsBackwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsBackwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsBackwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsBackwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsBackwardSwitchEngaged is 8d152489e3225782ad2660c4dafc08f5
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 - IsDownSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsDownSwitchEngaged |
| Description: |
Headrest down switch engaged. |
| Comment: |
Affects the property (Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Headrest
Headrest-->IsDownSwitchEngaged
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.PassengerSide.Headrest.IsDownSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsDownSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsDownSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsDownSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsDownSwitchEngaged is dc1e82797f5955da88c192980aee6793
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 - IsForwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsForwardSwitchEngaged |
| Description: |
Headrest forward switch engaged. |
| Comment: |
Affects the property (Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Headrest
Headrest-->IsForwardSwitchEngaged
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.PassengerSide.Headrest.IsForwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsForwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsForwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsForwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsForwardSwitchEngaged is fb20cfc5c5c85ae08725eb095c49db03
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 - IsUpSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsUpSwitchEngaged |
| Description: |
Headrest up switch engaged. |
| Comment: |
Affects the property (Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Headrest
Headrest-->IsUpSwitchEngaged
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.PassengerSide.Headrest.IsUpSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsUpSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsUpSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsUpSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Headrest.IsUpSwitchEngaged is d059ad5f4c8c51d4a8242cd45ffcb532
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 - IsBackwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsBackwardSwitchEngaged |
| Description: |
Seat backward switch engaged. |
| Comment: |
Affects the property (Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsBackwardSwitchEngaged
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.PassengerSide.IsBackwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsBackwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsBackwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsBackwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsBackwardSwitchEngaged is bb17b59a618f5ce89d04f2659b7a047c
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.
4 - IsCoolerSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsCoolerSwitchEngaged |
| Description: |
Cooler switch for Seat heater. |
| Comment: |
Affects the property (HeatingCooling). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsCoolerSwitchEngaged
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.PassengerSide.IsCoolerSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsCoolerSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsCoolerSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsCoolerSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsCoolerSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsCoolerSwitchEngaged is 33afd2a78b5854a499de6692944c1979
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.
5 - IsDecreaseMassageLevelSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsDecreaseMassageLevelSwitchEngaged |
| Description: |
Decrease massage level switch engaged. |
| Comment: |
Affects the property (Massage.Level). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsDecreaseMassageLevelSwitchEngaged
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.PassengerSide.IsDecreaseMassageLevelSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsDecreaseMassageLevelSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsDecreaseMassageLevelSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsDecreaseMassageLevelSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsDecreaseMassageLevelSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsDecreaseMassageLevelSwitchEngaged is df205d7064205871b217d26466cacb62
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.
6 - IsDownSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsDownSwitchEngaged |
| Description: |
Seat down switch engaged. |
| Comment: |
Affects the property (Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsDownSwitchEngaged
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.PassengerSide.IsDownSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsDownSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsDownSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsDownSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsDownSwitchEngaged is fd81aa4745765a9ba2e4620b050b5424
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.
7 - IsForwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsForwardSwitchEngaged |
| Description: |
Seat forward switch engaged. |
| Comment: |
Affects the property (Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsForwardSwitchEngaged
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.PassengerSide.IsForwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsForwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsForwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsForwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsForwardSwitchEngaged is 80724594d80e5dc1bf7379879803cd69
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.
8 - IsIncreaseMassageLevelSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsIncreaseMassageLevelSwitchEngaged |
| Description: |
Increase massage level switch engaged. |
| Comment: |
Affects the property (Massage.Level). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsIncreaseMassageLevelSwitchEngaged
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.PassengerSide.IsIncreaseMassageLevelSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsIncreaseMassageLevelSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsIncreaseMassageLevelSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsIncreaseMassageLevelSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsIncreaseMassageLevelSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsIncreaseMassageLevelSwitchEngaged is ed6181f134d2574ea4c77dbb7f8a3226
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.
9 - IsTiltBackwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltBackwardSwitchEngaged |
| Description: |
Tilt backward switch engaged. |
| Comment: |
Affects the property (Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsTiltBackwardSwitchEngaged
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.PassengerSide.IsTiltBackwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltBackwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltBackwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltBackwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltBackwardSwitchEngaged is c39848a520535ad08b528affec046627
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.
10 - IsTiltForwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltForwardSwitchEngaged |
| Description: |
Tilt forward switch engaged. |
| Comment: |
Affects the property (Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsTiltForwardSwitchEngaged
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.PassengerSide.IsTiltForwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltForwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltForwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltForwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsTiltForwardSwitchEngaged is f12d46c541045825ad4ca7568966534e
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.
11 - IsUpSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsUpSwitchEngaged |
| Description: |
Seat up switch engaged. |
| Comment: |
Affects the property (Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsUpSwitchEngaged
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.PassengerSide.IsUpSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsUpSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsUpSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsUpSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsUpSwitchEngaged is b4b078b170c0518c9cf2ba8afb12f00c
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.
12 - IsWarmerSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsWarmerSwitchEngaged |
| Description: |
Warmer switch for Seat heater. |
| Comment: |
Affects the property (HeatingCooling). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsWarmerSwitchEngaged
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.PassengerSide.IsWarmerSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsWarmerSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsWarmerSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsWarmerSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsWarmerSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsWarmerSwitchEngaged is ae0d1f8475cb57a280c3112b72829552
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.
13 - NeckScarf
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf |
| Description: |
NeckScarf settings. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->NeckScarf
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf is 3a9e263b4b7e533688cc551da039e277
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.
13.1 - FanSpeed
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.FanSpeed |
| Description: |
Speed of the fan. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->NeckScarf
NeckScarf-->FanSpeed
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.PassengerSide.NeckScarf.FanSpeed
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.FanSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.FanSpeed 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.Cabin.Seat.Row2.PassengerSide.NeckScarf.FanSpeed is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.FanSpeed is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.FanSpeed is 6cb029e9b591566e94590d61716b9184
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.
13.2 - HeatingCooling
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.HeatingCooling |
| Description: |
Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->NeckScarf
NeckScarf-->HeatingCooling
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.PassengerSide.NeckScarf.HeatingCooling
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.HeatingCooling 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.HeatingCooling is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.HeatingCooling is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.NeckScarf.HeatingCooling is fd8b35e563e452138fe59d199904a450
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.
14 - Seating
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating |
| Description: |
Describes signals related to the seat bottom of the seat. |
| Comment: |
Seating is here considered as the part of the seat that supports the thighs. Additional cushions (if any) for support of lower legs is not covered by this branch. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Seating
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Seating is ef3307b33fae500b837da872d2fad454
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.
14.1 - HeatingCooling
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.HeatingCooling |
| Description: |
Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Seating
Seating-->HeatingCooling
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.PassengerSide.Seating.HeatingCooling
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.HeatingCooling 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.HeatingCooling is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.HeatingCooling is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.HeatingCooling is e4ec631bce1c519e91ad8ad932d93096
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.
14.2 - IsBackwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsBackwardSwitchEngaged |
| Description: |
Is switch to decrease seating length engaged. |
| Comment: |
Affects the property (Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Seating
Seating-->IsBackwardSwitchEngaged
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.PassengerSide.Seating.IsBackwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsBackwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsBackwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsBackwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsBackwardSwitchEngaged is 00432ea53aea51d9987b752cbb807028
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.
14.3 - IsForwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsForwardSwitchEngaged |
| Description: |
Is switch to increase seating length engaged. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Seating
Seating-->IsForwardSwitchEngaged
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.PassengerSide.Seating.IsForwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsForwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsForwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsForwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.IsForwardSwitchEngaged is d616b77c1ba656e2b05d3d7129be6d88
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.
14.4 - Length
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.Length |
| Description: |
Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Seating
Seating-->Length
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.PassengerSide.Seating.Length
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.Length 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 uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.Length is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.Length is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.Length is 68e28b1aadcf5c3db177943af27a9098
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.
14.5 - SideBolsterSupportLeft
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportLeft |
| Description: |
Seat bottom side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Seating
Seating-->SideBolsterSupportLeft
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.PassengerSide.Seating.SideBolsterSupportLeft
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportLeft 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.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportLeft is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportLeft is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportLeft is 74c260fbdc725088b8b9451f7dbf5c4b
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.
14.6 - SideBolsterSupportRight
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportRight |
| Description: |
Seat bottom side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Seating
Seating-->SideBolsterSupportRight
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.PassengerSide.Seating.SideBolsterSupportRight
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportRight 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.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportRight is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportRight is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Seating.SideBolsterSupportRight is 09007fd813ed5d239f68368c35267de6
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.
15 - Backrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest |
| Description: |
Describes signals related to the backrest of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest is ea5285b1124c527681e1a45c51429bdb
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.
15.1 - BottomLumbarSupport
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.BottomLumbarSupport |
| Description: |
Bottom lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->BottomLumbarSupport
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.PassengerSide.Backrest.BottomLumbarSupport
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.BottomLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.BottomLumbarSupport 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.Cabin.Seat.Row2.PassengerSide.Backrest.BottomLumbarSupport is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.BottomLumbarSupport is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.BottomLumbarSupport is fd220e8064be51c1a911a0427eaeeb53
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.
15.2 - IsLessLumbarSupportSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessLumbarSupportSwitchEngaged |
| Description: |
Is switch for less lumbar support engaged. |
| Comment: |
Affects the property (Backrest.LumbarSupport). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsLessLumbarSupportSwitchEngaged
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.PassengerSide.Backrest.IsLessLumbarSupportSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessLumbarSupportSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessLumbarSupportSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessLumbarSupportSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessLumbarSupportSwitchEngaged is b58cbfa8383f5c838807c5ee77cbefa1
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.
15.3 - IsLessSideBolsterSupportSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessSideBolsterSupportSwitchEngaged |
| Description: |
Is switch for less side bolster support engaged. |
| Comment: |
Affects the property (Backrest.SideBolsterSupport). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsLessSideBolsterSupportSwitchEngaged
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.PassengerSide.Backrest.IsLessSideBolsterSupportSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessSideBolsterSupportSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessSideBolsterSupportSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessSideBolsterSupportSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLessSideBolsterSupportSwitchEngaged is b817fee4bc0e58ec85f0a38a98472077
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.
15.4 - IsLumbarDownSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarDownSwitchEngaged |
| Description: |
Lumbar down switch engaged. |
| Comment: |
Affects the property (Backrest.LumbarSupport). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsLumbarDownSwitchEngaged
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.PassengerSide.Backrest.IsLumbarDownSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarDownSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarDownSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarDownSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarDownSwitchEngaged is ef58a31a41f95a77b7bc29f2a36ba157
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.
15.5 - IsLumbarUpSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarUpSwitchEngaged |
| Description: |
Lumbar up switch engaged. |
| Comment: |
Affects the property (Backrest.LumbarSupport). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsLumbarUpSwitchEngaged
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.PassengerSide.Backrest.IsLumbarUpSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarUpSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarUpSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarUpSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsLumbarUpSwitchEngaged is 2d2f3ae194275e4a956206c610d36505
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.
15.6 - IsMoreLumbarSupportSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreLumbarSupportSwitchEngaged |
| Description: |
Is switch for more lumbar support engaged. |
| Comment: |
Affects the property (Backrest.LumbarSupport). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsMoreLumbarSupportSwitchEngaged
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.PassengerSide.Backrest.IsMoreLumbarSupportSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreLumbarSupportSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreLumbarSupportSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreLumbarSupportSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreLumbarSupportSwitchEngaged is 760e76cc837d5d2892832c73a4ffc150
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.
15.7 - IsMoreSideBolsterSupportSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreSideBolsterSupportSwitchEngaged |
| Description: |
Is switch for more side bolster support engaged. |
| Comment: |
Affects the property (Backrest.SideBolsterSupport). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsMoreSideBolsterSupportSwitchEngaged
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.PassengerSide.Backrest.IsMoreSideBolsterSupportSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreSideBolsterSupportSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreSideBolsterSupportSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreSideBolsterSupportSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsMoreSideBolsterSupportSwitchEngaged is ef4ef41cbc805e4eae050c813dba0b99
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.
15.8 - IsReclineBackwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineBackwardSwitchEngaged |
| Description: |
Backrest recline backward switch engaged. |
| Comment: |
Affects the property (Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsReclineBackwardSwitchEngaged
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.PassengerSide.Backrest.IsReclineBackwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineBackwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineBackwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineBackwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineBackwardSwitchEngaged is eb51abe7bfb352ae8d726332225d4152
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.
15.9 - IsReclineForwardSwitchEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineForwardSwitchEngaged |
| Description: |
Backrest recline forward switch engaged. |
| Comment: |
Affects the property (Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->IsReclineForwardSwitchEngaged
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.PassengerSide.Backrest.IsReclineForwardSwitchEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineForwardSwitchEngaged false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineForwardSwitchEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineForwardSwitchEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.IsReclineForwardSwitchEngaged is d9c0b3c565b45f47a99b5668c2eb5541
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.
15.10 - LumbarHeight
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarHeight |
| Description: |
Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->LumbarHeight
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.PassengerSide.Backrest.LumbarHeight
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarHeight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarHeight 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.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarHeight is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarHeight is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarHeight is 90defb00efff591ba27bca2ba83e7db0
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.
15.11 - SideBolsterSupport
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupport |
| Description: |
Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->SideBolsterSupport
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.PassengerSide.Backrest.SideBolsterSupport
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupport 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.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupport is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupport is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupport is f434679fb71056ed8b7ddbc7594836f2
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.
15.12 - SideBolsterSupportLeft
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportLeft |
| Description: |
Side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->SideBolsterSupportLeft
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.PassengerSide.Backrest.SideBolsterSupportLeft
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportLeft 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.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportLeft is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportLeft is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportLeft is 35d4640e36b15880a058aafd68f2257a
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.
15.13 - SideBolsterSupportRight
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportRight |
| Description: |
Side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->SideBolsterSupportRight
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.PassengerSide.Backrest.SideBolsterSupportRight
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportRight 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.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportRight is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportRight is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.SideBolsterSupportRight is 7dcbf31cd9225f72b042e27bb77760e5
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.
15.14 - UpperShoulderSupport
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.UpperShoulderSupport |
| Description: |
Upper shoulder support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->UpperShoulderSupport
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.PassengerSide.Backrest.UpperShoulderSupport
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.UpperShoulderSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.UpperShoulderSupport 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.Cabin.Seat.Row2.PassengerSide.Backrest.UpperShoulderSupport is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.UpperShoulderSupport is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.UpperShoulderSupport is 1cd74ca5b6315d2c9fd85e029b491bb0
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.
15.15 - HeatingCooling
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.HeatingCooling |
| Description: |
Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->HeatingCooling
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.PassengerSide.Backrest.HeatingCooling
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.HeatingCooling 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.HeatingCooling is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.HeatingCooling is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.HeatingCooling is 5b55adff9ba35886a1a3f0aa34f738a4
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.
15.16 - LumbarSupport
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarSupport |
| Description: |
Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position. |
| Comment: |
A vehicle should typically either use this generic lumbar signal or the more specified top/mid/bottom signals. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->LumbarSupport
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.PassengerSide.Backrest.LumbarSupport
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarSupport 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.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarSupport is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarSupport is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.LumbarSupport is 5a463467c7415fbbade8e36031a53b18
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.
15.17 - MidLumbarSupport
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.MidLumbarSupport |
| Description: |
Mid lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->MidLumbarSupport
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.PassengerSide.Backrest.MidLumbarSupport
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.MidLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.MidLumbarSupport 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.Cabin.Seat.Row2.PassengerSide.Backrest.MidLumbarSupport is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.MidLumbarSupport is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.MidLumbarSupport is 3eb1db7519565a1cbb0d7e97deb76e01
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.
15.18 - Recline
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.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
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->Recline
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.PassengerSide.Backrest.Recline
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.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.
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.Cabin.Seat.Row2.PassengerSide.Backrest.Recline is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.Recline is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.Recline is 6e3669fe31425539a49a2235c11bd5b5
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.
15.19 - TopLumbarSupport
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.TopLumbarSupport |
| Description: |
Top lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Backrest
Backrest-->TopLumbarSupport
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.PassengerSide.Backrest.TopLumbarSupport
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.TopLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.TopLumbarSupport 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.Cabin.Seat.Row2.PassengerSide.Backrest.TopLumbarSupport is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.TopLumbarSupport is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Backrest.TopLumbarSupport is a18ba5a740815e6b9038c7f5ad799d01
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.
16 - HeatingCooling
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.HeatingCooling |
| Description: |
Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->HeatingCooling
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.PassengerSide.HeatingCooling
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.HeatingCooling 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.HeatingCooling is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.HeatingCooling is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.HeatingCooling is 61dbad56f18e5ecba04d189ebd943770
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.
17 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Height |
| Description: |
Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Height
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.PassengerSide.Height
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Height 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 uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Height is b1ca33bf7f4455ada6be941b92b824da
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.
18 - IsBelted
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.IsBelted |
| Description: |
Is the belt engaged. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->IsBelted
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.PassengerSide.IsBelted
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.IsBelted: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.IsBelted false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsBelted is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.IsBelted is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.IsBelted is c7d63d6c97845df5b602791f700968f7
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.
19 - Massage
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage |
| Description: |
Massage related information for the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Massage
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Massage is bd9ec382d92e52ae826cb532ba13e11f
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.
19.1 - IsAvailable
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.IsAvailable |
| Description: |
True if the seat have the massage capability |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Massage
Massage-->IsAvailable
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.PassengerSide.Massage.IsAvailable
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.IsAvailable: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.IsAvailable false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.IsAvailable is an Attribute.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.IsAvailable is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.IsAvailable is 996676e876ac5a52bff7981ee10f1558
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.
19.2 - Level
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Level |
| Description: |
Seat massage level. 0 = off. 100 = max massage. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Massage
Massage-->Level
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.PassengerSide.Massage.Level
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Level: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Level 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.Cabin.Seat.Row2.PassengerSide.Massage.Level is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Level is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Level is 3c06f6301aa851cda0885c431fee8e5c
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.
19.3 - Status
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Status |
| Description: |
Massage status. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Massage
Massage-->Status
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.PassengerSide.Massage.Status
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Status: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Status Foo
[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 string datatype is a character string.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Status is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Status is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.Status is 411ba9ae5c4e5414ae1986a3de8db1d7
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.
19.4 - SupportedTypes
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.SupportedTypes |
| Description: |
Type of massage. |
| Comment: |
OEMs may define a list of identifiers for supported massage types using the allowed keyword |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Massage
Massage-->SupportedTypes
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.PassengerSide.Massage.SupportedTypes
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.SupportedTypes: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.SupportedTypes 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
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.SupportedTypes is an Attribute.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.SupportedTypes is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.SupportedTypes is 6a6d17b542275f0d9dd8ae64e048a7e1
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.
19.5 - TypeActive
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.TypeActive |
| Description: |
Type of massage active. |
| Comment: |
OEMs may define a list of identifiers for supported massage types using the allowed keyword |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Massage
Massage-->TypeActive
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.PassengerSide.Massage.TypeActive
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.TypeActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.TypeActive Foo
[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 string datatype is a character string.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.TypeActive is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.TypeActive is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Massage.TypeActive is a08292f549b85f16b3d82ecbc6ef20ef
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.
20 - OccupancyStatus
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.OccupancyStatus |
| Description: |
Occupancy status of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->OccupancyStatus
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.PassengerSide.OccupancyStatus
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.OccupancyStatus: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.OccupancyStatus Foo
[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 string datatype is a character string.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.OccupancyStatus is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.OccupancyStatus is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.OccupancyStatus is a86fc38b06f65ce28d43d952eb05f170
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.
21 - Position
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Position |
| Description: |
Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Position
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.PassengerSide.Position
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Position 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 uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Position is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Position is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Position is 07a8fe28cc1850dc96458e827a9ebeb5
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.
22 - SeatBeltHeight
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.SeatBeltHeight |
| Description: |
Seat belt position on vehicle z-axis. Position is relative within available movable range of the seat belt. 0 = Lowermost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->SeatBeltHeight
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.PassengerSide.SeatBeltHeight
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.SeatBeltHeight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.SeatBeltHeight 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 uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.SeatBeltHeight is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.SeatBeltHeight is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.SeatBeltHeight is 9648e0ea501b583a86d211d09a953b14
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.
23 - Tilt
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.PassengerSide.Tilt |
| Description: |
Tilting of seat (seating and backrest) relative to vehicle x-axis. 0 = seat bottom is flat, seat bottom and vehicle x-axis are parallel. Positive degrees = seat tilted backwards, seat x-axis tilted upward, seat z-axis is tilted backward. |
| Comment: |
In VSS it is assumed that tilting a seat affects both seating (seat bottom) and backrest, i.e. the angle between seating and backrest will not be affected when changing Tilt. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->PassengerSide
PassengerSide-->Tilt
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.PassengerSide.Tilt
[get] OK
Vehicle.Cabin.Seat.Row2.PassengerSide.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.PassengerSide.Tilt 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.Cabin.Seat.Row2.PassengerSide.Tilt is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.PassengerSide.Tilt is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.PassengerSide.Tilt is 646c179da57a59c39ca9777a4808980b
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.