ArduPilot / ArduPilot/MissionPlanner

Interface Issues

Open
#3,342 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2.4k
Forks
2.9k
Avg merge
19h 16m
Merged PRs (30d)
4

Description

[ ] A few months ago Randy, myself and others agreed that the "BASIC" and ADVANCE parameter tabs should be removed and requested it....the parameters have not been diligently maintained with these designations for a long time and just are not needed
[ ] The new Plane parameters need to be added in the Plane Tuning window which still shows only the old params
[ ] Since we have many many autopilots now that usually use Betaflight when they migrate to Ardupilot, we need to add the BetaflightX and Xreversed as selectable options in the Frame type dialog in SETUP to assist these new AP users get setup

#### Platform
[X ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Sub

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the Plane Tuning window and the Frame type dialog in the Mission Planner UI, then inspect how the parameter tabs and selectable frame types are populated. Done means removing the BASIC and ADVANCE tabs, showing the new Plane parameters, and adding BetaflightX and Xreversed as frame type options.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.