-
Notifications
You must be signed in to change notification settings - Fork 39
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
MoveIt! stop feature not working for NXO #284
Comments
I just tried it and it does not work for me either. But I have not tried to send cancel signal to corresponding topic. This means that you can not stop a movement or it is problem of the button of the graphical interface? |
I'm not sure what you're trying to say :) It DOES work for Pepper on simulator as the video referenced from the link I shared. |
It does work for UR10 robot in simulation.
Sorry, I'm trying to say that I had not try publishing in Instead, I have tested the same with UR10 robot (in this case publishing in |
Using simulation, I confirmed that
|
you have to merge start-jsk/rtmros_common#765 to enable this feature. |
I confirmed on simulation that with start-jsk/rtmros_common#765 the stop feature works as expected. Testing on real robots (ie. not just on simulation) is requested before that change to be merged start-jsk/rtmros_common#765 (comment), which doesn't seem to have happened since the date the pull request was opened back in 2015. If anyone, including @hectorherrero, is interested in testing this feature, we would appreciate and are gladly going to assist you. You can apply the change by like this for example.
|
We are very interested on testing this with the real robot. I will try to test this in the next weeks but I do not know if this feature requires a specific version of hrpsys/bridge on the QNX controller. Is there a version requirement on this side? |
Thank you for your considerations @hectorherrero ! UPDATE: This feature probably requires hrpsys 315.5.0 or higher. See #284 (comment) |
I have followed the steps you provide above, but trajectory execution does not work. I receive the following output:
The content of the HrpsysJointTrajectoryBridge log file (the others are empty)
|
Hi, this is just a report. I have same problem when I follow @130s 's instruction. MoveIt can plan the trajectory, but fail to execute. My error message on MoveIt! is different from @hectorherrero 's.
Using release package of rtmros_common, the robot can execute trajectories. Update: I confirmed it works fine in the simulator. |
As mentioned in start-jsk/rtmros_common#765 by @k-okada , hrpsys-base 315.1.9 and 315.2.8 don't have idl for the function 'setJointAnglesSequenceOfGroup'. I guess it is the reason why the real robot cannot execute trajectories. Is it correct? I don't know exact version of hrpsys in my NXO though. |
Sorry, I have to take back my comment #284 (comment) As I left a comment start-jsk/rtmros_common#765 (comment) I think |
OK, I'm clear 😄 |
I have confirmed as follows.
|
but real problem is not that
|
upated, start-jsk/rtmros_common#765 |
ok, created new PR for this -> start-jsk/rtmros_common#996, |
Hi, thank you for your effort. I tried it with the simulator. I have confirmed your branch code can interrupt the motion successfully, while the old (I mean, apt got) system cannot. I will try it with the real robot on my lab soon. Below is just a report.
And push rviz 'Stop' button while the motion is executed, the robot stopped immediately. Now on a new terminal to try with the old (apt got) system,
And we cannot stop the motion by pushing the 'Stop' button. |
Hi, I have confirmed the stop feature with the real robot (Nextage Open). I simply done:
|
Thank you @longjie for confirmation on the real robot. |
Just for info, I want to confirm that now the motion is interrupted when stop button is pressed. I have tested on real HiroNx robot. All is working as expected. Thanks for your effort!! |
This isn't possible yet using binary (latest available: v1.3.2). Assuming majority of users use binary of |
Stop button on RViz on MoveIt! plugin does not stop NEXTAGE for me.
The text was updated successfully, but these errors were encountered: