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

Return to the regular view of this page.

RearLeft2
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2
Description: Root of the control unit branch
Comment: The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2

Digital Auto: Playground

playground.digital.auto provides an in-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.RearLeft2

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2 is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2 is 4f492d7dd47b54078c47599b648e7303

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 - Health
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health
Description: Health attributes and signals
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health

Digital Auto: Playground

playground.digital.auto provides an in-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.RearLeft2.Health

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health is 3e4eaf282f5558168a5d5b844651b891

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.1 - Network
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Network
Description: Network attributes and signals
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Network

Digital Auto: Playground

playground.digital.auto provides an in-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.RearLeft2.Health.Network

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network is e70e7d4ba989506a9d7c9cb53f1e0681

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.1.1 - CAN
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Network.CAN
Description: CAN network attributes and signals
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Network Network-->CAN

Digital Auto: Playground

playground.digital.auto provides an in-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.RearLeft2.Health.Network.CAN

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.CAN is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.CAN is 319d0fe61dfb56f89a38659f5b3e0601

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.1.1.1 - IsNetworkOK
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK
Description: Network status. True = No network problems detected. False = Network problems detected.
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Network Network-->CAN CAN-->IsNetworkOK

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK 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.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK 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.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK is 875e063a102555e5a5b75a7767927032

Feedback

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

About VSS

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

1.1.2 - ETH
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Network.ETH
Description: Ethernet network attributes and signals
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Network Network-->ETH

Digital Auto: Playground

playground.digital.auto provides an in-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.RearLeft2.Health.Network.ETH

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.ETH is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.ETH is dac0d73f92cb5834a22a02c0c14658da

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.1.2.1 - IsNetworkOK
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK
Description: Network status. True = No network problems detected. False = Network problems detected.
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Network Network-->ETH ETH-->IsNetworkOK

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK 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.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK 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.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK is 63bec0559779534684aaea0775b81618

Feedback

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

About VSS

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

1.2 - Resources
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Resources
Description: Resources attributes and signals
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Resources

Digital Auto: Playground

playground.digital.auto provides an in-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.RearLeft2.Health.Resources

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources is 527bf7f0ad905d4eac5762aea5f3b09d

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.2.1 - Power
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Resources.Power
Description: Power consumption
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Resources Resources-->Power

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.Resources.Power VSS: Addressing nodes
Data type float VSS: Datatypes
Unit W VSS: Units
Label watt
Description Power measured in watts VSS: Sensors & Actuators
Domain power

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

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Power is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Power is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Power is 199e4e43d17f57d7b2291e794f30ca82

Feedback

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

About VSS

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

1.2.2 - Temperature
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature
Description: Instance temperature
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->Resources Resources-->Temperature

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature 0
[set]  OK

Digital Auto: Playground

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

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

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature VSS: Addressing nodes
Data type float VSS: Datatypes
Unit Celsius VSS: Units
Label degree Celsius
Description Temperature measured in degree Celsius VSS: Sensors & Actuators
Domain temperature

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

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature is bdc8d001b629516c8a448309c456f52c

Feedback

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

About VSS

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization is eb0b58b49fc45c4db2087f11abec7d3d

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.2.3.1 - CPU
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU
Description: CPU utilization
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->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.RearLeft2.Health.Resources.Utilization.CPU
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.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.RearLeft2.Health.Resources.Utilization.CPU

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.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.RearLeft2.Health.Resources.Utilization.CPU is a Sensor.

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

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU is 58374ccea2f1569e9c3ab7329a6ea655

Feedback

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

About VSS

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

1.2.3.2 - Memory
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory
Description: Memory utilization
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->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.RearLeft2.Health.Resources.Utilization.Memory
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.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.RearLeft2.Health.Resources.Utilization.Memory

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.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.RearLeft2.Health.Resources.Utilization.Memory is a Sensor.

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

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory is 1732531c061d5b1b8a049bc6906e3a8d

Feedback

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

About VSS

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

1.3 - SWSupervision
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.SWSupervision
Description: SW supervision attributes and signals
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->SWSupervision

Digital Auto: Playground

playground.digital.auto provides an in-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.RearLeft2.Health.SWSupervision

Signal Information

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision is a Branch.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision is 8f0cf49b06da55ffa85c3ac679d35a60

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.3.1 - IsAliveTriggered
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered
Description: Whether the alive supervision was triggered
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->SWSupervision SWSupervision-->IsAliveTriggered

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered is 0432b4ab85955c3abd6d144e77253e55

Feedback

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

About VSS

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

1.3.2 - IsDeadlineTriggered
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered
Description: Whether the deadline supervision was triggered
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->SWSupervision SWSupervision-->IsDeadlineTriggered

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered is a5a0c94a04645c968d4186cf9efe3020

Feedback

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

About VSS

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

1.3.3 - IsLogicalTriggered
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered
Description: Whether the logical supervision was triggered
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->SWSupervision SWSupervision-->IsLogicalTriggered

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered is e617141cf6075bd6b7db114636847875

Feedback

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

About VSS

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

1.3.4 - IsWatchdogTriggered
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered
Description: Whether the watchdog deadline was triggered
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->Health Health-->SWSupervision SWSupervision-->IsWatchdogTriggered

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered
[get]  OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered 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.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered is a Sensor.

The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered is 657fd8f2e1835a80847ed6e144454725

Feedback

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

About VSS

The Vehicle Signal Specification (VSS) is an initiative by 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 - ID
Full qualified VSS Path: Vehicle.ControlUnit.RearLeft2.ID
Description: Control unit ID
flowchart LR Vehicle-->ControlUnit ControlUnit-->RearLeft2 RearLeft2-->ID

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.ControlUnit.RearLeft2.ID VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Default value 0 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.ControlUnit.RearLeft2.ID is an Attribute.

The vehicle signal Vehicle.ControlUnit.RearLeft2.ID is a Signal.

UUID

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

The UUID for Vehicle.ControlUnit.RearLeft2.ID is 0a9a70a673cd5a908cafea4333fa18ae

Feedback

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

About VSS

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