linked components won't update

[Anonymous]

One linked component in an assembly will not update, even though it says it it the latest version. I tried linking the same component again (after making changes), essentially making an identical component, and that one is the right version. Both (ostensibly identical) components say they are the same version, but they are clearly different.

I have tried opening the component in question and doing a "Compute All", saving, and updating references in the assembly and that didn't fix it. I also tried deleting my local 'F' directory, didn't help.

[lichtzeichenanlage]

Are both designs part of the same project?

[Anonymous]

Yes, both in the same project.

Here's a gif toggling between the two "identical" components in the assembly (dwc_probe_controller). The differences are in the positions of linked components in this component. Note the version number is the same on each, but one is clearly an older version before some things were moved.

As a workaround I would simply use the second component (that is up-to-date) but I've already referenced a bunch of features on the first one, which would break if I removed it. 

[TrippyLighting]

The version number in both cases is v28. The number behind the colon indicates the unique index number of the instance.

In order to determine what is going boron you may want to consider sharing the design.

It looks like you are wearing with a lt of linked components. That might not be the best workflow. Also, are you familiar with Fusion 360's R.U.L.E #1 ?

[Anonymous]

Thanks Peter. Here is the public link: https://a360.co/2Mi9i86. I don't know if this brings all the linked components with it, let me know if there's any issues. 

I'm linking components so they can be re-used in other designs (not locked up in a single file), which I assume is a best practice. Does Fusion 360 not like that?

Thanks for the link to the rules, but I'm not sure how they're relevant here? I can't activate a linked component from within the assembly it is linked to, although that would be a useful feature, and I know other CAD software supports such functionality.

I'm assuming this is just a bug (I've stumbled on a few), but it's definitely possible I'm missing something.

[lichtzeichenanlage · Accepted solution]

Are you missing position updates? If yes, the source of the problem might be, that you are not joining your components.

[TrippyLighting]

While the assembly you provided the link to is not the top assembly that's OK because I can already see what the problem is.

But let me first clarify the use of linked components. I general there is nothing wrong with linked components, but I wouldn't call that a best practice the way you are using them. Unless you intend to make any changes to the design of these linked composers, of loch most a re purchased items, there is really no need to maintain the link.

Here is a link to the handout for the Autodesk University Class I taught. It has a section on the use of liked components (and a lot of other useful, info).

The assembly you are using is completely unassembled. There is not a single joint in this assembly from the Assemble menu in Fusion 360. Also, using position capture to keep parts in place is definitely NOT a best practice but rather resides on the other end o the spectrum 😉

Maybe you can share what other bugs you've come across ...

---

[Anonymous]

Thanks, adding joints solved the problem. Although I still contend that this is a bug... there's no reason there should be two instances in an assembly that are different.

I find the joint tools in Fusion 360 to be clunky, although to be fair I have not fully gotten my head around them (though I have spent many hours trying). Thank you for the handout, I will take a look.

In general I feel that unless necessary, joints--or whatever a given CAD package calls them--should not be required. Exhaustively locking down all degrees of freedom for every component seems like a waste of time, unless there is some motion simulation, etc. In this case I used the "as-built joint" of the "rigid" type, but I feel that should just be implied when I leave a component somewhere.

Thanks again!

[Anonymous]

Thank you!

[TrippyLighting]

---

@Anonymous wrote:

Thanks, adding joints solved the problem. Although I still contend that this is a bug... there's no reason there should be two instances in an assembly that are different.

I find the joint tools in Fusion 360 to be clunky, although to be fair I have not fully gotten my head around them (though I have spent many hours trying). Thank you for the handout, I will take a look.

In general I feel that unless necessary, joints--or whatever a given CAD package calls them--should not be required. Exhaustively locking down all degrees of freedom for every component seems like a waste of time, unless there is some motion simulation, etc. In this case I used the "as-built joint" of the "rigid" type, but I feel that should just be implied when I leave a component somewhere.

Thanks again!

---

There is no bug. Just a different concept an a different workflow associated with it. It works fine once you get your head around it. That "assembly" of yours is really not an assembly, it's more a loose collection o parts that are floating in space without being attached to each other. But even after moving and locking them in place with the position capture feature , you can lock them in place using a single joint in the subassembly.

Simply right-click on the root of the browser and select "rigid group". That joint will take care of it!

[roy25G4T]

I have the same problem and all my components are joined

Error: Cannot Update components
No root component in Working Model. Can't check for Base Asset