-
Notifications
You must be signed in to change notification settings - Fork 412
Driver does not build on Melodic due to "SetPayload" service #235
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
Comments
Did you use my fork of the |
No I actually used the main repository. It is a bit confusing that now three versions of ur_msgs exist. But that should solve the issue, thanks. |
I am facing the same issue and could not figure out which fork I must use for Melodic?? The current version of the ur_msg repository has a variable name Mass And the hardware interfaces file in is still using payload as variable |
@anshulpaigwar Please follow the instructions in the README file |
My environment is: Following README file but still got errors: What's wrong? @fmauch Thanks |
I only followed the instructions I think my previous trouble was caused in universal_robotTutorials |
@suc1 please do not hijack an old (and closed) issue for your problems. You can link to related issues, by simply writing
|
It seems like the driver does not build on melodic (and kinetic) currently because of #50 . When using the universal_robot metapackage, the "SetPayload" service is missing the "center_of_gravity" member. When using the standalone ur_msgs package, it does not build because the "payload" member was renamed to "mass". Or is this already solved in a branch?
The text was updated successfully, but these errors were encountered: