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

Return to the regular view of this page.

Front
Full qualified VSS Path: Vehicle.Body.Trunk.Front
Description: Trunk status. Start position for Trunk is Closed.
Comment: A trunk is a luggage compartment in a vehicle. Depending on vehicle, it can be either in the front or back of the vehicle. Some vehicles may have trunks both at the front and at the rear of the vehicle.
flowchart LR Vehicle-->Body Body-->Trunk Trunk-->Front

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.Body.Trunk.Front

Signal Information

The vehicle signal Vehicle.Body.Trunk.Front is a Branch.

UUID

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

The UUID for Vehicle.Body.Trunk.Front is a455aca5bae55c22b7949fd31a765a6c

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 - IsLightOn
Full qualified VSS Path: Vehicle.Body.Trunk.Front.IsLightOn
Description: Is trunk light on
Comment: V4.0 Moved from Vehicle.Cabin.Lights.IsTrunkOn because Trunk is not defined as part of the Cabin.
flowchart LR Vehicle-->Body Body-->Trunk Trunk-->Front Front-->IsLightOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.IsLightOn is an Actuator.

The vehicle signal Vehicle.Body.Trunk.Front.IsLightOn is a Signal.

UUID

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

The UUID for Vehicle.Body.Trunk.Front.IsLightOn is 43d7844934a45890bf2a287b676a994b

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 - IsLocked
Full qualified VSS Path: Vehicle.Body.Trunk.Front.IsLocked
Description: Is item locked or unlocked. True = Locked. False = Unlocked.
flowchart LR Vehicle-->Body Body-->Trunk Trunk-->Front Front-->IsLocked

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Front.IsLocked
[get]  OK
Vehicle.Body.Trunk.Front.IsLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.IsLocked

Data Type & Unit
Path Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.IsLocked is an Actuator.

The vehicle signal Vehicle.Body.Trunk.Front.IsLocked is a Signal.

UUID

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

The UUID for Vehicle.Body.Trunk.Front.IsLocked is e0eabc210f07505fa1b66b67729d681b

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 - IsOpen
Full qualified VSS Path: Vehicle.Body.Trunk.Front.IsOpen
Description: Is item open or closed? True = Fully or partially open. False = Fully closed.
flowchart LR Vehicle-->Body Body-->Trunk Trunk-->Front Front-->IsOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Front.IsOpen
[get]  OK
Vehicle.Body.Trunk.Front.IsOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.IsOpen

Data Type & Unit
Path Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.IsOpen is an Actuator.

The vehicle signal Vehicle.Body.Trunk.Front.IsOpen is a Signal.

UUID

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

The UUID for Vehicle.Body.Trunk.Front.IsOpen is 2047de0896a352fcaf02baa06819a023

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.

4 - Position
Full qualified VSS Path: Vehicle.Body.Trunk.Front.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-->Body Body-->Trunk Trunk-->Front Front-->Position

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Front.Position
[get]  OK
Vehicle.Body.Trunk.Front.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.Position

Data Type & Unit
Path Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.Position is an Actuator.

The vehicle signal Vehicle.Body.Trunk.Front.Position is a Signal.

UUID

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

The UUID for Vehicle.Body.Trunk.Front.Position is 6d871111a565517098cd29936a30dd22

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.

5 - Switch
Full qualified VSS Path: Vehicle.Body.Trunk.Front.Switch
Description: Switch controlling sliding action such as window, sunroof, or blind.
flowchart LR Vehicle-->Body Body-->Trunk Trunk-->Front Front-->Switch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Front.Switch
[get]  OK
Vehicle.Body.Trunk.Front.Switch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.Switch

Data Type & Unit
Path Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.Switch is an Actuator.

The vehicle signal Vehicle.Body.Trunk.Front.Switch is a Signal.

UUID

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

The UUID for Vehicle.Body.Trunk.Front.Switch is 63a651cd414652aba970a937af0b3621

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.