Must home all axis while 3D Beacon Probe set up

General Discussion
1

Basic Information:

Printer Model: Panda Cube
MCU / Printerboard: SKR V1.4
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:

Yesterday I set up my new 3D Beacon Probe. For that I had to move the printhead to the middle of the bed. But my printer only allows that, when ALL axis have been homed. But for that to work I have to have a working Endstop/Probe for the z-axis. Normally homing x and y is sufficient for movement that only requieres moving the x and y-axis. Only temporarily turning off everything related to z_tilt_adjust and mesh_bed_leveling made it possible to use the x and y-axis whitout homing the z-axis. Maybe thats helpful to someone.
klippy(4).log (7.9 MB)

2

Sorry, what is that?

[stepper_z]
step_pin = EXP2_6
dir_pin = !EXP2_5
enable_pin = !EXP2_7
microsteps = 32
rotation_distance = 8
endstop_pin = probe:z_virtual_endstop
homing_retract_dist = 0
position_max = 235
position_min = -40

[tmc2208 stepper_z]
uart_pin = EXP1_6
run_current = 0.650
stealthchop_threshold = 999999

[stepper_z1]
step_pin = P0.22
dir_pin = !P2.11
enable_pin = !P0.21
microsteps = 32
rotation_distance = 8
endstop_pin = probe:z_virtual_endstop   # <--------------

[tmc2209 stepper_z1]
uart_pin = P1.8
run_current = 0.650
stealthchop_threshold = 999999

[stepper_z2]
step_pin = EXP2_3
dir_pin = !EXP2_4
enable_pin = !EXP1_8
microsteps = 32
rotation_distance = 8
endstop_pin = probe:z_virtual_endstop   # <--------------

[tmc2208 stepper_z2]
uart_pin = EXP1_4
run_current = 0.650
stealthchop_threshold = 999999

Applies also to triple z axes

3

What excactly do you mean? In general these are all the z-motors which I use for my independent triple z set up. Similiar to what the rat-rig uses.

4

Only [stepper_z] has endstop_pin = probe:z_virtual_endstop
The other (z1,z2, …) have not.

5

Didn’t know that. I mean it still worked fine for months. Or is that the cause why I had to temporarily turn off mesh bed leveling for the beacon set up?

6

Or is that the cause why I had to temporarily turn off mesh bed leveling [and z_tilt_adjust] for the beacon set up?

You had to turn those off because they require moving the Z axis to get into position (especially if it was previously set up for a BLTouch), and you cannot move your Z axis into position until you home your Z axis, which you cannot do until you have your probe set up… which you already mentioned as part of your issue. Until the probe is set up, you simply cannot have the machine move the Z axis for anything other than setting up the probe (such as running a backlash test or determining the Z offset), unless you’re using physical endstop switches to home it first. This is not a bug, it is a feature. You can potentially cause a lot of damage if you smash your hotend into your bed.

Besides, you’re going to want a different mesh setup with the Beacon anyway, it can easily do a 100 x 100 mesh in less time than it would take to do a 5 x 5 with the BLTouch since it can move constantly while taking measurements multiple times a second.

7

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