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

Return to the regular view of this page.

Rear
Full qualified VSS Path: Vehicle.Body.Windshield.Rear
Description: Windshield signals.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

1 - IsHeatingOn
Full qualified VSS Path: Vehicle.Body.Windshield.Rear.IsHeatingOn
Description: Windshield heater status. False - off, True - on.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.IsHeatingOn

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.IsHeatingOn VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2 - WasherFluid
Full qualified VSS Path: Vehicle.Body.Windshield.Rear.WasherFluid
Description: Windshield washer fluid signals
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.WasherFluid

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.WasherFluid.IsLevelLow VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

2.2 - Level
Full qualified VSS Path: Vehicle.Body.Windshield.Rear.WasherFluid.Level
Description: Washer fluid level as a percent. 0 = Empty. 100 = Full.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.WasherFluid.Level

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.WasherFluid.Level VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Unit percent VSS: Units
Label percent
Description Relation measured in percent VSS: Sensors & Actuators
Domain relation
Maximum value 100 VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

3 - Wiping
Full qualified VSS Path: Vehicle.Body.Windshield.Rear.Wiping
Description: Windshield wiper signals.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.Intensity

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.Intensity VSS: Addressing nodes
Data type uint8 VSS: Datatypes

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.IsWipersWorn VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.Mode

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.Mode VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['OFF', 'SLOW', 'MEDIUM', 'FAST', 'INTERVAL', 'RAIN_SENSOR'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.ActualPosition VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.DriveCurrent VSS: Addressing nodes
Data type float VSS: Datatypes
Unit A VSS: Units
Label ampere
Description Electric current measured in amperes VSS: Sensors & Actuators
Domain electric current

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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).
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.Frequency

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.Frequency VSS: Addressing nodes
Data type uint8 VSS: Datatypes

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.IsBlocked VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.IsEndingWipeCycle VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.IsOverheated VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.IsPositionReached VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.IsWiperError VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.IsWiping VSS: Addressing nodes
Data type boolean VSS: Datatypes

Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.Mode

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.Mode VSS: Addressing nodes
Data type string VSS: Datatypes
Allowed values ['STOP_HOLD', 'WIPE', 'PLANT_MODE', 'EMERGENCY_STOP'] VSS: Specifying allowed values

Note: The string datatype is a character string.

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.System.TargetPosition VSS: Addressing nodes
Data type float VSS: Datatypes
Unit degrees VSS: Units
Label degree
Description Angle measured in degrees VSS: Sensors & Actuators
Domain angle

Note: The float datatype is a floating point number which technically allows values between -3.4e ^ -38 and 3.4e ^ 38

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.

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.
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.

Vehicle Model Direct link to Vehicle Signal
ACME Car (EV) v0.1 Vehicle.Body.Windshield.Rear.Wiping.WiperWear

Data Type & Unit
Path Vehicle.Body.Windshield.Rear.Wiping.WiperWear VSS: Addressing nodes
Data type uint8 VSS: Datatypes
Maximum value 100 VSS: Sensors & Actuators

Note: The uint8 datatype is an unsigned 8-bit integer which technically allows values between 0 and 255 (inclusive).

Signal Information

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:
Enhancement request Create COVESA GitHub Issue
Join COVESA www.covesa.global
Discuss VSS on Slack w3cauto.slack.com
VSS Data Experts on Google Groups covesa.global data-expert-group

About VSS

The Vehicle Signal Specification (VSS) is an initiative by COVESA to define a syntax and a catalog for vehicle signals. The source code and releases can be found in the VSS github repository.

Supported datatypes

The following is a list of VSS supported built-in datatypes:

Name Type Min Max
uint8 unsigned 8-bit integer 0 255
int8 signed 8-bit integer -128 127
uint16 unsigned 16-bit integer 0 65535
int16 signed 16-bit integer -32768 32767
uint32 unsigned 32-bit integer 0 4294967295
int32 signed 32-bit integer -2147483648 2147483647
uint64 unsigned 64-bit integer 0 2^64 - 1
int64 signed 64-bit integer -2^63 2^63 - 1
boolean boolean value 0/false 1/true
float floating point number -3.4e -38 3.4e 38
double double precision floating point number -1.7e -300 1.7e 300
string character string n/a n/a

Min, max and default values defined in a Vehicle Signal Specification must be in the supported range of the data type.