This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Pos3
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3 |
| Description: |
All seats. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3 is a40aa679981551e7a92b8438533911d4
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1 - Airbag
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Airbag |
| Description: |
Airbag signals. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Airbag
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Airbag is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Airbag is e1d14ad055955eac914a47ee180a6e78
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1.1 - IsDeployed
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed |
| Description: |
Airbag deployment status. True = Airbag deployed. False = Airbag not deployed. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Airbag
Airbag-->IsDeployed
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed is 6802243fcb3155b196cca3a825c12bcb
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2 - Headrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Headrest |
| Description: |
Headrest settings. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Headrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest is a14ecc5524645ca883e2838f666bce70
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.1 - Angle
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle |
| Description: |
Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Headrest
Headrest-->Angle
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle is bf6f63ab87e453af965c90f0495ea972
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.2 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height |
| Description: |
Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Headrest
Headrest-->Height
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height is 2ae8b66df4045f46a96acbcdd6d2d452
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 - Switch
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch |
| Description: |
Seat switch signals |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch is e0cfa7aceac75980b33075ceef5c9125
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 - Headrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest |
| Description: |
Switches for SingleSeat.Headrest. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Headrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest is dd4de742803250eaa1efeceaad116e1d
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.1 - IsBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged |
| Description: |
Head rest backward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Headrest.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is 04e14e79404b5ff7ac9067841f81bbc9
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.1.2 - IsDownEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged |
| Description: |
Head rest down switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Headrest.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Headrest.IsDownEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged is 61a58c7fa7ed5e08a17067193bb9c951
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.1.3 - IsForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged |
| Description: |
Head rest forward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Headrest.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Headrest.IsForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged is 3c94aab710ff5e8f8a48fdbf6dc7b989
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.1.4 - IsUpEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged |
| Description: |
Head rest up switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Headrest.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Headrest.IsUpEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged is e40c92c141f6562382f4f29d783cfa26
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 - Massage
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage |
| Description: |
Switches for SingleSeat.Massage. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Massage is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage is ac2bb22d6acf56988582353a1453cbe3
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.2.1 - IsDecreaseEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged |
| Description: |
Decrease massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Massage.IsDecreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is 7226bc97842452099d5484baad0af620
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.2 - IsIncreaseEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged |
| Description: |
Increase massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Massage.IsIncreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is fb062e9f85fd568cbd774b36fbf5113f
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.3 - Backrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest |
| Description: |
Describes switches related to the backrest of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest is 583a22d4a1365db9bf386a96bcafd292
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.3.1 - IsReclineBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged |
| Description: |
Backrest recline backward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is eed918c7f0b558a99bbe804582a31b64
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.3.2 - IsReclineForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged |
| Description: |
Backrest recline forward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is 0cc4f8336f0d585f93f4ab5c89e133d8
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.3.3 - Lumbar
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar |
| Description: |
Switches for SingleSeat.Backrest.Lumbar. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.Lumbar is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar is 1d631b9c90a25a858a6caabe8ead1826
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.3.3.1 - IsDownEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged |
| Description: |
Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is dcd08d675e7e5f4eafe85311a3e40f1e
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.3.3.2 - IsLessSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged |
| Description: |
Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is 866f9a7d358e5eb5985c9c675b4f7eb4
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.3.3.3 - IsMoreSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged |
| Description: |
Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is cf9c077f2f4d5573a6022f5f08e807d3
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.3.3.4 - IsUpEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged |
| Description: |
Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is f0fd5a54865452bcbf2939d8acd4273c
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.3.4 - SideBolster
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster |
| Description: |
Switches for SingleSeat.Backrest.SideBolster. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.SideBolster is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster is 79d8d65b4c1d54a4ab1306d56e839c49
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.3.4.1 - IsLessSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.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-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is e99b4f4b07af511b9d86454eec1c483c
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.3.4.2 - IsMoreSupportEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.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-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is 92341df5af725c8282f6f93644f1ec9f
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.4 - IsBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged |
| Description: |
Seat backward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged is 267429a5f95d5f47ac47ec301755df32
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.5 - IsCoolerEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged |
| Description: |
Cooler switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsCoolerEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsCoolerEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged is ffff3283b2cf5f7292e241ec2ee27e77
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.6 - IsDownEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged |
| Description: |
Seat down switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsDownEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged is 73d2e688696a507b826230d5b53c429f
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.7 - IsForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged |
| Description: |
Seat forward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged is 397a8afd0dd1533b8899248596ae7566
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.8 - IsTiltBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged |
| Description: |
Tilt backward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsTiltBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsTiltBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged is 4490bc9063715f238c00c1eea91fa964
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.9 - IsTiltForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged |
| Description: |
Tilt forward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsTiltForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsTiltForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged is 98d34a35ab82571e88e2d647b5a772f4
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.10 - IsUpEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged |
| Description: |
Seat up switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsUpEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged is 26752cad0db150a2aa6737b825e96256
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.11 - IsWarmerEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged |
| Description: |
Warmer switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.IsWarmerEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.IsWarmerEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged is 820cc2c323b45ef989d5bcb8aac9527e
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.12 - Seating
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating |
| Description: |
Describes switches related to the seating of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Seating is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating is 0ed3b90fe1b4581782fac8496bace4b8
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.12.1 - IsBackwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged |
| Description: |
Is switch to decrease seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Seating.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Seating.IsBackwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged is 2999a262b18e5476ab621e0cba4045e8
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.12.2 - IsForwardEngaged
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged |
| Description: |
Is switch to increase seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Switch.Seating.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Switch.Seating.IsForwardEngaged is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged is d32a5d6d85ff5b64b0157ae215cee44e
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 - Backrest
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Backrest |
| Description: |
Describes signals related to the backrest of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Backrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest is 561be9f8b4f9587bb0d139cc33071742
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.
4.1 - Lumbar
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.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-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Backrest.Lumbar is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar is 2410df6d719c56a58617644a8afc7240
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.
4.1.1 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.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-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Backrest.Lumbar.Height
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Backrest.Lumbar.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height is 38b30eb99fd35c5693c18361c566c6e9
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.1.2 - Support
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support |
| Description: |
Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Backrest.Lumbar.Support
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Backrest.Lumbar.Support is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support is b227f493bab0503589b3a54c30ade03c
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.2 - Recline
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline |
| Description: |
Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline. |
| Comment: |
Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Backrest
Backrest-->Recline
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline is 867a9d4d4e685407906d561946921c24
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.3 - SideBolster
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster |
| Description: |
Backrest side bolster (lumbar side support) settings. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Backrest.SideBolster is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster is d52ea54e1d725eb88fa1c061a07a3217
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.
4.3.1 - Support
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.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-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Backrest.SideBolster.Support
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Backrest.SideBolster.Support is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support is b4cef1fd83d653aca5c941865bbf96b7
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 - Heating
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Heating |
| Description: |
Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Heating
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Heating: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Heating is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Heating is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Heating is 2a175561eed05247b3048263c0122fa1
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 - Height
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Height |
| Description: |
Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Height
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Height
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Height 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Height is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Height is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Height is 077a21fca4d857dd81debfd81119bc73
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 - IsBelted
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.IsBelted |
| Description: |
Is the belt engaged. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->IsBelted
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.IsBelted
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.IsBelted: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.IsBelted false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.IsBelted is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.IsBelted is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.IsBelted is 815f9e1dc05b5078aaefc3868319b18b
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 - IsOccupied
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied |
| Description: |
Does the seat have a passenger in it. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.IsOccupied
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.IsOccupied is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied is 018a7ef68dd75f0ea391c7d8191acd9d
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 - Massage
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Massage |
| Description: |
Seat massage level. 0 = off. 100 = max massage. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Massage
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Massage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Massage is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Massage is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Massage is fffccf6ae6365b83ab093031f573e452
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 - Occupant
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Occupant |
| Description: |
Occupant data. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Occupant is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant is a8df9afde2335f8ab7cf4b185148f20e
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 - Identifier
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier |
| Description: |
Identifier attributes based on OAuth 2.0. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Occupant.Identifier is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier is 296e51d414a65cea96e1eea27dc3e1dd
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 - Issuer
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.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-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Occupant.Identifier.Issuer
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Occupant.Identifier.Issuer is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer is d96b225635b959a1aea0d6febb955ae8
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 - Subject
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject |
| Description: |
Subject for the authentication of the occupant. E.g. UserID 7331677. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->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.Row2.Pos3.Occupant.Identifier.Subject
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Row2.Pos3.Occupant.Identifier.Subject is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject is ea36896f5572580b9d8379a6256f61b5
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 - Position
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Position |
| Description: |
Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Position
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Position
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Position 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Position is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Position is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Position is 64eb763cc10358b49968797fbf50c092
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 - Seating
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Seating |
| Description: |
Describes signals related to the seat bottom of the seat. |
| Comment: |
Seating is here considered as the part of the seat that supports the thighs. Additional cushions (if any) for support of lower legs is not covered by this branch. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Seating
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Seating is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Seating is 1dcb55c75dd55fc0bf752fcf17ba79be
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.
12.1 - Length
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length |
| Description: |
Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Seating
Seating-->Length
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length is b188311a9fd95b9195b28ab7be00d68f
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 - Tilt
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos3.Tilt |
| Description: |
Tilting of seat (seating and backrest) relative to vehicle x-axis. 0 = seat bottom is flat, seat bottom and vehicle x-axis are parallel. Positive degrees = seat tilted backwards, seat x-axis tilted upward, seat z-axis is tilted backward. |
| Comment: |
In VSS it is assumed that tilting a seat affects both seating (seat bottom) and backrest, i.e. the angle between seating and backrest will not be affected when changing Tilt. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos3
Pos3-->Tilt
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Tilt
[get] OK
Vehicle.Cabin.Seat.Row2.Pos3.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Tilt 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Tilt is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Tilt is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Tilt is 5702e9961d4353eea849901a12886cf1
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.