ArduPilot / ArduPilot/MissionPlanner
WP_RADIUS does not save in Flight Plan screen.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
Issue details
On the Flight Plan screen, if one changes the WP Radius, then leave the screen and return, WP Radius reverts to the previous value. And parameter WP_RADIUS does not change.
Only if the actual parameter is changed in the Full Parameter List does the WP Radius value change stick on the Flight Plan screen
Version
V1.3.56
Platform
[ ] All
[ ] AntennaTracker
[X] Copter
[X] Plane
[ ] Rover
[ ] Sub
Airframe type
Twin boom plane
Hardware type
AUAV-X2 & Pixhawk
Logs
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the Mission Planner Flight Plan screen on a Copter or Plane setup: change WP Radius, leave and return, then compare it with the Full Parameter List. Trace the Flight Plan screen's WP Radius handling and parameter update path. Done means changing WP Radius updates WP_RADIUS and the value remains after leaving and returning to the screen.
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
- 35/100