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

Return to the regular view of this page.

Seating
Full qualified VSS Path: Vehicle.Cabin.Seat.Row1.DriverSide.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-->Row1 Row1-->DriverSide DriverSide-->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.Row1.DriverSide.Seating

Signal Information

The vehicle signal Vehicle.Cabin.Seat.Row1.DriverSide.Seating is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.DriverSide.Seating is 1e49fb9d59d85494b290e53b7753dd72

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 - HeatingCooling
Full qualified VSS Path: Vehicle.Cabin.Seat.Row1.DriverSide.Seating.HeatingCooling
Description: Heating or Cooling requsted for the Item. -100 = Maximum cooling, 0 = Heating/cooling deactivated, 100 = Maximum heating.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->DriverSide DriverSide-->Seating Seating-->HeatingCooling

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.Row1.DriverSide.Seating.HeatingCooling
[get]  OK
Vehicle.Cabin.Seat.Row1.DriverSide.Seating.HeatingCooling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.DriverSide.Seating.HeatingCooling 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.Row1.DriverSide.Seating.HeatingCooling

Data Type & Unit
Path Vehicle.Cabin.Seat.Row1.DriverSide.Seating.HeatingCooling 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.Row1.DriverSide.Seating.HeatingCooling is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.DriverSide.Seating.HeatingCooling is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.DriverSide.Seating.HeatingCooling is 15f9899c5ced51cc8ee9c6a828bee525

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 - IsBackwardSwitchEngaged
Full qualified VSS Path: Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsBackwardSwitchEngaged
Description: Is switch to decrease seating length engaged.
Comment: Affects the property (Seating.Length).
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->DriverSide DriverSide-->Seating Seating-->IsBackwardSwitchEngaged

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.Row1.DriverSide.Seating.IsBackwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsBackwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsBackwardSwitchEngaged 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.Row1.DriverSide.Seating.IsBackwardSwitchEngaged

Data Type & Unit
Path Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsBackwardSwitchEngaged 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.Row1.DriverSide.Seating.IsBackwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsBackwardSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsBackwardSwitchEngaged is d7d3b2f6525a5c4cacfe7ec207d9045f

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 - IsForwardSwitchEngaged
Full qualified VSS Path: Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsForwardSwitchEngaged
Description: Is switch to increase seating length engaged.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->DriverSide DriverSide-->Seating Seating-->IsForwardSwitchEngaged

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.Row1.DriverSide.Seating.IsForwardSwitchEngaged
[get]  OK
Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsForwardSwitchEngaged: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsForwardSwitchEngaged 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.Row1.DriverSide.Seating.IsForwardSwitchEngaged

Data Type & Unit
Path Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsForwardSwitchEngaged 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.Row1.DriverSide.Seating.IsForwardSwitchEngaged is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsForwardSwitchEngaged is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.DriverSide.Seating.IsForwardSwitchEngaged is 2e9746e0f95a5620bc5e0aeeeea6a897

Feedback

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

About VSS

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

Supported datatypes

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

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

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

4 - Length
Full qualified VSS Path: Vehicle.Cabin.Seat.Row1.DriverSide.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-->Row1 Row1-->DriverSide DriverSide-->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.Row1.DriverSide.Seating.Length
[get]  OK
Vehicle.Cabin.Seat.Row1.DriverSide.Seating.Length: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.DriverSide.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.Row1.DriverSide.Seating.Length

Data Type & Unit
Path Vehicle.Cabin.Seat.Row1.DriverSide.Seating.Length VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Length measured in millimeters VSS: Sensors & Actuators
Domain length
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.Row1.DriverSide.Seating.Length is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.DriverSide.Seating.Length is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.DriverSide.Seating.Length is b030abb632dc503aa313ba5c75ba36f1

Feedback

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

About VSS

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

Supported datatypes

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

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

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

5 - SideBolsterSupportLeft
Full qualified VSS Path: Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportLeft
Description: Seat bottom side bolster support left. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->DriverSide DriverSide-->Seating Seating-->SideBolsterSupportLeft

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.Row1.DriverSide.Seating.SideBolsterSupportLeft
[get]  OK
Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportLeft: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportLeft 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.Row1.DriverSide.Seating.SideBolsterSupportLeft

Data Type & Unit
Path Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportLeft 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.Row1.DriverSide.Seating.SideBolsterSupportLeft is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportLeft is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportLeft is d67eb6e1780a5d71a0de6da945520b81

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.

6 - SideBolsterSupportRight
Full qualified VSS Path: Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportRight
Description: Seat bottom side bolster support right. 0 = Minimum support (widest side bolster setting). 100 = Maximum support.
flowchart LR Vehicle-->Cabin Cabin-->Seat Seat-->Row1 Row1-->DriverSide DriverSide-->Seating Seating-->SideBolsterSupportRight

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.Row1.DriverSide.Seating.SideBolsterSupportRight
[get]  OK
Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportRight: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportRight 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.Row1.DriverSide.Seating.SideBolsterSupportRight

Data Type & Unit
Path Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportRight 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.Row1.DriverSide.Seating.SideBolsterSupportRight is an Actuator.

The vehicle signal Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportRight is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Seat.Row1.DriverSide.Seating.SideBolsterSupportRight is ac17b65e74a0555b83b589da4a083538

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.