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

Deploying to gh-pages from @ Klipper3d/klipper@1cc6398074 🚀

Browse Source
This commit is contained in:
KevinOConnor
2025-05-04 00:06:21 +00:00
parent 9d64784cd9
commit 06b88075fb
308 changed files with 12816 additions and 2971 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
zh/404.html
View File

@@ -1281,8 +1281,8 @@
<li class="md-nav__item">
<a href="/Load_Cell.md" class="md-nav__link">
None
<a href="/Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

36
zh/API_Server.html
View File

@@ -1177,15 +1177,8 @@
</li>
<li class="md-nav__item">
<a href="#hx71xdump_hx71x" class="md-nav__link">
hx71x/dump_hx71x
</a>
</li>
<li class="md-nav__item">
<a href="#ads1220dump_ads1220" class="md-nav__link">
ads1220/dump_ads1220
<a href="#load_celldump_force" class="md-nav__link">
load_cell/dump_force
</a>
</li>
@@ -1517,8 +1510,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1714,15 +1707,8 @@
</li>
<li class="md-nav__item">
<a href="#hx71xdump_hx71x" class="md-nav__link">
hx71x/dump_hx71x
</a>
</li>
<li class="md-nav__item">
<a href="#ads1220dump_ads1220" class="md-nav__link">
ads1220/dump_ads1220
<a href="#load_celldump_force" class="md-nav__link">
load_cell/dump_force
</a>
</li>
@@ -1881,12 +1867,10 @@ gcode:
<p>该端点用于订阅<a href="Config_Reference.html#Angel">角度传感器数据</a>。获取这些低级运动更新对于诊断和调试目的可能有用。使用此终结点可能会增加Klipper的系统负载。</p>
<p>请求可能类似于：<code>{“id”：123，“方法”：“角度/转储_角度”，“参数”：{“传感器”：“我的角度_传感器”，“响应模板”：{}</code>，并且可能返回：<code>{“id”：123，“结果”：{“标题”：[“时间”，“角度”]}}</code>，并且可能稍后产生诸如：<code>{“参数”：{“位置偏移量”：3.151562，“错误”：0,“data”：[[1290.951905，-5063]，[1290.952321，-5065]}}</code></p>
<p>初始查询响应中的“Header”字段用于描述在随后的“数据”响应中找到的字段。</p>
<h3 id="hx71xdump_hx71x">hx71x/dump_hx71x<a class="headerlink" href="#hx71xdump_hx71x" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to raw HX711 and HX717 ADC data. Obtaining these low-level ADC 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":"hx71x/dump_hx71x", "params": {"sensor": "load_cell", "response_template": {}}}</code> and might return: <code>{"id": 123,"result":{"header":["time","counts","value"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"data":[[3292.432935, 562534, 0.067059278], [3292.4394937, 5625322, 0.670590639]]}}</code></p>
<h3 id="ads1220dump_ads1220">ads1220/dump_ads1220<a class="headerlink" href="#ads1220dump_ads1220" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to raw ADS1220 ADC data. Obtaining these low-level ADC 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":"ads1220/dump_ads1220", "params": {"sensor": "load_cell", "response_template": {}}}</code> and might return: <code>{"id": 123,"result":{"header":["time","counts","value"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"data":[[3292.432935, 562534, 0.067059278], [3292.4394937, 5625322, 0.670590639]]}}</code></p>
<h3 id="load_celldump_force">load_cell/dump_force<a class="headerlink" href="#load_celldump_force" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to force data produced by a load_cell. 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":["time", "force (g)", "counts", "tare_counts"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"data":[[3292.432935, 40.65, 562534, -234467]]}}</code></p>
<p>初始查询响应中的“Header”字段用于描述在随后的“数据”响应中找到的字段。</p>
<h3 id="_">暂停_继续/取消<a class="headerlink" href="#_" title="Permanent link">&para;</a></h3>
<p>该端点类似于运行“PRINT_CANCEL”G-Code命令。例如：<code>{“id”：123，“方法”：“PAUSE_RESUME/Cancel”}</code></p>
<p>与“gcode/脚本”终结点一样，该终结点只有在所有挂起的G-Code命令完成后才会完成。</p>

50
zh/Axis_Twist_Compensation.html
View File

@@ -726,13 +726,6 @@
For Y-Axis Calibration
</a>
</li>
<li class="md-nav__item">
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
Automatic Calibration for Both Axes
</a>
</li>
</ul>
@@ -1365,8 +1358,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1440,13 +1433,6 @@
For Y-Axis Calibration
</a>
</li>
<li class="md-nav__item">
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
Automatic Calibration for Both Axes
</a>
</li>
</ul>
@@ -1479,7 +1465,7 @@
<h1 id="_1">轴扭曲补偿<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h1>
<p>本文档介绍了[AXIS_TWIST_COMPOMENT]模块。</p>
<p>This document describes the <code>[axis_twist_compensation]</code> module.</p>
<p>Some printers may have a small twist in their X rail which can skew the results of a probe attached to the X carriage. This is common in printers with designs like the Prusa MK3, Sovol SV06 etc and is further described under <a href="Probe_Calibrate.html#location-bias-check">probe location
bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed Mesh</a>, <a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a>, <a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a> etc returning inaccurate representations of the bed.</p>
<p>该模块使用用户手动测量来修正探头的结果。请注意，如果您的轴严重扭曲，强烈建议您在应用软件更正之前首先使用机械方法修复它。</p>
@@ -1495,42 +1481,38 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE
</code></pre></div>
<p>This command will calibrate the X-axis by default. - The calibration wizard will prompt you to measure the probe Z offset at several points along the bed. - By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=&lt;value&gt;</code></p>
<p>This command will calibrate the X-axis by default.</p>
<ul>
<li>The calibration wizard will prompt you to measure the probe Z offset at several points along the bed.</li>
<li>By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=&lt;value&gt;</code></li>
</ul>
<ol>
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).</li>
<li>
<p><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</p>
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to <a href="Probe_Calibrate.html#calibrating-probe-z-offset">adjust your Z offset</a>.</li>
<li><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</li>
</ol>
<ul>
<li><a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a></li>
<li><a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a></li>
</ul>
</li>
<li>
<p><strong>Finalize the Setup:</strong></p>
<ol>
<li><strong>Finalize the Setup:</strong></li>
</ol>
<ul>
<li>Home all axes, and perform a <a href="Bed_Mesh.html">Bed Mesh</a> if necessary.</li>
<li>Run a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> if needed.</li>
</ul>
</li>
</ol>
<h3 id="for-y-axis-calibration">For Y-Axis Calibration<a class="headerlink" href="#for-y-axis-calibration" title="Permanent link">&para;</a></h3>
<p>The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:</p>
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y
</code></pre></div>
<p>This will guide you through the same measuring process as for the X-axis.</p>
<h3 id="automatic-calibration-for-both-axes">Automatic Calibration for Both Axes<a class="headerlink" href="#automatic-calibration-for-both-axes" title="Permanent link">&para;</a></h3>
<p>To perform automatic calibration for both the X and Y axes without manual intervention, use:</p>
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
</code></pre></div>
<p>In this mode, the calibration process will run for both axes automatically.</p>
<blockquote>
<p><strong>提示：</strong>床温、喷嘴温度和尺寸似乎对校准过程没有影响。</p>
</blockquote>
<h2 id="axis_twist_commention">[AXIS_TWIST_COMMENTION]设置和命令<a class="headerlink" href="#axis_twist_commention" title="Permanent link">&para;</a></h2>
<p>可在<a href="Config_Reference.html#axis_twist_compensation">配置Reference</a>.]中找到[AXIS_TWIST_COMPOMENT]的配置选项。</p>
<p>可在<a href="G-Codes.html#axis_twist_compensation">G-Codes Reference</a>]中找到[AXIS_TWIST_COMPATION]的命令</p>
<p>Configuration options for <code>[axis_twist_compensation]</code> can be found in the <a href="Config_Reference.html#axis_twist_compensation">Configuration Reference</a>.</p>
<p>Commands for <code>[axis_twist_compensation]</code> can be found in the <a href="G-Codes.html#axis_twist_compensation">G-Codes Reference</a></p>
</article>

4
zh/BLTouch.html
View File

@@ -1380,8 +1380,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Beaglebone.html
View File

@@ -1399,8 +1399,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Bed_Level.html
View File

@@ -1345,8 +1345,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Bed_Mesh.html
View File

@@ -1568,8 +1568,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

28
zh/Benchmarks.html
View File

@@ -1475,8 +1475,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1985,30 +1985,30 @@ finalize_config crc=0
</tbody>
</table>
<h3 id="stm32h7">STM32H7 步进率基准测试<a class="headerlink" href="#stm32h7" title="Permanent link">&para;</a></h3>
<p>在STM32H743VIT6上使用以下配置序列：</p>
<p>The following configuration sequence is used on STM32H723:</p>
<div class="highlight"><pre><span></span><code>allocate_oids count=3
config_stepper oid=0 step_pin=PD4 dir_pin=PD3 invert_step=-1 step_pulse_ticks=0
config_stepper oid=1 step_pin=PA15 dir_pin=PA8 invert_step=-1 step_pulse_ticks=0
config_stepper oid=2 step_pin=PE2 dir_pin=PE3 invert_step=-1 step_pulse_ticks=0
config_stepper oid=0 step_pin=PA13 dir_pin=PB5 invert_step=-1 step_pulse_ticks=52
config_stepper oid=1 step_pin=PB2 dir_pin=PB6 invert_step=-1 step_pulse_ticks=52
config_stepper oid=2 step_pin=PB3 dir_pin=PB7 invert_step=-1 step_pulse_ticks=52
finalize_config crc=0
</code></pre></div>
<p>该测试最后一次运行基于提交 <code>00191b5c</code>，gcc 版本为 <code>arm-none-eabi-gcc (15:8-2019-q3-1+b1) 8.3.1 20190703 (release) [gcc-8-branch revision 273027]</code>。</p>
<p>The test was last run on commit <code>554ae78d</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code>.</p>
<table>
<thead>
<tr>
<th>stm32h7</th>
<th>stm32h723</th>
<th>ticks</th>
</tr>
</thead>
<tbody>
<tr>
<td>1个步进电机</td>
<td>44</td>
<td>70</td>
</tr>
<tr>
<td>3个步进电机</td>
<td>198</td>
<td>181</td>
</tr>
</tbody>
</table>
@@ -2215,7 +2215,7 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
finalize_config crc=0
</code></pre></div>
<p>The test was last run on commit <code>f6718291</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
<p>The test was last run on commit <code>14c105b8</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
<table>
<thead>
<tr>
@@ -2226,11 +2226,11 @@ finalize_config crc=0
<tbody>
<tr>
<td>1个步进电机</td>
<td>5</td>
<td>3</td>
</tr>
<tr>
<td>3个步进电机</td>
<td>22</td>
<td>14</td>
</tr>
</tbody>
</table>
@@ -2252,7 +2252,7 @@ finalize_config crc=0
</tr>
</tbody>
</table>
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 125Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM core cycles.</p>
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 200Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 ARM core cycles.</p>
<h3 id="linux-mcu">Linux MCU 步速率基准测试<a class="headerlink" href="#linux-mcu" title="Permanent link">&para;</a></h3>
<p>树莓派上使用以下配置序列：</p>
<div class="highlight"><pre><span></span><code>allocate_oids count=3

4
zh/Bootloader_Entry.html
View File

@@ -1429,8 +1429,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Bootloaders.html
View File

@@ -1501,8 +1501,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

5
zh/CANBUS.html
View File

@@ -1371,8 +1371,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1549,6 +1549,7 @@ iface can0 can static
</li>
</ul>
<ul>
<li>It is only valid to use USB to CAN bridge mode if there is a functioning CAN bus with at least one other node available (in addition to the bridge node itself). Use a standard USB configuration if the goal is to communicate only with the single USB device. Using USB to CAN bridge mode without a fully functioning CAN bus (including terminating resistors and an additional node) may result in sporadic errors even when communicating with the bridge node.</li>
<li>USB转CAN桥板不会显示为USB串口设备，也不会在运行<code>ls/dev/Serial/by-id</code>时出现，也不能在Klipper的printer.cfg文件中使用<code>Serial：</code>参数进行配置。桥接板显示为“USB CAN适配器”，并在printer.cfg中配置为<a href="#configuring-klipper">CAN节点</a>。</li>
</ul>
<h2 id="_4">故障排除提示<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>

38
zh/CANBUS_Troubleshooting.html
View File

@@ -1284,6 +1284,13 @@
使用适当的 txqueuelen 设置
</a>
</li>
<li class="md-nav__item">
<a href="#use-canbus_querypy-only-to-identify-nodes-never-previously-seen" class="md-nav__link">
Use canbus_query.py only to identify nodes never previously seen
</a>
</li>
<li class="md-nav__item">
@@ -1370,8 +1377,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1444,6 +1451,13 @@
使用适当的 txqueuelen 设置
</a>
</li>
<li class="md-nav__item">
<a href="#use-canbus_querypy-only-to-identify-nodes-never-previously-seen" class="md-nav__link">
Use canbus_query.py only to identify nodes never previously seen
</a>
</li>
<li class="md-nav__item">
@@ -1500,12 +1514,16 @@ resistors</a> on the CAN bus. If the resistors are not properly installed then m
<p>确认CAN总线接线上的所有插头和线夹都已完全固定。打印机刀头的移动可能会挤压CAN总线布线，导致不良的线缆卷曲或未固定的插头，从而导致间歇性通信错误。</p>
<h2 id="bytes_invalid">检查递增BYTES_INVALID计数器<a class="headerlink" href="#bytes_invalid" title="Permanent link">&para;</a></h2>
<p>当打印机处于活动状态时，Klipper日志文件将每秒报告一次<code>Stats‘行。对于每个微控制器，这些“Stat”行都将有一个</code>bytes_valid`计数器。在正常的打印机操作期间，此计数器不应递增(重新启动后计数器为非零值是正常的，如果计数器每月递增一次也无关紧要)。如果在正常打印过程中，CAN Bus微控制器上的此计数器增加(每隔几个小时或更频繁地增加一次)，则表示存在严重问题。</p>
<p>在CAN总线连接上递增<code>BYTES_INVALID</code>是CAN总线上消息重新排序的症状。消息重新排序有两个已知原因：</p>
<ol>
<li>用于USB CAN适配器的常用烛光固件的旧版本有一个错误，可能会导致消息重新排序。如果使用运行此固件的USB CAN适配器，则在观察到递增的<code>Bytes_Invalid</code>时，请确保更新到最新固件。</li>
<li>已知一些用于嵌入式设备的Linux内核版本会对CAN总线消息进行重新排序。可能需要使用替代的Linux内核，或者使用支持不存在此问题的主流Linux内核的替代硬件。</li>
</ol>
<p>重新排序的消息是一个必须解决的严重问题。这将导致行为不稳定，并可能导致打印的任何部分出现令人困惑的错误。</p>
<p>Incrementing <code>bytes_invalid</code> on a CAN bus connection is a symptom of reordered messages on the CAN bus. If seen, make sure to:</p>
<ul>
<li>Use a Linux kernel version 6.6.0 or later.</li>
<li>If using a USB-to-CANBUS adapter running candlelight firmware, use v2.0 or later of candleLight_fw.</li>
<li>If using Klipper's USB-to-CANBUS bridge mode, make sure the bridge node is flashed with Klipper v0.12.0 or later.</li>
</ul>
<p>Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print. An incrementing <code>bytes_invalid</code> is not caused by wiring or similar hardware issues and can only be fixed by identifying and updating the faulty software.</p>
<p>Older versions of the Linux kernel had a bug in the gs_usb canbus driver code that could cause reordered canbus packets. The issue is thought to be fixed in <a href="https://github.com/torvalds/linux/commit/24bc41b4558347672a3db61009c339b1f5692169">Linux commit 24bc41b4</a> which was released in v6.6.0. In some cases, older Linux versions may not show the problem (due to how hardware interrupts are configured), however if problems are seen the recommended solution is to upgrade to a newer kernel.</p>
<p>Older versions of candlelight firmware could reorder canbus packets, and the issue is thought to be fixed in <a href="https://github.com/candle-usb/candleLight_fw/commit/8b3a7b4565a3c9521b762b154c94c72c5acb2bcf">candlelight_fw commit 8b3a7b45</a>.</p>
<p>Older versions of Klipper's USB-to-CANBUS bridge code could incorrectly drop canbus messages. This is not as severe as reordering messages, but it should still be fixed. It is thought to be fixed with <a href="https://github.com/Klipper3d/klipper/pull/6175">Klipper PR #6175</a>.</p>
<h2 id="txqueuelen">使用适当的 txqueuelen 设置<a class="headerlink" href="#txqueuelen" title="Permanent link">&para;</a></h2>
<p>Klipper 代码使用 Linux 内核来管理 CAN 总线流量。默认情况下，内核只会排队 10 个 CAN 传输数据包。建议使用 <code>txqueuelen 128</code> <a href="CANBUS.html#host-hardware">配置 can0 设备</a> 来增加该大小。</p>
<p>如果 Klipper 传输了一个数据包，而 Linux 已经填满了其所有的传输队列空间，那么 Linux 将丢弃该数据包，并且 Klipper 日志中将出现如下消息：</p>
@@ -1517,6 +1535,10 @@ resistors</a> on the CAN bus. If the resistors are not properly installed then m
<p>可以通过运行 Linux 命令“ip link show can0”来检查当前队列大小。它应该会报告一堆文本，包括代码片段“qlen 128”。如果看到类似“qlen 10”的内容，则表明 CAN 设备尚未正确配置。</p>
<p>不建议使用明显大于 128 的 <code>txqueuelen</code>。以 1000000 频率运行的 CAN 总线通常需要大约 120us 来传输 CAN 数据包。因此，128 个数据包的队列可能需要大约 15-20ms 才能耗尽。大得多的队列可能会导致消息往返时间出现过度峰值，从而导致无法恢复的错误。换句话说，如果 Klipper 的应用程序重传系统不必等待 Linux 耗尽可能过时的过大队列，它会更加强大。这类似于互联网路由器上的 <a href="https://en.wikipedia.org/wiki/Bufferbloat">bufferbloat</a> 问题。</p>
<p>在正常情况下，Klipper 可能每个 MCU 使用约 25 个队列槽 - 通常仅在重传期间使用更多槽。（具体而言，Klipper 主机可能向每个 Klipper MCU 传输最多 192 个字节，然后才会收到该 MCU 的确认。）如果单个 CAN 总线上有 5 个或更多 Klipper MCU，则可能需要将<code>txqueuelen</code>增加到建议值 128 以上。但是，如上所述，选择新值时应小心谨慎，以避免过长的往返时间延迟。</p>
<h2 id="use-canbus_querypy-only-to-identify-nodes-never-previously-seen">Use <code>canbus_query.py</code> only to identify nodes never previously seen<a class="headerlink" href="#use-canbus_querypy-only-to-identify-nodes-never-previously-seen" title="Permanent link">&para;</a></h2>
<p>It is only valid to use the <a href="CANBUS.html#finding-the-canbus_uuid-for-new-micro-controllers"><code>canbus_query.py</code> tool</a> to identify micro-controllers that have never been previously identified. Once all nodes on a bus are identified, record the resulting uuids in the printer.cfg, and avoid running the tool unnecessarily.</p>
<p>The tool is implemented using a low-level mechanism that can cause nodes to internally observe bus errors. These internal errors may result in communication interruptions and may result is some nodes disconnecting from the bus.</p>
<p>It is not valid to use the tool to "ping" if a node is connected. Do not run the tool during an active print.</p>
<h2 id="candump">获取candump日志<a class="headerlink" href="#candump" title="Permanent link">&para;</a></h2>
<p>向微控制器发送和从微控制器发送的CAN总线消息由Linux内核处理。出于调试目的，可以从内核捕获这些消息。这些消息的日志可能在诊断中有用。</p>
<p>Linux<a href="https://github.com/linux-can/can-utils">can-utils</a>工具提供了捕获软件。通常通过运行以下命令将其安装在计算机上：</p>

4
zh/CANBUS_protocol.html
View File

@@ -1370,8 +1370,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/CONTRIBUTING.html
View File

@@ -1370,8 +1370,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Code_Overview.html
View File

@@ -1385,8 +1385,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Command_Templates.html
View File

@@ -1421,8 +1421,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

10
zh/Config_Changes.html
View File

@@ -1327,8 +1327,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1410,6 +1410,12 @@
<p>本文档涵盖了软件更新中对配置文件不向后兼容的部分。在升级 Klipper 时，最好也查看一下这份文档。</p>
<p>文档的所有日期都是大概时间。</p>
<h2 id="_2">变更<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<p>20250428: The maximum <code>cycle_time</code> for pwm <code>[output_pin]</code>, <code>[pwm_cycle_time]</code>, <code>[pwm_tool]</code>, and similar config sections is now 3 seconds (reduced from 5 seconds). The <code>maximum_mcu_duration</code> in <code>[pwm_tool]</code> is now also 3 seconds.</p>
<p>20250418: The manual_stepper <code>STOP_ON_ENDSTOP</code> feature may now take less time to complete. Previously, the command would wait the entire time the move could possibly take even if the endstop triggered earlier. Now, the command finishes shortly after the endstop trigger.</p>
<p>20250417: SPI devices using "software SPI" are now rate limited. Previously, the <code>spi_speed</code> in the config was ignored and the transmission speed was only limited by the processing speed of the micro-controller. Now, speeds are limited by the <code>spi_speed</code> config parameter (actual hardware speeds are likely to be lower than the configured value due to software overhead).</p>
<p>20250411: Klipper v0.13.0 released.</p>
<p>20250308: The <code>AUTO</code> parameter of the <code>AXIS_TWIST_COMPENSATION_CALIBRATE</code> command has been removed.</p>
<p>20250131: Option <code>VARIABLE=&lt;name&gt;</code> in <code>SAVE_VARIABLE</code> requires lowercase value. For example, <code>extruder</code> instead of mixedcase <code>Extruder</code> or uppercase <code>EXTRUDER</code>. Using any uppercase letter will raise an error.</p>
<p>20241203: The resonance test has been changed to include slow sweeping moves. This change requires that testing point(s) have some clearance in X/Y plane (+/- 30 mm from the test point should suffice when using the default settings). The new test should generally produce more accurate and reliable test results. However, if required, the previous test behavior can be restored by adding options <code>sweeping_period: 0</code> and <code>accel_per_hz: 75</code> to the <code>[resonance_tester]</code> config section.</p>
<p>20241201: In some cases Klipper may have ignored leading characters or spaces in a traditional G-Code command. For example, "99M123" may have been interpreted as "M123" and "M 321" may have been interpreted as "M321". Klipper will now report these cases with an "Unknown command" warning.</p>
<p>20241112: Option <code>CHIPS=&lt;chip_name&gt;</code> in <code>TEST_RESONANCES</code> and <code>SHAPER_CALIBRATE</code> requires specifying the full name(s) of the accel chip(s). For example, <code>adxl345 rpi</code> instead of short name - <code>rpi</code>.</p>

197
zh/Config_Reference.html
View File

@@ -931,6 +931,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#icm20948" class="md-nav__link">
[icm20948]
</a>
</li>
<li class="md-nav__item">
@@ -1741,6 +1748,13 @@
[adc_scaled]
</a>
</li>
<li class="md-nav__item">
<a href="#ads1x1x" class="md-nav__link">
[ads1x1x]
</a>
</li>
<li class="md-nav__item">
@@ -2600,8 +2614,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -3053,6 +3067,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#icm20948" class="md-nav__link">
[icm20948]
</a>
</li>
<li class="md-nav__item">
@@ -3863,6 +3884,13 @@
[adc_scaled]
</a>
</li>
<li class="md-nav__item">
<a href="#ads1x1x" class="md-nav__link">
[ads1x1x]
</a>
</li>
<li class="md-nav__item">
@@ -5212,6 +5240,22 @@ cs_pin:
# 共振测量的质量。
</code></pre></div>
<h3 id="icm20948">[icm20948]<a class="headerlink" href="#icm20948" title="Permanent link">&para;</a></h3>
<p>Support for icm20948 accelerometers.</p>
<div class="highlight"><pre><span></span><code>[icm20948]
#i2c_address:
# Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
#i2c_mcu:
#i2c_bus:
#i2c_software_scl_pin:
#i2c_software_sda_pin:
#i2c_speed: 400000
# See the &quot;common I2C settings&quot; section for a description of the
# above parameters. The default &quot;i2c_speed&quot; is 400000.
#axes_map: x, y, z
# See the &quot;adxl345&quot; section for information on this parameter.
</code></pre></div>
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">&para;</a></h3>
<p>Support for LIS2DW accelerometers.</p>
<div class="highlight"><pre><span></span><code>[lis2dw]
@@ -5529,6 +5573,9 @@ z_offset:
sensor_type: ldc1612
# The sensor chip used to perform eddy current measurements. This
# parameter must be provided and must be set to ldc1612.
#frequency:
# The external crystal frequency (in Hz) of the LDC1612 chip.
# The default is 12000000.
#intb_pin:
# MCU gpio pin connected to the ldc1612 sensor&#39;s INTB pin (if
# available). The default is to not use the INTB pin.
@@ -6436,20 +6483,27 @@ pin:
<p>在一个按钮被按下或放开（或当一个引脚状态发生变化时）时运行G代码。你可以使用 <code>QUERY_BUTTON button=my_gcode_button</code> 来查询按钮的状态。</p>
<div class="highlight"><pre><span></span><code>[gcode_button my_gcode_button]
pin:
# 连接到按钮的引脚。
# 必须提供此参数。
# The pin on which the button is connected. This parameter must be
# provided.
#analog_range:
# 两个逗号分隔的阻值(单位：欧姆)，指定了按钮的最小和最大电阻。
# 如果提供了 analog_range ，必须使用一个模拟功能的引脚。默认
# 情况下为按钮使用数字GPIO。
# analog_pullup_resistor:
# 当定义 analog_range 时的上拉电阻(欧姆)。默认为4700欧姆。
# Two comma separated resistances (in Ohms) specifying the minimum
# and maximum resistance range for the button. If analog_range is
# provided then the pin must be an analog capable pin. The default
# is to use digital gpio for the button.
#analog_pullup_resistor:
# The pullup resistance (in Ohms) when analog_range is specified.
# The default is 4700 ohms.
#press_gcode:
# 当按钮被按下时要执行的 G-Code 命令序列，支持G-Code模板。
# 必须提供此参数。
# A list of G-Code commands to execute when the button is pressed.
# G-Code templates are supported. This parameter must be provided.
#release_gcode:
# 当按钮被释放时要执行的G-Code命令序列，支持G-Code模板。
# 默认在按钮释放时不运行任何命令。
# A list of G-Code commands to execute when the button is released.
# G-Code templates are supported. The default is to not run any
# commands on a button release.
#debounce_delay:
# A period of time in seconds to debounce events prior to running the
# button gcode. If the button is pressed and released during this
# delay, the entire button press is ignored. Default is 0.
</code></pre></div>
<h3 id="output_pin">[output_pin]<a class="headerlink" href="#output_pin" title="Permanent link">&para;</a></h3>
@@ -6582,8 +6636,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#coolstep_threshold:
# The velocity (in mm/s) to set the TMC driver internal &quot;CoolStep&quot;
# threshold to. If set, the coolstep feature will be enabled when
@@ -6632,6 +6687,7 @@ run_current:
#driver_PWM_FREQ: 1
#driver_PWM_GRAD: 4
#driver_PWM_AMPL: 128
#driver_FREEWHEEL: 0
#driver_SGT: 0
#driver_SEMIN: 0
#driver_SEUP: 0
@@ -6689,8 +6745,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#driver_MULTISTEP_FILT: True
#driver_IHOLDDELAY: 8
#driver_TPOWERDOWN: 20
@@ -6705,6 +6762,7 @@ run_current:
#driver_PWM_FREQ: 1
#driver_PWM_GRAD: 14
#driver_PWM_OFS: 36
#driver_FREEWHEEL: 0
# Set the given register during the configuration of the TMC2208
# chip. This may be used to set custom motor parameters. The
# defaults for each parameter are next to the parameter name in the
@@ -6748,6 +6806,7 @@ run_current:
#driver_PWM_FREQ: 1
#driver_PWM_GRAD: 14
#driver_PWM_OFS: 36
#driver_FREEWHEEL: 0
#driver_SGTHRS: 0
#driver_SEMIN: 0
#driver_SEUP: 0
@@ -6864,8 +6923,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#coolstep_threshold:
# The velocity (in mm/s) to set the TMC driver internal &quot;CoolStep&quot;
# threshold to. If set, the coolstep feature will be enabled when
@@ -6992,8 +7052,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#coolstep_threshold:
# The velocity (in mm/s) to set the TMC driver internal &quot;CoolStep&quot;
# threshold to. If set, the coolstep feature will be enabled when
@@ -7575,35 +7636,39 @@ text:
<h3 id="filament_switch_sensor">[filament_switch_sensor]<a class="headerlink" href="#filament_switch_sensor" title="Permanent link">&para;</a></h3>
<p>耗材开关传感器。支持使用开关传感器（如限位开关）进行耗材插入和耗尽检测。</p>
<p>更多信息请参阅<a href="G-Codes.html#filament_switch_sensor">命令参考</a>。</p>
<div class="highlight"><pre><span></span><code>[filament_switch_sensor my_sensor]。
<div class="highlight"><pre><span></span><code>[filament_switch_sensor my_sensor]
#pause_on_runout: True
# 当设置为 &quot;True &quot;时，会在检测到耗尽后立即暂停打印机。
# 请注意, 如果 pause_on_runout 为 False 并且没有定义。
# runout_gcode的话, 耗尽检测将被禁用。
# 默认为 True。
# When set to True, a PAUSE will execute immediately after a runout
# is detected. Note that if pause_on_runout is False and the
# runout_gcode is omitted then runout detection is disabled. Default
# is True.
#runout_gcode:
# 在检测到耗材耗尽后会执行的G代码命令列表。
# 有关G-Code 格式请见 docs/Command_Templates.md。
# 如果 pause_on_runout 被设置为 True，这个G-Code将在
# 暂停后执行。
# 默认情况是不运行任何 G-Code 命令。
# A list of G-Code commands to execute after a filament runout is
# detected. See docs/Command_Templates.md for G-Code format. If
# pause_on_runout is set to True this G-Code will run after the
# PAUSE is complete. The default is not to run any G-Code commands.
#insert_gcode:
# 在检测到耗材插入后会执行的 G-Code 命令列表。
# 关于G代码格式，请参见 docs/Command_Templates.md。
# 默认不运行任何 G-Code 命令，这将禁用耗材插入检测。
# A list of G-Code commands to execute after a filament insert is
# detected. See docs/Command_Templates.md for G-Code format. The
# default is not to run any G-Code commands, which disables insert
# detection.
#event_delay: 3.0
# 事件之间的最小延迟时间（秒）。
# 在这个时间段内触发的事件将被默许忽略。
# 默认为3秒。
# The minimum amount of time in seconds to delay between events.
# Events triggered during this time period will be silently
# ignored. The default is 3 seconds.
#pause_delay: 0.5
# 暂停命令和执行 runout_gcode 之间的延迟时间, 单位是秒。
# 如果在OctoPrint的情况下，增加这个延迟可能改善暂
# 停的可靠性。如果OctoPrint表现出奇怪的暂停行为，
# 考虑增加这个延迟。
# 默认为0.5秒。
# The amount of time to delay, in seconds, between the pause command
# dispatch and execution of the runout_gcode. It may be useful to
# increase this delay if OctoPrint exhibits strange pause behavior.
# Default is 0.5 seconds.
#debounce_delay:
# A period of time in seconds to debounce events prior to running the
# switch gcode. The switch must he held in a single state for at least
# this long to activate. If the switch is toggled on/off during this delay,
# the event is ignored. Default is 0.
#switch_pin:
# 连接到检测开关的引脚。
# 必须提供此参数。
# The pin on which the switch is connected. This parameter must be
# provided.
</code></pre></div>
<h3 id="filament_motion_sensor">[filament_motion_sensor]<a class="headerlink" href="#filament_motion_sensor" title="Permanent link">&para;</a></h3>
@@ -7693,6 +7758,16 @@ adc2:
<div class="highlight"><pre><span></span><code>[load_cell]
sensor_type:
# This must be one of the supported sensor types, see below.
#counts_per_gram:
# The floating point number of sensor counts that indicates 1 gram of force.
# This value is calculated by the LOAD_CELL_CALIBRATE command.
#reference_tare_counts:
# The integer tare value, in raw sensor counts, taken when LOAD_CELL_CALIBRATE
# is run. This is the default tare value when klipper starts up.
#sensor_orientation:
# Change the sensor&#39;s orientation. Can be either &#39;normal&#39; or &#39;inverted&#39;.
# The default is &#39;normal&#39;. Use &#39;inverted&#39; if the sensor reports a
# decreasing force value when placed under load.
</code></pre></div>
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">&para;</a></h4>
@@ -7836,6 +7911,38 @@ vssa_pin:
# VSSA 测量来减少测量的干扰。默认为2秒。
</code></pre></div>
<h3 id="ads1x1x">[ads1x1x]<a class="headerlink" href="#ads1x1x" title="Permanent link">&para;</a></h3>
<p>ADS1013, ADS1014, ADS1015, ADS1113, ADS1114 and ADS1115 are I2C based Analog to Digital Converters that can be used for temperature sensors. They provide 4 analog input pins either as single line or as differential input.</p>
<p>Note: Use caution if using this sensor to control heaters. The heater min_temp and max_temp are only verified in the host and only if the host is running and operating normally. (ADC inputs directly connected to the micro-controller verify min_temp and max_temp within the micro-controller and do not require a working connection to the host.)</p>
<div class="highlight"><pre><span></span><code>[ads1x1x my_ads1x1x]
chip: ADS1115
#pga: 4.096V
# Default value is 4.096V. The maximum voltage range used for the input. This
# scales all values read from the ADC. Options are: 6.144V, 4.096V, 2.048V,
# 1.024V, 0.512V, 0.256V
#adc_voltage: 3.3
# The suppy voltage for the device. This allows additional software scaling
# for all values read from the ADC.
i2c_mcu: host
i2c_bus: i2c.1
#address_pin: GND
# Default value is GND. There can be up to four addressed devices depending
# upon wiring of the device. Check the datasheet for details. The i2c_address
# can be specified directly instead of using the address_pin.
</code></pre></div>
<p>The chip provides pins that can be used on other sensors.</p>
<div class="highlight"><pre><span></span><code>sensor_type: ...
# Can be any thermistor or adc_temperature.
sensor_pin: my_ads1x1x:AIN0
# A combination of the name of the ads1x1x chip and the pin. Possible
# pin values are AIN0, AIN1, AIN2 and AIN3 for single ended lines and
# DIFF01, DIFF03, DIFF13 and DIFF23 for differential between their
# correspoding lines. For example
# DIFF03 measures the differential between line 0 and 3. Only specific
# combinations for the differentials are allowed.
</code></pre></div>
<h3 id="replicape">[replicape]<a class="headerlink" href="#replicape" title="Permanent link">&para;</a></h3>
<p>Replicape支持 - 参考<a href="Beaglebone.html">beaglebone guide</a>和<a href="./config/generic-replicape.cfg">generic-replicape.cfg</a></p>
<div class="highlight"><pre><span></span><code># &quot;replicape&quot;配置分段添加了&quot;replicape:stepper_x_enable&quot;虚拟步进使能
@@ -7898,7 +8005,7 @@ host_mcu:
<p>Palette 2 多材料支持 - 提供更紧密的集成，支持处于连接模式的 Palette 2 设备。</p>
<p>该模块的全部功能需要<code>[virtual_sdcard]</code>和<code>[pause_resume]</code>。</p>
<p>不要和 Octoprint 的 Palette 2插件一起使用这个模块，因为它们会发生冲突，造成初始化和打印失败。</p>
<p>如果使用 OctoPrint 并通过串行端口流式传输 G-Code，而不通过 virtual_sd 打印，将 * 设置&gt;串行连接&gt;固件和协议 * 中的“暂停命令” 设置为<strong>M1</strong> 和 <strong>M0</strong> 可以避免在开始打印时需要在Palette 2 上选择开始打印并在 OctoPrint 中取消暂停。</p>
<p>If you use Octoprint and stream gcode over the serial port instead of printing from virtual_sd, then remove <strong>M1</strong> and <strong>M0</strong> from <em>Pausing commands</em> in <em>Settings &gt; Serial Connection &gt; Firmware &amp; protocol</em> will prevent the need to start print on the Palette 2 and unpausing in Octoprint for your print to begin.</p>
<div class="highlight"><pre><span></span><code>[palette2]
serial:
# 与 Palette 2 连接的串口。

4
zh/Config_checks.html
View File

@@ -1385,8 +1385,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

19
zh/Contact.html
View File

@@ -451,8 +451,8 @@
</li>
<li class="md-nav__item">
<a href="#klipper-github" class="md-nav__link">
Klipper GitHub
<a href="#professional-services" class="md-nav__link">
Professional Services
</a>
</li>
@@ -1376,8 +1376,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1481,8 +1481,8 @@
</li>
<li class="md-nav__item">
<a href="#klipper-github" class="md-nav__link">
Klipper GitHub
<a href="#professional-services" class="md-nav__link">
Professional Services
</a>
</li>
@@ -1558,9 +1558,10 @@
<h2 id="klipper_2">我正在进行一些我想添加到 Klipper 中的改进<a class="headerlink" href="#klipper_2" title="Permanent link">&para;</a></h2>
<p>Klipper 是开源软件，我们非常感谢新的贡献。</p>
<p>新的贡献（包括代码和文档）需要通过拉取请求(PR)提交。重要信息请参见<a href="CONTRIBUTING.html">贡献文档</a>。</p>
<p>有几个<a href="Overview.html#developer-documentation">开发者文档</a>。如果你对代码有疑问，那么你也可以在<a href="#community-forum">Klipper社区论坛</a>或<a href="#discord-chat">Klipper社区Discord</a>上提问。</p>
<h2 id="klipper-github">Klipper GitHub<a class="headerlink" href="#klipper-github" title="Permanent link">&para;</a></h2>
<p>Klipper GitHub可以被贡献者用来分享他们改进Klipper的工作状态。我们希望创建GitHub Ticket的人正在积极地处理给定的任务，并将执行所有必要工作以完成该任务。Klipper GitHub不用于功能请求，也不用于报告bug，更不用于提问。请使用<a href="#community-forum">Klipper社区论坛</a>或<a href="#discord-chat">Klipper社区Discord</a>来代替。</p>
<p>There are several <a href="Overview.html#developer-documentation">documents for developers</a>. If you have questions on the code then you can also ask in the <a href="#discourse-forum">Klipper Discourse Forum</a> or on the <a href="#discord-chat">Klipper Discord Chat</a>.</p>
<h2 id="professional-services">Professional Services<a class="headerlink" href="#professional-services" title="Permanent link">&para;</a></h2>
<p><img alt="" src="img/klipper-logo-small.png" /></p>
<p>Custom software development, software support, and solutions: <a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a></p>
</article>

4
zh/Debugging.html
View File

@@ -1384,8 +1384,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Delta_Calibrate.html
View File

@@ -1365,8 +1365,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

8
zh/Eddy_Probe.html
View File

@@ -1329,8 +1329,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1487,13 +1487,13 @@
<a href="Sponsors.html" class="md-footer__link md-footer__link--next" aria-label="下一页: 赞助" rel="next">
<a href="Load_Cell.html" class="md-footer__link md-footer__link--next" aria-label="下一页: Load Cells" rel="next">
<div class="md-footer__title">
<div class="md-ellipsis">
<span class="md-footer__direction">
下一页
</span>
赞助
Load Cells
</div>
</div>
<div class="md-footer__button md-icon">

4
zh/Endstop_Phase.html
View File

@@ -1344,8 +1344,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Example_Configs.html
View File

@@ -1329,8 +1329,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Exclude_Object.html
View File

@@ -1356,8 +1356,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/FAQ.html
View File

@@ -1488,8 +1488,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

28
zh/Features.html
View File

@@ -1334,8 +1334,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1443,18 +1443,18 @@
<li>标准 G 代码支持。支持由常见“切片软件”（SuperSlicer、Cura、PrusaSlicer 等）生成的通用 G 代码命令。</li>
<li>支持多挤出机。包括对共享热端的挤出机（多进一出）和多头（IDEX）的支持。</li>
<li>支持笛卡尔、三角洲、CoreXY、CoreXZ、混合CoreXY、混合CoreXZ、deltesian、旋转三角洲、极坐标和缆绳铰盘式打印机。</li>
<li>自动床面平整支持。Klipper可以被配置为基本的床身倾斜检测或网床调平。如果床铺使用多个Z步进器，那么Klipper也可以通过独立操纵Z步进器来调平。支持大多数Z高度探头，包括BL-Touch探头和伺服激活的探头。</li>
<li>Automatic bed leveling support. Klipper can be configured for basic bed tilt detection or full mesh bed leveling. The bed mesh can be customized to the print size (adaptive bed mesh). If the bed uses multiple Z steppers then Klipper can also level by independently manipulating the Z steppers. Most Z height probes are supported, including BL-Touch probes and servo activated probes. Probes may be calibrated for axis twist compensation. If using an "eddy current probe" then one can utilize fast bed mesh scanning,</li>
<li>支持自动delta校准。校准工具可以进行基本的高度校准，以及增强的X和Y尺寸校准。校准可以用Z型高度探头或通过手动探测来完成。</li>
<li>支持打印时“排除对象”。配置后，此模块可以取消多零件打印中的一个对象。</li>
<li>支持常见的温度传感器（例如，常见的热敏电阻、AD595、AD597、AD849x、PT100、PT1000、MAX6675、MAX31855、MAX31856、MAX31865、BME280、HTU21D、DS18B20和LM75）。还可以配置自定义热敏电阻和自定义模拟温度传感器。还可以监测微控制器和 Raspberry Pi 内部的温度传感器。</li>
<li>Support for common temperature sensors (eg, common thermistors, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20, AHT10, SHT3x, and LM75). Custom thermistors and custom analog temperature sensors can also be configured. One can monitor the internal micro-controller temperature sensor and the internal temperature sensor of a Raspberry Pi.</li>
<li>默认启用基本加热器保护。</li>
<li>支持标准风扇、喷嘴风扇和温控风扇。不需要在打印机闲置时保持风扇运转。可以在带有转速表的风扇上监测风扇速度。</li>
<li>Support for standard fans, nozzle fans, and temperature controlled fans. No need to keep fans running when the printer is idle. Fan speed can be monitored on fans that have a tachometer. One can assign a "math formula" to a fan for automatic fan speed updating.</li>
<li>支持TMC2130、TMC2208/TMC2224、TMC2209、TMC2660和TMC5160步进电机驱动器的运行时配置。还支持通过AD5206、DAC084S085、MCP4451、MCP4728、MCP4018和PWM引脚对传统步进驱动器进行电流控制。</li>
<li>支持直接连接到打印机的普通LCD显示器。还提供了一个默认的菜单。显示器和菜单的内容可以通过配置文件完全定制。</li>
<li>恒定加速和“look-ahead”（前瞻）支持。所有打印机移动将从静止逐渐加速到巡航速度，然后减速回到静止。对传入的 G 代码移动命令流进行排队和分析 - 将优化类似方向上的移动之间的加速度，以减少打印停顿并改善整体打印时间。</li>
<li>Klipper 实现了一种“步进相位限位”算法，可以提高典型限位开关的精度。如果调整得当，它可以提高打印件首层和打印床的附着力。</li>
<li>支持打印丝存在传感器、打印丝运动传感器和打印丝宽度传感器。</li>
<li>支持使用 adxl345、mpu9250 和 mpu 6050 加速度计测量和记录加速度。</li>
<li>Support for measuring and recording acceleration using adxl345, mpu9250, mpu6050, lis2dw12, lis3dh, and icm20948 accelerometers.</li>
<li>支持限制短距离“之”字形移动的最高速度，以减少打印机的振动和噪音。更多信息见<a href="Kinematics.html">运动学</a>文档。</li>
<li>许多常见的打印机都有样本配置文件。查看<a href="https://github.com/Klipper3d/klipper/blob/master/config/">配置文件夹</a>中的列表。</li>
</ul>
@@ -1526,11 +1526,6 @@
<td>1622K</td>
</tr>
<tr>
<td>RP2040</td>
<td>2400K</td>
<td>1636K</td>
</tr>
<tr>
<td>SAM4E8E</td>
<td>2500K</td>
<td>1674K</td>
@@ -1556,6 +1551,11 @@
<td>2634K</td>
</tr>
<tr>
<td>RP2040</td>
<td>4000K</td>
<td>2571K</td>
</tr>
<tr>
<td>RP2350</td>
<td>4167K</td>
<td>2663K</td>
@@ -1566,9 +1566,9 @@
<td>4737K</td>
</tr>
<tr>
<td>STM32H743</td>
<td>9091K</td>
<td>6061K</td>
<td>STM32H723</td>
<td>7429K</td>
<td>8619K</td>
</tr>
</tbody>
</table>

524
zh/G-Codes.html
View File

@@ -1620,6 +1620,68 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
[load_cell]
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_diagnostic" class="md-nav__link">
LOAD_CELL_DIAGNOSTIC
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_calibrate" class="md-nav__link">
LOAD_CELL_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_tare" class="md-nav__link">
LOAD_CELL_TARE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_read-load_cellname" class="md-nav__link">
LOAD_CELL_READ load_cell="name"
</a>
</li>
<li class="md-nav__item">
@@ -1694,33 +1756,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -1789,26 +1824,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -1850,6 +1865,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -2281,6 +2316,54 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#_2" class="md-nav__link">
关于
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
<li class="md-nav__item">
@@ -2429,54 +2512,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#_2" class="md-nav__link">
关于
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
</ul>
@@ -3006,8 +3041,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -3881,6 +3916,68 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
[load_cell]
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_diagnostic" class="md-nav__link">
LOAD_CELL_DIAGNOSTIC
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_calibrate" class="md-nav__link">
LOAD_CELL_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_tare" class="md-nav__link">
LOAD_CELL_TARE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_read-load_cellname" class="md-nav__link">
LOAD_CELL_READ load_cell="name"
</a>
</li>
<li class="md-nav__item">
@@ -3955,33 +4052,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4050,26 +4120,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4111,6 +4161,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4542,6 +4612,54 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#_2" class="md-nav__link">
关于
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
<li class="md-nav__item">
@@ -4690,54 +4808,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#_2" class="md-nav__link">
关于
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
</ul>
@@ -4831,11 +4901,10 @@
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
section</a> is enabled.</p>
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">&para;</a></h4>
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=&lt;X|Y&gt;] [AUTO=&lt;True|False&gt;] [SAMPLE_COUNT=&lt;value&gt;]</code></p>
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=&lt;X|Y&gt;] [SAMPLE_COUNT=&lt;value&gt;]</code></p>
<p>Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.</p>
<ul>
<li><strong>AXIS:</strong> Define the axis (<code>X</code> or <code>Y</code>) for which the twist compensation will be calibrated. If not specified, the axis defaults to <code>'X'</code>.</li>
<li><strong>AUTO:</strong> Enables automatic calibration mode. When <code>AUTO=True</code>, the calibration will run for both the X and Y axes. In this mode, <code>AXIS</code> cannot be specified. If both <code>AXIS</code> and <code>AUTO</code> are provided, an error will be raised.</li>
</ul>
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">&para;</a></h3>
<p>启用[床网格配置部分]（config_Reference.md#bed_mesh）时，以下命令可用（另请参阅[床网格指南]（bed_mesh.md））。</p>
@@ -4965,7 +5034,10 @@ section</a> is enabled.</p>
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">&para;</a></h4>
<p><code>FORCE_MOVE STEPPER=&lt;config_name&gt; DISTANCE=&lt;value&gt; VELOCITY=&lt;value&gt; [ACCEL=&lt;value&gt;]</code> 。该命令将以给定的恒定速度（mm/s）强制移动给定的步进器，移动距离（mm）。如果指定了ACCEL并且大于零，那么将使用给定的加速度（单位：mm/s^2）；否则不进行加速。不执行边界检查；不进行运动学更新；一个轴上的其他平行步进器将不会被移动。请谨慎使用，因为不正确的命令可能会导致损坏使用该命令几乎肯定会使低级运动学处于不正确的状态；随后发出G28命令以重置运动学。该命令用于低级别的诊断和调试。</p>
<h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">&para;</a></h4>
<p><code>SET_KINEMATIC_POSITION [X=&lt;value&gt;] [Y=&lt;value&gt;] [Z=&lt;value&gt;] [CLEAR=&lt;[X][Y][Z]&gt;]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an axis is not specified then it will default to the position that the head was last commanded to. Setting an incorrect or invalid position may lead to internal software errors. Use the CLEAR parameter to forget the homing state for the given axes. Note that CLEAR will not override the previous functionality; if an axis is not specified to CLEAR it will have its kinematic position set as per above. This command may invalidate future boundary checks; issue a G28 afterwards to reset the kinematics.</p>
<p><code>SET_KINEMATIC_POSITION [X=&lt;value&gt;] [Y=&lt;value&gt;] [Z=&lt;value&gt;] [SET_HOMED=&lt;[X][Y][Z]&gt;] [CLEAR_HOMED=&lt;[X][Y][Z]&gt;]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position and set/clear homed status. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. Setting an incorrect or invalid position may lead to internal software errors.</p>
<p>The <code>X</code>, <code>Y</code>, and <code>Z</code> parameters are used to alter the low-level kinematic position tracking. If any of these parameters are not set then the position is not changed - for example <code>SET_KINEMATIC_POSITION Z=10</code> would set all axes as homed, set the internal Z position to 10, and leave the X and Y positions unchanged. Changing the internal position tracking is not dependent on the internal homing state - one may alter the position for both homed and not homed axes, and similarly one may set or clear the homing state of an axis without altering its internal position.</p>
<p>The <code>SET_HOMED</code> parameter defaults to <code>XYZ</code> which instructs the kinematics to consider all axes as homed. A bare <code>SET_KINEMATIC_POSITION</code> command will result in all axes being considered homed (and not change its current position). If it is not desired to change the state of homed axes then assign <code>SET_HOMED</code> to an empty string - for example: <code>SET_KINEMATIC_POSITION SET_HOMED= X=10</code>. It is also possible to request an individual axis be considered homed (eg, <code>SET_HOMED=X</code>), but note that non-cartesian style kinematics (such as delta kinematics) may not support setting an individual axis as homed.</p>
<p>The <code>CLEAR_HOMED</code> parameter instructs the kinematics to consider the given axes as not homed. For example, <code>CLEAR_HOMED=XYZ</code> would request all axes to be considered not homed (and thus require homing prior to movement on those axes). The default is <code>SET_HOMED=XYZ</code> even if <code>CLEAR_HOMED</code> is present, so the command <code>SET_KINEMATIC_POSITION CLEAR_HOMED=Z</code> will set X and Y as homed and clear the homing state for Z. Use <code>SET_KINEMATIC_POSITION SET_HOMED= CLEAR_HOMED=Z</code> if the goal is to clear only the Z homing state. If an axis is specified in neither <code>SET_HOMED</code> nor <code>CLEAR_HOMED</code> then its homing state is not changed and if it is specified in both then <code>CLEAR_HOMED</code> has precedence. It is possible to request clearing of an individual axis, but on non-cartesian style kinematics (such as delta kinematics) doing so may result in clearing the homing state of additional axes. Note the <code>CLEAR</code> parameter is currently an alias for the <code>CLEAR_HOMED</code> parameter, but this alias will be removed in the future.</p>
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">&para;</a></h3>
<p>The gcode module is automatically loaded.</p>
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">&para;</a></h4>
@@ -5028,6 +5100,28 @@ section</a> is enabled.</p>
<p>The following command is enabled if an <a href="Config_Reference.html#input_shaper">input_shaper config section</a> has been enabled (also see the <a href="Resonance_Compensation.html">resonance compensation guide</a>).</p>
<h4 id="set_input_shaper">SET_INPUT_SHAPER<a class="headerlink" href="#set_input_shaper" title="Permanent link">&para;</a></h4>
<p><code>SET_INPUT_SHAPER [SHAPER_FREQ_X=&lt;shaper_freq_x&gt;] [SHAPER_FREQ_Y=&lt;shaper_freq_y&gt;] [DAMPING_RATIO_X=&lt;damping_ratio_x&gt;] [DAMPING_RATIO_Y=&lt;damping_ratio_y&gt;] [SHAPER_TYPE=&lt;shaper&gt;] [SHAPER_TYPE_X=&lt;shaper_type_x&gt;] [SHAPER_TYPE_Y=&lt;shaper_type_y&gt;]</code>：修改输入整形参数。注意 SHAPER_TYPE 参数会同时覆写 X 和 Y 轴的整形器类型，即使它们在 [input_shaper] 配置分段中有不同的整形器类型。SHAPER_TYPE 不能和 SHAPER_TYPE_X 和 SHAPER_TYPE_Y 参数同时使用。这些参数的细节请见<a href="Config_Reference.html#input_shaper">配置参考</a>。</p>
<h3 id="led">[led]<a class="headerlink" href="#led" title="Permanent link">&para;</a></h3>
<p>The following command is available when any of the <a href="Config_Reference.html#leds">led config sections</a> are enabled.</p>
<h4 id="set_led">SET_LED<a class="headerlink" href="#set_led" title="Permanent link">&para;</a></h4>
<p><code>SET_LED LED=&lt;config_name&gt; RED=&lt;value&gt; GREEN=&lt;value&gt; BLUE=&lt;value&gt; WHITE=&lt;value&gt; [INDEX=&lt;index&gt;] [TRANSMIT=0] [SYNC=1]</code>: This sets the LED output. Each color <code>&lt;value&gt;</code> must be between 0.0 and 1.0. The WHITE option is only valid on RGBW LEDs. If the LED supports multiple chips in a daisy-chain then one may specify INDEX to alter the color of just the given chip (1 for the first chip, 2 for the second, etc.). If INDEX is not provided then all LEDs in the daisy-chain will be set to the provided color. If TRANSMIT=0 is specified then the color change will only be made on the next SET_LED command that does not specify TRANSMIT=0; this may be useful in combination with the INDEX parameter to batch multiple updates in a daisy-chain. By default, the SET_LED command will sync it's changes with other ongoing gcode commands. This can lead to undesirable behavior if LEDs are being set while the printer is not printing as it will reset the idle timeout. If careful timing is not needed, the optional SYNC=0 parameter can be specified to apply the changes without resetting the idle timeout.</p>
<h4 id="set_led_template">SET_LED_TEMPLATE<a class="headerlink" href="#set_led_template" title="Permanent link">&para;</a></h4>
<p><code>SET_LED_TEMPLATE LED=&lt;led_name&gt; TEMPLATE=&lt;template_name&gt; [&lt;param_x&gt;=&lt;literal&gt;] [INDEX=&lt;index&gt;]</code>: Assign a <a href="Config_Reference.html#display_template">display_template</a> to a given <a href="Config_Reference.html#leds">LED</a>. For example, if one defined a <code>[display_template my_led_template]</code> config section then one could assign <code>TEMPLATE=my_led_template</code> here. The display_template should produce a comma separated string containing four floating point numbers corresponding to red, green, blue, and white color settings. The template will be continuously evaluated and the LED will be automatically set to the resulting colors. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If INDEX is not specified then all chips in the LED's daisy-chain will be set to the template, otherwise only the chip with the given index will be updated. If TEMPLATE is an empty string then this command will clear any previous template assigned to the LED (one can then use <code>SET_LED</code> commands to manage the LED's color settings).</p>
<h3 id="load_cell">[load_cell]<a class="headerlink" href="#load_cell" title="Permanent link">&para;</a></h3>
<p>The following commands are enabled if a <a href="Config_Reference.html#load_cell">load_cell config section</a> has been enabled.</p>
<h3 id="load_cell_diagnostic">LOAD_CELL_DIAGNOSTIC<a class="headerlink" href="#load_cell_diagnostic" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_DIAGNOSTIC [LOAD_CELL=&lt;config_name&gt;]</code>: This command collects 10 seconds of load cell data and reports statistics that can help you verify proper operation of the load cell. This command can be run on both calibrated and uncalibrated load cells.</p>
<h3 id="load_cell_calibrate">LOAD_CELL_CALIBRATE<a class="headerlink" href="#load_cell_calibrate" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_CALIBRATE [LOAD_CELL=&lt;config_name&gt;]</code>: Start the guided calibration utility. Calibration is a 3 step process:</p>
<ol>
<li>First you remove all load from the load cell and run the <code>TARE</code> command</li>
<li>Next you apply a known load to the load cell and run the <code>CALIBRATE GRAMS=nnn</code> command</li>
<li>Finally use the <code>ACCEPT</code> command to save the results</li>
</ol>
<p>You can cancel the calibration process at any time with <code>ABORT</code>.</p>
<h3 id="load_cell_tare">LOAD_CELL_TARE<a class="headerlink" href="#load_cell_tare" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_TARE [LOAD_CELL=&lt;config_name&gt;]</code>: This works just like the tare button on digital scale. It sets the current raw reading of the load cell to be the zero point reference value. The response is the percentage of the sensors range that was read and the raw value in counts.</p>
<h3 id="load_cell_read-load_cellname">LOAD_CELL_READ load_cell="name"<a class="headerlink" href="#load_cell_read-load_cellname" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_READ [LOAD_CELL=&lt;config_name&gt;]</code>: This command takes a reading from the load cell. The response is the percentage of the sensors range that was read and the raw value in counts. If the load cell is calibrated a force in grams is also reported.</p>
<h3 id="manual_probe">[manual_probe]<a class="headerlink" href="#manual_probe" title="Permanent link">&para;</a></h3>
<p>The manual_probe module is automatically loaded.</p>
<h4 id="manual_probe_1">MANUAL_PROBE<a class="headerlink" href="#manual_probe_1" title="Permanent link">&para;</a></h4>
@@ -5049,12 +5143,6 @@ section</a> is enabled.</p>
<p>The following command is available when a <a href="Config_Reference.html#mcp4018">mcp4018 config section</a> is enabled.</p>
<h4 id="set_digipot">SET_DIGIPOT<a class="headerlink" href="#set_digipot" title="Permanent link">&para;</a></h4>
<p><code>SET_DIGIPOT DIGIPOT=config_name WIPER=&lt;value&gt;</code>: This command will change the current value of the digipot. This value should typically be between 0.0 and 1.0, unless a 'scale' is defined in the config. When 'scale' is defined, then this value should be between 0.0 and 'scale'.</p>
<h3 id="led">[led]<a class="headerlink" href="#led" title="Permanent link">&para;</a></h3>
<p>The following command is available when any of the <a href="Config_Reference.html#leds">led config sections</a> are enabled.</p>
<h4 id="set_led">SET_LED<a class="headerlink" href="#set_led" title="Permanent link">&para;</a></h4>
<p><code>SET_LED LED=&lt;config_name&gt; RED=&lt;value&gt; GREEN=&lt;value&gt; BLUE=&lt;value&gt; WHITE=&lt;value&gt; [INDEX=&lt;index&gt;] [TRANSMIT=0] [SYNC=1]</code>: This sets the LED output. Each color <code>&lt;value&gt;</code> must be between 0.0 and 1.0. The WHITE option is only valid on RGBW LEDs. If the LED supports multiple chips in a daisy-chain then one may specify INDEX to alter the color of just the given chip (1 for the first chip, 2 for the second, etc.). If INDEX is not provided then all LEDs in the daisy-chain will be set to the provided color. If TRANSMIT=0 is specified then the color change will only be made on the next SET_LED command that does not specify TRANSMIT=0; this may be useful in combination with the INDEX parameter to batch multiple updates in a daisy-chain. By default, the SET_LED command will sync it's changes with other ongoing gcode commands. This can lead to undesirable behavior if LEDs are being set while the printer is not printing as it will reset the idle timeout. If careful timing is not needed, the optional SYNC=0 parameter can be specified to apply the changes without resetting the idle timeout.</p>
<h4 id="set_led_template">SET_LED_TEMPLATE<a class="headerlink" href="#set_led_template" title="Permanent link">&para;</a></h4>
<p><code>SET_LED_TEMPLATE LED=&lt;led_name&gt; TEMPLATE=&lt;template_name&gt; [&lt;param_x&gt;=&lt;literal&gt;] [INDEX=&lt;index&gt;]</code>: Assign a <a href="Config_Reference.html#display_template">display_template</a> to a given <a href="Config_Reference.html#leds">LED</a>. For example, if one defined a <code>[display_template my_led_template]</code> config section then one could assign <code>TEMPLATE=my_led_template</code> here. The display_template should produce a comma separated string containing four floating point numbers corresponding to red, green, blue, and white color settings. The template will be continuously evaluated and the LED will be automatically set to the resulting colors. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If INDEX is not specified then all chips in the LED's daisy-chain will be set to the template, otherwise only the chip with the given index will be updated. If TEMPLATE is an empty string then this command will clear any previous template assigned to the LED (one can then use <code>SET_LED</code> commands to manage the LED's color settings).</p>
<h3 id="output_pin">[output_pin]<a class="headerlink" href="#output_pin" title="Permanent link">&para;</a></h3>
<p>使用<a href="Config_Reference.html#output_pin">output_pin 配置分段</a>时，以下命令可用：</p>
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">&para;</a></h4>
@@ -5077,10 +5165,6 @@ section</a> is enabled.</p>
<p><code>PALETTE_CUT</code>:该命令指引Palette 2切割耗材并且装载分段的耗材。</p>
<h4 id="palette_smart_load">PALETTE_SMART_LOAD<a class="headerlink" href="#palette_smart_load" title="Permanent link">&para;</a></h4>
<p><code>PALETTE_SMART_LOAD</code>：该命令在Palette 2上启动智能加载序列。通过在设备上为打印机校准的距离挤压，自动加载耗材，并在加载完成后指示Palette 2。该命令与耗材加载完成后直接在Palette 2屏幕上按<strong>Smart Load</strong>相同。</p>
<h3 id="pid_calibrate">[pid_calibrate]<a class="headerlink" href="#pid_calibrate" title="Permanent link">&para;</a></h3>
<p>The pid_calibrate module is automatically loaded if a heater is defined in the config file.</p>
<h4 id="pid_calibrate_1">PID_CALIBRATE<a class="headerlink" href="#pid_calibrate_1" title="Permanent link">&para;</a></h4>
<p><code>PID_CALIBRATE HEATER=&lt;config_name&gt; TARGET=&lt;temperature&gt; [WRITE_FILE=1]</code>：执行一个PID校准测试。指定的加热器将被启用，直到达到指定的目标温度，然后加热器将被关闭和开启几个周期。如果WRITE_FILE参数被启用，那么将创建文件/tmp/heattest.txt，其中包含测试期间所有温度样本的日志。</p>
<h3 id="pause_resume">[pause_resume]<a class="headerlink" href="#pause_resume" title="Permanent link">&para;</a></h3>
<p>当<a href="Config_Reference.html#pause_resume">pause_resume 配置分段</a>被启用时，以下命令可用：</p>
<h4 id="pause">PAUSE<a class="headerlink" href="#pause" title="Permanent link">&para;</a></h4>
@@ -5091,6 +5175,10 @@ section</a> is enabled.</p>
<p><code>CLEAR_PAUSE</code>:清除当前的暂停状态而不恢复打印。如果一个人决定在暂停后取消打印，这很有用。建议将其添加到你的启动代码中，以确保每次打印时的暂停状态是新的。</p>
<h4 id="cancel_print">CANCEL_PRINT<a class="headerlink" href="#cancel_print" title="Permanent link">&para;</a></h4>
<p><code>CANCEL_PRINT</code>：取消当前的打印。</p>
<h3 id="pid_calibrate">[pid_calibrate]<a class="headerlink" href="#pid_calibrate" title="Permanent link">&para;</a></h3>
<p>The pid_calibrate module is automatically loaded if a heater is defined in the config file.</p>
<h4 id="pid_calibrate_1">PID_CALIBRATE<a class="headerlink" href="#pid_calibrate_1" title="Permanent link">&para;</a></h4>
<p><code>PID_CALIBRATE HEATER=&lt;config_name&gt; TARGET=&lt;temperature&gt; [WRITE_FILE=1]</code>：执行一个PID校准测试。指定的加热器将被启用，直到达到指定的目标温度，然后加热器将被关闭和开启几个周期。如果WRITE_FILE参数被启用，那么将创建文件/tmp/heattest.txt，其中包含测试期间所有温度样本的日志。</p>
<h3 id="print_stats">[print_stats]<a class="headerlink" href="#print_stats" title="Permanent link">&para;</a></h3>
<p>The print_stats module is automatically loaded.</p>
<h4 id="set_print_stats_info">SET_PRINT_STATS_INFO<a class="headerlink" href="#set_print_stats_info" title="Permanent link">&para;</a></h4>
@@ -5158,7 +5246,7 @@ section</a> is enabled.</p>
<h3 id="save_variables">[save_variables]<a class="headerlink" href="#save_variables" title="Permanent link">&para;</a></h3>
<p>The following command is enabled if a <a href="Config_Reference.html#save_variables">save_variables config section</a> has been enabled.</p>
<h4 id="save_variable">SAVE_VARIABLE<a class="headerlink" href="#save_variable" title="Permanent link">&para;</a></h4>
<p><code>SAVE_VARIABLE VARIABLE=&lt;name&gt; VALUE=&lt;value&gt;</code>：将变量保存到磁盘，以便在重新启动时使用。所有存储的变量都会在启动时加载到 <code>printer.save_variables.variables</code> 目录中，并可以在 gcode 宏中使用。所提供的 VALUE 会被解析为一个 Python 字面。</p>
<p><code>SAVE_VARIABLE VARIABLE=&lt;name&gt; VALUE=&lt;value&gt;</code>: Saves the variable to disk so that it can be used across restarts. The VARIABLE must be lowercase. All stored variables are loaded into the <code>printer.save_variables.variables</code> dict at startup and can be used in gcode macros. The provided VALUE is parsed as a Python literal.</p>
<h3 id="screws_tilt_adjust">[screws_tilt_adjust]<a class="headerlink" href="#screws_tilt_adjust" title="Permanent link">&para;</a></h3>
<p>The following commands are available when the <a href="Config_Reference.html#screws_tilt_adjust">screws_tilt_adjust config section</a> is enabled (also see the <a href="Manual_Level.html#adjusting-bed-leveling-screws-using-the-bed-probe">manual level guide</a>).</p>
<h4 id="screws_tilt_calculate">SCREWS_TILT_CALCULATE<a class="headerlink" href="#screws_tilt_calculate" title="Permanent link">&para;</a></h4>
@@ -5199,6 +5287,18 @@ section</a> is enabled.</p>
<p>使用<a href="Config_Reference.html#temperature_fan">temperature_fan配置分段</a>时，以下命令可用：</p>
<h4 id="set_temperature_fan_target">SET_TEMPERATURE_FAN_TARGET<a class="headerlink" href="#set_temperature_fan_target" title="Permanent link">&para;</a></h4>
<p><code>SET_TEMPERATURE_FAN_TARGET temperature_fan=&lt;temperature_fan_名称&gt; [target=&lt;目标温度&gt;] [min_speed=&lt;最小速度&gt;] [max_speed=&lt;最大速度&gt;]</code>：设置一个温度控制风扇的目标温度。如果没有提供目标温度，它将被设为配置文件中定义的温度。如果没有提供速度，则不会进行任何更改。</p>
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">&para;</a></h3>
<p>The following commands are available when a <a href="Config_Reference.html#temperature_probe">temperature_probe config section</a> is enabled.</p>
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_CALIBRATE [PROBE=&lt;probe name&gt;] [TARGET=&lt;value&gt;] [STEP=&lt;value&gt;]</code>: Initiates probe drift calibration for eddy current based probes. The <code>TARGET</code> is a target temperature for the last sample. When the temperature recorded during a sample exceeds the <code>TARGET</code> calibration will complete. The <code>STEP</code> parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to <code>TEMPERATURE_PROBE_NEXT</code>. The default <code>STEP</code> is 2.</p>
<h4 id="temperature_probe_next">TEMPERATURE_PROBE_NEXT<a class="headerlink" href="#temperature_probe_next" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_NEXT</code>: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by <code>STEP</code> has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.</p>
<h4 id="temperature_probe_complete">TEMPERATURE_PROBE_COMPLETE:<a class="headerlink" href="#temperature_probe_complete" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_COMPLETE</code>: Can be used to end calibration and save the current result before the <code>TARGET</code> temperature is reached. This command is only available during calibration.</p>
<h4 id="_2">关于<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h4>
<p><code>ABORT</code>：中止校准过程，丢弃当前结果。此命令仅在漂移校准期间可用。</p>
<h3 id="temperature_probe_enable">TEMPERATURE_PROBE_ENABLE<a class="headerlink" href="#temperature_probe_enable" title="Permanent link">&para;</a></h3>
<p><code>TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]</code>: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.</p>
<h3 id="tmcxxxx">[tmcXXXX]<a class="headerlink" href="#tmcxxxx" title="Permanent link">&para;</a></h3>
<p>The following commands are available when any of the <a href="Config_Reference.html#tmc-stepper-driver-configuration">tmcXXXX config sections</a> are enabled.</p>
<h4 id="dump_tmc">DUMP_TMC<a class="headerlink" href="#dump_tmc" title="Permanent link">&para;</a></h4>
@@ -5246,18 +5346,6 @@ section</a> is enabled.</p>
<p>The following commands are available when the <a href="Config_Reference.html#z_tilt">z_tilt config section</a> is enabled.</p>
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">&para;</a></h4>
<p><code>Z_TILT_ADJUST [RETRIES=&lt;value&gt;] [RETRY_TOLERANCE=&lt;value&gt;] [HORIZONTAL_MOVE_Z=&lt;value&gt;] [&lt;probe_parameter&gt;=&lt;value&gt;]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">&para;</a></h3>
<p>The following commands are available when a <a href="Config_Reference.html#temperature_probe">temperature_probe config section</a> is enabled.</p>
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_CALIBRATE [PROBE=&lt;probe name&gt;] [TARGET=&lt;value&gt;] [STEP=&lt;value&gt;]</code>: Initiates probe drift calibration for eddy current based probes. The <code>TARGET</code> is a target temperature for the last sample. When the temperature recorded during a sample exceeds the <code>TARGET</code> calibration will complete. The <code>STEP</code> parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to <code>TEMPERATURE_PROBE_NEXT</code>. The default <code>STEP</code> is 2.</p>
<h4 id="temperature_probe_next">TEMPERATURE_PROBE_NEXT<a class="headerlink" href="#temperature_probe_next" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_NEXT</code>: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by <code>STEP</code> has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.</p>
<h4 id="temperature_probe_complete">TEMPERATURE_PROBE_COMPLETE:<a class="headerlink" href="#temperature_probe_complete" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_COMPLETE</code>: Can be used to end calibration and save the current result before the <code>TARGET</code> temperature is reached. This command is only available during calibration.</p>
<h4 id="_2">关于<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h4>
<p><code>ABORT</code>：中止校准过程，丢弃当前结果。此命令仅在漂移校准期间可用。</p>
<h3 id="temperature_probe_enable">TEMPERATURE_PROBE_ENABLE<a class="headerlink" href="#temperature_probe_enable" title="Permanent link">&para;</a></h3>
<p><code>TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]</code>: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.</p>
</article>

4
zh/Hall_Filament_Width_Sensor.html
View File

@@ -1357,8 +1357,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

30
zh/Installation.html
View File

@@ -1366,8 +1366,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1481,8 +1481,8 @@
<h1 id="_1">安装<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h1>
<p>这些说明假设软件将在运行 Klipper 兼容前端的 Linux 主机上运行。建议使用 SBC（小型板计算机），例如 Raspberry Pi 或基于 Debian 的 Linux 设备作为主机（有关其他选项，请参阅 <a href="FAQ.html#can-i-run-klipper-on-something-other-than-a-raspberry-pi-3">FAQ</a>）。</p>
<p>就本说明而言，主机与 Linux 设备相关，而 mcu 与印刷电路板相关。SBC 与术语“小型板计算机”相关，例如 Raspberry Pi。</p>
<p>These instructions assume the software will run on a Linux-based host running a Klipper-compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian-based Linux device be used as the host machine (see the <a href="FAQ.html#can-i-run-klipper-on-something-other-than-a-raspberry-pi-3">FAQ</a> for other options).</p>
<p>For the purposes of these instructions, host relates to the Linux device and mcu relates to the printer board. SBC relates to the term Small Board Computer such as the Raspberry Pi.</p>
<h2 id="klipper">获取 Klipper 配置文件<a class="headerlink" href="#klipper" title="Permanent link">&para;</a></h2>
<p>大多数 Klipper 设置由“打印机配置文件”printer.cfg 决定，该文件将存储在主机上。通常可以通过在 Klipper <a href="https://github.com/Klipper3d/klipper/blob/master/config/">config 目录</a> 中查找以“printer-”前缀开头且与目标打印机相对应的文件来找到适当的配置文件。Klipper 配置文件包含安装过程中需要的有关打印机的技术信息。</p>
<p>如果 Klipper 配置目录中没有合适的打印机配置文件，请尝试搜索打印机制造商的网站，看看他们是否有合适的 Klipper 配置文件。</p>
@@ -1493,13 +1493,13 @@
<p>目前最好的选择是通过 <a href="https://moonraker.readthedocs.io/">Moonraker web API</a> 检索信息的前端，也可以选择使用 <a href="https://octoprint.org/">Octoprint</a> 来控制 Klipper。</p>
<p>用户可自行选择使用哪种工具，但底层的 Klipper 在所有情况下都是相同的。我们鼓励用户研究可用的选项并做出明智的决定。</p>
<h2 id="sbc">获取 SBC 的操作系统映像<a class="headerlink" href="#sbc" title="Permanent link">&para;</a></h2>
<p>有多种方法可以获取用于 SBC 的 Klipper 操作系统映像，大多数方法取决于您希望使用哪种前端。这些 SBC 板的一些制造商还提供自己的以 Klipper 为中心的映像。</p>
<p>两个主要的基于 Moonraker 的前端是 <a href="https://docs.fluidd.xyz/">Fluidd</a> 和 <a href="https://docs.mainsail.xyz/">Mainsail</a>，后者具有预制的安装映像 <a href="http://docs.mainsailOS.xyz">"MainsailOS"</a>，它有适用于 Raspberry Pi 和一些 OrangePi 变体的选项。</p>
<p>There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manufacturers of these SBC boards also provide their own Klipper-centric images.</p>
<p>The two main Moonraker-based front ends are <a href="https://docs.fluidd.xyz/">Fluidd</a> and <a href="https://docs.mainsail.xyz/">Mainsail</a>, the latter of which has a premade install image <a href="https://docs-os.mainsail.xyz/">"MainsailOS"</a>, this has the option for Raspberry Pi and some OrangePi variants.</p>
<p>Fluidd 可以通过 KIAUH（Klipper 安装和更新助手）进行安装，如下所述，它是所有 Klipper 的第三方安装程序。</p>
<p>OctoPrint 可以通过流行的 OctoPi 镜像或通过 KIAUH 安装，此过程在 <OctoPrint.md> 中有说明</p>
<h2 id="kiauh">通过 KIAUH 安装<a class="headerlink" href="#kiauh" title="Permanent link">&para;</a></h2>
<p>通常，您会从 SBC 的基本映像（例如 RPiOS Lite）开始，或者在 x86 Linux 设备的情况下，从 Ubuntu Server 开始。请注意，不建议使用桌面版本，因为某些辅助程序可能会阻止某些 Klipper 功能运行，甚至屏蔽对某些打印板的访问。</p>
<p>KIAUH 可用于在运行 Debian 的各种 Linux 系统上安装 Klipper 及其相关程序。更多信息请访问 <a href="https://github.com/dw-0/kiauh">https://github.com/dw-0/kiauh</a></p>
<p>Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of an x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions from working and even mask access to some printer boards.</p>
<p>KIAUH can be used to install Klipper and its associated programs on a variety of Linux-based systems that run a form of Debian. More information can be found at <a href="https://github.com/dw-0/kiauh">https://github.com/dw-0/kiauh</a></p>
<h2 id="_2">构建和刷写微控制器<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<p>要编译微控制器代码，首先在主机设备上运行以下命令：</p>
<div class="highlight"><pre><span></span><code>cd ~/klipper/
@@ -1510,7 +1510,7 @@ make menuconfig
<div class="highlight"><pre><span></span><code>make
</code></pre></div>
<p>如果<a href="#obtain-a-klipper-configuration-file">打印机配置文件</a>顶部的注释描述了"flashing"最终固件镜像到打印机控制板的特殊步骤，那么请遵循这些步骤，然后继续进行<a href="#configuring-octoprint-to-use-klipper">配置OctoPrint</a>。</p>
<p>If the comments at the top of the <a href="#obtain-a-klipper-configuration-file">printer configuration file</a> describe custom steps for "flashing" the final image to the printer control board, then follow those steps and then proceed to <a href="#configuring-octoprint-to-use-klipper">configuring OctoPrint</a>.</p>
<p>否则，通常采用以下步骤来"flash"打印机控制板。首先，需要确定连接到微控制器的串行端口。然后，运行以下程序：</p>
<div class="highlight"><pre><span></span><code>ls /dev/serial/by-id/*
</code></pre></div>
@@ -1520,8 +1520,8 @@ make menuconfig
</code></pre></div>
<p>通常，每台打印机都有自己独特的串行端口名称。此唯一名称将在刷新微控制器时使用。上面的输出中可能有多行 - 如果是这样，请选择与微控制器相对应的行。如果列出了许多项目并且选择不明确，请拔下电路板并再次运行命令，缺少的项目将是您的打印板（有关更多信息，请参阅 <a href="FAQ.html#wheres-my-serial-port">FAQ</a>）。</p>
<p>对于带有 STM32 或克隆芯片、LPC 芯片和其他芯片的常见微控制器，通常需要通过 SD 卡进行初始 Klipper 闪存。</p>
<p>使用此方法进行刷写时，务必确保打印板未通过 USB 连接到主机，因为某些电路板能够将电源反馈给电路板并阻止刷写开始。</p>
<p>For common micro-controllers with STM32 or clone chips, LPC chips and others, it is usual that these need an initial Klipper flash via SD card.</p>
<p>When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring.</p>
<p>对于使用 Atmega 芯片的常见微控制器，例如 2560，代码可以使用类似以下内容进行烧录：</p>
<div class="highlight"><pre><span></span><code>sudo service klipper stop
make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
@@ -1538,9 +1538,9 @@ sudo service klipper start
<p>It is important to note that RP2040 chips may need to be put into Boot mode before this operation.</p>
<h2 id="klipper_2">配置 Klipper<a class="headerlink" href="#klipper_2" title="Permanent link">&para;</a></h2>
<p>The next step is to copy the <a href="#obtain-a-klipper-configuration-file">printer configuration file</a> to the host.</p>
<p>Arguably the easiest way to set the Klipper configuration file is using the built in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.</p>
<p>Arguably the easiest way to set the Klipper configuration file is using the built-in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.</p>
<p>Another option is to use a desktop editor that supports editing files over the "scp" and/or "sftp" protocols. There are freely available tools that support this (eg, Notepad++, WinSCP, and Cyberduck). Load the printer config file in the editor and then save it as a file named "printer.cfg" in the home directory of the pi user (ie, /home/pi/printer.cfg).</p>
<p>Alternatively, one can also copy and edit the file directly on the host via ssh. That may look something like the following (be sure to update the command to use the appropriate printer config filename):</p>
<p>Alternatively, one can also copy and edit the file directly on the host via SSH. That may look something like the following (be sure to update the command to use the appropriate printer config filename):</p>
<div class="highlight"><pre><span></span><code>cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
nano ~/printer.cfg
</code></pre></div>
@@ -1558,9 +1558,9 @@ nano ~/printer.cfg
serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
</code></pre></div>
<p>After creating and editing the file it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.</p>
<p>After creating and editing the file, it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report that the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.</p>
<p>在定制打印机配置文件时，Klipper 报告配置错误是很正常的情况。如果发生错误，请对打印机配置文件进行必要的修正，并发出"restart"，直到"status"报告打印机已准备就绪。</p>
<p>Klipper reports error messages via the command console and via pop up in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located in ~/printer_data/logs this is named klippy.log</p>
<p>Klipper reports error messages via the command console and pop-ups in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located at <code>~/printer_data/logs/klippy.log</code>.</p>
<p>在Klipper报告打印机已就绪后，继续进入<a href="Config_checks.html">配置检查文件</a>，对配置文件中的定义进行一些基本检查。其他信息见主<a href="Overview.html">文档参考</a>。</p>

4
zh/Kinematics.html
View File

@@ -1411,8 +1411,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

1635
zh/Load_Cell.html Normal file
View File

File diff suppressed because it is too large Load Diff

4
zh/MCU_Commands.html
View File

@@ -1383,8 +1383,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Manual_Level.html
View File

@@ -1358,8 +1358,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

23
zh/Measuring_Resonances.html
View File

@@ -838,11 +838,11 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948
</a>
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500">
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948">
<ul class="md-nav__list">
<li class="md-nav__item">
@@ -1595,8 +1595,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1721,11 +1721,11 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948
</a>
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500">
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948">
<ul class="md-nav__list">
<li class="md-nav__item">
@@ -1942,7 +1942,7 @@
<p>Klipper has built-in support for the ADXL345, MPU-9250, LIS2DW and LIS3DH compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345 can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper. The LIS2DW and LIS3DH can be connected to either SPI or I2C with the same considerations as above.</p>
<p>When sourcing accelerometers, be aware that there are a variety of different PCB board designs and different clones of them. If it is going to be connected to a 5V printer MCU ensure it has a voltage regulator and level shifters.</p>
<p>For ADXL345s, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s and LIS2DW/LIS3DH there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948s and LIS2DW/LIS3DH there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
<h2 id="mcus-with-klipper-i2c-fast-mode-support">MCUs with Klipper I2C <em>fast-mode</em> Support<a class="headerlink" href="#mcus-with-klipper-i2c-fast-mode-support" title="Permanent link">&para;</a></h2>
<table>
<thead>
@@ -2107,7 +2107,7 @@ GND+SCL
</code></pre></div>
<p>请注意，与电缆屏蔽不同，任何接地网(S)都应在两端连接。</p>
<h4 id="mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500">MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500<a class="headerlink" href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500" title="Permanent link">&para;</a></h4>
<h4 id="mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948">MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948<a class="headerlink" href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948" title="Permanent link">&para;</a></h4>
<p>这些加速度计已在RPI、RP2040(Pico)和AVR上以400kbit/S(<em>快速模式</em>)的I2C模式工作。一些MPU加速度计模块包括上拉，但有些模块在10K时太大，必须更换或补充较小的并联电阻。</p>
<p>推荐的树莓派上的I2C连接方案：</p>
<table>
@@ -2328,6 +2328,7 @@ I2C_BUS：I2c.1。
100、100、20#一个例子
</code></pre></div>
<p>If you are using the ICM20948, replace instances of "mpu9250" with "icm20948".</p>
<h4 id="picompu-9520">配置与Pico兼容的MPU-9520<a class="headerlink" href="#picompu-9520" title="Permanent link">&para;</a></h4>
<p>默认情况下，Pico I2C设置为400000。只需将以下内容添加到printer.cfg：</p>
<div class="highlight"><pre><span></span><code>[mcu pico]
@@ -2346,6 +2347,7 @@ probe_points:
pins: pico:gpio23
</code></pre></div>
<p>If you are using the ICM20948, replace instances of "mpu9250" with "icm20948".</p>
<h4 id="configure-mpu-9520-compatibles-with-avr">Configure MPU-9520 Compatibles with AVR<a class="headerlink" href="#configure-mpu-9520-compatibles-with-avr" title="Permanent link">&para;</a></h4>
<p>AVR I2C will be set to 400000 by the mpu9250 option. Simply add the following to the printer.cfg:</p>
<div class="highlight"><pre><span></span><code>[mcu nano]
@@ -2360,6 +2362,7 @@ probe_points:
100, 100, 20 # an example
</code></pre></div>
<p>If you are using the ICM20948, replace instances of "mpu9250" with "icm20948".</p>
<p>通过<code>RESTART</code>命令重启Klipper。</p>
<h2 id="_6">测量共振值<a class="headerlink" href="#_6" title="Permanent link">&para;</a></h2>
<h3 id="_7">检查设置<a class="headerlink" href="#_7" title="Permanent link">&para;</a></h3>

4
zh/Multi_MCU_Homing.html
View File

@@ -1298,8 +1298,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Navigation.html
View File

@@ -1281,8 +1281,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/OctoPrint.html
View File

@@ -1345,8 +1345,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

5
zh/Overview.html
View File

@@ -1348,8 +1348,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1524,6 +1524,7 @@
<li><a href="TSL1401CL_Filament_Width_Sensor.html">TSL1401CL 耗材线径传感器</a></li>
<li><a href="Hall_Filament_Width_Sensor.html">霍尔耗材宽度传感器</a></li>
<li><a href="Eddy_Probe.html">Eddy 涡流感应探针</a></li>
<li><a href="Load_Cell.html">Load Cells</a></li>
</ul>

4
zh/Packaging.html
View File

@@ -1350,8 +1350,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

6
zh/Pressure_Advance.html
View File

@@ -1336,8 +1336,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1427,7 +1427,7 @@
<h2 id="_2">调整压力提前<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<p>压力提前有两个作用 - 它可以减少非挤出移动过程中的溢料和减少转弯时的凸起。本指南使用第二个功能（减少转弯过程中的凸起）作为优化机制。</p>
<p>为了校准压力提前，打印机必须已经配置完成并可以正常工作。因为调优测试涉及打印和检查测试对象。在运行测试之前，最好完整阅读本文档。</p>
<p>用切片软件将<a href="prints/square_tower.stl">docs/prints/square_tower.stl</a>模型转化为G-Code。建议切片时使用高速度（如大于100mm/s），0%填充，高层厚（如75%以上的喷嘴直径）。确保“动态加速度调整”功能已关闭。</p>
<p>Use a slicer to generate g-code for the large hollow square found in <a href="prints/square_tower.stl">docs/prints/square_tower.stl</a>. Use a high speed (eg, 100mm/s), zero infill, and a coarse layer height (the layer height should be around 75% of the nozzle diameter). Make sure any "dynamic acceleration control" and "scarf joint" seams are disabled in the slicer.</p>
<p>在打印G-Code前输入下面的命令：</p>
<div class="highlight"><pre><span></span><code>SET_VELOCITY_LIMIT SQUARE_CORNER_VELOCITY=1 ACCEL=500
</code></pre></div>

4
zh/Probe_Calibrate.html
View File

@@ -1359,8 +1359,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Protocol.html
View File

@@ -1437,8 +1437,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/RPi_microcontroller.html
View File

@@ -1378,8 +1378,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

74
zh/Releases.html
View File

@@ -371,6 +371,20 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#klipper-0130" class="md-nav__link">
Klipper 0.13.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0120" class="md-nav__link">
Klipper 0.12.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0110" class="md-nav__link">
Klipper 0.11.0
@@ -1403,8 +1417,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1458,6 +1472,20 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#klipper-0130" class="md-nav__link">
Klipper 0.13.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0120" class="md-nav__link">
Klipper 0.12.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0110" class="md-nav__link">
Klipper 0.11.0
@@ -1560,6 +1588,48 @@
<h1 id="_1">发行说明<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h1>
<p>Klipper版本发布。如何安装Klipper ，请查看<a href="Installation.html">installation</a>。</p>
<h2 id="klipper-0130">Klipper 0.13.0<a class="headerlink" href="#klipper-0130" title="Permanent link">&para;</a></h2>
<p>Available on 20250411. Major changes in this release:</p>
<ul>
<li>New "sweeping vibrations" resonance testing mechanism for input shaper.</li>
<li>Fans and GPIO pins can now be assigned a formula (via Jinja2 "templates").</li>
<li>The bed_mesh code now supports "adaptive bed mesh". The area probed can be adjusted for the size of the print.</li>
<li>A new <code>minimum_cruise_ratio</code> kinematic parameter has been added (it replaces the previous <code>max_accel_to_decel</code> parameter).</li>
<li>Several new sensors added:<ul>
<li>Support for ldc1612 "eddy" current sensors. This includes probing support, fast "scan" probing, and temperature calibration.</li>
<li>New support for "load cell" measurements. Support for connecting these load cells to hx71x and ads1220 ADC sensors.</li>
<li>Support for BMP180, BMP388, and SHT3x temperature sensors. Support for measuring temperature with ADS1x1x ADC chips.</li>
<li>New lis3dh and icm20948 accelerometer support.</li>
<li>Support for mt6816 and mt6826s "hall angle" sensors.</li>
</ul>
</li>
<li>New micro-controller improvements:<ul>
<li>New support for rp2350 micro-controllers.</li>
<li>Existing rp2040 chips now run at 200MHz (up from 125Mhz).</li>
<li>The micro-controller code can now define many more commands (up to 16384 from 128).</li>
</ul>
</li>
<li>Other modules added: aip31068_spi, canbus_stats, error_mcu, garbage_collection, pwm_cycle_time, pwm_tool, garbage_collection.</li>
<li>几个错误的修复和代码的清理。</li>
</ul>
<h2 id="klipper-0120">Klipper 0.12.0<a class="headerlink" href="#klipper-0120" title="Permanent link">&para;</a></h2>
<p>Available on 20231110. Major changes in this release:</p>
<ul>
<li>Support for COPY and MIRROR modes on IDEX printers.</li>
<li>Several micro-controller improvements:<ul>
<li>Support for new ar100 and hc32f460 architectures.</li>
<li>Support for stm32f7, stm32g0b0, stm32g07x, stm32g4, stm32h723, n32g45x, samc21, and samd21j18 chip variants.</li>
<li>Improved DFU and Katapult reboot handling.</li>
<li>Improved performance on USB to CANbus bridge mode.</li>
<li>Improved performance on "linux mcu".</li>
<li>New support for software based i2c.</li>
</ul>
</li>
<li>New hardware support for tmc2240 stepper motor drivers, lis2dw12 accelerometers, and aht10 temperature sensors.</li>
<li>New axis_twist_compensation and temperature_combined modules added.</li>
<li>New support for gcode arcs in XY, XZ, and YZ planes.</li>
<li>几个错误的修复和代码的清理。</li>
</ul>
<h2 id="klipper-0110">Klipper 0.11.0<a class="headerlink" href="#klipper-0110" title="Permanent link">&para;</a></h2>
<p>发布于2022年11月28日。此版本的主要更新：</p>
<ul>

4
zh/Resonance_Compensation.html
View File

@@ -1454,8 +1454,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Rotation_Distance.html
View File

@@ -1379,8 +1379,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/SDCard_Updates.html
View File

@@ -1384,8 +1384,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Skew_Correction.html
View File

@@ -1357,8 +1357,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Slicers.html
View File

@@ -1378,8 +1378,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

8
zh/Sponsors.html
View File

@@ -1286,8 +1286,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1527,7 +1527,7 @@
<nav class="md-footer__inner md-grid" aria-label="页脚">
<a href="Eddy_Probe.html" class="md-footer__link md-footer__link--prev" aria-label="上一页: Eddy 感应涡流探针" rel="prev">
<a href="Load_Cell.html" class="md-footer__link md-footer__link--prev" aria-label="上一页: Load Cells" rel="prev">
<div class="md-footer__button md-icon">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12z"/></svg>
</div>
@@ -1536,7 +1536,7 @@
<span class="md-footer__direction">
上一页
</span>
Eddy 感应涡流探针
Load Cells
</div>
</div>
</a>

74
zh/Status_Reference.html
View File

@@ -875,6 +875,13 @@
bed_screws
</a>
</li>
<li class="md-nav__item">
<a href="#canbus_stats" class="md-nav__link">
canbus_stats
</a>
</li>
<li class="md-nav__item">
@@ -994,6 +1001,13 @@
led
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
load_cell
</a>
</li>
<li class="md-nav__item">
@@ -1085,6 +1099,13 @@
servo
</a>
</li>
<li class="md-nav__item">
<a href="#skew_correctionpy" class="md-nav__link">
skew_correction.py
</a>
</li>
<li class="md-nav__item">
@@ -1639,8 +1660,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1713,6 +1734,13 @@
bed_screws
</a>
</li>
<li class="md-nav__item">
<a href="#canbus_stats" class="md-nav__link">
canbus_stats
</a>
</li>
<li class="md-nav__item">
@@ -1832,6 +1860,13 @@
led
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
load_cell
</a>
</li>
<li class="md-nav__item">
@@ -1923,6 +1958,13 @@
servo
</a>
</li>
<li class="md-nav__item">
<a href="#skew_correctionpy" class="md-nav__link">
skew_correction.py
</a>
</li>
<li class="md-nav__item">
@@ -2041,13 +2083,22 @@
<li><code>profiles</code>：当前定义的配置，使用 BED_MESH_PROFILE 进行设置。</li>
</ul>
<h2 id="bed_screws">bed_screws<a class="headerlink" href="#bed_screws" title="Permanent link">&para;</a></h2>
<p><code>Config_Reference.md#bed_screws</code> 对象中提供了以下信息：</p>
<p>The following information is available in the <a href="Config_Reference.html#bed_screws">bed_screws</a> object:</p>
<ul>
<li><code>is_active</code>：如果床调平螺丝调整工具当前处于活动状态，则返回 True。</li>
<li><code>state</code>：床调平螺丝调整工具状态。它可以是以下字符串之一："adjust", "fine"。</li>
<li><code>current_screw</code>：当前正在被调整的螺丝的索引。</li>
<li><code>accepted_screws</code>：已被接受的螺丝数量。</li>
</ul>
<h2 id="canbus_stats">canbus_stats<a class="headerlink" href="#canbus_stats" title="Permanent link">&para;</a></h2>
<p>The following information is available in the <code>canbus_stats some_mcu_name</code> object (this object is automatically available if an mcu is configured to use canbus):</p>
<ul>
<li><code>rx_error</code>: The number of receive errors detected by the micro-controller canbus hardware.</li>
<li><code>tx_error</code>: The number of transmit errors detected by the micro-controller canbus hardware.</li>
<li><code>tx_retries</code>: The number of transmit attempts that were retried due to bus contention or errors.</li>
<li><code>bus_state</code>: The status of the interface (typically "active" for a bus in normal operation, "warn" for a bus with recent errors, "passive" for a bus that will no longer transmit canbus error frames, or "off" for a bus that will no longer transmit or receive messages).</li>
</ul>
<p>Note that only the rp2XXX micro-controllers report a non-zero <code>tx_retries</code> field and the rp2XXX micro-controllers always report <code>tx_error</code> as zero and <code>bus_state</code> as "active".</p>
<h2 id="configfile">configfile<a class="headerlink" href="#configfile" title="Permanent link">&para;</a></h2>
<p><code>configfile</code> 对象中提供了以下信息（该对象始终可用）：</p>
<ul>
@@ -2161,6 +2212,7 @@
<h2 id="hall_filament_width_sensor">hall_filament_width_sensor<a class="headerlink" href="#hall_filament_width_sensor" title="Permanent link">&para;</a></h2>
<p><a href="Config_Reference.html#hall_filament_width_sensor">hall_filament_width_sensor</a> 对象提供了以下信息：</p>
<ul>
<li>all items from <a href="Status_Reference.html#filament_switch_sensor">filament_switch_sensor</a></li>
<li><code>is_active</code>：如果传感器当前处于活动状态，返回True。</li>
<li><code>Diameter</code>：上一次传感器读数，单位为 mm。</li>
<li><code>Raw</code>：上一次传感器原始 ADC 读数。</li>
@@ -2191,6 +2243,17 @@
<ul>
<li><code>color_data</code>：一个包含链中每个LED的RGBW值的颜色列表的列表。每个值都以0.0到1.0的浮点数表示。每个颜色列表包含4个项目（红、绿、蓝、白），即使底层的LED支持较少的颜色通道。例如，可以通过<code>printer["neopixel &lt;配置名&gt;"].color_data[1][2]</code>访问链中第二个neopixel的蓝色值（颜色列表中的第三项）。</li>
</ul>
<h2 id="load_cell">load_cell<a class="headerlink" href="#load_cell" title="Permanent link">&para;</a></h2>
<p>The following information is available for each <code>[load_cell name]</code>:</p>
<ul>
<li>'is_calibrated': True/False is the load cell calibrated</li>
<li>'counts_per_gram': The number of raw sensor counts that equals 1 gram of force</li>
<li>'reference_tare_counts': The reference number of raw sensor counts for 0 force</li>
<li>'tare_counts': The current number of raw sensor counts for 0 force</li>
<li>'force_g': The force in grams, averaged over the last polling period.</li>
<li>'min_force_g': The minimum force in grams, over the last polling period.</li>
<li>'max_force_g': The maximum force in grams, over the last polling period.</li>
</ul>
<h2 id="manual_probe">manual_probe<a class="headerlink" href="#manual_probe" title="Permanent link">&para;</a></h2>
<p><code>manual_probe</code> 对象中提供了以下信息：</p>
<ul>
@@ -2278,6 +2341,11 @@
<ul>
<li><code>printer["servo &lt;配置名&gt;"].value</code>：与指定伺服相关 PWM 引脚的上一次设置的值（0.0 和 1.0 之间的值）。</li>
</ul>
<h2 id="skew_correctionpy">skew_correction.py<a class="headerlink" href="#skew_correctionpy" title="Permanent link">&para;</a></h2>
<p>The following information is available in the <code>skew_correction</code> object (this object is available if any skew_correction is defined):</p>
<ul>
<li><code>current_profile_name</code>: Returns the name of the currently loaded SKEW_PROFILE.</li>
</ul>
<h2 id="stepper_enable">stepper_enable<a class="headerlink" href="#stepper_enable" title="Permanent link">&para;</a></h2>
<p>以下信息可在<code>stepper_enable</code> 对象中获得（这个对象在定义了任何步进电机后可用）：</p>
<ul>

5
zh/TMC_Drivers.html
View File

@@ -1535,8 +1535,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1837,6 +1837,7 @@
<p>一般来说，spreadCycle模式比stealthChop模式提供更大的扭矩和更高的定位精度。然而，在某些打印机上，stealthChop 模式显著降低可听到的噪音。</p>
<p>对两个模式的比较测试显示，在使用stealthChop模式时，恒速移动过程时有大约为一个整步75%的"位置滞后 "（例如，在一台旋转距离（rotation_distance ）为40mm、每圈200步（steps_per_rotation）的打印机上，恒速移动的位置偏差增加了约0.150mm）。然而，这种 "获得所需位置的延迟 "可能不会表现为明显的打印缺陷，大多数人可能更喜欢stealthChop模式更安静的打印。</p>
<p>建议总是使用 "spreadCycle "模式（通过不指定<code>stealthchop_threshold</code>）或总是使用 "stealthChop "模式（通过设置<code>stealthchop_threshold</code>为99999）。不幸的是，如果在电机处于非零速度时改变模式，驱动器往往会产生糟糕和混乱的结果。</p>
<p>Note that the <code>stealthchop_threshold</code> config option does not impact sensorless homing as Klipper automatically switches the TMC driver to an appropriate mode during sensorless homing operations.</p>
<h2 id="tmc_1">TMC插值设置引入了微小的位置偏差<a class="headerlink" href="#tmc_1" title="Permanent link">&para;</a></h2>
<p>TMC驱动程序的 <code>interpolate</code> 设置可以减少打印机运动的噪音，但代价是引入一个小的系统位置误差。这个系统性的位置误差是由驱动器在执行Klipper发送的 "步骤 "时的延迟造成的。在恒速移动过程中，这种延迟导致了将近一半的配置微步的位置误差（更准确地说，误差是一半的微步距离减去512分之一的整步距离）。例如，在一个旋转距离（rotation_distance）为40毫米、每圈200步（steps_per_rotation）、16微步的轴上，在恒速移动过程中引入的系统误差是~0.006毫米。</p>
<p>为了获得最佳的定位精度，可以考虑使用spreadCycle模式，并禁用插值（在TMC驱动配置中设置<code>interpolate: False</code> ）。当以这种方式配置时，可以增加<code>microstep</code>设置，以减少步进运动中的噪音。通常情况下，微步设置为<code>64</code>或<code>128</code>会有类似于插值的噪音水平，而且不会引入系统性的位置误差。</p>

4
zh/TSL1401CL_Filament_Width_Sensor.html
View File

@@ -1336,8 +1336,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
zh/Using_PWM_Tools.html
View File

@@ -1350,8 +1350,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

BIN
zh/_klipper3d/__pycache__/mkdocs_hooks.cpython-38.pyc
View File

Binary file not shown.

4
zh/index.html
View File

@@ -1283,8 +1283,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

2
zh/search/search_index.json
View File

File diff suppressed because one or more lines are too long

115
zh/sitemap.xml
View File

@@ -2,277 +2,282 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>

BIN
zh/sitemap.xml.gz
View File

Binary file not shown.