vehicle_signal_specification
vehicle_signal_specification copied to clipboard
COVESA
adding ObstacleDetection and Adaptive Cruise control signals
adding ObstacleDetection:ForwardDistance ObstacleDetection:ForwardTimeGap CruiseControl.AdaptiveIsActive CruiseControl.AdaptiveDistanceSet
Drawing from Android Automotive documentation
https://source.android.com/docs/automotive/vhal/adas-properties
which has:
ADAPTIVE_CRUISE_CONTROL_TARGET_TIME_GAP ADAPTIVE_CRUISE_CONTROL_LEAD_VEHICLE_DISTANCE
The Commercial Vehicle group came up with the proposed PR for VSS. Cruise Control and Emergency Braking Assist may share the sensor data if vehicle has both so we felt it appropriate to place some of this under ObjectDetection. While the time gap can be calculated based on distance and vehicle speed, we feel it should be defined and represented in VSS.
Nearby we also want to include blind spot detection, both left and right. Vehicle SAE ActiveAutonomyLevel less than 2 tend to merely indicate presence of a vehicle in blind spot, surely level 3 and greater keep track of distance. Instead of staging a proposed representation for left and right isWarning booleans and possibly distance, want to discuss on VSS call what a better future proof representation may be. There may be object (obstacle) presence and distance detection for multiple directions.
MoM:
- Please review
- Ted: This is just first contributions, we have other additions in pipe, future proof design of signals needed, like objects in blind sport. Input from OEMs wanted
- Stefan: I have seen some examples with "intention", like is pedestrian likely to cross the street or not
- Daniel: Modelling goes a bit beyond on what we can discuss here, we could possibly reuse info from https://www.asam.net/standards/asam-openxontology/
- Stephen: "feature complete" or work in progress. May need to have "concept" info that explains the intention of all small steps.
MoM:
- Ted informed that PR might be refactored
- Erik: If structs makes representation better we can consider that
MoM:
- Not to be part of 5.0
- Ted: We have identified some insurance/fleet signals, discussing how to progress
- Ted: Will create new PR replacing this one, input appreciated
- Ted: We have an insurance call where we discuss needed signals, feel free to join
Nearby discussions, proposals under discussion
https://github.com/COVESA/vehicle_signal_specification/issues/754 https://github.com/COVESA/vehicle_signal_specification/compare/master...StefanSellschopp:vehicle_signal_specification:master