Fusion 360 doesn't show my custom tool holder during manufacture mill simulation

chris7XW6D
Enthusiast

Fusion 360 doesn't show my custom tool holder during manufacture mill simulation

chris7XW6D
Enthusiast
Enthusiast

I have created a custom tool holder in the Manufacture area of Fusion 360 and I've selected it on the Holder tab of my mill ends in the tool library. But when I run a simulation on my setup in Fusion, the holder still looks like the generic one. How do I get my custom holder to show during simulation so that the interference errors are accurate for my machine?

0 Likes
Reply
Accepted solutions (1)
706 Views
5 Replies
Replies (5)

mathew.hutton
Alumni
Alumni

Hi @chris7XW6D 

 

Can you attach your project so we can have a look at this please. Maybe give the tool and holder a description such as "This one" so i know which tool and holder is the issue. 

 

Thanks

 

Mat



Mathew Hutton
Manufacturing Specialist
0 Likes

chris7XW6D
Enthusiast
Enthusiast
Accepted solution

Hey Matt.  Thanks for your response.  I have since found the issue, sort of.  I created the tools and holder in my local library.  In the document, the tools show up in the tool manager under the document section and under the local library section.  I'm not really sure why they show in both.  I suppose because the document is using the tool now?  Anyway, I created the holder and set the tool to use the holder in the local library but the change did not affect the tool in the document which had apparently been set to the version of the tool under the document tool tree.  This is confusing because as a user I don't distinguish between the two versions of the tool.  There is only one tool with product id 757 for example and that tool is managed from my local tool library across all projects.  I'm not sure why choosing a tool from a local library makes  a copy of the tool in the document.  At this point I've got 3 copies of the same tool in the document and from my perspective there is only one version of this tool.

 

At least I know how to work around it but as feedback, it's confusing and unclear why the tool is copied to the document.  I'd rather it was a live representation of what's in the library.

1 Like

mathew.hutton
Alumni
Alumni

Hi @chris7XW6D 

 

I think it just appears in that document library as some users change tools frequently, so rather than having a large local library and having to filter through that library for a tool they may have used for one project that they need again, they can open up the old project and access those tools via the old project document library. I think it's down to individual preferences. I can propose this as an improvement though, say, if you selected the tool from the local library, it doesn't duplicate the tool in the document library. Would this be a better workflow for you?

 

Mat



Mathew Hutton
Manufacturing Specialist
0 Likes

chris7XW6D
Enthusiast
Enthusiast

Personally, yes, I think the library is a better workflow.   Maybe someone would add a one time tool to a single document.  And maybe they'd even use that tool later in another document, in which case they can select it from the first document.  I imagine this may be more valuable if I was sharing the doc with someone who didn't have my library but did have my tool.  But I would think in most cases, and in all of my cases, I have a machine and a set of tools in the shop.  Those tools aren't tied to any particular document in Fusion.  The library represents the actual tools in real life in the shop.  In each document I refer to the tool.  I wouldn't change the tool in the document because it's still the same tool in real life in the shop.  I may run the same tool with different speeds, for example, but that is set in the individual operations.  The more tools I have, the more it makes sense they are managed in the library because otherwise I have real tools in the shop but I can't remember which Fusion doc they exist in.  I would just like the default to not copy into the document.  I could think of plenty of fixes/features that are more important though.  😉

0 Likes

mathew.hutton
Alumni
Alumni

Hi @chris7XW6D 

 

Yeah i completely understand your reasons. Coincidentally, i had a conference call this afternoon with some of the product owners and development team that handles all the tool library issues and i mentioned this issue, i was informed that they are working on a fix to this issue so that if you do follow the workflow of creating a tool in the local library and selecting it for a project, it won't copy this into the document library. I will create a task and suggest this as an improvement as well anyway just so it adds traction to the process and hopefully can speed this up. 

 

Cheers

 

Mat



Mathew Hutton
Manufacturing Specialist
1 Like