Hey guys!

I came across a strange anomaly last week on a starling drone I have. I was missing the voxl2 SDK version/ "voxl-suite" parameter as the drone boots up.

I remember, the week before I use to see "1.1.2" over there. The drone was still functioning and the voxl2 was not damaged in anyway. To move to a newer release I did an update and this is what happened.

First I did a sudo apt update, followed by sudo apt-get upgrade.
The output of the upgrade looked like below,

I did as suggested, "sudo apt autoremove", and below is the list of pacRemoving qrb5165-dfs-server (0.2.0) ...

Removing voxl-vision-hub (1.7.3) ...
Removing voxl-camera-server (1.8.9) ...
Removing libmodal-exposure (0.1.0) ...
Removing libvoxl-cci-direct (0.2.1) ...
Removing voxl-remote-id (0.0.9) ...
Removing libmodal-journal (0.2.2) ...
Removing qrb5165-rangefinder-server (0.1.1) ...
Removing voxl-lepton-server (1.2.0) ...
Removing voxl-elrs (0.1.3) ...
dpkg: warning: while removing voxl-elrs, directory '/usr/share/modalai/voxl-elrs/tools' not empty so no
t removed
dpkg: warning: while removing voxl-elrs, directory '/usr/share/modalai/voxl-elrs/esptool/esptool/target
s' not empty so not removed
Removing voxl-esc (1.3.7) ...
dpkg: warning: while removing voxl-esc, directory '/usr/share/modalai/voxl-esc-tools' not empty so not 
removed
Removing qrb5165-imu-server (1.0.1) ...
Removing voxl-qvio-server (1.0.0) ...
Removing voxl-utils (1.3.3) ...
Removing qrb5165-system-tweaks (0.2.3) ...
Removing voxl-tflite-server (0.3.1) ...
Removing qrb5165-tflite (2.8.0-2) ...
Removing voxl-bind-spektrum (0.1.0) ...
Removing voxl-camera-calibration (0.5.3) ...
Removing voxl-configurator (0.4.8) ...
Removing voxl-portal (0.6.3) ...
Removing voxl-cpu-monitor (0.4.7) ...
Removing voxl-docker-support (1.3.0) ...
Removing voxl-flow-server (0.3.3) ...
Removing voxl-feature-tracker (0.3.2) ...
Removing voxl-gphoto2-server (0.0.10) ...
Removing voxl-logger (0.3.5) ...
Removing voxl-jpeg-turbo (2.1.3-5) ...
Removing voxl-libgphoto2 (0.0.4) ...
Removing voxl-uvc-server (0.1.6) ...
Removing voxl-libuvc (1.0.7) ...
Removing voxl-mavcam-manager (0.5.3) ...
Removing voxl-mavlink (0.1.1) ...
Removing voxl-mavlink-server (1.3.2) ...
Removing voxl-modem (1.0.8) ...
Removing voxl-mongoose (7.7.0-1) ...
Removing voxl-mpa-to-ros (0.3.7) ...
Removing voxl-neopixel-manager (0.0.3) ...
Removing voxl-tag-detector (0.0.4) ...
Removing voxl-px4-imu-server (0.1.2) ...
Removing voxl-streamer (0.7.4) ...
Removing libmodal-cv (0.4.0) ...
Removing libqrb5165-io (0.4.2) ...
dpkg: warning: while removing libqrb5165-io, directory '/usr/local/lib/python3.6/dist-packages' not emp
ty so not removed
Removing voxl-mpa-tools (1.1.3) ...
Removing librc-math (1.4.2) ...
Removing voxl-opencv (4.5.5-2) ...
kages that were removed;

After this, the voxl2 looks like below,

I flashed the voxl2 with the latest SDK to revive it but in the process I lost a few setup files and containers I had installed on the drone for my work. I had to redo the setup of the drone and now everything looks operational but still it would be good to know if anybody has any ideas why the "voxl-suite" would become blank in the first place.

Thanks!

@Alex-Kushleyev Sorry for the late response. I had this issue a long time ago. At the time I was working with IMX377 Hires camera from Modal AI and I was using Voxl1 and not Voxl2.

Unfortunately, I didn't find a reason for a single 14.5cm cable not working, but connecting two 6cm cables was working so I continued my testing with that.

Thanks!

Hello,

I received a shipment of MIPI extension cables (14.5 cm) few weeks ago. Turns out the camera server keeps dying when I use those cables. Before using the long extension cables, I rigged many small cables and tested but the camera server didn't die. This confirmed that the port on the voxl and the camera is not the issue. While connecting the new cable, the voxl-camera-server starts but dies after a short time (~ 15 secs).

Can you please help me with this issue and tell why this would happen. I'm handling the cable with extreme care and making sure that I don't bend it 90degs. But still a fresh piece right out the ESD bag does not work for a long time.

Can somebody please help me what to do?

Thanks

@tom Hello, I work with @m1baldwin and he has asked me to share this information with you.

Board 1 - Serial no: M22000004FP
Version: 0.9.4

Board 2- Serial no: M22000004H7
Version: 0.9.4

I hope this helps. Let us know if anything else is required.
Thanks.