Basic Information:
Printer Model: Own design and build.
MCU / Printerboard: Octopus Pro (STM32F429)
Host / SBC - RPi5
klippy.log:
klippy-3.log (52.1 KB)
I know this problem has been encountered by others, but all the suggestions I have seen thus far have not worked for me.
The machine is one I designed and built myself. It has evolved through a number different iteration into its present form. I had not encountered this particular problem until my latest upgrades. All the upgrades were to hardware. 9mm linear rails to 12 mm, revised hot end carriage etc. I also went from a Pi 4 to a Pi 5. This did require me to reinstall the firmware of course, but I made no change to the printer.cfg or macros.cfg files. At no time during the development of this printer didi I encounter problems homing the z-axis. Until now that is.
Machine specs that may be of significance are: Build volume 400 x 400 x 360. I use four stepper motors for the z-axis and a piezo load cell probe. Limits set for z are -5 min to 360 max.
What I don’t get is how it determines it has made full movement. Until it has homed, surely it has no idea where it is in space!
As I say, I have just performed upgrades on this machine, but it has stood idle for months now due to this problem! ![]()
…