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

2024-02-22 00:03:57 +00:00
parent 4ce4b4ceec
commit 41c61d1cb4
75 changed files with 851 additions and 851 deletions
--- a/zh/CANBUS.html
+++ b/zh/CANBUS.html
@@ -623,7 +623,7 @@
  
    <li class="md-nav__item">
      <a href="Axis_Twist_Compensation.html" class="md-nav__link">
-        Axis Twist Compensation
+        轴扭曲补偿
      </a>
    </li>
  
@@ -1158,7 +1158,7 @@
  
    <li class="md-nav__item">
      <a href="Bootloader_Entry.html" class="md-nav__link">
-        Bootloader Entry
+        引导加载程序条目
      </a>
    </li>
  
@@ -1247,8 +1247,8 @@
 </li>
      
        <li class="md-nav__item">
-  <a href="#tips-for-troubleshooting" class="md-nav__link">
-    Tips for troubleshooting
+  <a href="#_4" class="md-nav__link">
+    故障排除提示
  </a>
  
 </li>
@@ -1269,7 +1269,7 @@
  
    <li class="md-nav__item">
      <a href="CANBUS_Troubleshooting.html" class="md-nav__link">
-        CANBUS Troubleshooting
+        CanBus故障排除
      </a>
    </li>
  
@@ -1394,8 +1394,8 @@
 </li>
      
        <li class="md-nav__item">
-  <a href="#tips-for-troubleshooting" class="md-nav__link">
-    Tips for troubleshooting
+  <a href="#_4" class="md-nav__link">
+    故障排除提示
  </a>
  
 </li>
@@ -1420,20 +1420,20 @@
 <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, SAME5x, and rp2040 chips. In addition, the micro-controller chip must be on a board that has a CAN transceiver.</p>
+<p>Klipper目前支持STM32、SAME5x和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>In order to use a CAN bus, it is necessary to have a host adapter. It is recommended to use a "USB to CAN adapter". There are many different USB to CAN adapters available from different manufacturers. When choosing one, we recommend verifying that the firmware can be updated on it. (Unfortunately, we've found some USB adapters run defective firmware and are locked down, so verify before purchasing.) Look for adapters that can run Klipper directly (in its "USB to CAN bridge mode") or that run the <a href="https://github.com/candle-usb/candleLight_fw">candlelight firmware</a>.</p>
+<p>为了使用CAN总线，必须有一个主机适配器。建议使用“USB转CAN适配器”。不同的制造商提供了许多不同的USB转CAN适配器。在选择其中一个时，我们建议验证是否可以在其上更新固件。(不幸的是，我们发现一些USB适配器运行有缺陷的固件并被锁定，因此请在购买之前进行验证。)。寻找可以直接运行Klipper的适配器(在其“USB to CAN桥模式”下)或运行<a href="https://github.com/candle-usb/candleLight_fw">Candlellight firmware</a>.</p>
 <p>还需要将主机操作系统配置为使用适配器。通常可以通过创建一个名为 <code>/etc/network/interfaces.d/can0</code> 的新文件来实现，该文件包含以下内容：</p>
-<div class="highlight"><pre><span></span><code>allow-hotplug can0
-iface can0 can static
-    bitrate 1000000
-    up ifconfig $IFACE txqueuelen 128
+<div class="highlight"><pre><span></span><code>允许-热插拔can0。
+IFace can0可以静态。
+比特率1000000。
+Up ifconfig$iFace txqueelen 128
 </code></pre></div>

 <h2 id="_3">终端电阻<a class="headerlink" href="#_3" title="Permanent link">&para;</a></h2>
 <p>CAN总线在 CANH 和 CANL 导线之间必须两个 120 欧姆的电阻。理想情况下，总线的两端各有一个电阻。</p>
-<p>Note that some devices have a builtin 120 ohm resistor that can not be easily removed. Some devices do not include a resistor at all. Other devices have a mechanism to select the resistor (typically by connecting a "pin jumper"). Be sure to check the schematics of all devices on the CAN bus to verify that there are two and only two 120 Ohm resistors on the bus.</p>
+<p>请注意，有些器件内置了120欧姆的电阻，不易拆卸。有些器件根本不包括电阻器。其他设备具有选择电阻的机制(通常通过连接“引脚跳线”)。务必检查CAN总线上所有器件的原理图，以验证该总线上是否有且只有两个120欧姆电阻。</p>
 <p>要测试电阻是否正确，先切断打印机的电源，并用多用表检查 CANH 和 CANL 线之间的阻值—在正确接线的 CAN 总线上，它应该报告大约60 欧姆。</p>
 <h2 id="canbus_uuid">寻找新微控制器的 canbus_uuid<a class="headerlink" href="#canbus_uuid" title="Permanent link">&para;</a></h2>
 <p>CAN 总线上的每个微控制器都根据编码到每个微控制器中的工厂芯片标识符分配了一个唯一的 ID。要查找每个微控制器设备 ID，请确保硬件已正确供电和接线，然后运行：</p>
@@ -1453,30 +1453,30 @@ canbus_uuid: 11aa22bb33cc
 </code></pre></div>

 <h2 id="usbcan">USB转CAN总线桥接模式<a class="headerlink" href="#usbcan" title="Permanent link">&para;</a></h2>
-<p>Some micro-controllers support selecting "USB to CAN bus bridge" mode during Klipper's "make menuconfig". This mode may allow one to use a micro-controller as both a "USB to CAN bus adapter" and as a Klipper node.</p>
-<p>When Klipper uses this mode the micro-controller appears as a "USB CAN bus adapter" under Linux. The "Klipper bridge mcu" itself will appear as if it was on this CAN bus - it can be identified via <code>canbus_query.py</code> and it must be configured like other CAN bus Klipper nodes.</p>
+<p>有些微控制器支持在Klipper的“make menuconfig”模式下选择“USB转CAN Bus Bridge”模式。该模式可使微控制器既可用作“USB转CAN总线适配器”，又可用作Klipper节点。</p>
+<p>当Klipper使用此模式时，微控制器在Linux下显示为“USB CAN Bus Adapter”。“Klipper网桥MCU”本身看起来就像在此CAN总线上一样-它可以通过<code>canbus_query.py</code>识别，并且必须像其他CAN Bus Klipper节点一样进行配置。</p>
 <p>使用该模式时的一些重要注意事项：</p>
 <ul>
 <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 use <code>allow-hotplug</code> in the <code>/etc/network/interfaces.d/can0</code> file. For example:</li>
+<li>每当桥接MCU重置时，Linux都会关闭相应的<code>can0</code>接口。为了确保Firmware_Restart和Restart命令的正确处理，建议使用<code>/etc/network/interfaces.d/can0</code>文件中的<code>Allow-hotplug</code>。例如：</li>
 </ul>
-<div class="highlight"><pre><span></span><code>allow-hotplug can0
-iface can0 can static
-    bitrate 1000000
-    up ifconfig $IFACE txqueuelen 128
+<div class="highlight"><pre><span></span><code>允许-热插拔can0。
+IFace can0可以静态。
+比特率1000000。
+Up ifconfig$iFace txqueelen 128
 </code></pre></div>

 <ul>
 <li>
-<p>The "bridge mcu" is not actually on the CAN bus. Messages to and from the bridge mcu will not be seen by other adapters that may be on the CAN bus.</p>
+<p>“桥式MCU”实际上并不在CAN总线上。可能位于CAN总线上的其他适配器不会看到进出桥接器MCU的消息。</p>
 <ul>
-<li>The available bandwidth to both the "bridge mcu" itself and all devices on the CAN bus is effectively limited by the CAN bus frequency. As a result, it is recommended to use a CAN bus frequency of 1000000 when using "USB to CAN bus bridge mode".Even at a CAN bus frequency of 1000000, there may not be sufficient bandwidth to run a <code>SHAPER_CALIBRATE</code> test if both the XY steppers and the accelerometer all communicate via a single "USB to CAN bus" interface.</li>
-<li>A USB to CAN bridge board will not appear as a USB serial device, it will not show up when running <code>ls /dev/serial/by-id</code>, and it can not be configured in Klipper's printer.cfg file with a <code>serial:</code> parameter. The bridge board appears as a "USB CAN adapter" and it is configured in the printer.cfg as a <a href="#configuring-klipper">CAN node</a>.</li>
+<li>“桥式MCU”本身和CAN总线上的所有设备的可用带宽都受到CAN总线频率的有效限制。因此，在使用“USB转CAN总线桥模式”时，建议使用1000000的CAN总线频率。即使在CAN总线频率为1000000的情况下，如果XY步进器和加速度计都通过单个“USB to CAN Bus”接口进行通信，也可能没有足够的带宽来运行 <code>SHAPER_CALIBRATE</code> 测试。</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>
 </li>
 </ul>
-<h2 id="tips-for-troubleshooting">Tips for troubleshooting<a class="headerlink" href="#tips-for-troubleshooting" title="Permanent link">&para;</a></h2>
-<p>See the <a href="CANBUS_Troubleshooting.html">CAN bus troubleshooting</a> document.</p>
+<h2 id="_4">故障排除提示<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>
+<p>参见<a href="CanBus_Troublrouoting.md">CAN Bus故障排除</a>文档。</p>

              
            </article>
@@ -1495,7 +1495,7 @@ iface can0 can static
    <nav class="md-footer__inner md-grid" aria-label="页脚">
      
        
-        <a href="Bootloader_Entry.html" class="md-footer__link md-footer__link--prev" aria-label="上一页: Bootloader Entry" rel="prev">
+        <a href="Bootloader_Entry.html" class="md-footer__link md-footer__link--prev" aria-label="上一页: 引导加载程序条目" 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>
@@ -1504,20 +1504,20 @@ iface can0 can static
              <span class="md-footer__direction">
                上一页
              </span>
-              Bootloader Entry
+              引导加载程序条目
            </div>
          </div>
        </a>
      
      
        
-        <a href="CANBUS_Troubleshooting.html" class="md-footer__link md-footer__link--next" aria-label="下一页: CANBUS Troubleshooting" rel="next">
+        <a href="CANBUS_Troubleshooting.html" class="md-footer__link md-footer__link--next" aria-label="下一页: CanBus故障排除" rel="next">
          <div class="md-footer__title">
            <div class="md-ellipsis">
              <span class="md-footer__direction">
                下一页
              </span>
-              CANBUS Troubleshooting
+              CanBus故障排除
            </div>
          </div>
          <div class="md-footer__button md-icon">