ArduPilot / ArduPilot/MissionPlanner
CAN UI issues
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
A few issues I've found with the CAN fw updater and UI:
- cancelling a CAN update fails (seems to keep waiting for a response)
- the BeginFirmwareUpdate needs to be retried (the AP_Periph fw relies on at least one retry)
- fetching parameters is very slow (seems to delay 0.3s between parameters, so with 90 parms takes 30s)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the CAN firmware updater and parameter-fetch flows in Mission Planner, focusing on cancellation, BeginFirmwareUpdate, and the apparent 0.3-second delay between parameters. Done means cancellation stops waiting, BeginFirmwareUpdate retries, and parameter fetching no longer incurs the reported delay.
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
- 25/100