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
In a trial to implement stop feature discussed in #36, I'm trying to utilize existing methods to achieve (1) stopping the arm that's moving according to the given trajectory, (2) canceling the given trajectory. (2) may or may not be critically in need depending on the situation.
I tried the following both on MoveIt! and hrpsys. Neither worked to my expectation. What's the right way to do so?
i think clear() clears queued waypoins, so you'd better to send command
with several way points using TrajectorJjointAction of ros interface and
MoveIt uses that.
On Mon, Sep 22, 2014 at 9:52 PM, Isaac I.Y. Saito [email protected]
wrote:
In a trial to implement stop feature discussed in #36 #36, I'm trying to
utilize existing methods to achieve (1) stopping the arm that's moving
according to the given trajectory, (2) canceling the given trajectory. (2)
may or may not be critically in need depending on the situation.
I tried the following both on MoveIt! and hrpsys. Neither worked to my
expectation. What's the right way to do so?
In a trial to implement
stop
feature discussed in #36, I'm trying to utilize existing methods to achieve (1) stopping the arm that's moving according to the given trajectory, (2) canceling the given trajectory. (2) may or may not be critically in need depending on the situation.I tried the following both on
MoveIt!
andhrpsys
. Neither worked to my expectation. What's the right way to do so?_MoveIt!_
Then move an arm by MoveIt!, maybe using RViz plugin's
random
feature. While the arm is moving, ran:_hrpsys_
The text was updated successfully, but these errors were encountered: