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

Return to the regular view of this page.

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.

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

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

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

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

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

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

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

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

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

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

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

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