ArduPilot/MethodicConfigurator

Is there an existing issue or pull request for this? I have searched the existing issues and pull requests Feature description Add support for firmware upload @iacker would you like to take a shot at this? Desired solution Firmware Upload Architecture Overview This feature allows a user to select an ArduPilot firmware image, validate it against the connected flight controller, flash it through the board bootloader, and reconnect to verify the result. The feature follows the project separation described in ARCHITECTURE.md: backend_flight_controller_firmware_upload.py is the I/O adapter. It owns serial ports, MAVLink bootloader-entry/reboot commands, the ArduPilot bootloader protocol, firmware file reading, and progress events. data_model_firmware_upload.py is the business/domain model. It owns firmware metadata, board compatibility, validation, workflow state, and user-facing error classifications. It does not open files, access serial ports, use Tkinter, or talk directly to the fli

Is there an existing issue for this? I have searched the existing issues Description of the bug Our CI automated regression test suite code coverage has dropped below 90% Previously it was 95% but lately we have added so much new code that the tests are lagging behind. Steps To Reproduce Look at the pytest coverage reports: pytest --cov=ardupilot_methodic_configurator --cov-report=term-missing Much of the code in the plugins and log_analysis directories is WIP and can lag for now. But the code coverage in the ardupilot_methodic_configurator directory should be above 95% on all files. @iacker @yashhzd can you help? There is a skill that should help a lot: .github/skills/pytest-testing/SKILL.md Expected behavior Coverage of the files in the ardupilot_methodic_configurator should be above 95% Screenshots / Logs No response Software information Operating system: All arduPilot Methodic Configuration version: latest Additional context No response

Is there an existing issue or pull request for this? I have searched the existing issues and pull requests Feature description Just like the code contains a battery monitor plugin and a motor test plugin, create a RC calibration plugin that calibrates the RC controller stick ranges values. Work on this already started in #1816 (merged) so create a new PR/branch to continue working on it. Desired solution It has a GUI similar to Mission planner or to MicoConfigurator > settings > RC input Alternatives considered Use MP or MicoConfigurator directly Additional context No response

Is there an existing issue or pull request for this? I have searched the existing issues and pull requests Feature description Support python 3.15 version. Desired solution It should be tested against python 3.15 release and use python 3.15 instead of python 3.14 Just search the entire codebase for "3.14" and either replace it with 3.15 or add 3.15 to it Alternatives considered Wait longer before it is officially released. But it is easy enough to integrate and test it already as it is in beta2 cycle. Additional context No response