I have a seeker with px4 firmware 1.11 and a M500 with firmware 1.13. We found that our seeker will switch into Altitude mode instead of Position mode when Offboard failsafe activates however our M500 does not (both had their COM_OBL_RC_ACT set to position). Our guess is the px4-fimware cause this problem, so we upgrade the px4 firmware to 1.13 for our seeker. And indeed once the firmware has been updated to 1.13, activating Offboard failsafe will switch seeker into position mode as expected.
However, after we update the seeker to 1.13 (either using the "modalai_fc_v1_default.px4" downloaded from the px4 github releases (we've also tried 1.13.3, 1.13.2, 1.13.0) or using QGC), loading parameters from either files (https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/platforms/v1.13/Seeker) will result in writing parameter fail for UART_ESC_XXX (and a couple more) because these parameters does not exits for the firmware. We suspect this is the reason for seeker not able to arm after the upgrade.(By not able to arm we mean we can send arm command through QGC and QGC will show "armed" but actually the motor is not responding)
(1) Why with FCv1 - v1.11.3-0.2.3, activating Offboard failsafe will switch seeker into altitude mode even with COM_OBL_RC_ACT set to position? (While with 1.13 activating Offboard failsafe it will switch to position as expected).
(2) How can we successfully load the parameters from https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/tree/master/platforms/v1.13/Seeker after update the firmware to 1.13 using QGC or .px4 files downloaded from https://github.com/PX4/PX4-Autopilot/releases?
(3) Or, could seeker not arming after updated to 1.13 actually caused by some other problem?
thanks in advance for your time and assistance.