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

2022-12-22 00:03:43 +00:00
parent 36606abf17
commit 8d550d64f4
51 changed files with 1568 additions and 417 deletions
--- a/zh-Hant/Config_Changes.html
+++ b/zh-Hant/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: It was previously possible to flash an rp2040 in bootloader mode by running <code>make flash FLASH_DEVICE=first</code>. The equivalent command is now <code>make flash FLASH_DEVICE=2e8a:0003</code>.</p>
 <p>20220612: The rp2040 micro-controller now has a workaround for the "rp2040-e5" USB errata. This should make initial USB connections more reliable. However, it may result in a change in behavior for the gpio15 pin. It is unlikely the gpio15 behavior change will be noticeable.</p>
 <p>20220407: The temperature_fan <code>pid_integral_max</code> config option has been removed (it was deprecated on 20210612).</p>
--- a/zh-Hant/Config_Reference.html
+++ b/zh-Hant/Config_Reference.html
@@ -4877,10 +4877,10 @@ 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:
-#   Default is 104 (0x68).
+#   Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
 #i2c_mcu:
 #i2c_bus:
 #i2c_speed: 400000
--- a/zh-Hant/Contact.html
+++ b/zh-Hant/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>
--- a/zh-Hant/Features.html
+++ b/zh-Hant/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>
--- a/zh-Hant/G-Codes.html
+++ b/zh-Hant/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 config section</a> 時，以下命令可用（另請參閱 <a href="Command_Templates.html">command templates guide</a>）。</p>
--- a/zh-Hant/Measuring_Resonances.html
+++ b/zh-Hant/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>採購 ADXL345 時，請注意有各種不同的 PCB 板設計和它們的不同克隆。確保電路板支持 SPI 模式（通過將 SDO 拉至 GND 來為 I2C 硬配置少數電路板），如果要連接到 5V 打印機 MCU，它有一個穩壓器和電平轉換器。</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>
--- a/zh-Hant/Releases.html
+++ b/zh-Hant/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>在20210929發佈，此版本的主要更新：</p>
 <ul>
--- a/zh-Hant/Status_Reference.html
+++ b/zh-Hant/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>
--- a/zh-Hant/_klipper3d/pycache/mkdocs_hooks.cpython-38.pyc
+++ b/zh-Hant/_klipper3d/pycache/mkdocs_hooks.cpython-38.pyc
--- a/zh-Hant/search/search_index.json
+++ b/zh-Hant/search/search_index.json
--- a/zh-Hant/sitemap.xml
+++ b/zh-Hant/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>
--- a/zh-Hant/sitemap.xml.gz
+++ b/zh-Hant/sitemap.xml.gz