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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

1 - Airbag


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Airbag`
Description:	Airbag signals.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Airbag

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Airbag

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Airbag is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Airbag is 278a7e2126435a46a04dec92fd50ff8a

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed (Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.)
Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled (Airbag enabled status. True = Airbag enabled. False = Airbag not enabled.)

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

1.1 - IsDeployed


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed`
Description:	Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Airbag Airbag-->IsDeployed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsDeployed is 41909de6e59a56f8b4d3d3a4296c4cb5

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

1.2 - IsEnabled


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled`
Description:	Airbag enabled status. True = Airbag enabled. False = Airbag not enabled.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Airbag Airbag-->IsEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Airbag.IsEnabled is 39572d51907d5e20a5da5ae9a3e34c75

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2 - Backrest


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest`
Description:	Describes signals related to the backrest of the seat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest is 5bef9412aeaf582284dc8f9cca5a5129

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport (Bottom lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling (Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged (Is switch for less lumbar support engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged (Is switch for less side bolster support engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged (Lumbar down switch engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged (Lumbar up switch engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged (Is switch for more lumbar support engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged (Is switch for more side bolster support engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged (Backrest recline backward switch engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged (Backrest recline forward switch engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight (Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport (Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport (Mid lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline (Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport (Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft (Side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight (Side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport (Top lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport (Upper shoulder support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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 - BottomLumbarSupport


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport`
Description:	Bottom lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->BottomLumbarSupport

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.BottomLumbarSupport is 2569c1b4f05951d1aa02b1aafaff65f5

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.2 - HeatingCooling


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling`
Description:	Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->HeatingCooling

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.HeatingCooling is 834222dce4b55ec2aa6e6b8fce45d676

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.3 - IsLessLumbarSupportSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged`
Description:	Is switch for less lumbar support engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsLessLumbarSupportSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is bc2866d90ba956ad90ea887d19e4f0aa

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.4 - IsLessSideBolsterSupportSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged`
Description:	Is switch for less side bolster support engaged.
Comment:	Affects the property (Backrest.SideBolsterSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsLessSideBolsterSupportSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is 9db1057a940b500f9e68a011b40436c6

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.5 - IsLumbarDownSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged`
Description:	Lumbar down switch engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsLumbarDownSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarDownSwitchEngaged is c36c3851dcc8585aaf3b8dbaf37d2ca8

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.6 - IsLumbarUpSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged`
Description:	Lumbar up switch engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsLumbarUpSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsLumbarUpSwitchEngaged is a3505997293b5f2b8f53726a6fd9c675

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.7 - IsMoreLumbarSupportSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged`
Description:	Is switch for more lumbar support engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsMoreLumbarSupportSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is c1046eb53250552c8581751021249778

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.8 - IsMoreSideBolsterSupportSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged`
Description:	Is switch for more side bolster support engaged.
Comment:	Affects the property (Backrest.SideBolsterSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsMoreSideBolsterSupportSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is c6d864ea252758d998ae41fcce9deb33

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.9 - IsReclineBackwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged`
Description:	Backrest recline backward switch engaged.
Comment:	Affects the property (Backrest.Recline).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsReclineBackwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineBackwardSwitchEngaged is 48e5b3114caa5409bf317942db7c8f44

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.10 - IsReclineForwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged`
Description:	Backrest recline forward switch engaged.
Comment:	Affects the property (Backrest.Recline).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->IsReclineForwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.IsReclineForwardSwitchEngaged is 74d52dd9c29b5f3bacf3389469ca129d

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.11 - LumbarHeight


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight`
Description:	Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->LumbarHeight

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length
Minimum value	`0`	VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarHeight is ec90cf9ae518554598ff79ecd4c9f707

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.12 - LumbarSupport


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport`
Description:	Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.
Comment:	A vehicle should typically either use this generic lumbar signal or the more specified top/mid/bottom signals.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->LumbarSupport

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.LumbarSupport is a917925de6a85ae4a4e7c2c6b416133a

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.13 - MidLumbarSupport


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport`
Description:	Mid lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->MidLumbarSupport

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.MidLumbarSupport is 0966650e57145146a4a53bb3ea0572ff

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.14 - Recline


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline`
Description:	Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline.
Comment:	Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->Recline

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`degrees`	VSS: Units
Label	degree
Description	Angle measured in degrees	VSS: Sensors & Actuators
Domain	angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.Recline is f16a244ea7e2560db3991cb581149683

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.15 - SideBolsterSupport


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport`
Description:	Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->SideBolsterSupport

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupport is 3348c5238e6b5d29b8fe110328c3aeaf

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.16 - SideBolsterSupportLeft


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft`
Description:	Side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->SideBolsterSupportLeft

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportLeft is baba4c20195857f387318c3373ece9eb

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.17 - SideBolsterSupportRight


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight`
Description:	Side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->SideBolsterSupportRight

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.SideBolsterSupportRight is 95ef8d5847da5c8f973205a3519e8e65

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.18 - TopLumbarSupport


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport`
Description:	Top lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->TopLumbarSupport

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.TopLumbarSupport is c5ec8e0917ce5a169b6d0da92813739f

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

2.19 - UpperShoulderSupport


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport`
Description:	Upper shoulder support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Backrest Backrest-->UpperShoulderSupport

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Backrest.UpperShoulderSupport is 1f1248a8455d581da5eafd1828a2dfb4

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

3 - Headrest


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Headrest`
Description:	Headrest settings.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Headrest

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Headrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Headrest is a183fc37f47d55de8c5d2f2f27c779e0

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle (Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.)
Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height (Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.)
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged (Headrest backward switch engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged (Headrest down switch engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged (Headrest forward switch engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged (Headrest up switch engaged.)

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

3.1 - Angle


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle`
Description:	Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Headrest Headrest-->Angle

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`degrees`	VSS: Units
Label	degree
Description	Angle measured in degrees	VSS: Sensors & Actuators
Domain	angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Headrest.Angle is d5cc4a79f94f515aa8f5fa59184a5c35

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

3.2 - Height


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height`
Description:	Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Headrest Headrest-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length
Minimum value	`0`	VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Headrest.Height is 520ec12b50515918a664ae6f2ac6b702

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

3.3 - IsBackwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged`
Description:	Headrest backward switch engaged.
Comment:	Affects the property (Headrest.Angle).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Headrest Headrest-->IsBackwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsBackwardSwitchEngaged is 537274d7f4e85b40ace8bb029ba9ac11

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

3.4 - IsDownSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged`
Description:	Headrest down switch engaged.
Comment:	Affects the property (Headrest.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Headrest Headrest-->IsDownSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsDownSwitchEngaged is a1ab296c8f825ee587656bec4000b42e

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

3.5 - IsForwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged`
Description:	Headrest forward switch engaged.
Comment:	Affects the property (Headrest.Angle).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Headrest Headrest-->IsForwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsForwardSwitchEngaged is 96b134406da75809a1ff03b2f6a2d770

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

3.6 - IsUpSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged`
Description:	Headrest up switch engaged.
Comment:	Affects the property (Headrest.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Headrest Headrest-->IsUpSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Headrest.IsUpSwitchEngaged is d7fe0537c9e05368a15be3a05d88bc30

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

4 - HeatingCooling


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling`
Description:	Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->HeatingCooling

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.HeatingCooling is fa7d96abfc2351fbbac29047c3bb46cd

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

5 - Height


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Height`
Description:	Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Height
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Height 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Height

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Height`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length
Minimum value	`0`	VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Height is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Height is e9ada64ce4b454928de166adaa4344da

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

6 - IsBackwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged`
Description:	Seat backward switch engaged.
Comment:	Affects the property (Position).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsBackwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsBackwardSwitchEngaged is b031398855635b218b13c366eda3c66e

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

7 - IsBelted


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsBelted`
Description:	Is the belt engaged.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsBelted

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsBelted
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsBelted: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsBelted false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsBelted

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsBelted`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsBelted is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsBelted is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsBelted is 42a9c6f57d75550180138950e91e096e

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

8 - IsCoolerSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged`
Description:	Cooler switch for Seat heater.
Comment:	Affects the property (HeatingCooling).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsCoolerSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsCoolerSwitchEngaged is 118f57d795095ac0affddc28092fc2ee

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

9 - IsDecreaseMassageLevelSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged`
Description:	Decrease massage level switch engaged.
Comment:	Affects the property (Massage.Level).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsDecreaseMassageLevelSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsDecreaseMassageLevelSwitchEngaged is e544c4af3ade59bdb8900ad0e7ff3763

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

10 - IsDownSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged`
Description:	Seat down switch engaged.
Comment:	Affects the property (Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsDownSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsDownSwitchEngaged is 011d23e466265dec99a94a4134e6cb64

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

11 - IsForwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged`
Description:	Seat forward switch engaged.
Comment:	Affects the property (Position).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsForwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsForwardSwitchEngaged is 8c2239e876b85b069726a8318e7d19e4

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

12 - IsIncreaseMassageLevelSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged`
Description:	Increase massage level switch engaged.
Comment:	Affects the property (Massage.Level).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsIncreaseMassageLevelSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsIncreaseMassageLevelSwitchEngaged is bfce5eb6b8ad5e7985dffce42f04b320

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

13 - IsTiltBackwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged`
Description:	Tilt backward switch engaged.
Comment:	Affects the property (Tilt).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsTiltBackwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsTiltBackwardSwitchEngaged is e3037de89fc550a7bec263ba0ee2a017

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

14 - IsTiltForwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged`
Description:	Tilt forward switch engaged.
Comment:	Affects the property (Tilt).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsTiltForwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsTiltForwardSwitchEngaged is 750e6a418d0d5a729cc7831f30b1c489

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

15 - IsUpSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged`
Description:	Seat up switch engaged.
Comment:	Affects the property (Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsUpSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsUpSwitchEngaged is f34b08b9d3a1554da8f00201cdab5197

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

16 - IsWarmerSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged`
Description:	Warmer switch for Seat heater.
Comment:	Affects the property (HeatingCooling).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->IsWarmerSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.IsWarmerSwitchEngaged is 2f4bcfebe5675f5e948b7bb11247ad59

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

17 - Massage


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Massage`
Description:	Massage related information for the seat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Massage

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Massage

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Massage is 17936943738e57888f4c11a38570f25c

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable (True if the seat have the massage capability)
Vehicle.Cabin.Seat.Row1.Middle.Massage.Level (Seat massage level. 0 = off. 100 = max massage.)
Vehicle.Cabin.Seat.Row1.Middle.Massage.Status (Massage status.)
Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes (Type of massage.)
Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive (Type of massage active.)

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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.

17.1 - IsAvailable


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable`
Description:	True if the seat have the massage capability

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Massage Massage-->IsAvailable

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable is an Attribute.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Massage.IsAvailable is f7cedbf5663656928b614ef0f52b7aa6

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

17.2 - Level


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Massage.Level`
Description:	Seat massage level. 0 = off. 100 = max massage.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Massage Massage-->Level

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Massage.Level
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Massage.Level: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Massage.Level 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Massage.Level

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Massage.Level`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.Level is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.Level is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Massage.Level is c62f621d99345562bbc823ae2e01ca99

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

17.3 - Status


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Massage.Status`
Description:	Massage status.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Massage Massage-->Status

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Massage.Status
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Massage.Status: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Massage.Status Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Massage.Status

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Massage.Status`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['ON', 'OFF']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.Status is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.Status is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Massage.Status is 32e5010d9cbe52109130ac8500b6d9a3

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

17.4 - SupportedTypes


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes`
Description:	Type of massage.
Comment:	OEMs may define a list of identifiers for supported massage types using the allowed keyword

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Massage Massage-->SupportedTypes

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes`	VSS: Addressing nodes
Data type	`string[]`	VSS: Datatypes

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes is an Attribute.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Massage.SupportedTypes is a8a8addfdf3d58d7bf6aa2e3f3d00783

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

17.5 - TypeActive


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive`
Description:	Type of massage active.
Comment:	OEMs may define a list of identifiers for supported massage types using the allowed keyword

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Massage Massage-->TypeActive

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Massage.TypeActive is adb11b1c61975af09d799dd176982148

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

18 - NeckScarf


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.NeckScarf`
Description:	NeckScarf settings.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->NeckScarf

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.NeckScarf

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.NeckScarf is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.NeckScarf is f2190387c5915353b73ba4e14f109f42

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed (Speed of the fan.)
Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling (Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.)

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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.

18.1 - FanSpeed


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed`
Description:	Speed of the fan.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->NeckScarf NeckScarf-->FanSpeed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.FanSpeed is 84aac3fd05f75521af1acc731d251b17

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

18.2 - HeatingCooling


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling`
Description:	Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->NeckScarf NeckScarf-->HeatingCooling

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.NeckScarf.HeatingCooling is 15932af9bc87568297ae24de019d6d41

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

19 - OccupancyStatus


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus`
Description:	Occupancy status of the seat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->OccupancyStatus

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['UNKNOWN', 'OCCUPIED', 'EMPTY']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.OccupancyStatus is 383d96c670785b3ea3267673b18745dc

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

20 - Position


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Position`
Description:	Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Position
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Position 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Position

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Position`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length
Minimum value	`0`	VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Position is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Position is a9c61deb42ac5bb1b2c92fb5ee222db9

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

21 - SeatBeltHeight


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight`
Description:	Seat belt position on vehicle z-axis. Position is relative within available movable range of the seat belt. 0 = Lowermost position supported.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->SeatBeltHeight

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.SeatBeltHeight is 7e7b9ef4f3b350e9adf8091dff7e799f

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

22 - Seating


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Seating`
Description:	Describes signals related to the seat bottom of the seat.
Comment:	Seating is here considered as the part of the seat that supports the thighs. Additional cushions (if any) for support of lower legs is not covered by this branch.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Seating

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating is a Branch.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Seating is 46a99e1f2b3553099fbb046a6b7dd86d

Children

This vehicle signal is a branch or structure and thus has sub-pages:

Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling (Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.)
Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged (Is switch to decrease seating length engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged (Is switch to increase seating length engaged.)
Vehicle.Cabin.Seat.Row1.Middle.Seating.Length (Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating).)
Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft (Seat bottom side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight (Seat bottom side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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.

22.1 - HeatingCooling


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling`
Description:	Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Seating Seating-->HeatingCooling

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`-100`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Seating.HeatingCooling is e4575c928ffd53f4a970b2fdbab08105

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

22.2 - IsBackwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged`
Description:	Is switch to decrease seating length engaged.
Comment:	Affects the property (Seating.Length).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Seating Seating-->IsBackwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Seating.IsBackwardSwitchEngaged is 02f193b5b7985126a76f83caa3b4eba9

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

22.3 - IsForwardSwitchEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged`
Description:	Is switch to increase seating length engaged.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Seating Seating-->IsForwardSwitchEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Seating.IsForwardSwitchEngaged is b0daea5aed555b5ca0622c8e0e714afe

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

22.4 - Length


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Seating.Length`
Description:	Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Seating Seating-->Length

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Seating.Length
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Seating.Length 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Seating.Length

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Seating.Length`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length
Minimum value	`0`	VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.Length is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.Length is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Seating.Length is 6fcbf711e9c852ba91f7d846f6066978

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

22.5 - SideBolsterSupportLeft


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft`
Description:	Seat bottom side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Seating Seating-->SideBolsterSupportLeft

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportLeft is 6bd67d29441c5dfcb2475c92705761cf

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

22.6 - SideBolsterSupportRight


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight`
Description:	Seat bottom side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Seating Seating-->SideBolsterSupportRight

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`100`	VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Seating.SideBolsterSupportRight is c2ee19a3b75e534f8e86dcc5f393e9c4

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

23 - Tilt


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Middle.Tilt`
Description:	Tilting of seat (seating and backrest) relative to vehicle x-axis. 0 = seat bottom is flat, seat bottom and vehicle x-axis are parallel. Positive degrees = seat tilted backwards, seat x-axis tilted upward, seat z-axis is tilted backward.
Comment:	In VSS it is assumed that tilting a seat affects both seating (seat bottom) and backrest, i.e. the angle between seating and backrest will not be affected when changing Tilt.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Middle Middle-->Tilt

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Middle.Tilt
[get]  OK
Vehicle.Cabin.Seat.Row1.Middle.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Middle.Tilt 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Middle.Tilt

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Middle.Tilt`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`degrees`	VSS: Units
Label	degree
Description	Angle measured in degrees	VSS: Sensors & Actuators
Domain	angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Tilt is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Middle.Tilt is a Signal.

UUID

Each vehicle signal is identified by a Universally Unique Identifier (UUID)

The UUID for Vehicle.Cabin.Seat.Row1.Middle.Tilt is a9931f9f76cd5c9aa7cac23c43d09e38

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:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

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

Middle

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - Airbag

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - IsDeployed

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.2 - IsEnabled

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2 - Backrest

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

2.1 - BottomLumbarSupport

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.2 - HeatingCooling

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.3 - IsLessLumbarSupportSwitchEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.4 - IsLessSideBolsterSupportSwitchEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information