Mark Sauder

Fix up the conflicts and maybe rebase. After that it should be good to go! -Mark

Hi @xinnad . I finally got back to collapsing the buffer zone checks to remove the duplicate dm reads and have no clue why I didn't see things this way...

Rebased into a single commit.

Thanks @hamishwillee ! > Does the buffer apply to mission geofence, failsafe geofence, or both? FMI does the failsafe action in https://docs.px4.io/main/en/config/safety.html#geofence-failsafe apply to both mission and failsafe geofences. Yes,...

Hi @beat, I apologize, I accidentally pushed to your branch while thinking I was updating #20164. I've reverted my mistake. This PR looks good to me so far. I'll be...

Flight tested checking geofence behaviors and mode changes here: https://review.px4.io/plot_app?log=fb5dc914-1d7b-479f-816e-9b054fd2a8e7

Hi @RomanBapst , I'm happy to re-open PR #19112 if it is useful in accomplishing what has been discussed here, . It accomplishes the graphic @NAmmann posted.

Thanks @coderkalyan ! I was just working on submitting this as well!

fmu-v2 is over flash but I've bench tested this and everything is fine on a pixhawk4 mini and pixhawk4, but I don't have any uavcan devices to validate hardware with.

This PR allows building firmware with Python 3.10, the version shipped with Ubuntu 22.04.