Closed joaocabogon closed 5 years ago
Please clarify which branch you have built: master
or kinetic-devel
.
And please show us how you start everything.
Then tell us which controller type you have (CB1, CB2, CB3 or an e-series controller), which robot and which version of polyscope/system software.
I am actually using this branch: https://github.com/plusone-robotics/ur_modern_driver/tree/ur_moderner_driver
I am using: roslaunch ur_modern_driver ur5e_ros_control.launch robot_ip:=...
Using a UR5e arm with Polyscope 5.3.1
I am actually using this branch: https://github.com/plusone-robotics/ur_modern_driver/tree/ur_moderner_driver
Then I'm rather confused as to why you are posting an issue here.
We do not support forks of this repository.
I am using:
roslaunch ur_modern_driver ur5e_ros_control.launch robot_ip:=...
Ah. ros_control
mode.
It's possible that fork does not include #213, which could cause this.
But I have no idea, as I don't use that fork.
As you are using a fork and not the package in this repository, I'm going to close the issue.
Please go to the maintainers of the fork for support.
Feel free to keep commenting on this issue of course.
Commenting just to thank you and to say that #213 solved the problem.
BTW, the fork I am using does not have an Issues tab, that's why I posted here.
Hello,
When the driver is launched the arm, goes to the HOME joints configuration (all zero) in a dangerous way.
How can I launch the driver and keep the arm in the current configuration? In other words, I want to launch the driver without moving the arm.
Thanks