Grounded Component Constantly Un-Grounding Itself!

[Anonymous]

I'm having a problem I've never seen before - I have a single component in a model that is grounded (a simple shaft, around which other components rotate).  But when I make ANY change to ANY part of the model that shaft becomes un-grounded.  I am left with an un-grounded component , even though there are one (or more) Ground operations on that component shown the timeline!  This is really frustrating!  Why is it happening?

Regards,

Ray L.

[davebYYPCU]

I have seen recommendations to Rigid joint that first component to the file Origin.

Otherwise, you might try a screencast or file export.

[Anonymous]

---

@davebYYPCU wrote:

I have seen recommendations to Rigid joint that first component to the file Origin.

Otherwise, you might try a screencast or file export.

---

A Rigid Joint to what?  This is the ONLY component in the assembly that does not move, so there is no other component to Rigid Joint it TO.   

What good is "ground" if it does not "stick"?

Regards,

Ray L.

[davebYYPCU]

Rigid joint that first component to the file Origin

[jeff_strater]

@Anonymous, can you share the model here + a screencast of the behavior you are seeing?  Is the component in an external design, or is it local to the design you are working in?  Are there more than one Ground or Unground features in the timeline?  Where is the Ground applied (is it at a sub-assembly level or at a leaf-level part)?  It's kind of hard to say what is going on without seeing the design itself.

[Anonymous]

Here is a simplified model, but it shows the same, if not worse, seemingly broken, ground functionality.  In this one, the very first component is grounded, except it's really NOT - it can STILL be moved around at will!

https://a360.co/2D194zL

Regards,

Ray L.

[lichtzeichenanlage · Accepted solution]

Here is a thread regarding  Ground vs As-Build-Joint the only (visible) difference is, that if you insert assembled designs into a new design, the ground doesn't work anymore. 

[lichtzeichenanlage]

More than one ground per component doesn't make sense to me EDIT:  and more grounded components neither.  Can you share the model or if not at least  screencast the problem?

[Anonymous]

---

@lichtzeichenanlage wrote:

More than one ground per component doesn't make sense to me EDIT:  and more grounded components neither.  Can you share the model or if not at least  screencast the problem?

---

I agree.  There should be only one grounded component in any design (at least that was my understanding).  The multiple grounds only occurred because the original ground becomes inactive, but remains in the timeline.  I noticed the component was no longer grounded, so grounded it again.  I eventually noticed there were several grounds in the timeline, and deleted all but the most recent one.  The "extra" ones have no effect whatsoever.

I have uploaded a simple design where I cannot get even a single component to be actually grounded.

Regards,

Ray L.

[Anonymous]

---

@davebYYPCU wrote:

Rigid joint that first component to the file Origin

---

How??  Joints only allow selecting components.  I see no way to select the origin as one member of a joint.

Regards,

Ray L.

[lichtzeichenanlage]

The root element is a component. Check my link and watch the last video. 

[Anonymous]

---

@lichtzeichenanlage wrote:

Here is a thread regarding  Ground vs As-Build-Joint the only (visible) difference is, that if you insert assembled designs into a new design, the ground doesn't work anymore. 

---

The first video in that thread seems to have solved my problem.  I can't say it makes logical sense to create a joint to the top level of the assembly being created, but it does do what I want.  Seems to me the "ground" functionality is of little or no use.  Not sure why it even exists...

Thanks!

Regards,

Ray L.

[lichtzeichenanlage]

Okay - I understand what you mean. And in this case I like to quote @TrippyLighting: "Grounding locks the origin (not the geometry) of the grounded component to the top level origin in that design".

And this might be the 2nd visible difference between ground and As-built-joint to the root component. The last on will also lock the geometry. 

[jeff_strater]

This is why I asked what level you had grounded.  Your design grounds a sub-assembly ("Firewall mount plate").  That sub-assembly is, indeed, grounded, and will not move.  However, you have not grounded the child component of that sub-assembly ("Component1"), so it is still free to move.

I went in and edited the "Firewall mount plate" design to make the root origin and Component1 origin visible, so that you can see that they are different components.  With the ground the way that it is, the sub-assembly is correctly grounded, and will never move, but Component1 is free to move.  If you ground Component1, then that will stay in place.  See the screencast below.

The underlying reason for this is because all Fusion sub-assemblies are inherently "flexible" - meaning that child components underneath a sub-assembly are free to move in the top-level assembly.  All of the suggestions in this thread about making a joint between a child component and the root of the sub-assembly are ways to make a sub-assembly be rigid.

screencast:

[lichtzeichenanlage]

I missed that. Well done!

[TrippyLighting]

---

@lichtzeichenanlage wrote:

Okay - I understand what you mean. And in this case I like to quote @TrippyLighting: "Grounding locks the origin (not the geometry) of the grounded component to the top level origin in that design".

And this might be the 2nd visible difference between ground and As-built-joint to the root component. The last on will also lock the geometry. 

---

No it does not. NO joint does that!

[lichtzeichenanlage]

Thanks for clarifying. I'm still struggling with that. h