This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Switch
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch |
Description: |
Seat switch signals |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch
is dd54a1a61c7c5d79a420edb7b1755aa1
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 - Massage
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage |
Description: |
Switches for SingleSeat.Massage. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Massage
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage
is 82f1b4ee3b9c58998115117f6e8c39a7
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 - IsDecreaseEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsDecreaseEngaged |
Description: |
Decrease massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Massage
Massage-->IsDecreaseEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsDecreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsDecreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsDecreaseEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsDecreaseEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsDecreaseEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsDecreaseEngaged
is b655bf7a99015d638a6d7177aa6d89e9
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.2 - IsIncreaseEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsIncreaseEngaged |
Description: |
Increase massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Massage
Massage-->IsIncreaseEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsIncreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsIncreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsIncreaseEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsIncreaseEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsIncreaseEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Massage.IsIncreaseEngaged
is 8d81938f575756199e1c604f6a51677e
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2 - Backrest
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest |
Description: |
Describes switches related to the backrest of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest
is 79b1c57ac9245a5ca426a8b5e21717a6
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 - IsReclineBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineBackwardEngaged |
Description: |
Backrest recline backward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->IsReclineBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineBackwardEngaged
is 524f91af31e150b8aca5de230369be7f
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 - IsReclineForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineForwardEngaged |
Description: |
Backrest recline forward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->IsReclineForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.IsReclineForwardEngaged
is e5bd5743807c5b899098d22e6cc3a4bc
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.3 - Lumbar
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar |
Description: |
Switches for SingleSeat.Backrest.Lumbar. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->Lumbar
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar
is b05d8f4aa67c5e28af3a6dc957786834
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
2.3.1 - IsDownEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsDownEngaged |
Description: |
Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsDownEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsDownEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsDownEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsDownEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsDownEngaged
is 3491b91384f95975851e64636514f52f
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.3.2 - IsLessSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged |
Description: |
Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsLessSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged
is af092a25f40a5003b7354f5f580b0e11
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.3.3 - IsMoreSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged |
Description: |
Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsMoreSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged
is 1ae05b08ed295d4f8305abc26088cca2
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.3.4 - IsUpEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsUpEngaged |
Description: |
Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsUpEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsUpEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsUpEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsUpEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.Lumbar.IsUpEngaged
is da6a3f596a5c5db2b5984356087278d4
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.4 - SideBolster
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster |
Description: |
Switches for SingleSeat.Backrest.SideBolster. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->SideBolster
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster
is 07ff192c99275f8e88451c79ceb7aa03
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.4.1 - IsLessSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged |
Description: |
Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->SideBolster
SideBolster-->IsLessSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged
is 5e6fa87ef4fd563d97299bc2d88300d1
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
2.4.2 - IsMoreSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged |
Description: |
Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Backrest
Backrest-->SideBolster
SideBolster-->IsMoreSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged
is 33b758ca51f15403a398ef3072dcaae2
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
3 - Headrest
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest |
Description: |
Switches for SingleSeat.Headrest. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Headrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest
is 250bfde61cbe52659913655dd521fa0f
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 - IsBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsBackwardEngaged |
Description: |
Head rest backward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Headrest
Headrest-->IsBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsBackwardEngaged
is 556de341eb5052489018ae6ff95310e2
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 - IsDownEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsDownEngaged |
Description: |
Head rest down switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Headrest
Headrest-->IsDownEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsDownEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsDownEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsDownEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsDownEngaged
is 2245feeb2eeb54e3b9303bc2dc232de6
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 - IsForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsForwardEngaged |
Description: |
Head rest forward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Headrest
Headrest-->IsForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsForwardEngaged
is 39e5e43777ab5af9ba972a6da265a4f1
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 - IsUpEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsUpEngaged |
Description: |
Head rest up switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Headrest
Headrest-->IsUpEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsUpEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsUpEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsUpEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Headrest.IsUpEngaged
is f182830bd5955b85b8e755895d578b03
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 - IsBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsBackwardEngaged |
Description: |
Seat backward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsBackwardEngaged
is 861eca7954cb554e9fb8a21568126e10
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 - IsCoolerEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsCoolerEngaged |
Description: |
Cooler switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsCoolerEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsCoolerEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsCoolerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsCoolerEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsCoolerEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsCoolerEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsCoolerEngaged
is d3e2606f6cdc57759850f19e1ce8c4f2
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 - IsDownEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsDownEngaged |
Description: |
Seat down switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsDownEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsDownEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsDownEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsDownEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsDownEngaged
is 7da73beabcbc5f338bc68e9b5e3daf06
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 - IsForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsForwardEngaged |
Description: |
Seat forward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsForwardEngaged
is 28ff94d05f795705928644e5a0101e8b
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 - IsTiltBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltBackwardEngaged |
Description: |
Tilt backward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsTiltBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltBackwardEngaged
is 0482452fd1a3501d96e06ee7c5dba6dd
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 - IsTiltForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltForwardEngaged |
Description: |
Tilt forward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsTiltForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsTiltForwardEngaged
is d0433b6d2d965fecb9384ac5205de397
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 - IsUpEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsUpEngaged |
Description: |
Seat up switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsUpEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsUpEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsUpEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsUpEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsUpEngaged
is 3906c493560e5c5686c69f0d2aa65e91
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 - IsWarmerEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsWarmerEngaged |
Description: |
Warmer switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->IsWarmerEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsWarmerEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsWarmerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsWarmerEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsWarmerEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsWarmerEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.IsWarmerEngaged
is 61eb1ede01d45ff2a6a4eec903741a08
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.Row1.Pos2.Switch.Seating |
Description: |
Describes switches related to the seating of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Seating
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating
is de12f83c5e425b6b9a9ef9e90b030fda
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 - IsBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsBackwardEngaged |
Description: |
Is switch to decrease seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Seating
Seating-->IsBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsBackwardEngaged
is e6d761d8e77651dab939076cdc8bd529
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.2 - IsForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsForwardEngaged |
Description: |
Is switch to increase seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos2
Pos2-->Switch
Switch-->Seating
Seating-->IsForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos2.Switch.Seating.IsForwardEngaged
is 4081bab44a1d5da1b70a5dc158f2ae39
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.