The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
If this callback is definitely not being called, then this looks like it is an issue with the http interface you've made in your class so technically not a ROS problem. Without seeing the rest of the class there's not much we can do.
Note, there's an unrelated minor bug in your code: Getting the initial point on the path should be:
self.x = msg.poses[0].pose.position.x
self.y = msg.poses[0].pose.position.y
| | 2 | No.2 Revision |
If this callback is definitely not being called, then this looks like it is an issue with the http interface you've made in your class so technically not a ROS problem. Without seeing the rest of the class there's not much we can do.
Note, there's an unrelated minor bug in your code: Getting the initial point on the path should be:
self.x = msg.poses[0].pose.position.x
self.y = msg.poses[0].pose.position.y
UPDATE:
The only thing I can think is that several path messages are being received at the very start and several callbacks are being executed. The unusual thing about the callback has a time.sleep(2) inside the loop meaning that it could easily take minutes to finish executing for a path with 60+ way-points. Try removing the sleep call and see how it behaves then.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.