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

Return to the regular view of this page.

Utilization
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization
Description: Resources utilization branch
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft1 RearLeft1-->Health Health-->Resources Resources-->Utilization

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization is 3413972ecdc55a92a9bbc4cd8d5b117d

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 - CPU
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU
Description: CPU utilization
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft1 RearLeft1-->Health Health-->Resources Resources-->Utilization Utilization-->CPU

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU
[get]  OK
Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU 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.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU VSS: Addressing nodes
Data type float VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

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

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU is 5747abc243f85911a9a809f0a6022c4b

Feedback

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

About VSS

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

Supported datatypes

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

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

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory
[get]  OK
Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory 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.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory VSS: Addressing nodes
Data type float VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Minimum value 0 VSS: Sensors & Actuators
Maximum value 100 VSS: Sensors & Actuators

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

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory is e9269c7cc7a059e290ce3ccd0d9e2d11

Feedback

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

About VSS

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

Supported datatypes

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

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