
Full qualified VSS Path:	`Vehicle.Cabin.Light`
Description:	Light that is part of the Cabin.
Comment:	V4.0 branch renamed from “Lights” to “Light” to comply with singular naming of entities. Use SingleConfigurableLight.vspec to describe interior lights that can be configured.

flowchart LR Vehicle-->Cabin Cabin-->Light

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

Signal Information

The vehicle signal Vehicle.Cabin.Light is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light is 2fc2ad48d5315cc4aa1e4638a6985585

Children

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

Vehicle.Cabin.Light.AmbientLight (Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.)
Vehicle.Cabin.Light.InteractiveLightBar (Decorative coloured light bar that supports effects, usually mounted on the dashboard (e.g. BMW i7 Interactive bar).)
Vehicle.Cabin.Light.IsDomeOn (Is central dome light on)
Vehicle.Cabin.Light.IsGloveBoxOn (Is glove box light on)
Vehicle.Cabin.Light.PerceivedAmbientLight (The percentage of ambient light that is measured (e.g., by a sensor) inside the cabin. 0 = No ambient light. 100 = Full brightness.)
Vehicle.Cabin.Light.Spotlight (Spotlight for a specific area in the vehicle.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight`
Description:	Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight

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.Light.AmbientLight

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight is c3983df208565cb78c8af970a57351fd

Children

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

Vehicle.Cabin.Light.AmbientLight.Row1 (Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.)
Vehicle.Cabin.Light.AmbientLight.Row2 (Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1`
Description:	Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1

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.Light.AmbientLight.Row1

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1 is b3447dca710f51e39ed1af3d240f8851

Children

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

Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide (Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.)
Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide (Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide`
Description:	Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->DriverSide

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.Light.AmbientLight.Row1.DriverSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide is e42bfc0abac857f0a40f579cc0ced424

Children

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

Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->DriverSide DriverSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color 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.Light.AmbientLight.Row1.DriverSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Color is c5717a5df33359959d1df3ae75dd687e

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->DriverSide DriverSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity 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.Light.AmbientLight.Row1.DriverSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity`	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	`1`	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.Light.AmbientLight.Row1.DriverSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.Intensity is a9ddbecc501e5ad4b95b7197cd4d6edf

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->DriverSide DriverSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn 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.Light.AmbientLight.Row1.DriverSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn`	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.Light.AmbientLight.Row1.DriverSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.DriverSide.IsLightOn is 3b6d9d8d6acb55bc81022522cf2499a3

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide`
Description:	Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->PassengerSide

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.Light.AmbientLight.Row1.PassengerSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide is 05a04fb5fb025049b9e9fbb109fef22a

Children

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

Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->PassengerSide PassengerSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color 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.Light.AmbientLight.Row1.PassengerSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Color is a58681f838a75596b6b64623803479cc

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->PassengerSide PassengerSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity 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.Light.AmbientLight.Row1.PassengerSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity`	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	`1`	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.Light.AmbientLight.Row1.PassengerSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.Intensity is 9d9096fdd737597b8423214633a97063

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row1 Row1-->PassengerSide PassengerSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn 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.Light.AmbientLight.Row1.PassengerSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn`	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.Light.AmbientLight.Row1.PassengerSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row1.PassengerSide.IsLightOn is a52466424a9550868a5f6a1aa83f3dce

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2`
Description:	Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2

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.Light.AmbientLight.Row2

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2 is f4462f76907e529fbcc7cc6761ca5cbe

Children

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

Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide (Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.)
Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide (Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide`
Description:	Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->DriverSide

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.Light.AmbientLight.Row2.DriverSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide is ddf477f1910e595f8c8055508cbdd808

Children

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

Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->DriverSide DriverSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color 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.Light.AmbientLight.Row2.DriverSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Color is 8eb7ad17cb3f546c96fb8f76a7ac09f6

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->DriverSide DriverSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity 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.Light.AmbientLight.Row2.DriverSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity`	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	`1`	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.Light.AmbientLight.Row2.DriverSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.Intensity is 93c3bf189e045a52b2134aa20cfcf2b2

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->DriverSide DriverSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn 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.Light.AmbientLight.Row2.DriverSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn`	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.Light.AmbientLight.Row2.DriverSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.DriverSide.IsLightOn is c95376e9f63f5ae996907ab83fa40a0b

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide`
Description:	Decorative coloured light inside the cabin, usually mounted on the door, ceiling, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->PassengerSide

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.Light.AmbientLight.Row2.PassengerSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide is b9a621db27d75d56b377890d98222d53

Children

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

Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->PassengerSide PassengerSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color 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.Light.AmbientLight.Row2.PassengerSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Color is 6ed1d61f74155275bde970d8233f0f51

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->PassengerSide PassengerSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity 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.Light.AmbientLight.Row2.PassengerSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity`	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	`1`	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.Light.AmbientLight.Row2.PassengerSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.Intensity is 1e9bcef987795ad3a38bc76de810df19

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->AmbientLight AmbientLight-->Row2 Row2-->PassengerSide PassengerSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn 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.Light.AmbientLight.Row2.PassengerSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn`	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.Light.AmbientLight.Row2.PassengerSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.AmbientLight.Row2.PassengerSide.IsLightOn is e61968ff0fb15adf891efadc9181f78c

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.InteractiveLightBar`
Description:	Decorative coloured light bar that supports effects, usually mounted on the dashboard (e.g. BMW i7 Interactive bar).

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->InteractiveLightBar

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.Light.InteractiveLightBar

Signal Information

The vehicle signal Vehicle.Cabin.Light.InteractiveLightBar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.InteractiveLightBar is de6062a1a9c05ff687128f748307e331

Children

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

Vehicle.Cabin.Light.InteractiveLightBar.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.InteractiveLightBar.Effect (Light effect selection from a predefined set of allowed values.)
Vehicle.Cabin.Light.InteractiveLightBar.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.InteractiveLightBar.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->InteractiveLightBar InteractiveLightBar-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.InteractiveLightBar.Color
[get]  OK
Vehicle.Cabin.Light.InteractiveLightBar.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.InteractiveLightBar.Color 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.Light.InteractiveLightBar.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.InteractiveLightBar.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.InteractiveLightBar.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.InteractiveLightBar.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.InteractiveLightBar.Color is 099955ec87a0528ba1a89cc3e439c806

Feedback

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


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

About VSS

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

Supported datatypes

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

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

2.2 - Effect


Full qualified VSS Path:	`Vehicle.Cabin.Light.InteractiveLightBar.Effect`
Description:	Light effect selection from a predefined set of allowed values.
Comment:	Default and allowed values are OEM-specific and should be defined accordingly (e.g. with the use of overlays).

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->InteractiveLightBar InteractiveLightBar-->Effect

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.InteractiveLightBar.Effect
[get]  OK
Vehicle.Cabin.Light.InteractiveLightBar.Effect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.InteractiveLightBar.Effect 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.Light.InteractiveLightBar.Effect

Data Type & Unit


Path	`Vehicle.Cabin.Light.InteractiveLightBar.Effect`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.InteractiveLightBar.Effect is an Actuator.

The vehicle signal Vehicle.Cabin.Light.InteractiveLightBar.Effect is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.InteractiveLightBar.Effect is c0167026c1575ec8a2de0901a71d0d8d

Feedback

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


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

About VSS

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

Supported datatypes

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

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

2.3 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.InteractiveLightBar.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->InteractiveLightBar InteractiveLightBar-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.InteractiveLightBar.Intensity
[get]  OK
Vehicle.Cabin.Light.InteractiveLightBar.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.InteractiveLightBar.Intensity 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.Light.InteractiveLightBar.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.InteractiveLightBar.Intensity`	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	`1`	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.Light.InteractiveLightBar.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.InteractiveLightBar.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.InteractiveLightBar.Intensity is 9c73159ff0db5341af2bd3aaffc183c5

Feedback

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


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

About VSS

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

Supported datatypes

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

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

2.4 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->InteractiveLightBar InteractiveLightBar-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn
[get]  OK
Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn 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.Light.InteractiveLightBar.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn`	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.Light.InteractiveLightBar.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.InteractiveLightBar.IsLightOn is 7c858ba899585fd6bb65a981db056fd7

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.IsDomeOn`
Description:	Is central dome light on

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->IsDomeOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.IsDomeOn
[get]  OK
Vehicle.Cabin.Light.IsDomeOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.IsDomeOn 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.Light.IsDomeOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.IsDomeOn`	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.Light.IsDomeOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.IsDomeOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.IsDomeOn is 0dcbdddcc3bb59d292bd7a0cf3747c83

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.IsGloveBoxOn`
Description:	Is glove box light on

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->IsGloveBoxOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.IsGloveBoxOn
[get]  OK
Vehicle.Cabin.Light.IsGloveBoxOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.IsGloveBoxOn 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.Light.IsGloveBoxOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.IsGloveBoxOn`	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.Light.IsGloveBoxOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.IsGloveBoxOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.IsGloveBoxOn is 9b4db6bf8cc95c7a855442b95e1e0e18

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.PerceivedAmbientLight`
Description:	The percentage of ambient light that is measured (e.g., by a sensor) inside the cabin. 0 = No ambient light. 100 = Full brightness.
Comment:	V4.0 named changed from “AmbientLight” to “PerceivedAmbientLight”. This is a read-only property that refers to the pre-existing light (e.g., natural light). If you are looking for the in-cabin decorative lights that sometimes are also called “AmbientLights”, please refer to the branch Vehicle.Cabin.Light.AmbientLight.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->PerceivedAmbientLight

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.PerceivedAmbientLight
[get]  OK
Vehicle.Cabin.Light.PerceivedAmbientLight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.PerceivedAmbientLight 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.Light.PerceivedAmbientLight

Data Type & Unit


Path	`Vehicle.Cabin.Light.PerceivedAmbientLight`	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.Light.PerceivedAmbientLight is a Sensor.

The vehicle signal Vehicle.Cabin.Light.PerceivedAmbientLight is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.PerceivedAmbientLight is 4d605e0e591a510d9613bdb412175729

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight

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.Light.Spotlight

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight is a03cd35849a05136ac8e16f4e96d866b

Children

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

Vehicle.Cabin.Light.Spotlight.Row1 (Spotlight for a specific area in the vehicle.)
Vehicle.Cabin.Light.Spotlight.Row2 (Spotlight for a specific area in the vehicle.)
Vehicle.Cabin.Light.Spotlight.Row3 (Spotlight for a specific area in the vehicle.)
Vehicle.Cabin.Light.Spotlight.Row4 (Spotlight for a specific area in the vehicle.)

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.

6.1 - Row1


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1

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.Light.Spotlight.Row1

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1 is 35f4c5574dbb5c5bafe82107b55377ec

Children

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

Vehicle.Cabin.Light.Spotlight.Row1.DriverSide (Spotlight for a specific area in the vehicle.)
Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide (Spotlight for a specific area in the vehicle.)

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.

6.1.1 - DriverSide


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.DriverSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->DriverSide

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.Light.Spotlight.Row1.DriverSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.DriverSide is 39ac4414f40754e2ab28a6bb10b397bb

Children

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

Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.1.1.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->DriverSide DriverSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color 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.Light.Spotlight.Row1.DriverSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Color is 838b3bc619d153d993ddfad96918ad7e

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.1.1.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->DriverSide DriverSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity 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.Light.Spotlight.Row1.DriverSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity`	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	`1`	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.Light.Spotlight.Row1.DriverSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.Intensity is 497ba6de557452829f1c3bbcad2c1386

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.1.1.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->DriverSide DriverSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn 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.Light.Spotlight.Row1.DriverSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn`	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.Light.Spotlight.Row1.DriverSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.DriverSide.IsLightOn is dff99845cbdf54239f1cc36834434a91

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->PassengerSide

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.Light.Spotlight.Row1.PassengerSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide is 669fe375bd1151b497eab93492e41597

Children

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

Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.1.2.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->PassengerSide PassengerSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color 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.Light.Spotlight.Row1.PassengerSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Color is 7643021f0af15edeba9e35f7e87a7bd5

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.1.2.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->PassengerSide PassengerSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity 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.Light.Spotlight.Row1.PassengerSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity`	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	`1`	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.Light.Spotlight.Row1.PassengerSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.Intensity is a2d72853978f54379cd66a2c82cd63fa

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.1.2.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row1 Row1-->PassengerSide PassengerSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn 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.Light.Spotlight.Row1.PassengerSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn`	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.Light.Spotlight.Row1.PassengerSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row1.PassengerSide.IsLightOn is 834df09382ee509b898b2ff2652a3ea2

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2

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.Light.Spotlight.Row2

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2 is 259f6228620a532abbac5548c72b3c35

Children

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

Vehicle.Cabin.Light.Spotlight.Row2.DriverSide (Spotlight for a specific area in the vehicle.)
Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide (Spotlight for a specific area in the vehicle.)

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.

6.2.1 - DriverSide


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.DriverSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->DriverSide

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.Light.Spotlight.Row2.DriverSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.DriverSide is 92fe0ca17e39548d8681a0fdd4f2a035

Children

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

Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.2.1.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->DriverSide DriverSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color 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.Light.Spotlight.Row2.DriverSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Color is fddcfd397c63530b8b7e6f3c5fd98b20

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.2.1.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->DriverSide DriverSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity 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.Light.Spotlight.Row2.DriverSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity`	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	`1`	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.Light.Spotlight.Row2.DriverSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.Intensity is 054dfd5255675357b090663df26c6370

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.2.1.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->DriverSide DriverSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn 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.Light.Spotlight.Row2.DriverSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn`	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.Light.Spotlight.Row2.DriverSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.DriverSide.IsLightOn is d7cdb8c7fe305b99a482ac7f8025519b

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.2.2 - PassengerSide


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->PassengerSide

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.Light.Spotlight.Row2.PassengerSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide is 1e9617c06a0b53eca745dcf96f8d5d70

Children

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

Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.2.2.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->PassengerSide PassengerSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color 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.Light.Spotlight.Row2.PassengerSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Color is bdc48b556b565f0e9fd4e68b814ee934

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.2.2.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->PassengerSide PassengerSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity 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.Light.Spotlight.Row2.PassengerSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity`	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	`1`	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.Light.Spotlight.Row2.PassengerSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.Intensity is b5e5c87ee11c5f84a7d92dc7871f3241

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.2.2.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row2 Row2-->PassengerSide PassengerSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn 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.Light.Spotlight.Row2.PassengerSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn`	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.Light.Spotlight.Row2.PassengerSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row2.PassengerSide.IsLightOn is ded8281b9520524ead6bc1a5c3cccd5d

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3

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.Light.Spotlight.Row3

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3 is 7b6666a198e8514582f8c85525dccceb

Children

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

Vehicle.Cabin.Light.Spotlight.Row3.DriverSide (Spotlight for a specific area in the vehicle.)
Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide (Spotlight for a specific area in the vehicle.)

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.

6.3.1 - DriverSide


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.DriverSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->DriverSide

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.Light.Spotlight.Row3.DriverSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.DriverSide is 36bd0e114ba652b0919db771e3a0d946

Children

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

Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.3.1.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->DriverSide DriverSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color 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.Light.Spotlight.Row3.DriverSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Color is 5394e601144f5d75ae66a1566d182c68

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.3.1.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->DriverSide DriverSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity 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.Light.Spotlight.Row3.DriverSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity`	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	`1`	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.Light.Spotlight.Row3.DriverSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.Intensity is 50376cb5f02750d599f3ae5932520952

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.3.1.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->DriverSide DriverSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn 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.Light.Spotlight.Row3.DriverSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn`	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.Light.Spotlight.Row3.DriverSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.DriverSide.IsLightOn is fa58686f4c925907a17f40aded066a01

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.3.2 - PassengerSide


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->PassengerSide

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.Light.Spotlight.Row3.PassengerSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide is 69b6df651e9b5154b46c5709ce167fb6

Children

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

Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.3.2.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->PassengerSide PassengerSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color 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.Light.Spotlight.Row3.PassengerSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Color is b50787e8b3bf56ebb3e007ee21aa1f30

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.3.2.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->PassengerSide PassengerSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity 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.Light.Spotlight.Row3.PassengerSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity`	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	`1`	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.Light.Spotlight.Row3.PassengerSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.Intensity is b8e1a7326abe538199f595555c4c0ca0

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.3.2.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row3 Row3-->PassengerSide PassengerSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn 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.Light.Spotlight.Row3.PassengerSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn`	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.Light.Spotlight.Row3.PassengerSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row3.PassengerSide.IsLightOn is 68eacf65617c56489f0c1f475576eaaa

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


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4

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.Light.Spotlight.Row4

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4 is 41b0adb2cba85665824d3ad497b593a8

Children

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

Vehicle.Cabin.Light.Spotlight.Row4.DriverSide (Spotlight for a specific area in the vehicle.)
Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide (Spotlight for a specific area in the vehicle.)

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.

6.4.1 - DriverSide


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.DriverSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->DriverSide

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.Light.Spotlight.Row4.DriverSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.DriverSide is 661dcc2f512159329fc272128a054b0b

Children

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

Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.4.1.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->DriverSide DriverSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color 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.Light.Spotlight.Row4.DriverSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Color is 6cc3fc21887c593a90d799209dcc40c0

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.4.1.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->DriverSide DriverSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity 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.Light.Spotlight.Row4.DriverSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity`	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	`1`	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.Light.Spotlight.Row4.DriverSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.Intensity is 5459910482cb507db1583252b26e62c7

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.4.1.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->DriverSide DriverSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn 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.Light.Spotlight.Row4.DriverSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn`	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.Light.Spotlight.Row4.DriverSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.DriverSide.IsLightOn is ca9e9652c52757ce98744209c0d2344f

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.4.2 - PassengerSide


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide`
Description:	Spotlight for a specific area in the vehicle.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->PassengerSide

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.Light.Spotlight.Row4.PassengerSide

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide is fbffb10dc86a523bb40f624c1ad385e7

Children

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

Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color (Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.)
Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity (How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).)
Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn (Indicates whether the light is turned on. True = On, False = Off.)

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.

6.4.2.1 - Color


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color`
Description:	Hexadecimal color code represented as a 3-byte RGB (i.e. Red, Green, and Blue) value preceded by a hash symbol “#”. Allowed range “#000000” to “#FFFFFF”.
Comment:	For example; “#C0C0C0” = Silver, “#FFD700” = Gold, “#000000” = Black, “#FFFFFF” = White, etc.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->PassengerSide PassengerSide-->Color

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color 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.Light.Spotlight.Row4.PassengerSide.Color

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Color is fde4be32cd6f5fcf8997b01564eaadaf

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.4.2.2 - Intensity


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity`
Description:	How much of the maximum possible brightness of the light is used. 1 = Maximum attenuation, 100 = No attenuation (i.e. full brightness).
Comment:	Minimum value cannot be zero as on/off is controlled by the actuator IsLightOn. V4.0 moved from Cabin.Lights.AmbientLight.Intensity to enable individual control of lights via the SingleConfigurableLight.vspec.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->PassengerSide PassengerSide-->Intensity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity 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.Light.Spotlight.Row4.PassengerSide.Intensity

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity`	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	`1`	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.Light.Spotlight.Row4.PassengerSide.Intensity is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.Intensity is 8be53f681198503bb8f93d331e2315cd

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.4.2.3 - IsLightOn


Full qualified VSS Path:	`Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn`
Description:	Indicates whether the light is turned on. True = On, False = Off.

flowchart LR Vehicle-->Cabin Cabin-->Light Light-->Spotlight Spotlight-->Row4 Row4-->PassengerSide PassengerSide-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn
[get]  OK
Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn 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.Light.Spotlight.Row4.PassengerSide.IsLightOn

Data Type & Unit


Path	`Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn`	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.Light.Spotlight.Row4.PassengerSide.IsLightOn is an Actuator.

The vehicle signal Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Light.Spotlight.Row4.PassengerSide.IsLightOn is c35925e7af4d5a929b153cb7f587ca5b

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

Light

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - AmbientLight

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - Row1

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1.1 - DriverSide

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1.1.1 - Color

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.1.2 - Intensity

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.1.3 - IsLightOn

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.2 - PassengerSide

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1.2.1 - Color

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes