# Machine goes wild in z direction

**URL:** <https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799>\
**Category:** ❓ Question\
**Created:** [September 1, 2025, 5:00pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799 "2025-09-01T17:00:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wascally](https://forum.sienci.com/letter_avatar_proxy/v4/letter/w/58f4c7/32.png) [@Wascally](https://forum.sienci.com/u/Wascally)\
**Post date:** [September 1, 2025, 5:00pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/1 "2025-09-01T17:00:48Z")

</div>

I know I have had issues in the past with this but I don’t think I ever saw a diffinitive answer. I ran a test piece on my longmill using the latest gSender and it cut fine. I put my production piece in an left x any alone but rezeroed z. When I started it up instead of cutting .02 deep it was going more than .25 deep. It happened on another run too. Any solutions?

---

<div class="post-metadata">

**Author:** ![gwilki](https://forum.sienci.com/user_avatar/forum.sienci.com/gwilki/32/366_2.png) [@gwilki](https://forum.sienci.com/u/gwilki)\
**Post date:** [September 1, 2025, 5:17pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/2 "2025-09-01T17:17:07Z")

</div>

@Wascally I’ve moved your question from the Bug category. I’m not sure that this is even a gSender issue, but with more information, I may be better able to determine that.

1. Was the production material the same thickness as the test material?
2. How did you reset the Z0 - on the surface of the material or the surface of your spoilboard?

---

<div class="post-metadata">

**Author:** ![Wascally](https://forum.sienci.com/letter_avatar_proxy/v4/letter/w/58f4c7/32.png) [@Wascally](https://forum.sienci.com/u/Wascally)\
**Post date:** [September 1, 2025, 6:33pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/3 "2025-09-01T18:33:28Z")

</div>

The test piece was 3/4” and the prod piece was 9/16”. I put the piece in the machine in the same x-y position as the test piece. I then manually moved the bit to the zero x and zero y position and brought the bit down to the surface and hit the zero z button. I did it without the touch plate. So at this point it is using the original x and y zero and I have a new zero for z.. Since the stock was thinner than the test piece if it kept the original z it would not have touch the new surface.

---

<div class="post-metadata">

**Author:** ![gwilki](https://forum.sienci.com/user_avatar/forum.sienci.com/gwilki/32/366_2.png) [@gwilki](https://forum.sienci.com/u/gwilki)\
**Post date:** [September 1, 2025, 11:45pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/4 "2025-09-01T23:45:48Z")

</div>

@Wascally Post your gcode

---

<div class="post-metadata">

**Author:** ![Wascally](https://forum.sienci.com/letter_avatar_proxy/v4/letter/w/58f4c7/32.png) [@Wascally](https://forum.sienci.com/u/Wascally)\
**Post date:** [September 19, 2025, 9:03pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/5 "2025-09-19T21:03:41Z")

</div>

Sorry this took so long to get back to the forum. Here is my gcode. It did not change between the test piece and the prod run.

[D Nichter bottom side of lid.gcode](https://forum.sienci.com/uploads/short-url/nZPLwhAt5cx8ZRDMgGWXvWG1ozy.gcode) (71.2 KB)

---

<div class="post-metadata">

**Author:** ![chrismakesstuff](https://forum.sienci.com/user_avatar/forum.sienci.com/chrismakesstuff/32/10759_2.png) [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)\
**Post date:** [February 6, 2026, 7:21pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/6 "2026-02-06T19:21:37Z")

</div>

3 posts were merged into an existing topic: [Surfacing Tool wouldn’t accept alteration of project dimensions](https://forum.sienci.com/t/surfacing-tool-wouldnt-accept-alteration-of-project-dimensions/22095/9)

---

<div class="post-metadata">

**Author:** ![chrismakesstuff](https://forum.sienci.com/user_avatar/forum.sienci.com/chrismakesstuff/32/10759_2.png) [@chrismakesstuff](https://forum.sienci.com/u/chrismakesstuff)\
**Post date:** [March 24, 2026, 5:24pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/7 "2026-03-24T17:24:22Z")

</div>

Hi all, since we’re gearing up for a new gSender Main release I’m digging through older topics that fell through the cracks to see if the problems are now resolved on new gSender or gSender Edge versions, or if they still are occurring and if so then we’d like to fix them up promptly if we can.

If you can give any response in the next week or so it’d be greatly appreciated 👍

---

<div class="post-metadata">

**Author:** ![Wascally](https://forum.sienci.com/letter_avatar_proxy/v4/letter/w/58f4c7/32.png) [@Wascally](https://forum.sienci.com/u/Wascally)\
**Post date:** [March 24, 2026, 5:53pm UTC](https://forum.sienci.com/t/machine-goes-wild-in-z-direction/21799/8 "2026-03-24T17:53:36Z")

</div>

I haven’t had time to verify if the problem of wild z axis movement still exists. Too many projects going on.
