Felix Exner (fexner)
Felix Exner (fexner)
Yes, that would have been the suggestion I would have done. #35 comes closest to what you want to achieve. As you can see in the discussion there, this has...
Regarding the OP: Please do not use a wireless connection. @shrutichakraborty, @JohnL-Fxa Please open separate issues describing your setup.
Closing this due to inactivity and proposed solution. Please feel free to comment / reopen if the issue still persists.
I messed up the base branch, sorry.
I've been playing around with an RHEL workflow, but it seems to be failing on installing dependencies that should be there, see https://github.com/fmauch/Universal_Robots_ROS2_Driver/actions/runs/3536558367/jobs/5935691095. --- Edit: It should not necessarily be...
Thank you for your feedback. Just to ensure: You did see the big fat warning during startup? ``` [ERROR] [1697532375.479429100] [URPositionHardwareInterface]: The calibration parameters of the connected robot don't match...
I'll add an enhancement label to that but we currently do not prioritize implementing that.
I am confused. Are you using URSim or gazebo? If you are using gazebo then there is no need to actually use this driver.
As written in https://github.com/UniversalRobots/Universal_Robots_ROS2_Description/pull/70 I'd love to get this into https://github.com/UniversalRobots/Universal_Robots_ROS_Tutorials. I'm probably going to work on the tutorials next week.
Yes, dropping it from the driver makes sense and making the script generate good output if docker is missing seems like a fair solution. We'll have to remember installing docker...