Dual z axis won't "home"

General Discussion
1

Basic Information:

Printer Model: Flyingbear Reborn with RatRig/EVA 3.0 Mod
MCU / Printerboard: BTT OCtopus

Dear all,

after hours of trying this issue drives me crazy :frowning:

I completely rubuilt my FB reborn to a BTT Octopus + EBB36 setup. Everything is running fine, but not my two Z axis.

I have a leadscrews (stepper_z, stepper_z1) on each side of the bed with two endstops (one for each motor).

When I’m homing - than homing stops if the first endstop (normally the right one) is triggered. I have to manually adjuste the left side so that the second endstop is also triggered. Same game while “second homing” attempt with lower speed :frowning:

From my old marlin setup, ervything was automatic - means each z motor is running as long as “his” endstop is triggered.

Any Idea, what I’m doing wrong?

#Z-Right
[stepper_z]
step_pin: PF11
dir_pin: !PG3
enable_pin: !PG5
microsteps: 4
rotation_distance: 8
endstop_pin: !PG9
position_endstop: 0
position_max: 300
homing_speed: 10
second_homing_speed: 2

[tmc2209 stepper_z]
uart_pin: PC6
run_current: 1.25
hold_current: 0.80
stealthchop_threshold: 0

#Z-Left
[stepper_z1]
step_pin: PG4
dir_pin: !PC1
enable_pin: !PA0
microsteps: 4
rotation_distance: 8
endstop_pin: !PG10

[tmc2209 stepper_z1]
uart_pin: PC7
run_current: 1.25
hold_current: 0.80
stealthchop_threshold: 0

2

Hello @Vincenth !

Have you seen this:

Also: Can you share the klippy.log as it was asked for?

3

Yes already seen the post for sure. But didnt try yet - tmc2209 uart is runing fine on both axis - have to take apart half of the printer to reach the stepsticks
:frowning:

Sorry I’m new to klipper - when I’m bacj home, I’ll try tonfind that klippy.log an post :wink:

4

At the end it’s always a users problem an not the one of the printer :slight_smile:

To sum it up - I totally oversee that on any octopus board the stepstick “motor_2” shares two (!!!) connecotrs for motors an not one like the others do. So in this case, I connected both steppers to one driver and didn’t check that - shame on me :frowning:

Now its working fine!

1 Like