- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I recently made a 4-sided case and used a new technique for the mitered corners. I've used the 90-deg v-bit trick before, but I don't like the variability in re-zeroing after a tool change, and I wondered if I could get away with a parallel toolpath using the 1/4in bit used for everything else. It worked great! ...
...except it cut into my part in the surrounding area during the operation. Like all things I suspected myself, but I just looked more closely before I go to make a second, and it looks to be real in the generated toolpath.
Can anyone illuminate on why it would generate a path that cuts into the final model?
Here's the part for reference. I will note that this was made in SolidWorks and imported to Fusion. Not sure if that matters or not.
Here is the parallel operation cutting my miter:
I adaptive clear to rough everything out, then run the miter parallel toolpath, and then clean up the "shelf" and walls with this 2d conI also have this contour cleaning up the "shelf" and protruding walls after this miter operation:
Now I'm orienting to the front view (looking at the miter/shelf from the side) and zooming way in:
Here's the contour, which makes that shelf disappear behind the toolpath lines:
Now here's that parallel path highlighted, which is clearly below the shelf as I experienced in real life:
Here's the geometry tab, which I'd think is the most relevant?
I thought it might have been the use of touch surfaces, but here's with turning them off. In this view from the side, you can see the toolpath line disappear right into the part!
Any other information that would be helpful for me to provide? All other cuts/passes seem correct, and in checking other dimensions, things seem well within what I'd expect. My walls should be 4.37mm and I get 4.34-4.37mm with my caliper away from the ends, but 4.19-4.22mm where the parallel path hit.
I appreciate any suggestions, and again am happy to provide other details/settings that would be needed to troubleshoot further. I've never had this happen so I'm not sure how to diagnose!
Solved! Go to Solution.