This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
PassengerSide
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide |
| Description: |
All doors, including windows and switches. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
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.Door.Row1.PassengerSide is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide is 9ea0425fb2085ded9a393d4e999ae90a
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 - IsChildLockActive
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.IsChildLockActive |
| Description: |
Is door child lock active. True = Door cannot be opened from inside. False = Door can be opened from inside. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->IsChildLockActive
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.IsChildLockActive
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.IsChildLockActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.IsChildLockActive false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.IsChildLockActive is a Sensor.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.IsChildLockActive is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.IsChildLockActive is 74a842786a73553ba3491975c2077ac7
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 - IsLocked
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.IsLocked |
| Description: |
Is item locked or unlocked. True = Locked. False = Unlocked. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->IsLocked
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.IsLocked
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.IsLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.IsLocked false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.IsLocked is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.IsLocked is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.IsLocked is 48d4388ec67b519ab500ee424ce4b6cb
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 - IsOpen
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.IsOpen |
| Description: |
Is item open or closed? True = Fully or partially open. False = Fully closed. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->IsOpen
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.IsOpen
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.IsOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.IsOpen false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.IsOpen is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.IsOpen is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.IsOpen is 80aca3884840557db10f1314a27a5eeb
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.
4 - Position
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Position |
| Description: |
Item position. 0 = Start position 100 = End position. |
| Comment: |
Relationship between Open/Close and Start/End position is item dependent. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Position
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Position
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Position 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
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Position is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Position is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Position is 7002316cdf9852afb027abc03309b15d
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.
5 - Shade
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Shade |
| Description: |
Side window shade. Open = Retracted, Closed = Deployed. Start position for Shade is Open/Retracted. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Shade
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.Door.Row1.PassengerSide.Shade is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Shade is dfe64259f26a54bda64b9aa24362c7eb
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.
5.1 - IsOpen
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Shade.IsOpen |
| Description: |
Is item open or closed? True = Fully or partially open. False = Fully closed. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Shade
Shade-->IsOpen
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Shade.IsOpen
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Shade.IsOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Shade.IsOpen false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Shade.IsOpen is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Shade.IsOpen is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Shade.IsOpen is 46bec5f9c4ef594fb41836d413e79400
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.
5.2 - Position
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Position |
| Description: |
Item position. 0 = Start position 100 = End position. |
| Comment: |
Relationship between Open/Close and Start/End position is item dependent. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Shade
Shade-->Position
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Position
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Position 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
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Position is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Position is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Position is 8f583d09021e51319aa6bdd0e29aefc8
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.
5.3 - Switch
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Switch |
| Description: |
Switch controlling sliding action such as window, sunroof, or blind. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Shade
Shade-->Switch
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Switch
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Switch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Switch 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.Door.Row1.PassengerSide.Shade.Switch is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Switch is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Shade.Switch is c700d6a13a16522ead84b81314fd452b
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.
6 - Switch
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Switch |
| Description: |
Switch controlling sliding action such as window, sunroof, or blind. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Switch
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Switch
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Switch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Switch 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.Door.Row1.PassengerSide.Switch is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Switch is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Switch is c1244ebb7ef35c2a9e0f6ebf47710536
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.
7 - Window
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Window |
| Description: |
Door window status. Start position for Window is Closed. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Window
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.Door.Row1.PassengerSide.Window is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Window is c588ac43d3945dc0a45994c4d298d9b0
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.
7.1 - IsOpen
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Window.IsOpen |
| Description: |
Is item open or closed? True = Fully or partially open. False = Fully closed. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Window
Window-->IsOpen
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Window.IsOpen
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Window.IsOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Window.IsOpen false
[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 boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Window.IsOpen is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Window.IsOpen is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Window.IsOpen is 120e3b950fd657fabd90069e6e01f44e
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.
7.2 - Position
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Window.Position |
| Description: |
Item position. 0 = Start position 100 = End position. |
| Comment: |
Relationship between Open/Close and Start/End position is item dependent. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Window
Window-->Position
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Window.Position
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Window.Position: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Window.Position 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
Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Window.Position is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Window.Position is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Window.Position is ec293d2eb9e052e88d01927c811711ef
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.
7.3 - Switch
|
|
| Full qualified VSS Path: |
Vehicle.Cabin.Door.Row1.PassengerSide.Window.Switch |
| Description: |
Switch controlling sliding action such as window, sunroof, or blind. |
Navigation
flowchart LR
Vehicle-->Cabin
Cabin-->Door
Door-->Row1
Row1-->PassengerSide
PassengerSide-->Window
Window-->Switch
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Cabin.Door.Row1.PassengerSide.Window.Switch
[get] OK
Vehicle.Cabin.Door.Row1.PassengerSide.Window.Switch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Cabin.Door.Row1.PassengerSide.Window.Switch 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.Door.Row1.PassengerSide.Window.Switch is an Actuator.
The vehicle signal Vehicle.Cabin.Door.Row1.PassengerSide.Window.Switch is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Cabin.Door.Row1.PassengerSide.Window.Switch is 36efa23a161a5fe1b65e36f5656738fb
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.