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.