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

    Vio low frequency in Qgroundcontrol/ rc slow response

    Sentinel
    3
    9
    485
    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.
    • S
      stevedan
      last edited by

      @Eric-Katzfey Maybe you can help me fixed but the vio result on Qgroundcontrol is streaming at 1hz, and the reaction speed of the remote control on Qgroundcontrol is really bad. It reacts slow, is there something I am doing wrong
      da55f918-135a-4636-a2b4-8bfb0f634445-image.png

      What is strange is that from the drone, the vio data ms is fine voxl2:~$ voxl-inspect-qvio
      waiting for server

      dt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| error_codes |
      29.3 | -0.00 -0.00 -0.00| -0.0 0.0 0.0| 28 | 27% | OKAY |

      This is a video of what I mean-> https://drive.google.com/drive/folders/122cPZ1S3Z_gP0yo8nipRGJHqpJTSj9c3?usp=sharing

      Eric KatzfeyE 1 Reply Last reply Reply Quote 0
      • Eric KatzfeyE
        Eric Katzfey ModalAI Team @stevedan
        last edited by

        @stevedan Is this with original code or with the new code I just provided?

        S 2 Replies Last reply Reply Quote 0
        • S
          stevedan @Eric Katzfey
          last edited by

          @Eric-Katzfey with the new code. I just calibrated and followed the steps on the sentinel integration page.

          1 Reply Last reply Reply Quote 0
          • S
            stevedan @Eric Katzfey
            last edited by

            @Eric-Katzfey i used the software binding for the rc and setup the voxl px4 vision hub as usual.

            1 Reply Last reply Reply Quote 0
            • James StrawsonJ
              James Strawson ModalAI Team
              last edited by

              @stevedan

              That's correct. QGC gets a low data rate stream for telemetry only, devices onboard VOXL can access much higher data rates without the wireless link bottleneck.

              The "normal" telemetry mavlink data rates are defined by PX4 here:
              https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1490

              The faster "onboard" data rates are defined here:
              https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/mavlink_main.cpp#L1545

              From a VOXL shell, you can use the new voxl-inspect-mavlink tool to see the actual data rates being sent by PX4.

              voxl-inspect-mavlink mavlink_to_gcs
              voxl-inspect-mavlink mavlink_onboard
              

              Note, the configuration for the mavlink-to-gcs broadcaster lives here
              https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/voxl2/target/voxl-px4-start#L191

              S 2 Replies Last reply Reply Quote 0
              • S
                stevedan @James Strawson
                last edited by stevedan

                @James-Strawson, is this documented somewhere because this change is different from the previous versions and it might seem like a problem when it isn't. I will fly the drone on Tuesday and give update on this.

                1 Reply Last reply Reply Quote 0
                • S
                  stevedan @James Strawson
                  last edited by

                  @James-Strawson Is it possible to modify this rates?

                  Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                  • Eric KatzfeyE
                    Eric Katzfey ModalAI Team @stevedan
                    last edited by

                    @stevedan The mavlink rates are all configured in /usr/bin/voxl-px4-start. Look at the end of that file. You can change it to whatever you like.

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      stevedan @Eric Katzfey
                      last edited by

                      @Eric-Katzfey Thanks, problem solved.

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