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

Return to the regular view of this page.

Row2
Full qualified VSS Path: Vehicle.Cabin.Door.Row2
Description: All doors, including windows and switches.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->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.Door.Row2

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2 is 74c8a76ad2545ceba474a85ae84eec8e

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 - DriverSide
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide
Description: All doors, including windows and switches.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->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.Door.Row2.DriverSide

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide is 996c7ede1ac453ae9aed508c2835ae56

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 - IsChildLockActive
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.IsChildLockActive
Description: Is door child lock active. True = Door cannot be opened from inside. False = Door can be opened from inside.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->IsChildLockActive

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.IsChildLockActive 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.Door.Row2.DriverSide.IsChildLockActive is a Sensor.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.IsChildLockActive is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.IsChildLockActive is 707facc3d89052d8ae66675ffd8755a8

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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 - IsLocked
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.IsLocked
Description: Is item locked or unlocked. True = Locked. False = Unlocked.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->IsLocked

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.IsLocked 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.Door.Row2.DriverSide.IsLocked is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.IsLocked is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.IsLocked is df98641aae1553a68b741826496d9d42

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.3 - IsOpen
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.IsOpen
Description: Is item open or closed? True = Fully or partially open. False = Fully closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->IsOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.IsOpen 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.Door.Row2.DriverSide.IsOpen is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.IsOpen is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.IsOpen is 49c55921d1825bc1a82334a40eeb45f9

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.4 - Position
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Position
Description: Item position. 0 = Start position 100 = End position.
Comment: Relationship between Open/Close and Start/End position is item dependent.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row2.DriverSide.Position
[get]  OK
Vehicle.Cabin.Door.Row2.DriverSide.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row2.DriverSide.Position 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.DriverSide.Position

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Position 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.Door.Row2.DriverSide.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Position is bf1d5b2f6a0b59bcb18abf24ea45c11e

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.5 - Shade
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Shade
Description: Side window shade. Open = Retracted, Closed = Deployed. Start position for Shade is Open/Retracted.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Shade

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.DriverSide.Shade

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Shade is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Shade is 9b08a5dc400253b8bf31776582f275fd

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.5.1 - IsOpen
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Shade.IsOpen
Description: Is item open or closed? True = Fully or partially open. False = Fully closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Shade Shade-->IsOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Shade.IsOpen 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.Door.Row2.DriverSide.Shade.IsOpen is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Shade.IsOpen is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Shade.IsOpen is 69c6da83b3aa51cd8156e57b2ba431a5

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.5.2 - Position
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position
Description: Item position. 0 = Start position 100 = End position.
Comment: Relationship between Open/Close and Start/End position is item dependent.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Shade Shade-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position
[get]  OK
Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position 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.Door.Row2.DriverSide.Shade.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Shade.Position is 96227261fc205735adb031fb549de6bf

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.5.3 - Switch
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Shade.Switch
Description: Switch controlling sliding action such as window, sunroof, or blind.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Shade Shade-->Switch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Shade.Switch VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['INACTIVE', 'CLOSE', 'OPEN', 'ONE_SHOT_CLOSE', 'ONE_SHOT_OPEN'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Shade.Switch is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Shade.Switch is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Shade.Switch is 81f6196e909d590d858fe4da18c60590

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.6 - Switch
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Switch
Description: Switch controlling sliding action such as window, sunroof, or blind.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Switch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Switch VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['INACTIVE', 'CLOSE', 'OPEN', 'ONE_SHOT_CLOSE', 'ONE_SHOT_OPEN'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Switch is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Switch is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Switch is 3e46afea496054afb12653a9c82c66ad

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.7 - Window
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Window
Description: Door window status. Start position for Window is Closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Window

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.DriverSide.Window

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Window is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Window is bb6ac206a45b507f9f1fe5fdfcf82b31

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.7.1 - IsOpen
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Window.IsOpen
Description: Is item open or closed? True = Fully or partially open. False = Fully closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Window Window-->IsOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Window.IsOpen 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.Door.Row2.DriverSide.Window.IsOpen is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Window.IsOpen is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Window.IsOpen is 1fa3b2f43118575aa2f136fdd15ff61f

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.7.2 - Position
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Window.Position
Description: Item position. 0 = Start position 100 = End position.
Comment: Relationship between Open/Close and Start/End position is item dependent.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Window Window-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row2.DriverSide.Window.Position
[get]  OK
Vehicle.Cabin.Door.Row2.DriverSide.Window.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row2.DriverSide.Window.Position 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.DriverSide.Window.Position

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Window.Position 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.Door.Row2.DriverSide.Window.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Window.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Window.Position is 8a097ade895c5cd8afe9efeef79532fc

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.7.3 - Switch
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.DriverSide.Window.Switch
Description: Switch controlling sliding action such as window, sunroof, or blind.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->DriverSide DriverSide-->Window Window-->Switch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.DriverSide.Window.Switch VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['INACTIVE', 'CLOSE', 'OPEN', 'ONE_SHOT_CLOSE', 'ONE_SHOT_OPEN'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Window.Switch is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.DriverSide.Window.Switch is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.DriverSide.Window.Switch is 4dd1a3858c1b54cc94a8dc4d011ea307

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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 - PassengerSide
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide
Description: All doors, including windows and switches.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->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.Door.Row2.PassengerSide

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide is 16bc38dcd8055f50b54f87478f72f776

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 - IsChildLockActive
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.IsChildLockActive
Description: Is door child lock active. True = Door cannot be opened from inside. False = Door can be opened from inside.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->IsChildLockActive

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.IsChildLockActive 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.Door.Row2.PassengerSide.IsChildLockActive is a Sensor.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.IsChildLockActive is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.IsChildLockActive is 082f7e3633ab56d4a48817329cf46ef9

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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 - IsLocked
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.IsLocked
Description: Is item locked or unlocked. True = Locked. False = Unlocked.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->IsLocked

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.IsLocked 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.Door.Row2.PassengerSide.IsLocked is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.IsLocked is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.IsLocked is 32fa3a8c0b2d5451a4a1976438417305

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.3 - IsOpen
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.IsOpen
Description: Is item open or closed? True = Fully or partially open. False = Fully closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->IsOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.IsOpen 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.Door.Row2.PassengerSide.IsOpen is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.IsOpen is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.IsOpen is 84cab77c9c1d59aba1565b3484c5e01f

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.4 - Position
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Position
Description: Item position. 0 = Start position 100 = End position.
Comment: Relationship between Open/Close and Start/End position is item dependent.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row2.PassengerSide.Position
[get]  OK
Vehicle.Cabin.Door.Row2.PassengerSide.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row2.PassengerSide.Position 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.PassengerSide.Position

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Position 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.Door.Row2.PassengerSide.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Position is 74e971377a1053d284a6bf80cf1aa1c1

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.5 - Shade
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Shade
Description: Side window shade. Open = Retracted, Closed = Deployed. Start position for Shade is Open/Retracted.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Shade

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.PassengerSide.Shade

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Shade is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Shade is 8dc8133322a65057844f9b7eceee6ef9

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.5.1 - IsOpen
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Shade.IsOpen
Description: Is item open or closed? True = Fully or partially open. False = Fully closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Shade Shade-->IsOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Shade.IsOpen 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.Door.Row2.PassengerSide.Shade.IsOpen is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Shade.IsOpen is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Shade.IsOpen is d667cda8637e518e900f0e599f59ca1d

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.5.2 - Position
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position
Description: Item position. 0 = Start position 100 = End position.
Comment: Relationship between Open/Close and Start/End position is item dependent.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Shade Shade-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position
[get]  OK
Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position 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.Door.Row2.PassengerSide.Shade.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Position is aa5627291c29505b8d2f7d652cc4800d

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.5.3 - Switch
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Switch
Description: Switch controlling sliding action such as window, sunroof, or blind.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Shade Shade-->Switch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Switch VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['INACTIVE', 'CLOSE', 'OPEN', 'ONE_SHOT_CLOSE', 'ONE_SHOT_OPEN'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Switch is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Switch is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Shade.Switch is 0c33dd31375452d6ad0c531eac1637c6

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.6 - Switch
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Switch
Description: Switch controlling sliding action such as window, sunroof, or blind.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Switch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Switch VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['INACTIVE', 'CLOSE', 'OPEN', 'ONE_SHOT_CLOSE', 'ONE_SHOT_OPEN'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Switch is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Switch is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Switch is 1411f865d2065849aeb214875d0c099b

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.7 - Window
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Window
Description: Door window status. Start position for Window is Closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Window

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.PassengerSide.Window

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Window is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Window is b64ba696bf7b5fdc8dba79ae5cb119d1

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.7.1 - IsOpen
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Window.IsOpen
Description: Is item open or closed? True = Fully or partially open. False = Fully closed.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Window Window-->IsOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Window.IsOpen 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.Door.Row2.PassengerSide.Window.IsOpen is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Window.IsOpen is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Window.IsOpen is 13e37e2924115c73a36df78f09fad493

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.7.2 - Position
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position
Description: Item position. 0 = Start position 100 = End position.
Comment: Relationship between Open/Close and Start/End position is item dependent.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Window Window-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position
[get]  OK
Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position 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.Door.Row2.PassengerSide.Window.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Window.Position is e3e3fa03f4e357ae8ac8f43799a99350

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.7.3 - Switch
Full qualified VSS Path: Vehicle.Cabin.Door.Row2.PassengerSide.Window.Switch
Description: Switch controlling sliding action such as window, sunroof, or blind.
flowchart LR Vehicle-->Cabin Cabin-->Door Door-->Row2 Row2-->PassengerSide PassengerSide-->Window Window-->Switch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Cabin.Door.Row2.PassengerSide.Window.Switch VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['INACTIVE', 'CLOSE', 'OPEN', 'ONE_SHOT_CLOSE', 'ONE_SHOT_OPEN'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Window.Switch is an Actuator.

The vehicle signal Vehicle.Cabin.Door.Row2.PassengerSide.Window.Switch is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Door.Row2.PassengerSide.Window.Switch is 174b3bc145625a22b23a283c424c28b4

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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.