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


Full qualified VSS Path:	`Vehicle.Occupant.Row1`
Description:	Occupant (Driver or Passenger) data.

flowchart LR Vehicle-->Occupant Occupant-->Row1

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

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1 is 66f753d5c1c6557388831aa460f580b0

Children

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

Vehicle.Occupant.Row1.DriverSide (Occupant (Driver or Passenger) data.)
Vehicle.Occupant.Row1.Middle (Occupant (Driver or Passenger) data.)
Vehicle.Occupant.Row1.PassengerSide (Occupant (Driver or Passenger) data.)

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 - DriverSide


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide`
Description:	Occupant (Driver or Passenger) data.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->DriverSide

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.DriverSide

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide is 49d88393d8555778b331b19c5c60f91e

Children

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

Vehicle.Occupant.Row1.DriverSide.HeadPosition (The current position of the driver head on vehicle axis according to ISO 23150:2023.)
Vehicle.Occupant.Row1.DriverSide.Identifier (Identifier attributes based on OAuth 2.0.)
Vehicle.Occupant.Row1.DriverSide.MidEyeGaze (Direction from mid eye position to object driver is looking at.)

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.1 - HeadPosition


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.HeadPosition`
Description:	The current position of the driver head on vehicle axis according to ISO 23150:2023.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->DriverSide DriverSide-->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.DriverSide.HeadPosition

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.HeadPosition is 4f780854e0205d8ab0347b1a00b45513

Children

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

Vehicle.Occupant.Row1.DriverSide.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.DriverSide.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.DriverSide.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.DriverSide.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.DriverSide.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.DriverSide.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.1.1 - Pitch


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.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-->DriverSide DriverSide-->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.DriverSide.HeadPosition.Pitch
[get]  OK
Vehicle.Occupant.Row1.DriverSide.HeadPosition.Pitch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Pitch

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Pitch is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.HeadPosition.Pitch is 24184d4116015ca78244e7113f53f9cc

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

1.1.1.2 - Roll


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.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-->DriverSide DriverSide-->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.DriverSide.HeadPosition.Roll
[get]  OK
Vehicle.Occupant.Row1.DriverSide.HeadPosition.Roll: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Roll

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Roll is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.HeadPosition.Roll is f4cf52cb4e8253a6a37337a6712d2eb4

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

1.1.1.3 - X


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.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-->DriverSide DriverSide-->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.DriverSide.HeadPosition.X
[get]  OK
Vehicle.Occupant.Row1.DriverSide.HeadPosition.X: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.X

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.X is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.HeadPosition.X is 669294afa3ca53ba94610c7725d3a777

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

1.1.1.4 - Y


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.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-->DriverSide DriverSide-->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.DriverSide.HeadPosition.Y
[get]  OK
Vehicle.Occupant.Row1.DriverSide.HeadPosition.Y: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Y

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Y is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.HeadPosition.Y is f78a146f62615fc196f2e0175f448c36

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

1.1.1.5 - Yaw


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.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-->DriverSide DriverSide-->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.DriverSide.HeadPosition.Yaw
[get]  OK
Vehicle.Occupant.Row1.DriverSide.HeadPosition.Yaw: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Yaw

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Yaw is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.HeadPosition.Yaw is e5362f14c81550f38b26a74676064172

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

1.1.1.6 - Z


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.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-->DriverSide DriverSide-->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.DriverSide.HeadPosition.Z
[get]  OK
Vehicle.Occupant.Row1.DriverSide.HeadPosition.Z: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Z

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.HeadPosition.Z is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.HeadPosition.Z is 21be15e24b225c4c825d3c14443107bc

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

1.1.2 - Identifier


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.Identifier`
Description:	Identifier attributes based on OAuth 2.0.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->DriverSide DriverSide-->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.DriverSide.Identifier

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.Identifier is 8e565c588b955a7d9cd56a065c89e516

Children

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

Vehicle.Occupant.Row1.DriverSide.Identifier.Issuer (Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.)
Vehicle.Occupant.Row1.DriverSide.Identifier.Subject (Subject for the authentication of the occupant e.g. UserID 7331677.)

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.2.1 - Issuer


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.Identifier.Issuer`
Description:	Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->DriverSide DriverSide-->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.DriverSide.Identifier.Issuer
[get]  OK
Vehicle.Occupant.Row1.DriverSide.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.Identifier.Issuer

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.Identifier.Issuer is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.Identifier.Issuer is f97f70d1be805fad801b925df888d638

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

1.1.2.2 - Subject


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.Identifier.Subject`
Description:	Subject for the authentication of the occupant e.g. UserID 7331677.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->DriverSide DriverSide-->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.DriverSide.Identifier.Subject
[get]  OK
Vehicle.Occupant.Row1.DriverSide.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.DriverSide.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.DriverSide.Identifier.Subject

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.Identifier.Subject is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.Identifier.Subject is e307c94cb9d45ee1851c0957dfe572ba

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

1.1.3 - MidEyeGaze


Full qualified VSS Path:	`Vehicle.Occupant.Row1.DriverSide.MidEyeGaze`
Description:	Direction from mid eye position to object driver is looking at.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->DriverSide DriverSide-->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.DriverSide.MidEyeGaze

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.MidEyeGaze is 4e6869d72ecf51f2a63b744118db723e

Children

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

Vehicle.Occupant.Row1.DriverSide.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.DriverSide.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.1.3.1 - Azimuth


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

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.MidEyeGaze.Azimuth is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.MidEyeGaze.Azimuth is 0273cb24210950aaa330e736fe66c1dc

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

1.1.3.2 - Elevation


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

Data Type & Unit


Path	`Vehicle.Occupant.Row1.DriverSide.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.DriverSide.MidEyeGaze.Elevation is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.DriverSide.MidEyeGaze.Elevation is a0989b2d4f06510cbe1220d3f5d34e9d

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

1.2 - Middle


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle`
Description:	Occupant (Driver or Passenger) data.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->Middle

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.Middle

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle is dc2eeeffc04559aaae315e3ef99eac79

Children

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

Vehicle.Occupant.Row1.Middle.HeadPosition (The current position of the driver head on vehicle axis according to ISO 23150:2023.)
Vehicle.Occupant.Row1.Middle.Identifier (Identifier attributes based on OAuth 2.0.)
Vehicle.Occupant.Row1.Middle.MidEyeGaze (Direction from mid eye position to object driver is looking at.)

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.2.1 - HeadPosition


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.HeadPosition`
Description:	The current position of the driver head on vehicle axis according to ISO 23150:2023.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->Middle Middle-->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.Middle.HeadPosition

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.HeadPosition is 9dc77abbb70d520aa95cb96d042f6d17

Children

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

Vehicle.Occupant.Row1.Middle.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.Middle.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.Middle.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.Middle.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.Middle.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.Middle.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.2.1.1 - Pitch


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.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-->Middle Middle-->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.Middle.HeadPosition.Pitch
[get]  OK
Vehicle.Occupant.Row1.Middle.HeadPosition.Pitch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Pitch

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Pitch is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.HeadPosition.Pitch is 0ef41c4346265a92be1e974ddf347d89

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

1.2.1.2 - Roll


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.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-->Middle Middle-->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.Middle.HeadPosition.Roll
[get]  OK
Vehicle.Occupant.Row1.Middle.HeadPosition.Roll: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Roll

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Roll is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.HeadPosition.Roll is ad47bfdcb1eb5463bc3c41eaa94eaabc

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

1.2.1.3 - X


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.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-->Middle Middle-->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.Middle.HeadPosition.X
[get]  OK
Vehicle.Occupant.Row1.Middle.HeadPosition.X: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.X

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.X is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.HeadPosition.X is a1cad252cf7a597aaba93d32784a126d

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

1.2.1.4 - Y


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.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-->Middle Middle-->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.Middle.HeadPosition.Y
[get]  OK
Vehicle.Occupant.Row1.Middle.HeadPosition.Y: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Y

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Y is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.HeadPosition.Y is c016f107005a5dfe8545a36cca929430

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

1.2.1.5 - Yaw


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.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-->Middle Middle-->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.Middle.HeadPosition.Yaw
[get]  OK
Vehicle.Occupant.Row1.Middle.HeadPosition.Yaw: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Yaw

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Yaw is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.HeadPosition.Yaw is 0c5b8b50463c58d7af30080df76f5820

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

1.2.1.6 - Z


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.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-->Middle Middle-->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.Middle.HeadPosition.Z
[get]  OK
Vehicle.Occupant.Row1.Middle.HeadPosition.Z: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Z

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.HeadPosition.Z is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.HeadPosition.Z is f1bb11674fb75c3e8ec61d53b2f7433b

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

1.2.2 - Identifier


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.Identifier`
Description:	Identifier attributes based on OAuth 2.0.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->Middle Middle-->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.Middle.Identifier

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.Identifier is 53ec9c25837b57ec9d9cee3964a27918

Children

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

Vehicle.Occupant.Row1.Middle.Identifier.Issuer (Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.)
Vehicle.Occupant.Row1.Middle.Identifier.Subject (Subject for the authentication of the occupant e.g. UserID 7331677.)

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.2.2.1 - Issuer


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.Identifier.Issuer`
Description:	Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->Middle Middle-->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.Middle.Identifier.Issuer
[get]  OK
Vehicle.Occupant.Row1.Middle.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.Identifier.Issuer

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.Identifier.Issuer is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.Identifier.Issuer is b4f12dfbffb4501383b4d4fe1a558108

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

1.2.2.2 - Subject


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.Identifier.Subject`
Description:	Subject for the authentication of the occupant e.g. UserID 7331677.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->Middle Middle-->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.Middle.Identifier.Subject
[get]  OK
Vehicle.Occupant.Row1.Middle.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row1.Middle.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.Middle.Identifier.Subject

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.Identifier.Subject is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.Identifier.Subject is 9ec61409eb97538daf3b9f86ac415f65

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

1.2.3 - MidEyeGaze


Full qualified VSS Path:	`Vehicle.Occupant.Row1.Middle.MidEyeGaze`
Description:	Direction from mid eye position to object driver is looking at.

flowchart LR Vehicle-->Occupant Occupant-->Row1 Row1-->Middle Middle-->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.Middle.MidEyeGaze

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.MidEyeGaze is c98236d5f2a25794977a3f1e25495345

Children

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

Vehicle.Occupant.Row1.Middle.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.Middle.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.2.3.1 - Azimuth


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

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.MidEyeGaze.Azimuth is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.MidEyeGaze.Azimuth is e0dc657083845a33b8e327612c6d833b

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

1.2.3.2 - Elevation


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

Data Type & Unit


Path	`Vehicle.Occupant.Row1.Middle.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.Middle.MidEyeGaze.Elevation is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row1.Middle.MidEyeGaze.Elevation is 9f7e80b4119553a98cbace5687b64e64

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

1.3 - 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:

Vehicle.Occupant.Row1.PassengerSide.HeadPosition (The current position of the driver head on vehicle axis according to ISO 23150:2023.)
Vehicle.Occupant.Row1.PassengerSide.Identifier (Identifier attributes based on OAuth 2.0.)
Vehicle.Occupant.Row1.PassengerSide.MidEyeGaze (Direction from mid eye position to object driver is looking at.)

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.3.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.3.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

1.3.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

1.3.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

1.3.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

1.3.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

1.3.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

1.3.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:

Vehicle.Occupant.Row1.PassengerSide.Identifier.Issuer (Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.)
Vehicle.Occupant.Row1.PassengerSide.Identifier.Subject (Subject for the authentication of the occupant e.g. UserID 7331677.)

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.3.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

1.3.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

1.3.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.

1.3.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

1.3.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

2 - Row2


Full qualified VSS Path:	`Vehicle.Occupant.Row2`
Description:	Occupant (Driver or Passenger) data.

flowchart LR Vehicle-->Occupant Occupant-->Row2

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

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row2 is 750e678708de5855b393e45c2b69a251

Children

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

Vehicle.Occupant.Row2.DriverSide (Occupant (Driver or Passenger) data.)
Vehicle.Occupant.Row2.Middle (Occupant (Driver or Passenger) data.)
Vehicle.Occupant.Row2.PassengerSide (Occupant (Driver or Passenger) data.)

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 - Middle


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle`
Description:	Occupant (Driver or Passenger) data.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->Middle

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.Middle

Signal Information

The vehicle signal Vehicle.Occupant.Row2.Middle is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle is 00b8c2475b7555d48ce8fea956280134

Children

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

Vehicle.Occupant.Row2.Middle.HeadPosition (The current position of the driver head on vehicle axis according to ISO 23150:2023.)
Vehicle.Occupant.Row2.Middle.Identifier (Identifier attributes based on OAuth 2.0.)
Vehicle.Occupant.Row2.Middle.MidEyeGaze (Direction from mid eye position to object driver is looking at.)

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.1 - HeadPosition


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.HeadPosition`
Description:	The current position of the driver head on vehicle axis according to ISO 23150:2023.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->Middle Middle-->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.Row2.Middle.HeadPosition

Signal Information

The vehicle signal Vehicle.Occupant.Row2.Middle.HeadPosition is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.HeadPosition is 6ee8230f930254f49886427d884a1cc0

Children

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

Vehicle.Occupant.Row2.Middle.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.Row2.Middle.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.Row2.Middle.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.Row2.Middle.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.Row2.Middle.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.Row2.Middle.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.

2.1.1.1 - Pitch


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.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-->Row2 Row2-->Middle Middle-->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.Row2.Middle.HeadPosition.Pitch
[get]  OK
Vehicle.Occupant.Row2.Middle.HeadPosition.Pitch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Pitch

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Pitch is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.HeadPosition.Pitch is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.HeadPosition.Pitch is c14f269395c25f6e9d2a201b1cdd855f

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

2.1.1.2 - Roll


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.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-->Row2 Row2-->Middle Middle-->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.Row2.Middle.HeadPosition.Roll
[get]  OK
Vehicle.Occupant.Row2.Middle.HeadPosition.Roll: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Roll

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Roll is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.HeadPosition.Roll is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.HeadPosition.Roll is 08c07e4df47d59d0a013358ea01ca584

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

2.1.1.3 - X


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.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-->Row2 Row2-->Middle Middle-->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.Row2.Middle.HeadPosition.X
[get]  OK
Vehicle.Occupant.Row2.Middle.HeadPosition.X: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.X

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.X is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.HeadPosition.X is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.HeadPosition.X is c2864d33fdca5f1d8494cf4f6cb924a9

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

2.1.1.4 - Y


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.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-->Row2 Row2-->Middle Middle-->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.Row2.Middle.HeadPosition.Y
[get]  OK
Vehicle.Occupant.Row2.Middle.HeadPosition.Y: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Y

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Y is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.HeadPosition.Y is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.HeadPosition.Y is 5c97946c598650668765d7f116eee2ec

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

2.1.1.5 - Yaw


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.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-->Row2 Row2-->Middle Middle-->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.Row2.Middle.HeadPosition.Yaw
[get]  OK
Vehicle.Occupant.Row2.Middle.HeadPosition.Yaw: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Yaw

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Yaw is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.HeadPosition.Yaw is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.HeadPosition.Yaw is 3deb3674741554b7a3ad9646b8233532

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

2.1.1.6 - Z


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.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-->Row2 Row2-->Middle Middle-->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.Row2.Middle.HeadPosition.Z
[get]  OK
Vehicle.Occupant.Row2.Middle.HeadPosition.Z: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Z

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.HeadPosition.Z is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.HeadPosition.Z is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.HeadPosition.Z is 0bd55b22d0435448a10e9f48a2caf2b2

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

2.1.2 - Identifier


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.Identifier`
Description:	Identifier attributes based on OAuth 2.0.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->Middle Middle-->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.Row2.Middle.Identifier

Signal Information

The vehicle signal Vehicle.Occupant.Row2.Middle.Identifier is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.Identifier is 9fdb1309f85e5d5e8f4a89b71819f472

Children

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

Vehicle.Occupant.Row2.Middle.Identifier.Issuer (Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.)
Vehicle.Occupant.Row2.Middle.Identifier.Subject (Subject for the authentication of the occupant e.g. UserID 7331677.)

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.2.1 - Issuer


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.Identifier.Issuer`
Description:	Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->Middle Middle-->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.Row2.Middle.Identifier.Issuer
[get]  OK
Vehicle.Occupant.Row2.Middle.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.Identifier.Issuer

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.Identifier.Issuer is 878576740c0d50d6aea85bf437575e4d

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

2.1.2.2 - Subject


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.Identifier.Subject`
Description:	Subject for the authentication of the occupant e.g. UserID 7331677.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->Middle Middle-->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.Row2.Middle.Identifier.Subject
[get]  OK
Vehicle.Occupant.Row2.Middle.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.Middle.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.Row2.Middle.Identifier.Subject

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Row2.Middle.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.Middle.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.Identifier.Subject is f85e10b1a8d65e75930374c588a56b80

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

2.1.3 - MidEyeGaze


Full qualified VSS Path:	`Vehicle.Occupant.Row2.Middle.MidEyeGaze`
Description:	Direction from mid eye position to object driver is looking at.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->Middle Middle-->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.Middle.MidEyeGaze

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.MidEyeGaze is 5794864972575c048b0f8262e88729f5

Children

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

Vehicle.Occupant.Row2.Middle.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.Middle.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.

2.1.3.1 - Azimuth


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

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Middle.MidEyeGaze.Azimuth is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.MidEyeGaze.Azimuth is 20033f2800005040bfb57bc270a98a23

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

2.1.3.2 - Elevation


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

Data Type & Unit


Path	`Vehicle.Occupant.Row2.Middle.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.Middle.MidEyeGaze.Elevation is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.Middle.MidEyeGaze.Elevation is ca56a79f619f591e91263c7ece92e31a

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

2.2 - PassengerSide


Full qualified VSS Path:	`Vehicle.Occupant.Row2.PassengerSide`
Description:	Occupant (Driver or Passenger) data.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->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.Row2.PassengerSide

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide is 74f49a22daf158aab9ddeaf75abfe5ac

Children

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

Vehicle.Occupant.Row2.PassengerSide.HeadPosition (The current position of the driver head on vehicle axis according to ISO 23150:2023.)
Vehicle.Occupant.Row2.PassengerSide.Identifier (Identifier attributes based on OAuth 2.0.)
Vehicle.Occupant.Row2.PassengerSide.MidEyeGaze (Direction from mid eye position to object driver is looking at.)

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.2.1 - HeadPosition


Full qualified VSS Path:	`Vehicle.Occupant.Row2.PassengerSide.HeadPosition`
Description:	The current position of the driver head on vehicle axis according to ISO 23150:2023.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->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.Row2.PassengerSide.HeadPosition

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.HeadPosition is 89267dd9ab785563a97088e6a03f6738

Children

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

Vehicle.Occupant.Row2.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.Row2.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.Row2.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.Row2.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.Row2.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.Row2.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.

2.2.1.1 - Pitch


Full qualified VSS Path:	`Vehicle.Occupant.Row2.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-->Row2 Row2-->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.Row2.PassengerSide.HeadPosition.Pitch
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Pitch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Pitch

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Pitch is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Pitch is 1621e4d2e83c5228a8a8186993a8721f

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

2.2.1.2 - Roll


Full qualified VSS Path:	`Vehicle.Occupant.Row2.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-->Row2 Row2-->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.Row2.PassengerSide.HeadPosition.Roll
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Roll: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Roll

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Roll is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Roll is c642637931305398b68e8a7bfa8e670c

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

2.2.1.3 - X


Full qualified VSS Path:	`Vehicle.Occupant.Row2.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-->Row2 Row2-->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.Row2.PassengerSide.HeadPosition.X
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.HeadPosition.X: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.X

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.X is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.HeadPosition.X is d21c93bbe88459c99df6e7b86eced3d3

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

2.2.1.4 - Y


Full qualified VSS Path:	`Vehicle.Occupant.Row2.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-->Row2 Row2-->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.Row2.PassengerSide.HeadPosition.Y
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Y: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Y

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Y is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Y is 2c56feb8f82f51fe9a9ca692a151becf

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

2.2.1.5 - Yaw


Full qualified VSS Path:	`Vehicle.Occupant.Row2.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-->Row2 Row2-->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.Row2.PassengerSide.HeadPosition.Yaw
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Yaw: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Yaw

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Yaw is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Yaw is 071d4a9b940558229919e195cab4b128

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

2.2.1.6 - Z


Full qualified VSS Path:	`Vehicle.Occupant.Row2.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-->Row2 Row2-->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.Row2.PassengerSide.HeadPosition.Z
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Z: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Z

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.HeadPosition.Z is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.HeadPosition.Z is d3211d821eb25349b1821208224abe7f

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

2.2.2 - Identifier


Full qualified VSS Path:	`Vehicle.Occupant.Row2.PassengerSide.Identifier`
Description:	Identifier attributes based on OAuth 2.0.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->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.Row2.PassengerSide.Identifier

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.Identifier is 653279c6ce8e5952a3da705c78b85d64

Children

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

Vehicle.Occupant.Row2.PassengerSide.Identifier.Issuer (Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.)
Vehicle.Occupant.Row2.PassengerSide.Identifier.Subject (Subject for the authentication of the occupant e.g. UserID 7331677.)

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.2.2.1 - Issuer


Full qualified VSS Path:	`Vehicle.Occupant.Row2.PassengerSide.Identifier.Issuer`
Description:	Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->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.Row2.PassengerSide.Identifier.Issuer
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.Identifier.Issuer

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.Identifier.Issuer is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.Identifier.Issuer is 7ca8b9f5bcfa57dbb9d38b18e85136c0

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

2.2.2.2 - Subject


Full qualified VSS Path:	`Vehicle.Occupant.Row2.PassengerSide.Identifier.Subject`
Description:	Subject for the authentication of the occupant e.g. UserID 7331677.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->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.Row2.PassengerSide.Identifier.Subject
[get]  OK
Vehicle.Occupant.Row2.PassengerSide.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.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.Row2.PassengerSide.Identifier.Subject

Data Type & Unit


Path	`Vehicle.Occupant.Row2.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.Row2.PassengerSide.Identifier.Subject is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.PassengerSide.Identifier.Subject is bafe3d40eb235498b8fd0bf86d8b2ebe

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

2.2.3 - 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.

2.2.3.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

2.2.3.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

2.3 - DriverSide


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide`
Description:	Occupant (Driver or Passenger) data.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->DriverSide

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.DriverSide

Signal Information

The vehicle signal Vehicle.Occupant.Row2.DriverSide is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide is c6c3f443ac2e516e8b7cd80a6b180e31

Children

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

Vehicle.Occupant.Row2.DriverSide.HeadPosition (The current position of the driver head on vehicle axis according to ISO 23150:2023.)
Vehicle.Occupant.Row2.DriverSide.Identifier (Identifier attributes based on OAuth 2.0.)
Vehicle.Occupant.Row2.DriverSide.MidEyeGaze (Direction from mid eye position to object driver is looking at.)

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.3.1 - HeadPosition


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.HeadPosition`
Description:	The current position of the driver head on vehicle axis according to ISO 23150:2023.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.HeadPosition

Signal Information

The vehicle signal Vehicle.Occupant.Row2.DriverSide.HeadPosition is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.HeadPosition is bf6a0584eb8b5a7fb26e66217673fda6

Children

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

Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.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.Row2.DriverSide.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.Row2.DriverSide.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.Row2.DriverSide.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.Row2.DriverSide.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.

2.3.1.1 - Pitch


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.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-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.HeadPosition.Pitch
[get]  OK
Vehicle.Occupant.Row2.DriverSide.HeadPosition.Pitch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Pitch

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Pitch is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.HeadPosition.Pitch is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.HeadPosition.Pitch is e3c46fc7a5a550b3813370f06279950e

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

2.3.1.2 - Roll


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.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-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.HeadPosition.Roll
[get]  OK
Vehicle.Occupant.Row2.DriverSide.HeadPosition.Roll: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Roll

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Roll is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.HeadPosition.Roll is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.HeadPosition.Roll is d14a0b33b7c35a5b9ec87f2da5694453

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

2.3.1.3 - X


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.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-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.HeadPosition.X
[get]  OK
Vehicle.Occupant.Row2.DriverSide.HeadPosition.X: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.X

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.X is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.HeadPosition.X is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.HeadPosition.X is fe1fb3d4425f59f6916954121960d690

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

2.3.1.4 - Y


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.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-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.HeadPosition.Y
[get]  OK
Vehicle.Occupant.Row2.DriverSide.HeadPosition.Y: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Y

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Y is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.HeadPosition.Y is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.HeadPosition.Y is 5cc9ed20d04b548d9cb082e876797585

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

2.3.1.5 - Yaw


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.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-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.HeadPosition.Yaw
[get]  OK
Vehicle.Occupant.Row2.DriverSide.HeadPosition.Yaw: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Yaw

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Yaw is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.HeadPosition.Yaw is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.HeadPosition.Yaw is b03251103f8c5b018259f4c1f8ae7e68

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

2.3.1.6 - Z


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.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-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.HeadPosition.Z
[get]  OK
Vehicle.Occupant.Row2.DriverSide.HeadPosition.Z: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Z

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.HeadPosition.Z is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.HeadPosition.Z is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.HeadPosition.Z is c403eb440e085247b7210930eaca7745

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

2.3.2 - MidEyeGaze


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.MidEyeGaze`
Description:	Direction from mid eye position to object driver is looking at.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->DriverSide DriverSide-->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.DriverSide.MidEyeGaze

Signal Information

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

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.MidEyeGaze is c349e0a9afa95020a74b1cea60f1cb0e

Children

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

Vehicle.Occupant.Row2.DriverSide.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.DriverSide.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.

2.3.2.1 - Azimuth


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

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.DriverSide.MidEyeGaze.Azimuth is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.MidEyeGaze.Azimuth is e55a2a56a6205c64825fdacf24003b00

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

2.3.2.2 - Elevation


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

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.DriverSide.MidEyeGaze.Elevation is a Sensor.

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

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.MidEyeGaze.Elevation is 1e8b21ad6a9855e9a75150722b43ae22

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

2.3.3 - Identifier


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.Identifier`
Description:	Identifier attributes based on OAuth 2.0.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.Identifier

Signal Information

The vehicle signal Vehicle.Occupant.Row2.DriverSide.Identifier is a Branch.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.Identifier is 370982d13eee5e408dd41dcb7bb17c3b

Children

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

Vehicle.Occupant.Row2.DriverSide.Identifier.Issuer (Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.)
Vehicle.Occupant.Row2.DriverSide.Identifier.Subject (Subject for the authentication of the occupant e.g. UserID 7331677.)

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.3.3.1 - Issuer


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.Identifier.Issuer`
Description:	Unique Issuer for the authentication of the occupant e.g. https://accounts.funcorp.com.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.Identifier.Issuer
[get]  OK
Vehicle.Occupant.Row2.DriverSide.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.Identifier.Issuer

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.Identifier.Issuer is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.Identifier.Issuer is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.Identifier.Issuer is 0b15bde15dea59639c192a301ea03c09

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

2.3.3.2 - Subject


Full qualified VSS Path:	`Vehicle.Occupant.Row2.DriverSide.Identifier.Subject`
Description:	Subject for the authentication of the occupant e.g. UserID 7331677.

flowchart LR Vehicle-->Occupant Occupant-->Row2 Row2-->DriverSide DriverSide-->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.Row2.DriverSide.Identifier.Subject
[get]  OK
Vehicle.Occupant.Row2.DriverSide.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.Identifier.Subject

Data Type & Unit


Path	`Vehicle.Occupant.Row2.DriverSide.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.Row2.DriverSide.Identifier.Subject is a Sensor.

The vehicle signal Vehicle.Occupant.Row2.DriverSide.Identifier.Subject is a Signal.

UUID

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

The UUID for Vehicle.Occupant.Row2.DriverSide.Identifier.Subject is 4c6821a6567c5b2c9d59310006a21ab7

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

Occupant

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1 - Row1

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1 - DriverSide

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1.1 - HeadPosition

Navigation

Digital Auto: Playground

Signal Information

UUID

Children

Feedback

About VSS

1.1.1.1 - Pitch

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.1.2 - Roll

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.1.3 - X

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.1.4 - Y

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback

About VSS

Supported datatypes

1.1.1.5 - Yaw

Navigation

Eclipse Leda: Usage Example

Digital Auto: Playground

Data Type & Unit

Signal Information

UUID

Feedback