Add new comment

Submitted by Elias on Fri, 03/26/2021 Permalink

Hi All

For the past few days I've been struggling with a particular issue with this firmware.

I recently bought a BLTouch and hooked it up to my Ender 3 (stock V1 8-bit board).

I have configured the nozzle to probe offsets correctly for the mount I printed (I'm comfortable with building and flashing the firmware myself).

What is working:

  • I slice my print with following start gcode:
...
G28 ; Home all axes
G29
...
  • After the nozzle and bed are at the target temperature, the probing starts
  • When the probing is done (after 5-10 minutes) the printing starts with beautiful first layer results and perfect adhesion

What is not working

To save some time when I'm doing consecutive shorter prints (probing 25 points takes a while), I would like to level the bed once in a while and use that mesh for my prints without the need to level before each print in the start gcode

  • I warm my bed to target temp (around 50-60 celsius) and give it some time to settle
  • In the LCD menu I go to Prepare > Bed leveling > Level bed(I have tried sending M29 myself as well)
  • The probing starts and seems to run well
  • When it's done, I save that result (have tried both gcode M500 and Store Settings from the LCD)
  • I slice my print with following start gcode:
...
G28 ; Home all axes
M420 S1 ; turn leveling on and use stored mesh
...
  • The print starts, but unlike previously when doing G29 in my print start gcode, the nozzle starts printing above the bed, so much that there is no adhesion.

I'm not sure what is going wrong, but it would be so much more comfortable in my workflow to be able to level when I want it, not standard before every print. It seems as though in the second scenario my configured Z-offset is ignored (maybe why it's printing in the air), although some compensation seems to be applied.

As I said, in the first scenario the results are perfect. I manually leveled my bed to minimize the delta and my bed/ x-axis have no wobble and my frame is square. (if that would be an issue it would fail in the first scenario as well). It feels like I'm missing something obvious.

What can I check/ what can I try out?

Any help will be greatly appreciated!

The content of this field is kept private and will not be shown publicly.
CAPTCHA
3 + 11 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
Protected by Spam Master