You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thank you for the great tool.
I have a tiny issue, I am trying to go to a point with the package, and after reaching there, I give another point. You can think of it as a loop between the corners of a triangle shape. I want to pause while going to these corners from time to time.
The problem is when I publish 'true' data to the /pause topic, I can see the interpolator marker stop, and the robot also stops when reaches that position. There is no problem when I publish a 'false' data after a few seconds but, If I wait for a longer time, as 30-60 seconds, then publish the 'false' data, the interpolator assumes that it has arrived and starts from the next corner. It also publishes a 'true' to /trajectory_finished before doing this.
Is there an internal timeout for this that I can change, or am I doing something wrong?
The text was updated successfully, but these errors were encountered:
Interesting...
There is no additional timeout present that I am aware off.
When you resume successfully, does the marker start at the correct location again?
No, it starts from the next trajectory to be followed, thus making the robot rush to the start point of that.
However I tested with a higher spec pc and been testing for a while now yet the same thing didn't happen even once so I guess it could be because of that.
Hi, thank you for the great tool.
I have a tiny issue, I am trying to go to a point with the package, and after reaching there, I give another point. You can think of it as a loop between the corners of a triangle shape. I want to pause while going to these corners from time to time.
The problem is when I publish 'true' data to the /pause topic, I can see the interpolator marker stop, and the robot also stops when reaches that position. There is no problem when I publish a 'false' data after a few seconds but, If I wait for a longer time, as 30-60 seconds, then publish the 'false' data, the interpolator assumes that it has arrived and starts from the next corner. It also publishes a 'true' to /trajectory_finished before doing this.
Is there an internal timeout for this that I can change, or am I doing something wrong?
The text was updated successfully, but these errors were encountered: