Deploying to gh-pages from @ Klipper3d/klipper@8d7e487149 🚀

This commit is contained in:
KevinOConnor 2025-05-29 23:32:56 +00:00
parent 3dcdeaff9a
commit 24c01d2836
18 changed files with 514 additions and 11 deletions

View file

@ -1181,6 +1181,13 @@
load_cell/dump_force
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_probedump_taps" class="md-nav__link">
load_cell_probe/dump_taps
</a>
</li>
<li class="md-nav__item">
@ -1711,6 +1718,13 @@
load_cell/dump_force
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_probedump_taps" class="md-nav__link">
load_cell_probe/dump_taps
</a>
</li>
<li class="md-nav__item">
@ -2065,6 +2079,25 @@ and might later produce asynchronous messages such as:
<code>{"params":{"data":[[3292.432935, 40.65, 562534, -234467]]}}</code></p>
<p>The "header" field in the initial query response is used to describe
the fields found in later "data" responses.</p>
<h3 id="load_cell_probedump_taps">load_cell_probe/dump_taps<a class="headerlink" href="#load_cell_probedump_taps" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to details of probing "tap" events.
Using this endpoint may increase Klipper's system load.</p>
<p>A request may look like:
<code>{"id": 123, "method":"load_cell/dump_force",
"params": {"sensor": "load_cell", "response_template": {}}}</code>
and might return:
<code>{"id": 123,"result":{"header":["probe_tap_event"]}}</code>
and might later produce asynchronous messages such as:</p>
<div class="highlight"><pre><span></span><code>{&quot;params&quot;:{&quot;tap&quot;:&#39;{
&quot;time&quot;: [118032.28039, 118032.2834, ...],
&quot;force&quot;: [-459.4213119680034, -458.1640702543264, ...],
}}}
</code></pre></div>
<p>This data can be used to render:</p>
<ul>
<li>The time/force graph</li>
</ul>
<h3 id="pause_resumecancel">pause_resume/cancel<a class="headerlink" href="#pause_resumecancel" title="Permanent link">&para;</a></h3>
<p>This endpoint is similar to running the "PRINT_CANCEL" G-Code command.
For example: