<p>Looking at your prints, the problem is possibly related to the fade out height of the BLTouch functionality.</p>
<p>If you look closely at the 20x20x20 mm cube:</p>
<ul>
<li>half the print is fine (top half of the original correct cube)</li>
<li>the bottom &quot;half&quot; (not really half as it is stretched) is porous (grey, indicating more space allowed than the correct layer height per layer should be).</li>
</ul>
<p>If you look closely at the 40x40x40 mm cube:</p>
<ul>
<li>the first &quot;quart&quot; of the 40x40x40 mm is also incorrect (also stretched),</li>
<li>the rest, 3/4 of the top of the print is fine (correct layer height).</li>
</ul>
<p>Your <code>configuration_backend.h</code> config file doesn't look strange, so the underlying problem could well be more complicated.</p>
<p>A possibility is that there is no reference found to the <code>DEFAULT_LEVELING_FADE_HEIGHT</code> in the linked firmware file. A more in depth answer on enabling/setting the fade height is found <a href="https://3dprinting.stackexchange.com/a/6905/">here</a>.</p>
<blockquote>
<pre><code>M420 S1  ; Enable compensation using current grid/mesh
M420 Z10 ; Gradually reduce compensation until Z=10
</code></pre>
</blockquote>
<p>It is good to have a fade out height, if zero, the imperfections of the bottom travel all the way to the top of the print; the solution is to use bed geometry (<code>M420 S1</code>) and fade out over 10 mm (<code>M420 Z10</code>).</p>

CC BY-SA 4.0
2021-07-26T14:21:39.400Z
Just for other people's reference, the "switch" for this (`ENABLE_LEVELING_FADE_HEIGHT`) and the parameter itself (`DEFAULT_LEVELING_FADE_HEIGHT`) is found in the `Configuration_backend.h` of the TH3D firmware (Unified 2 4.2.7 board version)
Lewis
CC BY-SA 4.0
2021-07-26T13:44:28.353Z
2021-07-26T21:46:28.773Z
2021-07-26T21:46:28.773Z
0scar
<p>If you check TH3D's site, as of January 12, 2022, there's an updated Unified 2 firmware(Unified 2.36a) that is meant to correct this problem.</p>
<p>Announcement is here: <a href="https://www.th3dstudio.com/2022/01/12/unified-2-36a-is-now-live-firmware-update/" rel="nofollow noreferrer">Unified 2.36a is now live! | Firmware Update</a></p>
<blockquote>
<h3>Release Notes:</h3>
<p><strong>Bugfixes</strong></p>
<ul>
<li>Disable ABL fade height by default</li>
<li>Fix EZBoard V2 DIY Config Driver Type Setting</li>
</ul>
<p><strong>Other Changes</strong></p>
<ul>
<li>Update URLs in config files to support articles</li>
<li>Improve EZABL mount wording for more user clarity</li>
</ul>
</blockquote>

CC BY-SA 4.0
2022-01-14T08:24:48.480Z
2022-01-14T16:34:29.950Z
2022-01-14T16:34:29.950Z
Kevin Jones
<p><em>TLDR - I’ve just driven myself insane trying to fix what I thought was a physical problem with my Z-axis, but it seems to have been solved by switching from the TH3D firmware to the Creality firmware. I’m hoping someone can help me see where I went wrong here, so I can learn from it. Have I missed something obvious?</em></p>
<p>My printer is a Creality Ender 3 Pro. I have a BLTouch. I recently upgraded to the silent 4.2.7 board and compiled my own firmware using TH3D Unified 2 using their instructions. <a href="https://pastebin.com/MYs8sYGj" rel="nofollow noreferrer">This is my <code>configuration.h</code></a>.</p>
<p>This “worked”, but after that upgrade, I had severe print problems. (See the photos below) These are supposed to be 20x20x20 calibration cubes (the big one is 200%). They are significantly taller than they should be. It may be hard to see in the photo, but this is because the Z spacing on the bottom layers seems to be too high. But, at the same point on each print (even the bigger one), the problem seems to just stop - and layer spacing is correct again for the end of the print.</p>
<p><a href="https://i.sstatic.net/BGayd.jpg" rel="nofollow noreferrer" title="Comparison of multiple calibration cubes"><img src="https://i.sstatic.net/BGayd.jpg" alt="Comparison of multiple calibration cubes" title="Comparison of multiple calibration cubes" /></a></p>
<p>I tried everything to figure out what this was and I was convinced it was a physical problem with my Z-axis. I read lots of questions on here but nothing quite on topic. I printed on different parts of the bed and got the same result. I re-calibrated my Z steps, but these turned out to be pretty much at the firmware default anyway. I tightened every bolt and eccentric nut I could find that related to the X-axis gantry, but nothing made any difference. Same problem, every time.</p>
<p>Out of desperation, I eventually switched to the official Creality firmware for the Ender 3 Pro 4.2.7 board with BLTouch - and the problem was fixed:</p>
<p><a href="https://i.sstatic.net/7tXcf.jpg" rel="nofollow noreferrer" title="Printed calibration cube after firmware change"><img src="https://i.sstatic.net/7tXcf.jpg" alt="Printed calibration cube after firmware change" title="Printed calibration cube after firmware change" /></a></p>
<p>Does anyone have any ideas about what caused this? Have I overlooked something obvious? I’d ideally like to go back to the TH3D firmware but it’s seemingly not an option.</p>
<p><a href="https://pastebin.com/MYs8sYGj" rel="nofollow noreferrer">https://pastebin.com/MYs8sYGj</a></p>

CC BY-SA 4.0
2021-07-26T08:00:41.703Z
I totally respect the idea behind TH3D software, it is to make flashing firmware easier for a lot of people. But, the problems you experience are one of the many examples that this doesn't work always out of the box, and why I would't recommend using TH3D software, I understand the good intentions from the owner/maintainer (this is not meant as a bash to the developer)! When it doesn't work, the user is left clueless what went wrong. It is far better to use the firmware sources directly from the original repository (no delay in releases) and learn how to configure the firmware using tutorials.
0scar
CC BY-SA 4.0
2021-07-26T12:33:07.003Z
@0scar - You nailed it. This was exactly the problem. I compared the Creality and TH3D firmware settings and TH3D is using `M420 S1 Z0.00`, but the TH3D firmware seemingly has a default of `M420 S0 Z10.00`. Sending `M420 S1 Z0.00` on TH3D crashes the printer, but `M420 Z0` is seemingly enough to fix the issue. I have no idea why this is set to `Z10` in the TH3D firmware by default... seems like a bad idea to me. If you want to post this as an answer you can get the points for it!
Lewis
CC BY-SA 4.0
2021-07-26T14:38:54.277Z
To correct my comment above for other readers, `M420 S1` was crashing my printer as I had no stored compensation matrix at that time (I'd just reset the printer). Like most BLTouch users, I have `G29` in my startup G-code which will create a matrix *and enable it*. So, in this case, simply setting `M420 Z0` (followed by `M500`) fixes my problem entirely, as the fade out seemingly doesn't work well with the BLTouch. I hope that helps someone avoid this!
Lewis
CC BY-SA 4.0
2021-07-27T05:47:27.507Z
@0scar Bold of you to assume good intentions in TH3D ;)
towe
<creality-ender-3><marlin><firmware><bltouch><th3d>
Creality Ender 3 Pro - Z travel issue with TH3D firmware
Lewis
# Creality Ender 3 Pro - Z travel issue with TH3D firmware

(Asked by: username_0 on 2021-07-25)

*TLDR - I’ve just driven myself insane trying to fix what I thought was a physical problem with my Z-axis, but it seems to have been solved by switching from the TH3D firmware to the Creality firmware. I’m hoping someone can help me see where I went wrong here, so I can learn from it. Have I missed something obvious?*

My printer is a Creality Ender 3 Pro. I have a BLTouch. I recently upgraded to the silent 4.2.7 board and compiled my own firmware using TH3D Unified 2 using their instructions. [This is my `configuration.h`](https://pastebin.com/MYs8sYGj).

This “worked”, but after that upgrade, I had severe print problems. (See the photos below) These are supposed to be 20x20x20 calibration cubes (the big one is 200%). They are significantly taller than they should be. It may be hard to see in the photo, but this is because the Z spacing on the bottom layers seems to be too high. But, at the same point on each print (even the bigger one), the problem seems to just stop - and layer spacing is correct again for the end of the print.

[![Comparison of multiple calibration cubes](https://i.sstatic.net/BGayd.jpg "Comparison of multiple calibration cubes")](https://i.sstatic.net/BGayd.jpg "Comparison of multiple calibration cubes")

I tried everything to figure out what this was and I was convinced it was a physical problem with my Z-axis. I read lots of questions on here but nothing quite on topic. I printed on different parts of the bed and got the same result. I re-calibrated my Z steps, but these turned out to be pretty much at the firmware default anyway. I tightened every bolt and eccentric nut I could find that related to the X-axis gantry, but nothing made any difference. Same problem, every time.

Out of desperation, I eventually switched to the official Creality firmware for the Ender 3 Pro 4.2.7 board with BLTouch - and the problem was fixed:

[![Printed calibration cube after firmware change](https://i.sstatic.net/7tXcf.jpg "Printed calibration cube after firmware change")](https://i.sstatic.net/7tXcf.jpg "Printed calibration cube after firmware change")

Does anyone have any ideas about what caused this? Have I overlooked something obvious? I’d ideally like to go back to the TH3D firmware but it’s seemingly not an option.

<https://pastebin.com/MYs8sYGj>

**Tags:** creality-ender-3, marlin, firmware, bltouch, th3d

> **Comments:**
> **username_1**: I totally respect the idea behind TH3D software, it is to make flashing firmware easier for a lot of people. But, the problems you experience are one of the many examples that this doesn't work always out of the box, and why I would't recommend using TH3D software, I understand the good intentions from the owner/maintainer (this is not meant as a bash to the developer)! When it doesn't work, the user is left clueless what went wrong. It is far better to use the firmware sources directly from the original repository (no delay in releases) and learn how to configure the firmware using tutorials.  
> **username_0**: @username_1 - You nailed it. This was exactly the problem. I compared the Creality and TH3D firmware settings and TH3D is using `M420 S1 Z0.00`, but the TH3D firmware seemingly has a default of `M420 S0 Z10.00`. Sending `M420 S1 Z0.00` on TH3D crashes the printer, but `M420 Z0` is seemingly enough to fix the issue. I have no idea why this is set to `Z10` in the TH3D firmware by default... seems like a bad idea to me. If you want to post this as an answer you can get the points for it!  
> **username_0**: To correct my comment above for other readers, `M420 S1` was crashing my printer as I had no stored compensation matrix at that time (I'd just reset the printer). Like most BLTouch users, I have `G29` in my startup G-code which will create a matrix *and enable it*. So, in this case, simply setting `M420 Z0` (followed by `M500`) fixes my problem entirely, as the fade out seemingly doesn't work well with the BLTouch. I hope that helps someone avoid this!  
> **username_2**: @username_1 Bold of you to assume good intentions in TH3D ;)  

---

## 2 answers

### Answer by username_1 on 2021-07-26. Score: 2 | Accepted answer

Looking at your prints, the problem is possibly related to the fade out height of the BLTouch functionality.

If you look closely at the 20x20x20 mm cube:

* half the print is fine (top half of the original correct cube)
* the bottom "half" (not really half as it is stretched) is porous (grey, indicating more space allowed than the correct layer height per layer should be).

If you look closely at the 40x40x40 mm cube:

* the first "quart" of the 40x40x40 mm is also incorrect (also stretched),
* the rest, 3/4 of the top of the print is fine (correct layer height).

Your `configuration_backend.h` config file doesn't look strange, so the underlying problem could well be more complicated.

A possibility is that there is no reference found to the `DEFAULT_LEVELING_FADE_HEIGHT` in the linked firmware file. A more in depth answer on enabling/setting the fade height is found [here](https://3dprinting.stackexchange.com/a/6905/).

> ```
> M420 S1  ; Enable compensation using current grid/mesh
> M420 Z10 ; Gradually reduce compensation until Z=10
>
> ```

It is good to have a fade out height, if zero, the imperfections of the bottom travel all the way to the top of the print; the solution is to use bed geometry (`M420 S1`) and fade out over 10 mm (`M420 Z10`).

> **Comments:**
> **username_0**: Just for other people's reference, the "switch" for this (`ENABLE_LEVELING_FADE_HEIGHT`) and the parameter itself (`DEFAULT_LEVELING_FADE_HEIGHT`) is found in the `Configuration_backend.h` of the TH3D firmware (Unified 2 4.2.7 board version)  

---

### Answer by username_3 on 2022-01-14. Score: 2

If you check TH3D's site, as of January 12, 2022, there's an updated Unified 2 firmware(Unified 2.36a) that is meant to correct this problem.

Announcement is here: [Unified 2.36a is now live! | Firmware Update](https://www.th3dstudio.com/2022/01/12/unified-2-36a-is-now-live-firmware-update/)

> ### Release Notes:
>
> **Bugfixes**
>
> * Disable ABL fade height by default
> * Fix EZBoard V2 DIY Config Driver Type Setting
>
> **Other Changes**
>
> * Update URLs in config files to support articles
> * Improve EZABL mount wording for more user clarity


---

