Can't post multiple operations that all use the same tool

[Anonymous]

Hi, I am new to Fusion 360 and trying it out via the personal use 1 year trial. When I try to post multiple operations that all use my T1 (a 0.25" endmill) I get the error message:  "When using Fusion 360 for Personal Use, you cannot post process operations that contain tool changes in a single NC file". I understand the limitation, however in this case I am using the same tool for each operation! I feel like this worked just the other day when I used a different Post Processing configuration (now I switched to Carbide 3D).

I have two questions: One, is this a bug that was introduced with the new personal use limitations?

Two, is there a way to modify the config file or my operations to get around this??

[Anonymous]

@jodom4 

[seth.madore]

There was a bug found in testing that behaved exactly like this, but we fixed it internally. My testing isn't showing the same behavior as yours though. Can you share your file, it's possible we missed something. In my test I've got a drill cycle, 3D Contour and (2x) 2D Contours posting just fine, using the same tool throughout

[Anonymous]

Hi, see the attached .f3d

[seth.madore · Accepted solution]

I bet I know what happened. Have you restarted Fusion yet? If you're on an older build, the fix for that went out in the last HotFix on.....Wednesday or Thursday. Restart Fusion and let me know if it's still failing. You should be at 2.0.9009

It's posting out fine on my personal testing account.

[Anonymous]

Wow - Thanks - I guess that's all I needed.

I have another question, but I'll create another post and tag you to learn more

[albino.caporale]

I'm having this same issue, I've tried restarting fusion 360 multiple times.  Are there potential issues in the setup that could cause this as well?

[turbobug64]

I am having the same problem. Just updated Fusion 360 today 10/12/2020 and this STILL does not work. I am using the centroid TURNING post from the Fusion 360 Library. I can not post more than a single operation with the same tool. 

Just turn on multiple tools for everyone again. You guys are making a mess. Please ACTUALLY fix this

[seth.madore]

If you are selecting the same tool multiple times from a library, Fusion will register this as separate unique tools. However, if you select the same tool from the active document, it will work properly

[turbobug64]

How do you select the tool from the active document??  When I click select tool it takes me to the library??

[seth.madore]

 

[whizbanger]

I don't see how this could be marked as resolved, the suggested solution is unrealistic....it's the same tool, and it originally got into the job from my library at one point!

I have tried every possible way to get multiple TPs in a folder or in a Setup that use the same tool to export together & they won't, unless they use the exact same feedrates.  Again, not realistic.  How about allowing users to create setup sheets & posts with 'the same tool', exactly as we were told we should be able to?

Even if I tried to select 'the tool' for each TP in a setup like you recommended Seth it's impossible because I can't see the differences between the instances used.  How would you pick which one of these to apply to multiple TPs in a setup with multiple tool feedrates?

[albino.caporale]

Hi @whizbanger , that resolved the problem for me, which is why I marked it as resolved.  I believe @seth.madore pointed out something I was doing incorrectly which contributed to the issue as well.  Instead of selecting the tool from your library each time, it should be selected from the setup so it is not assigned a unique ID.  I haven't tried this approach yet though.

[whizbanger]

I'd be happy to hear how that works once you have more than 1 TP in a setup with the same tool that uses different feedrates in each TP.

[seth.madore]

What @albino.caporale says is correct. If you are going back to your local or cloud library each time to select the same tool, that is an incorrect workflow. You need to select it from the active document each time. Doing otherwise will actually create new "instances" of the same tool, each with a unique ID number. The mechanism that's used to check against tool changes is that ID number.

[albino.caporale]

@seth.madore  To be fair, although it may be an incorrect work flow, the people most likely to be on the free license are people who are new and inexperienced with the software.  It seems that this an issue that people have commonly encountered, since someone who is new is very unlikely to know what a proper workflow is.  Given that, a more thoughtful implementation maybe should have been considered.

[whizbanger]

@seth.madoreThat's new to me, but OK, if that's how I'm supposed to pick tools for each TP I can do that in the future.  Please tell me how I'm supposed to fix this for the many TPs I've already created?  How do I select the right tool (I can't see that ID # you mentioned) & how do I make it keep all the unique tooling info (RPM, feed, etc...) I've configured in each TP?

[seth.madore]

@whizbanger @albino.caporale consider this:

[whizbanger]

I wanted to post a followup on this topic relating to my situation. Thanks to @seth.madore  and @albino.caporale for taking the time to explain this.  In the end, when using the same tool in multiple operations, I learned it's now necessary to select that tool from the 'project's library' rather than repeatedly selecting it from 'another library' (ie: my main tool library).  To be fair, this was never a problem until Autodesk recently changed the rules for the personal license & then left us to sort it out ourselves.

In my case the project I was working on had several operations that used the same tool, which I had previously 'erroneously' selected each time from my tool library, and each instance (operation) required custom feedrates.  In order to comply with the new 'rules' & to be able to post NC cut files & setup sheets, I had to edit each operation by re-selecting the tool that was used in the project & then re-entering any unique feedrates I wanted in that operation.

[Anonymous]

Worked for me thanx. I had to go to tools and delete duplicated milling bits from the document folder.