Problem engraving circles

[Anonymous]

I am trying to engrave some designs for cookie stamps and I am running into a problem.  The desired contours are selected but no toolpaths are generated for some or all of the circular contours.

I've extracted a couple examples of the problem into a new design file and was able to replicate the problem.  I've attached that example exported design file for you to examine.

Here's a screenshot of one of the engraving paths:

This particular one, after completion of editing the settings, generates no toolpaths at all, and shows a warning.

The next path, pictured below, which includes the wavy rays as well as those same circles, generates no warning, but simply does not engrave the circles either.

Generated paths (in blue):

To make matter weirder, the toolpaths for the third example stamp seem to randomly pick some circles to engrave and skip others.  It is not related to circle diameter as there are a range of diameters for this third stamp and sometimes one will have a toolpath but not another one of the same size.

Any help or a workaround that you can suggest will be appreciated.

Thanks,

Jonathan Lee

[masa.minohara]

Hi @Anonymous,

Thank you for posting! Engrave is not designed to engrave on contours where the space between to lines is greater than the tool radius. The selection of a single circle, while it creates a toolpath, is not intended use of the toolpath type. Suggestion would be to add an additional circle offset from the initial circle. Please see CJ's comment in this forum thread for more details.

Hopefully that helps!

[Anonymous]

Thank you for your reply.  However, I don't believe that the cause of this problem is due to the tool radius.  The tool in question is a 90 deg. V-bit with a radius of 0.5 inches, much larger than the radius of any of the selected circles. (See relative tool size in the simulation image below).  The problem is not that a toolpath is being generated which doesn't clear the interior of the circle.  The problem is that no toolpath is being generated at all, almost randomly.

CJ's answer doesn't really apply here as the tool can touch all sides of the circle without requiring an interior offset circle and without violating the depth limit.

If you look at the screenshot of the simulation below, you will see:

1. The size of the tool is huge relative to the size of even the largest dot being cut.
2. There are dots of various sizes and some dots of a specific size will be cut while other dots of the same size will be skipped.  I have circled two examples, but there are others, even of the smallest size.  There are 8 dots of each size in this example and every single discrete size has at least one dot that gets cut with others of the same size skipped.

Thanks,

Jonathan

[masa.minohara · Accepted solution]

Hi @Anonymous,

Thank you for your response! I was able to get Engrave toolpath generated for all the circles by changing the bottom height but the results are different depending on the diameter. Below is a screenshot of two different results, are you looking to the left one or the right one? If you need plunge move (like the one on the left), I think you can use Drill instead.

I apologize that I cannot provide a clear explanation of why Fusion skips some dots while the others will be cut right now. I'll reach out to the CAM team and let you know as soon as I have more information to share. 

[Anonymous]

Hello @masa.minohara,

Due to the small diameters, in this case I am looking for a profile like the one on the left.  Thank you for your suggestion of using a Drill toolpath as a workaround to engrave the missing dots.  I was able to get that path to work correctly by tweaking the drill bottom depth until the OD matched the circle ODs.

Additionally, I am still interested in the fix for engrave operation, so please keep me informed on that front.

Sincerely,

Jonathan Lee

[maarten.nijhuis]

I am encountering the same issue with a much larger file with a lot more circles where manual selection and finding the correct plunge depth is not really an option. Is this issue with Fusion Cam solved?