3diy
/
klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Update Multi_MCU_Homing.md to note the importance of low-latency 

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor 2024-01-04 19:06:00 -05:00
parent 1ea9f3aa35
commit 447a88eb08
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/Multi_MCU_Homing.md
View File

@ -31,9 +31,15 @@ overshoot and account for it in its calculations. However, it is
important that the hardware design is capable of handling overshoot important that the hardware design is capable of handling overshoot
without causing damage to the machine. without causing damage to the machine.
Should Klipper detect a communication issue between micro-controllers In order to use this "multi-mcu homing" capability the hardware must
during multi-mcu homing then it will raise a "Communication timeout have predictably low latency between the host computer and all of the
during homing" error. micro-controllers. Typically the round-trip time must be consistently
less than 10ms. High latency (even for short periods) is likely to
result in homing failures.
Should high latency result in a failure (or if some other
communication issue is detected) then Klipper will raise a
"Communication timeout during homing" error.
Note that an axis with multiple steppers (eg, `stepper_z` and Note that an axis with multiple steppers (eg, `stepper_z` and
`stepper_z1`) need to be on the same micro-controller in order to use `stepper_z1`) need to be on the same micro-controller in order to use