Posts made by tom

@ashwin Interesting, can you post the output of the failure you're seeing when you attempt to flash the board via. QDL?

@claw Not at this time as ROS2 takes up a lot of space so we don't include it by default

@ashwin Okay so it is enumerating into a bricked state as expected. If you switch SW2 to on and repeat the same test what do you see?

@MikeD Docker is not installed by default, but you can follow the ubuntu install instructions on VOXL2:https://docs.docker.com/engine/install/ubuntu/

@Morten-Nissov Likely should all be off, it's been a while since I've had one of these come across my desk. I'll see if I can find one to reference.

@ashwin What do you see if you run dmesg -wH and then power and plug in the board via USB

@tahawaru You should select 8 for rb5-flight

@griffin Are you able to view the tof data in voxl-portal?

@ramp Yes you could still do HITL with a starling 2 max, would just require unplugging the ESC from the VOXL 2 and using that connector

@antenna-eng What hardware do you have connected to the VOXL 2 board? Cameras etc.

@LR I would recommend upgrading to the newly released SDK 1.4.1 from downloads.modalai.com

Simply, download, untar, and run ./install.sh

It'll retain any important calibration files and will re-configure the drone based off the SKU

@tom It always preferable to run linux natively to avoid issues like this

@Taka It doesn't seem as though the USB device is being passed from your host machine to your VM, that's likely something that needs to be configured manually via your VM software

@tkddnjs825 Nope, if you run through install.sh it'll get everything setup as necessary

@arcj Try voxl-tflite-server -d

@RSAUser1 It's not something I've tried, but I assume it would work in the same way you would do it on another Ubuntu 18.04 device.

@tkddnjs825 QVIO can only do single cam VIO.

If you upgrade to SDK 1.4.0 it will use voxl-open-vins-server for VIO by default, which will use dual-cam

@arcj voxl-tflite-server is likely running as a systemd service.

For debugging purposes I would disable it from running on boot with the following:

systemctl disable voxl-tflite-server

and also kill it

systemctl stop voxl-tflite-server

then run voxl-tflite-server from the command line to monitor the output

@RSAUser1 If you upgrade to the latest SDK (1.4.0) you'll see a new option in voxl-wifi for softap5 which will create a 5GHz network

@dlee We publish "nightly" SDK builds at https://storage.googleapis.com/platform-nightlies/voxl2/voxl2_SDK_nightly_20250213.tar.gz (URL will match yesterday's date, PST)

This takes the latest of each repo's dev branch as well as the latest system image built every night