Subassembly parts floating
If you are placing components, in your sub-assembly, and joining them with Joints, the sub-assembly should stay together when you insert it into another model. The only thing you will need to do is Pin (Ground) one component or add a Joint to another component in the assembly. Attach one of your sub-assemblies and let the Forum users take a look.
If you do not know how to attach your Fusion 360 model follow these easy steps. Open the model in Fusion 360, select the File menu, then Export and save as a F3D or F3Z file to your hard drive. Then use the Attachments section, of a forum post, to attach it.
John Hackney, Retired
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@bwat009 wrote:
Quite often I've noticed subassembly parts are floating in space when I insert the subassembly into a higher level assembly. I've been fixing it by going to the subassembly and making all the parts a rigid group, but was wondering if there is something I'm missing. It doesn't seem like making it a rigid group should be necessary. I'm sure this is something easy.
Making the components in a sub-assembly a rigid group (or with other joints) IS the right way to do this. If you are creating a sub-assembly that you expect to be rigid, you need to tell Fusion that it is rigid. By default, Fusion assumes that all components are free to move, within the sub-assembly, and at a higher level of component.
Jeff Strater
Engineering Director
@bwat009 wrote:
I am using rigid joints to anchor the parts. I noticed though that the ones that still float are instances of patterns. Is this normal?
Yes!
Patterns only place objects (bodies, components) but don't join/assemble them. Assuming you properly joined the seed instance, use a rigid group to join the patterned instances and the seed instance.
@bwat009 wrote:
I'm unable to attach examples because the models are proprietary.
If you still can, you may ant to reconsider working with proprietary models until you have better knowledge of basic Fusion functionality. It is very difficult and often impossible for us in most cases to provide help without a model.
@bwat009 wrote:
...It surprises me that the instances wouldn't be fixed if the parent object is joined...
That catches many users off-guard as it is different at least for any of the other CAD systems I know and have worked with. There is a workaround possible using the new ground-to-parent feature that avoids having to rigid-group the patterned instances, but I'd have to see the model to see if its feasible 😉
