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

Return to the regular view of this page.

DestinationSet
Full qualified VSS Path: Vehicle.Cabin.Infotainment.Navigation.DestinationSet
Description: A navigation has been selected.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->Navigation Navigation-->DestinationSet

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.Cabin.Infotainment.Navigation.DestinationSet

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.Navigation.DestinationSet is a Branch.

UUID

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

The UUID for Vehicle.Cabin.Infotainment.Navigation.DestinationSet is f51ce253dc5b58168ecca99297139455

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 - Latitude
Full qualified VSS Path: Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude
Description: Latitude of destination in WGS 84 geodetic coordinates.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->Navigation Navigation-->DestinationSet DestinationSet-->Latitude

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude
[get]  OK
Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude 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.Cabin.Infotainment.Navigation.DestinationSet.Latitude

Data Type & Unit
Path Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude VSS: Addressing nodes
Data type double 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 double datatype is a double precision floating point number which technically allows values between -1.7e ^ -300 and 1.7e ^ 300

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Latitude is 3e33f3252934565d86de5409c761262b

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 - Longitude
Full qualified VSS Path: Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude
Description: Longitude of destination in WGS 84 geodetic coordinates.
flowchart LR Vehicle-->Cabin Cabin-->Infotainment Infotainment-->Navigation Navigation-->DestinationSet DestinationSet-->Longitude

Eclipse Leda: Usage Example

In Eclipse Kuksa.VAL Databroker CLI:

$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude
[get]  OK
Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude 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.Cabin.Infotainment.Navigation.DestinationSet.Longitude

Data Type & Unit
Path Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude VSS: Addressing nodes
Data type double 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 double datatype is a double precision floating point number which technically allows values between -1.7e ^ -300 and 1.7e ^ 300

Signal Information

The vehicle signal Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude is an Actuator.

The vehicle signal Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude is a Signal.

UUID

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

The UUID for Vehicle.Cabin.Infotainment.Navigation.DestinationSet.Longitude is e9bd511146ca51639c8d42c0702e22ee

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.