ModalAI Forum

@Jetson-Nano

If this doesn't work, on the mavlink console (after testing the collision prevention) call:
listener obstacle_distance_fused 1
listener collision_constraints 1

and let me know the results.

@Jetson-Nano

voxl-px4_1.14.0-2.0.142_arm64.deb

Google Docs (drive.google.com)

I attached the link above, I am using parameters:

MPC_POS_MODE: Simple position control
CP_DIST 1.5 m
CP_DELAY 0.4 s
CP_GUIDE_ANG : 0 deg
CP_GO_NO_DATA: Enabled

@Jetson-Nano

I used VIO with FC, but the path from obstacle detection to Collision Prevention is unchanged between the 2 modes.

I used the mainline ModalAI PX4 SDK branch. I can share the built px4 deb build with you if that's helpful, but I would try changing the mpc_pos_mode parameter first on your current build to see if that fixes your issue.

@Jetson-Nano

I was able to identify the issue.

mpc_pos_mode - acceleration based doesn't call Collision Prevention in any of the newest PX4 builds..

You need to use mpc_pos_mode - Simple Position Control (0) or mpc_pos_mode - smooth position control (3).

I was able to test this on a similar setup, and confirmed that collision prevention only worked with the mpc_pos_mode indicated above, and notably did not with mpc_pos_mode acceleration.

@Jetson-Nano

Can you see if you are using the MO169 or the MO178?

@Jetson-Nano

What TOF sensor are you using for obstacle distance?

Just confirming, you are using the ARK Flow MR facing downwards just for optical flow and position hold, but not for collision prevention?

@Jetson-Nano

Looking through the PX4 codebase, the ARK Flow MR publishes to distance_sensor by default, not obstacle_distance. Have you made any changes to the codebase that would affect obstacle_distance or mounted any other sensors?

Also, how have you mounted the ark_flow_mr. Is it pointing downwards on the vehicle, or forward pointing or some other configuration?

Finally, have you tried setting the distance for collision prevention higher, and seeing how the drone reacts in that case?