# Setting XY home point doesn't work

**URL:** <https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919>\
**Category:** No Judgement\
**Created:** [July 26, 2024, 4:10pm UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919 "2024-07-26T16:10:12Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [July 31, 2024, 5:05pm UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919/21 "2024-07-31T17:05:12Z")

</div>

I think that I have explanations for both of these 😀

> [@tr7](#):
>
> After it stopped cutting, I clicked to move left 50mm. However, it kept going well beyond that and I had to pause it to stop. I tried in the other direction and the same thing happened,

This happens when the gcode is inches. The gcode file leaves the machine in inch mode but the jog distance is still 100 so it tries to jog 100 inches. We need to come up with a better fix for that.

> [@tr7](#):
>
> I had just released the belt tension. Then went to move the Z axis up (1mm) and instead, the belts tightened again. (Below where it says Set to comply is where the Release Tension and Tighten Belts happened.)

Whenever any motor is moving all of the motors will hold position which leads to the belts tightening up. I’m open to changing how this works but we need to come up with a clear definition of what the expected behavior is

---

<div class="post-metadata">

**Author:** ![tr7](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tr7](https://forums.maslowcnc.com/u/tr7)\
**Post date:** [July 31, 2024, 6:20pm UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919/22 "2024-07-31T18:20:16Z")

</div>

Whew! That’s a relief to hear that these are somewhat known issues and not just my machine going rogue. So either I should create gcode files in mm (not as fun) or for now just do a unit conversion before moving the machine away. With regards to the other issue, I guess for now it’s better to just make any z-axis height changes before releasing belt tension? I can live with that.

Btw, is the fact that I’ve sometimes been seeing a mismatch between the actual position of the machine on the frame and its onscreen position at all related to the fact that the frame is in mm and the gcode in inches?

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [July 31, 2024, 7:06pm UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919/23 "2024-07-31T19:06:00Z")

</div>

> [@tr7](#):
>
> Btw, is the fact that I’ve sometimes been seeing a mismatch between the actual position of the machine on the frame and its onscreen position at all related to the fact that the frame is in mm and the gcode in inches?

Potentially!

That’s something that I should dig into more. I do everything in MM so I don’t test inches as much as I should

---

<div class="post-metadata">

**Author:** ![tr7](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tr7](https://forums.maslowcnc.com/u/tr7)\
**Post date:** [July 31, 2024, 7:11pm UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919/24 "2024-07-31T19:11:07Z")

</div>

Okay, I will see try working in mm and see the difference.

---

<div class="post-metadata">

**Author:** ![bar](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/bar/32/10_2.png) [@bar](https://forums.maslowcnc.com/u/bar)\
**Post date:** [July 31, 2024, 7:29pm UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919/25 "2024-07-31T19:29:22Z")

</div>

No! We need to fix it if there are issues with inches! 😂 The behavior of the machine should be the same in either unit

---

<div class="post-metadata">

**Author:** ![tr7](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tr7](https://forums.maslowcnc.com/u/tr7)\
**Post date:** [July 31, 2024, 7:37pm UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919/26 "2024-07-31T19:37:23Z")

</div>

Yes, that’s true. That would be great actually. I personally find working in inches much more intuitive. 🙂

---

<div class="post-metadata">

**Author:** ![dlang](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.maslowcnc.com/dlang/32/859_2.png) [@dlang](https://forums.maslowcnc.com/u/dlang)\
**Post date:** [August 1, 2024, 3:43am UTC](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919/27 "2024-08-01T03:43:02Z")

</div>

Bar wrote:

> This happens when the gcode is inches. The gcode file leaves the machine in inch mode but the jog distance is still 100 so it tries to jog 100 inches. We need to come up with a better fix for that.

we need something to watch the gcode or the internal state of fluidnc and be  
able to tell us if it’s in inches or mm

There isn’t any standard gcode to do this, but possibly the fluidnc folks would  
be open to some $ command to report it??

David Lang

[Previous page](https://forums.maslowcnc.com/t/setting-xy-home-point-doesnt-work/21919.md?page=1)
