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.Row2.Pos1.Switch |
Description: |
Seat switch signals |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch
is 1c4b708222de55aabddb3697308253ee
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 - Backrest
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest |
Description: |
Describes switches related to the backrest of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest
is 4cc0b73f30e65456a6268f52ad7fee70
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 - IsReclineBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged |
Description: |
Backrest recline backward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->IsReclineBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged
is 0b5415702e0b5461afacea857c05a6fe
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 - IsReclineForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged |
Description: |
Backrest recline forward switch engaged (SingleSeat.Backrest.Recline). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->IsReclineForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged
is 1e1bbfda10e25d228e01a632277d57c3
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.3 - Lumbar
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar |
Description: |
Switches for SingleSeat.Backrest.Lumbar. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar
is 4dc489e632e15d13afd6601188ed08b3
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.3.1 - IsDownEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged |
Description: |
Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsDownEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged
is 09337347e2f557fe8649342548c7fe3c
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.3.2 - IsLessSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged |
Description: |
Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsLessSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged
is 12fe41df5ab8545e8a3e7b2411585243
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.3.3 - IsMoreSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged |
Description: |
Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsMoreSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged
is 73e6514d130e5bfb85d4cfb7c45d8138
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.3.4 - IsUpEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged |
Description: |
Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->Lumbar
Lumbar-->IsUpEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged
is 47f8690805455b8c927f2834942b2ded
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.4 - SideBolster
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster |
Description: |
Switches for SingleSeat.Backrest.SideBolster. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->SideBolster
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster
is 184e9cc9d42e5ec993593da10b1b8299
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.4.1 - IsLessSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged |
Description: |
Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->SideBolster
SideBolster-->IsLessSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged
is f5e3fae9d90954ad9a240b72fa0a5cb4
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.4.2 - IsMoreSupportEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged |
Description: |
Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.Support). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Backrest
Backrest-->SideBolster
SideBolster-->IsMoreSupportEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged
is a7dc6c8941805c47b837334abfa7abee
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.Pos1.Switch.Headrest |
Description: |
Switches for SingleSeat.Headrest. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Headrest
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest
is f803a25975405ed38684b3f065535a4a
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 - IsBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged |
Description: |
Head rest backward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged
is 9ed038b597665225a0f2dfd262cf59b5
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 - IsDownEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged |
Description: |
Head rest down switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsDownEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged
is 4d3d29ccfcde55f9bdf40eeeb7ecf5dc
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 - IsForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged |
Description: |
Head rest forward switch engaged (SingleSeat.Headrest.Angle). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged
is ae9cdee6019a567ebac3e85a909fe7ca
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 - IsUpEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged |
Description: |
Head rest up switch engaged (SingleSeat.Headrest.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Headrest
Headrest-->IsUpEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged
is f929508b3527553a959952bcd227f70e
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 - IsDownEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged |
Description: |
Seat down switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsDownEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged
is fd41789d95035c2fa1e855d22eab80fa
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 - IsTiltBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged |
Description: |
Tilt backward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsTiltBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged
is 22726fefa40d5805b46b2c87e43782ed
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 - IsTiltForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged |
Description: |
Tilt forward switch engaged (SingleSeat.Tilt). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsTiltForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged
is f557b6a2712f5307b56577d93b9e746f
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 - IsUpEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged |
Description: |
Seat up switch engaged (SingleSeat.Height). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsUpEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged
is 3dacf86cf185576f8a3916a315c69b1d
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
Supported datatypes
The following is a list of VSS supported built-in datatypes:
Name |
Type |
Min |
Max |
uint8 |
unsigned 8-bit integer |
0 |
255 |
int8 |
signed 8-bit integer |
-128 |
127 |
uint16 |
unsigned 16-bit integer |
0 |
65535 |
int16 |
signed 16-bit integer |
-32768 |
32767 |
uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
boolean |
boolean value |
0/false |
1/true |
float |
floating point number |
-3.4e -38 |
3.4e 38 |
double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
7 - Massage
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage |
Description: |
Switches for SingleSeat.Massage. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Massage
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage
is 4857aac12637502da76202384a151715
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.
7.1 - IsDecreaseEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged |
Description: |
Decrease massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Massage
Massage-->IsDecreaseEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged
is d1f9e86a98be5f2ca81ac11d05356bb6
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.2 - IsIncreaseEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged |
Description: |
Increase massage level switch engaged (SingleSeat.Massage). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Massage
Massage-->IsIncreaseEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged
is 7b656c6aa62c5156aab2d437a03bd074
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 - Seating
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating |
Description: |
Describes switches related to the seating of the seat. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Seating
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating
is 1a3e7380e61852c98eda0f38e9f807aa
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.
8.1 - IsBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged |
Description: |
Is switch to decrease seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Seating
Seating-->IsBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged
is c02ddbb0e2c1536081dae3cb23baf4b1
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.2 - IsForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged |
Description: |
Is switch to increase seating length engaged (SingleSeat.Seating.Length). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->Seating
Seating-->IsForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged
is f0ef5926752f573ea02dacb2a242c8a1
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 - IsBackwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged |
Description: |
Seat backward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsBackwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged
is 57d1ff9eaf4e5a7cbe683c13eed6e691
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 - IsCoolerEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged |
Description: |
Cooler switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsCoolerEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged
is ac1a8efdbafb561bb11af807d48e8378
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 - IsForwardEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged |
Description: |
Seat forward switch engaged (SingleSeat.Position). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsForwardEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged
is 33ed964275af591d85773bc23d70bd68
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 - IsWarmerEngaged
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged |
Description: |
Warmer switch for Seat heater (SingleSeat.Heating). |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row2
Row2-->Pos1
Pos1-->Switch
Switch-->IsWarmerEngaged
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged
[get] OK
Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean
datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged
is an Actuator.
The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged
is 97a36b155294512f8c409a9bc82635bc
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.