-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support and moveit files for Yaskawa CSDA10F #32
Support and moveit files for Yaskawa CSDA10F #32
Conversation
@shaun-edwards @gavanderhoorn can you guys help me out here. I am trying to make a pull request for the support and move it files for the Yaskawa CSDA10F. However, the Travis CI builder fails for the kinetic distro and passes for the indigo distro. I have no problem running path planning in both indigo and kinetic (I have check them in both versions). |
@amrith1007, the roslaunch check fails with this error:
I'm not sure why this fails in kinetic only. Does anything in this error message catch your eye? |
@shaun-edwards @amrith1007 I have corrected little details on the .xacro files, clean up some files that weren't used and added some comments. The CSDA10F packages (support and Moveit configuration) are only being pushed to the Kinetic-Devel...that is why Indigo-devel was passing Travis CI test, but in theory I don't see a reason why it wouldn't work on Indigo once push to this branch. |
Good day @shaun-edwards @gavanderhoorn, this is just a friendly reminder for the pull request, we are using this files for the integration of the CSDA10F robot for a German Company and would like to have the experts opinion on it. As a matter of fact I know that @amrith1007 change the tool_0 link position, can you please push that change my friend. Thanks to all, sorry to bother. |
Update the position of tool_0
As of now, the URDF and the moveit files for the CSDA10F have been tested on the kinetic-devel. Awaiting confirmation or comments from the experts :) Thanks in advance. |
@amrith1007, sorry for our delay in getting back to you. I took a quick look. I'm not familiar with all the details of dual arm setups, so I wouldn't consider myself an "expert". The only "issue" I notices was that you chose a different naming convention for joint from our other robots. See bmda3. Did you have a particular reason for doing this? |
Hi @shaun-edwards, I believe @amrith1007 based the joint naming convention following the already accepted motoman_sda10f_support/config/joint_names_sda10f.yaml, since both robots are quite similar. |
@Danfoa, thanks for the pointer. Thanks for the contribution....accepting. As this is a the "experimental" we will let this mature in this repo for a bit. However, if you should want to push this into the main motoman repo, please let me know. |
@shaun-edwards thank you very much, We will be testing the packages with the real robot soon, when we confirm everything is ok i will push again here and probably in the non experimental repo too. |
@shaun-edwards thank you very much for the merge. As Daniel said, I stuck to the same naming convention as the SDA10F (thanks for clearing that up @Danfoa ). As you said we could push it onto the main motoman repo when the testing with the real robot is done. Cheers guys ! |
No description provided.