I’m experiencing intermittent z-tilt failures reporting:
No trigger on probe after full movement
However, the system (presumably klipper/klippy) knows that a full movement has not been completed (see screenshot).
From the screenshot you can see that there was a successful probe at the first of the z-tilt locations. The probe is at the second of the locations and the reported z height is 18.92. The z_tilt configuration is pasted below but also in the logs, from it you can see that there is a z backoff of 20 mm. So, if the current z height is 18.92 this was not a full move.
[z_tilt]
z_positions =
0,0
200,400
400,0
points =
60, 37.5
200, 317.5
340, 37.5
horizontal_move_z = 20
retries = 10
retry_tolerance = 0.02
speed = 300
klippy.log (189.5 KB)
Digging into this, looks like it may in fact be a Beacon issue, as the error message is unique to their code.
In chatting with a member of the Annex Engineering Discord, they pointed out that the error is in fact from Klipper. Specifically from this section:
for mcu_endstop, name in self.endstops:
try:
trigger_time = mcu_endstop.home_wait(move_end_print_time)
except self.printer.command_error as e:
if error is None:
error = "Error during homing %s: %s" % (name, str(e))
continue
if trigger_time > 0.:
trigger_times[name] = trigger_time
elif check_triggered and error is None:
error = "No trigger on %s after full movement" % (name,)
# Determine stepper halt positions
self.toolhead.flush_step_generation()
for sp in self.stepper_positions:
tt = trigger_times.get(sp.endstop_name, move_end_print_time)
sp.note_home_end(tt)
if probe_pos:
halt_steps = {sp.stepper_name: sp.halt_pos - sp.start_pos
for sp in self.stepper_positions}
trig_steps = {sp.stepper_name: sp.trig_pos - sp.start_pos
for sp in self.stepper_positions}
The error is not from Klipper, it’s the error message .
As for the log, all test points have been successfully been probed three times before.
When it came to the fourth time of probing, after the first point, the issue occurred.
Is this reproducible?
BTW: You may tidy up your printer.cfg. Ther is [stepper_z] at the beginning and 500 lines later the other steppers and also the [tmc2240 stepper_z]
Yes, this is reproducible. We (Annex Enigneering and I) have found the root cause is a communication error. The error message in its above form is incorrect (there was no full move) and is being improved/changed:
1 Like
system
December 2, 2024, 4:38pm
6
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
