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

zh/Config_Changes.html

@@ -1287,6 +1287,7 @@
 <p>本文档涵盖了软件更新中对配置文件不向后兼容的部分。在升级 Klipper 时，最好也查看一下这份文档。</p>
 <p>文档的所有日期都是大概时间。</p>
 <h2 id="_2">变更<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
+<p>20221122: Previously, with safe_z_home, it was possible that the z_hop after the g28 homing would go in the negative z direction. Now, a z_hop is performed after g28 only if it results in a positive hop, mirroring the behavior of the z_hop that occurs before the g28 homing.</p>
 <p>20220616：以前可以通过运行<code>make flash FLASH_DEVICE=first</code>在引导程序模式下刷写rp2040。新的等效命令是<code>make flash FLASH_DEVICE=2e8a:0003</code>。</p>
 <p>20220612: 实现了rp2040上"rp2040-e5"USB数据错误的一个解决办法。这应该使最初的 USB 连接更加可靠。然而，它可能会导致gpio15引脚的行为发生变化。gpio15的行为变化不太可能有明显影响。</p>
 <p>20220407：temperature_fan 配置分段中的 <code>pid_integral_max</code> 选项已被删除（在 20210612 时已弃用）。</p>

zh/Config_Reference.html

@@ -4832,17 +4832,17 @@ cs_pin:
 </code></pre></div>
 
 <h3 id="mpu9250">[mpu9250]<a class="headerlink" href="#mpu9250" title="Permanent link">&para;</a></h3>
-<p>Support for mpu9250 and mpu6050 accelerometers (one may define any number of sections with an "mpu9250" prefix).</p>
+<p>Support for MPU-9250, MPU-9255, MPU-9255, MPU-6050, and MPU-6500 accelerometers (one may define any number of sections with an "mpu9250" prefix).</p>
 <div class="highlight"><pre><span></span><code>[mpu9250 my_accelerometer]
 #i2c_address:
-#   默认为104 (0x68)。
+#   Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
 #i2c_mcu:
 #i2c_bus:
 #i2c_speed: 400000
-#   参见 &quot;常见的I2C设置 &quot;一节，了解关于上述参数的描述。
-#   默认的 &quot;i2c_speed &quot;是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
-#   参见 &quot;adxl345 &quot;部分关于这个参数的信息。
+#   See the &quot;adxl345&quot; section for information on this parameter.
 </code></pre></div>
 
 <h3 id="resonance_tester">[resonance_tester]<a class="headerlink" href="#resonance_tester" title="Permanent link">&para;</a></h3>

zh/Contact.html

@@ -431,17 +431,24 @@
 </li>
       
         <li class="md-nav__item">
-  <a href="#klipper_1" class="md-nav__link">
-    我在 Klipper 软件中诊断出了一个缺陷
+  <a href="#i-found-a-bug-in-the-klipper-software" class="md-nav__link">
+    I found a bug in the Klipper software
   </a>
   
 </li>
       
         <li class="md-nav__item">
-  <a href="#klipper_2" class="md-nav__link">
+  <a href="#klipper_1" class="md-nav__link">
     我正在进行一些我想添加到 Klipper 中的改进
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#klipper-github" class="md-nav__link">
+    Klipper github
+  </a>
+  
 </li>
       
     </ul>
@@ -1337,17 +1344,24 @@
 </li>
       
         <li class="md-nav__item">
-  <a href="#klipper_1" class="md-nav__link">
-    我在 Klipper 软件中诊断出了一个缺陷
+  <a href="#i-found-a-bug-in-the-klipper-software" class="md-nav__link">
+    I found a bug in the Klipper software
   </a>
   
 </li>
       
         <li class="md-nav__item">
-  <a href="#klipper_2" class="md-nav__link">
+  <a href="#klipper_1" class="md-nav__link">
     我正在进行一些我想添加到 Klipper 中的改进
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#klipper-github" class="md-nav__link">
+    Klipper github
+  </a>
+  
 </li>
       
     </ul>
@@ -1375,8 +1389,9 @@
 <li><a href="#i-have-a-question-about-klipper">我有一个关于 Klipper 的问题</a></li>
 <li><a href="#i-have-a-feature-request">我有一个功能请求</a></li>
 <li><a href="#help-it-doesnt-work">我需要帮助！它炸了！</a></li>
-<li><a href="#i-have-diagnosed-a-defect-in-the-klipper-software">我在 Klipper 中发现了一个缺陷</a></li>
+<li><a href="#i-found-a-bug-in-the-klipper-software">I found a bug in the Klipper software</a></li>
 <li><a href="#i-am-making-changes-that-id-like-to-include-in-klipper">我正在进行我想纳入 Klipper 的修改</a></li>
+<li><a href="#klipper-github">Klipper github</a></li>
 </ol>
 <h2 id="_2">社区论坛<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
 <p>有一个用来讨论 Klipper 的 <a href="https://community.klipper3d.org">Klipper 社区 Discourse 服务器</a>。</p>
@@ -1388,10 +1403,8 @@
 <p>也可以在<a href="#community-forum"> Klipper 社区论坛</a>中搜索类似的问题。</p>
 <p>如果你有兴趣与其他 Klipper 用户分享你的知识和经验，那么你可以加入<a href="#community-forum"> Klipper 社区论坛</a>或<a href="#discord-chat"> Klipper Discord 聊天室</a>。这两个社区都是 Klipper 用户间讨论 Klipper 的地方。</p>
 <p>我们经常收到许多并不针对 Klipper 的常规3D打印疑问。如果你有常规的疑问或遇到了常规的打印问题，那么你可能会在一般的3D打印论坛或专门针对你的打印机硬件的论坛上得到更好的答案。</p>
-<p>不要在 Klipper 的 Github 上创建议题来提问。</p>
 <h2 id="_3">我有一个功能请求<a class="headerlink" href="#_3" title="Permanent link">&para;</a></h2>
 <p>所有的新功能都需要有感兴趣并能够实现这些功能的人。如果你想帮助实现或测试一个新功能，你可以在<a href="#community-forum"> Klipper 社区论坛</a>中搜索正在进行的开发进程。还有<a href="#discord-chat">Klipper Discord 聊天室</a>供合作者之间讨论。</p>
-<p>不要在 Klipper 的 Github 上创建议题来请求功能。</p>
 <h2 id="_4">我需要帮助！它炸了！<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>
 <p>不幸的是，我们收到的帮助请求往往比我们能够回答的要多。我们发现大多数问题报告的根本原因都是：</p>
 <ol>
@@ -1402,34 +1415,29 @@
 <p>如果你遇到了打印问题，我们建议仔细检查打印机的硬件（所有接头、电线、螺丝等），确认没有任何异常。我们发现大多数打印问题都与 Klipper 软件无关。如果你确实发现了打印机硬件的问题，在一般的3D打印论坛或专门针对你的打印机硬件的论坛上搜索通常可以得到更好的答复。</p>
 <p>也可以在<a href="#community-forum"> Klipper 社区论坛</a>中查找类似的问题。</p>
 <p>如果你有兴趣与其他 Klipper 用户分享你的知识和经验，那么你可以加入<a href="#community-forum"> Klipper 社区论坛</a>或<a href="#discord-chat"> Klipper Discord 聊天室</a>。这两个社区都是 Klipper 用户间讨论 Klipper 的地方。</p>
-<p>不要在 Klipper 的 Github 上创建议题来求助。</p>
-<h2 id="klipper_1">我在 Klipper 软件中诊断出了一个缺陷<a class="headerlink" href="#klipper_1" title="Permanent link">&para;</a></h2>
+<h2 id="i-found-a-bug-in-the-klipper-software">I found a bug in the Klipper software<a class="headerlink" href="#i-found-a-bug-in-the-klipper-software" title="Permanent link">&para;</a></h2>
 <p>Klipper 是一个开源项目，我们诚挚的感谢贡献者们在软件中诊断出错误。</p>
+<p>Problems should be reported in the <a href="#community-forum">Klipper Community Forum</a>.</p>
 <p>修复bug需要提供一些重要的信息。请遵循以下步骤：</p>
 <ol>
-<li>首先要确定这个错误是在 Klipper 软件中。如果你在想 "我有一个问题，我无法找出原因，因此这是一个Klipper的错误"，那么<strong>不要</strong>创建一个 Github 议题。在这种情况下，有兴趣且有能力的人需要先找到问题的根源。如果你想分享你的研究结果或检查其他用户是否遇到类似的问题，那么你可以搜索 <a href="#community-forum">Klipper 社区论坛</a>。</li>
-<li>请确保您正在运行 <a href="https://github.com/Klipper3d/klipper ">https://github.com/Klipper3d/klipper </a> 的未修改代码。如果代码已被修改或从其他来源获得，则您需要在报告问题之前先在 <a href="https://github.com/Klipper3d/klipper ">https://github.com/Klipper3d/klipper </a> 获取的未修改的代码上重现问题。</li>
-<li>如果可能的话，在不期望的事件发生后，立即在 OctoPrint 终端窗口运行一个<code>M112</code>命令。这将使 Klipper 进入 "关闭"(shutdown)状态，并在日志文件中写入额外的调试信息。</li>
-<li>
-<p>获取事件发送时的 Klipper 日志文件。该日志文件已被设计用来给 Klipper 开发人员提供关于软件及其运行环境的常见问题（软件版本、硬件类型、配置、事件时间和数百个其他问题）。</p>
-<ol>
+<li>Make sure you are running unmodified code from <a href="https://github.com/Klipper3d/klipper">https://github.com/Klipper3d/klipper</a>. If the code has been modified or is obtained from another source, then you should reproduce the problem on the unmodified code from <a href="https://github.com/Klipper3d/klipper">https://github.com/Klipper3d/klipper</a> prior to reporting.</li>
+<li>If possible, run an <code>M112</code> command immediately after the undesirable event occurs. This causes Klipper to go into a "shutdown state" and it will cause additional debugging information to be written to the log file.</li>
+<li>获取事件发送时的 Klipper 日志文件。该日志文件已被设计用来给 Klipper 开发人员提供关于软件及其运行环境的常见问题（软件版本、硬件类型、配置、事件时间和数百个其他问题）。<ol>
 <li>Klipper 日志文件位于 Klipper "主机"（树莓派）的<code>/tmp/klippy.log</code>文件中。</li>
 <li>你需要用“scp”或“sftp”程序将此日志文件复制到您的计算机。 “scp”程序是 Linux 和 MacOS 系统的标准配置。其他系统也通常有可用的 scp 实用程序（例如 WinSCP）。如果使用图形界面的 scp 程序无法直接复制 <code>/tmp/klippy.log</code>，可以尝试重复点击 <code>..</code>或者<code>parent folder</code>（父文件夹）直到进入根目录，再点击<code>tmp</code>文件夹，然后选择<code>klippy.log</code>文件。</li>
 <li>将日志文件复制到你的电脑，以便将其上传到问题报告中。</li>
 <li>不要以任何方式修改日志文件；不要只提供日志的片段。只有完整的未修改的日志文件才能够提供必要的信息。</li>
-<li>
-<p>如果日志文件非常大（例如，大于2MB），那么可能需要用 zip 或 gzip 来压缩日志。</p>
-</li>
-<li>
-<p>在 <a href="https://github.com/Klipper3d/klipper/issues">https://github.com/Klipper3d/klipper/issues</a>开一个新的GitHub议题，并对问题进行清晰的描述。Klipper 开发者需要了解你采取了哪些步骤，期望的结果是什么，以及实际发生了什么结果。Klipper 的日志文件<strong>必须被添加到议题附件</strong>：<img alt="议题附件" src="img/attach-issue.png" /></p>
-</li>
+<li>It is a good idea to compress the log file with zip or gzip.</li>
 </ol>
 </li>
+<li>Open a new topic on the <a href="#community-forum">Klipper Community Forum</a> and provide a clear description of the problem. Other Klipper contributors will need to understand what steps were taken, what the desired outcome was, and what outcome actually occurred. The compressed Klipper log file should be attached to that topic.</li>
 </ol>
-<h2 id="klipper_2">我正在进行一些我想添加到 Klipper 中的改进<a class="headerlink" href="#klipper_2" title="Permanent link">&para;</a></h2>
+<h2 id="klipper_1">我正在进行一些我想添加到 Klipper 中的改进<a class="headerlink" href="#klipper_1" 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>上提问。如果你想提供你目前的进展情况，那么你可以在 Github 上开一个问题，写上你的代码的位置，修改的概述，以及对其目前状态的描述。</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="#community-forum">Klipper Community Forum</a> or on the <a href="#discord-chat">Klipper Community Discord</a>.</p>
+<h2 id="klipper-github">Klipper github<a class="headerlink" href="#klipper-github" title="Permanent link">&para;</a></h2>
+<p>Klipper github may be used by contributors to share the status of their work to improve Klipper. It is expected that the person opening a github ticket is actively working on the given task and will be the one performing all the work necessary to accomplish it. The Klipper github is not used for requests, nor to report bugs, nor to ask questions. Use the <a href="#community-forum">Klipper Community Forum</a> or the <a href="#discord-chat">Klipper Community Discord</a> instead.</p>
 
               
             </article>

zh/Features.html

@@ -1300,13 +1300,14 @@
 <h1 id="_1">功能<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h1>
 <p>Klipper 有几个引人注目的功能：</p>
 <ul>
-<li>高精度步进运动。Klipper使用一个应用处理器（例如低成本的树莓派）来计算打印机运动。应用处理器决定何时对每个步进电机发出步进信号，压缩这些事件，并将它们发送到微控制器。微处理器将会把每个事件按请求时间执行。每一个步进事件被以25毫秒或更高的精度安排。软件不进行运动估计，例如 Bresenham算法，而是通过加速度与机械运动物理计算精确的步进时间。更精准的步进电机运动意味着打印机更安静和稳定的运行。</li>
+<li>High precision stepper movement. Klipper utilizes an application processor (such as a low-cost Raspberry Pi) when calculating printer movements. The application processor determines when to step each stepper motor, it compresses those events, transmits them to the micro-controller, and then the micro-controller executes each event at the requested time. Each stepper event is scheduled with a precision of 25 micro-seconds or better. The software does not use kinematic estimations (such as the Bresenham algorithm) - instead it calculates precise step times based on the physics of acceleration and the physics of the machine kinematics. More precise stepper movement provides quieter and more stable printer operation.</li>
 <li>同类项目中最佳的性能。 Klipper 能够在新旧微控制器上实现高步进速率。即使是旧的 8 位微控制器也可以发送超过每秒 175K 步的速率。在较新的微控制器上，每秒数百万步也可以实现。更高的步进速率可以实现更高的打印速度。步进事件计时即使在高速下也能保持精确，提高了整体稳定性。</li>
 <li>Klipper 支持带有多个微控制器的打印机。例如，一个微控制器可以被用来控制挤出机，而另一个用来控制加热器，并使用第三个来控制其他的打印机组件。Klipper 主机程序实现了时钟同步，解决了微处理器之间的时钟漂移。 启用多个控制器只需要在配置文件中添加几行，不需要任何特殊代码。</li>
 <li>通过简单的配置文件进行配置。修改设置不需要重新刷写微控制器。Klipper 的所有配置都被存储在一个易编辑的配置文件中，大大减少了配置与维护硬件的难度。</li>
 <li>Klipper 支持“平滑提前压力”--一种考虑了挤出机内压力影响的机制。这项技术可以减少喷嘴溢料并改善转角的打印质量。Klipper 的实现不会引入瞬间挤出机速度变化，改善了整体稳定性和稳健性。</li>
 <li>支持使用“输入整形”来减少振动对打印质量的影响。这项功能可以减少或消除打印件的“振纹(ringing)”（又名“ghosting”，“echoing”，或“rippling”）。在一些情况下它可以在保持打印质量的同时提高打印速度。</li>
 <li>Klipper 使用“迭代求解器”从简单的运动学方程中计算精准的步进时间。这降低了移植Klipper到新的机械结构的难度并保证了精确的步进计时（而不需要“线段化”）。</li>
+<li>Klipper is hardware agnostic. One should get the same precise timing independent of the low-level electronics hardware. The Klipper micro-controller code is designed to faithfully follow the schedule provided by the Klipper host software (or prominently alert the user if it is unable to). This makes it easier to use available hardware, to upgrade to new hardware, and to have confidence in the hardware.</li>
 <li>易移植的代码。Klipper 可以在 ARM，AVR，和PRU架构的微控制器上运行。现有的“reprap”类打印机不需要改动任何硬件就可以运行 Klipper，只需要加一个树莓派。Klipper 的内部代码结构使它能够被简单的移植到其他架构。</li>
 <li>简洁的代码。大部分 Klipper 代码使用一个极高级编程语言（Python），这包括了运动算法，G代码解析，加热，温度传感器算法和其他，降低了开发新功能的难度。</li>
 <li>自定义可编程脚本。可以在打印机配置文件中定义新的G代码命令（而不需要修改任何代码）。这些命令都是可编程的，可以能根据打印机的状态做出不同的响应。</li>
@@ -1315,21 +1316,22 @@
 <h2 id="_2">其他功能<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
 <p>Klipper 支持许多标准的 3d 打印机功能：</p>
 <ul>
-<li>兼容Octoprint。这使得打印机可以通过普通浏览器来控制。运行Klipper的树莓派可以同时用来运行Octoprint。</li>
+<li>Several web interfaces available. Works with Mainsail, Fluidd, OctoPrint and others. This allows the printer to be controlled using a regular web-browser. The same Raspberry Pi that runs Klipper can also run the web interface.</li>
 <li>标准 G 代码支持。支持由常见“切片软件”（SuperSlicer、Cura、PrusaSlicer 等）生成的通用 G 代码命令。</li>
 <li>支持多挤出机。包括对共享热端的挤出机（多进一出）和多头（IDEX）的支持。</li>
-<li>支持笛卡尔、三角洲、CoreXY、CoreXZ、混合CoreXY、混合CoreXZ、旋转三角洲、极坐标和缆绳铰盘式打印机。</li>
+<li>Support for cartesian, delta, corexy, corexz, hybrid-corexy, hybrid-corexz, deltesian, rotary delta, polar, and cable winch style printers.</li>
 <li>自动床面平整支持。Klipper可以被配置为基本的床身倾斜检测或网床调平。如果床铺使用多个Z步进器，那么Klipper也可以通过独立操纵Z步进器来调平。支持大多数Z高度探头，包括BL-Touch探头和伺服激活的探头。</li>
 <li>支持自动delta校准。校准工具可以进行基本的高度校准，以及增强的X和Y尺寸校准。校准可以用Z型高度探头或通过手动探测来完成。</li>
+<li>Run-time "exclude object" support. When configured, this module may facilitate canceling of just one object in a multi-part print.</li>
 <li>支持常见的温度传感器（例如，常见的热敏电阻、AD595、AD597、AD849x、PT100、PT1000、MAX6675、MAX31855、MAX31856、MAX31865、BME280、HTU21D、DS18B20和LM75）。还可以配置自定义热敏电阻和自定义模拟温度传感器。还可以监测微控制器和 Raspberry Pi 内部的温度传感器。</li>
 <li>默认启用基本加热器保护。</li>
 <li>支持标准风扇、喷嘴风扇和温控风扇。不需要在打印机闲置时保持风扇运转。可以在带有转速表的风扇上监测风扇速度。</li>
-<li>支持TMC2130、TMC2208/TMC2224、TMC2209、TMC2660和TMC5160步进电机驱动器的运行时配置。还支持通过AD5206、MCP4451、MCP4728、MCP4018和PWM引脚对传统步进驱动器进行电流控制。</li>
+<li>Support for run-time configuration of TMC2130, TMC2208/TMC2224, TMC2209, TMC2660, and TMC5160 stepper motor drivers. There is also support for current control of traditional stepper drivers via AD5206, DAC084S085, MCP4451, MCP4728, MCP4018, and PWM pins.</li>
 <li>支持直接连接到打印机的普通LCD显示器。还提供了一个默认的菜单。显示器和菜单的内容可以通过配置文件完全定制。</li>
 <li>恒定加速和“look-ahead”（前瞻）支持。所有打印机移动将从静止逐渐加速到巡航速度，然后减速回到静止。对传入的 G 代码移动命令流进行排队和分析 - 将优化类似方向上的移动之间的加速度，以减少打印停顿并改善整体打印时间。</li>
 <li>Klipper 实现了一种“步进相位限位”算法，可以提高典型限位开关的精度。如果调整得当，它可以提高打印件首层和打印床的附着力。</li>
 <li>支持打印丝存在传感器、打印丝运动传感器和打印丝宽度传感器。</li>
-<li>支持使用 adxl345 加速度计测量和记录加速度。</li>
+<li>Support for measuring and recording acceleration using an adxl345, mpu9250, and mpu6050 accelerometers.</li>
 <li>支持限制短距离“之”字形移动的最高速度，以减少打印机的振动和噪音。更多信息见<a href="Kinematics.html">运动学</a>文档。</li>
 <li>许多常见的打印机都有样本配置文件。查看<a href="https://github.com/Klipper3d/klipper/blob/master/config/">配置文件夹</a>中的列表。</li>
 </ul>

zh/G-Codes.html

@@ -4556,7 +4556,8 @@
 <h3 id="gcode_arcs">[gcode_arcs]<a class="headerlink" href="#gcode_arcs" title="Permanent link">&para;</a></h3>
 <p>如果启用了<a href="Config_Reference.html#gcode_arcs">gcode_arcs 配置分段</a>，下列标准G代码命令可用：</p>
 <ul>
-<li>受控弧线移动（G2或G3）。<code>G2 [X&lt;pos&gt;] [Y&lt;pos&gt;] [Z&lt;pos&gt;] [E&lt;pos&gt;] [F&lt;speed&gt;] I&lt;value&gt; J&lt;value&gt;</code> 。</li>
+<li>Arc Move Clockwise (G2), Arc Move Counter-clockwise (G3): <code>G2|G3 [X&lt;pos&gt;] [Y&lt;pos&gt;] [Z&lt;pos&gt;] [E&lt;pos&gt;] [F&lt;speed&gt;] I&lt;value&gt; J&lt;value&gt;|I&lt;value&gt; K&lt;value&gt;|J&lt;value&gt; K&lt;value&gt;</code></li>
+<li>Arc Plane Select: G17 (XY plane), G18 (XZ plane), G19 (YZ plane)</li>
 </ul>
 <h3 id="gcode_macro">[gcode_macro]<a class="headerlink" href="#gcode_macro" title="Permanent link">&para;</a></h3>
 <p>当<a href="Config_Reference.html#gcode_macro">gcode_macro配置分段</a>被启用时，以下命令可用（也可参见<a href="Command_Templates.html">命令模板指南</a>）：</p>

zh/Measuring_Resonances.html

@@ -713,6 +713,52 @@
     接线
   </a>
   
+    <nav class="md-nav" aria-label="接线">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#spi-accelerometers" class="md-nav__link">
+    SPI Accelerometers
+  </a>
+  
+    <nav class="md-nav" aria-label="SPI Accelerometers">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#adxl345" class="md-nav__link">
+    ADXL345
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#i2c-accelerometers" class="md-nav__link">
+    I2C Accelerometers
+  </a>
+  
+    <nav class="md-nav" aria-label="I2C Accelerometers">
+      <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>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
           <li class="md-nav__item">
@@ -727,6 +773,33 @@
     软件设置
   </a>
   
+    <nav class="md-nav" aria-label="软件设置">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#configure-adxl345-with-rpi" class="md-nav__link">
+    Configure ADXL345 With RPi
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#configure-mpu-60009000-series-with-rpi" class="md-nav__link">
+    Configure MPU-6000/9000 series With RPi
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#configure-mpu-60009000-series-with-pico" class="md-nav__link">
+    Configure MPU-6000/9000 series With PICO
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
       </ul>
@@ -1385,6 +1458,52 @@
     接线
   </a>
   
+    <nav class="md-nav" aria-label="接线">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#spi-accelerometers" class="md-nav__link">
+    SPI Accelerometers
+  </a>
+  
+    <nav class="md-nav" aria-label="SPI Accelerometers">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#adxl345" class="md-nav__link">
+    ADXL345
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#i2c-accelerometers" class="md-nav__link">
+    I2C Accelerometers
+  </a>
+  
+    <nav class="md-nav" aria-label="I2C Accelerometers">
+      <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>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
           <li class="md-nav__item">
@@ -1399,6 +1518,33 @@
     软件设置
   </a>
   
+    <nav class="md-nav" aria-label="软件设置">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#configure-adxl345-with-rpi" class="md-nav__link">
+    Configure ADXL345 With RPi
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#configure-mpu-60009000-series-with-rpi" class="md-nav__link">
+    Configure MPU-6000/9000 series With RPi
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#configure-mpu-60009000-series-with-pico" class="md-nav__link">
+    Configure MPU-6000/9000 series With PICO
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
       </ul>
@@ -1510,6 +1656,18 @@
 <p>When sourcing ADXL345, be aware that there is a variety of different PCB board designs and different clones of them. Make sure that the board supports SPI mode (small number of boards appear to be hard-configured for I2C by pulling SDO to GND), and, if it is going to be connected to a 5V printer MCU, that it has a voltage regulator and a level shifter.</p>
 <h2 id="_2">安装指南<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
 <h3 id="_3">接线<a class="headerlink" href="#_3" title="Permanent link">&para;</a></h3>
+<p>An ethernet cable with shielded twisted pairs (cat5e or better) is recommended for signal integrety over a long distance. If you still experience signal integrity issues (SPI/I2C errors), shorten the cable.</p>
+<p>Connect ethernet cable shielding to the controller board/RPI ground.</p>
+<p><strong><em>Double-check your wiring before powering up to prevent damaging your MCU/Raspberry Pi or the accelerometer.</em></strong></p>
+<h4 id="spi-accelerometers">SPI Accelerometers<a class="headerlink" href="#spi-accelerometers" title="Permanent link">&para;</a></h4>
+<p>Suggested twisted pair order:</p>
+<div class="highlight"><pre><span></span><code>GND+MISO
+3.3V+MOSI
+SCLK+CS
+</code></pre></div>
+
+<h5 id="adxl345">ADXL345<a class="headerlink" href="#adxl345" title="Permanent link">&para;</a></h5>
+<p><strong>Note: Many MCUs will work with an ADXL345 in SPI mode(eg Pi Pico), wiring and configuration will vary according to your specific board and avaliable pins.</strong></p>
 <p>我们需要将ADXL345连接到树莓派的SPI接口。注意，尽管ADXL345文档推荐使用I2C，但其数据吞吐能力不足，<strong>不能</strong>实现共振测量的要求。推荐的接线图为：</p>
 <table>
 <thead>
@@ -1552,7 +1710,17 @@
 </tr>
 </tbody>
 </table>
-<p>An alternative to the ADXL345 is the MPU-9250 (or MPU-6050). This accelerometer has been tested to work over I2C on the RPi at 400kbaud. Recommended connection scheme for I2C:</p>
+<p>部分ADXL345开发板的Fritzing接线图如下：</p>
+<p><img alt="ADXL345-树莓派" src="img/adxl345-fritzing.png" /></p>
+<h4 id="i2c-accelerometers">I2C Accelerometers<a class="headerlink" href="#i2c-accelerometers" title="Permanent link">&para;</a></h4>
+<p>Suggested twisted pair order:</p>
+<div class="highlight"><pre><span></span><code>3.3V+SDA
+GND+SCL
+</code></pre></div>
+
+<h5 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></h5>
+<p>Alternatives to the ADXL345 are MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500. These accelerometers have been tested to work over I2C on the RPi or RP2040(pico) at 400kbaud.</p>
+<p>Recommended connection scheme for I2C on the Raspberry Pi:</p>
 <table>
 <thead>
 <tr>
@@ -1563,7 +1731,7 @@
 </thead>
 <tbody>
 <tr>
-<td align="center">3V3 或 VCC</td>
+<td align="center">VCC</td>
 <td align="center">01</td>
 <td align="center">3.3v 直流（DC）电源</td>
 </tr>
@@ -1584,9 +1752,40 @@
 </tr>
 </tbody>
 </table>
-<p>部分ADXL345开发板的Fritzing接线图如下：</p>
-<p><img alt="ADXL345-树莓派" src="img/adxl345-fritzing.png" /></p>
-<p>为避免损坏树莓派或者加速度传感器，请检测接线正确再对树莓派上电。</p>
+<p><img alt="MPU-9250 connected to RPI" src="img/mpu9250-PI-fritzing.png" /></p>
+<p>Recommended connection scheme for I2C(i2c0a) on the RP2040:</p>
+<table>
+<thead>
+<tr>
+<th align="center">MPU-9250 pin</th>
+<th align="center">RP2040 pin</th>
+<th align="center">树莓派引脚名称</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td align="center">VCC</td>
+<td align="center">39</td>
+<td align="center">3v3</td>
+</tr>
+<tr>
+<td align="center">GND</td>
+<td align="center">38</td>
+<td align="center">地（GND）</td>
+</tr>
+<tr>
+<td align="center">SDA</td>
+<td align="center">01</td>
+<td align="center">GP0 (I2C0 SDA)</td>
+</tr>
+<tr>
+<td align="center">SCL</td>
+<td align="center">02</td>
+<td align="center">GP1 (I2C0 SCL)</td>
+</tr>
+</tbody>
+</table>
+<p><img alt="MPU-9250 connected to PICO" src="img/mpu9250-PICO-fritzing.png" /></p>
 <h3 id="_4">固定加速度传感器<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h3>
 <p>加速度传感器应固定在打印头上。应根据打印机的情况设计合适的固定件。推荐将加速度的测量轴与打印机运行轴的方向进行对齐。然而，如果轴对齐极其麻烦，可以将打印机的轴使用其他测量轴对齐，比如打印机+X对应传感器-X，甚至打印机+X对应传感器-Z等。</p>
 <p>下面是ADXL345固定到SmartEffector的示例：</p>
@@ -1605,8 +1804,9 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev
 
 <p>Note that, depending on the performance of the CPU, it may take <em>a lot</em> of time, up to 10-20 minutes. Be patient and wait for the completion of the installation. On some occasions, if the board has too little RAM the installation may fail and you will need to enable swap.</p>
 <p>之后，参考<a href="RPi_microcontroller.html">树莓派作为微控制器文档</a>的指引完成“LINUX微处理器”的设置。</p>
+<h4 id="configure-adxl345-with-rpi">Configure ADXL345 With RPi<a class="headerlink" href="#configure-adxl345-with-rpi" title="Permanent link">&para;</a></h4>
 <p>通过运行<code>sudo raspi-config</code> 后的 "Interfacing options"菜单中启用 SPI 以确保Linux SPI 驱动已启用。</p>
-<p>For the ADXL345, add the following to the printer.cfg file:</p>
+<p>在printer.cfg中添加以下内容：</p>
 <div class="highlight"><pre><span></span><code>[mcu rpi]
 serial: /tmp/klipper_host_mcu
 
@@ -1620,7 +1820,8 @@ probe_points:
 </code></pre></div>
 
 <p>建议在测试开始前，用探针在热床中央进行一次探测，触发后稍微上移。</p>
-<p>For the MPU-9250, make sure the Linux I2C driver is enabled and the baud rate is set to 400000 (see <a href="RPi_microcontroller.html#optional-enabling-i2c">Enabling I2C</a> section for more details). Then, add the following to the printer.cfg:</p>
+<h4 id="configure-mpu-60009000-series-with-rpi">Configure MPU-6000/9000 series With RPi<a class="headerlink" href="#configure-mpu-60009000-series-with-rpi" title="Permanent link">&para;</a></h4>
+<p>Make sure the Linux I2C driver is enabled and the baud rate is set to 400000 (see <a href="RPi_microcontroller.html#optional-enabling-i2c">Enabling I2C</a> section for more details). Then, add the following to the printer.cfg:</p>
 <div class="highlight"><pre><span></span><code>[mcu rpi]
 serial: /tmp/klipper_host_mcu
 
@@ -1634,6 +1835,24 @@ probe_points:
     100, 100, 20  # an example
 </code></pre></div>
 
+<h4 id="configure-mpu-60009000-series-with-pico">Configure MPU-6000/9000 series With PICO<a class="headerlink" href="#configure-mpu-60009000-series-with-pico" title="Permanent link">&para;</a></h4>
+<p>PICO I2C is set to 400000 on default. Simply add the following to the printer.cfg:</p>
+<div class="highlight"><pre><span></span><code>[mcu pico]
+serial: /dev/serial/by-id/&lt;your PICO&#39;s serial ID&gt;
+
+[mpu9250]
+i2c_mcu: pico
+i2c_bus: i2c1a
+
+[resonance_tester]
+accel_chip: mpu9250
+probe_points:
+    100, 100, 20  # an example
+
+[static_digital_output pico_3V3pwm] # Improve power stability
+pin: pico:gpio23
+</code></pre></div>
+
 <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>
@@ -1647,6 +1866,7 @@ probe_points:
 </code></pre></div>
 
 <p>如果输出类似 <code>Invalid adxl345 id (got xx vs e5)</code>，其中'xx'为e5以外ID，这表示出现连接问题（如，连接错误、线缆电阻过大、干扰等），或传感器错误（如，残次传感器 或 错误的传感器）。请在此检查电源，接线（再三确定接线正确，没有破损、松动的电线）或焊接问题。</p>
+<p><strong>If you are using MPU-6000/9000 series accelerometer and it show up as <code>mpu-unknown</code>, use with caution! They are probably refurbished chips!</strong></p>
 <p>下一步，在Octoprint中输入 <code>MEASURE_AXES_NOISE</code>，之后将会显示各个轴的基准测量噪声（其值应在1-100之间）。如果轴的噪声极高（例如 1000 或更高）可能意味着3D打印机上存在传感器问题、电源问题或不平衡的风扇。</p>
 <h3 id="_8">测量共振值<a class="headerlink" href="#_8" title="Permanent link">&para;</a></h3>
 <p>现在可以运行进行实测。运行以下命令:</p>

zh/Releases.html

@@ -365,6 +365,13 @@
     </label>
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
       
+        <li class="md-nav__item">
+  <a href="#klipper-0110" class="md-nav__link">
+    Klipper 0.11.0
+  </a>
+  
+</li>
+      
         <li class="md-nav__item">
   <a href="#klipper-0100" class="md-nav__link">
     Klipper 0.10.0
@@ -1328,6 +1335,13 @@
     </label>
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
       
+        <li class="md-nav__item">
+  <a href="#klipper-0110" class="md-nav__link">
+    Klipper 0.11.0
+  </a>
+  
+</li>
+      
         <li class="md-nav__item">
   <a href="#klipper-0100" class="md-nav__link">
     Klipper 0.10.0
@@ -1423,6 +1437,20 @@
 
 <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-0110">Klipper 0.11.0<a class="headerlink" href="#klipper-0110" title="Permanent link">&para;</a></h2>
+<p>Available on 20221128. Major changes in this release:</p>
+<ul>
+<li>Trinamic stepper motor driver "step on both edges" optimization.</li>
+<li>Support for Python3. The Klipper host code will run with either Python2 or Python3.</li>
+<li>Enhanced CAN bus support. Support for CAN bus on rp2040, stm32g0, stm32h7, same51, and same54 chips. Support for "USB to CAN bus bridge" mode.</li>
+<li>Support for CanBoot bootloader.</li>
+<li>Support for mpu9250 and mpu6050 accelerometers.</li>
+<li>Improved error handling for max31856, max31855, max31865, and max6675 temperature sensors.</li>
+<li>It is now possible to configure LEDs to update during long running G-Code commands using LED "template" support.</li>
+<li>Several micro-controller improvements. New support for stm32h743, stm32h750, stm32l412, stm32g0b1, same70, same51, and same54 chips. Support for i2c reads on atsamd and stm32f0. Hardware pwm support on stm32. Linux mcu signal based event dispatch. New rp2040 support for "make flash", i2c, and rp2040-e5 USB errata.</li>
+<li>New modules added: angle, dac084S085, exclude_object, led, mpu9250, pca9632, smart_effector, z_thermal_adjust. New deltesian kinematics added. New dump_mcu tool added.</li>
+<li>几个错误的修复和代码的清理。</li>
+</ul>
 <h2 id="klipper-0100">Klipper 0.10.0<a class="headerlink" href="#klipper-0100" title="Permanent link">&para;</a></h2>
 <p>Available on 20210929. Major changes in this release:</p>
 <ul>

zh/Status_Reference.html

@@ -990,6 +990,13 @@
     query_endstops
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#screws_tilt_adjust" class="md-nav__link">
+    screws_tilt_adjust
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -1744,6 +1751,13 @@
     query_endstops
   </a>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#screws_tilt_adjust" class="md-nav__link">
+    screws_tilt_adjust
+  </a>
+  
 </li>
       
         <li class="md-nav__item">
@@ -2065,6 +2079,20 @@
 <ul>
 <li><code>last_query["&lt;限位&gt;"]</code>：如果在最后一次 QUERY_ENDSTOP 命令中，给定的 endstop 处于“触发”状态，则返回 True。注意，如果在宏中使用，由于模板扩展的顺序，QUERY_ENDSTOP 命令必须在包含这个引用的宏之前运行。</li>
 </ul>
+<h2 id="screws_tilt_adjust">screws_tilt_adjust<a class="headerlink" href="#screws_tilt_adjust" title="Permanent link">&para;</a></h2>
+<p>The following information is available in the <code>screws_tilt_adjust</code> object:</p>
+<ul>
+<li><code>error</code>: Returns True if the most recent <code>SCREWS_TILT_CALCULATE</code> command included the <code>MAX_DEVIATION</code> parameter and any of the probed screw points exceeded the specified <code>MAX_DEVIATION</code>.</li>
+<li><code>results</code>: A list of the probed screw locations. Each entry in the list will be a dictionary containing the following keys:<ul>
+<li><code>name</code>: The name of the screw as specified in the config file.</li>
+<li><code>x</code>: The X coordinate of the screw as specified in the config file.</li>
+<li><code>y</code>: The Y coordinate of the screw as specified in the config file.</li>
+<li><code>z</code>: The measured Z height of the screw location.</li>
+<li><code>sign</code>: A string specifying the direction to turn to screw for the necessary adjustment. Either "CW" for clockwise or "CCW" for counterclockwise. The base screw will not have a <code>sign</code> key.</li>
+<li><code>adjust</code>: The number of screw turns to adjust the screw, given in the format "HH:MM," where "HH" is the number of full screw turns and "MM" is the number of "minutes of a clock face" representing a partial screw turn. (E.g. "01:15" would mean to turn the screw one and a quarter revolutions.)</li>
+</ul>
+</li>
+</ul>
 <h2 id="servo">servo<a class="headerlink" href="#servo" title="Permanent link">&para;</a></h2>
 <p><a href="Config_Reference.html#servo">servo some_name</a> 对象提供了以下信息：</p>
 <ul>

zh/sitemap.xml

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