ArduPilot EU Dev Call 2026-02-11

Attendees (unique): 7

UTC0700

Peter: We do have an existing pattern to write an invalid value when the status of the lidar measurement is invalid.
Andy: Tridge wanted to send the last valid value.
Andrew: For out-of-range-close, we don’t do that.

  • I would prefer we were sending the last valid value, or the current value and have the front-end manipulate it.

A: Needs testing. You can use the frame quad-can to test it, it has a simulated CAN rangefinder.


UTC0715

P: I am concerned that if we land on a mountain, reboot and set the origin there, we won’t be able to take off again because it will be violating the lower fence threshod. Because it will be too high above Home.

  • I’ll write a test for it.

UTC0723

A: We have a filter library, which could be looking for too great differences.

  • We could try the register twice, provided they don’t get cleared after each read.

G: The problem could be electrical.
A: Most likely, but it wil be common, so we can do our best on our end as well.


UTC0732

Merged!


UTC0734

Merged!


UTC0737

Merged!


UTC0739

Merged!


UTC0740

A: Let’s hold off for Randy to have a say.


UTC0743

Merged!


UTC0745

Merged!


UTC0746

Merged!

1 Like

I would rather have the measured value as it may be of use to a script or for log analysis. Eg rangefinder that works reliably up to 15m but can provide data up to 25m if the conditions are right.