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

    issue with starting the cameras on my VOXL 2 device.

    VOXL-CAM
    2
    17
    692
    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.
    • T
      tom admin @Rawdha R
      last edited by tom 9 Sept 2024, 17:11 9 Sept 2024, 17:11

      @Rawdha-R Seems as though there is a permissions issue where fastboot isn't able to see the device.

      These are the permissions my user has, can you confirm your user has sudo, dialout, and plugdev permissions, and if not add them and restart your computer.![alt text](9e55a8de-be79-47b7-b0f0-db654645f521-image.png image url)

      R 1 Reply Last reply 10 Sept 2024, 04:46 Reply Quote 0
      • R
        Rawdha R @tom
        last edited by 10 Sept 2024, 04:46

        @tom Yes the permissions are there, I have attached a screenshot of the permissions. In the previous post sceenshot it shows as "[INFO} Found fastboot device", but once I send 1 and enter it's stuck. Screen Shot 2024-09-10 at 8.45.51 AM.png

        T 1 Reply Last reply 10 Sept 2024, 17:16 Reply Quote 0
        • T
          tom admin @Rawdha R
          last edited by tom 10 Sept 2024, 17:16 10 Sept 2024, 17:16

          @Rawdha-R Interesting, if you run dmesg -wH in another terminal while going through this process do you see the device enumerate and then drop out maybe?

          Also, are you running Ubuntu in a VM or directly on your hardware?

          R 1 Reply Last reply 11 Sept 2024, 05:54 Reply Quote 0
          • R
            Rawdha R @tom
            last edited by Rawdha R 11 Sept 2024, 06:36 11 Sept 2024, 05:54

            @tom
            Hello,

            I followed your instructions and ran sudo dmesg -wH to monitor the kernel messages while reproducing the issue. I observed the output, which I’ve attached as a screenshot.

            For context, I am running Ubuntu on a virtual machine (VM) and not directly on my hardware. I attempted the first flight of the drone, (VPN Tailscale) and while everything else was running smoothly, the only issue I faced was that the cameras did not turn on.

            Screen Shot 2024-09-11 at 9.55.23 AM.png

            T 1 Reply Last reply 11 Sept 2024, 16:44 Reply Quote 0
            • T
              tom admin @Rawdha R
              last edited by 11 Sept 2024, 16:44

              @Rawdha-R Okay that is a good sign, it seems as though the board is going into fastboot correctly and the ubuntu machine is recognizing it that way. I still wonder if there is some permissions weirdness in play. What if you try running the install script with sudo permissions?

              R 2 Replies Last reply 16 Sept 2024, 03:41 Reply Quote 0
              • R
                Rawdha R @tom
                last edited by 16 Sept 2024, 03:41

                @tom

                It worked! I have attached a screenshot of the update:
                Screen Shot 2024-09-12 at 2.41.23 PM.png
                Screen Shot 2024-09-12 at 2.44.44 PM.png

                1 Reply Last reply Reply Quote 0
                • R
                  Rawdha R @tom
                  last edited by Rawdha R 16 Sept 2024, 08:39 16 Sept 2024, 08:37

                  @tom I'm having trouble pinging the drone. I've set it up using a 5G modem (since the drone that I have doesnt have a wifi dongle) [VOXL AL & 5G Development drone-sentinel 5G LTE Modem] to connect to QGroundControl and proceed with installing the VPN on the drone. However, when I attempt to ping google.com, I get an error stating "unknown server," and I'm unable to see the drone's IP address. Prior to updating the SDK, I had successfully configured the modem and connected to QGroundControl via Tailscale VPN and I don't know why I'm getting these issues now. Any assistance in resolving this issue would be appreciated.
                  Screen Shot 2024-09-16 at 12.00.05 PM.png
                  Screen Shot 2024-09-16 at 12.05.15 PM.png
                  Screen Shot 2024-09-16 at 12.14.58 PM.png
                  Screen Shot 2024-09-16 at 12.33.35 PM.png

                  T 1 Reply Last reply 16 Sept 2024, 16:36 Reply Quote 0
                  • T
                    tom admin @Rawdha R
                    last edited by 16 Sept 2024, 16:36

                    @Rawdha-R What do you see with ifconfig? I'm not seeing a wwan0 network interface that I would expect to see with 5G modem

                    R 1 Reply Last reply 18 Sept 2024, 04:53 Reply Quote 0
                    • R
                      Rawdha R @tom
                      last edited by 18 Sept 2024, 04:53

                      @tom
                      This is what I got when I tried ifconfig there is no wwan0 in the list
                      Screen Shot 2024-09-18 at 8.52.57 AM.png

                      T 1 Reply Last reply 18 Sept 2024, 22:11 Reply Quote 0
                      • T
                        tom admin @Rawdha R
                        last edited by 18 Sept 2024, 22:11

                        @Rawdha-R Seems as though your 5G add-on board isn't fully seated and isn't able to enumerate

                        R 1 Reply Last reply 19 Sept 2024, 07:40 Reply Quote 0
                        • R
                          Rawdha R @tom
                          last edited by 19 Sept 2024, 07:40

                          @tom
                          Screen Shot 2024-09-19 at 11.34.12 AM.png
                          I have double-checked that the 5G add-on board is fully seated, and I followed the same process that worked successfully before the update. Given the current issue, what would you recommend I check next to help resolve this? I have attached a screenshot where I tried to reconfigured the modem and the issue still persists.

                          T 1 Reply Last reply 19 Sept 2024, 16:59 Reply Quote 0
                          • T
                            tom admin @Rawdha R
                            last edited by 19 Sept 2024, 16:59

                            @Rawdha-R What do you see with systemctl status voxl-modem?

                            If it is indeed not enumerating because of hardware there's nothing on the software side that will resolve it so we need to determine whether it is hw or sw at this point

                            R 2 Replies Last reply 23 Sept 2024, 05:09 Reply Quote 0
                            • R
                              Rawdha R @tom
                              last edited by Rawdha R 23 Sept 2024, 05:43 23 Sept 2024, 05:09

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • R
                                Rawdha R @tom
                                last edited by 23 Sept 2024, 07:08

                                @tom It worked! I tightened the screws, and it turns out it was a hardware issue. I've installed the Tailscale VPN on both the drone and my machine, and I've completed the calibration and binding. However, I'm having trouble starting the camera; it's not turning on in VLC or QGroundControl.

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