! TMC 'stepper_y' reports error: DRV_STATUS: 801f5000 s2vsa=1 stealth=1 CSACTUAL=31 stst=1

General Discussion
33

Here you go, to first 3 “TMC_DUMP Sessions” were without any physical load, the belts were detached.

  1. Before homing
  2. After homing
  3. After Z_TILT_ADJUST

The last 3 were done with physical load, the belts were attached.

  1. Before homing
  2. After homing
  3. After Z_TILT_ADJUST

klippy.log (332.7 KB)

The second log should have shown that if I do Z_TILT_ADJUST directly after homing with physical load the error why I opened this thread occurs… should because I made a mistake.

That’s my “Z_TILT_ADJUST” macro:

[gcode_macro START_TILT]
gcode:
TMC_INFO
BED_MESH_CLEAR
G28
TMC_INFO
Z_TILT_ADJUST
TMC_INFO
G1 X317 Y297 F4000
TMC_INFO

Before my TMC_DUMP sessions it looked like this:

[gcode_macro START_TILT]
gcode =
BED_MESH_CLEAR
G28
Z_TILT_ADJUST
G1 X317 Y288 F4000

Accidentally I switchted the position of the G1 line, so it’s now before the Z_TILT_ADJUST line. Well funnily everything works immediatly with this configuration.

See:
klippy_2.log (177.5 KB)

Third log-session… my macro looks like this again…

[gcode_macro START_TILT]
gcode:
TMC_INFO
BED_MESH_CLEAR
G28
TMC_INFO
Z_TILT_ADJUST
TMC_INFO
G1 X317 Y297 F4000
TMC_INFO

… aaaaand that’s the result:

!! TMC ‘stepper_y’ reports error: DRV_STATUS: 801f6000 s2vsb=1 stealth=1 CSACTUAL=31 stst=1

klippy_3.log (140.7 KB)

For me as a total n00b in software programming matters it somehow looks like a bug.

Thank’s in advance for having a look at it.

EDIT: Well the workaround I accidentially found works… moving it to the first Z_TILT_ADJUST probe-point with G1.