Assembly Extruded Cut/hole/fillet/etc.

Assembly Extruded Cut/hole/fillet/etc.

Anonymous
Not applicable
6,645 Views
16 Replies
Message 1 of 17

Assembly Extruded Cut/hole/fillet/etc.

Anonymous
Not applicable

Hi,

 

Why do we have to break the link to inserted components to make an assembly cut, hole, fillet, etc. that goes through all or selected components?  There are many times in a production situation when you assemble, then drill or cut multiple components - say a weldment.  You still buy the component as designed, then modify the assembly.  By breaking the link, you can't later modify the component by itself and have it update in the assembly.  SolidWorks, ProE/Creo, Catia, and many other CAD programs have the ability to make assembly features.

 

Or am I doing something wrong?

 

Steve

Accepted solutions (1)
6,646 Views
16 Replies
Replies (16)
Message 2 of 17

jeff_strater
Community Manager
Community Manager
Accepted solution

No, you are not doing anything wrong.  Fusion today does not support assembly features.  Somewhat surprisingly, we have not heard a lot of requests for this so far.  I would recommend creating an idea on the Fusion 360 Idea Station for this, and see what kind of response it gets from the community.  If enough others share your requirement, then it will become a priority.

 

Thanks for your post,

 

Jeff Strater (Fusion development)

 


Jeff Strater
Engineering Director
Message 3 of 17

TrippyLighting
Consultant
Consultant

@jeff_strater

I have a whole list of suggestions I could make that have to do with assembly and a good number of other areas.

Heck,  there are some I already have made that have gained no traction. There are some inherent disadvantages to how the Idea Station is currently structured 😉

 

However, the ability to have better access to linked components and assemblies is certainly high on my list. I agree with @Anonymous that the area of linked assemblies is certainly not currntly used to it's full potential.


EESignature

Message 4 of 17

Anonymous
Not applicable

 

 

Thanks!  I've submitted the idea.

Steve

 

Message 5 of 17

jeff_strater
Community Manager
Community Manager

@TrippyLighting, I agree on the use of referenced components and assemblies.  You should be able to make changes from the top level.  Believe it or not, this is high on our list, but it's a bit of a difficult problem to solve.  I'll resist the temptation to explain why...

 

One point here, though, that I would like to make:  There are two very different operations that are possible.  Internally, we call these "Component Features" and "Assembly Features".  The differences are a bit subtle, but important, and only show up if you have multiple instances of a component in your top-level assembly.

 

A "Component Feature" refers to a feature that is owned by the assembly, but which affects all instances of a lower-level component.  Imagine that you have an array of instances of a simple block component:

component pattern 1.png

 

If you sketch on the face of one of these, and draw a circle:

component pattern 2.png

 

Then, do an Extrude Cut, a Component Feature will change the definition of the shared geometry by all of the instances of the component:

component pattern 3.png

 

This is what you can do, today, in Fusion, if your components are all local to the design.  If they are external references, you cannot.  This is one project - to implement this for external components.

 

But, what I believe @Anonymous is asking for is what we call an assembly feature.  In an assembly feature, the extrude only affects the instance it interacts with.  Fusion does not do this today, but this is kind of what it would look like if it did:

component pattern 4.png

 

This very accurately mimics a common manufacturing workflow.  You buy instances of components, assemble them, then modify them in their assembly configuration.  A good example is assembling a couple of standard plates, then drilling a hole in them to bolt them together.  The holes are not necessarily in the same place on each plate, so they cannot be in the component itself.  This is a separate project for us.

 

Hope that clarifies the differences for everyone.

 

Jeff

 


Jeff Strater
Engineering Director
Message 6 of 17

Anonymous
Not applicable

 

 

Well, said Jeff.  The assembly feature is exactly what I'm looking for.  Looking forward to seeing it in a future revision!

Steve

 

 

Message 7 of 17

Anonymous
Not applicable

This is a feature I would use and would like to see it implemented, and here's an example of a typical cut I would make, but fails.

Thanks so much.

 

cut reject.JPG

Message 8 of 17

Anonymous
Not applicable

So I know this is 3 years later but rather than making a new post I though I would try a response here first.  Where are we on this concept? Being able to Assembly cut only particular instances of components in an assembly?  This is a very common workflow if you ask me.  I really want to drill a hole in only this instance via an assembly cut.

 

Capture.PNG

 

Please let us know if you have found a solution for this.  To be honest, it is a matter of using this product or not in the long run. 

0 Likes
Message 9 of 17

lichtzeichenanlage
Advisor
Advisor

@Raymondfox5: Instead of "Copy/Paste" a component just "Copy/Paste New" the component. The first action will create an instance that shares everything with the source, the second action duplicates each and every attribute of the source and you can do what you want with that copy.

 

 EDIT: I know that's a workaround but perhaps valid for you.

 

Screencast will be displayed here after you click Post.

f582a3d6-56fd-4ea4-8fa7-062740937955

 

0 Likes
Message 10 of 17

Anonymous
Not applicable

This may be in the wrong place - however, I see that this item is marked as solved.  I have the same problem that is described, but I cannot find the actual solution.  I only see that it was suggested to submit an idea to the idea station.  Am I missing the solution? I see items marked as solved quite frequently - but they are actually only pushed to an idea for future consideration - I am new to the forum, so I appologize if the answer is obvious - is there a way to find the actual solution (besides paste/new).

0 Likes
Message 11 of 17

chrisplyler
Mentor
Mentor

 

Work-around idea...

 

Let's say you have four instances of a linked-in Component - a steel plate for example - in your assembly, and you want to drill a hole through one of them.

 

Break the link on that one instance. Change the name of this unlinked Component to something that indicates the change. Drill your hole through it. Export this (now unique) Component back out into the same folder the original is in, using a file name. Now in that folder you've got TWO files; the original undrilled steel plate AND the drilled steel plate.

0 Likes
Message 12 of 17

TrippyLighting
Consultant
Consultant

@Anonymous My recommendation would be to not work with linked components if it is not absolutely necessary. I tought a class at Autodesk University covering reasons when and when not to use linked components. Here is a link to the handout.

 

If you don't work with linked components, some of the problems posted above can be addressed with the "configurations light" approach also described in the document.


EESignature

0 Likes
Message 13 of 17

Anonymous
Not applicable
I really like the configurations light workflow and will use that in the future. However I don’t believe that it solves my problem of not knowing I needed an assembly feature until after creating 12 copies that I initially believed would always be the same. I may start over with the suggestion above.

I am however still a bit confused why questions are marked solved when they are only sent to ideas. These work arounds are great if you know ahead of time that changes need to happen. My humble opinion of truly solved would be a solution to adding assembly features after assembled components are already in place - not that the team is working on it. By no means am I minimizing the effort it would take to solve this - only suggesting that it should not be marked solved. At least then I and others would know to stop looking and spend time re-doing the design with a workaround.

Help is much appreciated as always.
0 Likes
Message 14 of 17

TrippyLighting
Consultant
Consultant

@Anonymous wrote:
 However I don’t believe that it solves my problem of not knowing I needed an assembly feature until after creating 12 copies that I initially believed would always be the same. 



No, it certainly does not solve that and my suggestion was not intended as a replacement for the assembly feature workflow described above. It only helps in some cases and might bridge a gap until such a feature might be developed. I don't see that coming any time soon though.

 

As to why threads are marked as solutions. I sometimes do this if there's really not anything to answer anymore. If a thread contains a new idea it should be posted in the Idea Station.


EESignature

0 Likes
Message 15 of 17

lichtzeichenanlage
Advisor
Advisor

@Anonymous: I do see your point and I do understand it. That said doesn't mean that I can agree to your request threads like this shouldn't be answered. This might be because of my background (software architect, developer) that includes lots of requirement-, scope- and user management. Here some thougts

 

  • Technically the question from the TO was answered. He is not doing something wrong, he understands the product and the product he references to. But the function just does not exists in Fusion 360. That's an answer. Perhaps not satisfying but IMHO more than valid. Some members came up with workarounds. workarounds by definition are not perfect or satisfying but still might help in some cases. I'm not aware if the TO accepted the solution or an admin did it, but I'm 'closing' my own threads if I got a valid answer. Sometimes you've to fight for it, but if the conclusion is a missing function, just not possible or a bug it's an accepted answer for me. And if my mind does not trick me, I had all variations in my threads.
  • I can understand that admins do close threads, because for me as an user un-maintained threads are horrible. Perhaps this is my professional background and my German background, too 😉 I'm not a fan of it, but I can understand it. I would prefer TOs would be more responsible in some cases
  • It would be great if TOs would create posts in the IdeaStation if they have better solutions or change requests. Perhaps it was just fine for them and they do not see the need for the IdeaStation. And if you're not happy with a solution and you have a good idea it would be great if you would create the post in the IdeaStation. And think about marketing and cross-link the post in the related thread ;-).

 

Message 16 of 17

smkhalsa
Explorer
Explorer

@jeff_strater did this feature ever make it onto a product roadmap? If so, any update on the status? 

0 Likes
Message 17 of 17

jeff_strater
Community Manager
Community Manager

no, assembly features (features affecting a subset of component instances) have not yet been implemented in Fusion.  As far as I am aware, this is not on any near-term roadmap.  Surprisingly, this issue does not seem to come up frequently among customers.


Jeff Strater
Engineering Director
0 Likes