-
Notifications
You must be signed in to change notification settings - Fork 54
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
Frames not detected off root assembly #78
Comments
rsinnet
pushed a commit
to MisoRobotics/onshape-to-robot
that referenced
this issue
Jul 4, 2022
Before this commit, frames that were present on a subassembly that is not the main trunk assembly (first in the list in Onshape) would not be added to the URDF. This was occurring because such a frame was being associated to the parent subassembly as read in from Onshape, BUT this fails to account for the reassignment process for non-trunk parts. Refactor the functionality for appending frames to improve readability and reduce duplicate code. Fix the bug by looking up the proper parent assignment. Add print statements to improve diagnosability. Fixes: Rhoban#78
rsinnet
pushed a commit
to MisoRobotics/onshape-to-robot
that referenced
this issue
Jul 4, 2022
Before this commit, frames that were present on a subassembly that is not the main trunk assembly (first in the list in Onshape) would not be added to the URDF. This was occurring because such a frame was being associated to the parent subassembly as read in from Onshape, BUT this fails to account for the reassignment process for non-trunk parts. Refactor the functionality for appending frames to improve readability and reduce duplicate code. Fix the bug by looking up the proper parent assignment. Add print statements to improve diagnosability. Fixes: Rhoban#78
rsinnet
pushed a commit
to MisoRobotics/onshape-to-robot
that referenced
this issue
Jul 4, 2022
Before this commit, frames that were present on a subassembly that is not the main trunk assembly (first in the list in Onshape) would not be added to the URDF. This was occurring because such a frame was being associated to the parent subassembly as read in from Onshape, BUT this fails to account for the reassignment process for non-trunk parts. Refactor the functionality for appending frames to improve readability and reduce duplicate code. Fix the bug by looking up the proper parent assignment. Add print statements to improve diagnosability. Fixes: Rhoban#78
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider the following connection:
ROOT_ASSEMBLY -(dof_slider)-> ASSEMBLY_A -(frame_foo)-> ASSEMBLY_B
In the above case, ASSEMBLY_B will be omitted properly from the URDF in terms of meshes. HOWEVER, the expected frame does not appear.
FYI I fixed this in our fork by looking up the reassigned assembly after the assignation spreading step instead of the one returned by the API (which may be overwritten).
The text was updated successfully, but these errors were encountered: