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

    FC v2 Collision prevention issue with voxl 2

    Ask your questions right here!
    3
    12
    105
    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.
    • Jetson NanoJ
      Jetson Nano
      last edited by

      @Eric-Katzfey @Alex-Kushleyev

      I have the ark flow MR attached to the FC. While I want to check the standard builds, the standard build do not have UAVCAN modules enabled. i have to enable them manually.

      If anyone could share the built px4 file for the ModalAi FC v2 along with UAVCAN enabled and collision prevention working, It would mean alot.

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

        @Jetson-Nano Can you open the question about UAVCAN in a separate post? It has nothing to do with the initial question and we like each separate issue to have it's own posting / title. Thanks!

        Jetson NanoJ 1 Reply Last reply Reply Quote 0
        • Jetson NanoJ
          Jetson Nano @Eric Katzfey
          last edited by

          @Eric-Katzfey I will do that.

          1 Reply Last reply Reply Quote 0
          • S
            Sean Hickey @Jetson Nano
            last edited by

            @Jetson-Nano

            Looking through the PX4 codebase, the ARK Flow MR publishes to distance_sensor by default, not obstacle_distance. Have you made any changes to the codebase that would affect obstacle_distance or mounted any other sensors?

            Also, how have you mounted the ark_flow_mr. Is it pointing downwards on the vehicle, or forward pointing or some other configuration?

            Finally, have you tried setting the distance for collision prevention higher, and seeing how the drone reacts in that case?

            Jetson NanoJ 1 Reply Last reply Reply Quote 0
            • Jetson NanoJ
              Jetson Nano @Sean Hickey
              last edited by

              @Sean-Hickey I am using the optical flow sensor for position hold, it is attached directly to the FC.

              I am getting the obstacle_distance messages from the TOF sensor and I am able to see it.
              I did check with 1 m cp_dist and it was not working.

              S 1 Reply Last reply Reply Quote 0
              • S
                Sean Hickey @Jetson Nano
                last edited by

                @Jetson-Nano

                What TOF sensor are you using for obstacle distance?

                Just confirming, you are using the ARK Flow MR facing downwards just for optical flow and position hold, but not for collision prevention?

                Jetson NanoJ 1 Reply Last reply Reply Quote 0
                • Jetson NanoJ
                  Jetson Nano @Sean Hickey
                  last edited by

                  @Sean-Hickey PMD tof that comes with yellow board M0173 - https://docs.modalai.com/M0173/

                  Yes optical flow is facing down, it is used for position hold and not for collision prevention.

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    Sean Hickey @Jetson Nano
                    last edited by

                    @Jetson-Nano

                    Can you see if you are using the MO169 or the MO178?

                    Jetson NanoJ 1 Reply Last reply Reply Quote 0
                    • Jetson NanoJ
                      Jetson Nano @Sean Hickey
                      last edited by

                      @Sean-Hickey I am using M0178

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        Sean Hickey @Jetson Nano
                        last edited by Sean Hickey

                        @Jetson-Nano

                        I was able to identify the issue.

                        mpc_pos_mode - acceleration based doesn't call Collision Prevention in any of the newest PX4 builds..

                        You need to use mpc_pos_mode - Simple Position Control (0) or mpc_pos_mode - smooth position control (3).

                        I was able to test this on a similar setup, and confirmed that collision prevention only worked with the mpc_pos_mode indicated above, and notably did not with mpc_pos_mode acceleration.

                        Jetson NanoJ 1 Reply Last reply Reply Quote 0
                        • Jetson NanoJ
                          Jetson Nano @Sean Hickey
                          last edited by

                          @Sean-Hickey that great, just making sure, did you use optical flow with FC?

                          Also could you let me know which branch you used, or the Px4 built file. i want to test it out in my setup.

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