-
Notifications
You must be signed in to change notification settings - Fork 63
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
WARNING: part X has no dynamics (maybe it is a surface) #48
Comments
Hello, |
Thanks for the prompt response. Not to share the link publicly, I sent it to your email. The correctly generated link in urdf looks like this:
while the newest version generates this:
|
I investigated and found the origin of the problem, I will come back to you when this is fixed (there is something inconsistent in Onshape API, so I need to talk with them before) |
…(see #48 and onshape support ticket)
I did a fix so that (The |
If it helps, I also had this issue just after trying the version that solved issue #46 |
Thanks for looking into it. I upgraded the onshape-to-robot with command But unfortunately, there is still the same problem with the part without the link to STL file nor other properties related to shape. |
Hello Indeed the STL API word also requires no escaping for slashes |
Still the same ;) |
It still generates the wagon link with zeros. I uninstalled and installed again the newest version, the same. Should I do anything else to update? |
Try to clear your cache with |
Yes! Clearing cache helped. It seems to generate correctly now, thanks! |
Ok, great! |
Hello,
Last year in December I generated correctly the urdf from my onshape model which contained faulty topology (although it looks good visually). The newest version of onshape-to-robot that I tried a few days ago shows a problem: WARNING: part X has no dynamics (maybe it is a surface). It creates the urdf file but without linking to an stl model. I generated again a correct urdf with v.0.3.4 so definitely something changed between the newest and that version. I am not sure if this behaviour was desired but at least it prevents me from using the newest version because I cannot change the imported model in onshape and I cannot find what causes the faulty topology.
The text was updated successfully, but these errors were encountered: