Bed mesh doesn't work, random errors stopping the print

General Discussion
1

Ender 3 V2 (Bl-touch, stock everything else)
klippy.log (3.4 MB)

Hello everybody!

Switched from Octoprint to Klipper a week ago, tuned a lot, and I love it. Installed Minimus fan shroud (without taking off bl-touch), printed few things, best prints I’ve ever had.

Installed Octoanywhere, and started to get problems. Looks like my bed mesh stopped working. Decided to print a 4x4 gridfinity baseplate and on the first layer some layer lines were okay, but some came super super close to the bed.

Tried to print something else, failed to start the print, and noticed a few random messages in my console

[Album] Imgur: The magic of the Internet

(No errors with homing, just when I started the print). And I understand that slicer instructs my printer to move Y axis to 345, but after retry, the same gcode prints successfully (if we ignore the warped bed problem). And I haven’t changed any important settings before these errors.

Tried to print the same thing again (I think it was the calibration cube), this time it works and it looks good (maybe because it’s quite small).

I uninstalled Octoeverywhere, printed a few things again to test, the bed is very much uneven again.

Then tried to print the bed leveling calibration model, nozzle got to 60C and stopped - the print job failed to start. Also, I’ve noticed that the brim is harder to remove than before (more squishing?), but I can’t remember if I had this problem before Octoanywhere.

Between these last tests I’ve re-did the mesh (5x5, sampler rate 3) a few times.

The weird thing is that, to my limited knowledge, the last message means that the print head tried to go out of bounds, even though I haven’t changed the size. I haven’t touched printer.cfg, haven’t changed any settings.

My last option would be to nuke the card, reinstall Mainsail again, and import backups. But maybe it’s still salvageable?

Questions/thoughts:

  • Maybe I’ve fucked up something while screwing the hotend back? But the minimus backplate doesn’t interfere with screws or anything, hotend is at the same place as before.
  • But even if the hotend is not completely at the same place as before or is skewed, wouldn’t I have problems everywhere on my bed, not just at some spots?
  • Also, I believe “crooked” hotend wouldn’t summon these “Move out of range” errors?
  • Googled a lot, some people have problems with bed mesh but didn’t find anyone who had it happen so suddenly and with random errors.

(If needed, I can attach anything else, thank you!)

2

Hello @Tiny_Giggles !

Can you elaborate?

You know the difference between a print server and a firmware solution?

They are not random, they have a purpose.

Have you set the origin in the slicer to centre of the bed or to one of the corners?
Are the dimensions of the bed in the slicer the same as you set them in Klipper?

Maybe a short gcode file can help here.

1 Like
3

Your klippy.log contains several errors that may point to USB connection problems between your host and your controller board:

Write g-code response
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/gcode.py", line 446, in _respond_raw
    os.write(self.fd, (msg+"\n").encode())
BlockingIOError: [Errno 11] Resource temporarily unavailable

and

mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0'
MCU error during connect
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/mcu.py", line 800, in _mcu_identify
    self._serial.connect_uart(self._serialport, self._baud, rts)
  File "/home/pi/klipper/klippy/serialhdl.py", line 182, in connect_uart
    self._error("Unable to connect")
  File "/home/pi/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'mcu': Unable to connect

If you’re using a USB hub, I’d get rid of it. If not, try a better USB cable.

Beyond that, on the bed mesh, have you actually loaded the mesh after measuring it? Bed Mesh - Klipper documentation

4

Thank you for your reply!

You know the difference between a print server and a firmware solution?

Sorry, I’ve meant Marlin and Octoprint, now just Klipper.

They are not random, they have a purpose.

I understand that :smile: , but they appeared randomly and never happened before. The origin point is where the print head stays after homing, right? It’s the center.

I’ve added G90 command to my print start macro, we’ll see how it goes. It’s hard to replicate that error because the same model can one time fail and successfully print on the next run. I’ve started to print bed calibration model again and it’s printing (bed mesh is still off).

I believe it failed yesterday with this model:
LH02_In5_Sp100_PLA_0H_33M_3dbenchy.gcode (1.3 MB)

5

Thank you for looking into this! I can’t really understand these errors, but I trust you and I’m going to buy a new cable tomorrow :smile:

Beyond that, on the bed mesh, have you actually loaded the mesh after measuring it?

Yes, I did! I was successfully printing few days before (the first layer looked amazing).

6

Right, but you have to load the mesh every print, or at least every time the printer is restarted. BED_MESH_PROFILE LOAD=<name> should be in your slicer’s start gcode or in your start_print macro if you have one.

7

Yep, I have it in my start_print macro already.

Just did few tests and I just used the good old paper test and leveled my bed manually. Disabled bed mesh and my first layer now looks better than with automatic probing. Without ABL everything is ± okay, with ABL, it squishes same spots as before the manual leveling. Well, that sucks.

8

Check Axis Twist Compensation - Klipper documentation

9

I will after work, thank you!

10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.