-
Notifications
You must be signed in to change notification settings - Fork 52
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
OPW kinematic parameters #61
Comments
We've already done that for some support packages over in So: yes, we can do that, and we already have that in place for others. |
Fantastic; I'll close this issue since it's already been addressed. I have the parameters for the R2000iC165F; I can add those in a PR with the 125L variant. Is there a convenient way to reference this file in a MoveIt |
Could you please submit those in a separate PR? That way we keep PRs on-topic as much as possible.
Since moveit/moveit#1997 there is: in the UI of the MSA you can specify an "additional file" to load whatever parameters you need, which gets added to planning_context.launch. If you have an existing MoveIt configuration pkg, you could just add the |
Would it be beneficial to store OPW kinematic parameters in a file in the support packages for robot variants? They're not necessarily hard to set up (and the MoveIt OPW kinematics plugin has some helpful sanity checks for the parameters now), but it can be a bit confusing for those not familiar with the parameters or the means of figuring out what the parameters should be.
The text was updated successfully, but these errors were encountered: