-
Notifications
You must be signed in to change notification settings - Fork 43
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
Support multiple robots #21
Comments
Hi @mhubii, Really looking forward to this enhancement! My group and I, at Aalborg University, are currently working on implementing two Kuka IIWA 7s on a 'torso'. As such, the support for multiple arms is a necessity for us. :) So far, we have made a custom URDF, with the torso and both of the robots and reconfigured moveit with the setup assistant. Sadly, however, even though the simulation shows the correct URDF with both robots, it cannot plan trajectories for any of them. It would be highly appreciated if you could give us a few pointers as to what need to be changed in order for two robots to work concurrently. |
Hi @TheMipmap and sorry for the late response. This is actually functioning now. I can respond in more detail tomorrow. But in essence you can
when you launch this stack, you can amend the launch with port_id:=30201. With regard to moveit, it somehow has issues with namespacing multiple robots. But we can chat about that |
Supported since #121. Will open new issues indicating necessary documentation and the issues regarding moveit in multi-robot tomorrow |
Thanks for the reply @mhubii! Looking forward to the documentation regarding a multi-robot setup! :) I will try setting it up with the method you described above. If you have time, a detailed description of the moveit part, would be appreciated! :) |
May I kindly ask you to open a new issue regarding missing documentation? That would be great. Thank you for the help @TheMipmap |
Of course, I'll do that! :) |
Investigate support for multiple robots.
IP and Port: The robot's IP address and port, that this interface tries to connect to are specified in fri_hardware_interface.hpp. These are set as parameters in the lbr.ros2_control.xacro. The hardware interface is loaded as plugin and has thus access to these parameters. Check access of these parameters through launch files.
Namespaces: Check the namespaces
The text was updated successfully, but these errors were encountered: