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

Return to the regular view of this page.

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.

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