Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. General Questions
  3. Seeker offboard failsafe unexpected behavior and firmware update parameter issues.

Seeker offboard failsafe unexpected behavior and firmware update parameter issues.

Scheduled Pinned Locked Moved Unsolved General Questions
3 Posts 3 Posters 707 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • 張為超張 Offline
    張為超張 Offline
    張為超
    Contributor
    wrote on last edited by
    #1

    Hello team,

    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)

    In short:

    (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.

    Jeff

    Karrthik GkK 1 Reply Last reply
    0
    • 張為超張 張為超

      Hello team,

      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)

      In short:

      (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.

      Jeff

      Karrthik GkK Offline
      Karrthik GkK Offline
      Karrthik Gk
      wrote on last edited by
      #2

      @張為超 Hey
      We are facing the same issue with our drone
      Were you able to rectify this issue?

      tomT 1 Reply Last reply
      0
      • Karrthik GkK Karrthik Gk

        @張為超 Hey
        We are facing the same issue with our drone
        Were you able to rectify this issue?

        tomT Offline
        tomT Offline
        tom
        admin
        wrote on last edited by
        #3

        @Karrthik-Gk SDK 1.1.1 for voxl 1 includes PX4 v1.14 for flight core. I would recommend starting there

        1 Reply Last reply
        0

        Reading along? Create a free ModalAI Forum account to join in.

        With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.

        Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        ModalAI
        Categories Recent Tags ModalAI.com Docs
        © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups