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

Return to the regular view of this page.

Left
Full qualified VSS Path: Vehicle.ADAS.ObstacleDetection.Rear.Left
Description: Signals form Obstacle Sensor System.
flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->Rear Rear-->Left

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ADAS.ObstacleDetection.Rear.Left

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left is a Branch.

Children

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

Feedback

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

About VSS

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

1 - Distance
Full qualified VSS Path: Vehicle.ADAS.ObstacleDetection.Rear.Left.Distance
Description: Distance in meters to detected object
flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->Rear Rear-->Left Left-->Distance

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.Rear.Left.Distance
[get]  OK
Vehicle.ADAS.ObstacleDetection.Rear.Left.Distance: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.Rear.Left.Distance 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ADAS.ObstacleDetection.Rear.Left.Distance

Data Type & Unit
Path Vehicle.ADAS.ObstacleDetection.Rear.Left.Distance VSS: Addressing nodes
Data type float VSS: Datatypes
Unit m VSS: Units
Label meter
Description Length measured in meters VSS: Sensors & Actuators
Domain length
Minimum value 0.0 VSS: Sensors & Actuators

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.Distance is a Sensor.

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.Distance is a Signal.

Feedback

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

About VSS

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

Supported datatypes

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

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

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

2 - IsEnabled
Full qualified VSS Path: Vehicle.ADAS.ObstacleDetection.Rear.Left.IsEnabled
Description: Indicates if obstacle sensor system is enabled (i.e. monitoring for obstacles). True = Enabled. False = Disabled.
flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->Rear Rear-->Left Left-->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.Rear.Left.IsEnabled
[get]  OK
Vehicle.ADAS.ObstacleDetection.Rear.Left.IsEnabled: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.Rear.Left.IsEnabled false
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ADAS.ObstacleDetection.Rear.Left.IsEnabled

Data Type & Unit
Path Vehicle.ADAS.ObstacleDetection.Rear.Left.IsEnabled VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.IsEnabled is an Actuator.

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.IsEnabled is a Signal.

Feedback

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

About VSS

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

Supported datatypes

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

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

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

3 - IsError
Full qualified VSS Path: Vehicle.ADAS.ObstacleDetection.Rear.Left.IsError
Description: Indicates if obstacle sensor system incurred an error condition. True = Error. False = No Error.
flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->Rear Rear-->Left Left-->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.Rear.Left.IsError
[get]  OK
Vehicle.ADAS.ObstacleDetection.Rear.Left.IsError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.Rear.Left.IsError false
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ADAS.ObstacleDetection.Rear.Left.IsError

Data Type & Unit
Path Vehicle.ADAS.ObstacleDetection.Rear.Left.IsError VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.IsError is a Sensor.

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.IsError is a Signal.

Feedback

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

About VSS

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

Supported datatypes

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

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

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

4 - IsWarning
Full qualified VSS Path: Vehicle.ADAS.ObstacleDetection.Rear.Left.IsWarning
Description: Indicates if obstacle sensor system registered an obstacle.
flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->Rear Rear-->Left Left-->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.Rear.Left.IsWarning
[get]  OK
Vehicle.ADAS.ObstacleDetection.Rear.Left.IsWarning: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.Rear.Left.IsWarning false
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ADAS.ObstacleDetection.Rear.Left.IsWarning

Data Type & Unit
Path Vehicle.ADAS.ObstacleDetection.Rear.Left.IsWarning VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.IsWarning is a Sensor.

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.IsWarning is a Signal.

Feedback

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

About VSS

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

Supported datatypes

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

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

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

5 - TimeGap
Full qualified VSS Path: Vehicle.ADAS.ObstacleDetection.Rear.Left.TimeGap
Description: Time in milliseconds before potential impact object
flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->Rear Rear-->Left Left-->TimeGap

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.Rear.Left.TimeGap
[get]  OK
Vehicle.ADAS.ObstacleDetection.Rear.Left.TimeGap: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.Rear.Left.TimeGap 0
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ADAS.ObstacleDetection.Rear.Left.TimeGap

Data Type & Unit
Path Vehicle.ADAS.ObstacleDetection.Rear.Left.TimeGap VSS: Addressing nodes
Data type uint32 VSS: Datatypes
Unit ms VSS: Units
Label millisecond
Description Duration measured in milliseconds VSS: Sensors & Actuators
Domain duration

Note: The uint32 datatype is an unsigned 32-bit integer which technically allows values between 0 and 4294967295 (inclusive).

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.TimeGap is a Sensor.

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.TimeGap is a Signal.

Feedback

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

About VSS

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

Supported datatypes

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

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

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

6 - WarningType
Full qualified VSS Path: Vehicle.ADAS.ObstacleDetection.Rear.Left.WarningType
Description: Indicates the type of obstacle warning detected as some track not only the presence of an obstacle but potential intercepting trajectory or other characteristics.
Comment: Undefined obstacle warning type would merely alert of presence of obstacle and may measure distance.
flowchart LR Vehicle-->ADAS ADAS-->ObstacleDetection ObstacleDetection-->Rear Rear-->Left Left-->WarningType

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.Rear.Left.WarningType
[get]  OK
Vehicle.ADAS.ObstacleDetection.Rear.Left.WarningType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.ADAS.ObstacleDetection.Rear.Left.WarningType Foo
[set]  OK

Digital Auto: Playground

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

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.ADAS.ObstacleDetection.Rear.Left.WarningType

Data Type & Unit
Path Vehicle.ADAS.ObstacleDetection.Rear.Left.WarningType VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['UNDEFINED', 'CROSS_TRAFFIC', 'BLIND_SPOT'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.WarningType is a Sensor.

The vehicle signal Vehicle.ADAS.ObstacleDetection.Rear.Left.WarningType is a Signal.

Feedback

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

About VSS

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

Supported datatypes

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

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

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