@N-Chen I tried the webUI and the command line and as near as I can tell the webUI uses lsusb (or something along those lines) to detect the presence of the board. The install.sh uses adb or fastboot to detect the board and will sit waiting until the board is detected or CTL C is sent. My guess is the usb controller interface is alive and reporting but everything beyond it is dead.

@ravi I'm suspecting you have a bad cable or the cable is subject to some interference. Can you try this on a benchtop with just a VOXL 2 and an FC v2 and no other components? Is it currently integrated into a custom drone? Can you look at the signal quality on the TX and RX UART lines with an oscilloscope?

I have the same problem before — turns out the compass setup finally worked after I did a full sensor recalibration in QGroundControl and made sure the GPS/compass was facing the right direction. Worth a try if you haven’t done that yet! You can also try this tool for free. https://123compass.org/

@Dmytro-Stolbovyi Here is the updated link: https://docs.modalai.com/voxl2-unbricking/

@Moderator Many thanks for your reply Our goal is to develop a drone capable of indoor/confined-space autonomous flight without GPS, using SLAM-based navigation. The system should perform 3D mapping, obstacle avoidance, and full-area path planning. We would like to confirm the correct set of components and the required algorithm stack. Planned Algorithm Stack: State Estimation: QVIO (Visual-Inertial Odometry) providing position and velocity to PX4/EKF2 via voxl-vision-hub. Mapping: voxl-mapper (TSDF/ESDF) using a depth source. Planning and Avoidance: voxl-mapper’s path planner or PX4 avoidance, using VIO as the pose source. Autopilot: PX4 running on VOXL2 via voxl-px4. Proposed Hardware: VOXL2 Autopilot – https://www.modalai.com/products/voxl-2?variant=39914779836467 VOXL2 Tracking Camera (Mono Global-Shutter) – required for QVIO (please confirm the correct part number). -- https://www.modalai.com/collections/image-sensors/products/msu-m0149-1 VOXL2 Compatible adapter https://www.modalai.com/products/mdk-m0076-1 VOXL2 Time-of-Flight (ToF) Depth Sensor – https://www.modalai.com/products/m0178?variant=48528287793456 VOXL2 Mini 40-Pin Connector ToF Adapter (MDK-M0172-1-00) – https://www.modalai.com/products/mdk-m0172-1-00 Questions: Please confirm if this set (VOXL2 + Tracking Camera + Camera adapter + ToF sensor + ToF adapter) is sufficient for robust indoor SLAM navigation using PX4. For the tracking camera, which exact ModalAI part number is recommended for QVIO on VOXL2? Are there any best-practice configurations for voxl-mapper when using ToF instead of stereo depth? Would you recommend any additional sensors for improved performance in larger or more complex indoor environments? Goal Summary: We want the drone to hold position, generate a 3D occupancy map, avoid obstacles, and autonomously plan paths throughout the flyable space—without any GPS input. Thank you in advance for your guidance and confirmation. Best regards, Nitin

@adiprin1 On Ardupilot there is currently no way to use apps side UARTs (Some day we will add a method to use them). So, you would have to use one of the 3 UARTs attached to the DSP. If you removed the RC or the GPS and used that port then, theoretically, it could work. However, we have not tried that so can't make any guarantees. Also on PX4 you can use an apps side UART if there is one available on an add-on board. And, as you mention, you could use an SBUS RC on the VOXL 2 IO board and free up the standard RC UART.

@Aaron-Porter , perhaps systemd-timesyncd works together with systemd to correctly interpret the clock adjustments, so that run-time of systemd services is properly calculated. Alex

@Alex-Kushleyev The IMU is being configured with an 8K ODR so by increasing IMU_GYRO_RATEMAX you are reading the FIFO more often but reading less samples each time. So you are mainly increasing the overhead of context switching. Can you characterize how much the load increases just by increasing IMU_GYRO_RATEMAX and not doing any of the extra UART IO? Unfortunately we don't have a lot of control over the low level implementation of the IO drivers that are in the Qualcomm code. And there is no DMA that could help lower IO overhead. One idea would be to lower the ODR to 1K so that you are only reading one sample from the FIFO at each interrupt.

@tom Thank you for the support.

@Huynh-Gremsy No, there is no way to do that. There is no display output

@Aaron-Porter Most likely jump is due to NTP aligning the clock. The other device that is time stamping using real time clock really should move to monotonic.

@Federico-Wyrwal , please check the instructions for setting up EIS, specifically https://docs.modalai.com/camera-video/electronic-image-stabilization/#minimal-software-setup The latest drivers can be downloaded from here Please let me know if you have any other questions. Alex

@Alex-Kushleyev Thanks

@J-B-Song Hello J.B Song, Did you connect HDMI via USB-C on VOXL2? Did you use this image [image: 1756439982349-7d1ec055-c0a2-497c-8c85-be95d56a1125-image.png] Hope your reply soon, thanks so much.

@Eric-Katzfey thank you for reverting back, it was very helpful, i was able to get multiple streams.

@andrevs01 But, the configuration of what Mavlink broadcasts can be different than what it actually broadcasts. It will only broadcast something that it is configured to broadcast if it is receiving data from the required topic(s) internally.

@Thomas-Müller you can read up on our "VOA" implementations here: https://docs.modalai.com/voa/