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

    Seeker connection to QGC

    Ask your questions right here!
    2
    20
    770
    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.
    • P
      Pooyan
      last edited by

      Hello everyone,

      Till now, I could get connected to QGC using wi-fi. I just enabled the GPS from the QGC and reboot the seeker there, and suddenly I couldn't get connected any more! I can only see in the Firmware of QGC that says "Plug in your device via USB to start firmware upgrade.", and nothing will happen when I connect the USB cable.

      Untitled.jpg

      The version is as follow:
      voxl-suite: 0.9.5

      when I try "voxl-inspect-services" it seems that some of the services does not exist any more! I only see 17 service names.

      Untitled1.jpg

      I would appreciate it if you could help me.

      1 Reply Last reply Reply Quote 0
      • P
        Pooyan
        last edited by

        I have tried to update the SDK using "apt update && apt upgrade" but I get "-bash: apt: command not found". I tried to do "sudo apt-get install apt" for installing apt but I got "sudo: apt-get: command not found". I think something is going wrong!

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

          @Pooyan apt is only available on voxl2

          See here for how to upgrade to the latest voxl SDK: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

          Make sure you follow the instructions for voxl1

          P 1 Reply Last reply Reply Quote 0
          • P
            Pooyan @tom
            last edited by

            @tom Thank you so much for helping.

            I flashed the seeker as you said, but still I can't see all of the features!

            446c79c4-c16c-4ff3-bca2-6671c7711ed8-image.png

            As you can see the following services are missed:
            voxl-feature-tracker
            voxl-flow-server
            voxl-px4-imu-server
            voxl-px4
            voxl-softap
            voxl-static-ip

            After flashing there was a window about welcoming, and I choose "Seeker" and keep entering for the configurations.

            After flashing will the factory configurations stay remained? and do we need to do the SDK configurations?

            I would really appreciate it if you could help me through this.

            Best,

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

              @Pooyan Okay great, it seems as though you have the latest SDK loaded on the voxl.

              I would now flash the flight core portion of the seeker with the latest px4 release which can be found in the flight-core directory of the voxl_SDK_1.1.2 directory. You can load this binary via. QGC

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

                @tom It can also be flashed with the px_uploader python script. See instructions for both options here: https://docs.modalai.com/flight-core-v2-firmware/#qgroundcontrol-fw-update

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

                  @tom If your seeker has a Flight Core v1 it'll be the same process but just loading the FCv1 binary instead

                  P 1 Reply Last reply Reply Quote 0
                  • P
                    Pooyan @tom
                    last edited by

                    @tom Thank you for the information.

                    For the QGC, I should connect it through the USB while when I do it with either Windows or Ubuntu, nothing will happen and QGC will not recognize the Seeker! I would appreciate it if you could give me some hints on this situation.

                    I have tried the link you sent me on Ubuntu, but the bootloader will not find the Seeker after using the following code:
                    ./Tools/px_uploader.py --port /dev/ttyACM1 --baud-bootloader 1152000 /home/hulabs/Downloads/seeker/voxl_SDK_1.1.2/flight-core/modalai_fc-v2_1.14.0-2.0.63.px4
                    The location of the fc-v2, is from downloading the SDK 1.1.2 and the directory you told me to find it from.
                    I have tried both v1 and v2.
                    How can I know my flight Core is v1 or v2?

                    Screenshot from 2024-01-17 16-23-59.png

                    I think maybe the problem is with "/dev/ttyACM1" which I don't know my USB name in /dev location. what I have in my /dev directory is as follow:

                    Screenshot from 2024-01-17 16-22-48.png

                    The other thing is that in the link you sent me, it was said that for the bootloader step I have to connect the USB and I dont need to use external power source, however, if I dont power up the Seeker using its battery, there would be no USB connection. Is using USB connection with powering up the Seeker with its battery correct?

                    Sorry for providing too many problems and question at the same time.

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

                      @Pooyan What is the serial number of your seeker? There should be a sticker on the frame of the drone with a number in the form MXX00000XXX

                      I should be able determine whether you have a v1 or v2 based off of that

                      If you're able to get a QGC connection via. USB you should be able to see the hardware version in qgc

                      P 1 Reply Last reply Reply Quote 0
                      • P
                        Pooyan @tom
                        last edited by

                        @tom The serial is this: M22000001WW. Thank you for Checking. Do you think if you could give me some hints about the problems as well?

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

                          @Pooyan That serial number seems to be the number for your power module. Maybe there's another elsewhere.

                          As for other tips...

                          Make sure you don't have the package brltty installed as that will often hijack devices on ttyACM, you can remove it with sudo apt remove brltty

                          Also, if you do in fact have a FCv2, you have to remove both power and usb and then only plug in power. It'll provide enough power via. usb in order to flash the device.

                          P 1 Reply Last reply Reply Quote 0
                          • P
                            Pooyan @tom
                            last edited by

                            @tom Hello again and sorry for my late response.

                            There is another serial number: M2100000J6P

                            Thank you so much for checking that.

                            One thing I want to mention is that I couldn't ever get connected via USB only. I have tried both Windows and Linux. I need to connect the battery first, and then the USB will be recognized. Having said that even in that situation, it will not be recognized with QGC. I would appreciate it if you could give some hints on this.
                            On Ubuntu, I tried dmesg -w and made sure that till the power is not connected, the USB will not get connected.

                            Untitledfff.jpg

                            I did sudo apt remove brltty as you said, and tried again but everything is still the same as screenshots I sent previously.

                            Do you have any more suggestions?

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

                              @Pooyan Okay great thanks, It does appear that you have a FCv2. Can you show point out the USB port you are using in order to connect the flight core to your PC?

                              P 1 Reply Last reply Reply Quote 0
                              • P
                                Pooyan @tom
                                last edited by

                                @tom Thank you.

                                Hope this is the answer to your request:

                                10c1f690-76ca-444f-aef3-f18b615a39ef-image.png

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

                                  @Pooyan So in the voxl-cam there are two separate boards: VOXL and Flight Core. That connector you're plugging into is USB port that allows you to access ADB on VOXL, seen here: https://docs.modalai.com/voxl-cam-user-guide-core/#connect-to-voxl-cam-with-adb

                                  What you need to connect to in order to flash flight core is J3, which can be seen here: https://docs.modalai.com/flight-core-v2-usb-to-qgc/#j3---usb--qgroundcontrol

                                  In the photo on this page it is the blue connector: https://docs.modalai.com/voxl-cam-user-guide-flight/#voxl-cam-v1-flight-core-setup

                                  You need to use an MCBL-00010, seen here: https://docs.modalai.com/cable-datasheets/#mcbl-00010 in combination with a usb to micro-usb cable to plug into your pc

                                  It can be purchased here: https://www.modalai.com/products/mcbl-00010?_pos=26&_sid=5684dd53e&_ss=r

                                  P 3 Replies Last reply Reply Quote 0
                                  • P
                                    Pooyan @tom
                                    last edited by

                                    @tom Thank you so much for letting me know. I didn't know they mean that when they say USB in the documents. I will buy that and get back to you. Thanks again.

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      Pooyan @tom
                                      last edited by

                                      @tom Hello again,

                                      I got the USB cable and did the update for the FC2 using the QGC application. The versions I can see in QGC are as follow:
                                      ee652a7c-674f-4c8e-be5f-1300b1076499-image.png
                                      At first the Airframe and Actuators tabs were red, but now they are not. I tried to update the parameters through QGC, however, still in Actuators I am not sure if everything is fine:
                                      aff27561-718c-4b5d-bf11-376b45dbf900-image.png
                                      Now, if I disconnect the USB and connect through wi-fi, still I can't get connected to the QGC, the red led will blink and the VOXL-inspect-services is as it was after flashing (no px4 is there in the list):
                                      a641c4ec-ef0a-4a76-98c7-6cc6048d019f-image.png
                                      I will appreciate it if you could give me some hints on that.

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        Pooyan @tom
                                        last edited by

                                        @tom to get connected to the QGC, I need to configure the voxl-vision-px4 and add the ip to it in order to be able to get connected to the QGC, but this file does not exist and when I try voxl-vision-hub, there is no place for an ip to get connected to QGC.

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

                                          @Pooyan You won't see voxl-px4 in the last because that is only on voxl2 where px4 runs on voxl itself. In your case, px4 is running on the flight core.

                                          In newer SDKs, you can set the gcs ip in /etc/modalai/voxl-mavlink-server.conf

                                          {
                                                  "primary_static_gcs_ip":        "192.168.8.10",
                                          
                                          P 1 Reply Last reply Reply Quote 0
                                          • P
                                            Pooyan @tom
                                            last edited by

                                            @tom Thank you so much. It is done.

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