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

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

@tom
This is what I got when I tried ifconfig there is no wwan0 in the list

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

@tom

It worked! I have attached a screenshot of the update:

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

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

@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] It is stuck at this point, please see the screenshot above.

@tom this is the output: 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

When accessing the VOXL web portal, only the "Hires" camera is visible. Previously all 7 cameras where visible(Hires, Tracking, Qvio Overlay, Stereo Front (2 cameras), Stereo Rear (2 cameras))

This is the output for voxl-configure-cameras:
voxl2:/$ voxl-configure-cameras
ERROR: missing camera config ID

For more flexibility, use the general use case:
voxl-configure-cameras <configuration-id>

arguments are as follows:

sentinel - default for sentinel drone, no config ID needed
disable - disables voxl-camera-server
help - show this help text

If no configuration-id or arguments are given, the user will be
prompted with questions to help complete configuration

available camera configurations are as follows:

0 None
1 Tracking + Stereo(OV7251)
2 Tracking Only
3 Hires + Stereo(OV7251) + Tracking
4 Hires + Tracking
5 TOF + Tracking
6 Hires + TOF + Tracking
7 TOF + Stereo(OV7251) + Tracking
8 Hires Only
9 TOF Only
10 Stereo(OV7251) only
11 Tracking + Hires + Dual Stereo Pairs
12 Stereo(OV9782) only
13 Hires + Stereo(OV7251)

voxl-camera-server has only hires configured, I tried configuring the rest of the cameras but got the following error: voxl2:/$ sudo systemctl status voxl-camera-server
\u25cf voxl-camera-server.service - voxl-camera-server
Loaded: loaded (/usr/bin/voxl-camera-server; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Wed 2024-09-04 06:35:09 UTC; 4s ago
Process: 28196 ExecStart=/bin/bash -c /usr/bin/voxl-camera-server (code=killed
Main PID: 28196 (code=killed, signal=SEGV)

Sep 04 06:35:09 m0054 bash[28196]: Error in json_read_file while parsing file /e
Sep 04 06:35:09 m0054 bash[28196]: The syntax error occured immediately BEFORE t
Sep 04 06:35:09 m0054 bash[28196]: 412",
Sep 04 06:35:09 m0054 bash[28196]: ERROR: object missing cameras
Sep 04 06:35:09 m0054 bash[28196]: Segmentation fault:
Sep 04 06:35:09 m0054 bash[28196]: Fault thread: voxl-camera-ser(tid: 28196)
Sep 04 06:35:09 m0054 bash[28196]: Fault address: 0x10
Sep 04 06:35:09 m0054 bash[28196]: Address not mapped.
Sep 04 06:35:09 m0054 systemd[1]: voxl-camera-server.service: Main process exite
Sep 04 06:35:09 m0054 systemd[1]: voxl-camera-server.service: Failed with result
lines 1-16/16 (END) I triedd to reconfigure according to the following types but I'm still getting an error. (type: “ov7251”, “ov9782”, “imx214”, “imx412”, “imx678”, or “pmd-tof” )