This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

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:

Feedback

Do you think this 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 - 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:

Feedback

Do you think this 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 - 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:

Feedback

Do you think this 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 - 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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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:

Feedback

Do you think this 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 - 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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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:

Feedback

Do you think this 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 - 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:

Feedback

Do you think this 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.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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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:

Feedback

Do you think this 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.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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.