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

Return to the regular view of this page.

FrontLeft
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft
Description: Electric Motor specific data.
Comment: Instance Front to be used if the vehicle has a motor located at the front of the vehicle, serving front and possibly also rear axle. Instance Rear to be used if the vehicle has a motor located at the rear of the vehicle, serving rear and possiblsy also front axle. Instances with Left/Right intended to be used if vehicle has separate motors for left and right side.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->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.ElectricMotor.FrontLeft

Signal Information

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

Children

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

1 - EngineCode
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCode
Description: Engine code designation, as specified by vehicle manufacturer.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.EngineCode
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCode

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCode is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2 - EngineCoolant
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant
Description: Signals related to the engine coolant (if applicable).
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.EngineCoolant

Signal Information

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

Children

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

2.1 - Capacity
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.Capacity
Description: Engine coolant capacity in liters.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.EngineCoolant.Capacity
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.Capacity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCoolant.Capacity

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCoolant.Capacity is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2.2 - Level
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.Level
Description: Engine coolant level.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.EngineCoolant.Level
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.Level: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCoolant.Level

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCoolant.Level is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2.3 - LifeRemaining
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.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-->FrontLeft FrontLeft-->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.FrontLeft.EngineCoolant.LifeRemaining
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.LifeRemaining: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCoolant.LifeRemaining

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCoolant.LifeRemaining is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2.4 - Temperature
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.Temperature
Description: Engine coolant temperature.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.EngineCoolant.Temperature
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.EngineCoolant.Temperature

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.EngineCoolant.Temperature VSS: Addressing nodes
Data type float VSS: Datatypes
Unit Celsius VSS: Units

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.FrontLeft.EngineCoolant.Temperature is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

3 - MaxPower
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxPower
Description: Peak power, in kilowatts, that motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.MaxPower
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxPower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.MaxPower

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxPower VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit kW VSS: Units
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.FrontLeft.MaxPower is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

4 - MaxRegenPower
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxRegenPower
Description: Peak regen/brake power, in kilowatts, that motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.MaxRegenPower
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxRegenPower: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.MaxRegenPower

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxRegenPower VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit kW VSS: Units
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.FrontLeft.MaxRegenPower is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

5 - MaxRegenTorque
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxRegenTorque
Description: Peak regen/brake torque, in newton meter, that the motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.MaxRegenTorque
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxRegenTorque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.MaxRegenTorque

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxRegenTorque VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit Nm VSS: Units
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.FrontLeft.MaxRegenTorque is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

6 - MaxTorque
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxTorque
Description: Peak power, in newton meter, that the motor(s) can generate.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.MaxTorque
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxTorque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.MaxTorque

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.MaxTorque VSS: Addressing nodes
Data type uint16 VSS: Datatypes
Unit Nm VSS: Units
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.FrontLeft.MaxTorque is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

7 - Power
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.Power
Description: Current motor power output. Negative values indicate regen mode.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.Power
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.Power: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.Power

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.Power VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit kW VSS: Units

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

8 - Speed
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.Speed
Description: Motor rotational speed measured as rotations per minute. Negative values indicate reverse driving mode.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.Speed
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.Speed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.Speed

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.Speed is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

9 - Temperature
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.Temperature
Description: Motor temperature.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.Temperature
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.Temperature

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.Temperature VSS: Addressing nodes
Data type float VSS: Datatypes
Unit Celsius VSS: Units

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

10 - TimeInUse
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.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-->FrontLeft FrontLeft-->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.FrontLeft.TimeInUse
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.TimeInUse: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.TimeInUse

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.TimeInUse is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

11 - Torque
Full qualified VSS Path: Vehicle.Powertrain.ElectricMotor.FrontLeft.Torque
Description: Current motor torque. Negative values indicate regen mode.
flowchart LR Vehicle-->Powertrain Powertrain-->ElectricMotor ElectricMotor-->FrontLeft FrontLeft-->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.FrontLeft.Torque
[get]  OK
Vehicle.Powertrain.ElectricMotor.FrontLeft.Torque: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Powertrain.ElectricMotor.FrontLeft.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.FrontLeft.Torque

Data Type & Unit
Path Vehicle.Powertrain.ElectricMotor.FrontLeft.Torque VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit Nm VSS: Units

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

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

Supported datatypes

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

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

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.