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.Seat.Row2
Description: All seats.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->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.Seat.Row2

Signal Information

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

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2 is 8c3aaf015ef8595cb45d9461a9c1195f

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3
Description: All seats.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3

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.Seat.Row2.Pos3

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3 is a40aa679981551e7a92b8438533911d4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Airbag
Description: Airbag signals.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Airbag

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.Seat.Row2.Pos3.Airbag

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Airbag is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Airbag is e1d14ad055955eac914a47ee180a6e78

Children

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

Feedback

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

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

About VSS

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

1.1.1 - IsDeployed

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed
Description: Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Airbag Airbag-->IsDeployed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed 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.Seat.Row2.Pos3.Airbag.IsDeployed

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed 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.Seat.Row2.Pos3.Airbag.IsDeployed is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Airbag.IsDeployed is 6802243fcb3155b196cca3a825c12bcb

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Headrest
Description: Headrest settings.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Headrest

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.Seat.Row2.Pos3.Headrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest is a14ecc5524645ca883e2838f666bce70

Children

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

Feedback

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

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

About VSS

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

1.2.1 - Angle

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle
Description: Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Headrest Headrest-->Angle

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle 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.Seat.Row2.Pos3.Headrest.Angle

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Angle is bf6f63ab87e453af965c90f0495ea972

Feedback

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

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

About VSS

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

Supported datatypes

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

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

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

1.2.2 - Height

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height
Description: Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Headrest Headrest-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height 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.Seat.Row2.Pos3.Headrest.Height

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 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.Seat.Row2.Pos3.Headrest.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Headrest.Height is 2ae8b66df4045f46a96acbcdd6d2d452

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch
Description: Seat switch signals
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch

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.Seat.Row2.Pos3.Switch

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch is e0cfa7aceac75980b33075ceef5c9125

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest
Description: Switches for SingleSeat.Headrest.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Headrest

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.Seat.Row2.Pos3.Switch.Headrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest is dd4de742803250eaa1efeceaad116e1d

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged
Description: Head rest backward switch engaged (SingleSeat.Headrest.Angle).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged 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.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsBackwardEngaged is 04e14e79404b5ff7ac9067841f81bbc9

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged
Description: Head rest down switch engaged (SingleSeat.Headrest.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged 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.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsDownEngaged is 61a58c7fa7ed5e08a17067193bb9c951

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged
Description: Head rest forward switch engaged (SingleSeat.Headrest.Angle).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged 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.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsForwardEngaged is 3c94aab710ff5e8f8a48fdbf6dc7b989

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged
Description: Head rest up switch engaged (SingleSeat.Headrest.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Headrest Headrest-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged 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.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Headrest.IsUpEngaged is e40c92c141f6562382f4f29d783cfa26

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage
Description: Switches for SingleSeat.Massage.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Massage

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.Seat.Row2.Pos3.Switch.Massage

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage is ac2bb22d6acf56988582353a1453cbe3

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged
Description: Decrease massage level switch engaged (SingleSeat.Massage).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Massage Massage-->IsDecreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged 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.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsDecreaseEngaged is 7226bc97842452099d5484baad0af620

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged
Description: Increase massage level switch engaged (SingleSeat.Massage).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Massage Massage-->IsIncreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged 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.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Massage.IsIncreaseEngaged is fb062e9f85fd568cbd774b36fbf5113f

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest
Description: Describes switches related to the backrest of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest

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.Seat.Row2.Pos3.Switch.Backrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest is 583a22d4a1365db9bf386a96bcafd292

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged
Description: Backrest recline backward switch engaged (SingleSeat.Backrest.Recline).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->IsReclineBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged 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.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineBackwardEngaged is eed918c7f0b558a99bbe804582a31b64

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged
Description: Backrest recline forward switch engaged (SingleSeat.Backrest.Recline).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->IsReclineForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged 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.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.IsReclineForwardEngaged is 0cc4f8336f0d585f93f4ab5c89e133d8

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar
Description: Switches for SingleSeat.Backrest.Lumbar.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar

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.Seat.Row2.Pos3.Switch.Backrest.Lumbar

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar is 1d631b9c90a25a858a6caabe8ead1826

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged
Description: Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged 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.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsDownEngaged is dcd08d675e7e5f4eafe85311a3e40f1e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged
Description: Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged 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.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsLessSupportEngaged is 866f9a7d358e5eb5985c9c675b4f7eb4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged
Description: Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged 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.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsMoreSupportEngaged is cf9c077f2f4d5573a6022f5f08e807d3

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged
Description: Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged 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.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.Lumbar.IsUpEngaged is f0fd5a54865452bcbf2939d8acd4273c

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster
Description: Switches for SingleSeat.Backrest.SideBolster.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->SideBolster

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.Seat.Row2.Pos3.Switch.Backrest.SideBolster

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster is 79d8d65b4c1d54a4ab1306d56e839c49

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged
Description: Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged 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.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsLessSupportEngaged is e99b4f4b07af511b9d86454eec1c483c

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged
Description: Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged 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.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Backrest.SideBolster.IsMoreSupportEngaged is 92341df5af725c8282f6f93644f1ec9f

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged
Description: Seat backward switch engaged (SingleSeat.Position).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged 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.Seat.Row2.Pos3.Switch.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsBackwardEngaged is 267429a5f95d5f47ac47ec301755df32

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged
Description: Cooler switch for Seat heater (SingleSeat.Heating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsCoolerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged 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.Seat.Row2.Pos3.Switch.IsCoolerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsCoolerEngaged is ffff3283b2cf5f7292e241ec2ee27e77

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged
Description: Seat down switch engaged (SingleSeat.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged 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.Seat.Row2.Pos3.Switch.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsDownEngaged is 73d2e688696a507b826230d5b53c429f

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged
Description: Seat forward switch engaged (SingleSeat.Position).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged 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.Seat.Row2.Pos3.Switch.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsForwardEngaged is 397a8afd0dd1533b8899248596ae7566

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged
Description: Tilt backward switch engaged (SingleSeat.Tilt).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsTiltBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged 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.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltBackwardEngaged is 4490bc9063715f238c00c1eea91fa964

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged
Description: Tilt forward switch engaged (SingleSeat.Tilt).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsTiltForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged 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.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsTiltForwardEngaged is 98d34a35ab82571e88e2d647b5a772f4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged
Description: Seat up switch engaged (SingleSeat.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged 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.Seat.Row2.Pos3.Switch.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsUpEngaged is 26752cad0db150a2aa6737b825e96256

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged
Description: Warmer switch for Seat heater (SingleSeat.Heating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->IsWarmerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged 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.Seat.Row2.Pos3.Switch.IsWarmerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.IsWarmerEngaged is 820cc2c323b45ef989d5bcb8aac9527e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating
Description: Describes switches related to the seating of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Seating

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.Seat.Row2.Pos3.Switch.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating is 0ed3b90fe1b4581782fac8496bace4b8

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged
Description: Is switch to decrease seating length engaged (SingleSeat.Seating.Length).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Seating Seating-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged 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.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsBackwardEngaged is 2999a262b18e5476ab621e0cba4045e8

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged
Description: Is switch to increase seating length engaged (SingleSeat.Seating.Length).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Switch Switch-->Seating Seating-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged 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.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Switch.Seating.IsForwardEngaged is d32a5d6d85ff5b64b0157ae215cee44e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Backrest
Description: Describes signals related to the backrest of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Backrest

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.Seat.Row2.Pos3.Backrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest is 561be9f8b4f9587bb0d139cc33071742

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar
Description: Adjustable lumbar support mechanisms in seats allow the user to change the seat back shape.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Backrest Backrest-->Lumbar

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.Seat.Row2.Pos3.Backrest.Lumbar

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar is 2410df6d719c56a58617644a8afc7240

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height
Description: Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Backrest Backrest-->Lumbar Lumbar-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height 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.Seat.Row2.Pos3.Backrest.Lumbar.Height

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 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.Seat.Row2.Pos3.Backrest.Lumbar.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Height is 38b30eb99fd35c5693c18361c566c6e9

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support
Description: Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Backrest Backrest-->Lumbar Lumbar-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support 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.Seat.Row2.Pos3.Backrest.Lumbar.Support

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support VSS: Addressing nodes
Data type float 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Lumbar.Support is b227f493bab0503589b3a54c30ade03c

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline
Description: Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline.
Comment: Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Backrest Backrest-->Recline

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline 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.Seat.Row2.Pos3.Backrest.Recline

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.Recline is 867a9d4d4e685407906d561946921c24

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster
Description: Backrest side bolster (lumbar side support) settings.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Backrest Backrest-->SideBolster

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.Seat.Row2.Pos3.Backrest.SideBolster

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster is d52ea54e1d725eb88fa1c061a07a3217

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support
Description: Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Backrest Backrest-->SideBolster SideBolster-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support 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.Seat.Row2.Pos3.Backrest.SideBolster.Support

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support VSS: Addressing nodes
Data type float 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Backrest.SideBolster.Support is b4cef1fd83d653aca5c941865bbf96b7

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Heating
Description: Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Heating

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Heating VSS: Addressing nodes
Data type int8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value -100 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Heating is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Heating is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Heating is 2a175561eed05247b3048263c0122fa1

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Height
Description: Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Height VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Height is 077a21fca4d857dd81debfd81119bc73

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.IsBelted
Description: Is the belt engaged.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->IsBelted

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.IsBelted 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.Seat.Row2.Pos3.IsBelted is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.IsBelted is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.IsBelted is 815f9e1dc05b5078aaefc3868319b18b

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied
Description: Does the seat have a passenger in it.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->IsOccupied

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied 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.Seat.Row2.Pos3.IsOccupied is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.IsOccupied is 018a7ef68dd75f0ea391c7d8191acd9d

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Massage
Description: Seat massage level. 0 = off. 100 = max massage.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Massage

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Massage 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.Seat.Row2.Pos3.Massage is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Massage is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Massage is fffccf6ae6365b83ab093031f573e452

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Occupant
Description: Occupant data.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Occupant

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.Seat.Row2.Pos3.Occupant

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant is a8df9afde2335f8ab7cf4b185148f20e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier
Description: Identifier attributes based on OAuth 2.0.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Occupant Occupant-->Identifier

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.Seat.Row2.Pos3.Occupant.Identifier

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier is 296e51d414a65cea96e1eea27dc3e1dd

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer
Description: Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Occupant Occupant-->Identifier Identifier-->Issuer

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer 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.Seat.Row2.Pos3.Occupant.Identifier.Issuer

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Issuer is d96b225635b959a1aea0d6febb955ae8

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject
Description: Subject for the authentication of the occupant. E.g. UserID 7331677.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Occupant Occupant-->Identifier Identifier-->Subject

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject 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.Seat.Row2.Pos3.Occupant.Identifier.Subject

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Occupant.Identifier.Subject is ea36896f5572580b9d8379a6256f61b5

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Position
Description: Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->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.Seat.Row2.Pos3.Position
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.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.Seat.Row2.Pos3.Position

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Position VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Position is 64eb763cc10358b49968797fbf50c092

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Seating
Description: Describes signals related to the seat bottom of the seat.
Comment: Seating is here considered as the part of the seat that supports the thighs. Additional cushions (if any) for support of lower legs is not covered by this branch.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Seating

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.Seat.Row2.Pos3.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Seating is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Seating is 1dcb55c75dd55fc0bf752fcf17ba79be

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length
Description: Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Seating Seating-->Length

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length 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.Seat.Row2.Pos3.Seating.Length

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Seating.Length is b188311a9fd95b9195b28ab7be00d68f

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos3.Tilt
Description: Tilting of seat (seating and backrest) relative to vehicle x-axis. 0 = seat bottom is flat, seat bottom and vehicle x-axis are parallel. Positive degrees = seat tilted backwards, seat x-axis tilted upward, seat z-axis is tilted backward.
Comment: In VSS it is assumed that tilting a seat affects both seating (seat bottom) and backrest, i.e. the angle between seating and backrest will not be affected when changing Tilt.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos3 Pos3-->Tilt

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos3.Tilt VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Tilt is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos3.Tilt is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos3.Tilt is 5702e9961d4353eea849901a12886cf1

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2
Description: All seats.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2

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.Seat.Row2.Pos2

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2 is e8afa112abe75fda9ce3e1f0d712713d

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Airbag
Description: Airbag signals.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Airbag

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.Seat.Row2.Pos2.Airbag

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Airbag is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Airbag is 07f9f55e33055cf7bebdc06e7d5a6a14

Children

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

Feedback

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

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

About VSS

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

2.1.1 - IsDeployed

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Airbag.IsDeployed
Description: Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Airbag Airbag-->IsDeployed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Airbag.IsDeployed
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Airbag.IsDeployed 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.Seat.Row2.Pos2.Airbag.IsDeployed

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Airbag.IsDeployed 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.Seat.Row2.Pos2.Airbag.IsDeployed is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Airbag.IsDeployed is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Airbag.IsDeployed is 668f397bc95358989119fb1cfdfa8a01

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Headrest
Description: Headrest settings.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Headrest

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.Seat.Row2.Pos2.Headrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Headrest is 46dcaa7ca75d57c7a5301b7107538812

Children

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

Feedback

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

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

About VSS

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

2.2.1 - Angle

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle
Description: Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Headrest Headrest-->Angle

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle 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.Seat.Row2.Pos2.Headrest.Angle

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Angle is d3d4f0a7f5c15072b80f88c2743b77be

Feedback

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

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

About VSS

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

Supported datatypes

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

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

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

2.2.2 - Height

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Height
Description: Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Headrest Headrest-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Height 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.Seat.Row2.Pos2.Headrest.Height

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Height VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 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.Seat.Row2.Pos2.Headrest.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Headrest.Height is 1e955420a3d6591e84aa2b6bbd2bed18

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Seating
Description: Describes signals related to the seat bottom of the seat.
Comment: Seating is here considered as the part of the seat that supports the thighs. Additional cushions (if any) for support of lower legs is not covered by this branch.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Seating

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.Seat.Row2.Pos2.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Seating is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Seating is 899171a0b84a563daf6cea0542405031

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length
Description: Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Seating Seating-->Length

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length 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.Seat.Row2.Pos2.Seating.Length

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Seating.Length is fbdac9db983b5f52a900d24cf2d424c4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch
Description: Seat switch signals
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch

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.Seat.Row2.Pos2.Switch

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch is f3fdef2159cb5cda985cbc04220c3593

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest
Description: Switches for SingleSeat.Headrest.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Headrest

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.Seat.Row2.Pos2.Switch.Headrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest is 077d7df6106f5d04884a5f44f917493a

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsBackwardEngaged
Description: Head rest backward switch engaged (SingleSeat.Headrest.Angle).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Headrest Headrest-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsBackwardEngaged 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.Seat.Row2.Pos2.Switch.Headrest.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsBackwardEngaged is 5a6c05fe3aa854199b3a2d83a91ff07d

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsDownEngaged
Description: Head rest down switch engaged (SingleSeat.Headrest.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Headrest Headrest-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsDownEngaged 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.Seat.Row2.Pos2.Switch.Headrest.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsDownEngaged is a1bab160e2bf563b991b22c820ae17c4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsForwardEngaged
Description: Head rest forward switch engaged (SingleSeat.Headrest.Angle).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Headrest Headrest-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsForwardEngaged 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.Seat.Row2.Pos2.Switch.Headrest.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsForwardEngaged is aa43a5239e255308b617306b71723c5b

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsUpEngaged
Description: Head rest up switch engaged (SingleSeat.Headrest.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Headrest Headrest-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsUpEngaged 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.Seat.Row2.Pos2.Switch.Headrest.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Headrest.IsUpEngaged is 5b096959633953a9b7c4c52af0c85fa9

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage
Description: Switches for SingleSeat.Massage.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Massage

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.Seat.Row2.Pos2.Switch.Massage

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage is 1fabf329e8715f28b90b72a8a5b6c3de

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsDecreaseEngaged
Description: Decrease massage level switch engaged (SingleSeat.Massage).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Massage Massage-->IsDecreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsDecreaseEngaged 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.Seat.Row2.Pos2.Switch.Massage.IsDecreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsDecreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsDecreaseEngaged is 20b139513267583e8a4a2374fcde2626

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsIncreaseEngaged
Description: Increase massage level switch engaged (SingleSeat.Massage).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Massage Massage-->IsIncreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsIncreaseEngaged 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.Seat.Row2.Pos2.Switch.Massage.IsIncreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsIncreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Massage.IsIncreaseEngaged is 32fff40566d95d0cb36ed76100e515c3

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest
Description: Describes switches related to the backrest of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest

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.Seat.Row2.Pos2.Switch.Backrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest is 1abd0c2387ea56479575b324795cdf2e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineBackwardEngaged
Description: Backrest recline backward switch engaged (SingleSeat.Backrest.Recline).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->IsReclineBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineBackwardEngaged 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.Seat.Row2.Pos2.Switch.Backrest.IsReclineBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineBackwardEngaged is 366a8acb011b5997a07930a1b7e62e69

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineForwardEngaged
Description: Backrest recline forward switch engaged (SingleSeat.Backrest.Recline).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->IsReclineForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineForwardEngaged 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.Seat.Row2.Pos2.Switch.Backrest.IsReclineForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.IsReclineForwardEngaged is fd142d6b8b1353118a5c6e6afb635145

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar
Description: Switches for SingleSeat.Backrest.Lumbar.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->Lumbar

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.Seat.Row2.Pos2.Switch.Backrest.Lumbar

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar is ed202bc72cd75d5d940f8b7eedfce763

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsDownEngaged
Description: Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsDownEngaged 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.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsDownEngaged is 1092743255ee5cb7a11b172f2d6a9f2e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged
Description: Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged 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.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsLessSupportEngaged is 7dc46ce3336f5c6ab31fe33e52a56cb5

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged
Description: Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged 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.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsMoreSupportEngaged is 475e608bc2aa50f8ad9eea738415d7e3

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsUpEngaged
Description: Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsUpEngaged 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.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.Lumbar.IsUpEngaged is 5f6c6804d50955ec8a898a890120a126

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster
Description: Switches for SingleSeat.Backrest.SideBolster.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->SideBolster

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.Seat.Row2.Pos2.Switch.Backrest.SideBolster

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster is 69625c26aabf50fda25c5389994ad485

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged
Description: Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged 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.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsLessSupportEngaged is f9edf7174eda59a0a2403450939a4a00

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged
Description: Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged 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.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Backrest.SideBolster.IsMoreSupportEngaged is 4b8c68ce106155b78b40f09cc000dfdd

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsBackwardEngaged
Description: Seat backward switch engaged (SingleSeat.Position).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsBackwardEngaged 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.Seat.Row2.Pos2.Switch.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsBackwardEngaged is 19c46bf9c19955a1a619fd3311b5236e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsCoolerEngaged
Description: Cooler switch for Seat heater (SingleSeat.Heating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsCoolerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsCoolerEngaged 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.Seat.Row2.Pos2.Switch.IsCoolerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsCoolerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsCoolerEngaged is 0d72a18529d55286be69d517c94cbb74

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsDownEngaged
Description: Seat down switch engaged (SingleSeat.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsDownEngaged 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.Seat.Row2.Pos2.Switch.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsDownEngaged is 3774266336e05ddbacadd2ef017568b1

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsForwardEngaged
Description: Seat forward switch engaged (SingleSeat.Position).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsForwardEngaged 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.Seat.Row2.Pos2.Switch.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsForwardEngaged is 79d68b154c12508d91f28bedafb47a43

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltBackwardEngaged
Description: Tilt backward switch engaged (SingleSeat.Tilt).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsTiltBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltBackwardEngaged 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.Seat.Row2.Pos2.Switch.IsTiltBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltBackwardEngaged is c587834e47e651e3b1556b6f7b4c738d

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltForwardEngaged
Description: Tilt forward switch engaged (SingleSeat.Tilt).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsTiltForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltForwardEngaged 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.Seat.Row2.Pos2.Switch.IsTiltForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsTiltForwardEngaged is 90cdb504ff1a5d0bb512fe7034c7bf07

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsUpEngaged
Description: Seat up switch engaged (SingleSeat.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsUpEngaged 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.Seat.Row2.Pos2.Switch.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsUpEngaged is 7b1f9f36a4f65e7a8aad6b94c186ec00

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsWarmerEngaged
Description: Warmer switch for Seat heater (SingleSeat.Heating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->IsWarmerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsWarmerEngaged 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.Seat.Row2.Pos2.Switch.IsWarmerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsWarmerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.IsWarmerEngaged is e0a9b4614dbb5c4fbd3e333a73edf8b0

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating
Description: Describes switches related to the seating of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Seating

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.Seat.Row2.Pos2.Switch.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating is 10ccb625321652e5a12470d14ff7ecd0

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsBackwardEngaged
Description: Is switch to decrease seating length engaged (SingleSeat.Seating.Length).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Seating Seating-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsBackwardEngaged 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.Seat.Row2.Pos2.Switch.Seating.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsBackwardEngaged is 8f8492873cb05b9098e8eb564a43394a

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsForwardEngaged
Description: Is switch to increase seating length engaged (SingleSeat.Seating.Length).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Switch Switch-->Seating Seating-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsForwardEngaged 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.Seat.Row2.Pos2.Switch.Seating.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Switch.Seating.IsForwardEngaged is 4f2b176b4f1657fe8395439df7376d12

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Backrest
Description: Describes signals related to the backrest of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Backrest

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.Seat.Row2.Pos2.Backrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Backrest is 25a2e0b3833f55c1a0b8ad2589ad2a18

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster
Description: Backrest side bolster (lumbar side support) settings.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Backrest Backrest-->SideBolster

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.Seat.Row2.Pos2.Backrest.SideBolster

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster is ff84905ea881586dafbdfa2268888ba4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support
Description: Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Backrest Backrest-->SideBolster SideBolster-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support 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.Seat.Row2.Pos2.Backrest.SideBolster.Support

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support VSS: Addressing nodes
Data type float 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Backrest.SideBolster.Support is 5b7bbfe5ce975a79a029a839a91ebafb

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar
Description: Adjustable lumbar support mechanisms in seats allow the user to change the seat back shape.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Backrest Backrest-->Lumbar

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.Seat.Row2.Pos2.Backrest.Lumbar

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar is b69532b796ca54a1a897b28270fe0e56

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Height
Description: Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Backrest Backrest-->Lumbar Lumbar-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Height 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.Seat.Row2.Pos2.Backrest.Lumbar.Height

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Height VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 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.Seat.Row2.Pos2.Backrest.Lumbar.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Height is 6389ff80f23e5985b734207d97a4a58e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support
Description: Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Backrest Backrest-->Lumbar Lumbar-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support 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.Seat.Row2.Pos2.Backrest.Lumbar.Support

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support VSS: Addressing nodes
Data type float 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Lumbar.Support is fcbec0664f315476b901bd4f0b1df006

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline
Description: Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline.
Comment: Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Backrest Backrest-->Recline

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline 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.Seat.Row2.Pos2.Backrest.Recline

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Backrest.Recline is b260c18880c75c92a635b9dc887fadca

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Heating
Description: Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Heating

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Heating VSS: Addressing nodes
Data type int8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value -100 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Heating is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Heating is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Heating is c7eb6ca24426596dab519386d231a9d1

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Height
Description: Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Height VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Height is 3cf2e042421b540da4aa047680dcdf84

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.IsBelted
Description: Is the belt engaged.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->IsBelted

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.IsBelted 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.Seat.Row2.Pos2.IsBelted is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.IsBelted is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.IsBelted is f2c9c2d624bb5cf4bf9aba5842eb96eb

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.IsOccupied
Description: Does the seat have a passenger in it.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->IsOccupied

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.IsOccupied 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.Seat.Row2.Pos2.IsOccupied is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.IsOccupied is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.IsOccupied is dc1eaa7cab895c5198af0c7f5dea9d79

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Massage
Description: Seat massage level. 0 = off. 100 = max massage.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Massage

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Massage 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.Seat.Row2.Pos2.Massage is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Massage is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Massage is 77e8a4d481315520927fc0828158772e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Occupant
Description: Occupant data.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Occupant

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.Seat.Row2.Pos2.Occupant

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Occupant is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Occupant is 30e72777238850ff8a01c3a8f85b663e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier
Description: Identifier attributes based on OAuth 2.0.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Occupant Occupant-->Identifier

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.Seat.Row2.Pos2.Occupant.Identifier

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier is 24c23b9f5adb549483cb52acbd81a980

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer
Description: Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Occupant Occupant-->Identifier Identifier-->Issuer

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer 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.Seat.Row2.Pos2.Occupant.Identifier.Issuer

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Issuer is 6f4e6a9f8008536eae03197601a6366a

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject
Description: Subject for the authentication of the occupant. E.g. UserID 7331677.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Occupant Occupant-->Identifier Identifier-->Subject

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject 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.Seat.Row2.Pos2.Occupant.Identifier.Subject

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Occupant.Identifier.Subject is ae49d70515d55aad9b4719d8162b43c9

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Position
Description: Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->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.Seat.Row2.Pos2.Position
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos2.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos2.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.Seat.Row2.Pos2.Position

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Position VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Position is 7c24fa880576550da14bae1e5eed26b9

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos2.Tilt
Description: Tilting of seat (seating and backrest) relative to vehicle x-axis. 0 = seat bottom is flat, seat bottom and vehicle x-axis are parallel. Positive degrees = seat tilted backwards, seat x-axis tilted upward, seat z-axis is tilted backward.
Comment: In VSS it is assumed that tilting a seat affects both seating (seat bottom) and backrest, i.e. the angle between seating and backrest will not be affected when changing Tilt.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos2 Pos2-->Tilt

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos2.Tilt VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Tilt is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos2.Tilt is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos2.Tilt is 9f95869d8b0f5d9886bef2cc664414aa

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1
Description: All seats.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1

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.Seat.Row2.Pos1

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1 is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1 is ba975a6536f15545851d27972ab1fffe

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.

3.1 - Airbag

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Airbag
Description: Airbag signals.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Airbag

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.Seat.Row2.Pos1.Airbag

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Airbag is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Airbag is ccfadedface05d54bcc00b30082b30d6

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.

3.1.1 - IsDeployed

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Airbag.IsDeployed
Description: Airbag deployment status. True = Airbag deployed. False = Airbag not deployed.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Airbag Airbag-->IsDeployed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Airbag.IsDeployed
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Airbag.IsDeployed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Airbag.IsDeployed 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.Seat.Row2.Pos1.Airbag.IsDeployed

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Airbag.IsDeployed 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.Seat.Row2.Pos1.Airbag.IsDeployed is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Airbag.IsDeployed is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Airbag.IsDeployed is fea5a0ef57385df68e486ece13546bdf

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Backrest
Description: Describes signals related to the backrest of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Backrest

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.Seat.Row2.Pos1.Backrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest is 9e8063f29cf05c1892c1b5606fd05329

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.

3.2.1 - Lumbar

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar
Description: Adjustable lumbar support mechanisms in seats allow the user to change the seat back shape.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Backrest Backrest-->Lumbar

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.Seat.Row2.Pos1.Backrest.Lumbar

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar is 363835bd81535538a10acfe914f4c3cc

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.

3.2.1.1 - Height

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Height
Description: Height of lumbar support. Position is relative within available movable range of the lumbar support. 0 = Lowermost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Backrest Backrest-->Lumbar Lumbar-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Height 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.Seat.Row2.Pos1.Backrest.Lumbar.Height

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Height VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 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.Seat.Row2.Pos1.Backrest.Lumbar.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Height is 6cdd33ee68a65349bd478c3afbc515c4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support
Description: Lumbar support (in/out position). 0 = Innermost position. 100 = Outermost position.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Backrest Backrest-->Lumbar Lumbar-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support 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.Seat.Row2.Pos1.Backrest.Lumbar.Support

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support VSS: Addressing nodes
Data type float 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Lumbar.Support is f8fd42a3227d5c6a96834becd1247f5e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline
Description: Backrest recline compared to seat z-axis (seat vertical axis). 0 degrees = Upright/Vertical backrest. Negative degrees for forward recline. Positive degrees for backward recline.
Comment: Seat z-axis depends on seat tilt. This means that movement of backrest due to seat tilting will not affect Backrest.Recline as long as the angle between Seating and Backrest are constant. Absolute recline relative to vehicle z-axis can be calculated as Tilt + Backrest.Recline.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Backrest Backrest-->Recline

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline 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.Seat.Row2.Pos1.Backrest.Recline

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest.Recline is 4e793f7e663558b29130989024763680

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster
Description: Backrest side bolster (lumbar side support) settings.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Backrest Backrest-->SideBolster

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.Seat.Row2.Pos1.Backrest.SideBolster

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster is 1484136aa6ec5a46b6f2449b9506a5dd

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.

3.2.3.1 - Support

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support
Description: Side bolster support. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Backrest Backrest-->SideBolster SideBolster-->Support

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support 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.Seat.Row2.Pos1.Backrest.SideBolster.Support

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support VSS: Addressing nodes
Data type float 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Backrest.SideBolster.Support is 87cedae0f6ba58a0940859642b89fdb0

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Headrest
Description: Headrest settings.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Headrest

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.Seat.Row2.Pos1.Headrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Headrest is d8486ab7d8195559a4e8e7baebb888ef

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.

3.3.1 - Angle

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle
Description: Headrest angle, relative to backrest, 0 degrees if parallel to backrest, Positive degrees = tilted forward.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Headrest Headrest-->Angle

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle 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.Seat.Row2.Pos1.Headrest.Angle

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Angle is 7a720646e0d657c5b10979f1c403eb4b

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Height
Description: Position of headrest relative to movable range of the head rest. 0 = Bottommost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Headrest Headrest-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Height
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Height: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Height 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.Seat.Row2.Pos1.Headrest.Height

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Height VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 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.Seat.Row2.Pos1.Headrest.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Headrest.Height is 12d45094d6c9545089e932a2462d5f68

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Heating
Description: Seat cooling / heating. 0 = off. -100 = max cold. +100 = max heat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Heating

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Heating VSS: Addressing nodes
Data type int8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value -100 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Heating is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Heating is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Heating is 0f61ef421bcd5c8dbe6a5b477cb10a49

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Height
Description: Seat position on vehicle z-axis. Position is relative within available movable range of the seating. 0 = Lowermost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Height

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Height VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Height is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Height is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Height is 6e6e7aadfd0d52d4ac877147d84540d0

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.IsBelted
Description: Is the belt engaged.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->IsBelted

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.IsBelted 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.Seat.Row2.Pos1.IsBelted is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.IsBelted is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.IsBelted is ad65078f81075a67babb66ecd2c902f7

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.IsOccupied
Description: Does the seat have a passenger in it.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->IsOccupied

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.IsOccupied 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.Seat.Row2.Pos1.IsOccupied is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.IsOccupied is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.IsOccupied is e8c5a3df63b15e8a83f0b16b6a77092f

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Massage
Description: Seat massage level. 0 = off. 100 = max massage.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Massage

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Massage 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.Seat.Row2.Pos1.Massage is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Massage is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Massage is 406607948a235d829c5da212594813b1

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Occupant
Description: Occupant data.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Occupant

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.Seat.Row2.Pos1.Occupant

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Occupant is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Occupant is e7ab950f55b45b1a985f1a9d132aad02

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.

3.9.1 - Identifier

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier
Description: Identifier attributes based on OAuth 2.0.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Occupant Occupant-->Identifier

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.Seat.Row2.Pos1.Occupant.Identifier

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier is aba17bf3b5175e56bf047839f2a0f880

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.

3.9.1.1 - Issuer

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer
Description: Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Occupant Occupant-->Identifier Identifier-->Issuer

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer 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.Seat.Row2.Pos1.Occupant.Identifier.Issuer

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Issuer is 188458a15b30577d8fb01d0f15641a6e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject
Description: Subject for the authentication of the occupant. E.g. UserID 7331677.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Occupant Occupant-->Identifier Identifier-->Subject

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject 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.Seat.Row2.Pos1.Occupant.Identifier.Subject

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Occupant.Identifier.Subject is 159e7daad966588ca48997859b811b72

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Position
Description: Seat position on vehicle x-axis. Position is relative to the frontmost position supported by the seat. 0 = Frontmost position supported.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->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.Seat.Row2.Pos1.Position
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.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.Seat.Row2.Pos1.Position

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Position VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Position is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Position is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Position is 3dd247aae2555a1ebaf76ae4017f23bb

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Seating
Description: Describes signals related to the seat bottom of the seat.
Comment: Seating is here considered as the part of the seat that supports the thighs. Additional cushions (if any) for support of lower legs is not covered by this branch.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Seating

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.Seat.Row2.Pos1.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Seating is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Seating is 8fb01973fdad529d83ebf60514cad67c

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.

3.11.1 - Length

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length
Description: Length adjustment of seating. 0 = Adjustable part of seating in rearmost position (Shortest length of seating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Seating Seating-->Length

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length
[get]  OK
Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length 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.Seat.Row2.Pos1.Seating.Length

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance
Minimum value 0 VSS: Sensors & Actuators

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Seating.Length is 9eabbf5a69cd51c88de9e70eb9545750

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch
Description: Seat switch signals
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch

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.Seat.Row2.Pos1.Switch

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch is 1c4b708222de55aabddb3697308253ee

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.

3.12.1 - Backrest

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest
Description: Describes switches related to the backrest of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest

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.Seat.Row2.Pos1.Switch.Backrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest is 4cc0b73f30e65456a6268f52ad7fee70

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.

3.12.1.1 - IsReclineBackwardEngaged

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged
Description: Backrest recline backward switch engaged (SingleSeat.Backrest.Recline).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->IsReclineBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged 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.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineBackwardEngaged is 0b5415702e0b5461afacea857c05a6fe

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged
Description: Backrest recline forward switch engaged (SingleSeat.Backrest.Recline).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->IsReclineForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged 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.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.IsReclineForwardEngaged is 1e1bbfda10e25d228e01a632277d57c3

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar
Description: Switches for SingleSeat.Backrest.Lumbar.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->Lumbar

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.Seat.Row2.Pos1.Switch.Backrest.Lumbar

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar is 4dc489e632e15d13afd6601188ed08b3

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.

3.12.1.3.1 - IsDownEngaged

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged
Description: Lumbar down switch engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged 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.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsDownEngaged is 09337347e2f557fe8649342548c7fe3c

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged
Description: Is switch for less lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged 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.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsLessSupportEngaged is 12fe41df5ab8545e8a3e7b2411585243

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged
Description: Is switch for more lumbar support engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged 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.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsMoreSupportEngaged is 73e6514d130e5bfb85d4cfb7c45d8138

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged
Description: Lumbar up switch engaged (SingleSeat.Backrest.Lumbar.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->Lumbar Lumbar-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged 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.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.Lumbar.IsUpEngaged is 47f8690805455b8c927f2834942b2ded

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster
Description: Switches for SingleSeat.Backrest.SideBolster.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->SideBolster

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.Seat.Row2.Pos1.Switch.Backrest.SideBolster

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster is 184e9cc9d42e5ec993593da10b1b8299

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.

3.12.1.4.1 - IsLessSupportEngaged

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged
Description: Is switch for less side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsLessSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged 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.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsLessSupportEngaged is f5e3fae9d90954ad9a240b72fa0a5cb4

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged
Description: Is switch for more side bolster support engaged (SingleSeat.Backrest.SideBolster.Support).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Backrest Backrest-->SideBolster SideBolster-->IsMoreSupportEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged 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.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Backrest.SideBolster.IsMoreSupportEngaged is a7dc6c8941805c47b837334abfa7abee

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest
Description: Switches for SingleSeat.Headrest.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Headrest

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.Seat.Row2.Pos1.Switch.Headrest

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest is f803a25975405ed38684b3f065535a4a

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.

3.12.2.1 - IsBackwardEngaged

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged
Description: Head rest backward switch engaged (SingleSeat.Headrest.Angle).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Headrest Headrest-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged 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.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsBackwardEngaged is 9ed038b597665225a0f2dfd262cf59b5

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged
Description: Head rest down switch engaged (SingleSeat.Headrest.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Headrest Headrest-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged 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.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsDownEngaged is 4d3d29ccfcde55f9bdf40eeeb7ecf5dc

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged
Description: Head rest forward switch engaged (SingleSeat.Headrest.Angle).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Headrest Headrest-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged 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.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsForwardEngaged is ae9cdee6019a567ebac3e85a909fe7ca

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged
Description: Head rest up switch engaged (SingleSeat.Headrest.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Headrest Headrest-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged 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.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Headrest.IsUpEngaged is f929508b3527553a959952bcd227f70e

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged
Description: Seat down switch engaged (SingleSeat.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsDownEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged 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.Seat.Row2.Pos1.Switch.IsDownEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsDownEngaged is fd41789d95035c2fa1e855d22eab80fa

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged
Description: Tilt backward switch engaged (SingleSeat.Tilt).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsTiltBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged 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.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltBackwardEngaged is 22726fefa40d5805b46b2c87e43782ed

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged
Description: Tilt forward switch engaged (SingleSeat.Tilt).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsTiltForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged 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.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsTiltForwardEngaged is f557b6a2712f5307b56577d93b9e746f

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged
Description: Seat up switch engaged (SingleSeat.Height).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsUpEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged 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.Seat.Row2.Pos1.Switch.IsUpEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsUpEngaged is 3dacf86cf185576f8a3916a315c69b1d

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage
Description: Switches for SingleSeat.Massage.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Massage

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.Seat.Row2.Pos1.Switch.Massage

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage is 4857aac12637502da76202384a151715

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.

3.12.7.1 - IsDecreaseEngaged

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged
Description: Decrease massage level switch engaged (SingleSeat.Massage).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Massage Massage-->IsDecreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged 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.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsDecreaseEngaged is d1f9e86a98be5f2ca81ac11d05356bb6

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged
Description: Increase massage level switch engaged (SingleSeat.Massage).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Massage Massage-->IsIncreaseEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged 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.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Massage.IsIncreaseEngaged is 7b656c6aa62c5156aab2d437a03bd074

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating
Description: Describes switches related to the seating of the seat.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Seating

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.Seat.Row2.Pos1.Switch.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating is 1a3e7380e61852c98eda0f38e9f807aa

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.

3.12.8.1 - IsBackwardEngaged

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged
Description: Is switch to decrease seating length engaged (SingleSeat.Seating.Length).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Seating Seating-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged 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.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsBackwardEngaged is c02ddbb0e2c1536081dae3cb23baf4b1

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged
Description: Is switch to increase seating length engaged (SingleSeat.Seating.Length).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->Seating Seating-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged 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.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.Seating.IsForwardEngaged is f0ef5926752f573ea02dacb2a242c8a1

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged
Description: Seat backward switch engaged (SingleSeat.Position).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsBackwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged 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.Seat.Row2.Pos1.Switch.IsBackwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsBackwardEngaged is 57d1ff9eaf4e5a7cbe683c13eed6e691

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged
Description: Cooler switch for Seat heater (SingleSeat.Heating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsCoolerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged 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.Seat.Row2.Pos1.Switch.IsCoolerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsCoolerEngaged is ac1a8efdbafb561bb11af807d48e8378

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged
Description: Seat forward switch engaged (SingleSeat.Position).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsForwardEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged 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.Seat.Row2.Pos1.Switch.IsForwardEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsForwardEngaged is 33ed964275af591d85773bc23d70bd68

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged
Description: Warmer switch for Seat heater (SingleSeat.Heating).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Switch Switch-->IsWarmerEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged 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.Seat.Row2.Pos1.Switch.IsWarmerEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Switch.IsWarmerEngaged is 97a36b155294512f8c409a9bc82635bc

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

Full qualified VSS Path: Vehicle.Cabin.Seat.Row2.Pos1.Tilt
Description: Tilting of seat (seating and backrest) relative to vehicle x-axis. 0 = seat bottom is flat, seat bottom and vehicle x-axis are parallel. Positive degrees = seat tilted backwards, seat x-axis tilted upward, seat z-axis is tilted backward.
Comment: In VSS it is assumed that tilting a seat affects both seating (seat bottom) and backrest, i.e. the angle between seating and backrest will not be affected when changing Tilt.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row2 Row2-->Pos1 Pos1-->Tilt

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

Path Vehicle.Cabin.Seat.Row2.Pos1.Tilt VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Tilt is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row2.Pos1.Tilt is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row2.Pos1.Tilt is c61e74d2ae795b4da2e35325f8734005

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.