<p>TLDR; Make sure the bed isn't too high, the z-axis should reach the end-of-rail indicator without forcing against the bed</p>

<hr>

<p>So it appears I simply misunderstood (or mis-assumed) the way my printer works.</p>

<p>For some reason I believed that it was the printing head, while auto-homeing, that was defining the "point zero" for the z axis. Didn't realize, even after disassembled the whole head block, that there was no such mechanism built in.</p>

<p>While zeroing it before starting my on-going print I noticed the "click" of the end-of-rail switch for the z-axis while the head was forcing against the bed, desperately trying to reach that damn switch. Then it all clicked together ...</p>

<h2>What happened:</h2>

<p>For some reason a few weeks ago I decided to level the bed by raising the z-axis by spinning the its driving wheel <em>by hand</em>, taking it very far from the end-of-rail stopper. Ever since then I've been leveling the bed this way, not realizing I was preventing the head from reaching end-of-rail without having to force against the bed.</p>

<p>So yeah, just took the bed as far down as possible, made the printer auto-home and leveled the bed from there, as it should be done, and my print is now going very well.</p>

CC BY-SA 4.0
2019-08-13T20:10:27.083Z
One thing to watch out for is, if the z-axis limit switch ("end-of-rail indicator") assembly is fastened to the vertical member in the same way as it is on the Ender 3, it can be tricksy in how the lock nuts seem to be locked when you tighten the screws but aren't when you need them to be.
Andrew Morton
CC BY-SA 4.0
2019-08-12T21:41:17.420Z
2019-08-12T21:41:17.420Z
Mathieu VIALES
<p>Did you verify the Cura z-offset actually changed the corresponding G-Codes? </p>

<p>I had the opposite problem on my RF1000. To fix the problem I added the following 2 lines to my start G-Codes:</p>

<pre><code>M3001 ; Activate Z-Compensation 
M206 Z-0.3 ; Set z offset 0.3mm closer to the nozzle
</code></pre>

<p>The first line was default in some example prints and is (as far as I know) only used by Renkforce printers. The second line moves the nozzle closer to the bed. In your case you'd have to move it further away and would need a positive Z value.</p>

CC BY-SA 4.0
2019-08-12T21:42:59.047Z
Was in the process of trying to send these GCodes to cura, so to decide what value to give it decided to watch the printer while it did a "auto-home" to guess the needed distance. Then when I realized what the problem was and wrote my answer below.
To thank you, your answer led me to fixing this non-problem :-)
Mathieu VIALES
CC BY-SA 4.0
2019-08-12T18:08:19.663Z
2019-08-12T18:08:19.663Z
Stefan
<h2>Problem</h2>

<p>My CR-10 printer seems to be trying to print the model 4 or 5 layers too low. This means that for the first few layers, the printing nozzle is forced against the bed, preventing extrusion until the print reaches higher layers.</p>

<h2>Outcome</h2>

<p>This results in the bottom part of the print having the internal structure visible and the printing head deteriorating. I had to remove the old nozzle because it was clogged up with what I believe to be some residue that was picked up during preceding prints.</p>

<p><a href="https://i.sstatic.net/mUfsT.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/mUfsT.jpg" alt="A print showing the structure inside the model because of missing layers"></a>
<em>note: On this print, the top part is almost-well printed. It cannot be seen in pictures, but I say "almost" because the well-printed part is still much thinner than expected. This is the result of my purposeful mis-leveling the bed so that the part where the printer "homes" is higher than the lower part. I did this to see if there was any obvious bending of the printing bed. Doesn't look like there is.</em></p>

<h2>Fix attempts</h2>

<ul>
<li>I have tried to re-level the bed multiple times, but it doesn't matter as the "too low" effect is independent from the location on the bed.</li>
<li>I have tried using the printer's built-in Z-offset but to no avail. This might be due to the fact that I control the print through Ultimaker Cura 4, so I tried looking for the Z-offset property in Ultimaker Cura and even though internet says it exists, I failed to find it.</li>
</ul>

<h2>History</h2>

<p>The printer used to work perfectly well and I do not remember having changed anything before the problem arose. I recently changed the nozzle and made sure to tighten it as high as possible but the Z-offset problem still persists.</p>

CC BY-SA 4.0
2019-08-12T17:17:47.307Z
what is the thickness of the first layer? I use 0.2 mm for it to ensure I don't 'squish' it too much
Trish
CC BY-SA 4.0
2019-08-12T17:38:41.267Z
For my on-going print 0.16 mm
I've tried several layer thicknesses, it doesn't seem to affect the offset problem :-/
Mathieu VIALES
CC BY-SA 4.0
2019-08-12T18:21:32.570Z
Have you checked that everything is still assembled correctly? For example, the z-axis screw connector might be a bit loose, or the bed might wobble, or the z-axis stop microswitch asembly could be loose.
Andrew Morton
CC BY-SA 4.0
2019-08-12T21:43:54.207Z
Thank you all for your time, I fixed it. See my answer below for a good laugh at my lack of understand how a CR-10 works -_-
Mathieu VIALES
<z-axis><creality-cr-10>
Printer head too low when printing
Mathieu VIALES
# Printer head too low when printing

(Asked by: username_0 on 2019-08-12)

## Problem

My CR-10 printer seems to be trying to print the model 4 or 5 layers too low. This means that for the first few layers, the printing nozzle is forced against the bed, preventing extrusion until the print reaches higher layers.

## Outcome

This results in the bottom part of the print having the internal structure visible and the printing head deteriorating. I had to remove the old nozzle because it was clogged up with what I believe to be some residue that was picked up during preceding prints.

[![A print showing the structure inside the model because of missing layers](https://i.sstatic.net/mUfsT.jpg)](https://i.sstatic.net/mUfsT.jpg)
*note: On this print, the top part is almost-well printed. It cannot be seen in pictures, but I say "almost" because the well-printed part is still much thinner than expected. This is the result of my purposeful mis-leveling the bed so that the part where the printer "homes" is higher than the lower part. I did this to see if there was any obvious bending of the printing bed. Doesn't look like there is.*

## Fix attempts

* I have tried to re-level the bed multiple times, but it doesn't matter as the "too low" effect is independent from the location on the bed.
* I have tried using the printer's built-in Z-offset but to no avail. This might be due to the fact that I control the print through Ultimaker Cura 4, so I tried looking for the Z-offset property in Ultimaker Cura and even though internet says it exists, I failed to find it.

## History

The printer used to work perfectly well and I do not remember having changed anything before the problem arose. I recently changed the nozzle and made sure to tighten it as high as possible but the Z-offset problem still persists.

**Tags:** z-axis, creality-cr-10
> **Comments:**
> **username_1**: what is the thickness of the first layer? I use 0.2 mm for it to ensure I don't 'squish' it too much  
> **username_0**: For my on-going print 0.16 mm I've tried several layer thicknesses, it doesn't seem to affect the offset problem :-/  
> **username_2**: Have you checked that everything is still assembled correctly? For example, the z-axis screw connector might be a bit loose, or the bed might wobble, or the z-axis stop microswitch asembly could be loose.  
> **username_0**: Thank you all for your time, I fixed it. See my answer below for a good laugh at my lack of understand how a CR-10 works -_-  

---

## 2 answers

### Answer by username_0 on 2019-08-12. Score: 0 | Accepted answer

TLDR; Make sure the bed isn't too high, the z-axis should reach the end-of-rail indicator without forcing against the bed

---

So it appears I simply misunderstood (or mis-assumed) the way my printer works.

For some reason I believed that it was the printing head, while auto-homeing, that was defining the "point zero" for the z axis. Didn't realize, even after disassembled the whole head block, that there was no such mechanism built in.

While zeroing it before starting my on-going print I noticed the "click" of the end-of-rail switch for the z-axis while the head was forcing against the bed, desperately trying to reach that damn switch. Then it all clicked together ...

## What happened:

For some reason a few weeks ago I decided to level the bed by raising the z-axis by spinning the its driving wheel *by hand*, taking it very far from the end-of-rail stopper. Ever since then I've been leveling the bed this way, not realizing I was preventing the head from reaching end-of-rail without having to force against the bed.

So yeah, just took the bed as far down as possible, made the printer auto-home and leveled the bed from there, as it should be done, and my print is now going very well.

> **Comments:**
> **username_2**: One thing to watch out for is, if the z-axis limit switch ("end-of-rail indicator") assembly is fastened to the vertical member in the same way as it is on the Ender 3, it can be tricksy in how the lock nuts seem to be locked when you tighten the screws but aren't when you need them to be.  

---

### Answer by username_3 on 2019-08-12. Score: 1

Did you verify the Cura z-offset actually changed the corresponding G-Codes? 
I had the opposite problem on my RF1000. To fix the problem I added the following 2 lines to my start G-Codes:
M3001 ; Activate Z-Compensation 
M206 Z-0.3 ; Set z offset 0.3mm closer to the nozzle

The first line was default in some example prints and is (as far as I know) only used by Renkforce printers. The second line moves the nozzle closer to the bed. In your case you'd have to move it further away and would need a positive Z value.

> **Comments:**
> **username_0**: Was in the process of trying to send these GCodes to cura, so to decide what value to give it decided to watch the printer while it did a "auto-home" to guess the needed distance. Then when I realized what the problem was and wrote my answer below. To thank you, your answer led me to fixing this non-problem :-)  

---

