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

Return to the regular view of this page.

PassengerSide
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide
Description: Occupant (Driver or Passenger) data.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide

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.Row1.PassengerSide

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide is f8e6e66800f65da1adce3bbcb4757bff

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 - HeadPosition
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.HeadPosition
Description: The current position of the driver head on vehicle axis according to ISO 23150:2023.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->HeadPosition

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.Row1.PassengerSide.HeadPosition

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.HeadPosition is a5ca4a4fa5ac59fdbb28a0ce2060bf66

Children

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

  • Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Pitch (Head pitch angle, measured as angle from vehicle sprung mass XY-plane as defined by ISO 23150:2023 to the head X-axis. 0 = Head in normal position. Positive values = Head leaning up. Negative values = Head leaning down.)
  • Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Roll (Head roll angle about the head X-axis (right-hand rule). 0 = Head in normal position. Positive values = Head leaning to the right. Negative values = Head leaning to the left.)
  • Vehicle.Occupant.Row1.PassengerSide.HeadPosition.X (Longitudinal position of head center measured as mid eye position on X-axis of the vehicle rear-axle coordinate system as defined by ISO 23150:2023 section 3.7.12 Mid eye position refers to the center of a line drawn between the center of the drivers eyes. Positive values = forward of (first) rear-axle. Negative values = backward of (first) rear-axle.)
  • Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Y (Lateral position of head center measured as mid eye position on X-axis of the vehicle rear-axle coordinate system as defined by ISO 23150:2023 section 3.7.12 Mid eye position refers to the center of a line drawn between the center of the drivers eyes. Positive values = left of rear-axle center. Negative values = right of rear-axle center.)
  • Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Yaw (Head yaw angle, measured from the vehicle sprung mass X-axis as defined by ISO 23150:2023 to the head X-axis, around the vehicle Z-axis (right-hand rule). 0 = Head in normal position. Positive values = Head turned left. Negative values = Head turned right.)
  • Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Z (Height position of head center measured as mid eye position on X-axis of the vehicle rear-axle coordinate system as defined by ISO 23150:2023 section 3.7.12 Mid eye position refers to the center of a line drawn between the center of the drivers eyes. Positive values = above center of rear-axle reference point. Negative values = below center of rear-axle reference point.)

Feedback

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

About VSS

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

1.1 - Pitch
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Pitch
Description: Head pitch angle, measured as angle from vehicle sprung mass XY-plane as defined by ISO 23150:2023 to the head X-axis. 0 = Head in normal position. Positive values = Head leaning up. Negative values = Head leaning down.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->HeadPosition HeadPosition-->Pitch

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Pitch 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.Row1.PassengerSide.HeadPosition.Pitch is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Pitch is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Pitch is 7a86a41ad6705d80b8930eaf4a2c1a90

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.

1.2 - Roll
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Roll
Description: Head roll angle about the head X-axis (right-hand rule). 0 = Head in normal position. Positive values = Head leaning to the right. Negative values = Head leaning to the left.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->HeadPosition HeadPosition-->Roll

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Roll 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.Row1.PassengerSide.HeadPosition.Roll is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Roll is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Roll is 68d83b45e15c5e8581f445fa42698e7d

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.

1.3 - X
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.HeadPosition.X
Description: Longitudinal position of head center measured as mid eye position on X-axis of the vehicle rear-axle coordinate system as defined by ISO 23150:2023 section 3.7.12 Mid eye position refers to the center of a line drawn between the center of the drivers eyes. Positive values = forward of (first) rear-axle. Negative values = backward of (first) rear-axle.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->HeadPosition HeadPosition-->X

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.HeadPosition.X VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Length measured in millimeters VSS: Sensors & Actuators
Domain length

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.X is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.X is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.HeadPosition.X is b849cc49db1c59d7ba1f1f4bc1aa8508

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.

1.4 - Y
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Y
Description: Lateral position of head center measured as mid eye position on X-axis of the vehicle rear-axle coordinate system as defined by ISO 23150:2023 section 3.7.12 Mid eye position refers to the center of a line drawn between the center of the drivers eyes. Positive values = left of rear-axle center. Negative values = right of rear-axle center.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->HeadPosition HeadPosition-->Y

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Y VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Length measured in millimeters VSS: Sensors & Actuators
Domain length

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Y is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Y is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Y is 58e4545f7ac25a529c8caf30e9794946

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.

1.5 - Yaw
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Yaw
Description: Head yaw angle, measured from the vehicle sprung mass X-axis as defined by ISO 23150:2023 to the head X-axis, around the vehicle Z-axis (right-hand rule). 0 = Head in normal position. Positive values = Head turned left. Negative values = Head turned right.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->HeadPosition HeadPosition-->Yaw

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Yaw 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.Row1.PassengerSide.HeadPosition.Yaw is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Yaw is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Yaw is 8ed8b3c47ca05db9b4334493a3c7c71c

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.

1.6 - Z
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Z
Description: Height position of head center measured as mid eye position on X-axis of the vehicle rear-axle coordinate system as defined by ISO 23150:2023 section 3.7.12 Mid eye position refers to the center of a line drawn between the center of the drivers eyes. Positive values = above center of rear-axle reference point. Negative values = below center of rear-axle reference point.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->HeadPosition HeadPosition-->Z

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Z VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Length measured in millimeters VSS: Sensors & Actuators
Domain length

Note: The int16 datatype is a signed 16-bit integer which technically allows values between -32768 and 32767 (inclusive).

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Z is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Z is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.HeadPosition.Z is c7998e713b1b5e09a790126705f36e6d

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 - Identifier
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.Identifier
Description: Identifier attributes based on OAuth 2.0.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->Identifier

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.Row1.PassengerSide.Identifier

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.Identifier is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.Identifier is 99bd20324b7a52dc9d5a0d928842e891

Children

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

Feedback

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

About VSS

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

2.1 - Issuer
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.Identifier.Issuer
Description: Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->Identifier Identifier-->Issuer

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.Identifier.Issuer VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.Identifier.Issuer is aa2b6b1049045a94b0b5b3a002e45131

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.2 - Subject
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.Identifier.Subject
Description: Subject for the authentication of the occupant e.g. UserID 7331677.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->PassengerSide PassengerSide-->Identifier Identifier-->Subject

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

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

Data Type & Unit
Path Vehicle.Occupant.Row1.PassengerSide.Identifier.Subject VSS: Addressing nodes
Data type string VSS: Datatypes

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Occupant.Row1.PassengerSide.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.Identifier.Subject is 11ae8c9b4ce75d219f197b2a375805bc

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 - MidEyeGaze
Full qualified VSS Path: Vehicle.Occupant.Row1.PassengerSide.MidEyeGaze
Description: Direction from mid eye position to object driver is looking at.
flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->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.Row1.PassengerSide.MidEyeGaze

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.MidEyeGaze is d1fc6b599ef5557c9542b054f992a61d

Children

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

  • Vehicle.Occupant.Row1.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.Row1.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.

3.1 - Azimuth
Full qualified VSS Path: Vehicle.Occupant.Row1.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-->Row1 Row1-->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.Row1.PassengerSide.MidEyeGaze.Azimuth
[get]  OK
Vehicle.Occupant.Row1.PassengerSide.MidEyeGaze.Azimuth: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.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.Row1.PassengerSide.MidEyeGaze.Azimuth

Data Type & Unit
Path Vehicle.Occupant.Row1.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.Row1.PassengerSide.MidEyeGaze.Azimuth is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.MidEyeGaze.Azimuth is 00ccbe76c6e454a7955a09c67b46106a

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.2 - Elevation
Full qualified VSS Path: Vehicle.Occupant.Row1.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-->Row1 Row1-->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.Row1.PassengerSide.MidEyeGaze.Elevation
[get]  OK
Vehicle.Occupant.Row1.PassengerSide.MidEyeGaze.Elevation: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.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.Row1.PassengerSide.MidEyeGaze.Elevation

Data Type & Unit
Path Vehicle.Occupant.Row1.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.Row1.PassengerSide.MidEyeGaze.Elevation is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.PassengerSide.MidEyeGaze.Elevation is 818c7eff547150b3bfbd90a6683942f9

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.