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

This commit is contained in:
KevinOConnor
2022-08-24 00:03:59 +00:00
parent 1253c22ff6
commit 831e7e3ba5
24 changed files with 398 additions and 393 deletions

View File

@@ -1358,7 +1358,7 @@
<h1 id="can">CAN 总线<a class="headerlink" href="#can" title="Permanent link">&para;</a></h1>
<p>本文档描述了 Klipper 的 CAN 总线支持。</p>
<h2 id="_1">硬件设备<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h2>
<p>Klipper currently supports CAN on stm32 and rp2040 chips. In addition, the micro-controller chip must be on a board that has a CAN transceiver.</p>
<p>Klipper目前支持在stm32和rp2040芯片上使用CAN总线。此外微控制器芯片必须连接到一个CAN收发器。</p>
<p>要针对 CAN 进行编译,请运行 <code>make menuconfig</code>并选择"CAN Bus"作为通信接口。最后,编译微控制器代码并将其刷写到目标控制版上。</p>
<h2 id="_2">主机硬件<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<p>为了使用 CAN 总线,主机需要一个适配器。目前有两种常见的选择:</p>
@@ -1402,7 +1402,7 @@ canbus_uuid: 11aa22bb33cc
<ul>
<li>“桥接MCU” 实际上并不在CAN总线上。传入和传出的消息不会占用CAN总线上的带宽。因此位于CAN总线上的其他适配器无法看到MCU。</li>
<li>有必要在Linux中配置<code>can0</code> 或类似接口以便与总线通信。然而Klipper 会忽略 Linux的CAN总线速度和 CAN 总线bit-timing选项。目前CAN总线的频率需要在 "make menuconfig "中指定。Linux中指定的总线速度会被忽略。</li>
<li>Whenever the "bridge mcu" is reset, Linux will disable the corresponding <code>can0</code> interface. To ensure proper handling of FIRMWARE_RESTART and RESTART commands, it is recommended to replace <code>auto</code> with <code>allow-hotplug</code> in the <code>/etc/network/interfaces.d/can0</code> file. For example:</li>
<li>每当 "bridge mcu "被重置时Linux 将禁用相应的<code>can0</code> 接口。为了确保正确处理 FIRMWARE_RESTART RESTART 命令,建议在<code>/etc/network/interfaces.d/can0</code> 文件中用<code>allow-hotplug</code> 替换<code>auto</code> 。例如:</li>
</ul>
<div class="highlight"><pre><span></span><code>allow-hotplug can0
iface can0 can static

View File

@@ -778,8 +778,8 @@
</li>
<li class="md-nav__item">
<a href="#testing-custom-axes" class="md-nav__link">
Testing custom axes
<a href="#_11" class="md-nav__link">
自定义测试轴
</a>
</li>
@@ -790,7 +790,7 @@
</li>
<li class="md-nav__item">
<a href="#_11" class="md-nav__link">
<a href="#_12" class="md-nav__link">
输入整形器自动校准
</a>
@@ -798,7 +798,7 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#_12" class="md-nav__link">
<a href="#_13" class="md-nav__link">
重新校准输入整形器
</a>
@@ -1450,8 +1450,8 @@
</li>
<li class="md-nav__item">
<a href="#testing-custom-axes" class="md-nav__link">
Testing custom axes
<a href="#_11" class="md-nav__link">
自定义测试轴
</a>
</li>
@@ -1462,7 +1462,7 @@
</li>
<li class="md-nav__item">
<a href="#_11" class="md-nav__link">
<a href="#_12" class="md-nav__link">
输入整形器自动校准
</a>
@@ -1470,7 +1470,7 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#_12" class="md-nav__link">
<a href="#_13" class="md-nav__link">
重新校准输入整形器
</a>
@@ -1769,7 +1769,7 @@ max_smoothing: 0.25 # an example
<p>或者,按照<a href="Resonance_Compensation.html#selecting-max_accel">这个</a>章节的输入整形器调整指南,打印测试模型,通过实验选择<code>max_accel</code> 参数。</p>
<p>同样的通知也适用于带有<code>SHAPER_CALIBRATE</code> 命令的输入整形器<a href="#input-shaper-auto-calibration">自动校准</a>:在自动校准后仍需选择正确的<code>max_accel</code> 值,建议的加速度限制将不会被自动应用。</p>
<p>如果重新校准一个整形器,并且建议的整形器配置的报告平滑度与你在以前的校准中得到的几乎相同,这个步骤可以被跳过。</p>
<h3 id="testing-custom-axes">Testing custom axes<a class="headerlink" href="#testing-custom-axes" title="Permanent link">&para;</a></h3>
<h3 id="_11">自定义测试轴<a class="headerlink" href="#_11" title="Permanent link">&para;</a></h3>
<p><code>TEST_RESONANCES</code> command supports custom axes. While this is not really useful for input shaper calibration, it can be used to study printer resonances in-depth and to check, for example, belt tension.</p>
<p>To check the belt tension on CoreXY printers, execute</p>
<div class="highlight"><pre><span></span><code>TEST_RESONANCES AXIS=1,1 OUTPUT=raw_data
@@ -1792,24 +1792,24 @@ TEST_RESONANCES AXIS=0.866025404,-0.5 OUTPUT=raw_data
</code></pre></div>
<p>以生成<code>/tmp/resonances.png</code>,对比共振的数据。</p>
<h2 id="_11">输入整形器自动校准<a class="headerlink" href="#_11" title="Permanent link">&para;</a></h2>
<h2 id="_12">输入整形器自动校准<a class="headerlink" href="#_12" title="Permanent link">&para;</a></h2>
<p>除了为输入整形器功能手动选择适当的参数外还可以直接从Klipper运行输入整形器的自动调谐。通过Octoprint终端运行以下命令</p>
<div class="highlight"><pre><span></span><code>SHAPER_CALIBRATE
</code></pre></div>
<p>这将为两个轴运行完整的测试并生成用于频率响应和建议的输入整形器的csv输出默认为<code>/tmp/calibration_data_*.csv</code> 。在Octoprint中会提示控制台每个输入整形器的建议频率以及为这台打印机推荐的输入整形器。例如</p>
<div class="highlight"><pre><span></span><code>Calculating the best input shaper parameters for y axis # 正在计算y轴的最佳输入整形参数
Fitted shaper &#39;zv&#39; frequency = 39.0 Hz (vibrations = 13.2%, smoothing ~= 0.105) # 拟合整形“zv”
To avoid too much smoothing with &#39;zv&#39;, suggested max_accel &lt;= 5900 mm/sec^2 # 为避免使用“zv”方法产生过度平滑建议最大加速度&lt;=5900 mm/sec^2
Fitted shaper &#39;mzv&#39; frequency = 36.8 Hz (vibrations = 1.7%, smoothing ~= 0.150) # 拟合整形“mzv”
To avoid too much smoothing with &#39;mzv&#39;, suggested max_accel &lt;= 4000 mm/sec^2 # 为避免使用“mzv”方法产生过度平滑建议最大加速度&lt;=4000 mm/sec^2
Fitted shaper &#39;ei&#39; frequency = 36.6 Hz (vibrations = 2.2%, smoothing ~= 0.240) # 拟合整形“ei”
To avoid too much smoothing with &#39;ei&#39;, suggested max_accel &lt;= 2500 mm/sec^2 # 为避免使用“ei”方法产生过度平滑建议最大加速度&lt;=2500 mm/sec^2
Fitted shaper &#39;2hump_ei&#39; frequency = 48.0 Hz (vibrations = 0.0%, smoothing ~= 0.234) # 拟合整形“2hump_ei”
To avoid too much smoothing with &#39;2hump_ei&#39;, suggested max_accel &lt;= 2500 mm/sec^2 # 为避免使用“2hump_ei”方法产生过度平滑建议最大加速度&lt;=2500 mm/sec^2
Fitted shaper &#39;3hump_ei&#39; frequency = 59.0 Hz (vibrations = 0.0%, smoothing ~= 0.235) # 拟合整形“3hump_ei”
To avoid too much smoothing with &#39;3hump_ei&#39;, suggested max_accel &lt;= 2500 mm/sec^2 # 为避免使用“3hump_ei”方法产生过度平滑建议最大加速度&lt;=2500 mm/sec^2
Recommended shaper_type_y = mzv, shaper_freq_y = 36.8 Hz # 建议shaper_type_y = mzv, shaper_freq_y = 36.8 Hz
<div class="highlight"><pre><span></span><code>Calculating the best input shaper parameters for y axis
Fitted shaper &#39;zv&#39; frequency = 39.0 Hz (vibrations = 13.2%, smoothing ~= 0.105)
To avoid too much smoothing with &#39;zv&#39;, suggested max_accel &lt;= 5900 mm/sec^2
Fitted shaper &#39;mzv&#39; frequency = 36.8 Hz (vibrations = 1.7%, smoothing ~= 0.150)
To avoid too much smoothing with &#39;mzv&#39;, suggested max_accel &lt;= 4000 mm/sec^2
Fitted shaper &#39;ei&#39; frequency = 36.6 Hz (vibrations = 2.2%, smoothing ~= 0.240)
To avoid too much smoothing with &#39;ei&#39;, suggested max_accel &lt;= 2500 mm/sec^2
Fitted shaper &#39;2hump_ei&#39; frequency = 48.0 Hz (vibrations = 0.0%, smoothing ~= 0.234)
To avoid too much smoothing with &#39;2hump_ei&#39;, suggested max_accel &lt;= 2500 mm/sec^2
Fitted shaper &#39;3hump_ei&#39; frequency = 59.0 Hz (vibrations = 0.0%, smoothing ~= 0.235)
To avoid too much smoothing with &#39;3hump_ei&#39;, suggested max_accel &lt;= 2500 mm/sec^2
Recommended shaper_type_y = mzv, shaper_freq_y = 36.8 Hz
</code></pre></div>
<p>如果认同建议的参数,现在可以执行<code>SAVE_CONFIG</code> 来保存设置并重新启动Klipper。 请注意,这不会更新<code>[printer]</code> 分段中的<code>max_accel</code>值。应该按照<a href="#selecting-max_accel">选择max_accel</a>章节中的注意事项手动更新它。</p>
@@ -1819,7 +1819,7 @@ Recommended shaper_type_y = mzv, shaper_freq_y = 36.8 Hz # 建议shaper_type_y =
<p>可以在校准每个轴之后执行<code>SAVE_CONFIG</code></p>
<p>然而,如果同时连接了两个加速度计,只需要运行<code>SHAPER_CALIBRATE</code> ,而不指定轴,就可以一次性校准两个轴的输入整形器。</p>
<h3 id="_12">重新校准输入整形器<a class="headerlink" href="#_12" title="Permanent link">&para;</a></h3>
<h3 id="_13">重新校准输入整形器<a class="headerlink" href="#_13" title="Permanent link">&para;</a></h3>
<p><code>SHAPER_CALIBRATE</code> 命令也可以用来在将来重新校准输入整形器,特别是当打印机发生了一些可能影响其运动学的变化时。可以使用<code>SHAPER_CALIBRATE</code> 命令重新进行全面校准,或者通过提供<code>AXIS=</code> 参数将自动校准限制在一个轴上,例如</p>
<div class="highlight"><pre><span></span><code>SHAPER_CALIBRATE AXIS=X
</code></pre></div>

View File

@@ -1354,7 +1354,7 @@
<h1 id="_1">赞助<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h1>
<p>Klipper是自由软件。我们依赖于赞助商的慷慨支持。请考虑赞助Klipper或支持我们的赞助商。</p>
<h2 id="bigtreetech">BIGTREETECH<a class="headerlink" href="#bigtreetech" title="Permanent link">&para;</a></h2>
<p>[<img src="./img/sponsors/BTT_BTT.png" width="200" /></p>
<p><a href="<a href="https://bigtree-tech.com/collections/all-products">https://bigtree-tech.com/collections/all-products</a>"><img src="./img/sponsors/BTT_BTT.png" width="200"></a></p>
<p>BIGTREETECH是Klipper的官方主板赞助商。BIGTREETECH致力于开发创新和有竞争力的产品更好地服务于3D打印社区。在<a href="https://www.facebook.com/BIGTREETECH">Facebook</a><a href="https://twitter.com/BigTreeTech">Twitter</a>上关注他们。</p>
<h2 id="klipper">Klipper的开发者们<a class="headerlink" href="#klipper" title="Permanent link">&para;</a></h2>
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">&para;</a></h3>

View File

@@ -1834,12 +1834,12 @@
<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>The following information is available in the <code>Config_Reference.md#bed_screws</code> object:</p>
<p><code>Config_Reference.md#bed_screws</code> 对象中提供了以下信息:</p>
<ul>
<li><code>is_active</code>: Returns True if the bed screws adjustment tool is currently active.</li>
<li><code>state</code>: The bed screws adjustment tool state. It is one of the following strings: "adjust", "fine".</li>
<li><code>current_screw</code>: The index for the current screw being adjusted.</li>
<li><code>accepted_screws</code>: The number of accepted screws.</li>
<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="configfile">configfile<a class="headerlink" href="#configfile" title="Permanent link">&para;</a></h2>
<p><code>configfile</code> 对象中提供了以下信息(该对象始终可用):</p>

File diff suppressed because one or more lines are too long

View File

@@ -2,252 +2,252 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-08-23</lastmod>
<lastmod>2022-08-24</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>

Binary file not shown.