Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ObstacleDetection instances, attributes and Adaptive CruiseControl #780

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions spec/ADAS/ADAS.vspec
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,17 @@ CruiseControl.IsError:
type: sensor
description: Indicates if cruise control system incurred an error condition. True = Error. False = No Error.

CruiseControl.IsAdaptive:
datatype: boolean
type: actuator
description: Indicates if cruise control system is adaptive (i.e. actively controls speed).

CruiseControl.AdaptiveDistanceSet:
datatype: float
type: actuator
unit: m
description: Distance in meters to keep from lead vehicle

#
# Lane Departure Detection System
#
Expand Down Expand Up @@ -113,6 +124,9 @@ LaneDepartureDetection.IsError:
#
ObstacleDetection:
type: branch
instances:
- ["Front", "Rear"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need the instances also for the existing signals like IsEnabled, IsWarning and so on? If not we could split to two branches, one called ObstacleDetection (without instances) and one called Obstacles (with instances)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Each ObstacleDetection sensor could throw a separate warning, be disabled independently etc,

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previous conversation before considering instances approach

#770

- ["Left", "Center", "Right"]
description: Signals form Obstacle Sensor System.

ObstacleDetection.IsEnabled:
Expand All @@ -131,6 +145,28 @@ ObstacleDetection.IsError:
type: sensor
description: Indicates if obstacle sensor system incurred an error condition. True = Error. False = No Error.

ObstacleDetection.Distance:
datatype: float
type: sensor
unit: m
description: Distance in meters to detected object
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can never be negative, or?

And distance is distance from the specified "zone". I.e. an object just in front of the front number plate may be reported with distance==0.01 meter by Front.Center, but with distance==0.80 meter by Front.Right?


ObstacleDetection.TimeGap:
datatype: int32
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Has negative number a meaning, or would uint32 suffice?
Has this one and Distance only significance if ObstacleDetection.IsWarning is True, or what values should be used if there is no obstacle?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unsigned is fine but wanted decimal instead of rounding to full integer.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If no meaning - shall we use uint32, i.e. up to 65 seconds?

type: sensor
unit: ms
description: Time in milliseconds before potential impact object

ObstacleDetection.WarningType:
datatype: string
type: sensor
allowed: [
'UNDEFINED', # Object detection warning not further categorized
'CROSS_TRAFFIC', # Detected object is on an indirect trajectory that may intersect
'BLIND_SPOT', # Detected object may not be in driver line of sight, including from mirrors
]
description: Indicates the type of obstacle warning detected as some track not only the presence of an obstacle but potential intercepting trajectory or other characteristics.
comment: Undefined obstacle warning type would merely alert of presence of obstacle and may measure distance.

#
# Antilock Braking System
Expand Down
Loading