@bambamoda The VOXL 2 can support 8 PWM outputs with this add-on board: https://www.modalai.com/products/voxl2-io?variant=40610514206771.

@taiwohazeez Can you please provide the flight log?

@Zachary-Lowell-0 Hi, let me explain what i meant by hovering mode. There is a 3-way toggle switch beside the kill switch in the transmitter (toggling down switches to position mode, toggling up switches to the autonomous mode, while toggling to the middle maintains the drone flight positioning. I have another drone that when the button is switched to the middle, it maintains the drone position (thats what i meant by hover mode). My other starling 2 drones maintains their positions when the switch is toggled to the middle position, but this particular starling 2 drone doesnt.

@lhermosillo said in Recovering Flight Logs from a Bricked VOXL2:

odal hello\n[MODALAI] test log\n\n[MODALAI] Executing usb_open\n[MODALAI] Complete

If you use the tool, you'll lose your data, unlike what you wished for in the OP.
However, if you want to proceed with this issue, I'd unplug the usb from the host, and reboot the device. Once booted, I'd plug the device and check with lsusb that is there ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode). Then do the webUI process (select image, then flash).

@roy-crosthwaite said in Bricked VOXL2:

The only way I see the device is with lsusb or the web interface shown below

I've just received the voxl2, so not a lot of experience with it. Just for me to understand-- why not try to unbrick it with the qdl webUI, as it is the only tool that detects it? I'm asking since I have the my board at the same exact state, but this webUI tool failed, so I'm wondering if you know something that I don't (like whether seeing the device via fastboot is a prerequisite for the unbricking).

@N-Chen
Can someone from the ModalAI team assist with this issue?

Were you able to solve this issue and unbrick the device? Can you explain how?

@greg_s Hi there, can you post these 2 files from your drone:

/etc/modalai/voxl-vision-hub.conf /etc/modalai/voxl-open-vins-server.conf

One thing from your screenshot is I sort of see the drone's position and the trajectory planned. For example as in this screenshot, the drone's xyz position should be visible (xyz axes) and a trajectory (black & red lines) should be displayed before executing a trajectory. The drone should be moving in realtime hovering in position. If it's static the vio was likely lost.
mapper.jpg

@latif said in Requesting the factory original calibration files for ADK Ser#M2500000185:

M250000018S

Okay great, I will send you an email with that calibration file.

You'll have to re-calibrate the imu yourself.

See here for instructions: https://docs.modalai.com/calibrate-imu/#step-3

You will need the SKU supporting the TOF to accurately run current versions of voxl-mapper and VOA.

Zach

The system has an HDMI out so you can plug it into an external monitor yes:

https://docs.modalai.com/vrx-ground-unit-developer-guide/

@Ido-Goldstein to run yolov8 run voxl-configure-tflite-server and then when it prompts you to select your model, you can select yolov8. YOLOV11 is also currently supported however is still CPU bound so I would recommend using yolov8 for GPU processing

@Jakub-Tvrz said in Starling 2 Max for indoor:

● Next Generation PMD ToF image sensor for obstacle avoidance and 3D mapping

@Jakub-Tvrz if you purchased the starling 2 Max version that comes with the PMD TOF then you will be capable of running PX4's instance of visual obstacle avoidance - however, it is not... great.

● Next Generation PMD ToF image sensor for obstacle avoidance and 3D mapping

https://www.modalai.com/collections/all/products/starling-2-max?variant=49129974169904 <-- this the version you will had to buy for the TOF sensor

@tom I am using the Modalai Main fork of PX4 which already have the turtle mode, I just want the turtle mode to be enabled through joystick.

Hi @SKA ,

I believe i fixed this issue with full-follow mode in the camera server. Now EIS has a body->imu transform, which is read from the extrinsics file and is used to properly rotate the image, instead of hi-jacking the cam->cam_eis transform.

So now your cam->cam_eis transform should work. Please make sure the imu_apps->cam transform is correct, if your camera is rotated 90 degrees.

Please check the commits from Nov 10 : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/commits/dev

Alex

Hello @jeremyrbrown5 ,

Can you please answer the following questions to help us diagnose the issue?

Which wifi adapter are you using? Does rebooting VOXL2 Mini help? How are you measuring the connection quality?

Alex

@Eric-Katzfey
hey,
I observed something while the above behaviour still persists.
The modem and the camera server is showing not running while checking through the inspect services command.
I do not know whether this is related to this issue, but the voxl 2 is rebooting after sometime, the reboot is not constant and I am not able to able to find the reason for the reboot. Can everything be related to each other.
I am using the Microhard modem

Screenshot from 2025-11-10 15-27-45.png

Screenshot from 2025-11-10 15-30-27.png