This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Pos1
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1 |
| Description: |
All seats. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
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.Row1.Pos1 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1 is 9f570421f00a53f19f3741bd4e53303b
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.Row1.Pos1.Airbag |
| Description: |
Airbag signals. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Airbag is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Airbag is 51c12c552b745ead85e10392cd42791f
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.Row1.Pos1.Airbag.IsDeployed |
| Description: |
Airbag deployment status. True = Airbag deployed. False = Airbag not deployed. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Airbag.IsDeployed
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.Airbag.IsDeployed is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Airbag.IsDeployed is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Airbag.IsDeployed is 49cc2754a4385ef8bdd8ba4e81ae91f6
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 - Backrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Backrest |
| Description: |
Describes signals related to the backrest of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Backrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Backrest is b088e24466215c55b4e3b1ca84321fb9
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 - Lumbar
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar |
| Description: |
Adjustable lumbar support mechanisms in seats allow the user to change the seat back shape. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Backrest
Backrest-->Lumbar
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.Row1.Pos1.Backrest.Lumbar is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar is 58ce084f42255af281ba9827af2f69de
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.1 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Height |
| 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-->Row1
Row1-->Pos1
Pos1-->Backrest
Backrest-->Lumbar
Lumbar-->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.Row1.Pos1.Backrest.Lumbar.Height
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.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.Row1.Pos1.Backrest.Lumbar.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Height is 2093f65ca1085a8fab20837e00218461
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.1.2 - Support
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Support |
| Description: |
Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Backrest
Backrest-->Lumbar
Lumbar-->Support
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.Row1.Pos1.Backrest.Lumbar.Support
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Support 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.Row1.Pos1.Backrest.Lumbar.Support is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Support is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Lumbar.Support is c072a2f72b9554b2b45d81a352bc48ad
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 - Recline
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Recline |
| Description: |
Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline. |
| Comment: |
Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Backrest.Recline
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Recline 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
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.Row1.Pos1.Backrest.Recline is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Recline is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Backrest.Recline is b1d538f0eb1658639e64f024e1a42831
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 - SideBolster
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.SideBolster |
| Description: |
Backrest side bolster (lumbar side support) settings. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Backrest
Backrest-->SideBolster
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.Row1.Pos1.Backrest.SideBolster is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Backrest.SideBolster is dc92cbf22f7a54bca076ca9e64dde9e6
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.3.1 - Support
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.SideBolster.Support |
| Description: |
Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Backrest
Backrest-->SideBolster
SideBolster-->Support
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.Row1.Pos1.Backrest.SideBolster.Support
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Backrest.SideBolster.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Backrest.SideBolster.Support 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.Row1.Pos1.Backrest.SideBolster.Support is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Backrest.SideBolster.Support is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Backrest.SideBolster.Support is b9a59ddb83995d6381d38ebdd19fb4b9
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 - Headrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Headrest |
| Description: |
Headrest settings. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Headrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Headrest is 1b08f767214753648ce939fc23e7d530
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.
3.1 - Angle
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.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-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Headrest.Angle
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.Headrest.Angle is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Headrest.Angle is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Headrest.Angle is a438c09436955cdd859b08848642464e
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.2 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.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-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Headrest.Height
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.Headrest.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Headrest.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Headrest.Height is 04fbc8b58fb1507ca46e133f502212a8
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 - Heating
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Heating |
| Description: |
Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Heating
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.Row1.Pos1.Heating
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Heating: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Heating 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.Row1.Pos1.Heating is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Heating is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Heating is 6055f646e52c58959fe7c89e7e5e77df
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 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.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-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Height
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Height is a28e02777f0652c09282c639b2ab0a63
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 - IsBelted
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.IsBelted |
| Description: |
Is the belt engaged. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.IsBelted
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.IsBelted: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.IsBelted is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.IsBelted is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.IsBelted is 6bd16a2258d152919db77e9592ac837a
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 - Massage
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Massage |
| Description: |
Seat massage level. 0 = off. 100 = max massage. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Massage
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.Row1.Pos1.Massage
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Massage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Massage 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.Row1.Pos1.Massage is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Massage is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Massage is 0e668142a0855c31845050e3535ff1b3
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 - Position
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.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-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Position
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.Position is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Position is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Position is 78283eb5efee58f8bce8b5fa3760df54
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 - Seating
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.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-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Seating is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Seating is 0cfad6a333b651f4b3adc589a19bd8c2
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.
9.1 - Length
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.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-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Seating.Length
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.Seating.Length is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Seating.Length is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Seating.Length is 365425c0104757ae9d14c29c0cc61f78
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 - Switch
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch |
| Description: |
Seat switch signals |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
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.Row1.Pos1.Switch is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch is 6aeff0a2d48f5f28995f83cc5ada057d
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.
10.1 - Headrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest |
| Description: |
Switches for SingleSeat.Headrest. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->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.Row1.Pos1.Switch.Headrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest is e3d3659aed435d7c9bb58bad03590d3a
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.
10.1.1 - IsBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsBackwardEngaged |
| Description: |
Head rest backward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsBackwardEngaged
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.Row1.Pos1.Switch.Headrest.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsBackwardEngaged 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.Row1.Pos1.Switch.Headrest.IsBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsBackwardEngaged is 6ec4a46af3db57cc9d4c45923996923c
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.1.2 - IsDownEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsDownEngaged |
| Description: |
Head rest down switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsDownEngaged
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.Row1.Pos1.Switch.Headrest.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsDownEngaged 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.Row1.Pos1.Switch.Headrest.IsDownEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsDownEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsDownEngaged is 0d844cc3591453b48177a3ed45880e21
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.1.3 - IsForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsForwardEngaged |
| Description: |
Head rest forward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsForwardEngaged
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.Row1.Pos1.Switch.Headrest.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsForwardEngaged 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.Row1.Pos1.Switch.Headrest.IsForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsForwardEngaged is ca96e4f18b1753faab74e2d4c452d8df
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.1.4 - IsUpEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsUpEngaged |
| Description: |
Head rest up switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsUpEngaged
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.Row1.Pos1.Switch.Headrest.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsUpEngaged 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.Row1.Pos1.Switch.Headrest.IsUpEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsUpEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Headrest.IsUpEngaged is a603834c5eae54a78222d20515bd64df
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.2 - Massage
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage |
| Description: |
Switches for SingleSeat.Massage. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->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.Row1.Pos1.Switch.Massage is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage is 46a23e294875537d9ce222d748dd43ef
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.
10.2.1 - IsDecreaseEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsDecreaseEngaged |
| Description: |
Decrease massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Massage
Massage-->IsDecreaseEngaged
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.Row1.Pos1.Switch.Massage.IsDecreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsDecreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsDecreaseEngaged 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.Row1.Pos1.Switch.Massage.IsDecreaseEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsDecreaseEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsDecreaseEngaged is c6209e1fd41e5efbbe3b70910068533b
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.2.2 - IsIncreaseEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsIncreaseEngaged |
| Description: |
Increase massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Massage
Massage-->IsIncreaseEngaged
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.Row1.Pos1.Switch.Massage.IsIncreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsIncreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsIncreaseEngaged 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.Row1.Pos1.Switch.Massage.IsIncreaseEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsIncreaseEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Massage.IsIncreaseEngaged is 3500d7caafe458e19dac56fcff1ada61
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.3 - Seating
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating |
| Description: |
Describes switches related to the seating of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->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.Row1.Pos1.Switch.Seating is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating is 250088210ce059c7a262331242ef1408
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.
10.3.1 - IsBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsBackwardEngaged |
| Description: |
Is switch to decrease seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Seating
Seating-->IsBackwardEngaged
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.Row1.Pos1.Switch.Seating.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsBackwardEngaged 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.Row1.Pos1.Switch.Seating.IsBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsBackwardEngaged is b623d9fd81d658c7a4872550065a26f0
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.3.2 - IsForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsForwardEngaged |
| Description: |
Is switch to increase seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Seating
Seating-->IsForwardEngaged
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.Row1.Pos1.Switch.Seating.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsForwardEngaged 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.Row1.Pos1.Switch.Seating.IsForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Seating.IsForwardEngaged is 8ef4c44f8e42567f89c1ff54dd337e91
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.4 - Backrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest |
| Description: |
Describes switches related to the backrest of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->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.Row1.Pos1.Switch.Backrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest is b45a8ec5ab9251689f42d58d2d954c4e
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.
10.4.1 - SideBolster
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster |
| Description: |
Switches for SingleSeat.Backrest.SideBolster. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->SideBolster
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.Row1.Pos1.Switch.Backrest.SideBolster is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster is b49b7c0aa3135e209bb7888e143a6823
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.
10.4.1.1 - IsLessSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged |
| Description: |
Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->SideBolster
SideBolster-->IsLessSupportEngaged
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.Row1.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged 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.Row1.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged is cc76940524925bf3883918b8ee30d702
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.4.1.2 - IsMoreSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged |
| Description: |
Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->SideBolster
SideBolster-->IsMoreSupportEngaged
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.Row1.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged 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.Row1.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged is 515bd1ca932a5747b8f8523aa5e26466
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.4.2 - IsReclineBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineBackwardEngaged |
| Description: |
Backrest recline backward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->IsReclineBackwardEngaged
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.Row1.Pos1.Switch.Backrest.IsReclineBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineBackwardEngaged 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.Row1.Pos1.Switch.Backrest.IsReclineBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineBackwardEngaged is d21af34f33955fdf8a35b2909f1db5ae
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.4.3 - IsReclineForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineForwardEngaged |
| Description: |
Backrest recline forward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->IsReclineForwardEngaged
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.Row1.Pos1.Switch.Backrest.IsReclineForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineForwardEngaged 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.Row1.Pos1.Switch.Backrest.IsReclineForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.IsReclineForwardEngaged is fd1e56d716d2594b84e1c46b00ab47a5
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.4.4 - Lumbar
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar |
| Description: |
Switches for SingleSeat.Backrest.Lumbar. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
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.Row1.Pos1.Switch.Backrest.Lumbar is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar is 61bb2068d2355dad9ab5ef35709ce97a
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.
10.4.4.1 - IsDownEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsDownEngaged |
| Description: |
Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsDownEngaged
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.Row1.Pos1.Switch.Backrest.Lumbar.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsDownEngaged 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.Row1.Pos1.Switch.Backrest.Lumbar.IsDownEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsDownEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsDownEngaged is 01644b70287d5d1ba9a2f0c9770dadb8
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.4.4.2 - IsLessSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged |
| Description: |
Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsLessSupportEngaged
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.Row1.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged 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.Row1.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged is 757b1f58b4c558429b1d3f11f1a89e6f
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.4.4.3 - IsMoreSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged |
| Description: |
Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsMoreSupportEngaged
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.Row1.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged 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.Row1.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged is 3542721cf4cc5d8c86e9f8e4a3f36736
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.4.4.4 - IsUpEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsUpEngaged |
| Description: |
Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsUpEngaged
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.Row1.Pos1.Switch.Backrest.Lumbar.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsUpEngaged 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.Row1.Pos1.Switch.Backrest.Lumbar.IsUpEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsUpEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.Backrest.Lumbar.IsUpEngaged is ceceff9c973453d3bec25db6a56be86c
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.5 - IsBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsBackwardEngaged |
| Description: |
Seat backward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsBackwardEngaged
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.Row1.Pos1.Switch.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsBackwardEngaged 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.Row1.Pos1.Switch.IsBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsBackwardEngaged is 6a28f8e404f05a5b9339b3a40b8c0275
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.6 - IsCoolerEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsCoolerEngaged |
| Description: |
Cooler switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsCoolerEngaged
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.Row1.Pos1.Switch.IsCoolerEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsCoolerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsCoolerEngaged 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.Row1.Pos1.Switch.IsCoolerEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsCoolerEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsCoolerEngaged is abab10f2fc1753fc9276f4571d24b3ac
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.7 - IsDownEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsDownEngaged |
| Description: |
Seat down switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsDownEngaged
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.Row1.Pos1.Switch.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsDownEngaged 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.Row1.Pos1.Switch.IsDownEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsDownEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsDownEngaged is 2f758e9b09dc518693db398d31551eeb
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.8 - IsForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsForwardEngaged |
| Description: |
Seat forward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsForwardEngaged
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.Row1.Pos1.Switch.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsForwardEngaged 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.Row1.Pos1.Switch.IsForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsForwardEngaged is 849766f5f3885f9ba0c4cd817290b6a1
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.9 - IsTiltBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltBackwardEngaged |
| Description: |
Tilt backward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsTiltBackwardEngaged
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.Row1.Pos1.Switch.IsTiltBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltBackwardEngaged 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.Row1.Pos1.Switch.IsTiltBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltBackwardEngaged is 810dfaf2b68950e7b695efbfdd80f58a
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.10 - IsTiltForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltForwardEngaged |
| Description: |
Tilt forward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsTiltForwardEngaged
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.Row1.Pos1.Switch.IsTiltForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltForwardEngaged 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.Row1.Pos1.Switch.IsTiltForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsTiltForwardEngaged is ee55f014fe5c59c8a3808f64b0c51f9e
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.11 - IsUpEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsUpEngaged |
| Description: |
Seat up switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsUpEngaged
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.Row1.Pos1.Switch.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsUpEngaged 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.Row1.Pos1.Switch.IsUpEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsUpEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsUpEngaged is efb6bf4955d45232b8443c3428ec91c2
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.12 - IsWarmerEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsWarmerEngaged |
| Description: |
Warmer switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Switch
Switch-->IsWarmerEngaged
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.Row1.Pos1.Switch.IsWarmerEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsWarmerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsWarmerEngaged 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.Row1.Pos1.Switch.IsWarmerEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsWarmerEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Switch.IsWarmerEngaged is f60421d441985b5bb8f68fabae1e937a
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 - Tilt
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.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-->Row1
Row1-->Pos1
Pos1-->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.Row1.Pos1.Tilt
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.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.Row1.Pos1.Tilt is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Tilt is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Tilt is 20630968a82f53bc89aed9797e0b9c59
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 - IsOccupied
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.IsOccupied |
| Description: |
Does the seat have a passenger in it. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->IsOccupied
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.Row1.Pos1.IsOccupied
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.IsOccupied: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.IsOccupied 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.Row1.Pos1.IsOccupied is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.IsOccupied is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.IsOccupied is 4e85e2b0ec45582f90f2a17b3636ccc0
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 - Occupant
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Occupant |
| Description: |
Occupant data. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Occupant
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.Row1.Pos1.Occupant is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Occupant is e2303f18abb35b25932e97165858fa2e
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 - Identifier
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier |
| Description: |
Identifier attributes based on OAuth 2.0. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Occupant
Occupant-->Identifier
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.Row1.Pos1.Occupant.Identifier is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier is 473c3f152df7564589d0e09947ae428f
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.1 - Issuer
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Issuer |
| Description: |
Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Occupant
Occupant-->Identifier
Identifier-->Issuer
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.Row1.Pos1.Occupant.Identifier.Issuer
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Issuer 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.Row1.Pos1.Occupant.Identifier.Issuer is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Issuer is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Issuer is c631b08751b851ec9b12ade8332ba5e6
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.1.2 - Subject
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Subject |
| Description: |
Subject for the authentication of the occupant. E.g. UserID 7331677. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos1
Pos1-->Occupant
Occupant-->Identifier
Identifier-->Subject
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.Row1.Pos1.Occupant.Identifier.Subject
[get] OK
Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Subject 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.Row1.Pos1.Occupant.Identifier.Subject is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Subject is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos1.Occupant.Identifier.Subject is 8df99b3fedff5a219eacf254fb299ffb
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.