Skip to content
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

kr210_support: suspicious mass values in L150 xacro #36

Open
gavanderhoorn opened this issue Mar 11, 2016 · 4 comments
Open

kr210_support: suspicious mass values in L150 xacro #36

gavanderhoorn opened this issue Mar 11, 2016 · 4 comments
Labels

Comments

@gavanderhoorn
Copy link
Member

The inertial element of the KR 210 L150 xacro macro contains a suspicious value for the mass of base_link (here). The base is probably heavy, but 1572.9 Kg seems a bit much.

@gomezc: did you set this value on purpose (to fix the base in place in simulation, fi)? Or is this a solidworks error?

@gavanderhoorn gavanderhoorn changed the title kr210_support: suspicious mass value in L150 xacro kr210_support: suspicious mass values in L150 xacro Mar 11, 2016
@gavanderhoorn
Copy link
Member Author

Just noticed that all links have rather high masses specified. link_1 is 1300 Kg, link_2 still almost a 1000.

@gomezc
Copy link

gomezc commented Mar 11, 2016

@gavanderhoorn I believe it was SolidWorks generated. I did not use robot in simulation, so I don't think that's why I set a mass value there. Looks like I got it from a step file, so it's likely a solidworks error. I can't seem to locate the original file to verify that those are the masses in SW.

@gavanderhoorn
Copy link
Member Author

Lacking any way (or time) to get more realistic values for the masses and inertias, I think I'm going to remove the inertial elements entirely. This will make it harder to use the model in Gazebo, but it is missing the required dynamics elements already, so that doesn't work right now anyway.

I'll leave this open for now, so if anyone watching has objections to this, please speak up. Otherwise I'll update the macro next week.

@BrettHemes
Copy link
Member

To be addressed via #124

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants