-
Notifications
You must be signed in to change notification settings - Fork 25
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
Issues Launching Dual Arm Configuration with KUKA Drivers: Namespace and Controller Issues #198
Comments
We managed to load and get joint states from both robots at the same time by changing the Both arms activate using the lifecycle command The lastly activated control node stops the other external control channel:
Additionally this is also the case for the provided dual arm example launch file which doesn't include MoveIt. An update on this issue could be very useful on moving on with the dual arm setup. |
Thanks for reporting this issue, we previously did not have problems with the dual arm setup without moveit, we could launch the example, activate both drivers and move both robot with the |
Thanks for looking into it. I will provide a more detailed log for running the given We have a setup with 2 iisy11 robots and have modified the launch file with the robot models and proper IPs for our network like so:
Some times we are able to connect to both arms by configuring and activating all the controllers like this:
After activation, both arms appear as TF in RViz but the rqt trajectory tool fails to receive the robot description for either of the controllers and crashes so we cannot control them without MoveIt. Here is a full log of the terminal window. Please note at the end that after the activation of the test2 arm, the other external control crashes, thus causing us to lose control. This happens both on the example launch file and on our launch file with and without MoveIt.
|
Hi, could you find the reason for the deactivation? I started to rework the example, as the current version indeed has namespace issues. The feature/multi_robot branch currently works for me with
I did not have the chance to test it on real robots yet, is it possible, that using the same port for both causes the deactivation? |
We are experiencing significant difficulties in setting up a dual arm configuration using the provided KUKA launch files and drivers. We have both robotic arms integrated within a single URDF with the appropriate hardware systems configured, as we have additional links in the kinematic chain that are fixed and currently hardcoded.
What We Have Tried:
Despite these attempts, we have encountered persistent issues such as controllers failing to load, errors relating to missing type definitions, and namespace conflicts or the control node claiming all hardware resources from the whole URDF instead of only the namespaced one.
I will add our launch file for reference, as well as the trace logs from the command line, detailing the exact commands we used and the resulting error messages. Any insights into the proper setup or configuration adjustments that could help resolve these issues would be greatly appreciated.
Launch File:
controllers.yaml
Driver Config YAMLs:
Additionally we also have the same files loaded for the right arm joints and passed to the right control nodes.
For each arm in our URDF we load the appropriate ros2_control like so:
What we have noticed is that each control node launched claims both left_system and right_system so all the resources are claimed multiple times regardless of namespace setup and the same happens with the provided multi_robot_startup.
Below is the commands we execute and the relevant terminal trace:
Always the arm that is launched second from the launch file fails, and if the IPs are switched, the arm that previously couldn't connect, now connect normally (even though both connect individually).
The tracelog:
The text was updated successfully, but these errors were encountered: