This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
ControlUnit
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit |
| Description: |
Root of the control unit branch |
| Comment: |
The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed |
Navigation
flowchart LR
Vehicle-->ControlUnit
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit is 6c9e99457e2355ecb9e808c93cc2d408
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:
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 - FrontLeft
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft |
| Description: |
Root of the control unit branch |
| Comment: |
The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontLeft is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft is 95bba655772452219e5189cac7a7a21b
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health |
| Description: |
Health attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health is d5102e2727575671b702e9196810a070
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Network |
| Description: |
Network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->Network
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Network is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Network is 7f9fae9e59c651a187db6a7f4aaf51a5
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Network.CAN |
| Description: |
CAN network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Network.CAN is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Network.CAN is 31a0ae2938b65f6fb1dd7e02b512c203
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Network.CAN.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.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.
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Network.CAN.IsNetworkOK is 0339a9fa051e5616943f5840f73c261a
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.1.2 - ETH
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Network.ETH |
| Description: |
Ethernet network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Network.ETH is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Network.ETH is ad544ec581d955e7bcf564680db01113
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Network.ETH.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.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.
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Network.ETH.IsNetworkOK is cbed5922b9a3535298db68f67a4c4fb0
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.2 - Resources
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Resources |
| Description: |
Resources attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->Resources
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Resources is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Resources is 853a2a5bb4ee51fb860c2889f0b63492
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Resources.Power |
| Description: |
Power consumption |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->Resources
Resources-->Power
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Resources.Power is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Resources.Power is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Resources.Power is 7e398640b75c5608ad6492b4a4e703c4
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.2.2 - Temperature
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Resources.Temperature |
| Description: |
Instance temperature |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->Resources
Resources-->Temperature
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Resources.Temperature is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Resources.Temperature is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Resources.Temperature is b0b4636bbd395791a69c18fb64168b2f
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.2.3 - Utilization
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization |
| Description: |
Resources utilization branch |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->Resources
Resources-->Utilization
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization is 623205a599005639be66890fa3db7e7c
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization.CPU |
| Description: |
CPU utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->Resources
Resources-->Utilization
Utilization-->CPU
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization.CPU is 832248cf93c45e1ab825c25e60941346
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.2.3.2 - Memory
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization.Memory |
| Description: |
Memory utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->Resources
Resources-->Utilization
Utilization-->Memory
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.Resources.Utilization.Memory is ec4e69c8307151009b0cab6a03d1d49b
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.3 - SWSupervision
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.SWSupervision |
| Description: |
SW supervision attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->Health
Health-->SWSupervision
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.SWSupervision is 37e2f04eef7255deb8e6d748142942a5
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsAliveTriggered |
| Description: |
Whether the alive supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.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.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsAliveTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsAliveTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsAliveTriggered is 1d32249d68f95e77bbdcfea247e91c8a
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.3.2 - IsDeadlineTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsDeadlineTriggered |
| Description: |
Whether the deadline supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.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.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsDeadlineTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsDeadlineTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsDeadlineTriggered is 105d3a325b7d55dcb4ad5f8bf3266f05
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.3.3 - IsLogicalTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsLogicalTriggered |
| Description: |
Whether the logical supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.FrontLeft.Health.SWSupervision.IsLogicalTriggered
[get] OK
Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsLogicalTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontLeft.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.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsLogicalTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsLogicalTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsLogicalTriggered is e3249afbecd15e72aabd457ed270457c
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.1.3.4 - IsWatchdogTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsWatchdogTriggered |
| Description: |
Whether the watchdog deadline was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->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.FrontLeft.Health.SWSupervision.IsWatchdogTriggered
[get] OK
Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsWatchdogTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontLeft.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.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsWatchdogTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsWatchdogTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.Health.SWSupervision.IsWatchdogTriggered is 47f6a9eeeeb55f1786c4537d754b369d
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:
| Name |
Type |
Min |
Max |
| uint8 |
unsigned 8-bit integer |
0 |
255 |
| int8 |
signed 8-bit integer |
-128 |
127 |
| uint16 |
unsigned 16-bit integer |
0 |
65535 |
| int16 |
signed 16-bit integer |
-32768 |
32767 |
| uint32 |
unsigned 32-bit integer |
0 |
4294967295 |
| int32 |
signed 32-bit integer |
-2147483648 |
2147483647 |
| uint64 |
unsigned 64-bit integer |
0 |
2^64 - 1 |
| int64 |
signed 64-bit integer |
-2^63 |
2^63 - 1 |
| boolean |
boolean value |
0/false |
1/true |
| float |
floating point number |
-3.4e -38 |
3.4e 38 |
| double |
double precision floating point number |
-1.7e -300 |
1.7e 300 |
| string |
character string |
n/a |
n/a |
Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.
1.2 - ID
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontLeft.ID |
| Description: |
Control unit ID |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontLeft
FrontLeft-->ID
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.FrontLeft.ID
[get] OK
Vehicle.ControlUnit.FrontLeft.ID: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontLeft.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).
The vehicle signal Vehicle.ControlUnit.FrontLeft.ID is an Attribute.
The vehicle signal Vehicle.ControlUnit.FrontLeft.ID is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontLeft.ID is 3735a49ab2b7500ab30ec09e6e44c0a5
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:
| 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 - FrontRight
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight |
| Description: |
Root of the control unit branch |
| Comment: |
The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontRight is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight is fe687dbb68bc53ea83f9b2d6c7cce5b1
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health |
| Description: |
Health attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health is dc152fa430a95167bba65106e8805b91
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Network |
| Description: |
Network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->Network
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Network is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Network is 2eb07dfdc1725d78b3d31877f9751ecf
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Network.CAN |
| Description: |
CAN network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Network.CAN is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Network.CAN is 00895a76400c5cb3b197754ba55611e5
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Network.CAN.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.FrontRight.Health.Network.CAN.IsNetworkOK
[get] OK
Vehicle.ControlUnit.FrontRight.Health.Network.CAN.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Network.CAN.IsNetworkOK is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Network.CAN.IsNetworkOK is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Network.CAN.IsNetworkOK is c122a0bb2ece5d8d911357b897e47d26
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:
| 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.1.1.2 - ETH
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Network.ETH |
| Description: |
Ethernet network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Network.ETH is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Network.ETH is a582459286765d208c65f4028b0dc947
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Network.ETH.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.FrontRight.Health.Network.ETH.IsNetworkOK
[get] OK
Vehicle.ControlUnit.FrontRight.Health.Network.ETH.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Network.ETH.IsNetworkOK is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Network.ETH.IsNetworkOK is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Network.ETH.IsNetworkOK is d4281059e89b5bf4af24332b7087655a
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:
| 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.1.2 - Resources
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Resources |
| Description: |
Resources attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->Resources
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Resources is 9adc304dcef250b183d37e85193a0226
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Resources.Power |
| Description: |
Power consumption |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->Resources
Resources-->Power
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.FrontRight.Health.Resources.Power
[get] OK
Vehicle.ControlUnit.FrontRight.Health.Resources.Power: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Power is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Power is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Resources.Power is 4a5fffaec29851fcadc50da51cbd38a3
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:
| 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.1.2.2 - Temperature
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Resources.Temperature |
| Description: |
Instance temperature |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->Resources
Resources-->Temperature
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.FrontRight.Health.Resources.Temperature
[get] OK
Vehicle.ControlUnit.FrontRight.Health.Resources.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Temperature is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Temperature is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Resources.Temperature is b37dae6bd5ed51caae7c79b87b214b90
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:
| 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.1.2.3 - Utilization
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization |
| Description: |
Resources utilization branch |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->Resources
Resources-->Utilization
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization is 832357b908435a8bb4d58ca4c3c19add
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.CPU |
| Description: |
CPU utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->Resources
Resources-->Utilization
Utilization-->CPU
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.CPU
[get] OK
Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.CPU: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.CPU is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.CPU is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.CPU is acfa8acd4ba75f099b043a402721da10
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:
| 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.1.2.3.2 - Memory
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.Memory |
| Description: |
Memory utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->Resources
Resources-->Utilization
Utilization-->Memory
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.Memory
[get] OK
Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.Memory: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.Memory is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.Memory is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.Resources.Utilization.Memory is 08c34513f81d569c8b228d25efdcd2ca
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:
| 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.1.3 - SWSupervision
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.SWSupervision |
| Description: |
SW supervision attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->Health
Health-->SWSupervision
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.SWSupervision is c6271954b61d5ead818e6056af35b6fb
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsAliveTriggered |
| Description: |
Whether the alive supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.FrontRight.Health.SWSupervision.IsAliveTriggered
[get] OK
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsAliveTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsAliveTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsAliveTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsAliveTriggered is 74f0376546de5ad1b23d401f2f11565f
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:
| 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.1.3.2 - IsDeadlineTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsDeadlineTriggered |
| Description: |
Whether the deadline supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.FrontRight.Health.SWSupervision.IsDeadlineTriggered
[get] OK
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsDeadlineTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsDeadlineTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsDeadlineTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsDeadlineTriggered is cbad5d27fb535c2985b7f015a6f523fd
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:
| 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.1.3.3 - IsLogicalTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsLogicalTriggered |
| Description: |
Whether the logical supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.FrontRight.Health.SWSupervision.IsLogicalTriggered
[get] OK
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsLogicalTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsLogicalTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsLogicalTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsLogicalTriggered is 322ae313a9ed5632834d58f6836d6a9b
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:
| 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.1.3.4 - IsWatchdogTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsWatchdogTriggered |
| Description: |
Whether the watchdog deadline was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->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.FrontRight.Health.SWSupervision.IsWatchdogTriggered
[get] OK
Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsWatchdogTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsWatchdogTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsWatchdogTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.Health.SWSupervision.IsWatchdogTriggered is 952f60885c3e55c2b51785eb27a8e666
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:
| 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.2 - ID
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.FrontRight.ID |
| Description: |
Control unit ID |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->FrontRight
FrontRight-->ID
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.FrontRight.ID
[get] OK
Vehicle.ControlUnit.FrontRight.ID: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.FrontRight.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).
The vehicle signal Vehicle.ControlUnit.FrontRight.ID is an Attribute.
The vehicle signal Vehicle.ControlUnit.FrontRight.ID is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.FrontRight.ID is 4da6f9cee7395cd4be5830eb3b8c0e3f
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:
| 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 - RearLeft1
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1 |
| Description: |
Root of the control unit branch |
| Comment: |
The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft1 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1 is b535811e209a57a8ae68fe2ed7133f91
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health |
| Description: |
Health attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health is aa6b70eb9ceb55268482aa08e75cafa2
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Network |
| Description: |
Network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->Network
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Network is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Network is 763495dae0145fc182f25c33e0604cad
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Network.CAN |
| Description: |
CAN network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Network.CAN is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Network.CAN is bac3f481321d505ca95847a2516644f0
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Network.CAN.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.RearLeft1.Health.Network.CAN.IsNetworkOK
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.Network.CAN.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Network.CAN.IsNetworkOK is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Network.CAN.IsNetworkOK is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Network.CAN.IsNetworkOK is 14f95cd8564c59e2ba7e03485363b552
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:
| 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.1.1.2 - ETH
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Network.ETH |
| Description: |
Ethernet network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Network.ETH is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Network.ETH is bba3080555775e2f907f303cc3bfcbc6
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Network.ETH.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.RearLeft1.Health.Network.ETH.IsNetworkOK
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.Network.ETH.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Network.ETH.IsNetworkOK is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Network.ETH.IsNetworkOK is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Network.ETH.IsNetworkOK is deb319b401f6502c84780f32863f6db2
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:
| 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.1.2 - Resources
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Resources |
| Description: |
Resources attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->Resources
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources is 751defadf02c5c0d9bc833f90d6d6ff6
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Resources.Power |
| Description: |
Power consumption |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->Resources
Resources-->Power
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft1.Health.Resources.Power
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.Resources.Power: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Power is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Power is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Power is 93cdf58d9f0d5d079f9f413c0231c0e8
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:
| 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.1.2.2 - Temperature
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Resources.Temperature |
| Description: |
Instance temperature |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->Resources
Resources-->Temperature
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft1.Health.Resources.Temperature
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.Resources.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Temperature is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Temperature is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Temperature is f93543a8954359d5a1178538fa018ba0
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:
| 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.1.2.3 - Utilization
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization |
| Description: |
Resources utilization branch |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->Resources
Resources-->Utilization
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization is 3413972ecdc55a92a9bbc4cd8d5b117d
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU |
| Description: |
CPU utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->Resources
Resources-->Utilization
Utilization-->CPU
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.CPU is 5747abc243f85911a9a809f0a6022c4b
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.2.3.2 - Memory
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory |
| Description: |
Memory utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->Resources
Resources-->Utilization
Utilization-->Memory
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.Resources.Utilization.Memory is e9269c7cc7a059e290ce3ccd0d9e2d11
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.3 - SWSupervision
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision |
| Description: |
SW supervision attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->Health
Health-->SWSupervision
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.SWSupervision is 610177aa91c65772802c86c55ac6d52b
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:
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
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsAliveTriggered |
| Description: |
Whether the alive supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.RearLeft1.Health.SWSupervision.IsAliveTriggered
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsAliveTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsAliveTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsAliveTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsAliveTriggered is 3f2b38500fc657d394cedc02aec2831f
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:
| 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.1.3.2 - IsDeadlineTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsDeadlineTriggered |
| Description: |
Whether the deadline supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.RearLeft1.Health.SWSupervision.IsDeadlineTriggered
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsDeadlineTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsDeadlineTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsDeadlineTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsDeadlineTriggered is 6b319ced7a8d5c6baddc5e6c87f87672
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:
| 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.1.3.3 - IsLogicalTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsLogicalTriggered |
| Description: |
Whether the logical supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.RearLeft1.Health.SWSupervision.IsLogicalTriggered
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsLogicalTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsLogicalTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsLogicalTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsLogicalTriggered is e01a1451d2985e1a8f89fc9c262334af
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:
| 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.1.3.4 - IsWatchdogTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsWatchdogTriggered |
| Description: |
Whether the watchdog deadline was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->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.RearLeft1.Health.SWSupervision.IsWatchdogTriggered
[get] OK
Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsWatchdogTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsWatchdogTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsWatchdogTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.Health.SWSupervision.IsWatchdogTriggered is 8c82856215a8598fa106a087231797ee
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:
| 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.2 - ID
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft1.ID |
| Description: |
Control unit ID |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft1
RearLeft1-->ID
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft1.ID
[get] OK
Vehicle.ControlUnit.RearLeft1.ID: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft1.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).
The vehicle signal Vehicle.ControlUnit.RearLeft1.ID is an Attribute.
The vehicle signal Vehicle.ControlUnit.RearLeft1.ID is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft1.ID is a7a3a5eeb2785939969520c854c0d34b
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:
| 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 - RearLeft2
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2 |
| Description: |
Root of the control unit branch |
| Comment: |
The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2 is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2 is 4f492d7dd47b54078c47599b648e7303
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1 - Health
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health |
| Description: |
Health attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health is 3e4eaf282f5558168a5d5b844651b891
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1.1 - Network
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Network |
| Description: |
Network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Network
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network is e70e7d4ba989506a9d7c9cb53f1e0681
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1.1.1 - CAN
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Network.CAN |
| Description: |
CAN network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Network
Network-->CAN
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.CAN is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.CAN is 319d0fe61dfb56f89a38659f5b3e0601
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1.1.1.1 - IsNetworkOK
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Network
Network-->CAN
CAN-->IsNetworkOK
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.CAN.IsNetworkOK is 875e063a102555e5a5b75a7767927032
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.1.2 - ETH
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Network.ETH |
| Description: |
Ethernet network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Network
Network-->ETH
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.ETH is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.ETH is dac0d73f92cb5834a22a02c0c14658da
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1.1.2.1 - IsNetworkOK
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Network
Network-->ETH
ETH-->IsNetworkOK
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Network.ETH.IsNetworkOK is 63bec0559779534684aaea0775b81618
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.2 - Resources
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Resources |
| Description: |
Resources attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Resources
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources is 527bf7f0ad905d4eac5762aea5f3b09d
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1.2.1 - Power
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Resources.Power |
| Description: |
Power consumption |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Resources
Resources-->Power
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Resources.Power
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.Resources.Power: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Resources.Power 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Power is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Power is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Power is 199e4e43d17f57d7b2291e794f30ca82
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.2.2 - Temperature
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature |
| Description: |
Instance temperature |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Resources
Resources-->Temperature
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Temperature is bdc8d001b629516c8a448309c456f52c
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.2.3 - Utilization
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization |
| Description: |
Resources utilization branch |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Resources
Resources-->Utilization
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization is eb0b58b49fc45c4db2087f11abec7d3d
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1.2.3.1 - CPU
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU |
| Description: |
CPU utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Resources
Resources-->Utilization
Utilization-->CPU
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.CPU is 58374ccea2f1569e9c3ab7329a6ea655
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.2.3.2 - Memory
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory |
| Description: |
Memory utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->Resources
Resources-->Utilization
Utilization-->Memory
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.Resources.Utilization.Memory is 1732531c061d5b1b8a049bc6906e3a8d
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.3 - SWSupervision
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision |
| Description: |
SW supervision attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->SWSupervision
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision is 8f0cf49b06da55ffa85c3ac679d35a60
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
4.1.3.1 - IsAliveTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered |
| Description: |
Whether the alive supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->SWSupervision
SWSupervision-->IsAliveTriggered
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsAliveTriggered is 0432b4ab85955c3abd6d144e77253e55
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.3.2 - IsDeadlineTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered |
| Description: |
Whether the deadline supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->SWSupervision
SWSupervision-->IsDeadlineTriggered
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsDeadlineTriggered is a5a0c94a04645c968d4186cf9efe3020
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.3.3 - IsLogicalTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered |
| Description: |
Whether the logical supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->SWSupervision
SWSupervision-->IsLogicalTriggered
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsLogicalTriggered is e617141cf6075bd6b7db114636847875
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.1.3.4 - IsWatchdogTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered |
| Description: |
Whether the watchdog deadline was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->Health
Health-->SWSupervision
SWSupervision-->IsWatchdogTriggered
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered
[get] OK
Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.Health.SWSupervision.IsWatchdogTriggered is 657fd8f2e1835a80847ed6e144454725
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.2 - ID
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.RearLeft2.ID |
| Description: |
Control unit ID |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->RearLeft2
RearLeft2-->ID
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.RearLeft2.ID
[get] OK
Vehicle.ControlUnit.RearLeft2.ID: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ControlUnit.RearLeft2.ID 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.ControlUnit.RearLeft2.ID is an Attribute.
The vehicle signal Vehicle.ControlUnit.RearLeft2.ID is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.RearLeft2.ID is 0a9a70a673cd5a908cafea4333fa18ae
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
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.
5 - Trunk
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk |
| Description: |
Root of the control unit branch |
| Comment: |
The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Trunk is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk is 9e4e48d8cc6c58b7a7168095c8572956
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:
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.
5.1 - ID
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.ID |
| Description: |
Control unit ID |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->ID
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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).
The vehicle signal Vehicle.ControlUnit.Trunk.ID is an Attribute.
The vehicle signal Vehicle.ControlUnit.Trunk.ID is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.ID is 32b57a30dc905320b2bad520e89a92cc
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:
| 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.
5.2 - Health
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health |
| Description: |
Health attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Trunk.Health is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health is 5e824dd9232c5cb0a66348335be28c15
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:
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.
5.2.1 - Network
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Network |
| Description: |
Network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Health-->Network
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Network is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Network is e934dc1fe5de549f858d4287e6c1ab97
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:
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.
5.2.1.1 - CAN
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Network.CAN |
| Description: |
CAN network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->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.
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Network.CAN is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Network.CAN is 0009f5d443d65adb839b0e08fb64a2a0
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:
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.
5.2.1.1.1 - IsNetworkOK
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Network.CAN.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->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.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.
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Network.CAN.IsNetworkOK is 8541713d26e35cf99ced2687c7f03103
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:
| 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.
5.2.1.2 - ETH
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Network.ETH |
| Description: |
Ethernet network attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->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.
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Network.ETH is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Network.ETH is da00d7bb705c5566ad7befbd48a687cf
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:
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.
5.2.1.2.1 - IsNetworkOK
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Network.ETH.IsNetworkOK |
| Description: |
Network status. True = No network problems detected. False = Network problems detected. |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->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.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.
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Network.ETH.IsNetworkOK is cf381167b5de542caf54b2c2be355979
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:
| 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.
5.2.2 - Resources
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Resources |
| Description: |
Resources attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Health-->Resources
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Resources is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Resources is 8e41a31f205d5c3eb48665db9e9f2279
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:
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.
5.2.2.1 - Power
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Resources.Power |
| Description: |
Power consumption |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Health-->Resources
Resources-->Power
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Resources.Power is a Sensor.
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Resources.Power is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Resources.Power is 6f70873086b45589b850611c50a268ec
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:
| 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.
5.2.2.2 - Temperature
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Resources.Temperature |
| Description: |
Instance temperature |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Health-->Resources
Resources-->Temperature
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Resources.Temperature is a Sensor.
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Resources.Temperature is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Resources.Temperature is ad13d2b9102a5a6d80bf5d37bdf34397
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:
| 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.
5.2.2.3 - Utilization
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Resources.Utilization |
| Description: |
Resources utilization branch |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Health-->Resources
Resources-->Utilization
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Trunk.Health.Resources.Utilization is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Resources.Utilization is be8ef2441bfc509e87f073290c2a2ec4
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:
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.
5.2.2.3.1 - CPU
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Resources.Utilization.CPU |
| Description: |
CPU utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Health-->Resources
Resources-->Utilization
Utilization-->CPU
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Resources.Utilization.CPU is 9819ee5c82c858e7b74ef50653955c75
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:
| 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.
5.2.2.3.2 - Memory
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.Resources.Utilization.Memory |
| Description: |
Memory utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Trunk
Trunk-->Health
Health-->Resources
Resources-->Utilization
Utilization-->Memory
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Trunk.Health.Resources.Utilization.Memory is 796e76d88f905dc29fe25c3a04d60a86
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:
| 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.
5.2.3 - SWSupervision
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.SWSupervision |
| Description: |
SW supervision attributes and signals |
Navigation
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.
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:
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.
5.2.3.1 - IsLogicalTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsLogicalTriggered |
| Description: |
Whether the logical supervision was triggered |
Navigation
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.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.
5.2.3.2 - IsWatchdogTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsWatchdogTriggered |
| Description: |
Whether the watchdog deadline was triggered |
Navigation
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.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.
5.2.3.3 - IsAliveTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsAliveTriggered |
| Description: |
Whether the alive supervision was triggered |
Navigation
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.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.
5.2.3.4 - IsDeadlineTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Trunk.Health.SWSupervision.IsDeadlineTriggered |
| Description: |
Whether the deadline supervision was triggered |
Navigation
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.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.
6 - Central
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central |
| Description: |
Root of the control unit branch |
| Comment: |
The listed instances in the VSS standard catalog shall be seen as an example and can be customized as needed |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Central is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central is 3e7abc37a1e951f8b6f70ccf6394eb87
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:
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.
6.1 - ID
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.ID |
| Description: |
Control unit ID |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->ID
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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).
The vehicle signal Vehicle.ControlUnit.Central.ID is an Attribute.
The vehicle signal Vehicle.ControlUnit.Central.ID is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.ID is 39a03d78ab745a0ca5227e59f61ebc17
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:
| 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.
6.2 - Health
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health |
| Description: |
Health attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Central.Health is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health is 73ce14fb3078587bac4e955010f43469
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:
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.
6.2.1 - Network
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Network |
| Description: |
Network attributes and signals |
Navigation
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.
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:
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.
6.2.1.1 - CAN
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Network.CAN |
| Description: |
CAN network attributes and signals |
Navigation
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.
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:
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.
6.2.1.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. |
Navigation
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.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.
6.2.1.2 - ETH
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Network.ETH |
| Description: |
Ethernet network attributes and signals |
Navigation
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.
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:
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.
6.2.1.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. |
Navigation
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.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
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:
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.
6.2.2 - Resources
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Resources |
| Description: |
Resources attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Health-->Resources
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Central.Health.Resources is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.Resources is 9d52058d2ed25219b9fab1d0f6b68bf1
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:
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.
6.2.2.1 - Power
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Resources.Power |
| Description: |
Power consumption |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Health-->Resources
Resources-->Power
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
The vehicle signal Vehicle.ControlUnit.Central.Health.Resources.Power is a Sensor.
The vehicle signal Vehicle.ControlUnit.Central.Health.Resources.Power is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.Resources.Power is f442b72312445fe5b4a93730bdb1292b
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:
| 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.
6.2.2.2 - Temperature
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Resources.Temperature |
| Description: |
Instance temperature |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Health-->Resources
Resources-->Temperature
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
The vehicle signal Vehicle.ControlUnit.Central.Health.Resources.Temperature is a Sensor.
The vehicle signal Vehicle.ControlUnit.Central.Health.Resources.Temperature is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.Resources.Temperature is 4cf7808ce0cd555f83c020d83feafd26
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:
| 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.
6.2.2.3 - Utilization
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Resources.Utilization |
| Description: |
Resources utilization branch |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Health-->Resources
Resources-->Utilization
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Central.Health.Resources.Utilization is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.Resources.Utilization is 34f98d355cf9590fa181898a775be79b
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:
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.
6.2.2.3.1 - CPU
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Resources.Utilization.CPU |
| Description: |
CPU utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Health-->Resources
Resources-->Utilization
Utilization-->CPU
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.Resources.Utilization.CPU is 68af8bf9c56c50299a5352b2c09dd571
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:
| 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.
6.2.2.3.2 - Memory
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.Resources.Utilization.Memory |
| Description: |
Memory utilization |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Health-->Resources
Resources-->Utilization
Utilization-->Memory
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ControlUnit.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
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.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.Resources.Utilization.Memory is 709724dd51ff58eca52a77d4b195ca17
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:
| 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.
6.2.3 - SWSupervision
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.SWSupervision |
| Description: |
SW supervision attributes and signals |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->Health
Health-->SWSupervision
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.SWSupervision is f270e9c2882f5e48bf48d82c25799bfb
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:
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.
6.2.3.1 - IsAliveTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.SWSupervision.IsAliveTriggered |
| Description: |
Whether the alive supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->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.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.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsAliveTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsAliveTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.SWSupervision.IsAliveTriggered is f20b7c7f9c9f538d97baca31c2c08f1a
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:
| 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.
6.2.3.2 - IsDeadlineTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.SWSupervision.IsDeadlineTriggered |
| Description: |
Whether the deadline supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->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.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.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsDeadlineTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsDeadlineTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.SWSupervision.IsDeadlineTriggered is a2b5749cd452574a80594dd828e7086e
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:
| 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.
6.2.3.3 - IsLogicalTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.SWSupervision.IsLogicalTriggered |
| Description: |
Whether the logical supervision was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->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.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.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsLogicalTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsLogicalTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.SWSupervision.IsLogicalTriggered is 05fee3bf21c452baa5c17ed98a730c2e
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:
| 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.
6.2.3.4 - IsWatchdogTriggered
|
|
| Full qualified VSS Path: |
Vehicle.ControlUnit.Central.Health.SWSupervision.IsWatchdogTriggered |
| Description: |
Whether the watchdog deadline was triggered |
Navigation
flowchart LR
Vehicle-->ControlUnit
ControlUnit-->Central
Central-->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.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.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsWatchdogTriggered is a Sensor.
The vehicle signal Vehicle.ControlUnit.Central.Health.SWSupervision.IsWatchdogTriggered is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ControlUnit.Central.Health.SWSupervision.IsWatchdogTriggered is a72a1c22717a5bd0870af668d790916b
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:
| 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.