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

Return to the regular view of this page.

ChargeCurrent
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent
Description: Current charging current.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeCurrent

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

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent is 94739cf563735b438878ac0f85601f27

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 - DC
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.DC
Description: Current DC charging current at inlet. Negative if returning energy to grid.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeCurrent ChargeCurrent-->DC

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.Charging.ChargeCurrent.DC
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.DC: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.DC 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.Charging.ChargeCurrent.DC

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.DC VSS: Addressing nodes
Data type float VSS: Datatypes
Unit A VSS: Units
Label ampere
Description Electric current measured in amperes VSS: Sensors & Actuators
Domain electric current

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.Charging.ChargeCurrent.DC is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.DC is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.DC is 44204d7ae6fd5f8e954d0670a739bdf2

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 - Phase1
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase1
Description: Current AC charging current (rms) at inlet for Phase 1. Negative if returning energy to grid.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeCurrent ChargeCurrent-->Phase1

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.Charging.ChargeCurrent.Phase1
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase1: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase1 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.Charging.ChargeCurrent.Phase1

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase1 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit A VSS: Units
Label ampere
Description Electric current measured in amperes VSS: Sensors & Actuators
Domain electric current

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.Charging.ChargeCurrent.Phase1 is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase1 is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase1 is 400dca50fcde52a6bb605d7e86f49776

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 - Phase2
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase2
Description: Current AC charging current (rms) at inlet for Phase 2. Negative if returning energy to grid.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeCurrent ChargeCurrent-->Phase2

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.Charging.ChargeCurrent.Phase2
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase2: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase2 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.Charging.ChargeCurrent.Phase2

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase2 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit A VSS: Units
Label ampere
Description Electric current measured in amperes VSS: Sensors & Actuators
Domain electric current

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.Charging.ChargeCurrent.Phase2 is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase2 is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase2 is 32cb24d1c495503a9087d6f55997cf57

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 - Phase3
Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase3
Description: Current AC charging current (rms) at inlet for Phase 3. Negative if returning energy to grid.
flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeCurrent ChargeCurrent-->Phase3

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.Charging.ChargeCurrent.Phase3
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase3: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase3 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.Charging.ChargeCurrent.Phase3

Data Type & Unit
Path Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase3 VSS: Addressing nodes
Data type float VSS: Datatypes
Unit A VSS: Units
Label ampere
Description Electric current measured in amperes VSS: Sensors & Actuators
Domain electric current

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.Charging.ChargeCurrent.Phase3 is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase3 is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase3 is 55fb7fb7ff4a5df9b6a3af435eac868e

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.