Deploying to gh-pages from @ Klipper3d/klipper@6773ab074b 🚀

This commit is contained in:
KevinOConnor
2025-07-27 16:13:28 +00:00
parent 445d9129ea
commit dcc1e88401
24 changed files with 17 additions and 17 deletions

View File

@@ -1523,7 +1523,7 @@ load cell and resport statistics:</p>
<li>'Unique values' should be a large percentage of the 'Samples
Collected' value. If 'Unique values' is 1 it is very likely a wiring issue.</li>
<li>Tap or push on the sensor while <code>LOAD_CELL_DIAGNOSTIC</code> runs. If
things are working correctly ths should increase the 'Sample range'.</li>
things are working correctly this should increase the 'Sample range'.</li>
</ul>
<h2 id="calibrating-a-load-cell">Calibrating a Load Cell<a class="headerlink" href="#calibrating-a-load-cell" title="Permanent link">&para;</a></h2>
<p>Load cells are calibrated using the <code>LOAD_CELL_CALIBRATE</code> command. This is an
@@ -1648,7 +1648,7 @@ the <code>PROBE</code> command, load_cell_probe will tare the endstop at the cur
Multiple cycles of this will result in ever-increasing force on the toolhead.
<code>force_safety_limit</code> stops this cycle from running out of control.</p>
<p>Another way this run-away can happen is damage to a strain gauge. If the metal
part is permanently bent it wil change the <code>reference_tare_counts</code> of the
part is permanently bent it will change the <code>reference_tare_counts</code> of the
device. This puts the starting tare value much closer to the limit making it
more likely to be violated. You want to be notified if this is happening
because your hardware has been permanently damaged.</p>