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

Return to the regular view of this page.

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

Signal Information

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

UUID

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

The UUID for Vehicle.ControlUnit.Trunk.Health.SWSupervision is d0dff7e023ba5ca5aef7f81bf7c0a8e4

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 - IsLogicalTriggered
Full qualified VSS Path: Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsLogicalTriggered
Description: Whether the logical supervision was triggered
flowchart LR Vehicle-->ControlUnit ControlUnit-->Trunk Trunk-->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.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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsLogicalTriggered

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

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

UUID

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

The UUID for Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsLogicalTriggered is b5be8ed6de1f5e8fa9269129979b3831

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 - IsWatchdogTriggered
Full qualified VSS Path: Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsWatchdogTriggered
Description: Whether the watchdog deadline was triggered
flowchart LR Vehicle-->ControlUnit ControlUnit-->Trunk Trunk-->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.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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsWatchdogTriggered

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

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

UUID

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

The UUID for Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsWatchdogTriggered is 220fdfd416f75583a6cec40077eeb924

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsAliveTriggered

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

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

UUID

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

The UUID for Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsAliveTriggered is b5135e9da8c55d12888acd7e58b26fd3

Feedback

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

About VSS

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

Supported datatypes

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

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

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

4 - IsDeadlineTriggered
Full qualified VSS Path: Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsDeadlineTriggered
Description: Whether the deadline supervision was triggered
flowchart LR Vehicle-->ControlUnit ControlUnit-->Trunk Trunk-->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.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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsDeadlineTriggered

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

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

UUID

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

The UUID for Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsDeadlineTriggered is bb80e6f0fc65596fa5e0765dfae7f2d2

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.