ArduPilot EU Dev Call 2025-12-17

Attendees (unique): 6

UTC0702

Peter: We have attempted this in the past and it was hard to tackle.
Andrew: Left a review.

  • We did have a script that could trigger the issue.

UTC0708

George: I don’t like that this is integrated in TECS library.
A: It would be nice if we were able to run both controllers on a switch, depending on the flight stage. TECS for high-altitude flying, and the new one on low flying.

  • The autotest doesn’t work very nice yet. It’s hard to visualize the TECS altitude error.
  • We’ll have to test it a lot more before we accept it. We need experience testing it.

UTC0727

A: What is the impact on .bin logs? Are we going to be getting useful numbers?


UTC0728

P: Waiting for review of maintainers.


UTC0731

Merged!


UTC0735

P: Should we be asking for the FPGA code to be open-source?
A: It’s too one-off. Let’s not.
P: We have another partner who wants to use this sensor, but they won’t be able without the FIFO FPGA improvement.
A: We could merge it without the FIFO, but it will be very slow.
P: Flight logs seem OK, but they weren’t using it for flight. EK3_IMU_MASK doesn’t use it by default.
A: I’ve asked for a replay log.


UTC0748

Andy: We can look at this offline, Peter.
P: You can autotest with two Copter binaries at the same time, feeding the CRSF stream of one to the other, via the mcast network.


UTC0804

P: We need to keep pushing on differentiating “location” and “position” requirements.


UTC0815

P: Don’t upload the whole parameter file. Only the significant changes instead.


UTC0817

P: We don’t want to duplicate the altitude and frame deduction methods. It’s best to use what is available already.