Only base_link found in urdf file

[Omginmrobotics]

All the meshes are getting exported in meshes folder while the urdf file has only base_link. It only opens base_link in rviz then.

[Infinite-Echo]

I'm also experiencing this issue. I haven't spent a ton of time trying to figure out why yet. I plan on doing more experiments tomorrow. The example worked for me so I would assume it has something to do with a newer feature not being supported or the model not being set up correctly.

[Infinite-Echo]

Further experimentation has revealed to me that the issue likely stems from using as-built joints. I'm going to try to modify the script to see if I can get it to work with as-built joints as it would be much easier to use. I'll post my findings here.

[Omginmrobotics]

Yes even i found the same it was a problem with as built joint and normal joints is working fine and urdf was generated perfectly. Thank you!! Do make the changes for as built joints as it makes the process easier.

[KaushalkumarPatel]

Hi,

Right now It still produces only base_link in URDF file. Is the code still updated ? Did anyone has try and producing whole list of link in URDF ? @Infinite-Echo @Omginmrobotics

[Infinite-Echo]

I have a fork of the repo that supports as built joints. I haven't finished everything on it. You can try to use it. Switch to the other branch on my repo. Additionally, use this script to install numpy, scipy, and pyyaml. I ended up rewriting almost the entire repo so I don't plan on ever making a pull request to the main branch. Also, I designed it for ROS2 not ROS1 so you may have to change some things manually if you are still on ROS1. (Though ROS1 is out of date so I don't recommend it in the first place).

[Omginmrobotics]

Thank you for your update. I somehow went forward by creating urdf with just the "joints" and not using "as built joints". Here is one more issue I faced with the fusion2urdf plugin i.e. the inertial values above certain decimal places(i think it's around 10^-6) get neglected giving an error in a physics engine like Mujoco. So I had to manually insert the values from fusion properties. See if there is any fix for this issue.Also I will check with the as built joint fix on my fusion when I use it the next time.

[Omginmrobotics]

Thank you for your update. I somehow went forward by creating urdf with just the "joints" and not using "as built joints". Here is one more issue I faced with the fusion2urdf plugin i.e. the inertial values above certain decimal places(i think it's around 10^-6) get neglected giving an error in a physics engine like Mujoco giving an error. So I had to manually insert the values from fusion properties. See if there is any fix for this issue. Also I will check with the as built joint fix on my fusion when I use it the next time.

…

On Thu, Aug 15, 2024 at 12:39 AM Colin Fuelberth ***@***.***> wrote: I have a fork of the repo that supports as built joints. I haven't finished everything on it. You can try to use it. Switch to the other branch on my repo. Additionally, use this script <https://forums.autodesk.com/t5/fusion-api-and-scripts/how-to-use-modules-like-numpy-scipy-etc-by-conda-in-fusion-360/td-p/9355499> to install numpy, scipy, and pyyaml. I ended up rewriting almost the entire repo so I don't plan on ever making a pull request to the main branch. Also, I designed it for ROS2 not ROS1 so you may have to change some things manually if you are still on ROS1. (Though ROS1 is out of date so I don't recommend it in the first place). — Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BI2QSOBCCG2C5UWVGQ3M3JTZROTPFAVCNFSM6AAAAABISS3DJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBZGYZTGNZWGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- E mail Confidentiality Notice : The contents of this email message and any attachments thereof are intended solely for the addressee(s) and may contain confidential and/or privileged information. If you are not the intended recipient of this email message and/ or their authorised agent, or if this email message has been addressed to you in error, please immediately alert/ notify the sender by replying to the email and then permanently deleting this e-mail message and all attachments thereof from your system. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, distribution or storage of the contents of this e-mail message and/ or its attachments thereof, in any manner whatsoever, in whole or in part, is strictly prohibited.