RoadIcingState
| Full qualified VSS Path: | Vehicle.Safety.RoadIcingState |
| Description: | Indicates whether the vehicle is currently at risk of icing-related loss of control or has detected such conditions affecting traction. |
| Comment: | Derived assessment distinct from Vehicle.Exterior.RoadSurfaceCondition, which reports observed surface state; RoadIcingState reports the derived risk of icing-related loss of control. RISK can be elevated even when RoadSurfaceCondition reports DRY (black ice, freezing-rain onset), and NONE can hold even when it reports SNOW (low-speed packed snow with adequate winter-tire grip). May be derived from Vehicle.Exterior.RoadSurfaceCondition, Vehicle.Exterior.AirTemperature, Vehicle.ADAS.ESC.RoadFriction.MostProbable, and Vehicle.Exterior.RoadSurfaceTemperature. NONE indicates no elevated icing risk. RISK indicates conditions favor ice formation or onset of icing-related traction loss. DETECTED indicates active icing-related loss of control is occurring. UNKNOWN shall be used when the system cannot assess icing risk. Criteria for each state may be OEM specific. Primary consumers: driver-warning systems, ADAS interventions, and navigation systems (re-routing away from elevated-risk segments). Related to VSS issue #877 (Connected Safety signals). |
Navigation
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Safety.RoadIcingState
[get] OK
Vehicle.Safety.RoadIcingState: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Safety.RoadIcingState 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.Safety.RoadIcingState |
Data Type & Unit
| Path | Vehicle.Safety.RoadIcingState |
VSS: Addressing nodes |
| Data type | string |
VSS: Datatypes |
| Allowed values | ['UNKNOWN', 'NONE', 'RISK', 'DETECTED'] |
VSS: Specifying allowed values |
Note: The string datatype is a character string.
Signal Information
The vehicle signal Vehicle.Safety.RoadIcingState is a Sensor.
The vehicle signal Vehicle.Safety.RoadIcingState is a Signal.
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.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.