avoidance collision prevention disabled
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
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! -
@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! -
@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!
-
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.
-
@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! -
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! -
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! -
This post is deleted!
-
@AP123 We don't have any known issues with the 4 in 1 escs. If you have an issue can you open a new thread?
This post is deleted! -
This post is deleted!
@AP123 This is a shot in the dark, but can you turn off your GPS and Mag and see if that works. We tried to do collision prevention with GPS on and we were getting these errors
-
@AP123 This is a shot in the dark, but can you turn off your GPS and Mag and see if that works. We tried to do collision prevention with GPS on and we were getting these errors
This post is deleted!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login