Z axis not homing after extruder exchange

General Discussion
1

Basic Information:

Printer Model: Ender 5
MCU / Printerboard: Manta M8P
Host / SBC Do not know
klippy.log

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:

… My printer was working properly. About a week ago I installed an Orbiter v2 and an Orbiter Sensor.
When I powered up, did not see any “magic smoke”. Extruder and sensor were working fine.

Then I tried to print something. Printer would not home Z axis. Cannot Print.
Z Stepper was a little bit hotter than X or Y steppers.
Tried using different cable - no Z stepper response
Tried connecting Z stepper to different motor port on M8P - no Z stepper response.
Tried swapping Z and X cable connections - no homing at all.

What else can I do? Is it the stepper or the board bad?

klippy(1).zip (13.7 KB)

2

Update 1
Disconnected Extruder - Z stepper not responding.
Removed the Z stepper motor. Connected to Y Stepper cable, the motor moves.

So, the problem is not the motor.

Could it be the klipper configuration?

3

Is it intentional that you only have a [tmc2209 stepper_...] for Y and extruder?

4

For Y, i was trying sensorless homing becuase i could not get the physical Y endstoop to work. Did not try for X, and for Z read that due to the physics of may printer, Z would not be very reliable.

When I installed the Orbiter, part of the configuration required the TMC stepper to be active. The only way klipper would accept that was by enabling the UART

5

Well, my stupid question above could have given you the hint that it is required to have these configuration blocks for all involved TMC drivers.

Klipper uses these configuration blocks to correctly set the needed parameters, like current, stealth-chop vs. spread-cycle etc. Also, it is used to constantly monitor the driver’s status and react upon potential errors.

Set it for all your TMC drivers and see if it solves your issue.

6

will try your suggestion. will keep you posted. thanks for the idea

7

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