ArduPilot / ArduPilot/MissionPlanner
Delay at WP set by user in Grid ignored in Waypoint list, time calculation
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
This applies to ArduCopter: If a user constructs a flight plan using the Grid functionality, there is a field to enter a delay at each waypoint. This value never makes it into the flight plan; all WAYPOINT entries have zero for the delay parameter. Also, the total flight time calculation does not take these delays into account. Even if the delay times are only added as a first approximation (i.e. no acceleration/deceleration at the waypoint), it would be useful to have this factored in.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by tracing how the Grid flight-plan UI creates WAYPOINT entries and how total flight time is calculated; verify where the user-entered delay is lost. Done means waypoint delays are preserved and included in the total-time calculation, including an initial approximation without acceleration or deceleration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100