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

ModalAI Forum

  1. ModalAI Support Forum
  2. Ask your questions right here!
  3. ESC Mini 4-in-1 M0129 is not controllable through QGC

ESC Mini 4-in-1 M0129 is not controllable through QGC

Scheduled Pinned Locked Moved Ask your questions right here!
7 Posts 3 Posters 1.1k 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.
  • W Offline
    W Offline
    will.huang.oksi
    Contributor
    wrote on last edited by
    #1

    To whom it may concern,

    My VOXL2 Flight Deck is currently running the following SDK version:
    voxl-sdk-version.png

    The ESC Mini 4-in-1 is using the following firmware version:
    voxl-esc_scan.png

    I am able to successfully spin the motors using the command:

    voxl-esc 3) spin
    

    However, I am unable to spin the motors in QGroundControl using the Actuator Testing feature.
    Could you advise if there are any steps I might have missed?
    motor_not_controlled_by_qgc.png

    ====

    Additionally, I have connected the VOXL2 to a QGC instance running on an Ubuntu machine within the same network.
    I noticed that the ESC PWM Minimum and Maximum Calibration in QGC requires a USB connection.
    must_use_usb_msg.png

    I attempted to connect the VOXL2 to the Ubuntu machine via the USB-C port labeled "U" in the VOXL2 datasheet, but it did not establish a connection.
    fe98b14d-3d05-4731-9761-be23e24279fa-image.png

    Could you clarify which port should be used for this USB connection to ensure proper calibration support in QGC?

    Thank you for your assistance and please let me know if you need more details.

    ModeratorM 1 Reply Last reply
    0
    • W will.huang.oksi

      To whom it may concern,

      My VOXL2 Flight Deck is currently running the following SDK version:
      voxl-sdk-version.png

      The ESC Mini 4-in-1 is using the following firmware version:
      voxl-esc_scan.png

      I am able to successfully spin the motors using the command:

      voxl-esc 3) spin
      

      However, I am unable to spin the motors in QGroundControl using the Actuator Testing feature.
      Could you advise if there are any steps I might have missed?
      motor_not_controlled_by_qgc.png

      ====

      Additionally, I have connected the VOXL2 to a QGC instance running on an Ubuntu machine within the same network.
      I noticed that the ESC PWM Minimum and Maximum Calibration in QGC requires a USB connection.
      must_use_usb_msg.png

      I attempted to connect the VOXL2 to the Ubuntu machine via the USB-C port labeled "U" in the VOXL2 datasheet, but it did not establish a connection.
      fe98b14d-3d05-4731-9761-be23e24279fa-image.png

      Could you clarify which port should be used for this USB connection to ensure proper calibration support in QGC?

      Thank you for your assistance and please let me know if you need more details.

      ModeratorM Offline
      ModeratorM Offline
      Moderator
      ModalAI Team
      wrote on last edited by Moderator
      #2

      @will-huang-oksi you should connect to QGC with a WiFi connection. The "U" USB-C port is for ADB, and not QGC

      Link Preview Image
      Connect to QGC

      ModalAI technical documentation for VOXL and VOXL 2 Companion Computers for PX4 and ArduPilot Obstacle Avoidance and GPS-denied navigation, assembled in the USA

      favicon

      ModalAI Technical Docs (docs.modalai.com)

      ETA: It looks like you're connected to QGC via the network already, so you can ignore the above. That message likely means that you can only perform the calibration via command line. Here are the calibration instructions

      ModeratorM 1 Reply Last reply
      0
      • ModeratorM Moderator

        @will-huang-oksi you should connect to QGC with a WiFi connection. The "U" USB-C port is for ADB, and not QGC

        Link Preview Image
        Connect to QGC

        ModalAI technical documentation for VOXL and VOXL 2 Companion Computers for PX4 and ArduPilot Obstacle Avoidance and GPS-denied navigation, assembled in the USA

        favicon

        ModalAI Technical Docs (docs.modalai.com)

        ETA: It looks like you're connected to QGC via the network already, so you can ignore the above. That message likely means that you can only perform the calibration via command line. Here are the calibration instructions

        ModeratorM Offline
        ModeratorM Offline
        Moderator
        ModalAI Team
        wrote on last edited by
        #3

        @Moderator We will ask about QGC configuration of the ESCs.

        Alex KushleyevA 1 Reply Last reply
        0
        • ModeratorM Moderator

          @Moderator We will ask about QGC configuration of the ESCs.

          Alex KushleyevA Offline
          Alex KushleyevA Offline
          Alex Kushleyev
          ModalAI Team
          wrote on last edited by Alex Kushleyev
          #4

          You most likely have a mismatch in uart baud rate in esc params (250K) and px4 params for voxl esc (2mbit). You should update your ESC params on the ESC to 2mbit (2000000). We recommend using the higher baud rate.

          Also, voxl esc does not require (or support) min and max pwm calibration.

          Alex

          W 1 Reply Last reply
          0
          • Alex KushleyevA Alex Kushleyev

            You most likely have a mismatch in uart baud rate in esc params (250K) and px4 params for voxl esc (2mbit). You should update your ESC params on the ESC to 2mbit (2000000). We recommend using the higher baud rate.

            Also, voxl esc does not require (or support) min and max pwm calibration.

            Alex

            W Offline
            W Offline
            will.huang.oksi
            Contributor
            wrote on last edited by will.huang.oksi
            #5

            Hello @Alex-Kushleyev and @Moderator ,
            Thank you for the response!!!

            As Alex pointed out, the baud rate seems to be the issue preventing the motors from spinning through the Actuator Testing feature in QGC. I have another ESC configured with a 2M baud rate, and it works as expected with Actuator Testing.

            My question now is: how can I update the baud rate on the ESC?

            In QGC, the baud rate is already set to 2M.

            DRONE_II_ESC_IN_QGC.png

            In https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/tree/master/voxl-esc-tools,
            I came across the command:

            ./voxl-esc-upload-params.py --params-file ../params/esc_params_modalai_4_in_1.xml
            

            However, I wasn’t able to locate this XML file on the VOXL.
            Here's what I found in the VOXL:

            32b065aa-1eaf-4c5d-900f-63205ff3c1cc-image.png

            In the repo I found is esc_params_modalai_4_in_1_revb_mn1804_2400kv_gemfan5040.xml
            Should I upload this xml to /usr/share/modalai/voxl-esc-params/boards/, rename it to esc_params_modalai_4_in_1.xml, and use the python command above?

            I also tried to manually change the baud rate to 2M in those XML files but it gets overwritten after a reboot.

            Could you please provide more detailed instructions on how to properly update the ESC baud rate?

            Thank you.

            Alex KushleyevA 1 Reply Last reply
            0
            • W will.huang.oksi

              Hello @Alex-Kushleyev and @Moderator ,
              Thank you for the response!!!

              As Alex pointed out, the baud rate seems to be the issue preventing the motors from spinning through the Actuator Testing feature in QGC. I have another ESC configured with a 2M baud rate, and it works as expected with Actuator Testing.

              My question now is: how can I update the baud rate on the ESC?

              In QGC, the baud rate is already set to 2M.

              DRONE_II_ESC_IN_QGC.png

              In https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/tree/master/voxl-esc-tools,
              I came across the command:

              ./voxl-esc-upload-params.py --params-file ../params/esc_params_modalai_4_in_1.xml
              

              However, I wasn’t able to locate this XML file on the VOXL.
              Here's what I found in the VOXL:

              32b065aa-1eaf-4c5d-900f-63205ff3c1cc-image.png

              In the repo I found is esc_params_modalai_4_in_1_revb_mn1804_2400kv_gemfan5040.xml
              Should I upload this xml to /usr/share/modalai/voxl-esc-params/boards/, rename it to esc_params_modalai_4_in_1.xml, and use the python command above?

              I also tried to manually change the baud rate to 2M in those XML files but it gets overwritten after a reboot.

              Could you please provide more detailed instructions on how to properly update the ESC baud rate?

              Thank you.

              Alex KushleyevA Offline
              Alex KushleyevA Offline
              Alex Kushleyev
              ModalAI Team
              wrote on last edited by
              #6

              @will-huang-oksi ,

              You should probably review our Frequently Asked Questions section for the ESCs : https://docs.modalai.com/voxl-escs/faq/

              Additionally, you probably need to calibrate your ESC for the motor / propeller that you are using. Note this is different from the PWM range calibration for pwm-style ESCs. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md

              The calibration document also tells you how to upload the params file. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md?ref_type=heads#update-and-upload-calibration-file (you just need to provide the full path to the param file, wherever on voxl it is stored).

              You found the correct command for uploading params, however your original question is about which param file to use as the starting point before changing the baud rate (so let me answer that). Well, you should first figure out which ESC param file your other ESC is using (which has 2mbit as communication rate). You can check which param file is loaded to your ESC by running the following command from /usr/share/modalai/voxl-esc-tools:

              ./voxl-esc-verify-params.py
              

              This command will download the params from each of the 4 ESCs and will look for a parameter match in files located in /usr/share/modalai/voxl-esc-params. The script will tell you which param file the ESC params are matching. Then you could simply create a copy of that param file, change the baud rate to 2mbit and upload it to the ESC. This will effectively only change the baud rate and leave the other ESC params the same.

              However, it seems that you may end up with different ESCs with different param files, because your other ESC is already running at 2mbit. It is important to make sure that you know which ESC params you are using, otherwise the ESC performance will not be the same across different ESC boards. If you never calibrated the ESC for your motor / propeller, it is strongly suggested, because PX4 uses RPM-based control with ModalAI ESCs and if the ESC is not calibration, it will not perform optimally.

              Alex

              W 1 Reply Last reply
              0
              • Alex KushleyevA Alex Kushleyev

                @will-huang-oksi ,

                You should probably review our Frequently Asked Questions section for the ESCs : https://docs.modalai.com/voxl-escs/faq/

                Additionally, you probably need to calibrate your ESC for the motor / propeller that you are using. Note this is different from the PWM range calibration for pwm-style ESCs. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md

                The calibration document also tells you how to upload the params file. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md?ref_type=heads#update-and-upload-calibration-file (you just need to provide the full path to the param file, wherever on voxl it is stored).

                You found the correct command for uploading params, however your original question is about which param file to use as the starting point before changing the baud rate (so let me answer that). Well, you should first figure out which ESC param file your other ESC is using (which has 2mbit as communication rate). You can check which param file is loaded to your ESC by running the following command from /usr/share/modalai/voxl-esc-tools:

                ./voxl-esc-verify-params.py
                

                This command will download the params from each of the 4 ESCs and will look for a parameter match in files located in /usr/share/modalai/voxl-esc-params. The script will tell you which param file the ESC params are matching. Then you could simply create a copy of that param file, change the baud rate to 2mbit and upload it to the ESC. This will effectively only change the baud rate and leave the other ESC params the same.

                However, it seems that you may end up with different ESCs with different param files, because your other ESC is already running at 2mbit. It is important to make sure that you know which ESC params you are using, otherwise the ESC performance will not be the same across different ESC boards. If you never calibrated the ESC for your motor / propeller, it is strongly suggested, because PX4 uses RPM-based control with ModalAI ESCs and if the ESC is not calibration, it will not perform optimally.

                Alex

                W Offline
                W Offline
                will.huang.oksi
                Contributor
                wrote on last edited by
                #7

                @Alex-Kushleyev
                Thank you so much for the detailed explanation!
                I will keep you posted with the update shortly.

                1 Reply Last reply
                0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                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