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

Return to the regular view of this page.

Network

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

Signal Information

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

UUID

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

The UUID for Vehicle.ControlUnit.Central.Health.Network is 86c551a5544755fbb336c540bf80d374

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.ControlUnit.Central.Health.Network.CAN is 2a4c4a68a3e7516a9b2396cb232f8d23

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

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ControlUnit.Central.Health.Network.CAN.IsNetworkOK

Data Type & Unit

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

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

UUID

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

The UUID for Vehicle.ControlUnit.Central.Health.Network.CAN.IsNetworkOK is 7529e44bcc965ba2bfe22f506af55176

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

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

Signal Information

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

UUID

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

The UUID for Vehicle.ControlUnit.Central.Health.Network.ETH is 68be7a4537fd51f19faa773e25912112

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.

2.1 - IsNetworkOK

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ControlUnit.Central.Health.Network.ETH.IsNetworkOK

Data Type & Unit

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

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

UUID

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

The UUID for Vehicle.ControlUnit.Central.Health.Network.ETH.IsNetworkOK is 6277d4eba1115d55bab1c9ea7233482e

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.