ArduPilot / ArduPilot/MissionPlanner

Copter-4.0 updates to extended tuning screen

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

Description

As part of the Copter-4.0 beta testing, we've noticed that a few fields on the Extended tuning page are blanked out because we've changed parameter names.

![mp-extended-tuning-blank](https://user-images.githubusercontent.com/1498098/68100223-2f4f6900-ff0a-11e9-8c22-a96aa77dc028.png)

The TUNE_ parameters should be TUNE_MIN and TUNE_MAX (was TUNE_LOW, TUNE_HIGH)

For the Filters the single parameter for each axis has been replaced with 3 filters. So _FILT -> FLTE, FLTD and/or FLTT. After a discussion with @lthall we think it would be best if all three were shown.

@lthall is going to come up with some more input for this screen.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Extended tuning page and its existing parameter mappings. Check the TUNE_ and filter entries described in the issue; done means TUNE_MIN and TUNE_MAX display correctly and all three axis filter parameters—FLTE, FLTD, and FLTT—are shown.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.