-
Notifications
You must be signed in to change notification settings - Fork 14
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
Make example MoveIt 2 configuration package(s) available #74
Comments
Note: while the default would probably be Python launch files, XML based launch files are still supported, and might be easier to understand. Python launch files can quickly become very complex, especially since they don't directly get executed, but model a declarative description of what |
@Aaron-Levan, did you keep any of your previous work on this topic? |
No, I had everything in a VM that is, unfortunately, no longer with us... |
I keep putting this on my TODO, but it's too long already .. I have working package(s) for my GP25 + TSL1000, but it's for / from a very old version of MoveIt and not really suited for distribution. |
Hi, We have a GP25 in our lab that we have managed to get the MotoRos2 driver running on it. Best Regards |
Unfortunately I haven't had time to look into this yet. It shouldn't be too much work to put something together, but as I have a basic setup working, it hasn't been a priority for me so far. The main thing to keep in mind is I'll see if I can dig that out and post it here later. |
Hello, How do I make the moveit 2 launch files talk to motoROS2 on the robot controller? Any help is appreciated, |
We have some info in Usage - with MoveIt. Would that be enough? Note that MoveIt will not care about TF. It ignores it completely for basic usage. |
We are more wondering, what moveit files need to be launched. With ROS 1 we had followed the example of planning execution launch that was provided by the ROS industrial group: http://wiki.ros.org/Industrial/Tutorials/Create_a_MoveIt_Pkg_for_an_Industrial_Robot?action=AttachFile&do=view&target=moveit_planning_execution.launch.txt. I'm wondering now if there is a similar setup for motoros2. The MSA(moveit setup assistant) generates many files, but we aren't sure which one to launch when running with real robots. |
I keep saying I'll try to make something available, but due to time constraints, I never get to it. So I can't / don't want to promise anything, but I'll again try to look into it. As I wrote above: the majority of the output of the MSA, at least when it comes to configuring the the driver interface can be ignored, as it's all |
MoveIt 2 is non-trivial to configure.
Especially when not using
ros2_control
, as almost all available documentation and examples assumeros2_control
is being used.We give some hint(s) in the
README
(Usage - With MoveIt), but that's really rather minimal, and assumes an already working MoveIt 2 configuration package has been created, and just needs to be modified for use with MotoROS2.Providing an example, known good configuration package would help users set up something for their own / other robots.
The text was updated successfully, but these errors were encountered: