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

Return to the regular view of this page.

RangeExtender
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender
Description: Extended Range Electric Vehicle (EREV) specific data.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender is d97d2b08f45e57e19d47fa79fec06205

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 - ChargeDepleting
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.ChargeDepleting
Description: Signals related to Charge Depleting (CD) mode operation.
Comment: CD mode represents the electric-only or electric-primary operation of the EREV. During this mode, the vehicle maximizes the use of battery energy before the engine is engaged.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeDepleting

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.RangeExtender.ChargeDepleting

Signal Information

The vehicle signal Vehicle.Powertrain.RangeExtender.ChargeDepleting is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.ChargeDepleting is 78babe2c3695514d86e6c735d4002e77

Children

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

Feedback

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

About VSS

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

1.1 - EnergyConsumption
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption
Description: Current electric energy consumption rate during Charge Depleting mode operation.
Comment: This value represents the instantaneous or short-term average electric energy consumption while the vehicle is operating in CD mode. It is calculated based on the electrical energy drawn from the traction battery per distance traveled. This metric is analogous to fuel consumption but measured in electrical energy units. A lower value indicates more efficient electric operation.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeDepleting ChargeDepleting-->EnergyConsumption

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption VSS: Addressing nodes
Data type float VSS: Datatypes
Unit kWh/100km VSS: Units
Label kilowatt hours per 100 kilometers
Description Energy consumption per distance measured in kilowatt hours per 100 kilometers VSS: Sensors & Actuators
Domain energy-consumption-per-distance

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.RangeExtender.ChargeDepleting.EnergyConsumption is a Sensor.

The vehicle signal Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption is bf36188dfa285cf3aa2acf0156933c5c

Feedback

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

About VSS

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

Supported datatypes

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

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

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

1.2 - Range
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range
Description: Estimated remaining distance that can be traveled in Charge Depleting mode using available battery energy.
Comment: This range estimate is calculated based on the current battery state of charge and the recent energy consumption patterns in CD mode. The estimate may vary based on driving conditions, terrain, climate control usage, and other factors affecting battery consumption. When this range approaches zero, the vehicle will typically transition to Charge Sustaining mode.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeDepleting ChargeDepleting-->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.RangeExtender.ChargeDepleting.Range
[get]  OK
Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.ChargeDepleting.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.RangeExtender.ChargeDepleting.Range

Data Type & Unit
Path Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range VSS: Addressing nodes
Data type uint32 VSS: Datatypes
Unit m VSS: Units
Label meter
Description Length measured in meters VSS: Sensors & Actuators
Domain length

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.RangeExtender.ChargeDepleting.Range is a Sensor.

The vehicle signal Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range is ce970150781f51699673cfce2ebea639

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 - ChargeSustaining
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.ChargeSustaining
Description: Signals related to Charge Sustaining (CS) mode operation.
Comment: CS mode represents the range-extended operation where the internal combustion engine operates as a generator to maintain battery charge and provide extended driving range. During this mode, fuel consumption becomes the primary energy source metric.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeSustaining

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.RangeExtender.ChargeSustaining

Signal Information

The vehicle signal Vehicle.Powertrain.RangeExtender.ChargeSustaining is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.ChargeSustaining is b5d8945c8f8c54fbb15a1aca578ad70a

Children

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

Feedback

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

About VSS

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

2.1 - FuelEconomy
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy
Description: Current fuel economy during Charge Sustaining mode operation.
Comment: This value represents the fuel efficiency when the engine is operating as a generator to maintain battery charge. It differs from conventional vehicle fuel economy because the engine is optimized to run at efficient generator speeds rather than varying speeds for direct wheel propulsion. The actual fuel economy in CS mode may be different from the vehicle’s rated CS mode fuel economy depending on driving conditions and power demands.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeSustaining ChargeSustaining-->FuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy VSS: Addressing nodes
Data type float VSS: Datatypes
Unit km/l VSS: Units
Label kilometers per liter
Description Distance per volume measured in kilometers per liter VSS: Sensors & Actuators
Domain distance-per-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.RangeExtender.ChargeSustaining.FuelEconomy is a Sensor.

The vehicle signal Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy is b1cca487316a507faf2dbc371ca295ff

Feedback

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

About VSS

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

Supported datatypes

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

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

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

2.2 - Range
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range
Description: Estimated remaining distance that can be traveled in Charge Sustaining mode using available fuel.
Comment: This range estimate is calculated based on the current fuel level and recent fuel consumption patterns in CS mode. It represents the extended range capability provided by the internal combustion engine. The total vehicle range is the sum of CD mode range and CS mode range.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeSustaining ChargeSustaining-->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.RangeExtender.ChargeSustaining.Range
[get]  OK
Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.ChargeSustaining.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.RangeExtender.ChargeSustaining.Range

Data Type & Unit
Path Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range VSS: Addressing nodes
Data type uint32 VSS: Datatypes
Unit m VSS: Units
Label meter
Description Length measured in meters VSS: Sensors & Actuators
Domain length

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.RangeExtender.ChargeSustaining.Range is a Sensor.

The vehicle signal Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range is cb5d446b2cf25fc795e490be0ef4c35c

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 - CombinedFuelEconomy
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy
Description: Combined fuel economy equivalent that accounts for both electric energy and fuel consumption.
Comment: This metric provides a unified measure of overall vehicle efficiency by converting electric energy consumption to a fuel-equivalent value and combining it with actual fuel consumption. The calculation typically follows regulatory standards (such as EPA MPGe) that define the equivalence between electrical energy and liquid fuel energy. For example, EPA defines 33.7 kWh as equivalent to one gallon of gasoline. This combined metric is useful for comparing EREV efficiency with conventional vehicles and understanding the overall energy cost of operation. The value is weighted based on the proportion of driving in CD versus CS modes.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->CombinedFuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy VSS: Addressing nodes
Data type float VSS: Datatypes
Unit km/l VSS: Units
Label kilometers per liter
Description Distance per volume measured in kilometers per liter VSS: Sensors & Actuators
Domain distance-per-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.RangeExtender.CombinedFuelEconomy is a Sensor.

The vehicle signal Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy is 5844045f06595086936bb104347e768a

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 - OperatingMode
Full qualified VSS Path: Vehicle.Powertrain.RangeExtender.OperatingMode
Description: Current operating mode of the Extended Range Electric Vehicle.
Comment: CHARGE_DEPLETING (CD) - Vehicle operates primarily on battery power, battery SOC decreases. CHARGE_SUSTAINING (CS) - Engine operates as generator to maintain battery charge level. BLENDED - Both battery and engine are used simultaneously, typically during high power demands. The mode transition typically occurs automatically based on battery state of charge thresholds.
flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->OperatingMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.RangeExtender.OperatingMode VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['CHARGE_DEPLETING', 'CHARGE_SUSTAINING', 'BLENDED'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.RangeExtender.OperatingMode is a Sensor.

The vehicle signal Vehicle.Powertrain.RangeExtender.OperatingMode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender.OperatingMode is 107067e6a3405a6484adeca2651211f1

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.