3D-printing/klipper
1
0
Fork 0
mirror of https://github.com/Klipper3d/klipper.git synced 2025-07-24 07:04:01 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Deploying to gh-pages from @ Klipper3d/klipper@f3b995227a 🚀

Browse source
This commit is contained in:
KevinOConnor 2022-04-09 20:31:56 +00:00
parent 21245a37f1
commit 6585e6a6c3
24 changed files with 881 additions and 373 deletions
Download patch file Download diff file Expand all files Collapse all files

18
zh/API_Server.html
View file

@ -1074,6 +1074,13 @@
adxl345/dump_adxl345
</a>
</li>
<li class="md-nav__item">
<a href="#angledump_angle" class="md-nav__link">
angle/dump_angle
</a>
</li>
<li class="md-nav__item">
@ -1512,6 +1519,13 @@
adxl345/dump_adxl345
</a>
</li>
<li class="md-nav__item">
<a href="#angledump_angle" class="md-nav__link">
angle/dump_angle
</a>
</li>
<li class="md-nav__item">
@ -1656,6 +1670,10 @@ gcode:
<p>This endpoint is used to subscribe to ADXL345 accelerometer data. Obtaining these low-level motion updates may be useful for diagnostic and debugging purposes. Using this endpoint may increase Klipper's system load.</p>
<p>A request may look like: <code>{"id": 123, "method":"adxl345/dump_adxl345", "params": {"sensor": "adxl345", "response_template": {}}}</code> and might return: <code>{"id": 123,"result":{"header":["time","x_acceleration","y_acceleration", "z_acceleration"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"overflows":0,"data":[[3292.432935,-535.44309,-1529.8374,9561.4], [3292.433256,-382.45935,-1606.32927,9561.48375]]}}</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="angledump_angle">angle/dump_angle<a class="headerlink" href="#angledump_angle" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to <a href="Config_Reference.html#angle">angle sensor data</a>. Obtaining these low-level motion updates may be useful for diagnostic and debugging purposes. Using this endpoint may increase Klipper's system load.</p>
<p>A request may look like: <code>{"id": 123, "method":"angle/dump_angle", "params": {"sensor": "my_angle_sensor", "response_template": {}}}</code> and might return: <code>{"id": 123,"result":{"header":["time","angle"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"position_offset":3.151562,"errors":0, "data":[[1290.951905,-5063],[1290.952321,-5065]]}}</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="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: <code>{"id": 123, "method": "pause_resume/cancel"}</code></p>
<p>As with the "gcode/script" endpoint, this endpoint only completes after any pending G-Code commands complete.</p>