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

    issue with starting the cameras on my VOXL 2 device.

    VOXL-CAM
    2
    17
    691
    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.
    • tomT
      tom admin @Rawdha R
      last edited by

      @Rawdha-R I think the best first step would be to load the latest SDK on your VOXL 2 as that SDK is a few years old at this point.

      I would recommend flashing the latest SDK (1.3.3) from downloads.modalai.com under "VOXL 2 Platform Releases"

      Just follow the instructions here to do so: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

      Rawdha RR 1 Reply Last reply Reply Quote 0
      • Rawdha RR
        Rawdha R @tom
        last edited by

        @tom said in issue with starting the cameras on my VOXL 2 device.:

        @Rawdha-R I think the best first step would be to load the latest SDK on your VOXL 2 as that SDK is a few years old at this point.

        I would recommend flashing the latest SDK (1.3.3) from downloads.modalai.com under "VOXL 2 Platform Releases"

        Just follow the instructions here to do so: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

        Reply

        I tried flashing the latest SDK (1.3.3) from downloads modalai under VOXL 2 platform release[link text]Screen Shot 2024-09-09 at 9.59.59 AM.png It is stuck at this point, please see the screenshot above.

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

          @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)

          Rawdha RR 1 Reply Last reply Reply Quote 0
          • Rawdha RR
            Rawdha R @tom
            last edited by

            @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

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

              @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?

              Rawdha RR 1 Reply Last reply Reply Quote 0
              • Rawdha RR
                Rawdha R @tom
                last edited by Rawdha R

                @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

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

                  @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?

                  Rawdha RR 2 Replies Last reply Reply Quote 0
                  • Rawdha RR
                    Rawdha R @tom
                    last edited by

                    @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
                    • Rawdha RR
                      Rawdha R @tom
                      last edited by Rawdha R

                      @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

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

                        @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

                        Rawdha RR 1 Reply Last reply Reply Quote 0
                        • Rawdha RR
                          Rawdha R @tom
                          last edited by

                          @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

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

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

                            Rawdha RR 1 Reply Last reply Reply Quote 0
                            • Rawdha RR
                              Rawdha R @tom
                              last edited by

                              @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.

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

                                @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

                                Rawdha RR 2 Replies Last reply Reply Quote 0
                                • Rawdha RR
                                  Rawdha R @tom
                                  last edited by Rawdha R

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • Rawdha RR
                                    Rawdha R @tom
                                    last edited by

                                    @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
                                    • First post
                                      Last post
                                    Powered by NodeBB | Contributors