ControlUnit

• 1: Trunk
• 1.1: Health
• 1.1.1: Network
• 1.1.1.1: CAN
• 1.1.1.1.1: IsNetworkOK
• 1.1.1.2: ETH
• 1.1.1.2.1: IsNetworkOK
• 1.1.2: Resources
• 1.1.2.1: Power
• 1.1.2.2: Temperature
• 1.1.2.3: Utilization
• 1.1.2.3.1: CPU
• 1.1.2.3.2: Memory
• 1.1.3: SWSupervision
• 1.1.3.1: IsAliveTriggered
• 1.1.3.2: IsDeadlineTriggered
• 1.1.3.3: IsLogicalTriggered
• 1.1.3.4: IsWatchdogTriggered
• 1.2: ID
• 2: Central
• 2.1: Health
• 2.1.1: Network
• 2.1.1.1: CAN
• 2.1.1.1.1: IsNetworkOK
• 2.1.1.2: ETH
• 2.1.1.2.1: IsNetworkOK
• 2.1.2: Resources
• 2.1.2.1: Power
• 2.1.2.2: Temperature
• 2.1.2.3: Utilization
• 2.1.2.3.1: CPU
• 2.1.2.3.2: Memory
• 2.1.3: SWSupervision
• 2.1.3.1: IsAliveTriggered
• 2.1.3.2: IsDeadlineTriggered
• 2.1.3.3: IsLogicalTriggered
• 2.1.3.4: IsWatchdogTriggered
• 2.2: ID
• 3: FrontLeft
• 3.1: Health
• 3.1.1: Network
• 3.1.1.1: CAN
• 3.1.1.1.1: IsNetworkOK
• 3.1.1.2: ETH
• 3.1.1.2.1: IsNetworkOK
• 3.1.2: Resources
• 3.1.2.1: Power
• 3.1.2.2: Temperature
• 3.1.2.3: Utilization
• 3.1.2.3.1: CPU
• 3.1.2.3.2: Memory
• 3.1.3: SWSupervision
• 3.1.3.1: IsAliveTriggered
• 3.1.3.2: IsDeadlineTriggered
• 3.1.3.3: IsLogicalTriggered
• 3.1.3.4: IsWatchdogTriggered
• 3.2: ID
• 4: FrontRight
• 4.1: Health
• 4.1.1: Network
• 4.1.1.1: CAN
• 4.1.1.1.1: IsNetworkOK
• 4.1.1.2: ETH
• 4.1.1.2.1: IsNetworkOK
• 4.1.2: Resources
• 4.1.2.1: Power
• 4.1.2.2: Temperature
• 4.1.2.3: Utilization
• 4.1.2.3.1: CPU
• 4.1.2.3.2: Memory
• 4.1.3: SWSupervision
• 4.1.3.1: IsAliveTriggered
• 4.1.3.2: IsDeadlineTriggered
• 4.1.3.3: IsLogicalTriggered
• 4.1.3.4: IsWatchdogTriggered
• 4.2: ID
• 5: RearLeft1
• 5.1: Health
• 5.1.1: Network
• 5.1.1.1: CAN
• 5.1.1.1.1: IsNetworkOK
• 5.1.1.2: ETH
• 5.1.1.2.1: IsNetworkOK
• 5.1.2: Resources
• 5.1.2.1: Power
• 5.1.2.2: Temperature
• 5.1.2.3: Utilization
• 5.1.2.3.1: CPU
• 5.1.2.3.2: Memory
• 5.1.3: SWSupervision
• 5.1.3.1: IsAliveTriggered
• 5.1.3.2: IsDeadlineTriggered
• 5.1.3.3: IsLogicalTriggered
• 5.1.3.4: IsWatchdogTriggered
• 5.2: ID
• 6: RearLeft2
• 6.1: Health
• 6.1.1: Network
• 6.1.1.1: CAN
• 6.1.1.1.1: IsNetworkOK
• 6.1.1.2: ETH
• 6.1.1.2.1: IsNetworkOK
• 6.1.2: Resources
• 6.1.2.1: Power
• 6.1.2.2: Temperature
• 6.1.2.3: Utilization
• 6.1.2.3.1: CPU
• 6.1.2.3.2: Memory
• 6.1.3: SWSupervision
• 6.1.3.1: IsAliveTriggered
• 6.1.3.2: IsDeadlineTriggered
• 6.1.3.3: IsLogicalTriggered
• 6.1.3.4: IsWatchdogTriggered
• 6.2: ID

1 - Trunk

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health (Health attributes and signals)
• Vehicle.ControlUnit.Trunk.ID (Control unit ID)

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:

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

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health.Network (Network attributes and signals)
• Vehicle.ControlUnit.Trunk.Health.Resources (Resources attributes and signals)
• Vehicle.ControlUnit.Trunk.Health.SWSupervision (SW supervision attributes and signals)

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:

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

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health.Network.CAN (CAN network attributes and signals)
• Vehicle.ControlUnit.Trunk.Health.Network.ETH (Ethernet network attributes and signals)

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:

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

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health.Network.CAN.IsNetworkOK (Network status. True = No network problems detected. False = Network problems detected.)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.Network.CAN.IsNetworkOK is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.1.2 - ETH

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health.Network.ETH.IsNetworkOK (Network status. True = No network problems detected. False = Network problems detected.)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.Network.ETH.IsNetworkOK is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.2 - Resources

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health.Resources.Power (Power consumption)
• Vehicle.ControlUnit.Trunk.Health.Resources.Temperature (Instance temperature)
• Vehicle.ControlUnit.Trunk.Health.Resources.Utilization (Resources utilization branch)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.Resources.Power is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.2.2 - Temperature

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.Resources.Temperature is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.2.3 - Utilization

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health.Resources.Utilization.CPU (CPU utilization)
• Vehicle.ControlUnit.Trunk.Health.Resources.Utilization.Memory (Memory utilization)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.Resources.Utilization.CPU is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.2.3.2 - Memory

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.Resources.Utilization.Memory is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.3 - SWSupervision

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsAliveTriggered (Whether the alive supervision was triggered)
• Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsDeadlineTriggered (Whether the deadline supervision was triggered)
• Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsLogicalTriggered (Whether the logical supervision was triggered)
• Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsWatchdogTriggered (Whether the watchdog deadline was triggered)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.SWSupervision.IsAliveTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.3.2 - IsDeadlineTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.SWSupervision.IsDeadlineTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.3.3 - IsLogicalTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.SWSupervision.IsLogicalTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.1.3.4 - IsWatchdogTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Trunk.Health.SWSupervision.IsWatchdogTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

1.2 - ID

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.Trunk.ID
[get]  OK
Vehicle.ControlUnit.Trunk.ID: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.Trunk.ID 0
[set]  OK

Digital Auto: Playground

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

Data Type & Unit

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.Trunk.ID is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2 - Central

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health (Health attributes and signals)
• Vehicle.ControlUnit.Central.ID (Control unit ID)

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:

About VSS

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

2.1 - Health

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health.Network (Network attributes and signals)
• Vehicle.ControlUnit.Central.Health.Resources (Resources attributes and signals)
• Vehicle.ControlUnit.Central.Health.SWSupervision (SW supervision attributes and signals)

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:

About VSS

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

2.1.1 - Network

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health.Network.CAN (CAN network attributes and signals)
• Vehicle.ControlUnit.Central.Health.Network.ETH (Ethernet network attributes and signals)

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:

About VSS

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

2.1.1.1 - CAN

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health.Network.CAN.IsNetworkOK (Network status. True = No network problems detected. False = Network problems detected.)

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:

About VSS

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

2.1.1.1.1 - IsNetworkOK

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.Network.CAN.IsNetworkOK is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.1.2 - ETH

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health.Network.ETH.IsNetworkOK (Network status. True = No network problems detected. False = Network problems detected.)

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:

About VSS

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

2.1.1.2.1 - IsNetworkOK

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.Network.ETH.IsNetworkOK is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.2 - Resources

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health.Resources.Power (Power consumption)
• Vehicle.ControlUnit.Central.Health.Resources.Temperature (Instance temperature)
• Vehicle.ControlUnit.Central.Health.Resources.Utilization (Resources utilization branch)

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:

About VSS

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

2.1.2.1 - Power

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.Resources.Power is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.2.2 - Temperature

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.Resources.Temperature is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.2.3 - Utilization

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health.Resources.Utilization.CPU (CPU utilization)
• Vehicle.ControlUnit.Central.Health.Resources.Utilization.Memory (Memory utilization)

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:

About VSS

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

2.1.2.3.1 - CPU

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.Resources.Utilization.CPU is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.2.3.2 - Memory

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.Resources.Utilization.Memory is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.3 - SWSupervision

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.Central.Health.SWSupervision.IsAliveTriggered (Whether the alive supervision was triggered)
• Vehicle.ControlUnit.Central.Health.SWSupervision.IsDeadlineTriggered (Whether the deadline supervision was triggered)
• Vehicle.ControlUnit.Central.Health.SWSupervision.IsLogicalTriggered (Whether the logical supervision was triggered)
• Vehicle.ControlUnit.Central.Health.SWSupervision.IsWatchdogTriggered (Whether the watchdog deadline was triggered)

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:

About VSS

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

2.1.3.1 - IsAliveTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.SWSupervision.IsAliveTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.3.2 - IsDeadlineTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.SWSupervision.IsDeadlineTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.3.3 - IsLogicalTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.SWSupervision.IsLogicalTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.1.3.4 - IsWatchdogTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.Central.Health.SWSupervision.IsWatchdogTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

2.2 - ID

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.Central.ID
[get]  OK
Vehicle.ControlUnit.Central.ID: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.Central.ID 0
[set]  OK

Digital Auto: Playground

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

Data Type & Unit

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.Central.ID is an Attribute.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3 - FrontLeft

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health (Health attributes and signals)
• Vehicle.ControlUnit.FrontLeft.ID (Control unit ID)

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:

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

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health.Network (Network attributes and signals)
• Vehicle.ControlUnit.FrontLeft.Health.Resources (Resources attributes and signals)
• Vehicle.ControlUnit.FrontLeft.Health.SWSupervision (SW supervision attributes and signals)

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:

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

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health.Network.CAN (CAN network attributes and signals)
• Vehicle.ControlUnit.FrontLeft.Health.Network.ETH (Ethernet network attributes and signals)

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:

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

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health.Network.CAN.IsNetworkOK (Network status. True = No network problems detected. False = Network problems detected.)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.FrontLeft.Health.Network.CAN.IsNetworkOK is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3.1.1.2 - ETH

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health.Network.ETH.IsNetworkOK (Network status. True = No network problems detected. False = Network problems detected.)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.FrontLeft.Health.Network.ETH.IsNetworkOK is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3.1.2 - Resources

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health.Resources.Power (Power consumption)
• Vehicle.ControlUnit.FrontLeft.Health.Resources.Temperature (Instance temperature)
• Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization (Resources utilization branch)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3.1.2.2 - Temperature

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3.1.2.3 - Utilization

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization.CPU (CPU utilization)
• Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization.Memory (Memory utilization)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.FrontLeft.Health.Resources.Utilization.CPU is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3.1.2.3.2 - Memory

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.FrontLeft.Health.Resources.Utilization.Memory is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3.1.3 - SWSupervision

Navigation

Digital Auto: Playground

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

Signal Information

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

Children

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

• Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsAliveTriggered (Whether the alive supervision was triggered)
• Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsDeadlineTriggered (Whether the deadline supervision was triggered)
• Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsLogicalTriggered (Whether the logical supervision was triggered)
• Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsWatchdogTriggered (Whether the watchdog deadline was triggered)

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:

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

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit

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.FrontLeft.Health.SWSupervision.IsAliveTriggered is a Sensor.

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

Feedback

Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:

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:

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

3.1.3.2 - IsDeadlineTriggered

Navigation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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