ArduPilot / ArduPilot/MissionPlanner

Autopilot in HUD always stays unknown

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

#### Issue details
What Mavlink message (and what parameter) should be sent to MP to modify the autopilot field in the HUD?

#### Version
latest

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

#### Airframe type
fixed wing

#### Hardware type
custom Raspberry PI based FCC

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Plane HUD's autopilot field and trace how it interprets incoming MAVLink messages and parameters. Determine which message and parameter should provide the autopilot value, then verify that the HUD no longer displays Unknown for the reported Raspberry Pi-based Plane setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.