Deploying to gh-pages from @ Klipper3d/klipper@447a88eb08 🚀

Multi_MCU_Homing.html

@@ -1314,9 +1314,14 @@ the homing and probing procedure. The Klipper code will detect the
 overshoot and account for it in its calculations. However, it is
 important that the hardware design is capable of handling overshoot
 without causing damage to the machine.</p>
-<p>Should Klipper detect a communication issue between micro-controllers
+<p>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.</p>
+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.</p>
+<p>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.</p>
 <p>Note that an axis with multiple steppers (eg, <code>stepper_z</code> and
 <code>stepper_z1</code>) need to be on the same micro-controller in order to use
 multi-mcu homing. For example, if an endstop is on a separate