Moving an assembly by click n drag
Not only are your videos set to "private" and cannot be viewed, but without having access to the actual design there's little we can do to analyze what's working and what isn't.
@suneelmo wrote:
How do I send my designs to you?
You can use the methods presented in this thread. For projects that use linked components it's best to share a link.
I am looking this now. Using that many linked components down to that many level is really inefficient and also entirely unnecessary.
Using an assembly with only one component in it is also not useful and often leads to assembly problems.
You also aren'y applying Fusion 360's R.U.L.E #1.
You can ground an assembly only under certain circumstance, which don't apply to the way you've assembled this.
You have to ground a component.
@suneelmo wrote:
Thx for going into the details and replying me. Pl tell me if what I have
inferred is correct.
1. To avoid so many linked components should I design more n more
components in a single file?
You've broken this design down into several smaller assemblies which is a good thing. It makes sense to link these into a master assembly, but consider that this master assembly is only an assembly in which you don't create any new components. That would also allow you to not use the timeline in that master assembly, which keeps it light and nimble.
Within each subassembly I'd not use any other linked components, unless there is the one or the other component that iOS aper of more than one subassembly.
When working in these subassemblies, following Fusion 360's R.U.L.E becomes very important in order for you to be able to organize the project and keep sketches etc. with the components they are used for.
2. I have seen Rule No.1 and 2, thx for it!!
3. I ground a component so that the rest of the assembly moves. If I
dont grnd then whole assembly moves when dragged. Please elaborate or send
a linked vdo for same.
Let me first explain what grounding actually does. It locks the origin of a component to the top origin of the design. When you create a componet, the only thing is has in it is an origin. At that time you can already ground it! Origins are very important in understanding grounding and joints.
Consider the following "design" with no geometry (pretty fancy huh ?):
That "Design" has it's own origin, which is the top level origin.
If you ground components 1 or 2 you lock their origin to that top level origin.
Now lets take a look at component 3 which is actually a component group (or assembly/subassembly).
Component 3 has it's own origin, but so do the subcomponents 4 & 5. When you start assembling things in that subassembly named component 3 you likely join component 4 to component 5 and that takes care of the two origins of these 2 components, but it does not lock either origins to the origin in component 3. If you now ground component 3 it locks that origin to the top level design, but the origins in component 4 and 5 are not locked to the origin in component 3, so when you drag either componet 4 or 5 you can still move them around in the viewport.
So you can now lock one of the 2 components, 4 or 5 to the origin ini component 3 by creating a rigid group of components 3 and 4, or 5. If you then ground component 3 you cannot drag 4 or 5 anymore, or only as much as the joints between them allow.
The other method is to simply not ground component 3 but wither 4, or 5 depending on what you want your assembly to do.
See my responses in Blue
Glad you wanted @schneik-adsk's and Mike proms class. It was in fact excellent.!
You can use either methodology, to achieve the goal.
As I understand it grounding removes components from any assembly calculations, which helps in assemblies with many components and joints.
You would also not use a rigid joint, but a rigid group.
Also, I would not necessarily ground the first component, you would not fix the first component in SW either. You fix that component which is your stationary base component in a given assembly.
Most folks never attempt what I have described in my longer post. I've only;e ever seen it covered in Kevins class and that grounding really lok only the origins together is not described in any documentation or in any tutorial I have ever watched.