This is the multi-page printable view of this section.
Click here to print.
Return to the regular view of this page.
Safety
|
|
| Full qualified VSS Path: |
Vehicle.Safety |
| Description: |
Safety-related derived signals for crash detection and emergency response. |
Navigation
flowchart LR
Vehicle-->Safety
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 |
The vehicle signal Vehicle.Safety is a Branch.
Children
This vehicle signal is a branch or structure and thus has sub-pages:
Feedback
Do you think this Vehicle Signal specification needs enhancement? Do you want to discuss with experts? Try the following ressources to get in touch with the VSS community:
About VSS
The Vehicle Signal Specification (VSS)
is an initiative by COVESA to define a syntax and a catalog for vehicle signals.
The source code and releases can be found in the VSS github repository.
1 - IsFire
|
|
| Full qualified VSS Path: |
Vehicle.Safety.IsFire |
| Description: |
Indicates whether a fire has been detected in or on the vehicle. |
| Comment: |
Determination method is implementation specific. May be derived from temperature sensors, battery thermal runaway detection, or dedicated fire/smoke detection systems. Primary consumers: emergency dispatch and first responder systems. Related to VSS issue #877 (Connected Safety signals). |
|
|
Navigation
flowchart LR
Vehicle-->Safety
Safety-->IsFire
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Safety.IsFire
[get] OK
Vehicle.Safety.IsFire: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Safety.IsFire false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Safety.IsFire is a Sensor.
The vehicle signal Vehicle.Safety.IsFire 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:
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 - IsSubmersed
|
|
| Full qualified VSS Path: |
Vehicle.Safety.IsSubmersed |
| Description: |
Indicates whether the vehicle is partially or fully submersed in water. |
| Comment: |
Determination method is implementation specific. May be derived from pressure sensors, water contact sensors, door seal sensors, or anomalous rain detection intensity readings. Primary consumers: emergency dispatch and first responder systems. Related to VSS issue #877 (Connected Safety signals). |
|
|
Navigation
flowchart LR
Vehicle-->Safety
Safety-->IsSubmersed
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Safety.IsSubmersed
[get] OK
Vehicle.Safety.IsSubmersed: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Safety.IsSubmersed false
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The boolean datatype is a boolean value which technically allows values of either 0 and false; or 1 and true.
The vehicle signal Vehicle.Safety.IsSubmersed is a Sensor.
The vehicle signal Vehicle.Safety.IsSubmersed 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:
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 - 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
flowchart LR
Vehicle-->Safety
Safety-->RoadIcingState
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.
Data Type & Unit
Note: The string datatype is a character string.
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:
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 - Rollover
|
|
| Full qualified VSS Path: |
Vehicle.Safety.Rollover |
| Description: |
Indicates whether the vehicle has rolled over or is at risk of rollover. |
| Comment: |
May be derived from Vehicle.AngularVelocity, Vehicle.Orientation.Roll, and Vehicle.Orientation.Pitch signals. NONE indicates normal orientation. RISK indicates the vehicle is at elevated risk of rollover. DETECTED indicates a rollover event has occurred. UNKNOWN shall be used when the system cannot assess rollover status. Criteria for each state may be OEM specific. Primary consumers: emergency dispatch and first responder systems. Related to VSS issue #877 (Connected Safety signals). |
|
|
Navigation
flowchart LR
Vehicle-->Safety
Safety-->Rollover
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Safety.Rollover
[get] OK
Vehicle.Safety.Rollover: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Safety.Rollover Foo
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The string datatype is a character string.
The vehicle signal Vehicle.Safety.Rollover is a Sensor.
The vehicle signal Vehicle.Safety.Rollover 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:
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 - VisibilityImpairment
|
|
| Full qualified VSS Path: |
Vehicle.Safety.VisibilityImpairment |
| Description: |
Indicates whether reduced exterior visibility is currently creating a driving-safety risk, or such a condition has been detected. |
| Comment: |
Derived safety assessment layered on the Exterior observational signals Vehicle.Exterior.VisibilityCondition (dominant cause of reduced visibility) and Vehicle.Exterior.VisibilityDistance (quantitative range). VisibilityImpairment is cause-agnostic and reports only the derived, speed-relative safety risk on top of those signals; the cause itself (snow, fog, etc.) is carried by VisibilityCondition. May be derived from Vehicle.Exterior.VisibilityCondition and Vehicle.Exterior.VisibilityDistance, optionally combined with vehicle speed and stopping-distance context. NONE indicates visibility is adequate for current driving conditions. RISK indicates visibility is degrading toward a level that materially raises driving risk for the current speed. DETECTED indicates visibility impairment severe enough to require driver action is active. UNKNOWN shall be used when the system cannot assess visibility impairment. Criteria for each state may be OEM specific. Primary consumers: driver-warning systems, navigation systems (re-routing on impaired visibility), and emergency dispatch systems. Related to VSS issue #877 (Connected Safety signals). |
|
|
Navigation
flowchart LR
Vehicle-->Safety
Safety-->VisibilityImpairment
Eclipse Leda: Usage Example
In Eclipse Kuksa.VAL Databroker CLI:
$ databroker-cli
sdv.databroker.v1 > connect
[connect] OK
sdv.databroker.v1 > get Vehicle.Safety.VisibilityImpairment
[get] OK
Vehicle.Safety.VisibilityImpairment: ( NotAvailable )
sdv.databroker.v1 > set Vehicle.Safety.VisibilityImpairment Foo
[set] OK
Digital Auto: Playground
playground.digital.auto provides an in-browser, rapid prototyping environment utilizing the COVESA APIs for connected vehicles.
Data Type & Unit
Note: The string datatype is a character string.
The vehicle signal Vehicle.Safety.VisibilityImpairment is a Sensor.
The vehicle signal Vehicle.Safety.VisibilityImpairment 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:
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.