Printer homing problems

[WayneManion]

I'm not sure what's happening. I'm starting with the printer.cfg from repo:
https://github.com/bassamanator/Sovol-SV06-firmware/tree/sv06-plus

I add in the [t5uid1] section to printer.cfg. The touchscreen works OK,

If I home the printer using the touchscreen everything is fine. If I home the printer using G28 or by pressing the home button in Mainsail the X & Y go home as expected but the Z just smashes the nozzle into the print bed.

I've tried:

• Looking in klippy.log for some command related to the bed homing coming from the touchscreen
• Looking in both Desuuu repos (the screen firmware repo and the Klipper fork repo) for some kind of clue about some alternate command the touchscreen might be sending. I can't make any sense out of either.

Complete printer.cfg here

[fryc88]

Hi
It has nothing to do with the screen or branch used by this screen.
Screen is sending G28 couple of times, split to axes, that's why in some cases it is causing issues, but it is not possible to cause hitting the bed, especially when you do it via your GUI too - that means there's something wrong in your config file.
Screen works via UART, as lets say 'transmitter', firmware knows what button on the screen is calling what function or gcode, but neither screen or that branch can modify your settings.

Have you had Klipper working before on this printer without screen, or you have started from a scratch?
Did you adjust your Z offset? Is your induction probe aligned correctly to the nozzle? (bottom of probe has to be 1-2mm above of the nozzle tip).
Did it ever work correctly with marlin, or you are trying to solve some unknown issue by flashing the printer to klipper?

[WayneManion]

I think there is some kind of problem with Mainsail. I can home the printer with the touchscreen. I can home the printer using Mobileraker on my Android phone.

But something way funkier is going on. I'm running Klipper on a system with a Core i5 and 32 GB of DDR4 RAM. Ludicrous overkill for babysitting four 3D printers. If I use Mobileraker and then open a web browser on a computer to connect to my Klipper host machine Klipper gobbles all the memory on my computer (again, 32 GB) and a print I had going on another machine crashed.

So I rebooted my Klipper host, went through all the computers in my house that might have an open Mainsail browser window, closed them all, then went back to Mainsail on my primary computer (not the one running Klipper) and was able to home the printer using Mainsail.