This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
SmartphoneProjection
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Infotainment.SmartphoneProjection |
| Description: |
All smartphone projection actions. |
| Comment: |
Smartphone projection exposes or controls specific applications on the Smartphone on the vehicle infotainment system. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Infotainment
Infotainment-->SmartphoneProjection
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Cabin.Infotainment.SmartphoneProjection is a Branch.
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:
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 - Active
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Infotainment.SmartphoneProjection.Active |
| Description: |
Projection activation info. |
| Comment: |
NONE indicates that projection is not supported. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Infotainment
Infotainment-->SmartphoneProjection
SmartphoneProjection-->Active
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.SmartphoneProjection.Active
[get] OK
Vehicle.Cabin.Infotainment.SmartphoneProjection.Active: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.SmartphoneProjection.Active Foo
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The string datatype is a character string.
The vehicle signal Vehicle.Cabin.Infotainment.SmartphoneProjection.Active is an Actuator.
The vehicle signal Vehicle.Cabin.Infotainment.SmartphoneProjection.Active is a Signal.
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:
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 - Source
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Infotainment.SmartphoneProjection.Source |
| Description: |
Connectivity source selected for projection. |
| Comment: |
Smartphone projection exposes or controls specific applications on the Smartphone on the vehicle infotainment system. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Infotainment
Infotainment-->SmartphoneProjection
SmartphoneProjection-->Source
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.SmartphoneProjection.Source
[get] OK
Vehicle.Cabin.Infotainment.SmartphoneProjection.Source: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.SmartphoneProjection.Source Foo
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The string datatype is a character string.
The vehicle signal Vehicle.Cabin.Infotainment.SmartphoneProjection.Source is an Actuator.
The vehicle signal Vehicle.Cabin.Infotainment.SmartphoneProjection.Source is a Signal.
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:
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 - SupportedMode
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Infotainment.SmartphoneProjection.SupportedMode |
| Description: |
Supportable list for projection. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Infotainment
Infotainment-->SmartphoneProjection
SmartphoneProjection-->SupportedMode
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.SmartphoneProjection.SupportedMode
[get] OK
Vehicle.Cabin.Infotainment.SmartphoneProjection.SupportedMode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Infotainment.SmartphoneProjection.SupportedMode 0
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
The vehicle signal Vehicle.Cabin.Infotainment.SmartphoneProjection.SupportedMode is an Attribute.
The vehicle signal Vehicle.Cabin.Infotainment.SmartphoneProjection.SupportedMode is a Signal.
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:
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.