avoidance collision prevention disabled
-
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! -
@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! -
@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! -
@AP123
you can turn it off with has_gps and has_mag parameters I believe.
Yes, i believe this might be a PX4 thing. Might need to troubleshoot that PX4 bug in order to resolve -
Hi there, looks like there's some confusion with what mode is being tested. Here's some clarification. PX4 has 2 approaches to handling obstacle distance data:
a. Obstacle Avoidance(OA) feature which stops the aircraft if object detection occurs from the voxl-voa service. This requires CP_* parameters set that you can compare with your drone listed here based on your application.b. Collision Prevention(CP) feature, which not only includes OA, but also rerouting capability in all autonomous modes (position, alt, mission, offboard) and leverages the same voxl-voa service. This requires not only the CP_* parameters but also requires COM_OBS_AVOID = enable.
If your application requires (a), you can leave com_obs_avoid = disable and OA should work out of the box as is. If your application requires (b), then we have discovered a software bug in the VOA service. And the main reason you get the "collision module not ready", no arm possible. It has been corrected [code here] and binaries will be available in our gitlab daily builds shortly.
