5 Pro is cutting twice as deep as the depth of cut is set

[Etoimos (Keith)]

I’ve had this issue happen three times in the past couple of week. So far it has always happened on a circular pocket toolpath. I set my depth of cut for a 3/4 bowl bit to 2.5mm and the machine is actually cutting over 5mm deep. Here are some photos from tonight’s incident:

Tool settings

And two shots of the actual cut it made:

Note that the arrows are point to the cuts that it made too deeply. The level you see above that cut was done in multiple passes (DoC set to 2.5mm) as it should have been via the Lip Pocket toolpaths. As an added reference point, the thin strips of wood are 3mm wide.

I’ve checked and it is not that my bit is slipping in the collet. Any other thoughts on why my machine is cutting deeper than it is programed for? My file is attached below if that helps. In the below file, the Deep Pocket looks like it starts at 15mm instead of where the Lip pocket finishes (123mm), but is only because I made adjustments to it after it cut too deep. The original file started the Deep toolpath at 12mm.

11 inch round tray.c2d (2.1 MB)

[WillAdams (William Adams (Carbide 3D))]

Which version of Carbide Motion are you using?

If not 640, the current stable, try it:

Carbide Motion Downloads

and consider trying the beta:

https://carbide3d.com/carbidemotion/beta

If you still have trouble, let us know how you are setting zero and managing tool changes and we will look into this with you.

[Etoimos (Keith)]

Thanks Will. I am using 640. This morning it finished cutting the Deep pocket correctly. Ill be able to salvage this project, but ill have to remake the insert that sits on the lip since i had to increase the radius of the pocket due to the machine crashing on the too deep cuts.

As for setting zeros, i use the BitZero V2. Tool changes use the BitSetter.

[WillAdams (William Adams (Carbide 3D))]

Note when using the BitZero there are two ways to position it:

• fully registered at a corner for probing all three axes, or X/Y
• fully on a surface for Z only

and the difference is the height of the lip, which I leave to the reader to measure.

see:

Using/verifying the BitZero

Here is how I check out the functionality of the machine/BitZero: first check that you have sent the correct Z-axis configuration This can be easily done by jogging down to the wasteboard surface, setting zero, then using the Rapid Position command to lift 6mm above the current zero — measure how much the machine moved — if it’s wrong: open the Log Window go to the MDI (EDIT: Note that it will need to be enabled in options in current versions) and send $$ and check that the Z-axis steps/mm …

[Etoimos (Keith)]

I use the BitZero to register all three axis. That said, I’ve been thinking of making an L fence so I don’t always have to reset the X and Y. So the thread you link should be good reading.