Dev Call Nov 17 ,2025

Development Team
1

Release Update

Issues & Pull requests

CI Workflows

Discussion

Adding support for stm32 boards which will never be sold/generally available.

2

Attendee count (max): 18

UTC1101 - vehicle update

  • Release got stuck

    • CI not passing

    • The version is stuck in beta and Randy was trying to fix it

    • This might break the web tools

      • logs might get marked as “unofficial firmware”

    • Custom build server might have problems

      • Will it update its metadata correctly?

    • We’ll try it and see what breaks; might need to do a 4.6.4 if things do break

    • We will now have two firmware hashes which are 4.6.3

  • Unable to force 115200 on uBlox?

  • Internal error in landing controller

    • Leonard and Randy will look

UTC1111 - https://github.com/ArduPilot/ardupilot/pull/30842

  • H7 file log buffer improvements

UTC1116 - https://github.com/ArduPilot/ardupilot/pull/31405

  • LIS2MDL compass

  • This mess isn’t getting any better

  • Some naming requirements

  • Some reordering of probing in the internal/external probe

UTC1123 - https://github.com/ArduPilot/ardupilot/pull/31503

  • Small fixes and adjustments to prepare for upcoming NED conversion

  • Tricky and time-consuming

  • Removing fabsf on parameters?

    • Lazy when adding the parameter

    • These do now have a direction and magnitude

    • So formalising these so that things are unambiguous

  • The letters in these names (U or D) are really specifying an axis)

  • So e.g. set_max_speed_accel_U_m takes three arguments which are all speeds

  • Position controller is a NED controller (or will be)

  • Max_descent_speed / max_ascend_speed

  • Velmax down and velmax up are very bad - should be speed max down and speed max up

  • Real limits as to how much we can communicate in these method names

  • The letters are meaning different things in different functions

    • Sometimes it is specifying an axis, sometimes and axis and a direction

  • Some of these methods take an absolute value now

    • Some don’t and you have to pass the correct sign

    • E.g. set_correction_speed_U_m does fabsf

    • set_correction_speed_accel_U_m does not

    • “All values should be positive”

  • Potential behavioural change

    • Negative values in parameters might become ignored

  • Safe to say there’s going to be a bunch of people confused on the vertical axis signs

    • Arming checks required where we’re removing fabsf?

  • Fabsf in the vehicle code or in the library?

    • Leonard can add fabsf if desired

  • Peter suggested that commenting each caller to indicate that speeds and accels must be positive (and add fabsf if required)

  • Clarify variable names

  • Comments

  • Fabsf in callers

  • This one will be back

UTC1211 - https://github.com/ArduPilot/ardupilot/pull/31476

  • Fix blended problem where weights can be zero

  • Merged!

UTC1214 - https://github.com/ArduPilot/ardupilot/pull/30842

  • H7 log file buffer fix

  • Some discussion around the memory

  • Tridge is most concerned around DMA memory usage

  • SPI-based SD cards?

    • 32kB of DMA-capable memory will be slurped

UTC1226 - https://github.com/ArduPilot/ardupilot/pull/31492

  • Add more tests for Arc waypoints

  • Merged!

UTC1231 - https://github.com/ArduPilot/ardupilot/pull/31511

  • Rename airspeed methods to specify whether they are returning in EAS and TAS

  • Bugfix will be coming along tomorrow

  • Thomas will merge when he’s happy

UTC1237 - https://github.com/ArduPilot/ardupilot/pull/31534

  • Signal failure if not configured backends are enabled

  • Will make it a config error

UTC1243 - https://github.com/ArduPilot/ardupilot/pull/31537

  • Preflight reboot command handled by autopilot when it shouldn’t

    • When the component hasn’t been seen

  • Proposal is to change the router to not follow the routing spec and to reject messages to mav-compid-mission-planner and mav-comp-id-GPS

  • We would need an option bit to set it back to the original behaviour

  • Problems with UGCS

    • You can’t download a mission

    • Do-land-start doesn’t work

  • Potential breakage around remote-id and dataflash-over-mavlink

UTC1257 - CI roundup

  • Dead reckoning is back

  • Thomas is looking at the colcon stuff

UTC1258 - discussion around low-quality PRs adding boards

  • We’re getting many low-effort PRs

  • Heavy cost in terms of Henry and Andy

  • Ongoing maintenance costs for firmware server and updating PRs

  • Different classes of people involved

    • Genuine companies making products and want to get stuff into AP

      • If they can’t follow extensive instructions they should pay a consultant to do that

        • E.g. Henry or Andy

      • Some jobs are big, some are small

        • Consultants really should be hourly

    • Time-wasters

  • Can we say things need to be manufactured

  • LH thinks we should add a $ barrier for a board

  • Board drop policy?

  • If they are willing to pay a consultant then it might be OK

  • Junk ones are not welcome

  • Hard and fast rule?

UTC0019 - close