Closed BlueeHole closed 3 years ago
If you reduce the velocity limit to a small value, remember also to reduce the acceleration, otherwise there may not be feasible states.
If you reduce the velocity limit to a small value, remember also to reduce the acceleration, otherwise there may not be feasible states.
Thank you very much! I've retried and it sometimes works. However it's a little hard to adjust the velocity and acceleration by a proper degree at the same time.…
May be you also need to change the search/resolution to a smaller value, to ensure that the motion primitives do not end up in the same voxel.
May be you also need to change the search/resolution to a smaller value, to ensure that the motion primitives do not end up in the same voxel.
Thank you very much ! I will take consideration of it.
Hello, sorry to bother, but I encountered with a disgusting problem.
The original max_vel parameter is 3.0, everything is ok. But when I set the max_vel parameter to 0.5, kino_replan will report: kino search fail( open set empty, no path! ), while topo_replan will crash, reporting a Segmentation fault. The output is below:
(This is the origin version: only on simulation using rviz, no mavros and no other things)
Any solutions will be appreciated.Thanks a lot !