-
Notifications
You must be signed in to change notification settings - Fork 188
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
ROS Humble workspace building fails after having updated it after a while #904
Comments
Is there a .zip file from version 2.2.9 (or another way), to build version 2.2.9, humble, from source? |
Hi Daan, are you referring to the 2.2.9 version of ROS 2 Humble or the one of the UR ROS 2 driver? |
Hi! You can use the version parameter in the ros2.repos file.
|
Hii, @bmdyrdal Thanks! I've installed the right version now. |
I was trying to make my code work and it was using a version of the driver from February 2023. By the way is it possible to permanently change the urdf of the robot and use it in the newest version of the driver for ROS 2 Humble? I located the xacro files in the share folder of ur_description package and edited it the way I would like, but the package does not seem to register the change. So, I wonder if it is not possible to edit it anymore or I am doing something wrong? Kind regards, Francesco |
Changes are only possible when you installed the ur_description from source. Source your workspace: This should work fine. To be sure of this you could see how the package is declared inside your package. You could also delete the ur_description package when you also installed it also from binary which shall mean you got the package installed multiple times which could cause problems. |
Hi Daan, I tried your suggestion. At the moment I have both the driver downloaded from binary and the one built from source, although for the moment I am not sourcing the one built from source. Thanks Francesco |
I had the same problem with building from source.
For the ur_driver you will get the errors indead, so the ur_driver package I installed is the previous version. So my 'src' includes all three packages. |
I have just tried what you said ("humble" branch for Universal_Robots_ROS2_Description, "master" branch for Universal_Robots_Client_library and "2.2.9" branch for Universal_Robots_ROS2_Driver; it also required me to download the ur_msgs package). When I build the workspace with these three within, I get the following error: --- stderr: ur_controllers Failed <<< ur_controllers [3.27s, exited with code 2] Has this ever happened to you? |
Did you do a clean build? For me this build gave no errors. |
Yes, I did. I ran: --- stderr: ur_controllers
Some of these libraries may not be found correctly. /home/francesco/workspace/ros_ur_driver/src/Universal_Robots_ROS2_Driver/ur_controllers/src/scaled_joint_trajectory_controller.cpp: In member function ‘virtual controller_interface::return_type ur_controllers::ScaledJointTrajectoryController::update(const rclcpp::Time&, const rclcpp::Duration&)’: Failed <<< ur_controllers [12.1s, exited with code 2] Summary: 12 packages finished [1min 52s] |
Hi @francescosemeraro, |
Good afternoon, I probably still have this issue, but thankfully I managed to find a turnaround. Instead of changing the urdf, I used an AttachedCollisionObject that mimicks my end effector with good approximation.However, it would be good to change the urdf as was suggested for future works. By the way, @VinDp , I have recently opened another issue related to the driver here, could you please help me out there? Thanks! |
Hi @VinDp, I am also using ROS humble and I am getting the same error regarding the publish_state function when I build. --- stderr: ur_controllers
|
At first I was using the So instead I also tried using |
Affected ROS2 Driver version(s)
2.2.9-1jammy.20231213.212659
Used ROS distribution.
Humble
Which combination of platform is the ROS driver running on.
Ubuntu Linux with standard kernel
How is the UR ROS2 Driver installed.
Build both the ROS driver and UR Client Library from source
Which robot platform is the driver connected to.
UR E-series robot
Robot SW / URSim version(s)
5.12
How is the ROS driver used.
Through the robot teach pendant using External Control URCap
Issue details
Summary
I am not able to build my unchanged ROS 2 Humble UR driver workspace.
Issue details
I had downloaded the driver almost a year ago and has functioned very well until now. Suddenly, I was not able to build the workspace anymore, as I was receiving a "Missing command interfaces" error, which is something related to the release itself. I saw there were some similar issues posted here around last May. I looked them up and tried to update everything, but I couldn't manage to make it work again yet.
I am using them most up-to-date version of ROS 2 Humble, and I still have the humble branch set on my laptop. When I try to build the workspace, I get the following error:
I am not sure why this is happening. If I revert the driver at 2.2.6, the workspace is built properly. But, if at that point, I run the "ros2 launch ur_robot_driver ur_control.launch.py" command, I get the missing command interfaces error from ur_controllers.
Can you please help me out? Thanks!
Relevant log output
No response
Accept Public visibility
The text was updated successfully, but these errors were encountered: