@Yufei-Jiang What hardware are you using? Is this PX4 running on VOXL 2?

@Inverse-AJ @rogerli
Hi, I also struggled with the OBSTACLE_DISTANCE MAVLink message not appearing in the MAVLink Inspector. Moreover, obstacle avoidance was not functioning after I upgraded v1.3.5 to ModalAI SDK v1.5.0. If you're experiencing this issue, ensure the following:

Set MPC_POS_MODE to 0 (Simple Position Control) or 3 (Smooth Position Control). The default value (4, Acceleration-based Input) is incompatible with ModalAI’s VOXL platform.
Set COM_OBS_AVOID to 1. This enables obstacle avoidance in PX4.
Set CP_DIST to a value greater than 0. This specifies the critical distance for collision prevention.
Ensure your drone has a valid home position or local position from QVIO. This is required for proper navigation.
Ensure your drone is in Position Hold mode. Obstacle avoidance requires this flight mode.

Although the OBSTACLE_DISTANCE message does not appear in the MAVLink Inspector, QGroundControl displays the obstacle distance overlay in its telemetry view, and the drone successfully performs obstacle avoidance. Note: This applies to ModalAI SDK v1.5.0; check for updates in newer versions.

f0d0fe9f-61ff-4287-9210-186dafc0879a-Untitled.jpg

@Avery-Cuevas Yes, the VOXL powers up and I've tried using different USBs and still no result. I even tried reflashing the system, but it won't detect fastboot and adb devices

@tom said in Missing Config File:

voxl-configure-vision-hub factory_enable

thanks. I tried the Sku Wizard then MPA but I seem to still have a blank file when I open it in nano. I will try the factory default next.

@victochen , just to close the loop on the original issue.. the delay in the calibration procedure was caused by UART data or processing of the ESC feedback backing up. The fix is to just slow down the command rate, seen in this commit : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/commit/b512f9e3d5e695868775de3d40eedb2ad15cf6d9 . Additionally, using command line argument --cmd-rate 100 when you run the calibration script on VOXL2 will fix the issue.

Hi @VictorG
You should RMA the FlightCore and we should replace it. Just mention this thread or place a link to it in the form:
https://www.modalai.com/pages/rma?_pos=1&_sid=190e46152&_ss=r

We do not yet have a replacement set of cables, under normal circumstances, it takes us 6-8 weeks to get more, so we are trying to see if we have any small batch in our inventory to hold us over and replace every bad cable that we shipped.

If you want to try to re-pin your cable for the interim (you will not need to send it back, we can just replace it when we get more), try this link:
https://docs.modalai.com/cable-userguides/ and at the bottom are tips for re-pinning

e3db6dea-7d0a-43e4-8c21-44f7ab444469-image.png
or you can just search youtube for s JST GH re-pin tutorial and I'm sure you'll find plenty of good techniques. All that is needed is tweezers.

The three are all different makes/models