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

Return to the regular view of this page.

MidEyeGaze
Full qualified VSS Path: Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze
Description: Direction from mid eye position to object driver is looking at.
flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->PassengerSide PassengerSide-->MidEyeGaze

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.Occupant.Row2.PassengerSide.MidEyeGaze

Signal Information

The vehicle signal Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze is faecf64bf570546bbada87c53a102df6

Children

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

  • Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth (Mid eye azimuth gaze (right-hand rule) on vehicle sprung mass Z-axis as defined by ISO 23150:2023 0 = Driver looking forward. Positive values = Driver looking at something on the left side of driver. Negative values = Driver looking at something on the right side of driver.)
  • Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation (Elevation to observed object measured as angle between vehicle sprung mass XY-plane as defined by ISO 23150:2023 at driver mid eye position and object. 0 = Driver looking at something at same height as mid eye position. Positive values = Driver looking at something above mid eye position. Negative values = Driver looking at something below mid eye position.)

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 - Azimuth
Full qualified VSS Path: Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth
Description: Mid eye azimuth gaze (right-hand rule) on vehicle sprung mass Z-axis as defined by ISO 23150:2023 0 = Driver looking forward. Positive values = Driver looking at something on the left side of driver. Negative values = Driver looking at something on the right side of driver.
flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->PassengerSide PassengerSide-->MidEyeGaze MidEyeGaze-->Azimuth

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth 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.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth

Data Type & Unit
Path Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle
Minimum value -180 VSS: Sensors & Actuators
Maximum value 180 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.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Azimuth is 4d65415d915e54e2b2f185077cf63f60

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 - Elevation
Full qualified VSS Path: Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation
Description: Elevation to observed object measured as angle between vehicle sprung mass XY-plane as defined by ISO 23150:2023 at driver mid eye position and object. 0 = Driver looking at something at same height as mid eye position. Positive values = Driver looking at something above mid eye position. Negative values = Driver looking at something below mid eye position.
flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->PassengerSide PassengerSide-->MidEyeGaze MidEyeGaze-->Elevation

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation 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.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation

Data Type & Unit
Path Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle
Minimum value -90 VSS: Sensors & Actuators
Maximum value 90 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.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze.Elevation is 97dc8ee2d74a5d9aa065beb5795f5d4a

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.