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.Row2.Middle.Airbag`
Description:	Airbag signals.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Airbag

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Airbag is aa6d77c09158565787a2e418a1c9ea98

Children

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

Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed (Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.)
Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Airbag.IsDeployed`
Description:	Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Airbag.IsDeployed
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Airbag.IsDeployed

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Airbag.IsDeployed is a Sensor.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsDeployed is cc06da5cab1e5b2e91d180c93c9e8eab

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.Row2.Middle.Airbag.IsEnabled`
Description:	Airbag enabled status. True = Airbag enabled. False = Airbag not enabled.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Airbag.IsEnabled
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Airbag.IsEnabled

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Airbag.IsEnabled is a Sensor.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Airbag.IsEnabled is aa6f761c9c0d57b4bbc63453e70521a1

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.Row2.Middle.Backrest`
Description:	Describes signals related to the backrest of the seat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest is 4f54b32f4c85549b88acbe7cd19dcb20

Children

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

Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport (Bottom lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling (Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged (Is switch for less lumbar support engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged (Is switch for less side bolster support engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged (Lumbar down switch engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged (Lumbar up switch engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged (Is switch for more lumbar support engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged (Is switch for more side bolster support engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged (Backrest recline backward switch engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged (Backrest recline forward switch engaged.)
Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.LumbarSupport (Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport (Mid lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.SideBolsterSupport (Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft (Side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight (Side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport (Top lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)
Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.BottomLumbarSupport`
Description:	Bottom lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.BottomLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.BottomLumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.BottomLumbarSupport is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.BottomLumbarSupport is ca2fbaec7e4b5093a578380fd516217b

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.HeatingCooling is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.HeatingCooling is 03c3ba604f2b5ad1ad189138edd3ebbe

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.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged`
Description:	Is switch for less lumbar support engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessLumbarSupportSwitchEngaged is be65c02b330951ec901345de835154d7

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLessSideBolsterSupportSwitchEngaged is ba58711dca4550bea968ef9ae5ce366a

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.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged`
Description:	Lumbar down switch engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarDownSwitchEngaged is 73afa434e02c54fb830e2b714b1a4390

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.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged`
Description:	Lumbar up switch engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsLumbarUpSwitchEngaged is 31901845ff865c888c8414039a2bccb7

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.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged`
Description:	Is switch for more lumbar support engaged.
Comment:	Affects the property (Backrest.LumbarSupport).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreLumbarSupportSwitchEngaged is b482182275465841bca69b86f9a1e537

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsMoreSideBolsterSupportSwitchEngaged is dba443f0645e5a50b24bb10535157d8d

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.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged`
Description:	Backrest recline backward switch engaged.
Comment:	Affects the property (Backrest.Recline).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineBackwardSwitchEngaged is 108b15fceca25b4489a501641a60cd4b

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.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged`
Description:	Backrest recline forward switch engaged.
Comment:	Affects the property (Backrest.Recline).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.IsReclineForwardSwitchEngaged is e485a9ecb2895869908c8aadd1e663bf

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.LumbarHeight
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.LumbarHeight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.LumbarHeight is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarHeight is 287dc2e74c7f51e8b1a80e0d2082de5d

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.LumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.LumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.LumbarSupport is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.LumbarSupport is c3e749661b695fec9bb47c945054d434

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.Row2.Middle.Backrest.MidLumbarSupport`
Description:	Mid lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.MidLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.MidLumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.MidLumbarSupport is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.MidLumbarSupport is 1a5050bd0d00587e93f9218656157bf3

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.Recline
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.Recline

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.Recline is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.Recline is d24b223dcbb0534389c6c506126497e7

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.Row2.Middle.Backrest.SideBolsterSupport`
Description:	Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.SideBolsterSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.SideBolsterSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.SideBolsterSupport is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupport is 056d829d3b4754b6bd58eca3a5251807

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.SideBolsterSupportLeft
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.SideBolsterSupportLeft

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.SideBolsterSupportLeft is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportLeft is 7c99b57e9de05252a939c2187461a7b9

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Backrest.SideBolsterSupportRight
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.SideBolsterSupportRight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.SideBolsterSupportRight is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.SideBolsterSupportRight is bd306fb69af95f1ab0a9ccf42c374d26

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.Row2.Middle.Backrest.TopLumbarSupport`
Description:	Top lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.TopLumbarSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.TopLumbarSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.TopLumbarSupport is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.TopLumbarSupport is 36611986baa45f24abf784798582e04c

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.Row2.Middle.Backrest.UpperShoulderSupport`
Description:	Upper shoulder support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Backrest.UpperShoulderSupport
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.UpperShoulderSupport

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Backrest.UpperShoulderSupport is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Backrest.UpperShoulderSupport is 1e38aa6c85365114abb3baf78bcc9bf5

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.Row2.Middle.Headrest`
Description:	Headrest settings.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Headrest

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest is eb9a3ea623445fbab28e98ace9716f48

Children

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

Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle (Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.)
Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height (Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.)
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged (Headrest backward switch engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged (Headrest down switch engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged (Headrest forward switch engaged.)
Vehicle.Cabin.Seat.Row2.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.Row2.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-->Row2 Row2-->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.Row2.Middle.Headrest.Angle
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.Angle

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.Angle is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.Angle is 41f7b225f1485deaba50f489d58656da

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Headrest.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.Height

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.Height is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.Height is 987682ae6e7a539897bab4d96458fe15

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.Row2.Middle.Headrest.IsBackwardSwitchEngaged`
Description:	Headrest backward switch engaged.
Comment:	Affects the property (Headrest.Angle).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Headrest.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsBackwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsBackwardSwitchEngaged is be8984cd1ec55f3087dd41290be76ae1

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.Row2.Middle.Headrest.IsDownSwitchEngaged`
Description:	Headrest down switch engaged.
Comment:	Affects the property (Headrest.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Headrest.IsDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsDownSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsDownSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsDownSwitchEngaged is b1ece8266bf55bc394f96e08afc80f99

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.Row2.Middle.Headrest.IsForwardSwitchEngaged`
Description:	Headrest forward switch engaged.
Comment:	Affects the property (Headrest.Angle).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Headrest.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsForwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsForwardSwitchEngaged is bce17ef4aabf5d8e9b444b268b4dc904

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.Row2.Middle.Headrest.IsUpSwitchEngaged`
Description:	Headrest up switch engaged.
Comment:	Affects the property (Headrest.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Headrest.IsUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsUpSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Headrest.IsUpSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Headrest.IsUpSwitchEngaged is ee8aa5267d5b58cf8f71c4178b83f078

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.Row2.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-->Row2 Row2-->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.Row2.Middle.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.HeatingCooling is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.HeatingCooling is 1b0129f265225acba5f18aef705b9c54

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Height

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Height is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Height is 5e2a819627075c7ea1a6fb2c6b7e550d

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.Row2.Middle.IsBackwardSwitchEngaged`
Description:	Seat backward switch engaged.
Comment:	Affects the property (Position).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsBackwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsBackwardSwitchEngaged is 5f793e0dfcf4501591e2fabc5be2af28

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.Row2.Middle.IsBelted`
Description:	Is the belt engaged.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsBelted
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsBelted: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsBelted

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsBelted is a Sensor.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsBelted is a4c37cf044a25eb9925b2278786b6cba

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.Row2.Middle.IsCoolerSwitchEngaged`
Description:	Cooler switch for Seat heater.
Comment:	Affects the property (HeatingCooling).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsCoolerSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsCoolerSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsCoolerSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsCoolerSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsCoolerSwitchEngaged is ff1140c84d9d507f96938a9d3152e543

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.Row2.Middle.IsDecreaseMassageLevelSwitchEngaged`
Description:	Decrease massage level switch engaged.
Comment:	Affects the property (Massage.Level).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsDecreaseMassageLevelSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsDecreaseMassageLevelSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsDecreaseMassageLevelSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsDecreaseMassageLevelSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsDecreaseMassageLevelSwitchEngaged is 29456d12044f55e9a46654aee44e96d5

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.Row2.Middle.IsDownSwitchEngaged`
Description:	Seat down switch engaged.
Comment:	Affects the property (Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsDownSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsDownSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsDownSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsDownSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsDownSwitchEngaged is 96cece27e83d5c3999db197cd6fe8127

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.Row2.Middle.IsForwardSwitchEngaged`
Description:	Seat forward switch engaged.
Comment:	Affects the property (Position).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsForwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsForwardSwitchEngaged is e97fe062314f5177a957ab551a1ec07c

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.Row2.Middle.IsIncreaseMassageLevelSwitchEngaged`
Description:	Increase massage level switch engaged.
Comment:	Affects the property (Massage.Level).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsIncreaseMassageLevelSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsIncreaseMassageLevelSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsIncreaseMassageLevelSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsIncreaseMassageLevelSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsIncreaseMassageLevelSwitchEngaged is 66248149681e5acfb9a35681bcc07c60

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.Row2.Middle.IsTiltBackwardSwitchEngaged`
Description:	Tilt backward switch engaged.
Comment:	Affects the property (Tilt).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsTiltBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsTiltBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsTiltBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsTiltBackwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsTiltBackwardSwitchEngaged is 810d43de175a561c982e8633f6ad19d6

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.Row2.Middle.IsTiltForwardSwitchEngaged`
Description:	Tilt forward switch engaged.
Comment:	Affects the property (Tilt).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsTiltForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsTiltForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsTiltForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsTiltForwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsTiltForwardSwitchEngaged is a95c5a7ad9f25869af04f557f2fb1c65

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.Row2.Middle.IsUpSwitchEngaged`
Description:	Seat up switch engaged.
Comment:	Affects the property (Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsUpSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsUpSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsUpSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsUpSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsUpSwitchEngaged is a0bf0e0429475c0099e49081e008026a

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.Row2.Middle.IsWarmerSwitchEngaged`
Description:	Warmer switch for Seat heater.
Comment:	Affects the property (HeatingCooling).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.IsWarmerSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.IsWarmerSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsWarmerSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.IsWarmerSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.IsWarmerSwitchEngaged is e5515205b1fc52058984c3f82a81cc96

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.Row2.Middle.Massage`
Description:	Massage related information for the seat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Massage

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Massage is d5c053d69d3457ecb3b87be15ccbfe1c

Children

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

Vehicle.Cabin.Seat.Row2.Middle.Massage.IsAvailable (True if the seat have the massage capability)
Vehicle.Cabin.Seat.Row2.Middle.Massage.Level (Seat massage level. 0 = off. 100 = max massage.)
Vehicle.Cabin.Seat.Row2.Middle.Massage.Status (Massage status.)
Vehicle.Cabin.Seat.Row2.Middle.Massage.SupportedTypes (Type of massage.)
Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.IsAvailable`
Description:	True if the seat have the massage capability

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Massage.IsAvailable
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Massage.IsAvailable: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.IsAvailable

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.IsAvailable is an Attribute.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Massage.IsAvailable is 236cdccef8475f66b7ea563e4907b853

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.Row2.Middle.Massage.Level`
Description:	Seat massage level. 0 = off. 100 = max massage.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Massage.Level
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Massage.Level: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.Level

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.Level is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Massage.Level is 42f36d6391565e318c04f932fc650108

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.Row2.Middle.Massage.Status`
Description:	Massage status.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Massage.Status
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Massage.Status: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.Status

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.Status is a Sensor.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Massage.Status is 0ef20438065954ab87f45e379e60a443

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Massage.SupportedTypes
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Massage.SupportedTypes: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.SupportedTypes

Data Type & Unit


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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Massage.SupportedTypes is 2a941bbffdaf5d90b9733575b8e471f9

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Massage.TypeActive
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Massage.TypeActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.TypeActive

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Massage.TypeActive is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Massage.TypeActive is 3d91c02a4fd05e81b13e32ceeb84b3fd

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.Row2.Middle.NeckScarf`
Description:	NeckScarf settings.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.NeckScarf

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.NeckScarf is 8c87d16046f45f8eb69b011d7ea26032

Children

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

Vehicle.Cabin.Seat.Row2.Middle.NeckScarf.FanSpeed (Speed of the fan.)
Vehicle.Cabin.Seat.Row2.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.Row2.Middle.NeckScarf.FanSpeed`
Description:	Speed of the fan.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.NeckScarf.FanSpeed
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.NeckScarf.FanSpeed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.NeckScarf.FanSpeed

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.NeckScarf.FanSpeed is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.NeckScarf.FanSpeed is 15f7ccfd6f6a54549df0364df3638466

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.Row2.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-->Row2 Row2-->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.Row2.Middle.NeckScarf.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.NeckScarf.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.NeckScarf.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.NeckScarf.HeatingCooling is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.NeckScarf.HeatingCooling is c461efb1ea97557991fa8e8b98c7f09d

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.Row2.Middle.OccupancyStatus`
Description:	Occupancy status of the seat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.OccupancyStatus
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.OccupancyStatus: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.OccupancyStatus

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.OccupancyStatus is a Sensor.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.OccupancyStatus is a3a2c8e7e7e6514b83d5fcce2f77a6aa

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Position
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Position

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Position is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Position is c7e61a5fe6f35d0fb50a4cbb3c5d15e8

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.Row2.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-->Row2 Row2-->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.Row2.Middle.SeatBeltHeight
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.SeatBeltHeight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.SeatBeltHeight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.SeatBeltHeight is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.SeatBeltHeight is 6c22e3d28bcd51ae97e01c8ace4dee74

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Seating

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Seating is 8a5674259c805a498c827cc4341b20c7

Children

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

Vehicle.Cabin.Seat.Row2.Middle.Seating.HeatingCooling (Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.)
Vehicle.Cabin.Seat.Row2.Middle.Seating.IsBackwardSwitchEngaged (Is switch to decrease seating length engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Seating.IsForwardSwitchEngaged (Is switch to increase seating length engaged.)
Vehicle.Cabin.Seat.Row2.Middle.Seating.Length (Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating).)
Vehicle.Cabin.Seat.Row2.Middle.Seating.SideBolsterSupportLeft (Seat bottom side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.)
Vehicle.Cabin.Seat.Row2.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.Row2.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-->Row2 Row2-->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.Row2.Middle.Seating.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Seating.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.HeatingCooling

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.HeatingCooling is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Seating.HeatingCooling is d68be922379f5b069e0e8853f4b44c78

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.Row2.Middle.Seating.IsBackwardSwitchEngaged`
Description:	Is switch to decrease seating length engaged.
Comment:	Affects the property (Seating.Length).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Seating.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Seating.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.IsBackwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.IsBackwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Seating.IsBackwardSwitchEngaged is 01d7b09b14195b9fad13eb6681e11818

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.Row2.Middle.Seating.IsForwardSwitchEngaged`
Description:	Is switch to increase seating length engaged.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->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.Row2.Middle.Seating.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Seating.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.IsForwardSwitchEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.IsForwardSwitchEngaged is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Seating.IsForwardSwitchEngaged is b8a75d55af925d24bf867602ced23fb9

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Seating.Length
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.Length

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.Length is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Seating.Length is 76071549a729587fbdebb78ef360cad9

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Seating.SideBolsterSupportLeft
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Seating.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.SideBolsterSupportLeft

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.SideBolsterSupportLeft is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Seating.SideBolsterSupportLeft is df00febbd0255d9eb6e72050bd761e33

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Seating.SideBolsterSupportRight
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Seating.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.SideBolsterSupportRight

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Seating.SideBolsterSupportRight is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Seating.SideBolsterSupportRight is c02337e1f9d95608ada9bff8422eb2d1

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.Row2.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-->Row2 Row2-->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.Row2.Middle.Tilt
[get]  OK
Vehicle.Cabin.Seat.Row2.Middle.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Tilt

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row2.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.Row2.Middle.Tilt is an Actuator.

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Middle.Tilt is 30d7caa224e6589a882751be94fb7a33

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