-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Robot not moving forward #2
Comments
Hello Kevin, could you share all the topics present at the moment and make sure your robot's /cmd_vel topic is present. And also make sure the Official Navigation stack is installed properly. You can verify the working of the Navigation stack by placing "2D Nav Goal" somewhere within the visible map (Grey Area) in RVIZ by then the Robot should be planning a path and moving towards the goal. |
Thanks for your response,
|
Your frontier points (/frontiers or /frontiers_array) aren't being published I guess. Because these frontier points array are sent as a sequence of goals to the Navigation Stack and then the robot starts to accomplish each goal in sequence. Could you please monitor both the topics mentioned above? |
Yes, /frontiers and /filtered_points are not published. And because of that the code get stuck at line 61 while loop in assigner.py Is it running fine at your end? |
Yes it does run in my end as it should. I back tracked publishing script filter.py which publishes the /filtered_points which is computed from the map data received. I probably feel the correct map is not received by this node. Are you getting a status printed in the terminal such as 'waiting for the map' (Line 87) or 'waiting for the global costmap' (Line 93) . Could you try to verify this. |
After running
(same message continue) |
I just checked ObstacleFree function in global_rrt_detector.cpp is giving some erroneous output other than 1 and -1. (same for local_rrt_detector.cpp) |
Can you please share your update on this issue? |
I'm with the same problem, same environment and same error. Did you found a solution? |
@rodrigoaantunes nope, not yet |
I have the same issue but the package worked fine earlier this day, now i can't get it to work [same environment and same error]. |
I have also faced the same problem. |
I have also the same problem. I used ROS melodic before and everything was fine, but now I am using ROS noetic and the robot is not moving anymore. |
The robot is moving right now, I fixed the issue. Could somebody please verify my solution? old filter.py:
new filter.py:
Finally the problem was that the publishing code do not get any centroid data after the while loop. Therefore the assigner could not send any move action to the mobile robot. |
@iory thank you for your PR but can you tell me why the change is only necessary for this part of the code ? |
For noetic, python3 is the default, and for melodic, python2 is the default. |
@kvnptl @Avi241 @SinanK94 @rodrigoaantunes Hello Everyone. I am facing the same issue can anyone please help me in finding the solution. |
Hey @MJ1307 . Thanks |
Hey, I have the same issue, my robot is not moving. I use Ros Noetic and have tried @SinanK94 code but it's not working for me. [filter-7] process has died [pid 6452, exit code 1, cmd /home/amaya/catkin_ws/src/ros_autonomous_slam/scripts/filter.py __name:=filter __log:=/home/amaya/.ros/log/3d4bcb8c-6975-11ee-b407-65d4e7192b1e/filter-7.log]. To what I understand I have issue with my filter.py et assigner.py files but I don't really what to do. Thanks |
same question: |
After setting everything up as suggested, turtlebot is not moving. It seems RRT node is working fine, but the robot is not receiving any commands on
/cmd_vel
topic.Please take a look at below video:
Please suggest some changes to make it work.
The text was updated successfully, but these errors were encountered: