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

Return to the regular view of this page.

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

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

Signal Information

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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 - 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.
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.

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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 - 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).
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.

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.

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

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

Data Type & Unit
Path Vehicle.Body.Windshield.Front.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.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:
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.