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

Return to the regular view of this page.

BatteryConditioning
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.BatteryConditioning
Description: Properties related to preparing the vehicle battery for charging or driving.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning

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

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.BatteryConditioning is 3da3ed2e9690563da6000ca209af4a79

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 - IsActive
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive
Description: Indicates if battery conditioning is active (i.e. actively monitors battery temperature). True = Active. False = Inactive.
Comment: This signal is typically true when mode is not INACTIVE and time is within defined start/end times.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->IsActive

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive 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.TractionBattery.BatteryConditioning.IsActive is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive is 4961a0339cb35bedaa2fe94dc9e02080

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 - IsOngoing
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing
Description: Indicating if battery conditioning is currently ongoing. Battery conditioning is considered ongoing when the battery conditioning system is actively heating or cooling the battery, or requesting heating or cooling.
Comment: When battery conditioning is active, but temperature is already within acceptable range so that no cooling or heating is needed then IsOngoing shall report False.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->IsOngoing

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing 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.TractionBattery.BatteryConditioning.IsOngoing is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing is 7a8a4cb07bce52978e3636ca5c1fb7d2

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 - RequestedMode
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode
Description: Defines requested mode for battery conditioning. INACTIVE - Battery conditioning inactive. FAST_CHARGING_PREPARATION - Battery conditioning for fast charging. DRIVING_PREPARATION - Battery conditioning for driving.
Comment: The Mode and TargetTime can be used to calculate TargetTemperature and StartTime
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->RequestedMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['INACTIVE', 'FAST_CHARGING_PREPARATION', 'DRIVING_PREPARATION'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode is 2cce7f31c670560d89502a20f2abb8f3

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 - StartTime
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime
Description: Start time for battery conditioning, formatted according to ISO 8601 with UTC time zone.
Comment: If the vehicle is asleep, this is the time the vehicle and the battery conditioning system must wake up and start monitoring the battery and if necessary start heating/cooling of the battery.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->StartTime

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime 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.Powertrain.TractionBattery.BatteryConditioning.StartTime is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime is 72049c2761f3515080014ab719709395

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 - TargetTemperature
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature
Description: Target temperature for battery conditioning.
Comment: Target temperature possibly differs between different modes as well as other factors. Allowed deviation from target temperature is implementation dependent.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->TargetTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature VSS: Addressing nodes
Data type float VSS: Datatypes
Unit Celsius VSS: Units
Label degree Celsius
Description Temperature measured in degree Celsius VSS: Sensors & Actuators
Domain temperature

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.TractionBattery.BatteryConditioning.TargetTemperature is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature is 31798b409f2f5e65b868b9583442a479

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 - TargetTime
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime
Description: Target time when conditioning shall be finished, formatted according to ISO 8601 with UTC time zone.
Comment: For FAST_CHARGING mode this is typically the time when charging is supposed to start. For DRIVING mode this is typically the expected departure time. Battery conditioning will be deactivated when this time has passed.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->TargetTime

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime 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.Powertrain.TractionBattery.BatteryConditioning.TargetTime is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime is f66fc3a45f25537da2ea2d210664844b

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.