# Incorrect cut depth
**URL:** https://forum.sienci.com/t/incorrect-cut-depth/26775
**Category:** ❓ Question
**Created:** [July 25, 2026, 1:52am UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775 "2026-07-25T01:52:30Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@twells555](https://forum.sienci.com/u/twells555)
#### Post date: [July 25, 2026, 1:52am UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/1 "2026-07-25T01:52:30Z")
Hi All,
Shapeoko pro 5 owner. I have been using vcarve pro with carbide motion software for a while now, but have been trying gsender instead of carbide motion because of the additional features it offers. I have not had any issues or problems using vcarve and carbide motion. The cuts are very acurate.
However, when I run the same file with gsender, cut depths that should be .150 for example are coming out to be almost twice that…~.300.. All the gsender cuts have the problem.
Gsender seems to be running fine…I set an xyz zero using the shapeoko bitzero controlled by gsender which runs fine. I have gsender set up to use a fixed tool depth setter, the shapeoko bit setter. Running a multi tool file runs fine…all tool changes happen as expected and run without issue…except the cut depth is far too deep when using gsender.
So since the project file appears to be fine (Carbide Motion cuts it perfectly), I’m wondering if there is a depth calibration setup which I may have missed? Or something else?
Thanks in advance,
tim
---
### Author:  [@Spamming\_Eddie](https://forum.sienci.com/u/Spamming_Eddie)
#### Post date: [July 25, 2026, 5:52am UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/2 "2026-07-25T05:52:59Z")
Hey Tim,
Welcome to the play ground. There is indeed a calibration option in gsender.
> **[Calibration Tools - gSender](https://resources.sienci.com/view/gs-calibration-tools/)**
>
> Learn the about using XY squaring, movement tuning & surfacing.
---
### Author:  [@gwilki](https://forum.sienci.com/u/gwilki)
#### Post date: [July 25, 2026, 1:22pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/3 "2026-07-25T13:22:54Z")
@twells555 Welcome to the group. I would check out what gSender has as the thickness of your touchplate vs what it actually is.
---
### Author:  [@Chucky\_ott](https://forum.sienci.com/u/Chucky_ott)
#### Post date: [July 25, 2026, 2:38pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/4 "2026-07-25T14:38:09Z")
@twells555 @gwilki makes a good point. Are all your cuts twice what they should be or are they all simply deeper by 0.15" ?
The latter might indicate an offset of some kind. The touch plate could be the reason for that
The former could be a calibration issue like @Spamming_Eddie suggests.
---
### Author:  [@twells555](https://forum.sienci.com/u/twells555)
#### Post date: [July 25, 2026, 4:51pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/5 "2026-07-25T16:51:32Z")
Hi gwiki,
Thanks for the welcome and quick reply!
When I installed GSender I set up the bitzero using the defaults in the gsender config. I measuresd the actual bit zero thickness with calipers and checked the measurements against the default gsender values. The defaults looked correct…a very, very minor difference probably due to the cheap calipers I own, but definately nowhere near the error I am seeing…
tim
---
### Author:  [@twells555](https://forum.sienci.com/u/twells555)
#### Post date: [July 25, 2026, 5:01pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/6 "2026-07-25T17:01:34Z")
Thank you, I’ll take a look at that guide for any z depth calibrations.
tim
---
### Author:  [@twells555](https://forum.sienci.com/u/twells555)
#### Post date: [July 25, 2026, 5:11pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/7 "2026-07-25T17:11:49Z")
Hi Chucky\_ott, Thanks for the quick reply.
Very good question…I’m going to do some more test cuts later today and check out what you ask. Not sure at this point. Right now I have just seen that is it consistently much deeper than I ask…
One thing I have been wondering about…For using the bit setter, I just selected the settings in the gsender configuration for it. Its works fine like that functionally…but since setting it up I have seen some macros for bit setter us…and one in particuliar for the shapeoko. I am wondering if the macros are old and no longer necessary since the gsender folks have since integrated bit setter functionallity into the app when a shapeoko is chosen as the cnc, Or maybe the macro is still needed? (Kind of hoping one of the gsender ‘officials’ would chime in on that question)
tim
---
### Author:  [@twells555](https://forum.sienci.com/u/twells555)
#### Post date: [July 26, 2026, 2:14pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/8 "2026-07-26T14:14:27Z")
I did some further testing yesterday. Cuts which were supposed to be at .100, .200, .300, and .700 deep end up at a cutting depth of ,209, .295, .415, and .800. All cuts were consistently .100 deeper than specified by the vcarve software.
I then did a .200 deep cut without having the bitsetter feature enabled, A single tool job using the default bit zero probe routine to set up the xyz zero point. The cut depth on that job was .215. Exactly what it should be including a bit of error because of cheap measurement calipers. So it seems that maybe something in the default toolchange bitsetter routine is consistently adding ~.100 to the cut depth. Again, running the same cuts from the same job using the CarbideMotion software with bitsetter had no issues…all cuts were at the proper depth.
Why the Gsender built in bitsetter routine would have so much error is way out of my league…I am brand new to the software and have not found any type of calibration adjustments for it in the docs. Any assistance would be greatly appreciated…
Thank you in advance,
tim
---
### Author:  [@gwilki](https://forum.sienci.com/u/gwilki)
#### Post date: [July 26, 2026, 2:23pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/9 "2026-07-26T14:23:27Z")
@twells555 I’ve moved this discussion to the gSender category so that the team at Sienci will see it.
---
### Author:  [@twells555](https://forum.sienci.com/u/twells555)
#### Post date: [July 26, 2026, 2:49pm UTC](https://forum.sienci.com/t/incorrect-cut-depth/26775/10 "2026-07-26T14:49:35Z")
Ok, Thank you very much!
tim