ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    m500 VOXL Flight sdk update to v1.1.x

    VOXL SDK
    4
    26
    641
    Loading More Posts
    • 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.
    • Darshit DesaiD
      Darshit Desai @Darshit Desai
      last edited by Darshit Desai

      @tom On the next reboot it's showing esc failure in the logs

      [13:38:12.651] Info: Kill-switch engaged
      [13:38:13.768] Info: Kill-switch disengaged
      [13:39:33.963] Info: Armed by RC
      [13:39:34.096] Info: logging: opening log file sess114/log100.ulg
      [13:39:34.296] Critical: Failsafe activated, triggering disarm
      ESC failure
      [13:39:34.296] Info: Disarmed by failsafe
      [13:39:36.780] Info: Armed by RC
      [13:39:36.781] Info: logging: opening log file sess114/log101.ulg
      [13:39:37.131] Critical: Failsafe activated, triggering disarm
      [13:39:37.131] Info: Disarmed by failsafe
      [13:39:39.424] Info: Armed by RC
      [13:39:39.465] Info: logging: opening log file sess114/log102.ulg
      [13:39:39.787] Critical: Failsafe activated, triggering disarm
      [13:39:39.787] Info: Disarmed by failsafe

      And the motors try to spin up for a few seconds when arming and then instantly stop

      When I move this sliders now the motors rotate but when I try to arm the drone using RC it shows the ESC failure error

      a646b685-77d0-4ba3-8d65-72af8e7870ae-image.png

      tomT 1 Reply Last reply Reply Quote 0
      • Darshit DesaiD Darshit Desai referenced this topic on
      • tomT
        tom admin @Darshit Desai
        last edited by

        @Darshit-Desai If you upload the px4 log someone on our team can analyze it

        Darshit DesaiD 1 Reply Last reply Reply Quote 0
        • Darshit DesaiD
          Darshit Desai @tom
          last edited by Darshit Desai

          @tom By px4 log you mean the one mentioned in the post earlier, How can I access the log file which is mentioned here in the QGC log?

          @Darshit-Desai said in m500 VOXL Flight sdk update to v1.1.x:

          [13:38:12.651] Info: Kill-switch engaged
          [13:38:13.768] Info: Kill-switch disengaged
          [13:39:33.963] Info: Armed by RC
          [13:39:34.096] Info: logging: opening log file sess114/log100.ulg
          [13:39:34.296] Critical: Failsafe activated, triggering disarm
          ESC failure
          [13:39:34.296] Info: Disarmed by failsafe
          [13:39:36.780] Info: Armed by RC
          [13:39:36.781] Info: logging: opening log file sess114/log101.ulg
          [13:39:37.131] Critical: Failsafe activated, triggering disarm
          [13:39:37.131] Info: Disarmed by failsafe
          [13:39:39.424] Info: Armed by RC
          [13:39:39.465] Info: logging: opening log file sess114/log102.ulg
          [13:39:39.787] Critical: Failsafe activated, triggering disarm
          [13:39:39.787] Info: Disarmed by failsafe

          tomT 1 Reply Last reply Reply Quote 0
          • tomT
            tom admin @Darshit Desai
            last edited by

            @Darshit-Desai The logs can be downloaded through QGroundControl: https://docs.px4.io/v1.11/en/getting_started/flight_reporting.html#downloading-logs-from-the-flight-controller

            Darshit DesaiD 1 Reply Last reply Reply Quote 0
            • Darshit DesaiD
              Darshit Desai @tom
              last edited by

              @tom Here's the ulog file link,

              https://drive.google.com/file/d/1vuy_Ut0h_rEZDWseDgeywE093CISo9RB/view?usp=sharing

              C Darshit DesaiD 2 Replies Last reply Reply Quote 0
              • C
                coreyazion @Darshit Desai
                last edited by

                @Darshit-Desai Our m500 also showed something needed to be done with the acutator after updgrade to 1.14. But after loading the parameters (assuming you are using fcv2) and then reboot and it is okay.

                p.s. I vaguely rember having to do "loading parameters and rebooting" twice to get everything done. But I'm not very sure about this just I have this impression.

                Darshit DesaiD 1 Reply Last reply Reply Quote 0
                • Darshit DesaiD
                  Darshit Desai @coreyazion
                  last edited by

                  @coreyazion @tom This didn't work for me, although the drone esc and the drone functionality overall does work on an older sdk and flight core params, so its the newer version that's causing bugs for me

                  Darshit DesaiD 1 Reply Last reply Reply Quote 0
                  • Darshit DesaiD
                    Darshit Desai @Darshit Desai
                    last edited by

                    @tom any updates on this?

                    1 Reply Last reply Reply Quote 0
                    • Darshit DesaiD
                      Darshit Desai @Darshit Desai
                      last edited by

                      @tom any update on this?

                      ModeratorM 1 Reply Last reply Reply Quote 0
                      • ModeratorM
                        Moderator Dev Team @Darshit Desai
                        last edited by

                        @Darshit-Desai Can you try the v1.13 PX4 for the Flight Core? https://docs.modalai.com/flight-core-v2-firmware/

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Powered by NodeBB | Contributors