From 8e6e467ebc16f93ab01ed63c55d24af52b020b54 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Sun, 14 Dec 2025 15:31:09 -0500 Subject: [PATCH] mcu: Fix incorrect reqclock during endstop homing For correct operation the trsync system must be programmed prior to the start of endstop checking. This means the desired "reqclock" for the trsync configuration messages need to use the same "clock" that the endstop start message uses - even though the actual deadline for these messages is later. Signed-off-by: Kevin O'Connor --- klippy/mcu.py | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/klippy/mcu.py b/klippy/mcu.py index d9bd34fb8..507f77347 100644 --- a/klippy/mcu.py +++ b/klippy/mcu.py @@ -219,12 +219,11 @@ class MCU_trsync: self._mcu.register_response(self._handle_trsync_state, "trsync_state", self._oid) self._trsync_start_cmd.send([self._oid, report_clock, report_ticks, - self.REASON_COMMS_TIMEOUT], - reqclock=report_clock) + self.REASON_COMMS_TIMEOUT], reqclock=clock) for s in self._steppers: self._stepper_stop_cmd.send([s.get_oid(), self._oid]) self._trsync_set_timeout_cmd.send([self._oid, expire_clock], - reqclock=expire_clock) + reqclock=clock) def set_home_end_time(self, home_end_time): self._home_end_clock = self._mcu.print_time_to_clock(home_end_time) def stop(self):