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

Return to the regular view of this page.

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

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.

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.