ArduPilot / ArduPilot/MissionPlanner

Connect doesn't start until "Timeout in 7s"

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

When connecting to the drone, it is not until 23s after and the pop up window showing "Timeout in 7s" that we finally start receiving telemetry and downloading the params. It is systematically the same behavior, nothing happens before it shows "7s".

#### Version
1.3.68.1

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

#### Hardware type
PX4

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the connection flow in Mission Planner 1.3.68.1 with PX4 hardware, using the report's observation that telemetry and parameter downloads begin only when the "Timeout in 7s" popup appears. Compare the connection timing before and after that point; done means telemetry and parameters start without the reported 23-second delay.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.