-
Notifications
You must be signed in to change notification settings - Fork 193
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
Add gp180 support #395
Add gp180 support #395
Conversation
Made robots use materials from that package so they do not conflict when using multiple arms.
2018000
to
7d08b75
Compare
@Doomerdinger: it appears this model has been constructed such that all I assume that's because Path Robotics is using a calibration procedure which is based on D-H? Unfortunately we don't use that in ROS, and I'd really rather see we keep the models compliant with REP 103 (and all other support packages in our repositories), which would mean X+ 'forward', Y+ 'left', Z+ 'up'. If that wouldn't be something you'd want to do, I'll change the |
Yes we use a calibration procedure based on DH. I based on the wording in REP103 I did not think that standard necessarily applied to joints, and was more for things like base links or flange, transforms with respect to some body. I could've sworn I saw some examples in this repository with joint rotating around the Z. Regardless, if this is not possible by default do you think there's some way this could be customized? I'd prefer to not have a fork for every robot we create/use, it will make it harder to make contributions back. Whatever the case I can switch them easily, but if you're already on it be my guest. I won't get to it until sometime next week. |
@gavanderhoorn Expanding on my last comment after looking at some robot models. It seems I may have misunderstood the meaning of REP-103. Based on the way the robots in other support packages are configured, it seems that that axis are oriented in such a way that "x forward" is always with respect to the robot base. I had assumed that "x forward" applied to whatever body that the transform represented. With that interpretation the "forward" direction for each part of the robot is a bit more ambiguous. In my models the X axis points "forward" and Y "left" with Z "up" in accordance with the right hand rule with respect to the axis of orientation of the joint. So positive rotation of the joint is defined by the rotation from positive/forward X, to positive/forward Y. I was actually a bit confused as to why the support packages in this project didn't use the Z axis to rotate around, since it seemed to comply with REP-103 as well as allow for usage of things like DH. Is there a systematic way determine which "body" a particular transform is relative to so that "x forward" can be set correctly? |
@gavanderhoorn if you have time, you mentioned you could do what is necessary to bring this up to snuff to get it into the main branch? I've had slim to no time to work on this stuff in quite some time. |
I'll try to get to it. Thanks for letting us know @Doomerdinger. |
Replacement: #479. Thanks for the initial work @Doomerdinger 👍 |
And apologies for taking so long to get this merged in. |
Squashed commits: * Added gp180 support. * gp180: decimate visual meshes a bit more * gp180: clarify which specific variants are supported * gp180: note the base model rotates around Z+ * gp180: recognise author of base model Co-authored-by: G.A. vd. Hoorn <[email protected]>
Added support for GP180.
See #375
Requires #378.