ArduPilot / ArduPilot/MissionPlanner

2 OverShoot values, but only 1 LeadIn value ??

Open
#2,368 2 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

#### Issue details
In MP there are two OverShoot values, one for each end of the survey grid. This is great. However, there is only one LeadIn value so this applies to both ends of the grid.

In windy conditions with a fixed wing it may be necessary to go a long distance up wind to allow sufficient distance to turn around before re-entering the survey area. Conversely down wind there may not need to be very much distance at all to turn around. It wastes a lot of time having to travel the same distance down wind due to the single LeadIn value.

To get the best turn performance this needs both OverShoot and LeadIn.

Please consider splitting LeadIn in to two values, one for each end of the survey grid, just like OverShoot.

Thank you.

#### Version
1.3.70 currently but it has the same for a long, long time.

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

#### Airframe type
Mainly fixed wing but should not be aircraft specific

#### Hardware type
n/a

#### Logs
n/a

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is identified in the issue. Start by locating the Mission Planner handling for the survey-grid LeadIn and OverShoot values, then determine how separate upwind and downwind LeadIn settings should be represented and applied for fixed-wing grids.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.