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

Return to the regular view of this page.

GNSSReceiver
Full qualified VSS Path: Vehicle.CurrentLocation.GNSSReceiver
Description: Information on the GNSS receiver used for determining current location.
flowchart LR Vehicle-->CurrentLocation CurrentLocation-->GNSSReceiver

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.CurrentLocation.GNSSReceiver

Signal Information

The vehicle signal Vehicle.CurrentLocation.GNSSReceiver is a Branch.

UUID

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

The UUID for Vehicle.CurrentLocation.GNSSReceiver is b1bea5d88662539a8cff6f8fe4974740

Children

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

Feedback

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

About VSS

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

1 - FixType
Full qualified VSS Path: Vehicle.CurrentLocation.GNSSReceiver.FixType
Description: Fix status of GNSS receiver.
flowchart LR Vehicle-->CurrentLocation CurrentLocation-->GNSSReceiver GNSSReceiver-->FixType

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.CurrentLocation.GNSSReceiver.FixType
[get]  OK
Vehicle.CurrentLocation.GNSSReceiver.FixType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.CurrentLocation.GNSSReceiver.FixType 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.CurrentLocation.GNSSReceiver.FixType

Data Type & Unit
Path Vehicle.CurrentLocation.GNSSReceiver.FixType VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['NONE', 'TWO_D', 'TWO_D_SATELLITE_BASED_AUGMENTATION', 'TWO_D_GROUND_BASED_AUGMENTATION', 'TWO_D_SATELLITE_AND_GROUND_BASED_AUGMENTATION', 'THREE_D', 'THREE_D_SATELLITE_BASED_AUGMENTATION', 'THREE_D_GROUND_BASED_AUGMENTATION', 'THREE_D_SATELLITE_AND_GROUND_BASED_AUGMENTATION'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

The vehicle signal Vehicle.CurrentLocation.GNSSReceiver.FixType is a Sensor.

The vehicle signal Vehicle.CurrentLocation.GNSSReceiver.FixType is a Signal.

UUID

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

The UUID for Vehicle.CurrentLocation.GNSSReceiver.FixType is 52853b33d4605608bd0ae50595c69309

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 - MountingPosition
Full qualified VSS Path: Vehicle.CurrentLocation.GNSSReceiver.MountingPosition
Description: Mounting position of GNSS receiver antenna relative to vehicle coordinate system. Axis definitions according to ISO 8855. Origin at center of (first) rear axle.
flowchart LR Vehicle-->CurrentLocation CurrentLocation-->GNSSReceiver GNSSReceiver-->MountingPosition

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.CurrentLocation.GNSSReceiver.MountingPosition

Signal Information

The vehicle signal Vehicle.CurrentLocation.GNSSReceiver.MountingPosition is a Branch.

UUID

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

The UUID for Vehicle.CurrentLocation.GNSSReceiver.MountingPosition is 5c0887bce6fb5eb79402baaccb203e61

Children

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

  • Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.X (Mounting position of GNSS receiver antenna relative to vehicle coordinate system. Axis definitions according to ISO 8855. Origin at center of (first) rear axle. Positive values = forward of rear axle. Negative values = backward of rear axle.)
  • Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Y (Mounting position of GNSS receiver antenna relative to vehicle coordinate system. Axis definitions according to ISO 8855. Origin at center of (first) rear axle. Positive values = left of origin. Negative values = right of origin. Left/Right is as seen from driver perspective, i.e. by a person looking forward.)
  • Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Z (Mounting position of GNSS receiver on Z-axis. Axis definitions according to ISO 8855. Origin at center of (first) rear axle. Positive values = above center of rear axle. Negative values = below center of rear axle.)

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 - true
Full qualified VSS Path: Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Y
Description: Mounting position of GNSS receiver antenna relative to vehicle coordinate system. Axis definitions according to ISO 8855. Origin at center of (first) rear axle. Positive values = left of origin. Negative values = right of origin. Left/Right is as seen from driver perspective, i.e. by a person looking forward.
flowchart LR Vehicle-->CurrentLocation CurrentLocation-->GNSSReceiver GNSSReceiver-->MountingPosition MountingPosition-->Y

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Y
[get]  OK
Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Y: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.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.CurrentLocation.GNSSReceiver.MountingPosition.Y

Data Type & Unit
Path Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Y VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance

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.CurrentLocation.GNSSReceiver.MountingPosition.Y is an Attribute.

The vehicle signal Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Y is a Signal.

UUID

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

The UUID for Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Y is 16745ae827c0527ea2c48c20f0c146f1

Feedback

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

About VSS

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

Supported datatypes

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

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

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

2.2 - X
Full qualified VSS Path: Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.X
Description: Mounting position of GNSS receiver antenna relative to vehicle coordinate system. Axis definitions according to ISO 8855. Origin at center of (first) rear axle. Positive values = forward of rear axle. Negative values = backward of rear axle.
flowchart LR Vehicle-->CurrentLocation CurrentLocation-->GNSSReceiver GNSSReceiver-->MountingPosition MountingPosition-->X

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.X
[get]  OK
Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.X: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.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.CurrentLocation.GNSSReceiver.MountingPosition.X

Data Type & Unit
Path Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.X VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance

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.CurrentLocation.GNSSReceiver.MountingPosition.X is an Attribute.

The vehicle signal Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.X is a Signal.

UUID

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

The UUID for Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.X is f23d40f3556b5676a0d1e3def037197f

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.3 - Z
Full qualified VSS Path: Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Z
Description: Mounting position of GNSS receiver on Z-axis. Axis definitions according to ISO 8855. Origin at center of (first) rear axle. Positive values = above center of rear axle. Negative values = below center of rear axle.
flowchart LR Vehicle-->CurrentLocation CurrentLocation-->GNSSReceiver GNSSReceiver-->MountingPosition MountingPosition-->Z

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Z
[get]  OK
Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Z: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.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.CurrentLocation.GNSSReceiver.MountingPosition.Z

Data Type & Unit
Path Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Z VSS: Addressing nodes
Data type int16 VSS: Datatypes
Unit mm VSS: Units
Label millimeter
Description Distance measured in millimeters VSS: Sensors & Actuators
Domain distance

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.CurrentLocation.GNSSReceiver.MountingPosition.Z is an Attribute.

The vehicle signal Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Z is a Signal.

UUID

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

The UUID for Vehicle.CurrentLocation.GNSSReceiver.MountingPosition.Z is a4d04e86518e5c5ab60e5e4face35756

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.