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

Return to the regular view of this page.

FuelSystem
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem
Description: Fuel system data.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem

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

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem is dbc194a7f97d5a56bc8942c17c2db22e

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 - AverageConsumption
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.AverageConsumption
Description: Average consumption in liters per 100 km.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->AverageConsumption

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.AverageConsumption
[get]  OK
Vehicle.Powertrain.FuelSystem.AverageConsumption: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.AverageConsumption 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.Powertrain.FuelSystem.AverageConsumption

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.AverageConsumption VSS: Addressing nodes
Data type float VSS: Datatypes
Unit l/100km VSS: Units
Label liter per 100 kilometers
Description Volume per distance measured in liters per 100 kilometers VSS: Sensors & Actuators
Domain volume per distance
Minimum value 0 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.Powertrain.FuelSystem.AverageConsumption is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.AverageConsumption is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.AverageConsumption is e2252108125a54dcab34e1bad0fe8bdc

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 - ConsumptionSinceStart
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart
Description: Fuel amount in liters consumed since start of current trip.
Comment: A new trip is considered to start when engine gets enabled (e.g. LowVoltageSystemState in ON or START mode). A trip is considered to end when engine is no longer enabled. The signal may however keep the value of the last trip until a new trip is started.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->ConsumptionSinceStart

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart
[get]  OK
Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart 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.Powertrain.FuelSystem.ConsumptionSinceStart

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart VSS: Addressing nodes
Data type float VSS: Datatypes
Unit l VSS: Units
Label liter
Description Volume measured in liters VSS: Sensors & Actuators
Domain volume

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.Powertrain.FuelSystem.ConsumptionSinceStart is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart is adf0a40964ff556f92b10275ad918883

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 - HybridType
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.HybridType
Description: Defines the hybrid type of the vehicle.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->HybridType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.HybridType
[get]  OK
Vehicle.Powertrain.FuelSystem.HybridType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.HybridType UNKNOWN
[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.Powertrain.FuelSystem.HybridType

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.HybridType VSS: Addressing nodes
Data type string VSS: Datatypes
Default value UNKNOWN VSS: Sensors & Actuators
Allowed values ['UNKNOWN', 'NOT_APPLICABLE', 'STOP_START', 'BELT_ISG', 'CIMG', 'PHEV'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.HybridType is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.HybridType is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.HybridType is f0f72012f5e453c1935ff8c3a5aff696

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 - InstantConsumption
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.InstantConsumption
Description: Current consumption in liters per 100 km.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->InstantConsumption

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.InstantConsumption
[get]  OK
Vehicle.Powertrain.FuelSystem.InstantConsumption: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.InstantConsumption 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.Powertrain.FuelSystem.InstantConsumption

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.InstantConsumption VSS: Addressing nodes
Data type float VSS: Datatypes
Unit l/100km VSS: Units
Label liter per 100 kilometers
Description Volume per distance measured in liters per 100 kilometers VSS: Sensors & Actuators
Domain volume per distance
Minimum value 0 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.Powertrain.FuelSystem.InstantConsumption is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.InstantConsumption is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.InstantConsumption is cf65767ec8ad56ffadfdccd831e4b562

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 - IsEngineStopStartEnabled
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled
Description: Indicates whether eco start stop is currently enabled.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->IsEngineStopStartEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled
[get]  OK
Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled 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.Powertrain.FuelSystem.IsEngineStopStartEnabled

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled 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.Powertrain.FuelSystem.IsEngineStopStartEnabled is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled is 176eed5bb0da582a9ee56f1c70e12075

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 - IsFuelLevelLow
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.IsFuelLevelLow
Description: Indicates that the fuel level is low (e.g. <50km range).
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->IsFuelLevelLow

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.IsFuelLevelLow
[get]  OK
Vehicle.Powertrain.FuelSystem.IsFuelLevelLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.IsFuelLevelLow 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.Powertrain.FuelSystem.IsFuelLevelLow

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.IsFuelLevelLow 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.Powertrain.FuelSystem.IsFuelLevelLow is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.IsFuelLevelLow is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.IsFuelLevelLow is 65f18ee3b04f5d4c8bb76083227dd9fe

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 - Level
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.Level
Description: Level in fuel tank as percent of capacity. 0 = empty. 100 = full.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->Level

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.Level
[get]  OK
Vehicle.Powertrain.FuelSystem.Level: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.Level 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.Powertrain.FuelSystem.Level

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.Level 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.Powertrain.FuelSystem.Level is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.Level is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.Level is 902bd295a662573088291e8b6a6b7943

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 - Range
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.Range
Description: Remaining range in meters using only liquid fuel.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->Range

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.Range
[get]  OK
Vehicle.Powertrain.FuelSystem.Range: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.Range 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.Powertrain.FuelSystem.Range

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.Range VSS: Addressing nodes
Data type uint32 VSS: Datatypes
Unit m VSS: Units
Label meter
Description Distance measured in meters VSS: Sensors & Actuators
Domain distance

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.Range is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.Range is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.Range is c5a0dbe5e754553897f0aed0069af57a

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 - SupportedFuel
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.SupportedFuel
Description: Detailed information on fuels supported by the vehicle. Identifiers originating from DIN EN 16942:2021-08, appendix B, with additional suffix for octane (RON) where relevant.
Comment: RON 95 is sometimes referred to as Super, RON 98 as Super Plus.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->SupportedFuel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.SupportedFuel
[get]  OK
Vehicle.Powertrain.FuelSystem.SupportedFuel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.SupportedFuel 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.Powertrain.FuelSystem.SupportedFuel

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.SupportedFuel VSS: Addressing nodes
Data type string[] VSS: Datatypes
Allowed values ['E5_95', 'E5_98', 'E10_95', 'E10_98', 'E85', 'B7', 'B10', 'B20', 'B30', 'B100', 'XTL', 'LPG', 'CNG', 'LNG', 'H2', 'OTHER'] VSS: Specifying allowed values

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuel is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuel is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.SupportedFuel is 7fd3bf2ef0c650e69ff2037875ec59ee

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 - SupportedFuelTypes
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.SupportedFuelTypes
Description: High level information of fuel types supported
Comment: If a vehicle also has an electric drivetrain (e.g. hybrid) that will be obvious from the PowerTrain.Type signal.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->SupportedFuelTypes

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.SupportedFuelTypes
[get]  OK
Vehicle.Powertrain.FuelSystem.SupportedFuelTypes: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.SupportedFuelTypes 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.Powertrain.FuelSystem.SupportedFuelTypes

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.SupportedFuelTypes VSS: Addressing nodes
Data type string[] VSS: Datatypes
Allowed values ['GASOLINE', 'DIESEL', 'E85', 'LPG', 'CNG', 'LNG', 'H2', 'OTHER'] VSS: Specifying allowed values

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuelTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuelTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.SupportedFuelTypes is 80edc3002aa25097aba6455fe459fa6c

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 - TankCapacity
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.TankCapacity
Description: Capacity of the fuel tank in liters.
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->TankCapacity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.TankCapacity
[get]  OK
Vehicle.Powertrain.FuelSystem.TankCapacity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.TankCapacity 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.Powertrain.FuelSystem.TankCapacity

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.TankCapacity VSS: Addressing nodes
Data type float VSS: Datatypes
Unit l VSS: Units
Label liter
Description Volume measured in liters VSS: Sensors & Actuators
Domain volume

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.Powertrain.FuelSystem.TankCapacity is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.TankCapacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.TankCapacity is 362643b866c55d5386fdbdf383464e90

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 - TimeSinceStart
Full qualified VSS Path: Vehicle.Powertrain.FuelSystem.TimeSinceStart
Description: Time in seconds elapsed since start of current trip.
Deprecation V3.1 replaced by Vehicle.StartTime and Vehicle.TripDuration
flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->TimeSinceStart

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.FuelSystem.TimeSinceStart
[get]  OK
Vehicle.Powertrain.FuelSystem.TimeSinceStart: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.FuelSystem.TimeSinceStart 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.Powertrain.FuelSystem.TimeSinceStart

Data Type & Unit
Path Vehicle.Powertrain.FuelSystem.TimeSinceStart VSS: Addressing nodes
Data type uint32 VSS: Datatypes
Unit s VSS: Units
Label second
Description Time measured in seconds VSS: Sensors & Actuators
Domain time

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.TimeSinceStart is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.TimeSinceStart is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.TimeSinceStart is 1a8dbc5107b3522fad852e63aa85aef9

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.