Vehicle.Powertrain.TractionBattery.AccumulatedChargedEnergy (The accumulated energy delivered to the battery during charging over lifetime of the battery.)
Vehicle.Powertrain.TractionBattery.AccumulatedChargedThroughput (The accumulated charge throughput delivered to the battery during charging over lifetime of the battery.)
Vehicle.Powertrain.TractionBattery.AccumulatedConsumedEnergy (The accumulated energy leaving HV battery for propulsion and auxiliary loads over lifetime of the battery.)
Vehicle.Powertrain.TractionBattery.AccumulatedConsumedThroughput (The accumulated charge throughput leaving HV battery for propulsion and auxiliary loads over lifetime of the battery.)
Vehicle.Powertrain.TractionBattery.Charging (Properties related to battery charging.)
Vehicle.Powertrain.TractionBattery.CurrentCurrent (Current current flowing in/out of battery. Positive = Current flowing in to battery, e.g. during charging. Negative = Current flowing out of battery, e.g. during driving.)
Vehicle.Powertrain.TractionBattery.CurrentPower (Current electrical energy flowing in/out of battery. Positive = Energy flowing in to battery, e.g. during charging. Negative = Energy flowing out of battery, e.g. during driving.)
Vehicle.Powertrain.TractionBattery.CurrentVoltage (Current Voltage of the battery.)
Vehicle.Powertrain.TractionBattery.DCDC (Properties related to DC/DC converter converting high voltage (from high voltage battery) to vehicle low voltage (supply voltage, typically 12 Volts).)
Vehicle.Powertrain.TractionBattery.GrossCapacity (Gross capacity of the battery.)
Vehicle.Powertrain.TractionBattery.Id (Battery Identification Number as assigned by OEM.)
Vehicle.Powertrain.TractionBattery.IsGroundConnected (Indicating if the ground (negative terminator) of the traction battery is connected to the powertrain.)
Vehicle.Powertrain.TractionBattery.IsPowerConnected (Indicating if the power (positive terminator) of the traction battery is connected to the powertrain.)
Vehicle.Powertrain.TractionBattery.MaxVoltage (Max allowed voltage of the battery, e.g. during charging.)
Vehicle.Powertrain.TractionBattery.NetCapacity (Total net capacity of the battery considering aging.)
Vehicle.Powertrain.TractionBattery.NominalVoltage (Nominal Voltage of the battery.)
Vehicle.Powertrain.TractionBattery.PowerLoss (Electrical energy lost by power dissipation to heat inside the battery.)
Vehicle.Powertrain.TractionBattery.ProductionDate (Production date of battery in ISO8601 format, e.g. YYYY-MM-DD.)
Vehicle.Powertrain.TractionBattery.Range (Remaining range in meters using only battery.)
Vehicle.Powertrain.TractionBattery.StateOfCharge (Information on the state of charge of the vehicle’s high voltage battery.)
Vehicle.Powertrain.TractionBattery.StateOfHealth (Calculated battery state of health at standard conditions.)
Vehicle.Powertrain.TractionBattery.Temperature (Temperature Information for the battery pack.)

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.DCDC`
Description:	Properties related to DC/DC converter converting high voltage (from high voltage battery) to vehicle low voltage (supply voltage, typically 12 Volts).

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->DCDC

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.DCDC is 01f4943795b55cbd8f94e1bca137fc0a

Children

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

Vehicle.Powertrain.TractionBattery.DCDC.PowerLoss (Electrical energy lost by power dissipation to heat inside DC/DC converter.)
Vehicle.Powertrain.TractionBattery.DCDC.Temperature (Current temperature of DC/DC converter converting battery high voltage to vehicle low voltage (typically 12 Volts).)

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.DCDC.PowerLoss`
Description:	Electrical energy lost by power dissipation to heat inside DC/DC converter.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->DCDC DCDC-->PowerLoss

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.DCDC.PowerLoss`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`W`	VSS: Units
Label	watt
Description	Power measured in watts	VSS: Sensors & Actuators
Domain	power

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.DCDC.PowerLoss is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.DCDC.PowerLoss is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.DCDC.PowerLoss is f29e37087cdf57ca998188c7b945a77b

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

1.2 - Temperature


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.DCDC.Temperature`
Description:	Current temperature of DC/DC converter converting battery high voltage to vehicle low voltage (typically 12 Volts).

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->DCDC DCDC-->Temperature

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.DCDC.Temperature`	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.DCDC.Temperature is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.DCDC.Temperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.DCDC.Temperature is 4e587c3af2aa5fbb9205e42a64fc8d77

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

2 - Charging


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging`
Description:	Properties related to battery charging.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging is 49b9ef0c8b145a36afdf17d0cb44131b

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent (Current charging current.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeLimit (Target charge limit (state of charge) for battery.)
Vehicle.Powertrain.TractionBattery.Charging.ChargePlugType (Type of charge plug (charging inlet) available on the vehicle. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)
Vehicle.Powertrain.TractionBattery.Charging.ChargePortFlap (Status of the charge port cover, can potentially be controlled manually.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeRate (Current charging rate, as in kilometers of range added per hour.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage (Current charging voltage, as measured at the charging inlet.)
Vehicle.Powertrain.TractionBattery.Charging.IsCharging (True if charging is ongoing. Charging is considered to be ongoing if energy is flowing from charger to vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableConnected (Indicates if a charging cable is physically connected to the vehicle or not.)
Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.IsDischarging (True if discharging (vehicle to grid) is ongoing. Discharging is considered to be ongoing if energy is flowing from vehicle to charger/grid.)
Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent (Maximum charging current that can be accepted by the system, as measured at the charging inlet.)
Vehicle.Powertrain.TractionBattery.Charging.Mode (Control of the charge process. MANUAL means manually initiated (plug-in event, companion app, etc). TIMER means timer-based. GRID means grid-controlled (eg ISO 15118). PROFILE means controlled by profile download to vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.PowerLoss (Electrical energy lost by power dissipation to heat inside the AC/DC converter.)
Vehicle.Powertrain.TractionBattery.Charging.StartStopCharging (Start or stop the charging process.)
Vehicle.Powertrain.TractionBattery.Charging.Temperature (Current temperature of AC/DC converter converting grid voltage to battery voltage.)
Vehicle.Powertrain.TractionBattery.Charging.TimeToComplete (The time needed for the current charging process to reach Charging.ChargeLimit. 0 if charging is complete or no charging process is active or planned.)
Vehicle.Powertrain.TractionBattery.Charging.Timer (Properties related to timing of battery charging sessions.)

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

Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.DC (Current DC charging current at inlet. Negative if returning energy to grid.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase1 (Current AC charging current (rms) at inlet for Phase 1. Negative if returning energy to grid.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase2 (Current AC charging current (rms) at inlet for Phase 2. Negative if returning energy to grid.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeCurrent.Phase3 (Current AC charging current (rms) at inlet for Phase 3. Negative if returning energy to grid.)

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

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

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

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

2.2 - ChargeLimit


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargeLimit`
Description:	Target charge limit (state of charge) for battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeLimit

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargeLimit`	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.TractionBattery.Charging.ChargeLimit is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargeLimit is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeLimit is 62360a4ed1095275a7052d65112aaef1

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

2.3 - ChargePlugType


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargePlugType`
Description:	Type of charge plug (charging inlet) available on the vehicle. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging inlets. IEC_TYPE_1_AC refers to Type 1 as defined in IEC 62196-2. Also known as Yazaki or J1772 connector. IEC_TYPE_2_AC refers to Type 2 as defined in IEC 62196-2. Also known as Mennekes connector. IEC_TYPE_3_AC refers to Type 3 as defined in IEC 62196-2. Also known as Scame connector. IEC_TYPE_4_DC refers to AA configuration as defined in IEC 62196-3. Also known as Type 4 or CHAdeMO connector. IEC_TYPE_1_CCS_DC refers to EE Configuration as defined in IEC 62196-3. Also known as CCS1 or Combo1 connector. IEC_TYPE_2_CCS_DC refers to FF Configuration as defined in IEC 62196-3. Also known as CCS2 or Combo2 connector. TESLA_ROADSTER, TESLA_HPWC (High Power Wall Connector) and TESLA_SUPERCHARGER refer to non-standardized charging inlets/methods used by Tesla. GBT_AC refers to connector specified in GB/T 20234.2. GBT_DC refers to connector specified in GB/T 20234.3. Also specified as BB Configuration in IEC 62196-3. OTHER shall be used if the vehicle has a charging connector, but not one of the connectors listed above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargePlugType

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargePlugType`	VSS: Addressing nodes
Data type	`string[]`	VSS: Datatypes
Allowed values	`['IEC_TYPE_1_AC', 'IEC_TYPE_2_AC', 'IEC_TYPE_3_AC', 'IEC_TYPE_4_DC', 'IEC_TYPE_1_CCS_DC', 'IEC_TYPE_2_CCS_DC', 'TESLA_ROADSTER', 'TESLA_HPWC', 'TESLA_SUPERCHARGER', 'GBT_AC', 'GBT_DC', 'OTHER']`	VSS: Specifying allowed values

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargePlugType is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargePlugType is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargePlugType is 4c56357a6f1d586395215a9beeb26d91

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

2.4 - ChargePortFlap


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargePortFlap`
Description:	Status of the charge port cover, can potentially be controlled manually.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargePortFlap

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargePortFlap`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['OPEN', 'CLOSED']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargePortFlap is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargePortFlap is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargePortFlap is 71bdd2145bb55c3393df194bfc2e03e5

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

2.5 - ChargeRate


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargeRate`
Description:	Current charging rate, as in kilometers of range added per hour.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeRate

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargeRate`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/h`	VSS: Units
Label	kilometer per hour
Description	Speed measured in kilometers per hours	VSS: Sensors & Actuators
Domain	speed

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.ChargeRate is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargeRate is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeRate is a287cea3fdaa533180c8e349343a7851

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

2.6 - ChargeVoltage


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage`
Description:	Current charging voltage, as measured at the charging inlet.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargeVoltage

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage is 7170151d653b52c6bb5e75cb0a14d1c5

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.DC (Current DC charging voltage at charging inlet.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase1 (Current AC charging voltage (rms) at inlet for Phase 1.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase2 (Current AC charging voltage (rms) at inlet for Phase 2.)
Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase3 (Current AC charging voltage (rms) at inlet for Phase 3.)

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.DC`
Description:	Current DC charging voltage at charging inlet.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.DC`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.DC is 701c21d1a4815b35ba061415789ec911

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

2.6.2 - Phase1


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase1`
Description:	Current AC charging voltage (rms) at inlet for Phase 1.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase1`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase1 is 15991c8316585816815d6f4fb6b06776

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

2.6.3 - Phase2


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase2`
Description:	Current AC charging voltage (rms) at inlet for Phase 2.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase2`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase2 is 6c0dcf98169d5a5190736a6dd81291a4

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

2.6.4 - Phase3


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase3`
Description:	Current AC charging voltage (rms) at inlet for Phase 3.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase3`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargeVoltage.Phase3 is 1ab06b48231e54e2ac27e543508c84f0

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

2.7 - IsCharging


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.IsCharging`
Description:	True if charging is ongoing. Charging is considered to be ongoing if energy is flowing from charger to vehicle.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->IsCharging

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.IsCharging`	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.Charging.IsCharging is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.IsCharging is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.IsCharging is d28244c9e3365899954bd3e38ef46bb9

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

2.8 - IsChargingCableConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableConnected`
Description:	Indicates if a charging cable is physically connected to the vehicle or not.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->IsChargingCableConnected

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableConnected`	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.Charging.IsChargingCableConnected is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableConnected is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableConnected is a1c8e2f662b95a54a9933a1b163fff84

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

2.9 - IsChargingCableLocked


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableLocked`
Description:	Is charging cable locked to prevent removal.
Comment:	Locking of charging cable can be used to prevent unintentional removing during charging.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->IsChargingCableLocked

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableLocked`	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.Charging.IsChargingCableLocked is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableLocked is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.IsChargingCableLocked is 7fa81693f3b8587f8d71e7b1619c8e21

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

2.10 - IsDischarging


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.IsDischarging`
Description:	True if discharging (vehicle to grid) is ongoing. Discharging is considered to be ongoing if energy is flowing from vehicle to charger/grid.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->IsDischarging

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.IsDischarging`	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.Charging.IsDischarging is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.IsDischarging is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.IsDischarging is 534d884fb36652688535543b52419529

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

2.11 - MaximumChargingCurrent


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent`
Description:	Maximum charging current that can be accepted by the system, as measured at the charging inlet.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->MaximumChargingCurrent

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent is e3f2e57e7a395d9ca9931d429e540a34

Children

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

Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.DC (Maximum DC charging current at inlet that can be accepted by the system.)
Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase1 (Maximum AC charging current (rms) at inlet for Phase 1 that can be accepted by the system.)
Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase2 (Maximum AC charging current (rms) at inlet for Phase 2 that can be accepted by the system.)
Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase3 (Maximum AC charging current (rms) at inlet for Phase 3 that can be accepted by the system.)

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.DC`
Description:	Maximum DC charging current at inlet that can be accepted by the system.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.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.MaximumChargingCurrent.DC is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.DC is 5a70acfd3c8959898b43738151ab36e1

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

2.11.2 - Phase1


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase1`
Description:	Maximum AC charging current (rms) at inlet for Phase 1 that can be accepted by the system.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.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.MaximumChargingCurrent.Phase1 is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase1 is e3c1034e89cc55968ff51b990906db43

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

2.11.3 - Phase2


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase2`
Description:	Maximum AC charging current (rms) at inlet for Phase 2 that can be accepted by the system.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.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.MaximumChargingCurrent.Phase2 is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase2 is ab3514bc982e54f2b98698fb6c752368

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

2.11.4 - Phase3


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase3`
Description:	Maximum AC charging current (rms) at inlet for Phase 3 that can be accepted by the system.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.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.MaximumChargingCurrent.Phase3 is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.MaximumChargingCurrent.Phase3 is 47dd5e99c30d562e9e2e1c58007846b6

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

2.12 - Mode


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Mode`
Description:	Control of the charge process. MANUAL means manually initiated (plug-in event, companion app, etc). TIMER means timer-based. GRID means grid-controlled (eg ISO 15118). PROFILE means controlled by profile download to vehicle.
Comment:	The mechanism to provide a profile to the vehicle is currently not covered by VSS.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->Mode

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.Mode`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['MANUAL', 'TIMER', 'GRID', 'PROFILE']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Mode is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Mode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Mode is 1e4be3280b265873945531f6f6d0ec6b

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

2.13 - PowerLoss


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.PowerLoss`
Description:	Electrical energy lost by power dissipation to heat inside the AC/DC converter.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->PowerLoss

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.PowerLoss`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`W`	VSS: Units
Label	watt
Description	Power measured in watts	VSS: Sensors & Actuators
Domain	power

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.PowerLoss is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.PowerLoss is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.PowerLoss is 88f40bbeb80b5dfb97ceba13269665c5

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

2.14 - StartStopCharging


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.StartStopCharging`
Description:	Start or stop the charging process.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->StartStopCharging

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.StartStopCharging`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['START', 'STOP']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.StartStopCharging is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.StartStopCharging is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.StartStopCharging is 80506d3e9a2557c2b52f74a50d89593f

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

2.15 - Temperature


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Temperature`
Description:	Current temperature of AC/DC converter converting grid voltage to battery voltage.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->Temperature

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.Temperature`	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.Charging.Temperature is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Temperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Temperature is c3c0ef3a41db5df1bab659803adbc7ba

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

2.16 - Timer


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Timer`
Description:	Properties related to timing of battery charging sessions.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->Timer

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Timer is cd5b57ada627510e83f90832efed9d5a

Children

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

Vehicle.Powertrain.TractionBattery.Charging.Timer.Mode (Defines timer mode for charging: INACTIVE - no timer set, charging may start as soon as battery is connected to a charger. START_TIME - charging shall start at Charging.Timer.Time. END_TIME - charging shall be finished (reach Charging.ChargeLimit) at Charging.Timer.Time. When charging is completed the vehicle shall change mode to ‘inactive’ or set a new Charging.Timer.Time. Charging shall start immediately if mode is ‘starttime’ or ’endtime’ and Charging.Timer.Time is a time in the past.)
Vehicle.Powertrain.TractionBattery.Charging.Timer.Time (Time for next charging-related action, formatted according to ISO 8601 with UTC time zone. Value has no significance if Charging.Timer.Mode is ‘inactive’.)

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

Full qualified VSS Path: Vehicle.Powertrain.TractionBattery.Charging.Timer.Mode

Description: Defines timer mode for charging: INACTIVE - no timer set, charging may start as soon as battery is connected to a charger. START_TIME - charging shall start at Charging.Timer.Time. END_TIME - charging shall be finished (reach Charging.ChargeLimit) at Charging.Timer.Time. When charging is completed the vehicle shall change mode to ‘inactive’ or set a new Charging.Timer.Time. Charging shall start immediately if mode is ‘starttime’ or ’endtime’ and Charging.Timer.Time is a time in the past.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->Timer Timer-->Mode

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.Timer.Mode`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['INACTIVE', 'START_TIME', 'END_TIME']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Timer.Mode is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Timer.Mode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Timer.Mode is b09fb52261735977af275dda1904a7a1

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

2.16.2 - Time


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Timer.Time`
Description:	Time for next charging-related action, formatted according to ISO 8601 with UTC time zone. Value has no significance if Charging.Timer.Mode is ‘inactive’.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->Timer Timer-->Time

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.Timer.Time`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Timer.Time is an Actuator.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Timer.Time is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Timer.Time is c08dcaeda02b5e26aacd7e2542f0fc90

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

2.17 - TimeToComplete


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.TimeToComplete`
Description:	The time needed for the current charging process to reach Charging.ChargeLimit. 0 if charging is complete or no charging process is active or planned.
Comment:	Shall consider time set by Charging.Timer.Time. E.g. if charging shall start in 3 hours and 2 hours of charging is needed, then Charging.TimeToComplete shall report 5 hours.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->TimeToComplete

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.TimeToComplete`	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.TractionBattery.Charging.TimeToComplete is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.TimeToComplete is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.TimeToComplete is c6439c2e068652b08383b9654e2e784a

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

3 - PowerLoss


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.PowerLoss`
Description:	Electrical energy lost by power dissipation to heat inside the battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->PowerLoss

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.PowerLoss`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`W`	VSS: Units
Label	watt
Description	Power measured in watts	VSS: Sensors & Actuators
Domain	power

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.PowerLoss is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.PowerLoss is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.PowerLoss is 880082aafe025cb3a5776b623f9a48b5

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

4 - Range


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Range`
Description:	Remaining range in meters using only battery.

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.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.TractionBattery.Range is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Range is c0376a425e5d578d9d86ae0dc2ad9778

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

5 - AccumulatedChargedEnergy


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.AccumulatedChargedEnergy`
Description:	The accumulated energy delivered to the battery during charging over lifetime of the battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->AccumulatedChargedEnergy

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.AccumulatedChargedEnergy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kWh`	VSS: Units
Label	kilowatt hours
Description	Energy consumption measured in kilowatt hours	VSS: Sensors & Actuators
Domain	energy consumption

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.AccumulatedChargedEnergy is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.AccumulatedChargedEnergy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.AccumulatedChargedEnergy is 739d06021d795da0877bc0ef3c107de1

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

6 - AccumulatedChargedThroughput


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.AccumulatedChargedThroughput`
Description:	The accumulated charge throughput delivered to the battery during charging over lifetime of the battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->AccumulatedChargedThroughput

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.AccumulatedChargedThroughput`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`Ah`	VSS: Units
Label	ampere hours
Description	Electric charge measured in ampere hours	VSS: Sensors & Actuators
Domain	electric charge

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.AccumulatedChargedThroughput is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.AccumulatedChargedThroughput is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.AccumulatedChargedThroughput is 6d038ccc313351fba3a9104c1158a207

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

7 - AccumulatedConsumedEnergy


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.AccumulatedConsumedEnergy`
Description:	The accumulated energy leaving HV battery for propulsion and auxiliary loads over lifetime of the battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->AccumulatedConsumedEnergy

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.AccumulatedConsumedEnergy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kWh`	VSS: Units
Label	kilowatt hours
Description	Energy consumption measured in kilowatt hours	VSS: Sensors & Actuators
Domain	energy consumption

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.AccumulatedConsumedEnergy is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.AccumulatedConsumedEnergy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.AccumulatedConsumedEnergy is b844cb96765f574d8d31edb09ccaef81

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

8 - AccumulatedConsumedThroughput


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.AccumulatedConsumedThroughput`
Description:	The accumulated charge throughput leaving HV battery for propulsion and auxiliary loads over lifetime of the battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->AccumulatedConsumedThroughput

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.AccumulatedConsumedThroughput`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`Ah`	VSS: Units
Label	ampere hours
Description	Electric charge measured in ampere hours	VSS: Sensors & Actuators
Domain	electric charge

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.AccumulatedConsumedThroughput is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.AccumulatedConsumedThroughput is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.AccumulatedConsumedThroughput is f3e2ca21f3b550288d494827c9a172dd

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

9 - CurrentCurrent


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CurrentCurrent`
Description:	Current current flowing in/out of battery. Positive = Current flowing in to battery, e.g. during charging. Negative = Current flowing out of battery, e.g. during driving.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->CurrentCurrent

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.CurrentCurrent`	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.CurrentCurrent is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.CurrentCurrent is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CurrentCurrent is 7a1488e0c83f50a6b69d8ea85c5bb592

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

10 - CurrentPower


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CurrentPower`
Description:	Current electrical energy flowing in/out of battery. Positive = Energy flowing in to battery, e.g. during charging. Negative = Energy flowing out of battery, e.g. during driving.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->CurrentPower

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.CurrentPower`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`W`	VSS: Units
Label	watt
Description	Power measured in watts	VSS: Sensors & Actuators
Domain	power

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.CurrentPower is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.CurrentPower is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CurrentPower is 8859e1b0386a5eda880a9c30cd0dfa8e

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

11 - CurrentVoltage


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CurrentVoltage`
Description:	Current Voltage of the battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->CurrentVoltage

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.CurrentVoltage`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

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.CurrentVoltage is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.CurrentVoltage is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CurrentVoltage is 7b54ea22ee7d5f559da552aefcc07222

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

12 - GrossCapacity


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.GrossCapacity`
Description:	Gross capacity of the battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->GrossCapacity

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.GrossCapacity`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kWh`	VSS: Units
Label	kilowatt hours
Description	Energy consumption measured in kilowatt hours	VSS: Sensors & Actuators
Domain	energy consumption

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.GrossCapacity is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.GrossCapacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.GrossCapacity is 5460530488435dc8bfa1298bf47a993d

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

13 - Id


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Id`
Description:	Battery Identification Number as assigned by OEM.
Comment:	This could be serial number, part number plus serial number, UUID, or any other identifier that the OEM want to use to uniquely identify the battery individual.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Id

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Id`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Id is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Id is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Id is c8279874660c55b38c7ac64a8503a519

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

14 - IsGroundConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.IsGroundConnected`
Description:	Indicating if the ground (negative terminator) of the traction battery is connected to the powertrain.
Comment:	It might be possible to disconnect the traction battery used by an electric powertrain. This is achieved by connectors, typically one for plus and one for minus.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->IsGroundConnected

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.IsGroundConnected`	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.IsGroundConnected is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.IsGroundConnected is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.IsGroundConnected is dd38d1c7ee12530aac03f49ad01d5c04

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

15 - IsPowerConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.IsPowerConnected`
Description:	Indicating if the power (positive terminator) of the traction battery is connected to the powertrain.
Comment:	It might be possible to disconnect the traction battery used by an electric powertrain. This is achieved by connectors, typically one for plus and one for minus.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->IsPowerConnected

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.IsPowerConnected`	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.IsPowerConnected is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.IsPowerConnected is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.IsPowerConnected is e30ef59fc2a25f6b8990248e19a5cdf9

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

16 - MaxVoltage


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.MaxVoltage`
Description:	Max allowed voltage of the battery, e.g. during charging.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->MaxVoltage

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.MaxVoltage`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.MaxVoltage is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.MaxVoltage is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.MaxVoltage is a81264a0ef0c55d288671cfc62c4add5

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

17 - NetCapacity


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.NetCapacity`
Description:	Total net capacity of the battery considering aging.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->NetCapacity

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.NetCapacity`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kWh`	VSS: Units
Label	kilowatt hours
Description	Energy consumption measured in kilowatt hours	VSS: Sensors & Actuators
Domain	energy consumption

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.NetCapacity is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.NetCapacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.NetCapacity is 9c68fe42cb81501eb6349f8c9b0b6899

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

18 - NominalVoltage


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.NominalVoltage`
Description:	Nominal Voltage of the battery.
Comment:	Nominal voltage typically refers to voltage of fully charged battery when delivering rated capacity.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->NominalVoltage

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.NominalVoltage`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`V`	VSS: Units
Label	volt
Description	Electric potential measured in volts	VSS: Sensors & Actuators
Domain	electric potential

Note: The uint16 datatype is an unsigned 16-bit integer which technically allows values between 0 and 65535 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.NominalVoltage is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.NominalVoltage is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.NominalVoltage is 3eccae5633185b998d5bdb6ea33cd926

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

19 - ProductionDate


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.ProductionDate`
Description:	Production date of battery in ISO8601 format, e.g. YYYY-MM-DD.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->ProductionDate

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.ProductionDate`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.ProductionDate is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.ProductionDate is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.ProductionDate is c9509ba4d76c56d9a8c1d6e2280ae02f

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

20 - StateOfCharge


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.StateOfCharge`
Description:	Information on the state of charge of the vehicle’s high voltage battery.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->StateOfCharge

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.StateOfCharge is 26bae2ce7c4d5e2a951915ef2f5d8b7d

Children

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

Vehicle.Powertrain.TractionBattery.StateOfCharge.Current (Physical state of charge of the high voltage battery, relative to net capacity. This is not necessarily the state of charge being displayed to the customer.)
Vehicle.Powertrain.TractionBattery.StateOfCharge.Displayed (State of charge displayed to the customer.)

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.

20.1 - Current


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.StateOfCharge.Current`
Description:	Physical state of charge of the high voltage battery, relative to net capacity. This is not necessarily the state of charge being displayed to the customer.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->StateOfCharge StateOfCharge-->Current

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.StateOfCharge.Current`	VSS: Addressing nodes
Data type	`float`	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.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.TractionBattery.StateOfCharge.Current is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.StateOfCharge.Current is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.StateOfCharge.Current is 2e647ca3a1ff5e52af137aab240642da

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

20.2 - Displayed


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.StateOfCharge.Displayed`
Description:	State of charge displayed to the customer.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->StateOfCharge StateOfCharge-->Displayed

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.StateOfCharge.Displayed`	VSS: Addressing nodes
Data type	`float`	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.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.TractionBattery.StateOfCharge.Displayed is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.StateOfCharge.Displayed is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.StateOfCharge.Displayed is 1bfcc228293b5512aafe2508ab0500d2

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

21 - StateOfHealth


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.StateOfHealth`
Description:	Calculated battery state of health at standard conditions.
Comment:	Exact formula is implementation dependent. Could be e.g. current capacity at 20 degrees Celsius divided with original capacity at the same temperature.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->StateOfHealth

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.StateOfHealth`	VSS: Addressing nodes
Data type	`float`	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 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.StateOfHealth is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.StateOfHealth is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.StateOfHealth is 4d982c47f3245048bcfec1190973a3ed

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

22 - Temperature


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Temperature`
Description:	Temperature Information for the battery pack.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Temperature

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Temperature is 1cfbcf8c152959dcb3eb2c54fc42e623

Children

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

Vehicle.Powertrain.TractionBattery.Temperature.Average (Current average temperature of the battery cells.)
Vehicle.Powertrain.TractionBattery.Temperature.Max (Current maximum temperature of the battery cells, i.e. temperature of the hottest cell.)
Vehicle.Powertrain.TractionBattery.Temperature.Min (Current minimum temperature of the battery cells, i.e. temperature of the coldest cell.)

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.

22.1 - Average


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Temperature.Average`
Description:	Current average temperature of the battery cells.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Temperature Temperature-->Average

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Temperature.Average`	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.Temperature.Average is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Temperature.Average is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Temperature.Average is ae28e502137f56b9a037ed9b32bc04e1

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

22.2 - Max


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Temperature.Max`
Description:	Current maximum temperature of the battery cells, i.e. temperature of the hottest cell.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Temperature Temperature-->Max

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Temperature.Max`	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.Temperature.Max is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Temperature.Max is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Temperature.Max is 07aa7c8ba1d355398d7469c2b337152a

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

22.3 - Min


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Temperature.Min`
Description:	Current minimum temperature of the battery cells, i.e. temperature of the coldest cell.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Temperature Temperature-->Min

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Temperature.Min`	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.Temperature.Min is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Temperature.Min is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Temperature.Min is 4e3f630fefa7558fa302b175bc7eb5c7

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

TractionBattery

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - DCDC

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - PowerLoss

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.2 - Temperature

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2 - Charging

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

2.1 - ChargeCurrent

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

2.1.1 - DC

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.1.2 - Phase1

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

2.1.3 - Phase2

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback