issue with starting the cameras on my VOXL 2 device.
-
@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
, andplugdev
permissions, and if not add them and restart your computer.![alt text]( image url) -
@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.
-
@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?
-
@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.
-
@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? -
It worked! I have attached a screenshot of the update:
-
@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.
-
@Rawdha-R What do you see with
ifconfig
? I'm not seeing awwan0
network interface that I would expect to see with 5G modem -
@tom
This is what I got when I tried ifconfig there is no wwan0 in the list
-
@Rawdha-R Seems as though your 5G add-on board isn't fully seated and isn't able to enumerate
-
@tom
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.