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

Return to the regular view of this page.

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:

Feedback

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

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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 - 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

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

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

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

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

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

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

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