Vehicle.Powertrain.AccumulatedBrakingEnergy (The accumulated energy from regenerative braking over lifetime.)
Vehicle.Powertrain.CombustionEngine (Engine-specific data, stopping at the bell housing.)
Vehicle.Powertrain.ElectricMotor (Electric Motor specific data.)
Vehicle.Powertrain.FuelSystem (Fuel system data.)
Vehicle.Powertrain.IsAutoPowerOptimize (Auto Power Optimization Flag When set to ’true’, the system enables automatic power optimization, dynamically adjusting the power optimization level based on runtime conditions or features managed by the OEM. When set to ‘false’, manual control of the power optimization level is allowed.)
Vehicle.Powertrain.PowerOptimizeLevel (Power optimization level for this branch/subsystem. A higher number indicates more aggressive power optimization. Level 0 indicates that all functionality is enabled, no power optimization enabled. Level 10 indicates most aggressive power optimization mode, only essential functionality enabled.)
Vehicle.Powertrain.Range (Remaining range in meters using all energy sources available in the vehicle.)
Vehicle.Powertrain.RangeExtender (Extended Range Electric Vehicle (EREV) specific data.)
Vehicle.Powertrain.TimeRemaining (Time remaining in seconds before all energy sources available in the vehicle are empty.)
Vehicle.Powertrain.TractionBattery (Battery Management data.)
Vehicle.Powertrain.Transmission (Transmission-specific data, stopping at the drive shafts.)
Vehicle.Powertrain.Type (Defines the powertrain type of the vehicle.)

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem`
Description:	Fuel system data.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem is dbc194a7f97d5a56bc8942c17c2db22e

Children

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

Vehicle.Powertrain.FuelSystem.AbsoluteLevel (Current available fuel in the fuel tank expressed in liters.)
Vehicle.Powertrain.FuelSystem.AfterRefuelingFuelEconomy (Average fuel economy calculated from the most recent refueling event to the current time.)
Vehicle.Powertrain.FuelSystem.AverageConsumption (Average consumption in liters per 100 km.)
Vehicle.Powertrain.FuelSystem.ConsumptionSinceLastRefuel (Fuel consumption since last refueling.)
Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart (Fuel amount in liters consumed since start of current trip.)
Vehicle.Powertrain.FuelSystem.CumulativeFuelEconomy (Cumulative average fuel economy calculated from vehicle start or last user reset.)
Vehicle.Powertrain.FuelSystem.DriveFuelEconomy (Average fuel economy for the current drive cycle, calculated from engine start to current time.)
Vehicle.Powertrain.FuelSystem.HybridType (Defines the hybrid type of the vehicle.)
Vehicle.Powertrain.FuelSystem.InstantConsumption (Current consumption in liters per 100 km.)
Vehicle.Powertrain.FuelSystem.InstantantFuelEconomy (Real-time instantaneous fuel economy calculated over a short time window.)
Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled (Indicates whether eco start stop is currently enabled.)
Vehicle.Powertrain.FuelSystem.IsFuelLevelEmpty (Indicates that the fuel gauge on the instrument cluster displays empty (0).)
Vehicle.Powertrain.FuelSystem.IsFuelLevelLow (Indicates that the fuel level is low (e.g. <50km range).)
Vehicle.Powertrain.FuelSystem.IsFuelPortFlapOpen (Status of the fuel port flap(s). True if at least one is open.)
Vehicle.Powertrain.FuelSystem.Range (Remaining range in meters using only liquid fuel.)
Vehicle.Powertrain.FuelSystem.RefuelPortPosition (Position of refuel port(s). First part indicates side of vehicle, second part relative position on that side.)
Vehicle.Powertrain.FuelSystem.RelativeLevel (Level in fuel tank as percent of capacity. 0 = empty. 100 = full.)
Vehicle.Powertrain.FuelSystem.SupportedFuel (Detailed information on fuels supported by the vehicle. Identifiers originating from DIN EN 16942:2021-08, appendix B, with additional suffix for octane (RON) where relevant.)
Vehicle.Powertrain.FuelSystem.SupportedFuelTypes (High level information of fuel types supported)
Vehicle.Powertrain.FuelSystem.TankCapacity (Capacity of the fuel tank in liters.)
Vehicle.Powertrain.FuelSystem.TimeRemaining (Time remaining in seconds before the fuel tank is empty.)

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.AbsoluteLevel`
Description:	Current available fuel in the fuel tank expressed in liters.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->AbsoluteLevel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.AbsoluteLevel`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.AbsoluteLevel is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.AbsoluteLevel is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.AbsoluteLevel is 00a1399655ee5d9188022f3d55d8f05e

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.AfterRefuelingFuelEconomy`
Description:	Average fuel economy calculated from the most recent refueling event to the current time.
Comment:	This value represents the fuel efficiency for the period between consecutive refueling events. It is automatically reset to zero when refueling is detected and begins accumulating from that point. The calculation continues until the next refueling occurs. This metric is useful for tracking fuel efficiency improvements or changes between fill-ups.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->AfterRefuelingFuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.AfterRefuelingFuelEconomy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/l`	VSS: Units
Label	kilometers per liter
Description	Distance per volume measured in kilometers per liter	VSS: Sensors & Actuators
Domain	distance-per-volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.AfterRefuelingFuelEconomy is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.AfterRefuelingFuelEconomy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.AfterRefuelingFuelEconomy is 1550804daaa654359ade39ffee566c81

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.AverageConsumption`
Description:	Average consumption in liters per 100 km.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->AverageConsumption

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.AverageConsumption`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l/100km`	VSS: Units
Label	liter per 100 kilometers
Description	Volume per distance measured in liters per 100 kilometers	VSS: Sensors & Actuators
Domain	volume-per-distance
Minimum value	`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.FuelSystem.AverageConsumption is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.AverageConsumption is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.AverageConsumption is e2252108125a54dcab34e1bad0fe8bdc

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.ConsumptionSinceLastRefuel`
Description:	Fuel consumption since last refueling.
Comment:	Amount of fuel consumed since last refueling.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->ConsumptionSinceLastRefuel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.ConsumptionSinceLastRefuel`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.ConsumptionSinceLastRefuel is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.ConsumptionSinceLastRefuel is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.ConsumptionSinceLastRefuel is 79d18a88c39757aba435444a8c1c0079

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart`
Description:	Fuel amount in liters consumed since start of current trip.
Comment:	A new trip is considered to start when engine gets enabled (e.g. LowVoltageSystemState in ON or START mode). A trip is considered to end when engine is no longer enabled. The signal may however keep the value of the last trip until a new trip is started.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->ConsumptionSinceStart

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.ConsumptionSinceStart is adf0a40964ff556f92b10275ad918883

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.CumulativeFuelEconomy`
Description:	Cumulative average fuel economy calculated from vehicle start or last user reset.
Comment:	This represents the accumulated fuel economy over the entire period since the last reset. Unlike trip-based measurements, this provides a long-term average of fuel efficiency.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->CumulativeFuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.CumulativeFuelEconomy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/l`	VSS: Units
Label	kilometers per liter
Description	Distance per volume measured in kilometers per liter	VSS: Sensors & Actuators
Domain	distance-per-volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.CumulativeFuelEconomy is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.CumulativeFuelEconomy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.CumulativeFuelEconomy is da4f358cf03451c3a3803db09a563f3d

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.DriveFuelEconomy`
Description:	Average fuel economy for the current drive cycle, calculated from engine start to current time.
Comment:	This represents the fuel efficiency during the active driving session. The value is reset when the engine is no longer enabled or when the user manually initiates a drive fuel economy reset. After reset, it is recalculated from zero when the engine restarts or the new drive cycle begins. It provides real-time average fuel economy for the ongoing drive cycle.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->DriveFuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.DriveFuelEconomy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/l`	VSS: Units
Label	kilometers per liter
Description	Distance per volume measured in kilometers per liter	VSS: Sensors & Actuators
Domain	distance-per-volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.DriveFuelEconomy is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.DriveFuelEconomy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.DriveFuelEconomy is 2b901765b2b35018ad83a3cbe5d0fc7b

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.HybridType`
Description:	Defines the hybrid type of the vehicle.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->HybridType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.HybridType`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Default value	`UNKNOWN`	VSS: Sensors & Actuators
Allowed values	`['UNKNOWN', 'NOT_APPLICABLE', 'STOP_START', 'BELT_ISG', 'CIMG', 'PHEV']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.HybridType is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.HybridType is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.HybridType is f0f72012f5e453c1935ff8c3a5aff696

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.InstantantFuelEconomy`
Description:	Real-time instantaneous fuel economy calculated over a short time window.
Comment:	This value represents the current fuel efficiency at any given moment during vehicle operation. It is calculated based on the distance traveled and fuel consumed over a brief sampling period (typically around 500ms). The calculation compares the vehicle state before and after the sampling window to determine instantaneous efficiency. This metric refreshes frequently and can fluctuate significantly based on driving conditions, acceleration, and terrain. Unlike average fuel economy measurements, this provides immediate feedback on current driving efficiency.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->InstantantFuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.InstantantFuelEconomy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/l`	VSS: Units
Label	kilometers per liter
Description	Distance per volume measured in kilometers per liter	VSS: Sensors & Actuators
Domain	distance-per-volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.InstantantFuelEconomy is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.InstantantFuelEconomy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.InstantantFuelEconomy is 209ef58ef2be561c98d19e3e92982223

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.InstantConsumption`
Description:	Current consumption in liters per 100 km.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->InstantConsumption

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.InstantConsumption`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l/100km`	VSS: Units
Label	liter per 100 kilometers
Description	Volume per distance measured in liters per 100 kilometers	VSS: Sensors & Actuators
Domain	volume-per-distance
Minimum value	`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.FuelSystem.InstantConsumption is a Sensor.

The vehicle signal Vehicle.Powertrain.FuelSystem.InstantConsumption is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.InstantConsumption is cf65767ec8ad56ffadfdccd831e4b562

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled`
Description:	Indicates whether eco start stop is currently enabled.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->IsEngineStopStartEnabled

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.IsEngineStopStartEnabled is 176eed5bb0da582a9ee56f1c70e12075

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.IsFuelLevelEmpty`
Description:	Indicates that the fuel gauge on the instrument cluster displays empty (0).
Comment:	When this signal is true, the fuel gauge displays empty (0), but the vehicle typically still has reserve fuel allowing for some additional driving range depending on the vehicle design. This represents the displayed empty state, not actual tank empty condition.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->IsFuelLevelEmpty

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.FuelSystem.IsFuelLevelEmpty is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.IsFuelLevelEmpty is bccdab633d305dc4b054ce6089fbfcf5

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.IsFuelLevelLow`
Description:	Indicates that the fuel level is low (e.g. <50km range).

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->IsFuelLevelLow

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.FuelSystem.IsFuelLevelLow is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.IsFuelLevelLow is 65f18ee3b04f5d4c8bb76083227dd9fe

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.IsFuelPortFlapOpen`
Description:	Status of the fuel port flap(s). True if at least one is open.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->IsFuelPortFlapOpen

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.IsFuelPortFlapOpen`	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.FuelSystem.IsFuelPortFlapOpen is an Actuator.

The vehicle signal Vehicle.Powertrain.FuelSystem.IsFuelPortFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.IsFuelPortFlapOpen is fded7edb113c5894a21722085834f3ae

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.Range`
Description:	Remaining range in meters using only liquid fuel.

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

Data Type & Unit


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

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.Range is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.Range is c5a0dbe5e754553897f0aed0069af57a

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.RefuelPortPosition`
Description:	Position of refuel port(s). First part indicates side of vehicle, second part relative position on that side.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->RefuelPortPosition

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.RefuelPortPosition`	VSS: Addressing nodes
Data type	`string[]`	VSS: Datatypes
Allowed values	`['FRONT_LEFT', 'FRONT_MIDDLE', 'FRONT_RIGHT', 'REAR_LEFT', 'REAR_MIDDLE', 'REAR_RIGHT', 'LEFT_FRONT', 'LEFT_MIDDLE', 'LEFT_REAR', 'RIGHT_FRONT', 'RIGHT_MIDDLE', 'RIGHT_REAR']`	VSS: Specifying allowed values

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.RefuelPortPosition is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.RefuelPortPosition is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.RefuelPortPosition is a7b5eb269b345ef7b18602b66517f952

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.RelativeLevel`
Description:	Level in fuel tank as percent of capacity. 0 = empty. 100 = full.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->RelativeLevel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.FuelSystem.RelativeLevel is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.RelativeLevel is e90e3daa1dcd5165a9d78b09e890fb22

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.SupportedFuel`
Description:	Detailed information on fuels supported by the vehicle. Identifiers originating from DIN EN 16942:2021-08, appendix B, with additional suffix for octane (RON) where relevant.
Comment:	RON 95 is sometimes referred to as Super, RON 98 as Super Plus.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->SupportedFuel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.SupportedFuel`	VSS: Addressing nodes
Data type	`string[]`	VSS: Datatypes
Allowed values	`['E5_95', 'E5_98', 'E10_95', 'E10_98', 'E85', 'B7', 'B10', 'B20', 'B30', 'B100', 'XTL', 'LPG', 'CNG', 'LNG', 'H2', 'OTHER']`	VSS: Specifying allowed values

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuel is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuel is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.SupportedFuel is 7fd3bf2ef0c650e69ff2037875ec59ee

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.SupportedFuelTypes`
Description:	High level information of fuel types supported
Comment:	If a vehicle also has an electric drivetrain (e.g. hybrid) that will be obvious from the PowerTrain.Type signal.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->SupportedFuelTypes

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.SupportedFuelTypes`	VSS: Addressing nodes
Data type	`string[]`	VSS: Datatypes
Allowed values	`['GASOLINE', 'DIESEL', 'E85', 'LPG', 'CNG', 'LNG', 'H2', 'OTHER']`	VSS: Specifying allowed values

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuelTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.SupportedFuelTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.SupportedFuelTypes is 80edc3002aa25097aba6455fe459fa6c

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.TankCapacity`
Description:	Capacity of the fuel tank in liters.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->TankCapacity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.TankCapacity`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.FuelSystem.TankCapacity is an Attribute.

The vehicle signal Vehicle.Powertrain.FuelSystem.TankCapacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.TankCapacity is 362643b866c55d5386fdbdf383464e90

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


Full qualified VSS Path:	`Vehicle.Powertrain.FuelSystem.TimeRemaining`
Description:	Time remaining in seconds before the fuel tank is empty.

flowchart LR Vehicle-->Powertrain Powertrain-->FuelSystem FuelSystem-->TimeRemaining

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.FuelSystem.TimeRemaining`	VSS: Addressing nodes
Data type	`uint32`	VSS: Datatypes
Unit	`s`	VSS: Units
Label	second
Description	Duration measured in seconds	VSS: Sensors & Actuators
Domain	duration

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

The vehicle signal Vehicle.Powertrain.FuelSystem.TimeRemaining is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.FuelSystem.TimeRemaining is a531b80a16bc59949abb2ab5228a1034

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


Full qualified VSS Path:	`Vehicle.Powertrain.RangeExtender`
Description:	Extended Range Electric Vehicle (EREV) specific data.

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.RangeExtender is d97d2b08f45e57e19d47fa79fec06205

Children

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

Vehicle.Powertrain.RangeExtender.ChargeDepleting (Signals related to Charge Depleting (CD) mode operation.)
Vehicle.Powertrain.RangeExtender.ChargeSustaining (Signals related to Charge Sustaining (CS) mode operation.)
Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy (Combined fuel economy equivalent that accounts for both electric energy and fuel consumption.)
Vehicle.Powertrain.RangeExtender.OperatingMode (Current operating mode of the Extended Range Electric Vehicle.)

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


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

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeDepleting

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.ChargeDepleting

Signal Information

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

UUID

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

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

Children

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

Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption (Current electric energy consumption rate during Charge Depleting mode operation.)
Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range (Estimated remaining distance that can be traveled in Charge Depleting mode using available battery energy.)

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


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

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeDepleting ChargeDepleting-->EnergyConsumption

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption
[get]  OK
Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.ChargeDepleting.EnergyConsumption

Data Type & Unit


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

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

2.1.2 - Range


Full qualified VSS Path:	`Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range`
Description:	Estimated remaining distance that can be traveled in Charge Depleting mode using available battery energy.
Comment:	This range estimate is calculated based on the current battery state of charge and the recent energy consumption patterns in CD mode. The estimate may vary based on driving conditions, terrain, climate control usage, and other factors affecting battery consumption. When this range approaches zero, the vehicle will typically transition to Charge Sustaining mode.

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeDepleting ChargeDepleting-->Range

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range
[get]  OK
Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.ChargeDepleting.Range

Data Type & Unit


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

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

2.2 - ChargeSustaining


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

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeSustaining

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.ChargeSustaining

Signal Information

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

UUID

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

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

Children

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

Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy (Current fuel economy during Charge Sustaining mode operation.)
Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range (Estimated remaining distance that can be traveled in Charge Sustaining mode using available fuel.)

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


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

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeSustaining ChargeSustaining-->FuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy
[get]  OK
Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy

Data Type & Unit


Path	`Vehicle.Powertrain.RangeExtender.ChargeSustaining.FuelEconomy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/l`	VSS: Units
Label	kilometers per liter
Description	Distance per volume measured in kilometers per liter	VSS: Sensors & Actuators
Domain	distance-per-volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

2.2.2 - Range


Full qualified VSS Path:	`Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range`
Description:	Estimated remaining distance that can be traveled in Charge Sustaining mode using available fuel.
Comment:	This range estimate is calculated based on the current fuel level and recent fuel consumption patterns in CS mode. It represents the extended range capability provided by the internal combustion engine. The total vehicle range is the sum of CD mode range and CS mode range.

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->ChargeSustaining ChargeSustaining-->Range

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range
[get]  OK
Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.ChargeSustaining.Range

Data Type & Unit


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

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

2.3 - CombinedFuelEconomy


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

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->CombinedFuelEconomy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy
[get]  OK
Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy

Data Type & Unit


Path	`Vehicle.Powertrain.RangeExtender.CombinedFuelEconomy`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km/l`	VSS: Units
Label	kilometers per liter
Description	Distance per volume measured in kilometers per liter	VSS: Sensors & Actuators
Domain	distance-per-volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

2.4 - OperatingMode


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

flowchart LR Vehicle-->Powertrain Powertrain-->RangeExtender RangeExtender-->OperatingMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.RangeExtender.OperatingMode
[get]  OK
Vehicle.Powertrain.RangeExtender.OperatingMode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.RangeExtender.OperatingMode Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.RangeExtender.OperatingMode

Data Type & Unit


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

Note: The string datatype is a character string.

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

3 - ElectricMotor


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor`
Description:	Electric Motor specific data.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor is 1ade64f6b0d05f6c9340e7a667555ae2

Children

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

Vehicle.Powertrain.ElectricMotor.EngineCode (Engine code designation, as specified by vehicle manufacturer.)
Vehicle.Powertrain.ElectricMotor.EngineCoolant (Signals related to the engine coolant (if applicable).)
Vehicle.Powertrain.ElectricMotor.MaxPower (Peak power, in kilowatts, that motor(s) can generate.)
Vehicle.Powertrain.ElectricMotor.MaxRegenPower (Peak regen/brake power, in kilowatts, that motor(s) can generate.)
Vehicle.Powertrain.ElectricMotor.MaxRegenTorque (Peak regen/brake torque, in newton meter, that the motor(s) can generate.)
Vehicle.Powertrain.ElectricMotor.MaxTorque (Peak power, in newton meter, that the motor(s) can generate.)
Vehicle.Powertrain.ElectricMotor.Power (Current motor power output. Negative values indicate regen mode.)
Vehicle.Powertrain.ElectricMotor.Speed (Motor rotational speed measured as rotations per minute. Negative values indicate reverse driving mode.)
Vehicle.Powertrain.ElectricMotor.Temperature (Motor temperature.)
Vehicle.Powertrain.ElectricMotor.TimeInUse (Accumulated time during engine lifetime when the vehicule state’s is ‘READY’.)
Vehicle.Powertrain.ElectricMotor.Torque (Current motor torque. Negative values indicate regen mode.)

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.

3.1 - EngineCode


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.EngineCode`
Description:	Engine code designation, as specified by vehicle manufacturer.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->EngineCode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.EngineCode`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCode is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.EngineCode is e4102a5142ed501495e5edafd3d36dfb

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.EngineCoolant`
Description:	Signals related to the engine coolant (if applicable).

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->EngineCoolant

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

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.EngineCoolant is 898ca20307545537929a13522eea4844

Children

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

Vehicle.Powertrain.ElectricMotor.EngineCoolant.Capacity (Engine coolant capacity in liters.)
Vehicle.Powertrain.ElectricMotor.EngineCoolant.Level (Engine coolant level.)
Vehicle.Powertrain.ElectricMotor.EngineCoolant.LifeRemaining (Remaining engine coolant life in seconds. Negative values can be used to indicate that lifetime has been exceeded.)
Vehicle.Powertrain.ElectricMotor.EngineCoolant.Temperature (Engine coolant temperature.)

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.

3.2.1 - Capacity


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.EngineCoolant.Capacity`
Description:	Engine coolant capacity in liters.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->EngineCoolant EngineCoolant-->Capacity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.EngineCoolant.Capacity`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant.Capacity is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant.Capacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.EngineCoolant.Capacity is 86a4ebad21865e41ab35d449a0179881

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.EngineCoolant.Level`
Description:	Engine coolant level.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->EngineCoolant EngineCoolant-->Level

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.EngineCoolant.Level`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['CRITICALLY_LOW', 'LOW', 'NORMAL']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant.Level is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant.Level is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.EngineCoolant.Level is 3168787e45335fd4b1caf1b0703cd524

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.EngineCoolant.LifeRemaining`
Description:	Remaining engine coolant life in seconds. Negative values can be used to indicate that lifetime has been exceeded.
Comment:	In addition to this a signal a vehicle can report remaining time to service (including e.g. coolant change) by Vehicle.Service.TimeToService.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->EngineCoolant EngineCoolant-->LifeRemaining

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.EngineCoolant.LifeRemaining`	VSS: Addressing nodes
Data type	`int32`	VSS: Datatypes
Unit	`s`	VSS: Units
Label	second
Description	Duration measured in seconds	VSS: Sensors & Actuators
Domain	duration

Note: The int32 datatype is a signed 32-bit integer which technically allows values between -2147483648 and 2147483647 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant.LifeRemaining is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant.LifeRemaining is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.EngineCoolant.LifeRemaining is a9273c36bf00597992f731bfbcd49695

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.EngineCoolant.Temperature`
Description:	Engine coolant temperature.

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.ElectricMotor.EngineCoolant.Temperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.EngineCoolant.Temperature is 65e9e8758c4b5e69800d2fc2be2de007

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.MaxPower`
Description:	Peak power, in kilowatts, that motor(s) can generate.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxPower

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.MaxPower`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kW`	VSS: Units
Label	kilowatt
Description	Power measured in kilowatts	VSS: Sensors & Actuators
Domain	power
Default value	`0`	VSS: Sensors & Actuators

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.ElectricMotor.MaxPower is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxPower is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.MaxPower is 825ec7911ee958abb199b9f7903df3a6

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.MaxRegenPower`
Description:	Peak regen/brake power, in kilowatts, that motor(s) can generate.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxRegenPower

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.MaxRegenPower`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kW`	VSS: Units
Label	kilowatt
Description	Power measured in kilowatts	VSS: Sensors & Actuators
Domain	power
Default value	`0`	VSS: Sensors & Actuators

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.ElectricMotor.MaxRegenPower is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxRegenPower is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.MaxRegenPower is 7f2cb2650ba95485b7156ffe76e27366

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.MaxRegenTorque`
Description:	Peak regen/brake torque, in newton meter, that the motor(s) can generate.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxRegenTorque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.MaxRegenTorque`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`Nm`	VSS: Units
Label	newton meter
Description	Torque measured in newton meters	VSS: Sensors & Actuators
Domain	torque
Default value	`0`	VSS: Sensors & Actuators

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.ElectricMotor.MaxRegenTorque is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxRegenTorque is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.MaxRegenTorque is 0e5190c2517b55aa80fcb9bf698e02d6

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.MaxTorque`
Description:	Peak power, in newton meter, that the motor(s) can generate.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->MaxTorque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.MaxTorque`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`Nm`	VSS: Units
Label	newton meter
Description	Torque measured in newton meters	VSS: Sensors & Actuators
Domain	torque
Default value	`0`	VSS: Sensors & Actuators

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.ElectricMotor.MaxTorque is an Attribute.

The vehicle signal Vehicle.Powertrain.ElectricMotor.MaxTorque is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.MaxTorque is cf31eabcde5151f589e9b0f7a6090512

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.Power`
Description:	Current motor power output. Negative values indicate regen mode.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->Power

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.Power`	VSS: Addressing nodes
Data type	`int16`	VSS: Datatypes
Unit	`kW`	VSS: Units
Label	kilowatt
Description	Power measured in kilowatts	VSS: Sensors & Actuators
Domain	power

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.Power is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.Power is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.Power is 46b86286fba059349a733fed9a0e3232

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.Speed`
Description:	Motor rotational speed measured as rotations per minute. Negative values indicate reverse driving mode.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->Speed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.Speed`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`rpm`	VSS: Units
Label	revolutions per minute
Description	Rotational speed measured in revolutions per minute	VSS: Sensors & Actuators
Domain	rotational-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.ElectricMotor.Speed is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.Speed is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.Speed is ca961aa6ca435095a89f9d404a5d849d

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.Temperature`
Description:	Motor temperature.

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.ElectricMotor.Temperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.Temperature is 1b7c15e5341052139995bfacea2c05b2

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.TimeInUse`
Description:	Accumulated time during engine lifetime when the vehicule state’s is ‘READY’.
Comment:	Vehicles may define their READY state.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->TimeInUse

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.TimeInUse`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`h`	VSS: Units
Label	hour
Description	Duration measured in hours	VSS: Sensors & Actuators
Domain	duration

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

The vehicle signal Vehicle.Powertrain.ElectricMotor.TimeInUse is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.TimeInUse is d5fec5eaacd65575922b79c268370051

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


Full qualified VSS Path:	`Vehicle.Powertrain.ElectricMotor.Torque`
Description:	Current motor torque. Negative values indicate regen mode.

flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->Torque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.ElectricMotor.Torque`	VSS: Addressing nodes
Data type	`int16`	VSS: Datatypes
Unit	`Nm`	VSS: Units
Label	newton meter
Description	Torque measured in newton meters	VSS: Sensors & Actuators
Domain	torque

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.ElectricMotor.Torque is a Sensor.

The vehicle signal Vehicle.Powertrain.ElectricMotor.Torque is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.ElectricMotor.Torque is aceffe768ddf5b828fff0975349d2433

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery`
Description:	Battery Management data.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery is 1a2515d1a8875d86873431194ade2b50

Children

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

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.BatteryConditioning (Properties related to preparing the vehicle battery for charging or driving.)
Vehicle.Powertrain.TractionBattery.CellVoltage (Voltage information for cells in the battery pack.)
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.ErrorCodes (Current error codes related to the battery, if any.)
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.)
Vehicle.Powertrain.TractionBattery.TimeRemaining (Time remaining in seconds before the battery is empty.)

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.

4.1 - BatteryConditioning


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

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.TractionBattery.BatteryConditioning

Signal Information

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

UUID

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

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

Children

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

Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive (Indicates if battery conditioning is active (i.e. actively monitors battery temperature). True = Active. False = Inactive.)
Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing (Indicating if battery conditioning is currently ongoing. Battery conditioning is considered ongoing when the battery conditioning system is actively heating or cooling the battery, or requesting heating or cooling.)
Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode (Defines requested mode for battery conditioning. INACTIVE - Battery conditioning inactive. FAST_CHARGING_PREPARATION - Battery conditioning for fast charging. DRIVING_PREPARATION - Battery conditioning for driving.)
Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime (Start time for battery conditioning, formatted according to ISO 8601 with UTC time zone.)
Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature (Target temperature for battery conditioning.)
Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime (Target time when conditioning shall be finished, formatted according to ISO 8601 with UTC time zone.)

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.

4.1.1 - IsActive


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

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->IsActive

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive
[get]  OK
Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsActive`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

4.1.2 - IsOngoing


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

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->IsOngoing

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing
[get]  OK
Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing false
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.BatteryConditioning.IsOngoing`	VSS: Addressing nodes
Data type	`boolean`	VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

4.1.3 - RequestedMode


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode`
Description:	Defines requested mode for battery conditioning. INACTIVE - Battery conditioning inactive. FAST_CHARGING_PREPARATION - Battery conditioning for fast charging. DRIVING_PREPARATION - Battery conditioning for driving.
Comment:	The Mode and TargetTime can be used to calculate TargetTemperature and StartTime

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->RequestedMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode
[get]  OK
Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.TractionBattery.BatteryConditioning.RequestedMode

Data Type & Unit


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

Note: The string datatype is a character string.

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

4.1.4 - StartTime


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

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->StartTime

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime
[get]  OK
Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.BatteryConditioning.StartTime`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Unit	`iso8601`	VSS: Units
Label	ISO 8601
Description	Date and Time expressed as a string according to ISO 8601	VSS: Sensors & Actuators
Domain	datetime

Note: The string datatype is a character string.

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

4.1.5 - TargetTemperature


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature`
Description:	Target temperature for battery conditioning.
Comment:	Target temperature possibly differs between different modes as well as other factors. Allowed deviation from target temperature is implementation dependent.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->TargetTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature
[get]  OK
Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature 0
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTemperature

Data Type & Unit


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

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

4.1.6 - TargetTime


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

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->BatteryConditioning BatteryConditioning-->TargetTime

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime
[get]  OK
Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime Foo
[set]  OK

Digital Auto: Playground

playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.

Vehicle Model	Direct link to Vehicle Signal
ACME Car (EV) v0.1	Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.BatteryConditioning.TargetTime`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Unit	`iso8601`	VSS: Units
Label	ISO 8601
Description	Date and Time expressed as a string according to ISO 8601	VSS: Sensors & Actuators
Domain	datetime

Note: The string datatype is a character string.

Signal Information

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

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

UUID

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:


Enhancement request	Create COVESA GitHub Issue
Join COVESA	www.covesa.global
Discuss VSS on Slack	w3cauto.slack.com
VSS Data Experts on Google Groups	covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

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

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

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

4.3 - 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	work

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

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

4.5 - 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	work

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

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

4.7 - CellVoltage


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CellVoltage`
Description:	Voltage information for cells in the battery pack.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->CellVoltage

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CellVoltage is 0070210b80125f1a8e9473f8875fe3d1

Children

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

Vehicle.Powertrain.TractionBattery.CellVoltage.CellVoltages (Array of cell voltages. Length or array shall correspond to number of cells in vehicle.)
Vehicle.Powertrain.TractionBattery.CellVoltage.IdMax (Identifier of the battery cell with highest voltage.)
Vehicle.Powertrain.TractionBattery.CellVoltage.IdMin (Identifier of the battery cell with lowest voltage.)
Vehicle.Powertrain.TractionBattery.CellVoltage.Max (Current voltage of the battery cell with highest voltage.)
Vehicle.Powertrain.TractionBattery.CellVoltage.Min (Current voltage of the battery cell with lowest voltage.)

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.

4.7.1 - CellVoltages


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CellVoltage.CellVoltages`
Description:	Array of cell voltages. Length or array shall correspond to number of cells in vehicle.
Comment:	Cells are identified by relative position in array.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->CellVoltage CellVoltage-->CellVoltages

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.CellVoltage.CellVoltages`	VSS: Addressing nodes
Data type	`float[]`	VSS: Datatypes

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.CellVoltage.CellVoltages is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.CellVoltage.CellVoltages is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CellVoltage.CellVoltages is 1970692bc3a457f1b6f58aa53c905264

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CellVoltage.IdMax`
Description:	Identifier of the battery cell with highest voltage.
Comment:	Identifier is supposed to be relative index of the cell, starting with 0 the first cell.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->CellVoltage CellVoltage-->IdMax

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.CellVoltage.IdMax`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes

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

The vehicle signal Vehicle.Powertrain.TractionBattery.CellVoltage.IdMax is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CellVoltage.IdMax is c84a89bd5faa5e9cb0a9bf191bfeec9c

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CellVoltage.IdMin`
Description:	Identifier of the battery cell with lowest voltage.
Comment:	Identifier is supposed to be relative index of the cell, starting with 0 the first cell.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->CellVoltage CellVoltage-->IdMin

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.CellVoltage.IdMin`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes

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

The vehicle signal Vehicle.Powertrain.TractionBattery.CellVoltage.IdMin is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CellVoltage.IdMin is cbaef92ad3f55b20bc71188fba79d00d

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CellVoltage.Max`
Description:	Current voltage of the battery cell with highest voltage.

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

Data Type & Unit


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

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CellVoltage.Max is bde40aa6b442580db3c0d4c1efed8a09

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.CellVoltage.Min`
Description:	Current voltage of the battery cell with lowest voltage.

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

Data Type & Unit


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

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.CellVoltage.Min is b868f28cc42a5ba28a127647cd16cb93

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.8 - 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.AveragePower (Average charging power of last or current charging event.)
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.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.ChargingPort (Properties related to a particular charging port available in the vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.EvseId (EVSE charging point ID (without separators) of last or current charging event according to ISO 15118-2 Annex H.)
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.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.Location (Location of last or current charging event.)
Vehicle.Powertrain.TractionBattery.Charging.MaxPower (Maximum charging power of last or current charging event.)
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.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.

4.8.1 - AveragePower


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.AveragePower`
Description:	Average charging power of last or current charging event.

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

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.AveragePower`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kW`	VSS: Units
Label	kilowatt
Description	Power measured in kilowatts	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.AveragePower is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.AveragePower is acc1728f1839516287d86975f679ec33

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

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

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

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

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

4.8.3 - 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 100
[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
Default 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

4.8.4 - 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	Velocity measured in kilometers per hours	VSS: Sensors & Actuators
Domain	velocity

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

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

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

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

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

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

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

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

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

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

4.8.6 - EvseId


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.EvseId`
Description:	EVSE charging point ID (without separators) of last or current charging event according to ISO 15118-2 Annex H.
Comment:	Length of id between 7 and 37 characters. ZZ00000 to be used if SECC cannot provide id

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

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.EvseId is 5cd32296574a5f0db05434ecb24ea778

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

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

4.8.9 - Location


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Location`
Description:	Location of last or current charging event.
Comment:	This may depending on implementation represent the location of (the charge port of) the vehicle during charging, or the actual location of the charger/load connected to the vehicle.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Location is 5fef3925dfd55bbeb5d6590181fbbad8

Children

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

Vehicle.Powertrain.TractionBattery.Charging.Location.Altitude (Altitude relative to WGS 84 reference ellipsoid of last or current charging event.)
Vehicle.Powertrain.TractionBattery.Charging.Location.Latitude (Latitude of last or current charging event in WGS 84 geodetic coordinates.)
Vehicle.Powertrain.TractionBattery.Charging.Location.Longitude (Longitude of last or current charging event in WGS 84 geodetic coordinates.)

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.

4.8.9.1 - Altitude


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Location.Altitude`
Description:	Altitude relative to WGS 84 reference ellipsoid of last or current charging event.

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

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.Location.Altitude`	VSS: Addressing nodes
Data type	`double`	VSS: Datatypes
Unit	`m`	VSS: Units
Label	meter
Description	Length measured in meters	VSS: Sensors & Actuators
Domain	length

Note: The double datatype is a double precision floating point number which technically allows values between -1.7e ^ -300 and 1.7e ^ 300

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Location.Altitude is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Location.Altitude is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Location.Altitude is eed551cc893a5e12ba6a3b977d93cc03

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Location.Latitude`
Description:	Latitude of last or current charging event in WGS 84 geodetic coordinates.

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

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.Location.Latitude`	VSS: Addressing nodes
Data type	`double`	VSS: Datatypes
Unit	`degrees`	VSS: Units
Label	degree
Description	Angle measured in degrees	VSS: Sensors & Actuators
Domain	angle
Minimum value	`-90`	VSS: Sensors & Actuators
Maximum value	`90`	VSS: Sensors & Actuators

Note: The double datatype is a double precision floating point number which technically allows values between -1.7e ^ -300 and 1.7e ^ 300

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Location.Latitude is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Location.Latitude is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Location.Latitude is 33fc44c112735cc2bc0ee02f1786d948

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.Location.Longitude`
Description:	Longitude of last or current charging event in WGS 84 geodetic coordinates.

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

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.Location.Longitude`	VSS: Addressing nodes
Data type	`double`	VSS: Datatypes
Unit	`degrees`	VSS: Units
Label	degree
Description	Angle measured in degrees	VSS: Sensors & Actuators
Domain	angle
Minimum value	`-180`	VSS: Sensors & Actuators
Maximum value	`180`	VSS: Sensors & Actuators

Note: The double datatype is a double precision floating point number which technically allows values between -1.7e ^ -300 and 1.7e ^ 300

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Location.Longitude is a Sensor.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.Location.Longitude is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.Location.Longitude is 42db7473630c506eb5528c9bcaf8e8c6

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

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

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

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

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

4.8.11 - MaxPower


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.MaxPower`
Description:	Maximum charging power of last or current charging event.

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

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.MaxPower`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`kW`	VSS: Units
Label	kilowatt
Description	Power measured in kilowatts	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.MaxPower is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.MaxPower is a8abad6796d55f8abe925c1efd76280a

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

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

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

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

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

4.8.15.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
Unit	`iso8601`	VSS: Units
Label	ISO 8601
Description	Date and Time expressed as a string according to ISO 8601	VSS: Sensors & Actuators
Domain	datetime

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.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

4.8.16 - 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	Duration measured in seconds	VSS: Sensors & Actuators
Domain	duration

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

4.8.17 - ChargingPort


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort is a13011fe556b5e3388fec7d183022917

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition (Properties related to a particular charging port available in the vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft (Properties related to a particular charging port available in the vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle (Properties related to a particular charging port available in the vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight (Properties related to a particular charging port available in the vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft (Properties related to a particular charging port available in the vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle (Properties related to a particular charging port available in the vehicle.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight (Properties related to a particular charging port available in the vehicle.)

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.

4.8.17.1 - AnyPosition


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition is 4be233c9affa582b807eedc10aa844f7

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsChargingCableConnected (Indicates whether a charging cable is physically connected to a particular charging port or not.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsFlapOpen (Status of the charging port flap(s).)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.SupportedInletTypes (A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)

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.

4.8.17.1.1 - IsChargingCableLocked


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.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-->ChargingPort ChargingPort-->AnyPosition AnyPosition-->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.ChargingPort.AnyPosition.IsChargingCableLocked
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.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.ChargingPort.AnyPosition.IsChargingCableLocked

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsChargingCableLocked is 8c18465515465c98b8c23c99def98180

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsChargingCableConnected`
Description:	Indicates whether a charging cable is physically connected to a particular charging port or not.

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsChargingCableConnected is 21b78caf134f57cebc53b1e7823818b0

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsFlapOpen`
Description:	Status of the charging port flap(s).
Comment:	True = at least one flap of this port is open, False = All flaps of this port are closed.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->AnyPosition AnyPosition-->IsFlapOpen

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.IsFlapOpen is e57026369dc05a9d8193a4058432f799

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.SupportedInletTypes`
Description:	A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging ports. 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 ports/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 for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->AnyPosition AnyPosition-->SupportedInletTypes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.SupportedInletTypes`	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.ChargingPort.AnyPosition.SupportedInletTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.SupportedInletTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.AnyPosition.SupportedInletTypes is 8a3cb2e774785ec9af911df6379c9068

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft is 5e04ade2f801500b9f8fecf75b0adc89

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsChargingCableConnected (Indicates whether a charging cable is physically connected to a particular charging port or not.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsFlapOpen (Status of the charging port flap(s).)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.SupportedInletTypes (A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)

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.

4.8.17.2.1 - IsChargingCableConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsChargingCableConnected`
Description:	Indicates whether a charging cable is physically connected to a particular charging port or not.

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsChargingCableConnected is 7f547e3ddd6a538abb1ff6c2c7e0ce71

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.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-->ChargingPort ChargingPort-->FrontLeft FrontLeft-->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.ChargingPort.FrontLeft.IsChargingCableLocked
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.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.ChargingPort.FrontLeft.IsChargingCableLocked

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsChargingCableLocked is 7fc1498d306656249aa6bb355d614bd1

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsFlapOpen`
Description:	Status of the charging port flap(s).
Comment:	True = at least one flap of this port is open, False = All flaps of this port are closed.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->FrontLeft FrontLeft-->IsFlapOpen

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.IsFlapOpen is f111f8ed42695957b44d392471a346e2

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.SupportedInletTypes`
Description:	A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging ports. 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 ports/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 for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->FrontLeft FrontLeft-->SupportedInletTypes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.SupportedInletTypes`	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.ChargingPort.FrontLeft.SupportedInletTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.SupportedInletTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontLeft.SupportedInletTypes is a368cf97e9a45e988dc4bf8a512c440e

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle is d5b0b57da3fa57eb847f5f9a828688f5

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected (Indicates whether a charging cable is physically connected to a particular charging port or not.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen (Status of the charging port flap(s).)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes (A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)

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.

4.8.17.3.1 - IsChargingCableConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected`
Description:	Indicates whether a charging cable is physically connected to a particular charging port or not.

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableConnected is 6c1c71bf0be25246a98bdc80ebcb2446

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.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-->ChargingPort ChargingPort-->FrontMiddle FrontMiddle-->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.ChargingPort.FrontMiddle.IsChargingCableLocked
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.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.ChargingPort.FrontMiddle.IsChargingCableLocked

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsChargingCableLocked is bb1158a3adc95f7ba5efc8ee3b78975b

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen`
Description:	Status of the charging port flap(s).
Comment:	True = at least one flap of this port is open, False = All flaps of this port are closed.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->FrontMiddle FrontMiddle-->IsFlapOpen

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.IsFlapOpen is 597e986207e45d18bfa10c84b5cddbe8

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes`
Description:	A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging ports. 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 ports/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 for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->FrontMiddle FrontMiddle-->SupportedInletTypes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes`	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.ChargingPort.FrontMiddle.SupportedInletTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontMiddle.SupportedInletTypes is 59bf1b00e04850f4a37a3cd22ae3d52e

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight is a4e965cb3a6f56839481e06b28085e8b

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsChargingCableConnected (Indicates whether a charging cable is physically connected to a particular charging port or not.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsFlapOpen (Status of the charging port flap(s).)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.SupportedInletTypes (A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)

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.

4.8.17.4.1 - IsChargingCableConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsChargingCableConnected`
Description:	Indicates whether a charging cable is physically connected to a particular charging port or not.

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsChargingCableConnected is 2540a4f42eee5b70869eb79090ea8270

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.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-->ChargingPort ChargingPort-->FrontRight FrontRight-->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.ChargingPort.FrontRight.IsChargingCableLocked
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.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.ChargingPort.FrontRight.IsChargingCableLocked

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsChargingCableLocked is f65652b46a1d5e01a5b032a714bb1ba5

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsFlapOpen`
Description:	Status of the charging port flap(s).
Comment:	True = at least one flap of this port is open, False = All flaps of this port are closed.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->FrontRight FrontRight-->IsFlapOpen

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.IsFlapOpen is ebaddff71851543e93053d387bd7a984

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.SupportedInletTypes`
Description:	A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging ports. 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 ports/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 for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->FrontRight FrontRight-->SupportedInletTypes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.SupportedInletTypes`	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.ChargingPort.FrontRight.SupportedInletTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.SupportedInletTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.FrontRight.SupportedInletTypes is 86b84137f1825191b81985719bbbaaf2

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft is 9b4c66527fe651df8be6f86a4d23b2c2

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsChargingCableConnected (Indicates whether a charging cable is physically connected to a particular charging port or not.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsFlapOpen (Status of the charging port flap(s).)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.SupportedInletTypes (A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)

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.

4.8.17.5.1 - IsChargingCableConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsChargingCableConnected`
Description:	Indicates whether a charging cable is physically connected to a particular charging port or not.

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsChargingCableConnected is 5ae14eb72e95523cab93ba3c1d218b73

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.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-->ChargingPort ChargingPort-->RearLeft RearLeft-->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.ChargingPort.RearLeft.IsChargingCableLocked
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.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.ChargingPort.RearLeft.IsChargingCableLocked

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsChargingCableLocked is e2e89259fb865b208e6724c64f68bb4f

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsFlapOpen`
Description:	Status of the charging port flap(s).
Comment:	True = at least one flap of this port is open, False = All flaps of this port are closed.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->RearLeft RearLeft-->IsFlapOpen

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.IsFlapOpen is f930e7ffdcee5cb9a7eafff7d4e14395

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.SupportedInletTypes`
Description:	A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging ports. 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 ports/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 for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->RearLeft RearLeft-->SupportedInletTypes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.SupportedInletTypes`	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.ChargingPort.RearLeft.SupportedInletTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.SupportedInletTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearLeft.SupportedInletTypes is 9375b2c93d7852cf928cad9adba47331

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle is 26d619a347255f8bbc321c0771d021c5

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsChargingCableConnected (Indicates whether a charging cable is physically connected to a particular charging port or not.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsFlapOpen (Status of the charging port flap(s).)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.SupportedInletTypes (A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)

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.

4.8.17.6.1 - IsChargingCableConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsChargingCableConnected`
Description:	Indicates whether a charging cable is physically connected to a particular charging port or not.

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsChargingCableConnected is 99c6d6efc2595b8c9f66f465c326ba42

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.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-->ChargingPort ChargingPort-->RearMiddle RearMiddle-->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.ChargingPort.RearMiddle.IsChargingCableLocked
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.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.ChargingPort.RearMiddle.IsChargingCableLocked

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsChargingCableLocked is 5f5f0bf7734d576f92b4e26e51b2f381

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsFlapOpen`
Description:	Status of the charging port flap(s).
Comment:	True = at least one flap of this port is open, False = All flaps of this port are closed.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->RearMiddle RearMiddle-->IsFlapOpen

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.IsFlapOpen is 23cd37d0d75c5cddb92ac128b2f035c3

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.SupportedInletTypes`
Description:	A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging ports. 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 ports/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 for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->RearMiddle RearMiddle-->SupportedInletTypes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.SupportedInletTypes`	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.ChargingPort.RearMiddle.SupportedInletTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.SupportedInletTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearMiddle.SupportedInletTypes is 469d64af0d055ba3a264657afdd15890

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight`
Description:	Properties related to a particular charging port available in the vehicle.
Comment:	If a vehicle has a single charging port, then use the instance AnyPosition.

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight is 758a5cabe3b65f67a9a37c510113a86b

Children

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

Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsChargingCableConnected (Indicates whether a charging cable is physically connected to a particular charging port or not.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsChargingCableLocked (Is charging cable locked to prevent removal.)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsFlapOpen (Status of the charging port flap(s).)
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.SupportedInletTypes (A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.)

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.

4.8.17.7.1 - IsChargingCableConnected


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsChargingCableConnected`
Description:	Indicates whether a charging cable is physically connected to a particular charging port or not.

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

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsChargingCableConnected is d44664c6bba25bb9b7e20f7cfd5cfcd6

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.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-->ChargingPort ChargingPort-->RearRight RearRight-->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.ChargingPort.RearRight.IsChargingCableLocked
[get]  OK
Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsChargingCableLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.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.ChargingPort.RearRight.IsChargingCableLocked

Data Type & Unit


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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsChargingCableLocked is ab74289f06c3518e82b6a61ba9943418

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsFlapOpen`
Description:	Status of the charging port flap(s).
Comment:	True = at least one flap of this port is open, False = All flaps of this port are closed.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->RearRight RearRight-->IsFlapOpen

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsFlapOpen is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.IsFlapOpen is 2e0de78f83525041bbb928f948050837

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


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.SupportedInletTypes`
Description:	A list of the supported (i.e., available) charging inlets in a particular charging port. IEC types refer to IEC 62196, GBT refers to GB/T 20234.
Comment:	A vehicle may have multiple charging ports. 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 ports/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 for charging ports not included in the list above. For additional information see https://en.wikipedia.org/wiki/IEC_62196.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->Charging Charging-->ChargingPort ChargingPort-->RearRight RearRight-->SupportedInletTypes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.SupportedInletTypes`	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.ChargingPort.RearRight.SupportedInletTypes is an Attribute.

The vehicle signal Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.SupportedInletTypes is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Charging.ChargingPort.RearRight.SupportedInletTypes is 55fff0e7055e53fe8ed3da915b60ab18

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

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

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

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

4.12 - ErrorCodes


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.ErrorCodes`
Description:	Current error codes related to the battery, if any.
Comment:	Error code format is not defined, it may be DTCs according to OBD II (SAE-J2012DA_201812) standard ([P

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->ErrorCodes

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.ErrorCodes`	VSS: Addressing nodes
Data type	`string[]`	VSS: Datatypes

Signal Information

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.ErrorCodes is bbc1f199a5965e5eb4f99709052a7cc4

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

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

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

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

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

4.17 - 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	voltage

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

4.18 - 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	work

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

4.19 - 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	voltage

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

4.20 - 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.21 - 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
Unit	`iso8601`	VSS: Units
Label	ISO 8601
Description	Date and Time expressed as a string according to ISO 8601	VSS: Sensors & Actuators
Domain	datetime

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.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

4.22 - 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	Length measured in meters	VSS: Sensors & Actuators
Domain	length

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.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

4.23 - 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.CurrentEnergy (Physical state of charge of high voltage battery expressed in kWh.)
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.

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

4.23.2 - CurrentEnergy


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.StateOfCharge.CurrentEnergy`
Description:	Physical state of charge of high voltage battery expressed in kWh.
Comment:	Current energy could be calculated as .StateOfCharge.Current * .NetCapacity.

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

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.StateOfCharge.CurrentEnergy`	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	work

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.StateOfCharge.CurrentEnergy is 435ef8dbe4425450ae1ff6215fc9e40b

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

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

4.25 - 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.CellTemperature (Array of cell temperatures. Length or array shall correspond to number of cells in vehicle.)
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.

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

4.25.2 - CellTemperature


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.Temperature.CellTemperature`
Description:	Array of cell temperatures. Length or array shall correspond to number of cells in vehicle.
Comment:	Cells are identified by relative position in array.

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

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.Temperature.CellTemperature`	VSS: Addressing nodes
Data type	`float[]`	VSS: Datatypes

Signal Information

The vehicle signal Vehicle.Powertrain.TractionBattery.Temperature.CellTemperature is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.Temperature.CellTemperature is e92fede319da5e428f4bd024d7dd6970

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

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

4.26 - TimeRemaining


Full qualified VSS Path:	`Vehicle.Powertrain.TractionBattery.TimeRemaining`
Description:	Time remaining in seconds before the battery is empty.

flowchart LR Vehicle-->Powertrain Powertrain-->TractionBattery TractionBattery-->TimeRemaining

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

Data Type & Unit


Path	`Vehicle.Powertrain.TractionBattery.TimeRemaining`	VSS: Addressing nodes
Data type	`uint32`	VSS: Datatypes
Unit	`s`	VSS: Units
Label	second
Description	Duration measured in seconds	VSS: Sensors & Actuators
Domain	duration

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

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

UUID

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

The UUID for Vehicle.Powertrain.TractionBattery.TimeRemaining is 7a51820010f35dcabe968e669173b27e

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


Full qualified VSS Path:	`Vehicle.Powertrain.AccumulatedBrakingEnergy`
Description:	The accumulated energy from regenerative braking over lifetime.

flowchart LR Vehicle-->Powertrain Powertrain-->AccumulatedBrakingEnergy

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.AccumulatedBrakingEnergy`	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	work

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

The vehicle signal Vehicle.Powertrain.AccumulatedBrakingEnergy is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.AccumulatedBrakingEnergy is 0dd466d28d3d5ad094f2015adafb91a5

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine`
Description:	Engine-specific data, stopping at the bell housing.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine is 159e2e3e75f0590f95b4d2f6cfae54b5

Children

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

Vehicle.Powertrain.CombustionEngine.AspirationType (Type of aspiration (natural, turbocharger, supercharger etc).)
Vehicle.Powertrain.CombustionEngine.Bore (Bore in millimetres.)
Vehicle.Powertrain.CombustionEngine.CompressionRatio (Engine compression ratio, specified in the format ‘X:1’, e.g. ‘9.2:1’.)
Vehicle.Powertrain.CombustionEngine.Configuration (Engine configuration.)
Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid (Signals related to Diesel Exhaust Fluid (DEF). DEF is called AUS32 in ISO 22241.)
Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter (Diesel Particulate Filter signals.)
Vehicle.Powertrain.CombustionEngine.Displacement (Displacement in cubic centimetres.)
Vehicle.Powertrain.CombustionEngine.EOP (Engine oil pressure.)
Vehicle.Powertrain.CombustionEngine.EngineCode (Engine code designation, as specified by vehicle manufacturer.)
Vehicle.Powertrain.CombustionEngine.EngineCoolant (Signals related to the engine coolant)
Vehicle.Powertrain.CombustionEngine.EngineHours (Accumulated time during engine lifetime with ’engine speed (rpm) > 0’.)
Vehicle.Powertrain.CombustionEngine.EngineOil (Signals related to the engine oil)
Vehicle.Powertrain.CombustionEngine.IdleHours (Accumulated idling time during engine lifetime. Definition of idling is not standardized.)
Vehicle.Powertrain.CombustionEngine.IsRunning (Engine Running. True if engine is rotating (Speed > 0).)
Vehicle.Powertrain.CombustionEngine.MAF (Grams of air drawn into engine per second.)
Vehicle.Powertrain.CombustionEngine.MAP (Manifold absolute pressure possibly boosted using forced induction.)
Vehicle.Powertrain.CombustionEngine.MaxPower (Peak power, in kilowatts, that engine can generate.)
Vehicle.Powertrain.CombustionEngine.MaxTorque (Peak torque, in newton meter, that the engine can generate.)
Vehicle.Powertrain.CombustionEngine.NumberOfCylinders (Number of cylinders.)
Vehicle.Powertrain.CombustionEngine.NumberOfValvesPerCylinder (Number of valves per cylinder.)
Vehicle.Powertrain.CombustionEngine.Power (Current engine power output. Shall be reported as 0 during engine breaking.)
Vehicle.Powertrain.CombustionEngine.Speed (Engine speed measured as rotations per minute.)
Vehicle.Powertrain.CombustionEngine.StrokeLength (Stroke length in millimetres.)
Vehicle.Powertrain.CombustionEngine.TPS (Current throttle position.)
Vehicle.Powertrain.CombustionEngine.Torque (Current engine torque. Shall be reported as a negative number during engine breaking.)

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.

6.1 - AspirationType


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.AspirationType`
Description:	Type of aspiration (natural, turbocharger, supercharger etc).

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->AspirationType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.AspirationType`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Default value	`UNKNOWN`	VSS: Sensors & Actuators
Allowed values	`['UNKNOWN', 'NATURAL', 'SUPERCHARGER', 'TURBOCHARGER']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.AspirationType is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.AspirationType is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.AspirationType is 3ca6a8ff30275c20a9d8d6d6829574eb

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.Bore`
Description:	Bore in millimetres.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->Bore

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.Bore`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length

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.CombustionEngine.Bore is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.Bore is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.Bore is 1618fb16035b5464961570cc1afd934e

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.CompressionRatio`
Description:	Engine compression ratio, specified in the format ‘X:1’, e.g. ‘9.2:1’.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->CompressionRatio

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.CompressionRatio`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.CompressionRatio is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.CompressionRatio is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.CompressionRatio is ead42922511051a0a0a1b634781f3c09

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.Configuration`
Description:	Engine configuration.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->Configuration

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.Configuration`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Default value	`UNKNOWN`	VSS: Sensors & Actuators
Allowed values	`['UNKNOWN', 'STRAIGHT', 'V', 'BOXER', 'W', 'ROTARY', 'RADIAL', 'SQUARE', 'H', 'U', 'OPPOSED', 'X']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.Configuration is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.Configuration is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.Configuration is 586be4567fe059ee9e6cf42901c2e773

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid`
Description:	Signals related to Diesel Exhaust Fluid (DEF). DEF is called AUS32 in ISO 22241.
Comment:	In retail and marketing other names are typically used for the fluid.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselExhaustFluid

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

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid is 81d8eec46d9357a3b1064bfb5d070fa2

Children

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

Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Capacity (Capacity in liters of the Diesel Exhaust Fluid Tank.)
Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.IsLevelLow (Indicates if the Diesel Exhaust Fluid level is low. True if level is low. Definition of low is vehicle dependent.)
Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Level (Level of the Diesel Exhaust Fluid tank as percent of capacity. 0 = empty. 100 = full.)
Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Range (Remaining range in meters of the Diesel Exhaust Fluid present in the vehicle.)

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.

6.5.1 - Capacity


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Capacity`
Description:	Capacity in liters of the Diesel Exhaust Fluid Tank.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselExhaustFluid DieselExhaustFluid-->Capacity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Capacity`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Capacity is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Capacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Capacity is 863c16ad452b5cf5b7a37f58bdda14c3

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.IsLevelLow`
Description:	Indicates if the Diesel Exhaust Fluid level is low. True if level is low. Definition of low is vehicle dependent.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselExhaustFluid DieselExhaustFluid-->IsLevelLow

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.IsLevelLow`	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.CombustionEngine.DieselExhaustFluid.IsLevelLow is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.IsLevelLow is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.IsLevelLow is 811af3fe4f7f5270b4119bb66cff8759

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Level`
Description:	Level of the Diesel Exhaust Fluid tank as percent of capacity. 0 = empty. 100 = full.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselExhaustFluid DieselExhaustFluid-->Level

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Level`	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.CombustionEngine.DieselExhaustFluid.Level is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Level is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Level is f5b0269b58ff5a8e8399f6d96963a3b6

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Range`
Description:	Remaining range in meters of the Diesel Exhaust Fluid present in the vehicle.

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

Data Type & Unit


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

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Range is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Range is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselExhaustFluid.Range is 124afbee975c5a67b316413f7b805eac

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter`
Description:	Diesel Particulate Filter signals.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselParticulateFilter

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

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter is eeddd99ad6475b1a92b9ec7bd7cefdbd

Children

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

Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.DeltaPressure (Delta Pressure of Diesel Particulate Filter.)
Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.InletTemperature (Inlet temperature of Diesel Particulate Filter.)
Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.OutletTemperature (Outlet temperature of Diesel Particulate Filter.)

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.

6.6.1 - DeltaPressure


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.DeltaPressure`
Description:	Delta Pressure of Diesel Particulate Filter.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselParticulateFilter DieselParticulateFilter-->DeltaPressure

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.DeltaPressure`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`Pa`	VSS: Units
Label	pascal
Description	Pressure measured in pascal	VSS: Sensors & Actuators
Domain	pressure

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.CombustionEngine.DieselParticulateFilter.DeltaPressure is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.DeltaPressure is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.DeltaPressure is a6f476775c60531b93acb835e0bc6ab6

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.InletTemperature`
Description:	Inlet temperature of Diesel Particulate Filter.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselParticulateFilter DieselParticulateFilter-->InletTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.InletTemperature`	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.CombustionEngine.DieselParticulateFilter.InletTemperature is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.InletTemperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.InletTemperature is 70e90d202d3054bd967e67dce95c8ef2

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.OutletTemperature`
Description:	Outlet temperature of Diesel Particulate Filter.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->DieselParticulateFilter DieselParticulateFilter-->OutletTemperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.OutletTemperature`	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.CombustionEngine.DieselParticulateFilter.OutletTemperature is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.OutletTemperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.DieselParticulateFilter.OutletTemperature is e2b7f9d97bec5c0d94ade71a5e2f6518

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.Displacement`
Description:	Displacement in cubic centimetres.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->Displacement

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.Displacement`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`cm^3`	VSS: Units
Label	cubic centimeters
Description	Volume measured in cubic centimeters	VSS: Sensors & Actuators
Domain	volume

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.CombustionEngine.Displacement is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.Displacement is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.Displacement is 94dbd928847150ab842c00fa5caaf272

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineCode`
Description:	Engine code designation, as specified by vehicle manufacturer.
Comment:	For hybrid vehicles the engine code may refer to the combination of combustion and electric engine.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineCode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineCode`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCode is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineCode is 4ec845911b8e5b64b2cb1d34063184de

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineCoolant`
Description:	Signals related to the engine coolant

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineCoolant

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

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineCoolant is 0f42d5e38b7f5406aeee8772d0d7efad

Children

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

Vehicle.Powertrain.CombustionEngine.EngineCoolant.Capacity (Engine coolant capacity in liters.)
Vehicle.Powertrain.CombustionEngine.EngineCoolant.Level (Engine coolant level.)
Vehicle.Powertrain.CombustionEngine.EngineCoolant.LifeRemaining (Remaining engine coolant life in seconds. Negative values can be used to indicate that lifetime has been exceeded.)
Vehicle.Powertrain.CombustionEngine.EngineCoolant.Temperature (Engine coolant temperature.)

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.

6.9.1 - Capacity


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineCoolant.Capacity`
Description:	Engine coolant capacity in liters.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineCoolant EngineCoolant-->Capacity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineCoolant.Capacity`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant.Capacity is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant.Capacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineCoolant.Capacity is ccd65190ed855f2ebc284421e11d6f97

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineCoolant.Level`
Description:	Engine coolant level.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineCoolant EngineCoolant-->Level

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineCoolant.Level`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['CRITICALLY_LOW', 'LOW', 'NORMAL']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant.Level is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant.Level is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineCoolant.Level is 6ebd8880882d5f8591dbe17958d14f60

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineCoolant.LifeRemaining`
Description:	Remaining engine coolant life in seconds. Negative values can be used to indicate that lifetime has been exceeded.
Comment:	In addition to this a signal a vehicle can report remaining time to service (including e.g. coolant change) by Vehicle.Service.TimeToService.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineCoolant EngineCoolant-->LifeRemaining

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineCoolant.LifeRemaining`	VSS: Addressing nodes
Data type	`int32`	VSS: Datatypes
Unit	`s`	VSS: Units
Label	second
Description	Duration measured in seconds	VSS: Sensors & Actuators
Domain	duration

Note: The int32 datatype is a signed 32-bit integer which technically allows values between -2147483648 and 2147483647 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant.LifeRemaining is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant.LifeRemaining is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineCoolant.LifeRemaining is a1c4e6e28af95b6da3e7562e62eb17e3

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineCoolant.Temperature`
Description:	Engine coolant temperature.

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolant.Temperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineCoolant.Temperature is 318fd0816f9155d8b4a956a3c61c5901

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineHours`
Description:	Accumulated time during engine lifetime with ’engine speed (rpm) > 0'.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineHours

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineHours`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`h`	VSS: Units
Label	hour
Description	Duration measured in hours	VSS: Sensors & Actuators
Domain	duration

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineHours is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineHours is a23a62e24f58514d961890f53262e4e0

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineOil`
Description:	Signals related to the engine oil

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineOil

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

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil is a Branch.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineOil is 2f8c5bd3204c500cb71244bd69a8c463

Children

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

Vehicle.Powertrain.CombustionEngine.EngineOil.Capacity (Engine oil capacity in liters.)
Vehicle.Powertrain.CombustionEngine.EngineOil.Level (Engine oil level.)
Vehicle.Powertrain.CombustionEngine.EngineOil.LifeRemaining (Remaining engine oil life in seconds. Negative values can be used to indicate that lifetime has been exceeded.)
Vehicle.Powertrain.CombustionEngine.EngineOil.Temperature (EOT, Engine oil temperature.)

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.

6.11.1 - Capacity


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineOil.Capacity`
Description:	Engine oil capacity in liters.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineOil EngineOil-->Capacity

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineOil.Capacity`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`l`	VSS: Units
Label	liter
Description	Volume measured in liters	VSS: Sensors & Actuators
Domain	volume

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil.Capacity is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil.Capacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineOil.Capacity is 4994d5d3b6135a96b5be175d9e6581b0

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineOil.Level`
Description:	Engine oil level.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineOil EngineOil-->Level

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineOil.Level`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['CRITICALLY_LOW', 'LOW', 'NORMAL', 'HIGH', 'CRITICALLY_HIGH']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil.Level is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil.Level is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineOil.Level is 3200804bd8ad5741bbd8a393b9fa8e44

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineOil.LifeRemaining`
Description:	Remaining engine oil life in seconds. Negative values can be used to indicate that lifetime has been exceeded.
Comment:	In addition to this a signal a vehicle can report remaining time to service (including e.g. oil change) by Vehicle.Service.TimeToService.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineOil EngineOil-->LifeRemaining

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EngineOil.LifeRemaining`	VSS: Addressing nodes
Data type	`int32`	VSS: Datatypes
Unit	`s`	VSS: Units
Label	second
Description	Duration measured in seconds	VSS: Sensors & Actuators
Domain	duration

Note: The int32 datatype is a signed 32-bit integer which technically allows values between -2147483648 and 2147483647 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil.LifeRemaining is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil.LifeRemaining is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineOil.LifeRemaining is 5acb9268489850acb2eee1b7f663aea3

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EngineOil.Temperature`
Description:	EOT, Engine oil temperature.

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOil.Temperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineOil.Temperature is 3390b3e7b21451c6938d89433e8dd033

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.EOP`
Description:	Engine oil pressure.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EOP

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.EOP`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.EOP is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EOP is 76c7039dc7975ec3a003f0f4a04895ec

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.IdleHours`
Description:	Accumulated idling time during engine lifetime. Definition of idling is not standardized.
Comment:	Vehicles may calculate accumulated idle time for an engine. It might be based on engine speed (rpm) below a certain limit or any other mechanism.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->IdleHours

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.IdleHours`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`h`	VSS: Units
Label	hour
Description	Duration measured in hours	VSS: Sensors & Actuators
Domain	duration

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.IdleHours is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.IdleHours is 6caa3d7e669c5cc6aecd4a6be9a302d4

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.IsRunning`
Description:	Engine Running. True if engine is rotating (Speed > 0).

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->IsRunning

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.CombustionEngine.IsRunning is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.IsRunning is 57652c27679757398c44d56af7a044d3

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.MAF`
Description:	Grams of air drawn into engine per second.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->MAF

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.MAF`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`g/s`	VSS: Units
Label	grams per second
Description	Mass per time measured in grams per second	VSS: Sensors & Actuators
Domain	mass-per-time

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.MAF is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.MAF is 1e222ed8c48b5dcea60e43ac8af7d6df

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.MAP`
Description:	Manifold absolute pressure possibly boosted using forced induction.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->MAP

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.MAP`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kPa`	VSS: Units
Label	kilopascal
Description	Pressure measured in kilopascal	VSS: Sensors & Actuators
Domain	pressure

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.MAP is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.MAP is 28d4354fa34056369acb857aa7cc76ac

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.MaxPower`
Description:	Peak power, in kilowatts, that engine can generate.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->MaxPower

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.MaxPower`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kW`	VSS: Units
Label	kilowatt
Description	Power measured in kilowatts	VSS: Sensors & Actuators
Domain	power
Default value	`0`	VSS: Sensors & Actuators

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.CombustionEngine.MaxPower is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.MaxPower is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.MaxPower is 81fbdd5e90f557a38b96578a38dc137d

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.MaxTorque`
Description:	Peak torque, in newton meter, that the engine can generate.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->MaxTorque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.MaxTorque`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`Nm`	VSS: Units
Label	newton meter
Description	Torque measured in newton meters	VSS: Sensors & Actuators
Domain	torque
Default value	`0`	VSS: Sensors & Actuators

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.CombustionEngine.MaxTorque is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.MaxTorque is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.MaxTorque is 471cd478c1e8597f8e97c85b4e4ebe26

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.NumberOfCylinders`
Description:	Number of cylinders.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->NumberOfCylinders

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.NumberOfCylinders`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes

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.CombustionEngine.NumberOfCylinders is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.NumberOfCylinders is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.NumberOfCylinders is b2cd342c218257e88d214cdb511df82b

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.NumberOfValvesPerCylinder`
Description:	Number of valves per cylinder.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->NumberOfValvesPerCylinder

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.NumberOfValvesPerCylinder`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes

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.CombustionEngine.NumberOfValvesPerCylinder is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.NumberOfValvesPerCylinder is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.NumberOfValvesPerCylinder is 44633204726e561ca21beff31f3fef80

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.Power`
Description:	Current engine power output. Shall be reported as 0 during engine breaking.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->Power

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.Power`	VSS: Addressing nodes
Data type	`uint16`	VSS: Datatypes
Unit	`kW`	VSS: Units
Label	kilowatt
Description	Power measured in kilowatts	VSS: Sensors & Actuators
Domain	power

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.Power is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.Power is 20e8b5d2187758c2848ed421248c180d

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.Speed`
Description:	Engine speed measured as rotations per minute.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->Speed

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.Speed`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`rpm`	VSS: Units
Label	revolutions per minute
Description	Rotational speed measured in revolutions per minute	VSS: Sensors & Actuators
Domain	rotational-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.CombustionEngine.Speed is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.Speed is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.Speed is 557ce24c5a4d51cc825059c948ac9e29

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.StrokeLength`
Description:	Stroke length in millimetres.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->StrokeLength

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.StrokeLength`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`mm`	VSS: Units
Label	millimeter
Description	Length measured in millimeters	VSS: Sensors & Actuators
Domain	length

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.CombustionEngine.StrokeLength is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.StrokeLength is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.StrokeLength is 1bdfdab7904d51ed93e101b84ea54ddf

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.Torque`
Description:	Current engine torque. Shall be reported as a negative number during engine breaking.
Comment:	During engine breaking the engine delivers a negative torque to the transmission.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->Torque

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.Torque`	VSS: Addressing nodes
Data type	`int16`	VSS: Datatypes
Unit	`Nm`	VSS: Units
Label	newton meter
Description	Torque measured in newton meters	VSS: Sensors & Actuators
Domain	torque

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.CombustionEngine.Torque is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.Torque is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.Torque is b81f504bdb57513299ae6e9402ec7bcd

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


Full qualified VSS Path:	`Vehicle.Powertrain.CombustionEngine.TPS`
Description:	Current throttle position.

flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->TPS

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.CombustionEngine.TPS`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
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.CombustionEngine.TPS is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.TPS is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.TPS is 1ddb77860de558b4876ffb399a442bda

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


Full qualified VSS Path:	`Vehicle.Powertrain.IsAutoPowerOptimize`
Description:	Auto Power Optimization Flag When set to ’true’, the system enables automatic power optimization, dynamically adjusting the power optimization level based on runtime conditions or features managed by the OEM. When set to ‘false’, manual control of the power optimization level is allowed.

flowchart LR Vehicle-->Powertrain Powertrain-->IsAutoPowerOptimize

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.IsAutoPowerOptimize is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.IsAutoPowerOptimize is 2f76567bacce582aac9d9e62da78ce9c

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


Full qualified VSS Path:	`Vehicle.Powertrain.PowerOptimizeLevel`
Description:	Power optimization level for this branch/subsystem. A higher number indicates more aggressive power optimization. Level 0 indicates that all functionality is enabled, no power optimization enabled. Level 10 indicates most aggressive power optimization mode, only essential functionality enabled.

flowchart LR Vehicle-->Powertrain Powertrain-->PowerOptimizeLevel

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.PowerOptimizeLevel`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Minimum value	`0`	VSS: Sensors & Actuators
Maximum value	`10`	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.PowerOptimizeLevel is an Actuator.

The vehicle signal Vehicle.Powertrain.PowerOptimizeLevel is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.PowerOptimizeLevel is d740b02e2fb35c07bf88a6e5ebe2f6e4

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


Full qualified VSS Path:	`Vehicle.Powertrain.Range`
Description:	Remaining range in meters using all energy sources available in the vehicle.

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

Data Type & Unit


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

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.Range is a Sensor.

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

UUID

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

The UUID for Vehicle.Powertrain.Range is ea4b6de772d65d20b1fa611f997aa7b8

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


Full qualified VSS Path:	`Vehicle.Powertrain.TimeRemaining`
Description:	Time remaining in seconds before all energy sources available in the vehicle are empty.

flowchart LR Vehicle-->Powertrain Powertrain-->TimeRemaining

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.TimeRemaining`	VSS: Addressing nodes
Data type	`uint32`	VSS: Datatypes
Unit	`s`	VSS: Units
Label	second
Description	Duration measured in seconds	VSS: Sensors & Actuators
Domain	duration

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

The vehicle signal Vehicle.Powertrain.TimeRemaining is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.TimeRemaining is f0154f73e2575ab5a39fd10a44ec7149

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission`
Description:	Transmission-specific data, stopping at the drive shafts.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission

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

Signal Information

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

UUID

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

The UUID for Vehicle.Powertrain.Transmission is 6b71e284b63a527caa6296a66e9fdd0c

Children

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

Vehicle.Powertrain.Transmission.ClutchEngagement (Clutch engagement. 0% = Clutch fully disengaged. 100% = Clutch fully engaged.)
Vehicle.Powertrain.Transmission.ClutchWear (Clutch wear as a percent. 0 = no wear. 100 = worn.)
Vehicle.Powertrain.Transmission.CurrentGear (The current gear. 0=Neutral, 1/2/..=Forward, -1/-2/..=Reverse.)
Vehicle.Powertrain.Transmission.DiffLockFrontEngagement (Front Diff Lock engagement. 0% = Diff lock fully disengaged. 100% = Diff lock fully engaged.)
Vehicle.Powertrain.Transmission.DiffLockRearEngagement (Rear Diff Lock engagement. 0% = Diff lock fully disengaged. 100% = Diff lock fully engaged.)
Vehicle.Powertrain.Transmission.DriveType (Drive type.)
Vehicle.Powertrain.Transmission.GearChangeMode (Is the gearbox in automatic or manual (paddle) mode.)
Vehicle.Powertrain.Transmission.GearCount (Number of forward gears in the transmission. -1 = CVT.)
Vehicle.Powertrain.Transmission.IsElectricalPowertrainEngaged (Is electrical powertrain mechanically connected/engaged to the drivetrain or not. False = Disconnected/Disengaged. True = Connected/Engaged.)
Vehicle.Powertrain.Transmission.IsLowRangeEngaged (Is gearbox in low range mode or not. False = Normal/High range engaged. True = Low range engaged.)
Vehicle.Powertrain.Transmission.IsParkLockEngaged (Is the transmission park lock engaged or not. False = Disengaged. True = Engaged.)
Vehicle.Powertrain.Transmission.PerformanceMode (Current gearbox performance mode.)
Vehicle.Powertrain.Transmission.SelectedGear (The selected gear. 0=Neutral, 1/2/..=Forward, -1/-2/..=Reverse, 126=Park, 127=Drive.)
Vehicle.Powertrain.Transmission.Temperature (The current gearbox temperature.)
Vehicle.Powertrain.Transmission.TorqueDistribution (Torque distribution between front and rear axle in percent. -100% = Full torque to front axle, 0% = 50:50 Front/Rear, 100% = Full torque to rear axle.)
Vehicle.Powertrain.Transmission.TravelledDistance (Odometer reading, total distance travelled during the lifetime of the transmission.)
Vehicle.Powertrain.Transmission.Type (Transmission type.)

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.

11.1 - ClutchEngagement


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.ClutchEngagement`
Description:	Clutch engagement. 0% = Clutch fully disengaged. 100% = Clutch fully engaged.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->ClutchEngagement

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.ClutchEngagement`	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.Transmission.ClutchEngagement is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.ClutchEngagement is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.ClutchEngagement is 2890bd4a2b6a56c19b62d7bd95151fc6

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.ClutchWear`
Description:	Clutch wear as a percent. 0 = no wear. 100 = worn.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->ClutchWear

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.ClutchWear`	VSS: Addressing nodes
Data type	`uint8`	VSS: Datatypes
Unit	`percent`	VSS: Units
Label	percent
Description	Relation measured in percent	VSS: Sensors & Actuators
Domain	relation
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.Transmission.ClutchWear is a Sensor.

The vehicle signal Vehicle.Powertrain.Transmission.ClutchWear is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.ClutchWear is c113405ad165571a9d53ae4cf55dc929

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.DiffLockFrontEngagement`
Description:	Front Diff Lock engagement. 0% = Diff lock fully disengaged. 100% = Diff lock fully engaged.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->DiffLockFrontEngagement

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.DiffLockFrontEngagement`	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.Transmission.DiffLockFrontEngagement is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.DiffLockFrontEngagement is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.DiffLockFrontEngagement is 5149afe37fbd5c24847b5820821abc02

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.DiffLockRearEngagement`
Description:	Rear Diff Lock engagement. 0% = Diff lock fully disengaged. 100% = Diff lock fully engaged.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->DiffLockRearEngagement

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.DiffLockRearEngagement`	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.Transmission.DiffLockRearEngagement is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.DiffLockRearEngagement is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.DiffLockRearEngagement is 197c939bd1405613b80179becec6db83

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.GearChangeMode`
Description:	Is the gearbox in automatic or manual (paddle) mode.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->GearChangeMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.GearChangeMode`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['MANUAL', 'AUTOMATIC']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.Transmission.GearChangeMode is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.GearChangeMode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.GearChangeMode is ff3c69378c2f598286e51f7dac13adaa

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.IsElectricalPowertrainEngaged`
Description:	Is electrical powertrain mechanically connected/engaged to the drivetrain or not. False = Disconnected/Disengaged. True = Connected/Engaged.
Comment:	In some hybrid solutions it is possible to disconnect/disengage the electrical powertrain mechanically to avoid induced voltage reaching a too high level when driving at high speed.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->IsElectricalPowertrainEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.IsElectricalPowertrainEngaged`	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.Transmission.IsElectricalPowertrainEngaged is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.IsElectricalPowertrainEngaged is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.IsElectricalPowertrainEngaged is 6660cf1d88d15430b1e7c8908a7b769b

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.IsLowRangeEngaged`
Description:	Is gearbox in low range mode or not. False = Normal/High range engaged. True = Low range engaged.
Comment:	The possibility to switch between low and high gear range is typically only available in heavy vehicles and off-road vehicles.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->IsLowRangeEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.IsLowRangeEngaged`	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.Transmission.IsLowRangeEngaged is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.IsLowRangeEngaged is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.IsLowRangeEngaged is 63ba7593926b574ebbe4f90b28557e78

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.IsParkLockEngaged`
Description:	Is the transmission park lock engaged or not. False = Disengaged. True = Engaged.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->IsParkLockEngaged

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.IsParkLockEngaged`	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.Transmission.IsParkLockEngaged is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.IsParkLockEngaged is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.IsParkLockEngaged is 1578da3f925e54ac9df978abd0195408

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.PerformanceMode`
Description:	Current gearbox performance mode.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->PerformanceMode

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.PerformanceMode`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['NORMAL', 'SPORT', 'ECONOMY', 'SNOW', 'RAIN']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.Transmission.PerformanceMode is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.PerformanceMode is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.PerformanceMode is 6b5cfd85cb595e559503ccf993be04dd

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.Temperature`
Description:	The current gearbox temperature.

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

Data Type & Unit


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

The vehicle signal Vehicle.Powertrain.Transmission.Temperature is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.Temperature is 4f5e48c3511b5e1abff11aa7ec62dd18

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.TorqueDistribution`
Description:	Torque distribution between front and rear axle in percent. -100% = Full torque to front axle, 0% = 50:50 Front/Rear, 100% = Full torque to rear axle.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->TorqueDistribution

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.TorqueDistribution`	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	`-100`	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.Transmission.TorqueDistribution is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.TorqueDistribution is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.TorqueDistribution is d3bcaaf973d3512287817049db9bd677

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.CurrentGear`
Description:	The current gear. 0=Neutral, 1/2/..=Forward, -1/-2/..=Reverse.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->CurrentGear

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.CurrentGear`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.Transmission.CurrentGear is a Sensor.

The vehicle signal Vehicle.Powertrain.Transmission.CurrentGear is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.CurrentGear is cd0ba1d772565e16bff46cbd5c9361da

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.DriveType`
Description:	Drive type.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->DriveType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.DriveType`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Default value	`UNKNOWN`	VSS: Sensors & Actuators
Allowed values	`['UNKNOWN', 'FORWARD_WHEEL_DRIVE', 'REAR_WHEEL_DRIVE', 'ALL_WHEEL_DRIVE']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.Transmission.DriveType is an Attribute.

The vehicle signal Vehicle.Powertrain.Transmission.DriveType is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.DriveType is 0e480b76fb2d5f8bb08fb586f90ee6ae

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.GearCount`
Description:	Number of forward gears in the transmission. -1 = CVT.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->GearCount

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.GearCount`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes
Default value	`0`	VSS: Sensors & Actuators

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.Transmission.GearCount is an Attribute.

The vehicle signal Vehicle.Powertrain.Transmission.GearCount is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.GearCount is 84293f40d3ed57f1a08992d97b1a9ccd

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.SelectedGear`
Description:	The selected gear. 0=Neutral, 1/2/..=Forward, -1/-2/..=Reverse, 126=Park, 127=Drive.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->SelectedGear

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.SelectedGear`	VSS: Addressing nodes
Data type	`int8`	VSS: Datatypes

Note: The int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).

Signal Information

The vehicle signal Vehicle.Powertrain.Transmission.SelectedGear is an Actuator.

The vehicle signal Vehicle.Powertrain.Transmission.SelectedGear is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.SelectedGear is 490fd99b9d5f562eb180c19e8cef5e12

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.TravelledDistance`
Description:	Odometer reading, total distance travelled during the lifetime of the transmission.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->TravelledDistance

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.TravelledDistance`	VSS: Addressing nodes
Data type	`float`	VSS: Datatypes
Unit	`km`	VSS: Units
Label	kilometer
Description	Length measured in kilometers	VSS: Sensors & Actuators
Domain	length

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

The vehicle signal Vehicle.Powertrain.Transmission.TravelledDistance is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.TravelledDistance is b9dd66f20c7f5b12a046766b94dc20c1

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


Full qualified VSS Path:	`Vehicle.Powertrain.Transmission.Type`
Description:	Transmission type.

flowchart LR Vehicle-->Powertrain Powertrain-->Transmission Transmission-->Type

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Transmission.Type`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Default value	`UNKNOWN`	VSS: Sensors & Actuators
Allowed values	`['UNKNOWN', 'SEQUENTIAL', 'H', 'AUTOMATIC', 'DSG', 'CVT']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.Transmission.Type is an Attribute.

The vehicle signal Vehicle.Powertrain.Transmission.Type is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Transmission.Type is f83b9e5464d85a0288fcb32c164d3c63

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


Full qualified VSS Path:	`Vehicle.Powertrain.Type`
Description:	Defines the powertrain type of the vehicle.
Comment:	For vehicles with a combustion engine (including hybrids) more detailed information on fuels supported can be found in FuelSystem.SupportedFuelTypes and FuelSystem.SupportedFuels.

flowchart LR Vehicle-->Powertrain Powertrain-->Type

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit


Path	`Vehicle.Powertrain.Type`	VSS: Addressing nodes
Data type	`string`	VSS: Datatypes
Allowed values	`['COMBUSTION', 'HYBRID', 'ELECTRIC']`	VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Powertrain.Type is an Attribute.

The vehicle signal Vehicle.Powertrain.Type is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.Type is 2a000da4204658a4a6e3ecd5176bdfba

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

Powertrain

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - FuelSystem

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - AbsoluteLevel

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.2 - AfterRefuelingFuelEconomy

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.3 - AverageConsumption

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.4 - ConsumptionSinceLastRefuel

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.5 - ConsumptionSinceStart

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.6 - CumulativeFuelEconomy

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.7 - DriveFuelEconomy

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground