# issue with starting the cameras on my VOXL 2 device. Source: https://forum.modalai.com/topic/3772/issue-with-starting-the-cameras-on-my-voxl-2-device Category: Flight Core and Legacy VOXL (https://forum.modalai.com/category/9/flight-core-and-legacy-voxl) Tags: voxl-cam Posted: 2024-09-03 05:41:40 UTC by Rawdha R Replies: 15 · Views: 3641 ## Rawdha R · 2024-09-03 05:41:40 UTC I am facing an issue with starting the cameras on my VOXL 2 device. Previously, all cameras were visible in the VOXL web portal, but currently, only the "hires" camera is showing up. Additionally, the cameras are not working in QGroundControl or VLC. I have tried several troubleshooting steps, such as configuring the video settings in the General tab of QGroundControl, adding the RTSP URL, and setting the aspect ratio, but there is still no output. When I run voxl-camera-server, only the "hires" camera is enabled, while others are not visible. Could you please guide me on how to get all cameras working again in both VOXL web portal and QGroundControl/VLC? This is the VOXL version: Vol version: -------------------------------------------------------------------------------- system-image: 1.3.1-M0054-14.1a-perf kernel: #1 SMP PREEMPT Tue Aug 2 05:23:05 UTC 2022 4.19.125 -------------------------------------------------------------------------------- hw version: M0054 -------------------------------------------------------------------------------- voxl-suite: 0.8.1 -------------------------------------------------------------------------------- This is what I get when I do: voxl2:/$ voxl-inspect-services Service Name | Enabled | Running | CPU Usage --------------------------------------------------------------- docker-autorun | Disabled | Not Running | docker-daemon | Disabled | Not Running | modallink-relink | Enabled | Not Running | voxl-camera-server | Enabled | Running | 0.0 voxl-cpu-monitor | Enabled | Running | 0.0 voxl-dfs-server | Disabled | Not Running | voxl-imu-server | Enabled | Running | 0.0 voxl-mavlink-server | Enabled | Running | 0.0 voxl-modem | Enabled | Running | 0.0 voxl-portal | Enabled | Running | 15.0 voxl-px4-imu-server | Disabled | Not Running | voxl-px4 | Enabled | Running | 0.0 voxl-qvio-server | Enabled | Running | 0.0 voxl-softap | Disabled | Not Running | voxl-static-ip | Disabled | Not Running | voxl-streamer | Enabled | Running | 0.0 voxl-tag-detector | Disabled | Not Running | voxl-tflite-server | Disabled | Not Running | voxl-time-sync | Disabled | Not Running | voxl-vision-px4 | Enabled | Running | 0.0 voxl-wait-for-fs | Enabled | Completed | ## Reply by tom (ModalAI staff) · 2024-09-05 16:14:47 UTC @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 by Rawdha R · 2024-09-09 06:06:30 UTC (in reply to tom) @tom said in [issue with starting the cameras on my VOXL 2 device\.](/post/18902): > @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](https://forum.modalai.com/assets/uploads/files/1725861936761-screen-shot-2024-09-09-at-9.59.59-am-resized.png) It is stuck at this point, please see the screenshot above. ## Reply by tom (ModalAI staff) · 2024-09-09 17:11:09 UTC (in reply to Rawdha R) @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](https://forum.modalai.com/assets/uploads/files/1725901877732-9e55a8de-be79-47b7-b0f0-db654645f521-image.png) image url) ## Reply by Rawdha R · 2024-09-10 04:46:13 UTC (in reply to tom) @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](https://forum.modalai.com/assets/uploads/files/1725943565122-screen-shot-2024-09-10-at-8.45.51-am.png) ## Reply by tom (ModalAI staff) · 2024-09-10 17:16:18 UTC (in reply to Rawdha R) @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? ## Reply by Rawdha R · 2024-09-11 05:54:58 UTC (in reply to tom) @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](https://forum.modalai.com/assets/uploads/files/1726034188647-screen-shot-2024-09-11-at-9.55.23-am.png) ## Reply by tom (ModalAI staff) · 2024-09-11 16:44:30 UTC (in reply to Rawdha R) @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? ## Reply by Rawdha R · 2024-09-16 03:41:28 UTC (in reply to tom) @tom It worked! I have attached a screenshot of the update: ![Screen Shot 2024-09-12 at 2.41.23 PM.png](https://forum.modalai.com/assets/uploads/files/1726137806924-screen-shot-2024-09-12-at-2.41.23-pm.png) ![Screen Shot 2024-09-12 at 2.44.44 PM.png](https://forum.modalai.com/assets/uploads/files/1726137897858-screen-shot-2024-09-12-at-2.44.44-pm.png) ## Reply by Rawdha R · 2024-09-16 08:37:02 UTC (in reply to tom) @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](https://forum.modalai.com/assets/uploads/files/1726473612172-screen-shot-2024-09-16-at-12.00.05-pm.png) ![Screen Shot 2024-09-16 at 12.05.15 PM.png](https://forum.modalai.com/assets/uploads/files/1726473923379-screen-shot-2024-09-16-at-12.05.15-pm.png) ![Screen Shot 2024-09-16 at 12.14.58 PM.png](https://forum.modalai.com/assets/uploads/files/1726474505824-screen-shot-2024-09-16-at-12.14.58-pm.png) ![Screen Shot 2024-09-16 at 12.33.35 PM.png](https://forum.modalai.com/assets/uploads/files/1726475624959-screen-shot-2024-09-16-at-12.33.35-pm.png) ## Reply by tom (ModalAI staff) · 2024-09-16 16:36:41 UTC (in reply to Rawdha R) @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 ## Reply by Rawdha R · 2024-09-18 04:53:57 UTC (in reply to tom) @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](https://forum.modalai.com/assets/uploads/files/1726635183530-screen-shot-2024-09-18-at-8.52.57-am.png) ## Reply by tom (ModalAI staff) · 2024-09-18 22:11:13 UTC (in reply to Rawdha R) @Rawdha-R Seems as though your 5G add-on board isn't fully seated and isn't able to enumerate ## Reply by Rawdha R · 2024-09-19 07:40:50 UTC (in reply to tom) @tom ![Screen Shot 2024-09-19 at 11.34.12 AM.png](https://forum.modalai.com/assets/uploads/files/1726731256208-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. ## Reply by tom (ModalAI staff) · 2024-09-19 16:59:41 UTC (in reply to Rawdha R) @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 ## Reply by Rawdha R · 2024-09-23 07:08:37 UTC (in reply to tom) @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.