onshape-to-robot is not able write all the parts of robot in urdf
jayBhagiya opened this issue · 4 comments
Actually, I'm working on robotic arm, in which i have created all the joints and links but when i try to convert it in urdf, it is just converting some the parts of the robot.
below image shows my document in onshape. All the fastened and revolute are working fine, and i am also able to move my arm in assembly.
And this the photo of converting process. It has detected all the dofs but not writing them in urdf.
Though some of part of robot are not imported successfully, and is shows error like this "Contains faulty topology", which you can see in below image.
But this error containing part are being imported in porject folder and in urdf file as well. And also i am able to run this part in bullet, shown below.
That's why i am not able to get, where am i making mistake? So it would be really great if anybody can help me in this problem.
Thank You..
Hello,
Did you check the order of the mate connectors while creating revolute joints?
https://onshape-to-robot.readthedocs.io/en/latest/design.html#specifying-degrees-of-freedom
You can also have a look at this part of the tutorial:
https://www.youtube.com/watch?v=C8oK4uUmbRw&t=903s
If you want me to check, can you give me a link where I can make a copy of your workspace so that I can run onshape to robot myself to have a deeper look ?
I think i followed the same path as shown in the video and in the docs, first mate connector of child and then mate connector of parent. I also double checked it and tried it again, but i am having same problem.
So it will be great if you can check it once.
Here is the Link
Thank you.
@Gregwar are working on this problem? Just want to know that if you are not working on this, then I do not have to wait for your response.
Thank You.
The problem is solved.
The problem of not importing all the files is because there were too many parts in the assembly. So what I did Is created a subassembly for one or two parts, not more than that otherwise you may encounter the same error as above.
This is how my new workspace looks.
