This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Body
|
|
| Full qualified VSS Path: |
Vehicle.Body |
| Description: |
All body components. |
Navigation
flowchart LR
Vehicle-->Body
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.Body |
The vehicle signal Vehicle.Body is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body is bd2854e6a9165c5698ce8dd9f0438ecc
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 - PowerOptimizeLevel
|
|
| Full qualified VSS Path: |
Vehicle.Body.PowerOptimizeLevel |
| Description: |
Power optimization level for this branch/subsystem. A higher number indicates more aggressive power optimization. Level 0 indicates that all functionality is enabled, no power optimization enabled. Level 10 indicates most aggressive power optimization mode, only essential functionality enabled. |
Navigation
flowchart LR
Vehicle-->Body
Body-->PowerOptimizeLevel
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.PowerOptimizeLevel
[get] OK
Vehicle.Body.PowerOptimizeLevel: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.PowerOptimizeLevel 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.Body.PowerOptimizeLevel is an Actuator.
The vehicle signal Vehicle.Body.PowerOptimizeLevel is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.PowerOptimizeLevel is 2fe44a1c3bb155aca782b017efeb6175
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 - RearMainSpoilerPosition
|
|
| Full qualified VSS Path: |
Vehicle.Body.RearMainSpoilerPosition |
| Description: |
Rear spoiler position, 0% = Spoiler fully stowed. 100% = Spoiler fully exposed. |
Navigation
flowchart LR
Vehicle-->Body
Body-->RearMainSpoilerPosition
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.RearMainSpoilerPosition
[get] OK
Vehicle.Body.RearMainSpoilerPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.RearMainSpoilerPosition 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Body.RearMainSpoilerPosition is an Actuator.
The vehicle signal Vehicle.Body.RearMainSpoilerPosition is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.RearMainSpoilerPosition is 6209a82390585b869cc3d00d069eade2
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 - Mirrors
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors |
| Description: |
All mirrors. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Mirrors is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors is a4ea618914885a239ef5fa62c671a800
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.
3.1 - Right
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Right |
| Description: |
All mirrors. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Right
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Mirrors.Right is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Right is 64291c99f7e752c2b035262c17dc85dd
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.
3.1.1 - IsHeatingOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Right.IsHeatingOn |
| Description: |
Mirror Heater on or off. True = Heater On. False = Heater Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Right
Right-->IsHeatingOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Mirrors.Right.IsHeatingOn
[get] OK
Vehicle.Body.Mirrors.Right.IsHeatingOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Mirrors.Right.IsHeatingOn 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.Body.Mirrors.Right.IsHeatingOn is an Actuator.
The vehicle signal Vehicle.Body.Mirrors.Right.IsHeatingOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Right.IsHeatingOn is 9a57455f48ea5fdbb7a998905dda318c
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.1.2 - Pan
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Right.Pan |
| Description: |
Mirror pan as a percent. 0 = Center Position. 100 = Fully Left Position. -100 = Fully Right Position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Right
Right-->Pan
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Mirrors.Right.Pan
[get] OK
Vehicle.Body.Mirrors.Right.Pan: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Mirrors.Right.Pan 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Body.Mirrors.Right.Pan is an Actuator.
The vehicle signal Vehicle.Body.Mirrors.Right.Pan is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Right.Pan is 26088f96804d5d7e811ba50bfb1113eb
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.1.3 - Tilt
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Right.Tilt |
| Description: |
Mirror tilt as a percent. 0 = Center Position. 100 = Fully Upward Position. -100 = Fully Downward Position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Right
Right-->Tilt
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Mirrors.Right.Tilt
[get] OK
Vehicle.Body.Mirrors.Right.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Mirrors.Right.Tilt 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Body.Mirrors.Right.Tilt is an Actuator.
The vehicle signal Vehicle.Body.Mirrors.Right.Tilt is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Right.Tilt is 9a28a6ec824c57408881b916a1a0e32b
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.2 - Left
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Left |
| Description: |
All mirrors. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Left
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Mirrors.Left is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Left is 22609e45a09d58fc85cb77959a686abc
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.
3.2.1 - IsHeatingOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Left.IsHeatingOn |
| Description: |
Mirror Heater on or off. True = Heater On. False = Heater Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Left
Left-->IsHeatingOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Mirrors.Left.IsHeatingOn
[get] OK
Vehicle.Body.Mirrors.Left.IsHeatingOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Mirrors.Left.IsHeatingOn 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.Body.Mirrors.Left.IsHeatingOn is an Actuator.
The vehicle signal Vehicle.Body.Mirrors.Left.IsHeatingOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Left.IsHeatingOn is b8591c0592d8525e91e1a04495b6995d
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.2.2 - Pan
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Left.Pan |
| Description: |
Mirror pan as a percent. 0 = Center Position. 100 = Fully Left Position. -100 = Fully Right Position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Left
Left-->Pan
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Mirrors.Left.Pan
[get] OK
Vehicle.Body.Mirrors.Left.Pan: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Mirrors.Left.Pan 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Body.Mirrors.Left.Pan is an Actuator.
The vehicle signal Vehicle.Body.Mirrors.Left.Pan is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Left.Pan is 9dae4bc33a28531199fce500e0562f82
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.2.3 - Tilt
|
|
| Full qualified VSS Path: |
Vehicle.Body.Mirrors.Left.Tilt |
| Description: |
Mirror tilt as a percent. 0 = Center Position. 100 = Fully Upward Position. -100 = Fully Downward Position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Mirrors
Mirrors-->Left
Left-->Tilt
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Mirrors.Left.Tilt
[get] OK
Vehicle.Body.Mirrors.Left.Tilt: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Mirrors.Left.Tilt 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 int8 datatype is a signed 8-bit integer which technically allows values between -128 and 127 (inclusive).
The vehicle signal Vehicle.Body.Mirrors.Left.Tilt is an Actuator.
The vehicle signal Vehicle.Body.Mirrors.Left.Tilt is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Mirrors.Left.Tilt is 698fee82cc115f3cba54825a298b46ab
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 - Lights
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights |
| Description: |
Exterior lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights is 399d1ec14d6f55bb825e078a801bde55
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.
4.1 - Backup
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Backup |
| Description: |
Backup lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Backup
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Backup is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Backup is 4fe2cb68fc77506686eced7225aeff9a
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.
4.1.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Backup.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Backup
Backup-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Backup.IsDefect
[get] OK
Vehicle.Body.Lights.Backup.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Backup.IsDefect 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.Body.Lights.Backup.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Backup.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Backup.IsDefect is b907c4ac4ee459faa987c64a6da424c3
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.1.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Backup.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Backup
Backup-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Backup.IsOn
[get] OK
Vehicle.Body.Lights.Backup.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Backup.IsOn 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.Body.Lights.Backup.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.Backup.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Backup.IsOn is ef23a3fa6106564195a66e21d8cf69b4
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.2 - Brake
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Brake |
| Description: |
Brake lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Brake
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Brake is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Brake is 30eabe704102501cb299d03696fad92a
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.
4.2.1 - IsActive
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Brake.IsActive |
| Description: |
Indicates if break-light is active. INACTIVE means lights are off. ACTIVE means lights are on. ADAPTIVE means that break-light is indicating emergency-breaking. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Brake
Brake-->IsActive
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Brake.IsActive
[get] OK
Vehicle.Body.Lights.Brake.IsActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Brake.IsActive 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.Body.Lights.Brake.IsActive is an Actuator.
The vehicle signal Vehicle.Body.Lights.Brake.IsActive is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Brake.IsActive is 65eb84d61ea95313985054f626b85b59
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.2.2 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Brake.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Brake
Brake-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Brake.IsDefect
[get] OK
Vehicle.Body.Lights.Brake.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Brake.IsDefect 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.Body.Lights.Brake.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Brake.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Brake.IsDefect is 1db542c5ba715e09b948527418966728
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.3 - DirectionIndicator
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.DirectionIndicator |
| Description: |
Indicator lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->DirectionIndicator
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.DirectionIndicator is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.DirectionIndicator is 0566cb97d05c554eb88a07142f2475ac
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.
4.3.1 - Left
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.DirectionIndicator.Left |
| Description: |
Indicator lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->DirectionIndicator
DirectionIndicator-->Left
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.DirectionIndicator.Left is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.DirectionIndicator.Left is 446dea42b8e95d87b45e5e51c881bf98
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.
4.3.1.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.DirectionIndicator.Left.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->DirectionIndicator
DirectionIndicator-->Left
Left-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.DirectionIndicator.Left.IsDefect
[get] OK
Vehicle.Body.Lights.DirectionIndicator.Left.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.DirectionIndicator.Left.IsDefect 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.Body.Lights.DirectionIndicator.Left.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.DirectionIndicator.Left.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.DirectionIndicator.Left.IsDefect is 32a092936fb65165ba1dd8dfa38bf77d
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.3.1.2 - IsSignaling
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.DirectionIndicator.Left.IsSignaling |
| Description: |
Indicates if light is signaling or off. True = signaling. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->DirectionIndicator
DirectionIndicator-->Left
Left-->IsSignaling
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.DirectionIndicator.Left.IsSignaling
[get] OK
Vehicle.Body.Lights.DirectionIndicator.Left.IsSignaling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.DirectionIndicator.Left.IsSignaling 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.Body.Lights.DirectionIndicator.Left.IsSignaling is an Actuator.
The vehicle signal Vehicle.Body.Lights.DirectionIndicator.Left.IsSignaling is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.DirectionIndicator.Left.IsSignaling is 33ac6ec5e4d9550aac6ae0ce97dae259
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.3.2 - Right
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.DirectionIndicator.Right |
| Description: |
Indicator lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->DirectionIndicator
DirectionIndicator-->Right
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.DirectionIndicator.Right is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.DirectionIndicator.Right is 9922f6b417e95f1c945ef9f414bcdf78
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.
4.3.2.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.DirectionIndicator.Right.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->DirectionIndicator
DirectionIndicator-->Right
Right-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.DirectionIndicator.Right.IsDefect
[get] OK
Vehicle.Body.Lights.DirectionIndicator.Right.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.DirectionIndicator.Right.IsDefect 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.Body.Lights.DirectionIndicator.Right.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.DirectionIndicator.Right.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.DirectionIndicator.Right.IsDefect is db70c2d885725583a7ed95b215a8ec6c
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.3.2.2 - IsSignaling
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.DirectionIndicator.Right.IsSignaling |
| Description: |
Indicates if light is signaling or off. True = signaling. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->DirectionIndicator
DirectionIndicator-->Right
Right-->IsSignaling
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.DirectionIndicator.Right.IsSignaling
[get] OK
Vehicle.Body.Lights.DirectionIndicator.Right.IsSignaling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.DirectionIndicator.Right.IsSignaling 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.Body.Lights.DirectionIndicator.Right.IsSignaling is an Actuator.
The vehicle signal Vehicle.Body.Lights.DirectionIndicator.Right.IsSignaling is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.DirectionIndicator.Right.IsSignaling is 9b0a1dab153f5dcda8df2116c3b6d487
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.4 - Fog
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Fog |
| Description: |
Fog lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Fog
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Fog is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Fog is 1e90cf42bb825217b283c7285a606953
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.
4.4.1 - Front
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Fog.Front |
| Description: |
Fog lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Fog
Fog-->Front
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Fog.Front is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Fog.Front is 230cc65abaaf500c9085c29d48107552
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.
4.4.1.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Fog.Front.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Fog
Fog-->Front
Front-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Fog.Front.IsDefect
[get] OK
Vehicle.Body.Lights.Fog.Front.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Fog.Front.IsDefect 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.Body.Lights.Fog.Front.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Fog.Front.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Fog.Front.IsDefect is f9238f15d2615a22802ce9ec9f1d72e9
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.4.1.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Fog.Front.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Fog
Fog-->Front
Front-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Fog.Front.IsOn
[get] OK
Vehicle.Body.Lights.Fog.Front.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Fog.Front.IsOn 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.Body.Lights.Fog.Front.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.Fog.Front.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Fog.Front.IsOn is 0ec10846d20a5d1b9b8a286303ecb844
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.4.2 - Rear
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Fog.Rear |
| Description: |
Fog lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Fog
Fog-->Rear
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Fog.Rear is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Fog.Rear is 38359f258135516cb49c0fa1f093d478
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.
4.4.2.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Fog.Rear.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Fog
Fog-->Rear
Rear-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Fog.Rear.IsDefect
[get] OK
Vehicle.Body.Lights.Fog.Rear.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Fog.Rear.IsDefect 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.Body.Lights.Fog.Rear.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Fog.Rear.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Fog.Rear.IsDefect is 1d44e594ffa35d73a6f620f479eeef4c
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.4.2.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Fog.Rear.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Fog
Fog-->Rear
Rear-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Fog.Rear.IsOn
[get] OK
Vehicle.Body.Lights.Fog.Rear.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Fog.Rear.IsOn 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.Body.Lights.Fog.Rear.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.Fog.Rear.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Fog.Rear.IsOn is 1fe08a2f687c5c2880adef26cc7de746
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.5 - Hazard
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Hazard |
| Description: |
Hazard lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Hazard
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Hazard is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Hazard is 803498c3be6253dfb074c0e0294be758
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.
4.5.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Hazard.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Hazard
Hazard-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Hazard.IsDefect
[get] OK
Vehicle.Body.Lights.Hazard.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Hazard.IsDefect 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.Body.Lights.Hazard.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Hazard.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Hazard.IsDefect is 25cd3475beb6543a8538974b67544c43
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.5.2 - IsSignaling
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Hazard.IsSignaling |
| Description: |
Indicates if light is signaling or off. True = signaling. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Hazard
Hazard-->IsSignaling
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Hazard.IsSignaling
[get] OK
Vehicle.Body.Lights.Hazard.IsSignaling: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Hazard.IsSignaling 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.Body.Lights.Hazard.IsSignaling is an Actuator.
The vehicle signal Vehicle.Body.Lights.Hazard.IsSignaling is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Hazard.IsSignaling is c53950205aa15dffa304390dcb761cc3
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.6 - LicensePlate
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.LicensePlate |
| Description: |
License plate lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->LicensePlate
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.LicensePlate is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.LicensePlate is 7bb12e42a8c45c198f83bf41b19131fa
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.
4.6.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.LicensePlate.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->LicensePlate
LicensePlate-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.LicensePlate.IsDefect
[get] OK
Vehicle.Body.Lights.LicensePlate.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.LicensePlate.IsDefect 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.Body.Lights.LicensePlate.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.LicensePlate.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.LicensePlate.IsDefect is 4de6594de7815cec97e5b851d70e239b
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.6.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.LicensePlate.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->LicensePlate
LicensePlate-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.LicensePlate.IsOn
[get] OK
Vehicle.Body.Lights.LicensePlate.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.LicensePlate.IsOn 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.Body.Lights.LicensePlate.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.LicensePlate.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.LicensePlate.IsOn is afeace5d76ed53f989ae4251090ba069
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.7 - Parking
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Parking |
| Description: |
Parking lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Parking
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Parking is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Parking is dfb819be5cec5be09b9fb743829301c3
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.
4.7.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Parking.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Parking
Parking-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Parking.IsDefect
[get] OK
Vehicle.Body.Lights.Parking.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Parking.IsDefect 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.Body.Lights.Parking.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Parking.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Parking.IsDefect is 56761305eae559c7931f6ff5fee0dfa8
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.7.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Parking.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Parking
Parking-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Parking.IsOn
[get] OK
Vehicle.Body.Lights.Parking.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Parking.IsOn 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.Body.Lights.Parking.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.Parking.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Parking.IsOn is 6ba0825427335408ad7d0f148d6250ea
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.8 - Running
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Running |
| Description: |
Running lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Running
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Running is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Running is 38868a9f1bda573595501302c1f0a1db
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.
4.8.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Running.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Running
Running-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Running.IsDefect
[get] OK
Vehicle.Body.Lights.Running.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Running.IsDefect 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.Body.Lights.Running.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Running.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Running.IsDefect is 7cda127e6d45547681757e789c0b7a87
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.8.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Running.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Running
Running-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Running.IsOn
[get] OK
Vehicle.Body.Lights.Running.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Running.IsOn 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.Body.Lights.Running.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.Running.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Running.IsOn is 1c4e44f1e0275965b466ac674a5b8cac
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.9 - Beam
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Beam |
| Description: |
Beam lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Beam
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Beam is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Beam is 6685308a9d955ecdad92a7cc68666a12
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.
4.9.1 - High
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Beam.High |
| Description: |
Beam lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Beam
Beam-->High
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Beam.High is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Beam.High is 306b51d2e1ec572fa80172aad6727da0
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.
4.9.1.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Beam.High.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Beam
Beam-->High
High-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Beam.High.IsDefect
[get] OK
Vehicle.Body.Lights.Beam.High.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Beam.High.IsDefect 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.Body.Lights.Beam.High.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Beam.High.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Beam.High.IsDefect is 83561d8c9a025cfdad6c4b325829fa00
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.9.1.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Beam.High.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Beam
Beam-->High
High-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Beam.High.IsOn
[get] OK
Vehicle.Body.Lights.Beam.High.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Beam.High.IsOn 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.Body.Lights.Beam.High.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.Beam.High.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Beam.High.IsOn is 24d1346519b05697b872c06556a09fb4
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.9.2 - Low
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Beam.Low |
| Description: |
Beam lights. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Beam
Beam-->Low
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Lights.Beam.Low is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Beam.Low is f6f21ea5b263545297f4411b2e15037f
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.
4.9.2.1 - IsDefect
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Beam.Low.IsDefect |
| Description: |
Indicates if light is defect. True = Light is defect. False = Light has no defect. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Beam
Beam-->Low
Low-->IsDefect
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Beam.Low.IsDefect
[get] OK
Vehicle.Body.Lights.Beam.Low.IsDefect: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Beam.Low.IsDefect 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.Body.Lights.Beam.Low.IsDefect is a Sensor.
The vehicle signal Vehicle.Body.Lights.Beam.Low.IsDefect is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Beam.Low.IsDefect is 3a135f1267ea5b2a80aa9a17fc8072db
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.9.2.2 - IsOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.Beam.Low.IsOn |
| Description: |
Indicates if light is on or off. True = On. False = Off. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->Beam
Beam-->Low
Low-->IsOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.Beam.Low.IsOn
[get] OK
Vehicle.Body.Lights.Beam.Low.IsOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.Beam.Low.IsOn 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.Body.Lights.Beam.Low.IsOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.Beam.Low.IsOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.Beam.Low.IsOn is 8b4d4855b0c95963a25dc564c9758610
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.10 - IsHighBeamSwitchOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.IsHighBeamSwitchOn |
| Description: |
Status of the high beam switch. True = high beam enabled. False = high beam not enabled. |
| Comment: |
This signal indicates the status of the switch and does not indicate if low or high beam actually are on. That typically depends on vehicle logic and other signals like Lights.LightSwitch and Vehicle.LowVoltageSystemState. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->IsHighBeamSwitchOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.IsHighBeamSwitchOn
[get] OK
Vehicle.Body.Lights.IsHighBeamSwitchOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.IsHighBeamSwitchOn 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.Body.Lights.IsHighBeamSwitchOn is an Actuator.
The vehicle signal Vehicle.Body.Lights.IsHighBeamSwitchOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.IsHighBeamSwitchOn is ac7db3cd30f55650bc6939df504f1a79
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.11 - LightSwitch
|
|
| Full qualified VSS Path: |
Vehicle.Body.Lights.LightSwitch |
| Description: |
Status of the vehicle main light switch. |
| Comment: |
A vehicle typically does not support all alternatives. Which lights that actually are lit may vary according to vehicle configuration and local legislation. OFF is typically indicated by 0. POSITION is typically indicated by ISO 7000 symbol 0456. DAYTIME_RUNNING_LIGHTS (DRL) can be indicated by ISO 7000 symbol 2611. AUTO indicates that vehicle automatically selects suitable lights. BEAM is typically indicated by ISO 7000 symbol 0083. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Lights
Lights-->LightSwitch
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Lights.LightSwitch
[get] OK
Vehicle.Body.Lights.LightSwitch: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Lights.LightSwitch 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.Body.Lights.LightSwitch is an Actuator.
The vehicle signal Vehicle.Body.Lights.LightSwitch is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Lights.LightSwitch is 2feb14a3558256339442413783969f4f
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 - Horn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Horn |
| Description: |
Horn signals. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Horn
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Horn is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Horn is 09c76633887f52268b960740eb969c89
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 - IsActive
|
|
| Full qualified VSS Path: |
Vehicle.Body.Horn.IsActive |
| Description: |
Horn active or inactive. True = Active. False = Inactive. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Horn
Horn-->IsActive
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Horn.IsActive
[get] OK
Vehicle.Body.Horn.IsActive: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Horn.IsActive 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.Body.Horn.IsActive is an Actuator.
The vehicle signal Vehicle.Body.Horn.IsActive is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Horn.IsActive is ba20deed9314525bb9d552a2b787fb20
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 - Raindetection
|
|
| Full qualified VSS Path: |
Vehicle.Body.Raindetection |
| Description: |
Rainsensor signals. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Raindetection
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Raindetection is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Raindetection is f16759f3dcfb5be4832e962da29ebd6c
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.
6.1 - Intensity
|
|
| Full qualified VSS Path: |
Vehicle.Body.Raindetection.Intensity |
| Description: |
Rain intensity. 0 = Dry, No Rain. 100 = Covered. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Raindetection
Raindetection-->Intensity
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Raindetection.Intensity
[get] OK
Vehicle.Body.Raindetection.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Raindetection.Intensity 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.Body.Raindetection.Intensity is a Sensor.
The vehicle signal Vehicle.Body.Raindetection.Intensity is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Raindetection.Intensity is 1ee0a2f22e8257d299425a4ff2652555
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 - Windshield
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield |
| Description: |
Windshield signals. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield is 73efba535dcb5032b9edc43406b050b8
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 - Front
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front |
| Description: |
Windshield signals. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Front is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front is 8f0c61e4e4f557d98729210fc3c74f72
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.1 - IsHeatingOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.IsHeatingOn |
| Description: |
Windshield heater status. False - off, True - on. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->IsHeatingOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.IsHeatingOn
[get] OK
Vehicle.Body.Windshield.Front.IsHeatingOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.IsHeatingOn 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.Body.Windshield.Front.IsHeatingOn is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Front.IsHeatingOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.IsHeatingOn is 26e6a3b7e9bb58bebba29258faa6e300
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.1.2 - WasherFluid
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.WasherFluid |
| Description: |
Windshield washer fluid signals |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->WasherFluid
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Front.WasherFluid is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.WasherFluid is 2de24016515353289953de5ea81efd3c
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.2.1 - IsLevelLow
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.WasherFluid.IsLevelLow |
| Description: |
Low level indication for washer fluid. True = Level Low. False = Level OK. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->WasherFluid
WasherFluid-->IsLevelLow
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.WasherFluid.IsLevelLow
[get] OK
Vehicle.Body.Windshield.Front.WasherFluid.IsLevelLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.WasherFluid.IsLevelLow 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.Body.Windshield.Front.WasherFluid.IsLevelLow is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.WasherFluid.IsLevelLow is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.WasherFluid.IsLevelLow is 8ca54695ad115f9bb6f56d7c450781a7
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.1.2.2 - Level
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.WasherFluid.Level |
| Description: |
Washer fluid level as a percent. 0 = Empty. 100 = Full. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->WasherFluid
WasherFluid-->Level
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.WasherFluid.Level
[get] OK
Vehicle.Body.Windshield.Front.WasherFluid.Level: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.WasherFluid.Level 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.Body.Windshield.Front.WasherFluid.Level is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.WasherFluid.Level is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.WasherFluid.Level is a36dfb91414f5792bd01d193dceff1f4
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.1.3 - Wiping
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping |
| Description: |
Windshield wiper signals. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping is 2cffeccdc19a587cbe2264f426c6881a
Children
This vehicle signal is a branch or structure and thus has sub-pages:
- Vehicle.Body.Windshield.Front.Wiping.Intensity (Relative intensity/sensitivity for interval and rain sensor mode as requested by user/driver. Has no significance if Windshield.Wiping.Mode is OFF/SLOW/MEDIUM/FAST 0 - wipers inactive. 1 - minimum intensity (lowest frequency/sensitivity, longest interval). 2/3/4/… - higher intensity (higher frequency/sensitivity, shorter interval). Maximum value supported is vehicle specific.)
- Vehicle.Body.Windshield.Front.Wiping.IsWipersWorn (Wiper wear status. True = Worn, Replacement recommended or required. False = Not Worn.)
- Vehicle.Body.Windshield.Front.Wiping.Mode (Wiper mode requested by user/driver. INTERVAL indicates intermittent wiping, with fixed time interval between each wipe. RAIN_SENSOR indicates intermittent wiping based on rain intensity.)
- Vehicle.Body.Windshield.Front.Wiping.System (Signals to control behavior of wipers in detail. By default VSS expects only one instance.)
- Vehicle.Body.Windshield.Front.Wiping.WiperWear (Wiper wear as percent. 0 = No Wear. 100 = Worn. Replacement required. Method for calculating or estimating wiper wear is vehicle specific. For windshields with multiple wipers the wear reported shall correspond to the most worn wiper.)
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.3.1 - Intensity
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.Intensity |
| Description: |
Relative intensity/sensitivity for interval and rain sensor mode as requested by user/driver. Has no significance if Windshield.Wiping.Mode is OFF/SLOW/MEDIUM/FAST 0 - wipers inactive. 1 - minimum intensity (lowest frequency/sensitivity, longest interval). 2/3/4/… - higher intensity (higher frequency/sensitivity, shorter interval). Maximum value supported is vehicle specific. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->Intensity
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.Intensity
[get] OK
Vehicle.Body.Windshield.Front.Wiping.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.Intensity 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.Body.Windshield.Front.Wiping.Intensity is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.Intensity is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.Intensity is 7cdd36d1cc8f5f9a9f079f663190b588
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.1.3.2 - IsWipersWorn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.IsWipersWorn |
| Description: |
Wiper wear status. True = Worn, Replacement recommended or required. False = Not Worn. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->IsWipersWorn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.IsWipersWorn
[get] OK
Vehicle.Body.Windshield.Front.Wiping.IsWipersWorn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.IsWipersWorn 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.Body.Windshield.Front.Wiping.IsWipersWorn is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.IsWipersWorn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.IsWipersWorn is b04ccc7daedb559c9bcdda6b00332be5
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.1.3.3 - Mode
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.Mode |
| Description: |
Wiper mode requested by user/driver. INTERVAL indicates intermittent wiping, with fixed time interval between each wipe. RAIN_SENSOR indicates intermittent wiping based on rain intensity. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->Mode
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.Mode
[get] OK
Vehicle.Body.Windshield.Front.Wiping.Mode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.Mode 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.Body.Windshield.Front.Wiping.Mode is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.Mode is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.Mode is 3ee6552c96e551c5b06b79ad30226767
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.1.3.4 - System
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System |
| Description: |
Signals to control behavior of wipers in detail. By default VSS expects only one instance. |
| Comment: |
These signals are typically not directly available to the user/driver of the vehicle. The overlay in overlays/extensions/dual_wiper_systems.vspec can be used to modify this branch to support two instances; Primary and Secondary. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System is 9002ff76166950e0aa3b7c9df3b53468
Children
This vehicle signal is a branch or structure and thus has sub-pages:
- Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition (Actual position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific.)
- Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent (Actual current used by wiper drive.)
- Vehicle.Body.Windshield.Front.Wiping.System.Frequency (Wiping frequency/speed, measured in cycles per minute. The signal concerns the actual speed of the wiper blades when moving. Intervals/pauses are excluded, i.e. the value corresponds to the number of cycles that would be completed in 1 minute if wiping permanently over default range.)
- Vehicle.Body.Windshield.Front.Wiping.System.IsBlocked (Indicates if wiper movement is blocked. True = Movement blocked. False = Movement not blocked.)
- Vehicle.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle (Indicates if current wipe movement is completed or near completion. True = Movement is completed or near completion. Changes to RequestedPosition will be executed first after reaching previous RequestedPosition, if it has not already been reached. False = Movement is not near completion. Any change to RequestedPosition will be executed immediately. Change of direction may not be allowed.)
- Vehicle.Body.Windshield.Front.Wiping.System.IsOverheated (Indicates if wiper system is overheated. True = Wiper system overheated. False = Wiper system not overheated.)
- Vehicle.Body.Windshield.Front.Wiping.System.IsPositionReached (Indicates if a requested position has been reached. IsPositionReached refers to the previous position in case the TargetPosition is updated while IsEndingWipeCycle=True. True = Current or Previous TargetPosition reached. False = Position not (yet) reached, or wipers have moved away from the reached position.)
- Vehicle.Body.Windshield.Front.Wiping.System.IsWiperError (Indicates system failure. True if wiping is disabled due to system failure.)
- Vehicle.Body.Windshield.Front.Wiping.System.IsWiping (Indicates wiper movement. True if wiper blades are moving. Change of direction shall be considered as IsWiping if wipers will continue to move directly after the change of direction.)
- Vehicle.Body.Windshield.Front.Wiping.System.Mode (Requested mode of wiper system. STOP_HOLD means that the wipers shall move to position given by TargetPosition and then hold the position. WIPE means that wipers shall move to the position given by TargetPosition and then hold the position if no new TargetPosition is requested. PLANT_MODE means that wiping is disabled. Exact behavior is vehicle specific. EMERGENCY_STOP means that wiping shall be immediately stopped without holding the position.)
- Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition (Requested position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific. System behavior when receiving TargetPosition depends on Mode and IsEndingWipeCycle. Supported values are vehicle specific and might be dynamically corrected. If IsEndingWipeCycle=True then wipers will complete current movement before actuating new TargetPosition. If IsEndingWipeCycle=False then wipers will directly change destination if the TargetPosition is changed.)
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.3.4.1 - ActualPosition
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition |
| Description: |
Actual position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific. |
| Comment: |
Default parking position might be used as reference position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->ActualPosition
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.ActualPosition is 026307b591465a8a99ffc0ebf262b393
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.1.3.4.2 - DriveCurrent
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent |
| Description: |
Actual current used by wiper drive. |
| Comment: |
May be negative in special situations. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->DriveCurrent
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.DriveCurrent is 251e695821b758e7b7d459d5e2ab6ca4
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.1.3.4.3 - Frequency
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.Frequency |
| Description: |
Wiping frequency/speed, measured in cycles per minute. The signal concerns the actual speed of the wiper blades when moving. Intervals/pauses are excluded, i.e. the value corresponds to the number of cycles that would be completed in 1 minute if wiping permanently over default range. |
| Comment: |
Examples - 0 = Wipers stopped, 80 = Wipers doing 80 cycles per minute (in WIPE mode). |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->Frequency
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.Frequency
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.Frequency: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.Frequency 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.Body.Windshield.Front.Wiping.System.Frequency is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.Frequency is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.Frequency is 7394c8b8d20d52638881161ec1b41fc0
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.1.3.4.4 - IsBlocked
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.IsBlocked |
| Description: |
Indicates if wiper movement is blocked. True = Movement blocked. False = Movement not blocked. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->IsBlocked
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.IsBlocked
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.IsBlocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.IsBlocked 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.Body.Windshield.Front.Wiping.System.IsBlocked is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.IsBlocked is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.IsBlocked is 4b526a2c781e56e386c82df226061f9e
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.1.3.4.5 - IsEndingWipeCycle
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle |
| Description: |
Indicates if current wipe movement is completed or near completion. True = Movement is completed or near completion. Changes to RequestedPosition will be executed first after reaching previous RequestedPosition, if it has not already been reached. False = Movement is not near completion. Any change to RequestedPosition will be executed immediately. Change of direction may not be allowed. |
| Comment: |
In continuous wiping between A and B this sensor can be used a trigger to update TargetPosition. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->IsEndingWipeCycle
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle 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.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.IsEndingWipeCycle is 5000f7f0c39e5fed9a95413ae4166482
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.1.3.4.6 - IsOverheated
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.IsOverheated |
| Description: |
Indicates if wiper system is overheated. True = Wiper system overheated. False = Wiper system not overheated. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->IsOverheated
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.IsOverheated
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.IsOverheated: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.IsOverheated 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.Body.Windshield.Front.Wiping.System.IsOverheated is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.IsOverheated is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.IsOverheated is e05d376ec2525ba2b61039d55f93760f
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.1.3.4.7 - IsPositionReached
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.IsPositionReached |
| Description: |
Indicates if a requested position has been reached. IsPositionReached refers to the previous position in case the TargetPosition is updated while IsEndingWipeCycle=True. True = Current or Previous TargetPosition reached. False = Position not (yet) reached, or wipers have moved away from the reached position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->IsPositionReached
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.IsPositionReached
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.IsPositionReached: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.IsPositionReached 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.Body.Windshield.Front.Wiping.System.IsPositionReached is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.IsPositionReached is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.IsPositionReached is d42149fa8982593991aa5cd13a1cdee9
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.1.3.4.8 - IsWiperError
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.IsWiperError |
| Description: |
Indicates system failure. True if wiping is disabled due to system failure. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->IsWiperError
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.IsWiperError
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.IsWiperError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.IsWiperError 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.Body.Windshield.Front.Wiping.System.IsWiperError is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.IsWiperError is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.IsWiperError is 5276055d973f57998e1b8d6e536de735
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.1.3.4.9 - IsWiping
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.IsWiping |
| Description: |
Indicates wiper movement. True if wiper blades are moving. Change of direction shall be considered as IsWiping if wipers will continue to move directly after the change of direction. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->IsWiping
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.IsWiping
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.IsWiping: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.IsWiping 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.Body.Windshield.Front.Wiping.System.IsWiping is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.IsWiping is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.IsWiping is 2015a4610d7a5fbdbb63b260640838e6
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.1.3.4.10 - Mode
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.Mode |
| Description: |
Requested mode of wiper system. STOP_HOLD means that the wipers shall move to position given by TargetPosition and then hold the position. WIPE means that wipers shall move to the position given by TargetPosition and then hold the position if no new TargetPosition is requested. PLANT_MODE means that wiping is disabled. Exact behavior is vehicle specific. EMERGENCY_STOP means that wiping shall be immediately stopped without holding the position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->Mode
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.Mode
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.Mode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.Mode 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.Body.Windshield.Front.Wiping.System.Mode is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.Mode is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.Mode is d15518f5d1bc54a38718f43ef749dd34
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.1.3.4.11 - TargetPosition
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition |
| Description: |
Requested position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific. System behavior when receiving TargetPosition depends on Mode and IsEndingWipeCycle. Supported values are vehicle specific and might be dynamically corrected. If IsEndingWipeCycle=True then wipers will complete current movement before actuating new TargetPosition. If IsEndingWipeCycle=False then wipers will directly change destination if the TargetPosition is changed. |
| Comment: |
Default parking position might be used as reference position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->System
System-->TargetPosition
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition
[get] OK
Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.System.TargetPosition is 7a4a3fdd2947596dbada6980c142f090
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.1.3.5 - WiperWear
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Front.Wiping.WiperWear |
| Description: |
Wiper wear as percent. 0 = No Wear. 100 = Worn. Replacement required. Method for calculating or estimating wiper wear is vehicle specific. For windshields with multiple wipers the wear reported shall correspond to the most worn wiper. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Front
Front-->Wiping
Wiping-->WiperWear
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Front.Wiping.WiperWear
[get] OK
Vehicle.Body.Windshield.Front.Wiping.WiperWear: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Front.Wiping.WiperWear 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.Body.Windshield.Front.Wiping.WiperWear is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Front.Wiping.WiperWear is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Front.Wiping.WiperWear is 92c879c11bc65e6da30d582a3928caac
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 - Rear
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear |
| Description: |
Windshield signals. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Rear is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear is 095ff58459b854aaa742e56447fe7a93
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.2.1 - IsHeatingOn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.IsHeatingOn |
| Description: |
Windshield heater status. False - off, True - on. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->IsHeatingOn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.IsHeatingOn
[get] OK
Vehicle.Body.Windshield.Rear.IsHeatingOn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.IsHeatingOn 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.Body.Windshield.Rear.IsHeatingOn is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Rear.IsHeatingOn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.IsHeatingOn is 76d811b4c4c356f4898dd6383e28bc6f
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.2 - WasherFluid
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.WasherFluid |
| Description: |
Windshield washer fluid signals |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->WasherFluid
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Rear.WasherFluid is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.WasherFluid is 1ea4ac2370e1567b9b812c1e3020ddfb
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.2.2.1 - IsLevelLow
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow |
| Description: |
Low level indication for washer fluid. True = Level Low. False = Level OK. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->WasherFluid
WasherFluid-->IsLevelLow
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow
[get] OK
Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow 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.Body.Windshield.Rear.WasherFluid.IsLevelLow is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow is 8ca0356548ae54e8af3aeace49e5ed71
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.2.2 - Level
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.WasherFluid.Level |
| Description: |
Washer fluid level as a percent. 0 = Empty. 100 = Full. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->WasherFluid
WasherFluid-->Level
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.WasherFluid.Level
[get] OK
Vehicle.Body.Windshield.Rear.WasherFluid.Level: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.WasherFluid.Level 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.Body.Windshield.Rear.WasherFluid.Level is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.WasherFluid.Level is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.WasherFluid.Level is c167e5b265895c108da1b9582de2dd91
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.3 - Wiping
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping |
| Description: |
Windshield wiper signals. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping is f56e80a50fd75dbca48581aea4f012b7
Children
This vehicle signal is a branch or structure and thus has sub-pages:
- Vehicle.Body.Windshield.Rear.Wiping.Intensity (Relative intensity/sensitivity for interval and rain sensor mode as requested by user/driver. Has no significance if Windshield.Wiping.Mode is OFF/SLOW/MEDIUM/FAST 0 - wipers inactive. 1 - minimum intensity (lowest frequency/sensitivity, longest interval). 2/3/4/… - higher intensity (higher frequency/sensitivity, shorter interval). Maximum value supported is vehicle specific.)
- Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn (Wiper wear status. True = Worn, Replacement recommended or required. False = Not Worn.)
- Vehicle.Body.Windshield.Rear.Wiping.Mode (Wiper mode requested by user/driver. INTERVAL indicates intermittent wiping, with fixed time interval between each wipe. RAIN_SENSOR indicates intermittent wiping based on rain intensity.)
- Vehicle.Body.Windshield.Rear.Wiping.System (Signals to control behavior of wipers in detail. By default VSS expects only one instance.)
- Vehicle.Body.Windshield.Rear.Wiping.WiperWear (Wiper wear as percent. 0 = No Wear. 100 = Worn. Replacement required. Method for calculating or estimating wiper wear is vehicle specific. For windshields with multiple wipers the wear reported shall correspond to the most worn wiper.)
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.2.3.1 - Intensity
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.Intensity |
| Description: |
Relative intensity/sensitivity for interval and rain sensor mode as requested by user/driver. Has no significance if Windshield.Wiping.Mode is OFF/SLOW/MEDIUM/FAST 0 - wipers inactive. 1 - minimum intensity (lowest frequency/sensitivity, longest interval). 2/3/4/… - higher intensity (higher frequency/sensitivity, shorter interval). Maximum value supported is vehicle specific. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->Intensity
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.Intensity
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.Intensity: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.Intensity 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.Body.Windshield.Rear.Wiping.Intensity is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.Intensity is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.Intensity is f18b13b9d96b51c492c031d3d86d22da
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.3.2 - IsWipersWorn
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn |
| Description: |
Wiper wear status. True = Worn, Replacement recommended or required. False = Not Worn. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->IsWipersWorn
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn 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.Body.Windshield.Rear.Wiping.IsWipersWorn is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn is 0e8d5f7cb6295b908be3a03e8792cca8
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.3.3 - Mode
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.Mode |
| Description: |
Wiper mode requested by user/driver. INTERVAL indicates intermittent wiping, with fixed time interval between each wipe. RAIN_SENSOR indicates intermittent wiping based on rain intensity. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->Mode
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.Mode
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.Mode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.Mode 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.Body.Windshield.Rear.Wiping.Mode is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.Mode is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.Mode is 8cc0b88ac8b45f5fa30bb7755ce22648
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.3.4 - System
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System |
| Description: |
Signals to control behavior of wipers in detail. By default VSS expects only one instance. |
| Comment: |
These signals are typically not directly available to the user/driver of the vehicle. The overlay in overlays/extensions/dual_wiper_systems.vspec can be used to modify this branch to support two instances; Primary and Secondary. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System is a00826f6ecc25c3fae7ad164361bdb33
Children
This vehicle signal is a branch or structure and thus has sub-pages:
- Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition (Actual position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific.)
- Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent (Actual current used by wiper drive.)
- Vehicle.Body.Windshield.Rear.Wiping.System.Frequency (Wiping frequency/speed, measured in cycles per minute. The signal concerns the actual speed of the wiper blades when moving. Intervals/pauses are excluded, i.e. the value corresponds to the number of cycles that would be completed in 1 minute if wiping permanently over default range.)
- Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked (Indicates if wiper movement is blocked. True = Movement blocked. False = Movement not blocked.)
- Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle (Indicates if current wipe movement is completed or near completion. True = Movement is completed or near completion. Changes to RequestedPosition will be executed first after reaching previous RequestedPosition, if it has not already been reached. False = Movement is not near completion. Any change to RequestedPosition will be executed immediately. Change of direction may not be allowed.)
- Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated (Indicates if wiper system is overheated. True = Wiper system overheated. False = Wiper system not overheated.)
- Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached (Indicates if a requested position has been reached. IsPositionReached refers to the previous position in case the TargetPosition is updated while IsEndingWipeCycle=True. True = Current or Previous TargetPosition reached. False = Position not (yet) reached, or wipers have moved away from the reached position.)
- Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError (Indicates system failure. True if wiping is disabled due to system failure.)
- Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping (Indicates wiper movement. True if wiper blades are moving. Change of direction shall be considered as IsWiping if wipers will continue to move directly after the change of direction.)
- Vehicle.Body.Windshield.Rear.Wiping.System.Mode (Requested mode of wiper system. STOP_HOLD means that the wipers shall move to position given by TargetPosition and then hold the position. WIPE means that wipers shall move to the position given by TargetPosition and then hold the position if no new TargetPosition is requested. PLANT_MODE means that wiping is disabled. Exact behavior is vehicle specific. EMERGENCY_STOP means that wiping shall be immediately stopped without holding the position.)
- Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition (Requested position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific. System behavior when receiving TargetPosition depends on Mode and IsEndingWipeCycle. Supported values are vehicle specific and might be dynamically corrected. If IsEndingWipeCycle=True then wipers will complete current movement before actuating new TargetPosition. If IsEndingWipeCycle=False then wipers will directly change destination if the TargetPosition is changed.)
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.2.3.4.1 - ActualPosition
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition |
| Description: |
Actual position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific. |
| Comment: |
Default parking position might be used as reference position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->ActualPosition
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition is eddee2607a135582bbcf3d3afc845892
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.3.4.2 - DriveCurrent
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent |
| Description: |
Actual current used by wiper drive. |
| Comment: |
May be negative in special situations. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->DriveCurrent
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent is 7a254692329055dfb4089e2dcc1d4ef3
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.3.4.3 - Frequency
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.Frequency |
| Description: |
Wiping frequency/speed, measured in cycles per minute. The signal concerns the actual speed of the wiper blades when moving. Intervals/pauses are excluded, i.e. the value corresponds to the number of cycles that would be completed in 1 minute if wiping permanently over default range. |
| Comment: |
Examples - 0 = Wipers stopped, 80 = Wipers doing 80 cycles per minute (in WIPE mode). |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->Frequency
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.Frequency
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.Frequency: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.Frequency 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.Body.Windshield.Rear.Wiping.System.Frequency is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.Frequency is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.Frequency is 371171d971995c999585b028e19be461
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.3.4.4 - IsBlocked
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked |
| Description: |
Indicates if wiper movement is blocked. True = Movement blocked. False = Movement not blocked. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->IsBlocked
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked 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.Body.Windshield.Rear.Wiping.System.IsBlocked is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked is 046e818b4dd9595a8301503e9afe028b
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.3.4.5 - IsEndingWipeCycle
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle |
| Description: |
Indicates if current wipe movement is completed or near completion. True = Movement is completed or near completion. Changes to RequestedPosition will be executed first after reaching previous RequestedPosition, if it has not already been reached. False = Movement is not near completion. Any change to RequestedPosition will be executed immediately. Change of direction may not be allowed. |
| Comment: |
In continuous wiping between A and B this sensor can be used a trigger to update TargetPosition. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->IsEndingWipeCycle
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle 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.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle is c1357156d87c58f49d4c43c2a6e97c03
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.3.4.6 - IsOverheated
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated |
| Description: |
Indicates if wiper system is overheated. True = Wiper system overheated. False = Wiper system not overheated. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->IsOverheated
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated 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.Body.Windshield.Rear.Wiping.System.IsOverheated is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated is d30bc6f33b995ef491c252980a559ee2
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.3.4.7 - IsPositionReached
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached |
| Description: |
Indicates if a requested position has been reached. IsPositionReached refers to the previous position in case the TargetPosition is updated while IsEndingWipeCycle=True. True = Current or Previous TargetPosition reached. False = Position not (yet) reached, or wipers have moved away from the reached position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->IsPositionReached
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached 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.Body.Windshield.Rear.Wiping.System.IsPositionReached is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached is ad35e8d17cd95273b1091dcef2104ea1
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.3.4.8 - IsWiperError
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError |
| Description: |
Indicates system failure. True if wiping is disabled due to system failure. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->IsWiperError
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError 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.Body.Windshield.Rear.Wiping.System.IsWiperError is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError is ac5983deacbe59d7ba1312d44bfd9cd4
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.3.4.9 - IsWiping
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping |
| Description: |
Indicates wiper movement. True if wiper blades are moving. Change of direction shall be considered as IsWiping if wipers will continue to move directly after the change of direction. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->IsWiping
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping 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.Body.Windshield.Rear.Wiping.System.IsWiping is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping is 4e001bf679e85c9aa7319bafc3a86e75
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.3.4.10 - Mode
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.Mode |
| Description: |
Requested mode of wiper system. STOP_HOLD means that the wipers shall move to position given by TargetPosition and then hold the position. WIPE means that wipers shall move to the position given by TargetPosition and then hold the position if no new TargetPosition is requested. PLANT_MODE means that wiping is disabled. Exact behavior is vehicle specific. EMERGENCY_STOP means that wiping shall be immediately stopped without holding the position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->Mode
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.Mode
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.Mode: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.Mode 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.Body.Windshield.Rear.Wiping.System.Mode is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.Mode is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.Mode is f2f47522466d570baa7618fac5b0359c
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.3.4.11 - TargetPosition
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition |
| Description: |
Requested position of main wiper blade for the wiper system relative to reference position. Location of reference position (0 degrees) and direction of positive/negative degrees is vehicle specific. System behavior when receiving TargetPosition depends on Mode and IsEndingWipeCycle. Supported values are vehicle specific and might be dynamically corrected. If IsEndingWipeCycle=True then wipers will complete current movement before actuating new TargetPosition. If IsEndingWipeCycle=False then wipers will directly change destination if the TargetPosition is changed. |
| Comment: |
Default parking position might be used as reference position. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->System
System-->TargetPosition
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition 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 float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition is an Actuator.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition is c39bef0760185555904a92a305392080
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.3.5 - WiperWear
|
|
| Full qualified VSS Path: |
Vehicle.Body.Windshield.Rear.Wiping.WiperWear |
| Description: |
Wiper wear as percent. 0 = No Wear. 100 = Worn. Replacement required. Method for calculating or estimating wiper wear is vehicle specific. For windshields with multiple wipers the wear reported shall correspond to the most worn wiper. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Windshield
Windshield-->Rear
Rear-->Wiping
Wiping-->WiperWear
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Windshield.Rear.Wiping.WiperWear
[get] OK
Vehicle.Body.Windshield.Rear.Wiping.WiperWear: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Windshield.Rear.Wiping.WiperWear 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.Body.Windshield.Rear.Wiping.WiperWear is a Sensor.
The vehicle signal Vehicle.Body.Windshield.Rear.Wiping.WiperWear is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Windshield.Rear.Wiping.WiperWear is afd6a352230f5eeaa8ac5f1f188bfd33
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.
8 - BodyType
|
|
| Full qualified VSS Path: |
Vehicle.Body.BodyType |
| Description: |
Body type code as defined by ISO 3779. |
Navigation
flowchart LR
Vehicle-->Body
Body-->BodyType
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.BodyType
[get] OK
Vehicle.Body.BodyType: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.BodyType 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.Body.BodyType is an Attribute.
The vehicle signal Vehicle.Body.BodyType is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.BodyType is 6253412513105deea63b1d424117fd88
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.
9 - Hood
|
|
| Full qualified VSS Path: |
Vehicle.Body.Hood |
| Description: |
Hood status. |
| Comment: |
The hood is the hinged cover over the engine compartment of a motor vehicles. Depending on vehicle, it can be either in the front or back of the vehicle. Luggage compartments are in VSS called trunks, even if they are located at the front of the vehicle. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Hood
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Hood is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Hood is 84510652bf915bbe8bf5f477aab2b44a
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.
9.1 - IsOpen
|
|
| Full qualified VSS Path: |
Vehicle.Body.Hood.IsOpen |
| Description: |
Hood open or closed. True = Open. False = Closed. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Hood
Hood-->IsOpen
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Hood.IsOpen
[get] OK
Vehicle.Body.Hood.IsOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Hood.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.Body.Hood.IsOpen is an Actuator.
The vehicle signal Vehicle.Body.Hood.IsOpen is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Hood.IsOpen is 890aa3359e1a579288af1cf8e6b5b71f
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.
10 - RefuelPosition
|
|
| Full qualified VSS Path: |
Vehicle.Body.RefuelPosition |
| Description: |
Location of the fuel cap or charge port. |
Navigation
flowchart LR
Vehicle-->Body
Body-->RefuelPosition
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.RefuelPosition
[get] OK
Vehicle.Body.RefuelPosition: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.RefuelPosition 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.Body.RefuelPosition is an Attribute.
The vehicle signal Vehicle.Body.RefuelPosition is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.RefuelPosition is 53ef90a851fa57f0810d50238e852f02
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.
11 - Trunk
|
|
| Full qualified VSS Path: |
Vehicle.Body.Trunk |
| Description: |
Trunk status. |
| Comment: |
A trunk is a luggage compartment in a vehicle. Depending on vehicle, it can be either in the front or back of the vehicle. Some vehicles may have trunks both at the front and at the rear of the vehicle. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Trunk
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Trunk is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Trunk is a584c6a5aa235cb88ac686f8d72a1dff
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.
11.1 - Front
|
|
| Full qualified VSS Path: |
Vehicle.Body.Trunk.Front |
| Description: |
Trunk status. |
| Comment: |
A trunk is a luggage compartment in a vehicle. Depending on vehicle, it can be either in the front or back of the vehicle. Some vehicles may have trunks both at the front and at the rear of the vehicle. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Trunk
Trunk-->Front
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Trunk.Front is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Trunk.Front is a455aca5bae55c22b7949fd31a765a6c
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.
11.1.1 - IsLocked
|
|
| Full qualified VSS Path: |
Vehicle.Body.Trunk.Front.IsLocked |
| Description: |
Is trunk locked or unlocked. True = Locked. False = Unlocked. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Trunk
Trunk-->Front
Front-->IsLocked
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Front.IsLocked
[get] OK
Vehicle.Body.Trunk.Front.IsLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.IsLocked is an Actuator.
The vehicle signal Vehicle.Body.Trunk.Front.IsLocked is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Trunk.Front.IsLocked is e0eabc210f07505fa1b66b67729d681b
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.
11.1.2 - IsOpen
|
|
| Full qualified VSS Path: |
Vehicle.Body.Trunk.Front.IsOpen |
| Description: |
Trunk open or closed. True = Open. False = Closed. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Trunk
Trunk-->Front
Front-->IsOpen
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Front.IsOpen
[get] OK
Vehicle.Body.Trunk.Front.IsOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Front.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.Body.Trunk.Front.IsOpen is an Actuator.
The vehicle signal Vehicle.Body.Trunk.Front.IsOpen is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Trunk.Front.IsOpen is 2047de0896a352fcaf02baa06819a023
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.
11.2 - Rear
|
|
| Full qualified VSS Path: |
Vehicle.Body.Trunk.Rear |
| Description: |
Trunk status. |
| Comment: |
A trunk is a luggage compartment in a vehicle. Depending on vehicle, it can be either in the front or back of the vehicle. Some vehicles may have trunks both at the front and at the rear of the vehicle. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Trunk
Trunk-->Rear
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
The vehicle signal Vehicle.Body.Trunk.Rear is a Branch.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Trunk.Rear is a6170ff5e4325f38b5d57402e1d95e5a
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.
11.2.1 - IsLocked
|
|
| Full qualified VSS Path: |
Vehicle.Body.Trunk.Rear.IsLocked |
| Description: |
Is trunk locked or unlocked. True = Locked. False = Unlocked. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Trunk
Trunk-->Rear
Rear-->IsLocked
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Rear.IsLocked
[get] OK
Vehicle.Body.Trunk.Rear.IsLocked: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Rear.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.Body.Trunk.Rear.IsLocked is an Actuator.
The vehicle signal Vehicle.Body.Trunk.Rear.IsLocked is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Trunk.Rear.IsLocked is 8f9b55b002ed59d3ac2ef0b014abf4aa
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.
11.2.2 - IsOpen
|
|
| Full qualified VSS Path: |
Vehicle.Body.Trunk.Rear.IsOpen |
| Description: |
Trunk open or closed. True = Open. False = Closed. |
Navigation
flowchart LR
Vehicle-->Body
Body-->Trunk
Trunk-->Rear
Rear-->IsOpen
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Body.Trunk.Rear.IsOpen
[get] OK
Vehicle.Body.Trunk.Rear.IsOpen: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Body.Trunk.Rear.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.Body.Trunk.Rear.IsOpen is an Actuator.
The vehicle signal Vehicle.Body.Trunk.Rear.IsOpen is a Signal.
UUID
Each vehicle signal is identified by a Universally Unique Identifier (UUID)
The UUID for Vehicle.Body.Trunk.Rear.IsOpen is 3d3249e59306594698367b839b12c938
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.