[Older topic addendum Solved] "CANBUS Communication timeout while

Communication Timeout During Homing Probe. Pigeon Nest Or Tower Used By Homing Communication Pigeons Delft the communication with probe is very slow (M102 sS-5 take more then a minute) If the change has been set reboot the Pi with sudo reboot

CANBUS Communication timeout while homing Z 5 by charlespick
CANBUS Communication timeout while homing Z 5 by charlespick from klipper.discourse.group

Looking at when your issue was opened i don't believe BTT is very active here.. The Z_Probe was going out of range, I recently rebuilt the hot end and moved the probe

CANBUS Communication timeout while homing Z 5 by charlespick

Then confirm it by running cat klipper/klippy/mcu.py | grep "TRSYNC_TIMEOUT =" again Did you find a solution in the meantime? I ran into ai similar timeout but with x homing Basic Information: Printer Model: Voron 2.4 MCU / Printerboard: Octopus, Canable, EBB36 klippy.log (1.3 MB) Recently reflashed my pi, eb36, and octopus

Communication timeout during homing probe + Extrude below Min Temp. The extruder was working at a target of 225°C; The extruder heating gets turned off since the print is about to end; The print apparently finished: Finished SD card print Now without any startup procedure a new print seems to have started: Starting SD card print (position 0) The result is that it does not work because the new print has not been correctly initialized. If the change has been set reboot the Pi with sudo reboot

Communication timeout during homing probe + Extrude below Min Temp. I'm using a cannable for my toolhead, just usb for the octopus Did you find a solution in the meantime? I ran into ai similar timeout but with x homing