I often have those layer 8 issues as well.
Nice the read that it is now working!
Great to hear that you got it working - congratulations!
Have to be honest,thought your idea was a waste of time, cause its the bed and unrelated to the z/x axis.
But from my work with computers and cars i learned to just do it, to eliminate everything. And of course it led me to, “huh, why are you z_hopping when homing y” and the solution. and another example of, just do it ignore that you think its a waste or a dumb idea.
Maaaaybe a thing it’s would be nice to add to the documentation to. that any Z-hop is a bad idea. if Z is in the loop.
When working with 3D printers (all electronic devices, actually), I’ve found that it’s critical to be as consistent as possible across different functions for two reasons:
- It makes scanning for typos and errors much easier.
- It ensures the multiple hardware devices (both electronic and mechanical) are as similar as possible so that if one device is having a problem then finding the differences that are the reason for the problem becomes easier to find.
In my experience, suggesting that source/configuration/text/data files are made as consistent as possible results in finding the error 30% to 40% of the time. This was one of those cases.
Still, I think Klipper’s reaction is quite strange and an unhandled exception should not happen- @Scarte, can you provide the needed information how to reproduce this?
Tell me what you need and i will give it to you.
short of it is.
coreXZ, sensorless X, everything correct with hw, but Z_HOP set to 10mm in safe home in printer.cfg