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

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

Browse Source
This commit is contained in:
KevinOConnor
2024-01-16 19:22:15 +00:00
parent da4bd4dedf
commit ab87805025
14 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
Multi_MCU_Homing.html
View File

@@ -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
during multi-mcu homing then it will raise a "Communication timeout
during homing" error.</p>
<p>In order to use this "multi-mcu homing" capability the hardware must
have predictably low latency between the host computer and all of the
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