Patterning component toolpaths not working

[balancefromwithin]

Hi all-

Trying to pattern toolpaths ala this helpful video.

I can't seem to copy the new toolpaths.  I've got the pattern, but the toolpaths are not showing up.  These components are all set in one sheet of material. 

Does anyone know what I'm doing wrong?

[LibertyMachine]

What sort or pattern did you do to get all the parts? Did you use the Pattern function to arrange your parts or was it copy/paste? 

Pattern Toolpaths do not work with Copy/Paste (to my understanding)

[balancefromwithin]

ah, ok.

I copied/pasted.....Can't nest enough with pattern ;(

[LibertyMachine]

Actually.....

I just tried it now (it's been a while since I've needed that functionality) and it appears that copy/paste works just fine. Select the "master" piece and leave "Targets" blank

[balancefromwithin]

Seth-

Maybe it has to do something with my component tree?

Tried that and couldn't do it (tried preserve order, and order by tool)

[LibertyMachine]

Could you export and share the file?

File > Export > Save to local folder. Return to thread and attach the .f3d in your ext reply

[balancefromwithin]

Yes Sir!

[LibertyMachine]

I hate to leave this as a reply, but I'm stumped. I found a few things that I hoped would be the cause, but no luck:

You weren't capturing design history, so I went to my sample piece, turned it off and did a bunch of stuff and pattern still worked.

You didn't have any Models selected in the Setup. After selecting all 10 pieces, results were the same

You applied all your toolpaths to Component 2. Wondering if that had any impact, I moved them all over to Component 1. Results are unchanged.

I'm curious if anyone else has any ideas? @daniel_lyall, do you ever come across Pattern oddities?

[balancefromwithin]

Seth, very much appreciate your help regardless. We have a lot of parts to cut for our kickstarter; Ställdesk.com 😉

[daniel_lyall]

@LibertyMachine I think this is one for for the fusion team, I have a idea why it is failing but don't want to say until the guys have had a look.

@balancefromwithin You made a mistake with your press pull you missed one have a look at sketch 4

[LibertyMachine]

I was thinking about your response and waited to see if a dev would pop in and comment. No such luck, so I played with the file a bit more. It's odd, but deleting all the clones and redoing them (more or less) the component function works just fine:

I shall submit a bug report, get someone to look at it.

[daniel_lyall]

That's close to what I was thinking, It strange that it works after deleting almost everything, I was hoping the staff could've come up with something what did not included deleting all but one.

What I was thinking, What is wrong did not have time to test, was delete all but one and useing joints. It takes time to find a plug made 35 years ago, for a very expensive DRO and fix it.

[paul.clauss]

Hi @LibertyMachine, @daniel_lyall, @balancefromwithin,

Thank you for bringing this to my attention! This is not a bug, but rather a workflow issue stemming from the way the component instances were created.

When creating a component pattern in the CAM workspace, Fusion 360 looks for instances of a component rather than the actual geometry of each component. In @balancefromwithin's original post, you will notice that the components in the design are labeled "Component 1:1, Component 2:1, Component 3:1..." When the number before the colon changes, Fusion 360 is defining each of these components as unique instead of as an instance of the original component. This is what happens when you use the "Paste New" command while copy/pasting in the browser tree.

What we would like to do for CAM component patterning instead is use the "Paste" command. This will create instances of the copied/pasted component, which will show up in the browser tree as "Component 1:1, Component 1:2, Component 1:3..." The name and number to the left of the colon defines the actual component, while the number to the right shows the instance of the base component (that was copy/pasted). Using this workflow will allow the CAM component pattern to know that the components are identical instances of the original base component.

I have illustrated this in the screencast below - please let me know if you have any questions!

[LibertyMachine]

While what you say makes perfect sense and it plays out just as the last two screencasts have shown, I'm curious about one thing; What is the point then, of the Auto button and the manual selection button in the CAM Pattern dialog? If it's looking for XXX:1, XXX:2 etc, what would one even select?

[daniel_lyall]

@paul.clauss I can do it how you say you can sort of I did a copy and past, (yes Past not past new) whent back to cam reset the toolpaths started the pattern diag selected the first component then the rest auto populated.

[paul.clauss]

Hi @LibertyMachine

A situation you could use manual selection in is when you want to avoid instances of a component, like when certain instances are reoriented in the same program/ setup.