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

Return to the regular view of this page.

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:

Feedback

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

About VSS

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

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

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

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

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

Feedback

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

About VSS

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

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

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

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

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

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

3.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 Distance measured in meters VSS: Sensors & Actuators
Domain distance

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

Signal Information

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

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

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

Feedback

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

About VSS

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

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

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

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

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

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

5 - ECT
Full qualified VSS Path: Vehicle.Powertrain.CombustionEngine.ECT
Description: Engine coolant temperature.
flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->ECT

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

Data Type & Unit
Path Vehicle.Powertrain.CombustionEngine.ECT VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit celsius VSS: Units
Label degree celsius
Description Temperature measured in degree celsius VSS: Sensors & Actuators
Domain temperature

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.ECT is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.ECT is fff3cad23cac5b189a1a075c3ab562cd

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.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 - EngineCoolantCapacity
Full qualified VSS Path: Vehicle.Powertrain.CombustionEngine.EngineCoolantCapacity
Description: Engine coolant capacity in liters.
flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineCoolantCapacity

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

Data Type & Unit
Path Vehicle.Powertrain.CombustionEngine.EngineCoolantCapacity 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.EngineCoolantCapacity is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineCoolantCapacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineCoolantCapacity is 90b5b64808ea5f4fa2798d96143b0d60

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.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 - 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 Time measured in hours VSS: Sensors & Actuators
Domain time

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

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

8 - EngineOilCapacity
Full qualified VSS Path: Vehicle.Powertrain.CombustionEngine.EngineOilCapacity
Description: Engine oil capacity in liters.
flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineOilCapacity

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

Data Type & Unit
Path Vehicle.Powertrain.CombustionEngine.EngineOilCapacity 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.EngineOilCapacity is an Attribute.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOilCapacity is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineOilCapacity is 2ca7af6facb55a13885989faa9bc6ca7

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.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 - EngineOilLevel
Full qualified VSS Path: Vehicle.Powertrain.CombustionEngine.EngineOilLevel
Description: Engine oil level.
flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EngineOilLevel

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

Data Type & Unit
Path Vehicle.Powertrain.CombustionEngine.EngineOilLevel 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.EngineOilLevel is a Sensor.

The vehicle signal Vehicle.Powertrain.CombustionEngine.EngineOilLevel is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EngineOilLevel is e3813f59e94b509eb865fd97255a8a4f

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.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 - 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

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

11 - EOT
Full qualified VSS Path: Vehicle.Powertrain.CombustionEngine.EOT
Description: Engine oil temperature.
flowchart LR Vehicle-->Powertrain Powertrain-->CombustionEngine CombustionEngine-->EOT

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

Data Type & Unit
Path Vehicle.Powertrain.CombustionEngine.EOT VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit celsius VSS: Units
Label degree celsius
Description Temperature measured in degree celsius VSS: Sensors & Actuators
Domain temperature

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.EOT is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.EOT is eae6f5eae04f530e80f6b024f95b767d

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.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.

12 - 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 Time measured in hours VSS: Sensors & Actuators
Domain time

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

20 - OilLifeRemaining
Full qualified VSS Path: Vehicle.Powertrain.CombustionEngine.OilLifeRemaining
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-->OilLifeRemaining

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

Data Type & Unit
Path Vehicle.Powertrain.CombustionEngine.OilLifeRemaining VSS: Addressing nodes
Data type int32 VSS: Datatypes
Unit s VSS: Units
Label second
Description Time measured in seconds VSS: Sensors & Actuators
Domain time

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

The vehicle signal Vehicle.Powertrain.CombustionEngine.OilLifeRemaining is a Signal.

UUID

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

The UUID for Vehicle.Powertrain.CombustionEngine.OilLifeRemaining is 94303734c68c5353a02625f652103918

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.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.

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

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

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

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

23 - Torque
Full qualified VSS Path: Vehicle.Powertrain.CombustionEngine.Torque
Description: Current engine torque. Shall be reported as 0 during engine breaking.
Comment: During engine breaking the engine delivers a negative torque to the transmission. This negative torque shall be ignored, instead 0 shall be reported.
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 uint16 VSS: Datatypes
Unit Nm VSS: Units
Label newton meter
Description Torque measured in newton meters VSS: Sensors & Actuators
Domain torque

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

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

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

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

25 - 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 Distance measured in millimeters VSS: Sensors & Actuators
Domain 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.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

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

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

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

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

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

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

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

29 - 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 Distance measured in millimeters VSS: Sensors & Actuators
Domain 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.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

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