Geeetech Mizar S crashes into print bed when trying to home Z Axis

Basic Information:

Printer Model: Geeetech Mizar S
MCU / Printerboard: STM32F103
Klippy.log
klippy(2).log (1.2 MB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

I’m having a hell of a time trying to get Klipper working as expected with the Mizar S. Got my printer config from the Geeetech github page under the Klipper folder. Flashed Klipper firmware and added CFG in Mainsail. Printer connects, but homing was a nightmare. X and Y seem to hit their limits and then gracefully stop. Z on the other hand just kept climbing up by some amount for some reason - the carriage would just keep getting higher and further away from the print bed and Z limit switch every time I clicked “home”. Looked online, found that maybe the issue was a wacky config or something. I reversed the Z stepper direction in CFG and tried again - now it homes downward, only when the Z switch is set off, it is ignored and it continues to mercilessly plow the carriage into the print bed (thankfully since X and Y homed fine, it’s just the blower squashing into the print bed and not the nozzle).

I did a quick check with a command I found online and the sensors are recognized as the Z limit sensors and trigger or switch to “open” appropriately.

What in the heck?! Please help!

They should switch to “Triggered” when pushed and held, not “Open”.

They correctly identified as open or triggered when checked, but the 2 Z sensors seem not to have an effect and it tries to drive the carriage down through the print bed despite the sensor appearing to work.

To be clear, if I had miscommunicated, they correctly say “Open” when the switch isn’t detecting contact, and shows TRIGGERED when the sensor is tripped. That’s the confusing part - in software it looks for all intents and purposes like it should be fine.

Are you sure the endstops can be triggered by the hardware when the X-axis reaches that position?

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