# Randomly cut too deeply **URL:** \ **Category:** Troubleshooting\ **Created:** [February 6, 2022, 4:56pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076 "2022-02-06T16:56:05Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![TomIndelicato](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/tomindelicato/32/70581_2.png) [@TomIndelicato](https://community.inventables.com/u/TomIndelicato)\ **Post date:** [February 6, 2022, 4:56pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/1 "2022-02-06T16:56:05Z")
This weekend I needed to cut some shapes out of 1/8" thick aluminum (climbing hooks for an FRC robot). I’ve worked aluminum successfully before (up to 1/4" thick), and used the same settings (1/8" bit, 10in/min feed, 3in/min plunge, 0.002in depth per pass). The X-Carve initially did a perfect job of cutting the nine 0.201" diameter holes (63 passes per hole), but when it started cutting the outline, it dropped to a (caliper measured) depth of 0.05in! Naturally, it did a crappy job cutting for about 4" before the bit broke. Unfortunately (or maybe fortunately?), I wasn’t there at that moment, or I would have stopped it immediately. ![XCarve fail](https://canada1.discourse-cdn.com/flex009/uploads/inventables/original/3X/b/c/bc520f398ed861f010c000eac2a01ba978c2461f.jpeg) Could this be the fault of the cheap junk Chromebook I’m using to drive the XCarve? Is there a way to examine the command file to see where / why the depth suddenly went awry? Thanks in advance ---
**Author:** ![Ken4](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/ken4/32/87117_2.png) [@Ken4](https://community.inventables.com/u/Ken4)\ **Post date:** [February 6, 2022, 6:10pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/2 "2022-02-06T18:10:30Z")
can share your project? ---
**Author:** ![SethCNC](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/sethcnc/32/87515_2.png) [@SethCNC](https://community.inventables.com/u/SethCNC)\ **Post date:** [February 6, 2022, 6:29pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/3 "2022-02-06T18:29:03Z")
X-Carve Pro, Hmmm… What is the $1 grbl Setting? Go To Machine Inspector (Ctrl+Shift+D) and scroll to the bottom so see the settings. If It’s 0 then that is the problem. For reference: > [@Z Cut Too Deep](https://community.inventables.com/t/z-cut-too-deep/129003/16): > > So great! Thanks for the help! That fixed the z-issues now to tackle the feeds/speeds and bits! ---
**Author:** ![TomIndelicato](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/tomindelicato/32/70581_2.png) [@TomIndelicato](https://community.inventables.com/u/TomIndelicato)\ **Post date:** [February 6, 2022, 7:50pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/4 "2022-02-06T19:50:06Z")
Here’s the link to the project [https://easel.inventables.com/projects/zvaxy\_DcviMxVwXLpKaBlQ#](https://easel.inventables.com/projects/zvaxy_DcviMxVwXLpKaBlQ#) ---
**Author:** ![Ken4](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/ken4/32/87117_2.png) [@Ken4](https://community.inventables.com/u/Ken4)\ **Post date:** [February 6, 2022, 9:04pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/5 "2022-02-06T21:04:57Z")
your project is cutting a little agressive other than that you should take a look at your grbl setting like Seth mentioned earlier. quite a few people are having the same issue. ---
**Author:** ![TomIndelicato](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/tomindelicato/32/70581_2.png) [@TomIndelicato](https://community.inventables.com/u/TomIndelicato)\ **Post date:** [February 6, 2022, 9:36pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/6 "2022-02-06T21:36:17Z")
Not to sound too naïve, but what do you mean by “a little aggressive”? Do you have a suggestion for a better setting? ---
**Author:** ![TomIndelicato](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/tomindelicato/32/70581_2.png) [@TomIndelicato](https://community.inventables.com/u/TomIndelicato)\ **Post date:** [February 6, 2022, 9:39pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/7 "2022-02-06T21:39:16Z")
(I’m away from my system, so I can’t look right now.) Assuming I look at the grbl file and find the $1 setting is 0, what should it be set to? (Yes, I’m new to this level of debugging.) ---
**Author:** ![Ken4](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/ken4/32/87117_2.png) [@Ken4](https://community.inventables.com/u/Ken4)\ **Post date:** [February 6, 2022, 9:48pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/8 "2022-02-06T21:48:16Z")
Seth gave you a link about another person with the same issue. [![](https://community.inventables.com/user_avatar/discuss.inventables.com/sethcnc/90/75966_2.png)](https://community.inventables.com/u/SethCNC) [SethCNC](https://community.inventables.com/u/SethCNC) [2d](https://community.inventables.com/t/z-cut-too-deep/129003/15) at the very top (left) just type: $1=255 Hit enter Then scroll back to the bottom and hit the tiny refresh button and the value should be updated 🙂 ---
**Author:** ![Pavan](https://yyz1.discourse-cdn.com/flex009/user_avatar/community.inventables.com/pavan/32/83807_2.png) [@Pavan](https://community.inventables.com/u/Pavan)\ **Post date:** [February 14, 2022, 6:11pm UTC](https://community.inventables.com/t/randomly-cut-too-deeply/129076/9 "2022-02-14T18:11:34Z")
@TomIndelicato , I’m the Director of Marketing from Inventables! Thanks for sharing this issue. Please reach out to [help@inventables.com](mailto:help@inventables.com) and a member of our Customer Success team will help you resolve this.