0

Installed a BLTouch on an Ender 5 Pro. As usual, the official firmware from Creality is buggy trash (wrong BLTouch offsets, only 9 point probing, etc.) and useless to me.

I compiled and flashed the TH3D Unified firmware, which works well other than the fact that I have to redo the Z-offset via tune every time I do a print, as it does not apply the stored value (it does retain the value however). So the first print the Z-offset is ~ -11, and the next time it is -22, -33, etc.

Why is it doing this and how can I fix it?

Config files (Using marlin bugfix 2.1.x):

https://drive.google.com/drive/folders/1rLc0XlNgTj02fTgg2V190oUmv1MEOt_f

Side note:

So I was able to get the Creality stock firmware working by switching some wires around on the extruder and manually setting the offsets in pronterface, so anyone else in my predicament can at least do that- but I'm still stuck with v2.0.6 .bin file only and only 9 probing points so I really need a Marlin version that works as intended that I can compile myself.

Why is it that the latest Marlin often doesn't work on Creality printers and we are forced to use one that is years old?

benram14159
  • 109
  • 2
  • 11

1 Answers1

2

Not sure if its a solution to your problem but I had a similar problem and this worked for me:

My Problem

I could auto-home and configure my Z-offset as many times as I want but it behaved strangely. It just added the values on top and the offset did not apply whatever I did. I did auto home, drive to Z -3, set my Z-offset to -3, did auto home, and was again 3 millimeters too high.

How did I get there

I compiled Marlin 2.1.2 with the configuration for the Creality Ender 5 Pro and enabled ENDER5_USE_BLTOUCH. I did some adjustments to NOZZLE_TO_PROBE_OFFSET (where the 3rd parameter, the Z option didn't do anything).

My Solution

I commented out (put // before these lines) Z_HOMING_HEIGHT and Z_AFTER_HOMING which were commented in by the author of the Ender 5 Pro configuration.

Why I did that

I realised that every time the auto-home ran, it moved to Z 10. Ignoring my offset. This could be a bug, could be intentional behaviour but after commenting those lines it always moves 10+Z-offset down.

My guess as to why this happened

My assumption is that it always moved 10 mm but those lines made Marlin believe it moved also respecting the offset.

agarza
  • 1,734
  • 2
  • 16
  • 33
Joniras
  • 121
  • 3