avoidance collision prevention disabled
-
This post is deleted! -
This post is deleted! -
@AP123 might be worth trying this to see if the voxl-vision-px4 is handling the avoidance data correctly: https://docs.modalai.com/voxl-vision-px4-collision-prevention-0_9/#debugging-collision-prevention
-
This post is deleted! -
@AP123 When you click on Not Ready does it give you any more info?
-
This post is deleted! -
@AP123 What hardware setup are you using? One of our drones or a custom setup?
-
This post is deleted! -
@AP123 It's possible, I would take a look here as well for some relevant info: https://docs.modalai.com/configure-extrinsics/
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
@AP123 I'm at the end of my personal knowledge with VOA, I'll see if I can tag someone in
-
This post is deleted! -
@AP123 Hey there. Are you running VOA against a stereo camera pair or via a ToF sensor?
If you run
voxl-inspect-points voa_pc_outand see data, then the voxl2 SDK services are good and generating the correct mavlink obstacle distance points to PX4. If not then there's a configuration issue.If that is good, then you need to make sure PX4 has
MPC_POS_MODE= Simple pos control or smooth pos control,COM_OBS_AVOIDis enabled,CP_DIST> 0 (e.g. 2) and you must have an established home position (or good position from qvio if that is the case). Typically an "obstacle system not ready" is due to the MPC_POS_MODE (I think we default to acceleration-based input).If all those check out, then it's likely missing a home position requirement in PX4 & not voxl, and we'll need to look that up.
-
This post is deleted! -
@AP123 We just released SDK 1.1 yesterday which contains a few months worth of bug fixes, I would recommend loading that and seeing if your issue is resolved
-
This post is deleted! -
@AP123 No, didn't realize you were tackling that as well. M0065 PWM support will be in SDK 1.1.1 and we're actively polishing / testing that release and hope to have it out in the next couple weeks
-
This post is deleted!