This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
ObstacleDetection
|
|
Full qualified VSS Path: |
Vehicle.ADAS.ObstacleDetection |
Description: |
Signals form Obstacle Sensor System. |
Navigation
flowchart LR
Vehicle-->ADAS
ADAS-->ObstacleDetection
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.ADAS.ObstacleDetection
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ADAS.ObstacleDetection
is e7b6d81631cc5ac584d027d4c1a66cb5
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 - IsEnabled
|
|
Full qualified VSS Path: |
Vehicle.ADAS.ObstacleDetection.IsEnabled |
Description: |
Indicates if obstacle sensor system is enabled (i.e. monitoring for obstacles). True = Enabled. False = Disabled. |
Navigation
flowchart LR
Vehicle-->ADAS
ADAS-->ObstacleDetection
ObstacleDetection-->IsEnabled
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ObstacleDetection.IsEnabled
[get] OK
Vehicle.ADAS.ObstacleDetection.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.IsEnabled 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.ADAS.ObstacleDetection.IsEnabled
is an Actuator.
The vehicle signal Vehicle.ADAS.ObstacleDetection.IsEnabled
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ADAS.ObstacleDetection.IsEnabled
is cc0cd497285e5034a1cccb25f02e9db9
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 - IsError
|
|
Full qualified VSS Path: |
Vehicle.ADAS.ObstacleDetection.IsError |
Description: |
Indicates if obstacle sensor system incurred an error condition. True = Error. False = No Error. |
Navigation
flowchart LR
Vehicle-->ADAS
ADAS-->ObstacleDetection
ObstacleDetection-->IsError
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ObstacleDetection.IsError
[get] OK
Vehicle.ADAS.ObstacleDetection.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.IsError 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.ADAS.ObstacleDetection.IsError
is a Sensor.
The vehicle signal Vehicle.ADAS.ObstacleDetection.IsError
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ADAS.ObstacleDetection.IsError
is 368b74e2468d5217925a478ed6e34f9f
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 - IsWarning
|
|
Full qualified VSS Path: |
Vehicle.ADAS.ObstacleDetection.IsWarning |
Description: |
Indicates if obstacle sensor system registered an obstacle. |
Navigation
flowchart LR
Vehicle-->ADAS
ADAS-->ObstacleDetection
ObstacleDetection-->IsWarning
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.ADAS.ObstacleDetection.IsWarning
[get] OK
Vehicle.ADAS.ObstacleDetection.IsWarning: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.IsWarning 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.ADAS.ObstacleDetection.IsWarning
is a Sensor.
The vehicle signal Vehicle.ADAS.ObstacleDetection.IsWarning
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.ADAS.ObstacleDetection.IsWarning
is b0b1eab51f135ffcb2a17a7603415fec
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.