Vehicle.Cabin.Seat.Row1.Pos3.Airbag (Airbag signals.)
Vehicle.Cabin.Seat.Row1.Pos3.Backrest (Describes signals related to the backrest of the seat.)
Vehicle.Cabin.Seat.Row1.Pos3.Headrest (Headrest settings.)
Vehicle.Cabin.Seat.Row1.Pos3.Heating (Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat.)
Vehicle.Cabin.Seat.Row1.Pos3.Height (Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported.)
Vehicle.Cabin.Seat.Row1.Pos3.IsBelted (Is the belt engaged.)
Vehicle.Cabin.Seat.Row1.Pos3.IsOccupied (Does the seat have a passenger in it.)
Vehicle.Cabin.Seat.Row1.Pos3.Massage (Seat massage level. 0 = off. 100 = max massage.)
Vehicle.Cabin.Seat.Row1.Pos3.Occupant (Occupant data.)
Vehicle.Cabin.Seat.Row1.Pos3.Position (Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.)
Vehicle.Cabin.Seat.Row1.Pos3.Seating (Describes signals related to the seat bottom of the seat.)
Vehicle.Cabin.Seat.Row1.Pos3.Switch (Seat switch signals)
Vehicle.Cabin.Seat.Row1.Pos3.Tilt (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.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch`
Description:	Seat switch signals

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch

Digital Auto: Playground

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

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch is 1eda245135ce5788bfcbc75b082af947

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest (Describes switches related to the backrest of the seat.)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest (Switches for SingleSeat.Headrest.)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsBackwardEngaged (Seat backward switch engaged (SingleSeat.Position).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsCoolerEngaged (Cooler switch for Seat heater (SingleSeat.Heating).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsDownEngaged (Seat down switch engaged (SingleSeat.Height).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsForwardEngaged (Seat forward switch engaged (SingleSeat.Position).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltBackwardEngaged (Tilt backward switch engaged (SingleSeat.Tilt).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltForwardEngaged (Tilt forward switch engaged (SingleSeat.Tilt).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsUpEngaged (Seat up switch engaged (SingleSeat.Height).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsWarmerEngaged (Warmer switch for Seat heater (SingleSeat.Heating).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage (Switches for SingleSeat.Massage.)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating (Describes switches related to the seating of the seat.)

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


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

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest is ad180dd9d2de56cf911dfc35d47c46fb

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineBackwardEngaged (Backrest recline backward switch engaged (SingleSeat.Backrest.Recline).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineForwardEngaged (Backrest recline forward switch engaged (SingleSeat.Backrest.Recline).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar (Switches for SingleSeat.Backrest.Lumbar.)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster (Switches for SingleSeat.Backrest.SideBolster.)

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.1 - IsReclineBackwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineBackwardEngaged`
Description:	Backrest recline backward switch engaged (SingleSeat.Backrest.Recline).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->IsReclineBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineBackwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineBackwardEngaged is 1861981891f959dc896e00f4e369c86d

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.1.2 - IsReclineForwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineForwardEngaged`
Description:	Backrest recline forward switch engaged (SingleSeat.Backrest.Recline).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->IsReclineForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineForwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.IsReclineForwardEngaged is 2a8cc40fb0b3556da210b7dfce7c0c6d

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.1.3 - Lumbar


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar`
Description:	Switches for SingleSeat.Backrest.Lumbar.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar

Digital Auto: Playground

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

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar is 08b8112168d1584ab6fa8f594016745f

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsDownEngaged (Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged (Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged (Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsUpEngaged (Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.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.

1.1.3.1 - IsDownEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsDownEngaged`
Description:	Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsDownEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsDownEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is 9a3655967c5b5f058e01c0b3770ba0d3

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.1.3.2 - IsLessSupportEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged`
Description:	Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is 0f0708693e605289af83c3a1ecfd3159

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.1.3.3 - IsMoreSupportEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged`
Description:	Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is 6d590f0db798515b8d8e6f0bf1abfd67

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.1.3.4 - IsUpEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsUpEngaged`
Description:	Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsUpEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsUpEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is 663dca40a7645e66adfa00d64223dbbe

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.1.4 - SideBolster


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster`
Description:	Switches for SingleSeat.Backrest.SideBolster.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->SideBolster

Digital Auto: Playground

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

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster is 46c9fbf2750b517f8d1c09fee21fdd06

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged (Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged (Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.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.

1.1.4.1 - IsLessSupportEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged`
Description:	Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is 53a56a868fb3593fb21378b2d4dbbc7c

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.1.4.2 - IsMoreSupportEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged`
Description:	Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is 05b0ef6b02e55bb2814bcd95d9b77bd9

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


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest`
Description:	Switches for SingleSeat.Headrest.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Headrest

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest is e04ee2c9d0f852c983136186bb15be4c

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsBackwardEngaged (Head rest backward switch engaged (SingleSeat.Headrest.Angle).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsDownEngaged (Head rest down switch engaged (SingleSeat.Headrest.Height).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsForwardEngaged (Head rest forward switch engaged (SingleSeat.Headrest.Angle).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsUpEngaged (Head rest up switch engaged (SingleSeat.Headrest.Height).)

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.2.1 - IsBackwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsBackwardEngaged`
Description:	Head rest backward switch engaged (SingleSeat.Headrest.Angle).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsBackwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsBackwardEngaged is cc633d8a000a5da3b0efe50e520e21fa

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.2 - IsDownEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsDownEngaged`
Description:	Head rest down switch engaged (SingleSeat.Headrest.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsDownEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsDownEngaged is 4ed2d91060bf5e578746b4b2f5a3e671

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.3 - IsForwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsForwardEngaged`
Description:	Head rest forward switch engaged (SingleSeat.Headrest.Angle).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsForwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsForwardEngaged is 6ad93c92d96a59838e4810f0425f1fb0

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.4 - IsUpEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsUpEngaged`
Description:	Head rest up switch engaged (SingleSeat.Headrest.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsUpEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Headrest.IsUpEngaged is 89b2444c58c457bd936ecef543e7cc96

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.3 - IsBackwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsBackwardEngaged`
Description:	Seat backward switch engaged (SingleSeat.Position).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsBackwardEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsBackwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsBackwardEngaged is 52d8da88ec95586a93952ea3d59023ad

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.4 - IsCoolerEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsCoolerEngaged`
Description:	Cooler switch for Seat heater (SingleSeat.Heating).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsCoolerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsCoolerEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsCoolerEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsCoolerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsCoolerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsCoolerEngaged is f5ed89b2972e5461abb6966e30a906ff

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.5 - IsDownEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsDownEngaged`
Description:	Seat down switch engaged (SingleSeat.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsDownEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsDownEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsDownEngaged is 66e1d88d56ba572db7b97a5e20cc724c

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.6 - IsForwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsForwardEngaged`
Description:	Seat forward switch engaged (SingleSeat.Position).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsForwardEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsForwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsForwardEngaged is a3661e29e11957ed9cc12bb385b896bf

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.7 - IsTiltBackwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltBackwardEngaged`
Description:	Tilt backward switch engaged (SingleSeat.Tilt).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsTiltBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltBackwardEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltBackwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltBackwardEngaged is ed590c68f1085a3c9889fc571ace2176

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.8 - IsTiltForwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltForwardEngaged`
Description:	Tilt forward switch engaged (SingleSeat.Tilt).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsTiltForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltForwardEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltForwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsTiltForwardEngaged is 8eeefcb4a08e5d9f8eae76e92826e56e

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.9 - IsUpEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsUpEngaged`
Description:	Seat up switch engaged (SingleSeat.Height).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsUpEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsUpEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsUpEngaged is 1240dc083504580b97ba1cfadb9da659

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.10 - IsWarmerEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsWarmerEngaged`
Description:	Warmer switch for Seat heater (SingleSeat.Heating).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->IsWarmerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsWarmerEngaged

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsWarmerEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsWarmerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsWarmerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.IsWarmerEngaged is 0d7eed9ccb24537fb7f97f0163a4fdd8

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.11 - Massage


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage`
Description:	Switches for SingleSeat.Massage.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Massage

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage is a2c4a3a39758594d9e89a635bab499cb

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsDecreaseEngaged (Decrease massage level switch engaged (SingleSeat.Massage).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsIncreaseEngaged (Increase massage level switch engaged (SingleSeat.Massage).)

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.11.1 - IsDecreaseEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsDecreaseEngaged`
Description:	Decrease massage level switch engaged (SingleSeat.Massage).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Massage Massage-->IsDecreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsDecreaseEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsDecreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsDecreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsDecreaseEngaged is 329dfaaab56f55a39ca9c132ee4bf533

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.11.2 - IsIncreaseEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsIncreaseEngaged`
Description:	Increase massage level switch engaged (SingleSeat.Massage).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Massage Massage-->IsIncreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsIncreaseEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsIncreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsIncreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Massage.IsIncreaseEngaged is 6d09e331ceb55a2691f120a6f1205cbb

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.12 - Seating


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating`
Description:	Describes switches related to the seating of the seat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Seating

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating is b1ff7876dbab59f2bf7358c932a7e1fb

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsBackwardEngaged (Is switch to decrease seating length engaged (SingleSeat.Seating.Length).)
Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsForwardEngaged (Is switch to increase seating length engaged (SingleSeat.Seating.Length).)

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.12.1 - IsBackwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsBackwardEngaged`
Description:	Is switch to decrease seating length engaged (SingleSeat.Seating.Length).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Seating Seating-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsBackwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsBackwardEngaged is b9829f44a76857e0bc9deeb036ecd311

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.12.2 - IsForwardEngaged


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsForwardEngaged`
Description:	Is switch to increase seating length engaged (SingleSeat.Seating.Length).

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Switch Switch-->Seating Seating-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsForwardEngaged`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Switch.Seating.IsForwardEngaged is c8ab873dd8fb51dd9493fb00f33e01d6

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


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

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

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Airbag is 243d103c16055180abef52fef071ad22

Children

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

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

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


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Airbag.IsDeployed is c4e9b66d938d5e188ac577094daaf37e

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


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

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

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Backrest is ce7b00453a0a53d3b6e6cbc395bd5c78

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar (Adjustable lumbar support mechanisms in seats allow the user to change the seat back shape.)
Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Recline (Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline.)
Vehicle.Cabin.Seat.Row1.Pos3.Backrest.SideBolster (Backrest side bolster (lumbar side support) settings.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar`
Description:	Adjustable lumbar support mechanisms in seats allow the user to change the seat back shape.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Backrest Backrest-->Lumbar

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar is 678e3d997c295575ba6337464fe2a912

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Height (Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported.)
Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Support (Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.)

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.1 - Height


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

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Backrest Backrest-->Lumbar Lumbar-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Height`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Distance measured in millimeters	VSS: Sensors & Actuators
Domain	distance
Minimum value	`0`	VSS: Sensors & Actuators

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Height is 4a529381905750be9c09a1bfec05eabd

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.1.2 - Support


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Support`
Description:	Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Backrest Backrest-->Lumbar Lumbar-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Lumbar.Support is 127744c26ebe5c729d69a95bfe96b00e

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


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Backrest.Recline is dc901384498f5de6b93b2a5b3850fb87

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


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Backrest.SideBolster`
Description:	Backrest side bolster (lumbar side support) settings.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Backrest Backrest-->SideBolster

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Backrest.SideBolster is 605ae18d7b4e5613ac7252ee35df58c1

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Backrest.SideBolster.Support (Side bolster 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.

3.3.1 - Support


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

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Backrest Backrest-->SideBolster SideBolster-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Backrest.SideBolster.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Backrest.SideBolster.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Backrest.SideBolster.Support is dba595a898b75345bf1d013a45261681

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


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

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

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Headrest is 1714ccbc269f59ee807a51c7f1a6103b

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Headrest.Angle (Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.)
Vehicle.Cabin.Seat.Row1.Pos3.Headrest.Height (Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.)

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.

4.1 - Angle


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Headrest.Angle is b4d77cf7a7f55768b3910435e79027f2

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.2 - Height


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Headrest.Height is 420eaf9bc7ac5560a26ad018afe27e1b

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


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Heating`
Description:	Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Heating

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Heating is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Heating is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Heating is 4af67468dd7a55a58195d9b61997d077

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


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Height is d19199de59a153f782b8d61788c510a7

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


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

About VSS

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

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name	Type	Min	Max
uint8	unsigned 8-bit integer	0	255
int8	signed 8-bit integer	-128	127
uint16	unsigned 16-bit integer	0	65535
int16	signed 16-bit integer	-32768	32767
uint32	unsigned 32-bit integer	0	4294967295
int32	signed 32-bit integer	-2147483648	2147483647
uint64	unsigned 64-bit integer	0	2^64 - 1
int64	signed 64-bit integer	-2^63	2^63 - 1
boolean	boolean value	0/false	1/true
float	floating point number	-3.4e -38	3.4e 38
double	double precision floating point number	-1.7e -300	1.7e 300
string	character string	n/a	n/a

7 - IsBelted


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.IsBelted is 975fe66f9fa05d8ca7fb9d334641bb97

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


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.IsOccupied`
Description:	Does the seat have a passenger in it.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->IsOccupied

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.IsOccupied`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.IsOccupied is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.IsOccupied is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.IsOccupied is 1540906a83bd5f70af4859910aafd890

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


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Massage is d63d68381ec65f50a8dd6dfbc0bd751d

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


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Occupant`
Description:	Occupant data.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Occupant

Digital Auto: Playground

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

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

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant is 4e68d3feef825f6f99c44cec9f7c1217

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier (Identifier attributes based on OAuth 2.0.)

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.

10.1 - Identifier


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier`
Description:	Identifier attributes based on OAuth 2.0.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Occupant Occupant-->Identifier

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier is f59d9531974256cab958e5e31588565d

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer (Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com.)
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject (Subject for the authentication of the occupant. E.g. UserID 7331677.)

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.

10.1.1 - Issuer


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer`
Description:	Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Occupant Occupant-->Identifier Identifier-->Issuer

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer
[get]  OK
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer Foo
[set]  OK

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer is 0d29fa2a1b97563c8e1ba31b8571f328

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.1.2 - Subject


Full qualified VSS Path:	`Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject`
Description:	Subject for the authentication of the occupant. E.g. UserID 7331677.

flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->Pos3 Pos3-->Occupant Occupant-->Identifier Identifier-->Subject

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject
[get]  OK
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject Foo
[set]  OK

Digital Auto: Playground

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

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject

Data Type & Unit


Path	`Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject is a7306a24de2155f2a1de070bc8f1bd60

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


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Position is 2a2ba0e42dcc563cba80cc491b66c45f

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


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

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

Digital Auto: Playground

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Seating is 4c98bb65b4095480bdc7262b902a767a

Children

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

Vehicle.Cabin.Seat.Row1.Pos3.Seating.Length (Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating).)

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.

12.1 - Length


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Seating.Length is c44b283345dd5a428bd099ed1153d4a4

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


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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Digital Auto: Playground

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

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

Data Type & Unit


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

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

Signal Information

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

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Tilt is 9fb74b71b3ce54f4af6e5e472f159949

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

Pos3

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - Switch

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - Backrest

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1.1 - IsReclineBackwardEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.2 - IsReclineForwardEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.3 - Lumbar

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1.3.1 - IsDownEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.3.2 - IsLessSupportEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.3.3 - IsMoreSupportEngaged

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback