[Starling2] The devices are recognized as /dev/video* but no assigned as the device available in the voxl system

Yoshimaru Tanaka

Hi, I unblicked one of our Starling2, but I can not see any video in the app QGroundControl.

I found the problem with the debug tool described in the following log section.

However, I could not figure out how to fix it. Could you give me any help, please?

Thanks.

What hardware are you using? If you have specific SKU or serial number, that is also helpful

family code:   MRB-D0014 (starling-2)
compute board: 4 (voxl2)
hw version:    1
cam config:    27
modem config:  22 (M0141 w/ Alfa Networks WiFi Dongle AWUS036EACS)
tx config:     7 (elrs_beta_fpv)
extras config: 0 (none)
SKU:           MRB-D0014-4-V1-C27-T7-M22-X0

What version of software are you using? voxl-version is very helpful for determining software version.*

--------------------------------------------------------------------------------
system-image: 1.8.02-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Mon Nov 11 22:47:44 UTC 2024 4.19.125
--------------------------------------------------------------------------------
hw platform:  M0054
mach.var:     1.0.1
--------------------------------------------------------------------------------
voxl-suite:   1.4.1
--------------------------------------------------------------------------------
current IP:   wlan0: 192.168.8.1
--------------------------------------------------------------------------------

How have you configured the software? What is the output of voxl-inspect-services

Service Name             |  Enabled  |   Running   |  CPU Usage
-------------------------------------------------------------------
 docker-autorun           | Disabled  | Not Running |  
 modallink-relink         | Disabled  | Not Running |  
 voxl-auto-logger         | Disabled  | Not Running |  
 voxl-camera-server       |  Enabled  |   Running   |    31.9%
 voxl-cpu-monitor         |  Enabled  |   Running   |     0.7%
 voxl-dfs-server          | Disabled  | Not Running |  
 voxl-elrs-startup        | Disabled  | Not Running |  
 voxl-feature-tracker     | Disabled  | Not Running |  
 voxl-flow-server         | Disabled  | Not Running |  
 voxl-imu-server          |  Enabled  |   Running   |     4.3%
 voxl-io-server           | Disabled  | Not Running |  
 voxl-lepton-server       | Disabled  | Not Running |  
 voxl-lepton-tracker      | Disabled  | Not Running |  
 voxl-logger              | Disabled  | Not Running |  
 voxl-mavcam-manager      |  Enabled  |   Running   |     0.0%
 voxl-mavlink-server      |  Enabled  |   Running   |     4.0%
 voxl-modem               | Disabled  | Not Running |  
 voxl-open-vins-server    |  Enabled  | Not Running |  
 voxl-osd                 | Disabled  | Not Running |  
 voxl-portal              |  Enabled  |   Running   |     0.1%
 voxl-px4-imu-server      | Disabled  | Not Running |  
 voxl-px4                 |  Enabled  |   Running   |    42.9%
 voxl-qvio-server         | Disabled  | Not Running |  
 voxl-rangefinder-server  |  Enabled  |   Running   |     0.9%
 voxl-remote-id           | Disabled  | Not Running |  
 voxl-softap              |  Enabled  |  Completed  |  
 voxl-state-estimator     | 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-uvc-server          | Disabled  | Not Running |  
 voxl-vision-hub          |  Enabled  |   Running   |     9.3%
 voxl-vrx                 | Disabled  | Not Running |  
 voxl-vtx                 | Disabled  | Not Running |  
 voxl-wait-for-fs         |  Enabled  |  Completed  |

Do you have any logs? Uploading PX4 logs to https://logs.px4.io can be very helpful. See details on PX4 logs here

With this command:

voxl-inspect-cam -a

I got this:

Client is cleaning up pipes for the server
ERROR in pipe_client_open opening request pipe: No such device or address
closing and exitingver stopped without cleaning up

I also tried this:

voxl2:/$ ls /dev/video*  
/dev/video0  /dev/video1  /dev/video32  /dev/video33

Can you share pictures of your setup?
Have you looked at the source code? If so, can you point to any potential issues?
No.

Alex Kushleyev

@Yoshimaru-Tanaka ,

Can you please stop voxl-camera-server service and run the camera server in foreground to make sure that all cameras are started:

systemctl stop voxl-camera server
voxl-camera-server

If there is a problem, you should see it in the terminal output. I am surprised that voxl-inspect-cam -a does not produce any output, which means none of the cameras are alive, so you should see something in the output from voxl-camera-server process.

Perhaps your board is not correctly configured for the cameras, so you may want to run voxl-configure-cameras and select the correct option for your camera setup. Then re-start voxl-camera-server.

Alex