Done. Now this shit is getting more weird.
Now I’m getting the follwing message:
!! TMC 'stepper_y' reports error: GSTAT: 00000002 drv_err=1(ErrorShutdown!)
And now why this is relly weird… I’ve removed the XY-motors out of my printer, and did the same Z_TILT_ADJUST (the Z’s are still in their real position and moving the bed up and down) and everything works. Putting them back in their working position with belts, results in !! TMC 'stepper_y' reports error: GSTAT: 00000002 drv_err=1(ErrorShutdown!).
While writing this lines I did the following experiment…
- I loosened the belts so the XY-motors turn without any load, the xy-gantry isn’t moving than.
- I did homing like I always do, triggered stallguard with my fingers.
- I did Z_TITLT_ADJUST
- Wonder, nothing to adjust and no errors were raised.
- DUMP_TMC Stepper=stepper_* (with all 5 movement related stepper drivers)
- I tightened the belts so the motors are connected to the gantry
- M84 to be able to move the attached XY-gantry freely
- Fired my intial script ===> homing ==> Z_TITLT_ADJUST
- WTF it works, same components as all the time.
- Z_TILT_ADJUST, has been running 2 rounds and leveled the bed.
- Again I did DUMP_TMC for all movement related steppers/drivers.
- I copied moonraker.log & klippy.log after this whole session, perhaps it’s good for something.
==> klippy.log
As I am a man of science and support, I went for a FIRMWARE_RESTART to look what happens and funnily everything’s still fine, again Z_TILT_ADJUST ran 2 rounds, and bed is leveled.
Pushing it further I did RESTART, also works.
After powering off everything, with the power switch using my intial script again… well…:
!! TMC 'stepper_y' reports error: GSTAT: 00000002 drv_err=1(ErrorShutdown!)
I also have klippy.log of this session. ==> klippy.log
I don’t have any idea what is happening.