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

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

Browse source
This commit is contained in:
KevinOConnor 2022-08-27 00:04:27 +00:00
parent 162bcabe1f
commit fdc229efa7
22 changed files with 726 additions and 695 deletions
Download patch file Download diff file Expand all files Collapse all files

10
zh/API_Server.html
View file

@ -1005,8 +1005,8 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#info" class="md-nav__link">
info
<a href="#_3" class="md-nav__link">
信息
</a>
</li>
@ -1465,8 +1465,8 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#info" class="md-nav__link">
info
<a href="#_3" class="md-nav__link">
信息
</a>
</li>
@ -1661,7 +1661,7 @@
<p>A subscription request accepts a "response_template" dictionary in the "params" field of the request. That "response_template" dictionary is used as a template for future asynchronous messages - it may contain arbitrary key/value pairs. When sending these future asynchronous messages, Klipper will add a "params" field containing a dictionary with "endpoint" specific contents to the response template and then send that template. If a "response_template" field is not provided then it defaults to an empty dictionary (<code>{}</code>).</p>
<h2 id="endpoint">可用的"endpoint"<a class="headerlink" href="#endpoint" title="Permanent link">&para;</a></h2>
<p>By convention, Klipper "endpoints" are of the form <code>&lt;module_name&gt;/&lt;some_name&gt;</code>. When making a request to an "endpoint", the full name must be set in the "method" parameter of the request dictionary (eg, <code>{"method"="gcode/restart"}</code>).</p>
<h3 id="info">info<a class="headerlink" href="#info" title="Permanent link">&para;</a></h3>
<h3 id="_3">信息<a class="headerlink" href="#_3" title="Permanent link">&para;</a></h3>
<p>The "info" endpoint is used to obtain system and version information from Klipper. It is also used to provide the client's version information to Klipper. For example: <code>{"id": 123, "method": "info", "params": { "client_info": { "version": "v1"}}}</code></p>
<p>If present, the "client_info" parameter must be a dictionary, but that dictionary may have arbitrary contents. Clients are encouraged to provide the name of the client and its software version when first connecting to the Klipper API server.</p>
<h3 id="emergency_stop">emergency_stop<a class="headerlink" href="#emergency_stop" title="Permanent link">&para;</a></h3>