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

Return to the regular view of this page.

HMI
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI
Description: HMI related signals
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI

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

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI is a Branch.

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 - Brightness
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.Brightness
Description: Brightness of the HMI, relative to supported range. 0 = Lowest brightness possible. 100 = Maximum Brightness possible.
Comment: The value 0 does not necessarily correspond to a turned off HMI, as it may not be allowed/supported to turn off the HMI completely.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->Brightness

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.Brightness
[get]  OK
Vehicle.Cabin.Infotainment.HMI.Brightness: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.Brightness 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.Infotainment.HMI.Brightness

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.Brightness 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.Infotainment.HMI.Brightness is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.Brightness is a Signal.

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 - DateFormat
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.DateFormat
Description: Date format used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->DateFormat

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.DateFormat
[get]  OK
Vehicle.Cabin.Infotainment.HMI.DateFormat: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.DateFormat 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.Infotainment.HMI.DateFormat

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.DateFormat VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['YYYY_MM_DD', 'DD_MM_YYYY', 'MM_DD_YYYY', 'YY_MM_DD', 'DD_MM_YY', 'MM_DD_YY'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.DateFormat is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.DateFormat is a Signal.

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 - DayNightMode
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.DayNightMode
Description: Current display theme
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->DayNightMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.DayNightMode
[get]  OK
Vehicle.Cabin.Infotainment.HMI.DayNightMode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.DayNightMode 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.Infotainment.HMI.DayNightMode

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.DayNightMode VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['DAY', 'NIGHT'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.DayNightMode is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.DayNightMode is a Signal.

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 - DisplayOffDuration
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.DisplayOffDuration
Description: Duration in seconds before the display is turned off. Value shall be 0 if screen never shall turn off.
Comment: Display shall be turned off at HMI.LastActionTime + HMI.DisplayOffDuration, unless HMI.IsScreenAlwaysOn==True.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->DisplayOffDuration

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.DisplayOffDuration
[get]  OK
Vehicle.Cabin.Infotainment.HMI.DisplayOffDuration: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.DisplayOffDuration 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.Infotainment.HMI.DisplayOffDuration

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.DisplayOffDuration VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit s VSS: Units
Label second
Description Duration measured in seconds VSS: Sensors & Actuators
Domain duration

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.Infotainment.HMI.DisplayOffDuration is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.DisplayOffDuration is a Signal.

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 - DistanceUnit
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.DistanceUnit
Description: Distance unit used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->DistanceUnit

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.DistanceUnit
[get]  OK
Vehicle.Cabin.Infotainment.HMI.DistanceUnit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.DistanceUnit 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.Infotainment.HMI.DistanceUnit

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.DistanceUnit VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['MILES', 'KILOMETERS'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.DistanceUnit is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.DistanceUnit is a Signal.

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 - EVEconomyUnits
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.EVEconomyUnits
Description: EV fuel economy unit used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->EVEconomyUnits

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.EVEconomyUnits
[get]  OK
Vehicle.Cabin.Infotainment.HMI.EVEconomyUnits: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.EVEconomyUnits 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.Infotainment.HMI.EVEconomyUnits

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.EVEconomyUnits VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['MILES_PER_KILOWATT_HOUR', 'KILOMETERS_PER_KILOWATT_HOUR', 'KILOWATT_HOURS_PER_100_MILES', 'KILOWATT_HOURS_PER_100_KILOMETERS', 'WATT_HOURS_PER_MILE', 'WATT_HOURS_PER_KILOMETER'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.EVEconomyUnits is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.EVEconomyUnits is a Signal.

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.

7 - EVEnergyUnits
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.EVEnergyUnits
Description: EV energy unit used in the current HMI
Comment: Ampere hours is by definition not an energy unit, but can be used as a measurement of energy if the voltage, like nominal voltage of the battery, is known.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->EVEnergyUnits

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.EVEnergyUnits
[get]  OK
Vehicle.Cabin.Infotainment.HMI.EVEnergyUnits: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.EVEnergyUnits 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.Infotainment.HMI.EVEnergyUnits

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.EVEnergyUnits VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['WATT_HOURS', 'AMPERE_HOURS', 'KILOWATT_HOURS'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.EVEnergyUnits is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.EVEnergyUnits is a Signal.

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.

8 - FontSize
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.FontSize
Description: Font size used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->FontSize

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.FontSize
[get]  OK
Vehicle.Cabin.Infotainment.HMI.FontSize: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.FontSize 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.Infotainment.HMI.FontSize

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.FontSize VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['STANDARD', 'LARGE', 'EXTRA_LARGE'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.FontSize is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.FontSize is a Signal.

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.

9 - FuelEconomyUnits
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.FuelEconomyUnits
Description: Fuel economy unit used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->FuelEconomyUnits

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.FuelEconomyUnits
[get]  OK
Vehicle.Cabin.Infotainment.HMI.FuelEconomyUnits: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.FuelEconomyUnits 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.Infotainment.HMI.FuelEconomyUnits

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.FuelEconomyUnits VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['MPG_UK', 'MPG_US', 'MILES_PER_LITER', 'KILOMETERS_PER_LITER', 'LITERS_PER_100_KILOMETERS'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.FuelEconomyUnits is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.FuelEconomyUnits is a Signal.

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.

10 - FuelVolumeUnit
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.FuelVolumeUnit
Description: Fuel volume unit used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->FuelVolumeUnit

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.FuelVolumeUnit
[get]  OK
Vehicle.Cabin.Infotainment.HMI.FuelVolumeUnit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.FuelVolumeUnit 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.Infotainment.HMI.FuelVolumeUnit

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.FuelVolumeUnit VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['LITER', 'GALLON_US', 'GALLON_UK'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.FuelVolumeUnit is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.FuelVolumeUnit is a Signal.

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.

11 - IsScreenAlwaysOn
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.IsScreenAlwaysOn
Description: Used to prevent the screen going black if no action placed.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->IsScreenAlwaysOn

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.IsScreenAlwaysOn
[get]  OK
Vehicle.Cabin.Infotainment.HMI.IsScreenAlwaysOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.IsScreenAlwaysOn 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.Infotainment.HMI.IsScreenAlwaysOn

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.IsScreenAlwaysOn 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.Infotainment.HMI.IsScreenAlwaysOn is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.IsScreenAlwaysOn is a Signal.

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.

12 - LastActionTime
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.LastActionTime
Description: Time for last hmi action, formatted according to ISO 8601 with UTC time zone.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->LastActionTime

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.LastActionTime
[get]  OK
Vehicle.Cabin.Infotainment.HMI.LastActionTime: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.LastActionTime 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.Infotainment.HMI.LastActionTime

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.LastActionTime VSS: Addressing nodes
Data type string VSS: Datatypes
Unit iso8601 VSS: Units
Label ISO 8601
Description Date and Time expressed as a string according to ISO 8601 VSS: Sensors & Actuators
Domain datetime

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.LastActionTime is a Sensor.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.LastActionTime is a Signal.

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.

13 - SpeedUnit
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.SpeedUnit
Description: Speed unit used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->SpeedUnit

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.SpeedUnit
[get]  OK
Vehicle.Cabin.Infotainment.HMI.SpeedUnit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.SpeedUnit 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.Infotainment.HMI.SpeedUnit

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.SpeedUnit VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['METERS_PER_SECOND', 'MILES_PER_HOUR', 'KILOMETERS_PER_HOUR'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.SpeedUnit is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.SpeedUnit is a Signal.

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.

14 - TemperatureUnit
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.TemperatureUnit
Description: Temperature unit used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->TemperatureUnit

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.TemperatureUnit
[get]  OK
Vehicle.Cabin.Infotainment.HMI.TemperatureUnit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.TemperatureUnit 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.Infotainment.HMI.TemperatureUnit

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.TemperatureUnit VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['C', 'F'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.TemperatureUnit is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.TemperatureUnit is a Signal.

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.

15 - TimeFormat
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.TimeFormat
Description: Time format used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->TimeFormat

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.TimeFormat
[get]  OK
Vehicle.Cabin.Infotainment.HMI.TimeFormat: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.TimeFormat 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.Infotainment.HMI.TimeFormat

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.TimeFormat VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['HR_12', 'HR_24'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.TimeFormat is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.TimeFormat is a Signal.

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.

16 - TirePressureUnit
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.TirePressureUnit
Description: Tire pressure unit used in the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->TirePressureUnit

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.TirePressureUnit
[get]  OK
Vehicle.Cabin.Infotainment.HMI.TirePressureUnit: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.TirePressureUnit 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.Infotainment.HMI.TirePressureUnit

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.TirePressureUnit VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['PSI', 'KPA', 'BAR'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.TirePressureUnit is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.TirePressureUnit is a Signal.

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.

17 - CurrentLanguage
Full qualified VSS Path: Vehicle.Cabin.Infotainment.HMI.CurrentLanguage
Description: ISO 639-1 standard language code for the current HMI
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->HMI HMI-->CurrentLanguage

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.HMI.CurrentLanguage
[get]  OK
Vehicle.Cabin.Infotainment.HMI.CurrentLanguage: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.HMI.CurrentLanguage 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.Infotainment.HMI.CurrentLanguage

Data Type & Unit
Path Vehicle.Cabin.Infotainment.HMI.CurrentLanguage VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.HMI.CurrentLanguage is a Sensor.

The vehicle signal Vehicle.Cabin.Infotainment.HMI.CurrentLanguage is a Signal.

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.