This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Occupant
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos3.Occupant |
Description: |
Occupant data. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos3
Pos3-->Occupant
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.Seat.Row1.Pos3.Occupant
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant
is 4e68d3feef825f6f99c44cec9f7c1217
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 - Identifier
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier |
Description: |
Identifier attributes based on OAuth 2.0. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos3
Pos3-->Occupant
Occupant-->Identifier
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.Seat.Row1.Pos3.Occupant.Identifier
is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier
is f59d9531974256cab958e5e31588565d
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.1 - Issuer
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer |
Description: |
Unique Issuer for the authentication of the occupant. E.g. https://accounts.funcorp.com. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos3
Pos3-->Occupant
Occupant-->Identifier
Identifier-->Issuer
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer
[get] OK
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer 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.Seat.Row1.Pos3.Occupant.Identifier.Issuer
is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Issuer
is 0d29fa2a1b97563c8e1ba31b8571f328
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.
1.2 - Subject
|
|
Full qualified VSS Path: |
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject |
Description: |
Subject for the authentication of the occupant. E.g. UserID 7331677. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Seat
Seat-->Row1
Row1-->Pos3
Pos3-->Occupant
Occupant-->Identifier
Identifier-->Subject
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject
[get] OK
Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject 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.Seat.Row1.Pos3.Occupant.Identifier.Subject
is a Sensor.
The vehicle signal Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject
is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Seat.Row1.Pos3.Occupant.Identifier.Subject
is a7306a24de2155f2a1de070bc8f1bd60
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.