<p>I think the cleanest option is to move the X-endstop back about a centimeter to match, and then increase the size of the bed in both Slic3r's and the printer's settings.</p>

<p>You could also try using <a href="http://marlinfw.org/docs/gcode/M206.html" rel="nofollow noreferrer">M206</a> to set a persistent offset after homing.</p>

CC BY-SA 3.0
2017-04-29T13:22:05.880Z
I can't. The endstop is actually at the very beginning of the X axis (see picture above)
qwazix
CC BY-SA 3.0
2017-04-29T17:08:27.930Z
M206 should still work, is it not supported by your firmware?
ctag
CC BY-SA 3.0
2017-04-29T17:18:52.143Z
Haven't tried. I tried with G92 and it just did crazy things such as trying to honor both restrictions and thus restricting X movement completely. Will try and report back.
qwazix
CC BY-SA 3.0
2017-04-11T16:17:54.560Z
2017-04-11T16:17:54.560Z
ctag
<p>My <strong>mono mendel</strong> 0,0 position is on the left of the bed, when the nozzle is at the position of the green dot in this image.</p>

<p><a href="https://i.sstatic.net/YQ5aj.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/YQ5aj.png" alt="Mendel mono home position"></a></p>

<p>I would like to move that point to the left a bit, in order to print a slightly larger part (the bed has about a centimeter more space to the left). I know I can just allow negative values but I'd rather not to, for safety reasons.</p>

<p>However I cannot find where the offset of that point from the endstops (home position) is declared. There is no offset set in either pronterface or Slic3r, and unless my board came preloaded with different firmware than the one reprappro publishes, the <code>*_HOME_POS</code> variables in their Marlin repository are all equal to 0.</p>

<pre><code>// The position of the homing switches. Use MAX_LENGTH * -0.5 if the center should be 0, 0, 0
#define X_HOME_POS 0
#define Y_HOME_POS 0
#define Z_HOME_POS 0
</code></pre>

<p><a href="https://github.com/reprappro/Marlin/blob/master/Marlin/Configuration.h#L290" rel="nofollow noreferrer">https://github.com/reprappro/Marlin/blob/master/Marlin/Configuration.h#L290</a></p>

<p>Any ideas how I should go about it?</p>

<marlin><g-code>
Resetting the zero position of the X axis on a RepRapPro Mendel Mono
qwazix
# Resetting the zero position of the X axis on a RepRapPro Mendel Mono

(Asked by: username_0 on 2017-03-23)

My **mono mendel** 0,0 position is on the left of the bed, when the nozzle is at the position of the green dot in this image.

[![Mendel mono home position](https://i.sstatic.net/YQ5aj.png)](https://i.sstatic.net/YQ5aj.png)

I would like to move that point to the left a bit, in order to print a slightly larger part (the bed has about a centimeter more space to the left). I know I can just allow negative values but I'd rather not to, for safety reasons.

However I cannot find where the offset of that point from the endstops (home position) is declared. There is no offset set in either pronterface or Slic3r, and unless my board came preloaded with different firmware than the one reprappro publishes, the `*_HOME_POS` variables in their Marlin repository are all equal to 0.

```
// The position of the homing switches. Use MAX_LENGTH * -0.5 if the center should be 0, 0, 0
#define X_HOME_POS 0
#define Y_HOME_POS 0
#define Z_HOME_POS 0

```

<https://github.com/reprappro/Marlin/blob/master/Marlin/Configuration.h#L290>

Any ideas how I should go about it?

**Tags:** marlin, g-code


---

## 1 answers

### Answer by username_1 on 2017-04-11. Score: 1 | Accepted answer

I think the cleanest option is to move the X-endstop back about a centimeter to match, and then increase the size of the bed in both Slic3r's and the printer's settings.

You could also try using [M206](http://marlinfw.org/docs/gcode/M206.html) to set a persistent offset after homing.

> **Comments:**
> **username_0**: I can't. The endstop is actually at the very beginning of the X axis (see picture above)  
> **username_1**: M206 should still work, is it not supported by your firmware?  
> **username_0**: Haven't tried. I tried with G92 and it just did crazy things such as trying to honor both restrictions and thus restricting X movement completely. Will try and report back.  

---

