[BUG] Z axis might not work well with tap

[gyscos]

Describe the bug
Running AUTO_SPEED AXIS=Z on my voron 2.4 with tap sensor, it appears that all "missed steps" checks reported with 0.00 or 0.03. As a result it recommended the highest possible speed, which sounds unrealistic.

To Reproduce
Steps to reproduce the behavior:

1. Get a voron 2.4 with tap sensor
2. Run AUTO_SPEED AXIS=Z
3. Observe very optimistic recommendations

Printer (please complete the following information):

• Printer: Voron 2.4
• Kinematics Flying-gantry CoreXY
• klippy.log attached

Additional context
Add any other context about the problem here.

[AlatusAles]

Вверх!
Я получаю нереалистичные значения.

[stepper_z]
enable_pin:!PG2
step_pin:PF9
dir_pin:PF10
rotation_distance:4.0
microsteps:64
endstop_pin:probe:z_virtual_endstop
position_min:-1.0
position_max:291
homing_speed:5

[tmc2209 stepper_z]
uart_pin:PF2
sense_resistor:0.11
run_current:0.9
hold_current:0.9
stealthchop_threshold:0.0
interpolate:false
driver_TBL:2
driver_TOFF:12
driver_HSTRT:7
driver_HEND:1

[stepper_z1]
enable_pin:!PF1
step_pin:PC13
dir_pin:PF0
rotation_distance:4.0
microsteps:64

[tmc2209 stepper_z1]
uart_pin:PE4
sense_resistor:0.11
run_current:0.9
hold_current:0.9
stealthchop_threshold:0.0
interpolate:false
driver_TBL:1
driver_TOFF:12
driver_HSTRT:7
driver_HEND:0

[stepper_z2]
enable_pin:!PG5
step_pin:PF11
dir_pin:PG3
rotation_distance:4.0
microsteps:64

[tmc2209 stepper_z2]
uart_pin:PC6
sense_resistor:0.11
run_current:0.9
hold_current:0.9
stealthchop_threshold:0.0
interpolate:false
driver_TBL:2
driver_TOFF:12
driver_HSTRT:7
driver_HEND:0

[stepper_z3]
enable_pin:!PA2
step_pin:PG4
dir_pin:PC1
rotation_distance:4.0
microsteps:64

[tmc2209 stepper_z3]
uart_pin:PC7
sense_resistor:0.11
run_current:0.9
hold_current:0.9
stealthchop_threshold:0.0
interpolate:false
driver_TBL:3
driver_TOFF:10
driver_HSTRT:7
driver_HEND:0

[GavinHanson]

Can confirm, I'm also seeing this same result.