Help With ToolPath Collisions

Help With ToolPath Collisions

oldtbone55
Collaborator Collaborator
1,030 Views
11 Replies
Message 1 of 12

Help With ToolPath Collisions

oldtbone55
Collaborator
Collaborator

I've been trying to figure out what to do to fix the toolpath collisions I'm getting and need some help. I received some great help with creating the toolpaths but can't seem to figure out the reason(s) for the collisions. If someone would be kind enough to take a look at the file it would be appreciated.

0 Likes
1,031 Views
11 Replies
Replies (11)
Message 2 of 12

LibertyMachine
Mentor
Mentor

I'm not seeing the collisions during simulation. Are they there, or is it in real life you are having issues? If so, which Setup and operation?

 

I do see a large flaw with your Facing operation, as it's cutting right through the part....


Seth Madore
Owner, Liberty Machine, Inc.
Good. Fast. Cheap. Pick two.
0 Likes
Message 3 of 12

matthew.nichols
Alumni
Alumni

Yeah @LibertyMachine is right about the facing operation.  it does not recognize your model in your setup; it will literally just machine off everything that is inbetween top height and bottom height.

I am not seeing any crashes either unless you are talking about the exclamation mark on the adaptive in Setup1?



Matthew Nichols
Adoption Specialist - MFG
0 Likes
Message 4 of 12

oldtbone55
Collaborator
Collaborator

I'm getting the information about the collisions from the info tab of the simulate box. In Setup 2, Adaptive 1 Top Clearing there are 11 collisions reported. Also under Setup 2, Morphed Spiral-Finish cut I am also getting collisions in the info tab. I too didn't see any problems with collisions when I actually run the simulation but the collisions are showing up under those info tabs. I had a feeling that there was something wrong with the facing operation. What am I doing wrong?

 

Thanks.

0 Likes
Message 5 of 12

LibertyMachine
Mentor
Mentor

For the Facing operation:

Set your "Bottom Height" to Model Top and your Facing pass won't go below the Top of the part.

 

You are seeing those collisions only when you select the single operation. If you select the Setup it will select all the operations and display any crash. In this case, selecting all operations shows zero crashes. The reason you were seeing crashes is that the Simulation can only compare against the model and the tool paths selected for that simulation event. Select all and it has all the info needed. Select only one or two and it doesn't account for what a prior tool would have removed and it thinks you are going full rapid into material (that's actually not even there)


Seth Madore
Owner, Liberty Machine, Inc.
Good. Fast. Cheap. Pick two.
0 Likes
Message 6 of 12

oldtbone55
Collaborator
Collaborator

Thanks kindly Seth. Do you think it necessary to even perform the facing operation? When the rough cut is performed would it not remove the material it needed to anyway. The stock I would be starting with would already have been planed flat. What do you think about the warning in Setup 1? 

0 Likes
Message 7 of 12

LibertyMachine
Mentor
Mentor

I wouldn't bother with the Facing Operation, if you have that little material coming off (personally). It would be worth it if you had a much larger tool to put in and you could haul the material off quickly. As you are using the same tool for both operations, I'd dispense with the facing op.

 

The yellow warnings are of no consequence (in this case). All it's telling you is that it's lifted the Ramp to it's highest point. The REASON it's alarming out is because your Retract height is set to "Model Top". Set it to "Stock Top" and the warning goes away


Seth Madore
Owner, Liberty Machine, Inc.
Good. Fast. Cheap. Pick two.
0 Likes
Message 8 of 12

oldtbone55
Collaborator
Collaborator

Thanks again Seth. I eliminated the surfacing operation. When I run the simulation from the Setup 2 instead of the individual operations I'm still getting collisions. I see them when I run the simulation as I have it set to stop when a collision occurs. The tool turns red when there is a collision. I then have to click on the play button to continue with the machining operation. This needs to be done each time there's a collision. Could my laptop be a problem since it's not optimal for running fusion? I'm awaiting delivery of a laptop that will have the proper configuration for running Fusion.

0 Likes
Message 9 of 12

daniel_lyall
Mentor
Mentor

Seth I deselected the stock contour and just left it ticked and it keeps the tool inside the model, there was a stock crash at the top end of the model the tool was plowing through a bit of the stock.

 

@oldtbone55 I put it in the SG Guiar folder 


Win10 pro | 16 GB ram | 4 GB graphics Quadro K2200 | Intel(R) 8Xeon(R) CPU E5-1620 v3 @ 3.50GHz 3.50 GHz

Daniel Lyall
The Big Boss
Mach3 User
My Websight, Daniels Wheelchair Customisations.
Facebook | Twitter | LinkedIn

0 Likes
Message 10 of 12

oldtbone55
Collaborator
Collaborator

Hey Daniel, thanks for your help. Could you clarify something for me. When you say you deselected the stock contour and just left it ticked, where did you do the editing for this? By the way, I'm not getting any collisions now, I just have to fix the warning in Setup 1.


@daniel_lyall wrote:

Seth I deselected the stock contour and just left it ticked and it keeps the tool inside the model, there was a stock crash at the top end of the model the tool was plowing through a bit of the stock.

 

@oldtbone55 I put it in the SG Guiar folder 


 

0 Likes
Message 11 of 12

daniel_lyall
Mentor
Mentor

I realy hate when fusion does this, Last night before I posted your file there was a crash, deselecting the stock contour fixed it.

 

Open up the file to check and pop a screencast up for ya just now and the crash is gone.  I will still do a screencast to show what I said.

 

Fusion does this sometimes where a toolpath or something will be playing up you fix it or give up and move on then you can come back after a restart of fusion your computer what ever and what ever the problem was is gone.


Win10 pro | 16 GB ram | 4 GB graphics Quadro K2200 | Intel(R) 8Xeon(R) CPU E5-1620 v3 @ 3.50GHz 3.50 GHz

Daniel Lyall
The Big Boss
Mach3 User
My Websight, Daniels Wheelchair Customisations.
Facebook | Twitter | LinkedIn

Message 12 of 12

oldtbone55
Collaborator
Collaborator

Yeah, I'm starting to understand that. I now wait a while before jumping to any conclusions about what might be going on. I guess it's just something we're going to have to monitor and report back on. Thanks again for your help.

0 Likes