ArduPilot EU Dev Call 2026-11-04

Attendees (unique): 8

UTC0707

Andrew: It adds a lot of error messages pre-flight.
Peter: It looks like it’s blocking spoolup.
A: Some ESCs report error rates as % and some don’t?

  • Let’s leave it for later.

UTC0718

Merged!


UTC0720

A: Wny not switch into FBWA and glide instead?
George: I think it was because there were some bugs with FBWA behaving strangely in absence of RC.
A: Ah, it seems to be in response to a report from Henry.

Approved!


UTC0728

Andy: Upon lane switch, OF seemed to have timed-out. As a result, the new lane thought it was not moving, which made it not correct for motion at all.
Randy: When we do a reset we grab the latest sensor value. Resetting a sensor to 0 is not correct.
A: This PR could make things worse by overcorrecting the flow direction, if the reset happens during a turn.Better to use the latest, noisy reading, rather than the old reading.
Andy: Yes, I think you might be right.

  • Someone said that we should be averaging OF readings, rather than subsampling.

A: That might be correct. But we need to be careful to accumulate in the Earth frame, not in the Body frame, so we need to do a transformation for each sample.


UTC0743

A: What is 10e-5 about?
Sid: Yes, the number format is very weird.

  • Do we need to append .f in the float constants?

A: No, with the current compiler settings it does not make a difference.

  • Can you ask uBlox how we can scan for the features updated by a module?
  • Scanning strings is a crappy way to go about it.

S: Yes, I can ask.

A: We should probably stop parsing the old message, now that we have new parameters reporting.
S: We can set the message rate to 0.
A: Is it possible to have two X20s, one with a dual antenna and one without? So that we can have GPS for yaw but also GNSS redundancy.
S: I think it should work.

Okay to merge on AI Review.


UTC0753

S: We have had cubes with failling baro0 or baro1.

  • I found that PROM was getting corrupted, with failling CRC.
  • We get a low frequency of these failures, but they are accumulating.
  • This results in board validation error and failure to boot.
  • The manufacturer is aware of this issue.
  • If you don’t properly power down below 0.1V and then power up again, the PROM can get corrupted.
  • They recommend to store the PROM elsewhere and use it from there.

A: That’s a pretty crappy recommendation.

  • Have you found a way to resurrect the baro by writing to the PROM?

S: No, that’s a one-time write.

  • I recommend that we store the PROM into memory. Bootloader isn’t an option and the parameter space is user-writable, so some other place in FRAM could do.

A: But that would have us keep track of that memory space. I don’t like that.

  • I would find it acceptable to ignore this baro and use the other.
  • What type of user would want to continue with a failed baro?

S: I can’t name them, but they need to keep on flying.
A: We can have an option bit that allows you to boot with one bad baro.

  • Existing users can’t benefit from this PR anyways.

S: We do have that board option in master.
A: There you have it!
S: It would still be nice to be able to keep using that baro.


UTC0829

Merged!

A: What effect did this have? Do we need to backport it?

  • It would break the effect of the *MAG_MASK parameter.
  • But no-one ever uses this parameter.
    P: We’ve had this since 2020.
    A: And it’s in EKF2 as well.
    P: Yes, I’m opening a PR.

UTC0837

P: Please refactor our loiter and reuse it.


UTC0840

A: It’s ugly, but we might need to accept it.

  • Otherwise we’d need to change the lwip submodule.

P: We should compile regardless of optimization level.
A: But once you go to high optimization levels it’s hard to get no warnings.

Merged!


UTC0845

A: Okay, let’s approve it.


UTC0851

A: This has the potential to break existing boards with another sensor variant.

  • Upon review, it’s not zero-risk for existing boards, but it’s not high risk.
  • We do have the space for it.

Approved!


UTC0900

End