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

    MAVSDK running on another computer for HITL

    Ask your questions right here!
    3
    12
    781
    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.
    • K
      kerct @Zachary Lowell 0
      last edited by 6 Feb 2024, 09:34

      @Zachary-Lowell-0 I was trying the MAVSDK example which didn't work but after trying the example, I can't run HITL anymore (which worked previously)... not sure what's the issue here?

      9366dea7-4e64-4a39-9d27-c91ac223a206-image.png

      99b36e87-9f24-4f59-9387-87a6c4bccb02-image.png

      E 1 Reply Last reply 6 Feb 2024, 16:09 Reply Quote 0
      • E
        Eric Katzfey ModalAI Team @kerct
        last edited by 6 Feb 2024, 16:09

        @kerct If you power cycle the board does it do the same thing every time? It's acting like there is already code running on the DSP.

        K 2 Replies Last reply 7 Feb 2024, 01:31 Reply Quote 0
        • K
          kerct @Eric Katzfey
          last edited by 7 Feb 2024, 01:31

          @Eric-Katzfey Yes I still get the same error after power cycle

          1 Reply Last reply Reply Quote 0
          • K
            kerct @Eric Katzfey
            last edited by 7 Feb 2024, 03:05

            @Eric-Katzfey I'm also unable to connect to QGC now (without HITL). On VOXL portal I can still see the camera and pointclouds, but not the status of the drone.

            6fd26783-7309-4806-8e97-2be46d5a6973-image.png

            11db34e0-4c9a-4a38-b6cd-91f9fb7be2a9-image.png

            c856daa6-409a-4791-8759-c551cc293489-image.png

            9a66f134-b08e-4ded-8e30-e5aa118bb773-image.png

            E 2 Replies Last reply 7 Feb 2024, 16:01 Reply Quote 0
            • E
              Eric Katzfey ModalAI Team @kerct
              last edited by 7 Feb 2024, 16:01

              @kerct Can you use the SDK 1.1.2 installer to do a fresh install of the latest SDK (available here: https://developer.modalai.com/asset/2) and then see if the problem still exists?

              K 1 Reply Last reply 8 Feb 2024, 00:28 Reply Quote 0
              • E
                Eric Katzfey ModalAI Team @kerct
                last edited by 7 Feb 2024, 16:02

                @kerct I generally start by doing a fresh install. Then try to get HITL working with Gazebo without QGroundControl. Then add QGroundControl. And finally, when all of that seems to be working, add MAVSDK.

                1 Reply Last reply Reply Quote 0
                • K
                  kerct @Eric Katzfey
                  last edited by 8 Feb 2024, 00:28

                  @Eric-Katzfey will this work with SDK 1.0.0 too? would like to stick with that version for now since we have been testing with this version for our project

                  E 3 Replies Last reply 8 Feb 2024, 15:49 Reply Quote 0
                  • E
                    Eric Katzfey ModalAI Team @kerct
                    last edited by 8 Feb 2024, 15:49

                    @kerct We've many numerous improvements to HITL support since 1.0.0.

                    1 Reply Last reply Reply Quote 0
                    • E
                      Eric Katzfey ModalAI Team @kerct
                      last edited by 8 Feb 2024, 15:51

                      @kerct Perhaps you can try SDK 1.1.2 and just verify that you can get it all working the way that you want. That will at least rule out any issues coming from your environment. Then, if that all works fine, go back to 1.0.0 and see if you can determine which part is not working.

                      1 Reply Last reply Reply Quote 0
                      • E
                        Eric Katzfey ModalAI Team @kerct
                        last edited by 8 Feb 2024, 15:52

                        @kerct But I would strongly suggest moving to SDK 1.1.2. It's very hard for us to support customers using older SDK versions.

                        1 Reply Last reply Reply Quote 0
                        3 out of 12
                        • First post
                          3/12
                          Last post
                        Powered by NodeBB | Contributors