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

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

Browse Source
This commit is contained in:
KevinOConnor
2022-06-27 00:03:35 +00:00
parent 633d167c75
commit 1c4d97e5ba
165 changed files with 5839 additions and 678 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
zh-Hant/404.html
View File

@@ -818,8 +818,8 @@
<li class="md-nav__item">
<a href="/Exclude_Object.md" class="md-nav__link">
None
<a href="/Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/API_Server.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/BLTouch.html
View File

@@ -917,8 +917,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Beaglebone.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Bed_Level.html
View File

@@ -882,8 +882,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Bed_Mesh.html
View File

@@ -984,8 +984,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Benchmarks.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Bootloaders.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/CANBUS.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/CANBUS_protocol.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/CONTRIBUTING.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

6
zh-Hant/Code_Overview.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1389,7 +1389,7 @@
<h2 id="_3">微處理器的程式碼流<a class="headerlink" href="#_3" title="Permanent link">&para;</a></h2>
<p>微控制器的程式碼從對應架構的程式碼(即<strong>src/avr/main.c</strong>)開始執行，前述程式碼會持續呼叫<strong>src/sched.c</strong>中的 sched_main() 函式。sched_main() 程式碼會先執行經 DECL_INIT() 宏標註的所有函式。之後它將不斷重複執行由 DECL_TASK() 宏所標註的函式。</p>
<p>其中一個主要的任務函式為<strong>src/command.c</strong> 中的command_dispatch()。上述函式經由微處理器特定的 輸入/輸出 程式碼呼叫(即<strong>src/avr/serial.c</strong>, <strong>src/generic/serial_irq.c</strong>)，並執行輸入流中的命令所對應的命令函式。命令函式通過 DECL_COMMAND() 宏進行定義 (詳情參照<a href="Protocol.html">協議</a> 文件)。</p>
<p>任務、初始化和命令函式總是在中斷啟用的情況下執行（然而，可根據需要將中斷功能停用）。這些函式不應出現暫停、延遲或執行持續事件長於數微秒的任務。這些函式應由排程定時器在特定的事件進行呼叫。</p>
<p>Task, init, and command functions always run with interrupts enabled (however, they can temporarily disable interrupts if needed). These functions should avoid long pauses, delays, or do work that lasts a significant time. (Long delays in these "task" functions result in scheduling jitter for other "tasks" - delays over 100us may become noticeable, delays over 500us may result in command retransmissions, delays over 100ms may result in watchdog reboots.) These functions schedule work at specific times by scheduling timers.</p>
<p>定時函式通過呼叫sched_add_timer() (即 <strong>src/sched.c</strong>)方法進行註冊。排程器會在設定的時間點對註冊的函式進行呼叫。定時器中斷會在微處理器架構特定的初始化處理器中處理(例如 <strong>src/avr/timer.c</strong>)，該程式碼會呼叫 <strong>src/sched.c</strong>中的sched_timer_dispatch()。通過定時器中斷執行註冊的定時函式。定時函式總在中斷禁用下執行。定時函式應總能在數微秒內完成。在定時函式結束時，該函式可對自身進行重新定時。</p>
<p>如果事件中拋出錯誤， 程式碼可呼叫shutdown()（<strong>src/sched.c</strong>中的sched_shutdown()）。呼叫shutdown()會導致所有標記為DECL_SHUTDOWN()宏的函式被執行。shutdown()總是在禁用中斷的情況下執行。</p>
<p>微控制器的大部分功能涉及到通用輸入輸出引腳（GPIO）的操作。爲了從高級任務程式碼中抽像出特定架構底層程式碼，所有的GPIO事件都在特定架構的包裝器中實現（如，<strong>src/avr/gpio.c</strong>）。程式碼使用gcc的"-flto -fwhole-program "來優化編譯，以實現行內函數的高效能交叉編譯，大多數微小的GPIO操作函式內聯到它們的呼叫器中，使用這些GPIO將沒有任何執行時成本。</p>

4
zh-Hant/Command_Templates.html
View File

@@ -958,8 +958,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

6
zh-Hant/Config_Changes.html
View File

@@ -864,8 +864,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1266,6 +1266,8 @@
<p>本文件涵蓋了軟體更新中對配置檔案不向后相容的部分。在升級 Klipper 時，最好也檢視一下這份文件。</p>
<p>本文件中的所有日期都是不精確的。</p>
<h2 id="_2">變更<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<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>
<p>20220407: The default color order for pca9632 LEDs is now "RGBW". Add an explicit <code>color_order: RBGW</code> setting to the pca9632 config section to obtain the previous behavior.</p>
<p>20220330: The format of the <code>printer.neopixel.color_data</code> status information for neopixel and dotstar modules has changed. The information is now stored as a list of color lists (instead of a list of dictionaries). See the <a href="Status_Reference.html#led">status reference</a> for details.</p>

90
zh-Hant/Config_Reference.html
View File

@@ -824,6 +824,13 @@
[respond]
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object" class="md-nav__link">
[exclude_object]
</a>
</li>
</ul>
@@ -851,6 +858,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#mpu9250" class="md-nav__link">
[mpu9250]
</a>
</li>
<li class="md-nav__item">
@@ -1978,8 +1992,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -2702,6 +2716,13 @@
[respond]
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object" class="md-nav__link">
[exclude_object]
</a>
</li>
</ul>
@@ -2729,6 +2750,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#mpu9250" class="md-nav__link">
[mpu9250]
</a>
</li>
<li class="md-nav__item">
@@ -4442,9 +4470,9 @@ home_xy_position:
# than z_hop, then this will lift the head to a height of z_hop. If
# the Z axis is not already homed the head is lifted by z_hop.
# The default is to not implement Z hop.
#z_hop_speed: 20.0
#z_hop_speed: 15.0
# Speed (in mm/s) at which the Z axis is lifted prior to homing. The
# default is 20mm/s.
# default is 15 mm/s.
#move_to_previous: False
# When set to True, the X and Y axes are reset to their previous
# positions after Z axis homing. The default is False.
@@ -4561,11 +4589,13 @@ filename:
<p>如果主機的速度不足以很好地執行 OctoPrint，虛擬 SD 卡可能有幫助。它允許 Klipper 主機軟體使用標準的 SD 卡G程式碼命令（例如，M24）直接列印儲存在主機目錄中的 gcode 檔案。</p>
<div class="highlight"><pre><span></span><code>[virtual_sdcard]
path:
# 要查找的主機本地目錄的路徑
# g 代碼文件。這是一個只讀目錄（sdcard 文件寫入
# 不支持）。有人可能會將此指向 OctoPrint 的上傳
# 目錄（通常是 ~/.octoprint/uploads/ ）。該參數必須
＃ 提供。
# The path of the local directory on the host machine to look for
# g-code files. This is a read-only directory (sdcard file writes
# are not supported). One may point this to OctoPrint&#39;s upload
# directory (generally ~/.octoprint/uploads/ ). This parameter must
# be provided.
#on_error_gcode:
# A list of G-Code commands to execute when an error is reported.
</code></pre></div>
<h3 id="sdcard_loop">[sdcard_loop]<a class="headerlink" href="#sdcard_loop" title="Permanent link">&para;</a></h3>
@@ -4633,6 +4663,12 @@ path:
# 覆蓋“default_type”。
</code></pre></div>
<h3 id="exclude_object">[exclude_object]<a class="headerlink" href="#exclude_object" title="Permanent link">&para;</a></h3>
<p>Enables support to exclude or cancel individual objects during the printing process.</p>
<p>See the <a href="Exclude_Object.html">exclude objects guide</a> and <a href="G-Codes.html#excludeobject">command reference</a> for additional information. See the <a href="https://github.com/Klipper3d/klipper/blob/master/config/sample-macros.cfg">sample-macros.cfg</a> file for a Marlin/RepRapFirmware compatible M486 G-Code macro.</p>
<div class="highlight"><pre><span></span><code>[exclude_object]
</code></pre></div>
<h2 id="_13">共振補償<a class="headerlink" href="#_13" title="Permanent link">&para;</a></h2>
<h3 id="input_shaper">[input_shaper]<a class="headerlink" href="#input_shaper" title="Permanent link">&para;</a></h3>
<p>啟用 <a href="Resonance_Compensation.html">resonance compensation</a>。另請參閱 <a href="G-Codes.html#input_shaper">命令參考</a>。</p>
@@ -4692,6 +4728,20 @@ 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>
<div class="highlight"><pre><span></span><code>[mpu9250 my_accelerometer]
#i2c_address:
# Default is 104 (0x68).
#i2c_mcu:
#i2c_bus:
#i2c_speed: 400000
# See the &quot;common I2C settings&quot; section for a description of the
# above parameters. The default &quot;i2c_speed&quot; is 400000.
#axes_map: x, y, z
# See the &quot;adxl345&quot; section for information on this parameter.
</code></pre></div>
<h3 id="resonance_tester">[resonance_tester]<a class="headerlink" href="#resonance_tester" title="Permanent link">&para;</a></h3>
<p>支持共振測試和自動輸入整形器校準。為了使用該模塊的大部分功能，必須安裝額外的軟件依賴項；有關詳細信息，請參閱 <a href="Measuring_Resonances.html">測量共振</a> 和 <a href="G-Codes.html#resonance_tester">命令參考</a>。有關 <code>max_smoothing</code> 參數及其使用的更多信息，請參閱測量共振指南的 <a href="Measuring_Resonances.html#max-smoothing">Max Smoothing</a> 部分。</p>
<div class="highlight"><pre><span></span><code>[resonance_tester]
@@ -6822,19 +6872,23 @@ cs_pin:
<h3 id="i2c">通用 I2C 設定<a class="headerlink" href="#i2c" title="Permanent link">&para;</a></h3>
<p>以下參數通常適用於使用 I2C 總線的設備。</p>
<p>Note that Klipper's current micro-controller support for i2c is generally not tolerant to line noise. Unexpected errors on the i2c wires may result in Klipper raising a run-time error. Klipper's support for error recovery varies between each micro-controller type. It is generally recommended to only use i2c devices that are on the same printed circuit board as the micro-controller.</p>
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000. The Klipper "linux" micro-controller supports a 400000 speed, but it must be <a href="RPi_microcontroller.html#optional-enabling-i2c">set in the operating system</a> and the <code>i2c_speed</code> parameter is otherwise ignored. The Klipper "rp2040" micro-controller supports a rate of 400000 via the <code>i2c_speed</code> parameter. All other Klipper micro-controllers use a 100000 rate and ignore the <code>i2c_speed</code> parameter.</p>
<div class="highlight"><pre><span></span><code>#i2c_address:
# 裝置的 I2C 地址。必須是一個十進制數字（而不是十六進制）。
# 預設值取決於裝置的型別。
# The i2c address of the device. This must specified as a decimal
# number (not in hex). The default depends on the type of device.
#i2c_mcu:
# 晶片所連線的微控制器的名稱。
# 預設為&quot;mcu&quot;。
# The name of the micro-controller that the chip is connected to.
# The default is &quot;mcu&quot;.
#i2c_bus:
# 如果微控制器支援多個 I2C 匯流排，可以指定微控制器的匯流排名稱。
# 預設值取決於微控制器的型別。
# If the micro-controller supports multiple I2C busses then one may
# specify the micro-controller bus name here. The default depends on
# the type of micro-controller.
#i2c_speed:
# 與裝置通訊時使用的I2C速度（Hz）。在某些微控制器上，
# 該數值無效。
# 預設值是預設為100000。
# The I2C speed (in Hz) to use when communicating with the device.
# The Klipper implementation on most micro-controllers is hard-coded
# to 100000 and changing this value has no effect. The default is
# 100000.
</code></pre></div>

4
zh-Hant/Config_checks.html
View File

@@ -922,8 +922,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Contact.html
View File

@@ -906,8 +906,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Debugging.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Delta_Calibrate.html
View File

@@ -902,8 +902,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Endstop_Phase.html
View File

@@ -881,8 +881,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Example_Configs.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

1435
zh-Hant/Exclude_Object.html Normal file
View File

File diff suppressed because it is too large Load Diff

4
zh-Hant/FAQ.html
View File

@@ -1025,8 +1025,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Features.html
View File

@@ -871,8 +871,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

119
zh-Hant/G-Codes.html
View File

@@ -1071,6 +1071,47 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#exclude_object" class="md-nav__link">
[exclude_object]
</a>
<nav class="md-nav" aria-label="[exclude_object]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#exclude_object_1" class="md-nav__link">
EXCLUDE_OBJECT
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object_define" class="md-nav__link">
EXCLUDE_OBJECT_DEFINE
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object_start" class="md-nav__link">
EXCLUDE_OBJECT_START
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object_end" class="md-nav__link">
EXCLUDE_OBJECT_END
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -2300,8 +2341,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -3018,6 +3059,47 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#exclude_object" class="md-nav__link">
[exclude_object]
</a>
<nav class="md-nav" aria-label="[exclude_object]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#exclude_object_1" class="md-nav__link">
EXCLUDE_OBJECT
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object_define" class="md-nav__link">
EXCLUDE_OBJECT_DEFINE
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object_start" class="md-nav__link">
EXCLUDE_OBJECT_START
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object_end" class="md-nav__link">
EXCLUDE_OBJECT_END
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4252,16 +4334,37 @@
<p>當啟用 <a href="Config_Reference.html#endstop_phase">endstop_phase config section</a> 時，以下命令可用（另請參閱 <a href="Endstop_Phase.html">endstop phase guide</a>）。</p>
<h4 id="endstop_phase_calibrate">ENDSTOP_PHASE_CALIBRATE<a class="headerlink" href="#endstop_phase_calibrate" title="Permanent link">&para;</a></h4>
<p><code>ENDSTOP_PHASE_CALIBRATE [STEPPER=&lt;config_name&gt;]</code> 。如果沒有提供STEPPER參數，那麼該命令將報告在過去的歸位操作中對端停步進相的統計。當提供STEPPER參數時，它會安排將給定的終點站相位設定寫入配置檔案中（與SAVE_CONFIG命令一起使用）。</p>
<h3 id="exclude_object">[exclude_object]<a class="headerlink" href="#exclude_object" title="Permanent link">&para;</a></h3>
<p>The following commands are available when an <a href="Config_Reference.html#exclude_object">exclude_object config section</a> is enabled (also see the <a href="Exclude_Object.html">exclude object guide</a>):</p>
<h4 id="exclude_object_1"><code>EXCLUDE_OBJECT</code><a class="headerlink" href="#exclude_object_1" title="Permanent link">&para;</a></h4>
<p><code>EXCLUDE_OBJECT [NAME=object_name] [CURRENT=1] [RESET=1]</code>: With no parameters, this will return a list of all currently excluded objects.</p>
<p>When the <code>NAME</code> parameter is given, the named object will be excluded from printing.</p>
<p>When the <code>CURRENT</code> parameter is given, the current object will be excluded from printing.</p>
<p>When the <code>RESET</code> parameter is given, the list of excluded objects will be cleared. Additionally including <code>NAME</code> will only reset the named object. This <strong>can</strong> cause print failures, if layers were already skipped.</p>
<h4 id="exclude_object_define"><code>EXCLUDE_OBJECT_DEFINE</code><a class="headerlink" href="#exclude_object_define" title="Permanent link">&para;</a></h4>
<p><code>EXCLUDE_OBJECT_DEFINE [NAME=object_name [CENTER=X,Y] [POLYGON=[[x,y],...]] [RESET=1] [JSON=1]</code>: Provides a summary of an object in the file.</p>
<p>With no parameters provided, this will list the defined objects known to Klipper. Returns a list of strings, unless the <code>JSON</code> parameter is given, when it will return object details in json format.</p>
<p>When the <code>NAME</code> parameter is included, this defines an object to be excluded.</p>
<ul>
<li><code>NAME</code>: This parameter is required. It is the identifier used by other commands in this module.</li>
<li><code>CENTER</code>: An X,Y coordinate for the object.</li>
<li><code>POLYGON</code>: An array of X,Y coordinates that provide an outline for the object.</li>
</ul>
<p>When the <code>RESET</code> parameter is provided, all defined objects will be cleared, and the <code>[exclude_object]</code> module will be reset.</p>
<h4 id="exclude_object_start"><code>EXCLUDE_OBJECT_START</code><a class="headerlink" href="#exclude_object_start" title="Permanent link">&para;</a></h4>
<p><code>EXCLUDE_OBJECT_START NAME=object_name</code>: This command takes a <code>NAME</code> parameter and denotes the start of the gcode for an object on the current layer.</p>
<h4 id="exclude_object_end"><code>EXCLUDE_OBJECT_END</code><a class="headerlink" href="#exclude_object_end" title="Permanent link">&para;</a></h4>
<p><code>EXCLUDE_OBJECT_END [NAME=object_name]</code>: Denotes the end of the object's gcode for the layer. It is paired with <code>EXCLUDE_OBJECT_START</code>. A <code>NAME</code> parameter is optional, and will only warn when the provided name does not match the current object.</p>
<h3 id="extruder">[extruder]<a class="headerlink" href="#extruder" title="Permanent link">&para;</a></h3>
<p>如果啟用了 <a href="Config_Reference.html#extruder">extruder config section</a>，則以下命令可用：</p>
<h4 id="activate_extruder">ACTIVATE_EXTRUDER<a class="headerlink" href="#activate_extruder" title="Permanent link">&para;</a></h4>
<p><code>ACTIVATE_EXTRUDER EXTRUDER=&lt;config_name&gt;</code>: In a printer with multiple <a href="Config_Reference.html#extruder">extruder</a> config sections, this command changes the active hotend.</p>
<h4 id="set_pressure_advance">SET_PRESSURE_ADVANCE<a class="headerlink" href="#set_pressure_advance" title="Permanent link">&para;</a></h4>
<p><code>SET_PRESSURE_ADVANCE [EXTRUDER=&lt;config_name&gt;] [ADVANCE=&lt;pressure_advance&gt;] [SMOOTH_TIME=&lt;pressure_advance_smooth_time&gt;]</code>: Set pressure advance parameters of an extruder stepper (as defined in an <a href="Config_Reference#extruder">extruder</a> or <a href="Config_Reference#extruder_stepper">extruder_stepper</a> config section). If EXTRUDER is not specified, it defaults to the stepper defined in the active hotend.</p>
<p><code>SET_PRESSURE_ADVANCE [EXTRUDER=&lt;config_name&gt;] [ADVANCE=&lt;pressure_advance&gt;] [SMOOTH_TIME=&lt;pressure_advance_smooth_time&gt;]</code>: Set pressure advance parameters of an extruder stepper (as defined in an <a href="Config_Reference.html#extruder">extruder</a> or <a href="Config_Reference.html#extruder_stepper">extruder_stepper</a> config section). If EXTRUDER is not specified, it defaults to the stepper defined in the active hotend.</p>
<h4 id="set_extruder_rotation_distance">SET_EXTRUDER_ROTATION_DISTANCE<a class="headerlink" href="#set_extruder_rotation_distance" title="Permanent link">&para;</a></h4>
<p><code>SET_EXTRUDER_ROTATION_DISTANCE EXTRUDER=&lt;config_name&gt; [DISTANCE=&lt;distance&gt;]</code>: Set a new value for the provided extruder stepper's "rotation distance" (as defined in an <a href="Config_Reference#extruder">extruder</a> or <a href="Config_Reference#extruder_stepper">extruder_stepper</a> config section). If the rotation distance is a negative number then the stepper motion will be inverted (relative to the stepper direction specified in the config file). Changed settings are not retained on Klipper reset. Use with caution as small changes can result in excessive pressure between extruder and hotend. Do proper calibration with filament before use. If 'DISTANCE' value is not provided then this command will return the current rotation distance.</p>
<p><code>SET_EXTRUDER_ROTATION_DISTANCE EXTRUDER=&lt;config_name&gt; [DISTANCE=&lt;distance&gt;]</code>: Set a new value for the provided extruder stepper's "rotation distance" (as defined in an <a href="Config_Reference.html#extruder">extruder</a> or <a href="Config_Reference.html#extruder_stepper">extruder_stepper</a> config section). If the rotation distance is a negative number then the stepper motion will be inverted (relative to the stepper direction specified in the config file). Changed settings are not retained on Klipper reset. Use with caution as small changes can result in excessive pressure between extruder and hotend. Do proper calibration with filament before use. If 'DISTANCE' value is not provided then this command will return the current rotation distance.</p>
<h4 id="sync_extruder_motion">SYNC_EXTRUDER_MOTION<a class="headerlink" href="#sync_extruder_motion" title="Permanent link">&para;</a></h4>
<p><code>SYNC_EXTRUDER_MOTION EXTRUDER=&lt;name&gt; MOTION_QUEUE=&lt;name&gt;</code>：此命令將導致由 EXTRUDER 指定的步進器（在 <a href="Config_Reference#extruder">extruder</a> 或 <a href="Config_Reference#extruder_stepper">extruder_stepper</a> 配置部分中定義）變為與 MOTION_QUEUE 指定的擠出機的運動同步（如 <a href="Config_Reference#extruder">extruder</a> 配置部分中定義的）。如果 MOTION_QUEUE 是一個空字符串，那麼步進器將與所有擠出機運動不同步。</p>
<p><code>SYNC_EXTRUDER_MOTION EXTRUDER=&lt;name&gt; MOTION_QUEUE=&lt;name&gt;</code>: This command will cause the stepper specified by EXTRUDER (as defined in an <a href="Config_Reference.html#extruder">extruder</a> or <a href="Config_Reference.html#extruder_stepper">extruder_stepper</a> config section) to become synchronized to the movement of an extruder specified by MOTION_QUEUE (as defined in an <a href="Config_Reference.html#extruder">extruder</a> config section). If MOTION_QUEUE is an empty string then the stepper will be desynchronized from all extruder movement.</p>
<h4 id="set_extruder_step_distance">SET_EXTRUDER_STEP_DISTANCE<a class="headerlink" href="#set_extruder_step_distance" title="Permanent link">&para;</a></h4>
<p>此命令已棄用，並將在不久的將來被刪除。</p>
<h4 id="sync_stepper_to_extruder">SYNC_STEPPER_TO_EXTRUDER<a class="headerlink" href="#sync_stepper_to_extruder" title="Permanent link">&para;</a></h4>
@@ -4288,7 +4391,7 @@
<h4 id="get_retraction">GET_RETRACTION<a class="headerlink" href="#get_retraction" title="Permanent link">&para;</a></h4>
<p><code>GET_RETRACTION</code>:查詢目前韌體回抽所使用的參數並在終端顯示。</p>
<h3 id="force_move">[force_move]<a class="headerlink" href="#force_move" title="Permanent link">&para;</a></h3>
<p>模組force_move已自動載入，但是某些命令需要在 <a href="Config_Reference#force_move">printer config</a> 中設置 <code>enable_force_move</code>。</p>
<p>The force_move module is automatically loaded, however some commands require setting <code>enable_force_move</code> in the <a href="Config_Reference.html#force_move">printer config</a>.</p>
<h4 id="stepper_buzz">STEPPER_BUZZ<a class="headerlink" href="#stepper_buzz" title="Permanent link">&para;</a></h4>
<p><code>STEPPER_BUZZ STEPPER=&lt;配置名&gt;</code>：移動指定的步進電機前後運動一毫米，重複的10次。這是一個用於驗證步進電機接線的工具.</p>
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">&para;</a></h4>
@@ -4442,7 +4545,7 @@
<h4 id="measure_axes_noise">MEASURE_AXES_NOISE<a class="headerlink" href="#measure_axes_noise" title="Permanent link">&para;</a></h4>
<p><code>MEASURE_AXES_NOISE</code>：測量並輸出所有啟用的加速度計晶片的所有軸的噪聲。</p>
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">&para;</a></h4>
<p><code>TEST_RESONANCES AXIS=&lt;axis&gt; OUTPUT=&lt;resonances,raw_data&gt; [NAME=&lt;name&gt;] [FREQ_START=&lt;min_freq&gt;] [FREQ_END=&lt;max_freq&gt;] [HZ_PER_SEC=&lt;hz_per_sec&gt;] [INPUT_SHAPING=[&lt;0:1 &gt;]]</code>：在請求的“軸”的所有配置探針點中運行共振測試，並使用為相應軸配置的加速度計芯片測量加速度。 "axis" 可以是 X 或 Y，或者指定任意方向為 <code>AXIS=dx,dy</code>，其中 dx 和 dy 是定義方向向量的浮點數（例如 <code>AXIS=X</code>、<code>AXIS=Y</code>、或 <code>AXIS=1,-1</code> 定義對角線方向）。請注意，<code>AXIS=dx,dy</code> 和 <code>AXIS=-dx,-dy</code> 是等價的。如果 <code>INPUT_SHAPING=0</code> 或未設置（默認），則禁用諧振測試的輸入整形，因為在啟用輸入整形器的情況下運行諧振測試是無效的。 <code>OUTPUT</code> 參數是以逗號分隔的列表，其中將寫入輸出。如果請求 <code>raw_data</code>，則將原始加速度計數據寫入一個文件或一系列文件 <code>/tmp/raw_data_&lt;axis&gt;_[&lt;point&gt;_]&lt;name&gt;.csv</code> 與 (<code>&lt;point&gt;_</code> 僅在配置超過 1 個探測點時生成的部分名稱）。如果指定了 <code>resonances</code>，則計算頻率響應（跨所有探測點）並寫入 <code>/tmp/resonances_&lt;axis&gt;_&lt;name&gt;.csv</code> 文件。如果未設置，則 OUTPUT 默認為“共振”，NAME 默認為“YYYYMMDD_HHMMSS”格式的當前時間。</p>
<p><code>TEST_RESONANCES AXIS=&lt;axis&gt; OUTPUT=&lt;resonances,raw_data&gt; [NAME=&lt;name&gt;] [FREQ_START=&lt;min_freq&gt;] [FREQ_END=&lt;max_freq&gt;] [HZ_PER_SEC=&lt;hz_per_sec&gt;] [CHIPS=&lt;adxl345_chip_name&gt;] [POINT=x,y,z] [INPUT_SHAPING=[&lt;0:1&gt;]]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>adxl345_chip_name</code> can be one or more configured adxl345 chip,delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. Note that <code>adxl345</code> can be omitted from named adxl345 chips. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_&lt;axis&gt;_[&lt;chip_name&gt;_][&lt;point&gt;_]&lt;name&gt;.csv</code> with (<code>&lt;point&gt;_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_&lt;axis&gt;_&lt;name&gt;.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
<h4 id="shaper_calibrate">SHAPER_CALIBRATE<a class="headerlink" href="#shaper_calibrate" title="Permanent link">&para;</a></h4>
<p><code>SHAPER_CALIBRATE [AXIS=&lt;軸&gt;] [NAME=&lt;名稱&gt;] [FREQ_START=&lt;最小頻率&gt;] [FREQ_END=&lt;最大頻率&gt;] [HZ_PER_SEC=&lt;hz_per_sec&gt;] [MAX_SMOOTHING=&lt;max_smoothing&gt;]</code>：類似<code>TEST_RESONANCES</code>，該命令按配置執行共振測試並嘗試尋找給定軸最佳的輸入整形參數。如果沒有選擇<code>AXIS</code>，則測量X和Y軸。如果沒有選擇 <code>MAX_SMOOTHING</code> ，會使用 <code>[resonance_tester]</code> 的預設參數。有關該特性的使用方法，詳見共振量測量指南中的 <a href="Measuring_Resonances.html#max-smoothing">最大平滑</a>章節。測試結果會被輸出到終端，而頻響和不同輸入整形器的參數將被寫入到一個或多個 CSV 檔案中。它們的名稱是<code>/tmp/calibration_data_&lt;軸&gt;_&lt;名稱&gt;.csv</code>。如果沒有指定，名稱預設為「YYYYMMDD_HHMMSS」格式的當前時間。注意，可以通過請求 <code>SAVE_CONFIG</code> 命令將推薦的輸入整形器參數直接儲存到配置檔案中。</p>
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">&para;</a></h3>
@@ -4466,7 +4569,7 @@
<h3 id="screws_tilt_adjust">[screws_tilt_adjust]<a class="headerlink" href="#screws_tilt_adjust" title="Permanent link">&para;</a></h3>
<p>當啟用 <a href="Config_Reference.html#screws_tilt_adjust">screws_tilt_adjust config section</a> 時，以下命令可用（另請參閱 [manual level guide](Manual_Level.md#adjusting-bed-leveling-screws-using-the-bed-probe ））。</p>
<h4 id="screws_tilt_calculate">SCREWS_TILT_CALCULATE<a class="headerlink" href="#screws_tilt_calculate" title="Permanent link">&para;</a></h4>
<p><code>SCREWS_TILT_CALCULATE [DIRECTION=CW|CCW] [&lt;probe_parameter&gt;=&lt;value&gt;]</code>：該命令將呼叫熱床絲桿調整工具。它將命令噴嘴到不同的位置（如配置檔案中定義的）探測z高度，並計算出調整床面水平的旋鈕旋轉次數。如果指定了DIRECTION，旋鈕的轉動方向都是一樣的，順時針（CW）或逆時針（CCW）。有關可選探頭參數的詳細資訊，請參見PROBE命令。重要的是：在使用這個命令之前，你必須先做一個G28。</p>
<p><code>SCREWS_TILT_CALCULATE [DIRECTION=CW|CCW] [MAX_DEVIATION=&lt;value&gt;] [&lt;probe_parameter&gt;=&lt;value&gt;]</code>: This command will invoke the bed screws adjustment tool. It will command the nozzle to different locations (as defined in the config file) probing the z height and calculate the number of knob turns to adjust the bed level. If DIRECTION is specified, the knob turns will all be in the same direction, clockwise (CW) or counterclockwise (CCW). See the PROBE command for details on the optional probe parameters. IMPORTANT: You MUST always do a G28 before using this command. If MAX_DEVIATION is specified, the command will raise a gcode error if any difference in the screw height relative to the base screw height is greater than the value provided.</p>
<h3 id="sdcard_loop">[sdcard_loop]<a class="headerlink" href="#sdcard_loop" title="Permanent link">&para;</a></h3>
<p>當 <a href="Config_Reference.html#sdcard_loop">sdcard_loop config section</a> 啟用時，以下擴展命令可用。</p>
<h4 id="sdcard_loop_begin">SDCARD_LOOP_BEGIN<a class="headerlink" href="#sdcard_loop_begin" title="Permanent link">&para;</a></h4>

4
zh-Hant/Hall_Filament_Width_Sensor.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

68
zh-Hant/Installation.html
View File

@@ -432,6 +432,13 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#obtain-a-klipper-configuration-file" class="md-nav__link">
Obtain a Klipper Configuration File
</a>
</li>
<li class="md-nav__item">
<a href="#_2" class="md-nav__link">
準備操作系統映象
@@ -458,13 +465,6 @@
配置 Klipper
</a>
</li>
<li class="md-nav__item">
<a href="#_4" class="md-nav__link">
聯繫開發者
</a>
</li>
</ul>
@@ -894,8 +894,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1268,6 +1268,13 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#obtain-a-klipper-configuration-file" class="md-nav__link">
Obtain a Klipper Configuration File
</a>
</li>
<li class="md-nav__item">
<a href="#_2" class="md-nav__link">
準備操作系統映象
@@ -1294,13 +1301,6 @@
配置 Klipper
</a>
</li>
<li class="md-nav__item">
<a href="#_4" class="md-nav__link">
聯繫開發者
</a>
</li>
</ul>
@@ -1322,7 +1322,11 @@
<h1 id="_1">安裝<a class="headerlink" href="#_1" title="Permanent link">&para;</a></h1>
<p>本教程假定軟體將會在樹莓派上和 Octoprint 一起執行。推薦使用樹莓派2/3/4作為主機（關於其他裝置，請見<a href="FAQ.html#can-i-run-klipper-on-something-other-than-a-raspberry-pi-3">常見問題</a>）。</p>
<p>Klipper 目前支援多種基於 Atmel ATmega 微控制器、<a href="Features.html#step-benchmarks">基於 ARM 微控制器</a> 和基於 <a href="Beaglebone.html">Beaglebone 可程式設計實時單元</a> 的印表機。</p>
<h2 id="obtain-a-klipper-configuration-file">Obtain a Klipper Configuration File<a class="headerlink" href="#obtain-a-klipper-configuration-file" title="Permanent link">&para;</a></h2>
<p>Most Klipper settings are determined by a "printer configuration file" that will be stored on the Raspberry Pi. An appropriate configuration file can often be found by looking in the Klipper <a href="https://github.com/Klipper3d/klipper/blob/master/config/">config directory</a> for a file starting with a "printer-" prefix that corresponds to the target printer. The Klipper configuration file contains technical information about the printer that will be needed during the installation.</p>
<p>If there isn't an appropriate printer configuration file in the Klipper config directory then try searching the printer manufacturer's website to see if they have an appropriate Klipper configuration file.</p>
<p>If no configuration file for the printer can be found, but the type of printer control board is known, then look for an appropriate <a href="https://github.com/Klipper3d/klipper/blob/master/config/">config file</a> starting with a "generic-" prefix. These example printer board files should allow one to successfully complete the initial installation, but will require some customization to obtain full printer functionality.</p>
<p>It is also possible to define a new printer configuration from scratch. However, this requires significant technical knowledge about the printer and its electronics. It is recommended that most users start with an appropriate configuration file. If creating a new custom printer configuration file, then start with the closest example <a href="https://github.com/Klipper3d/klipper/blob/master/config/">config file</a> and use the Klipper <a href="Config_Reference.html">config reference</a> for further information.</p>
<h2 id="_2">準備操作系統映象<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<p>先在樹莓派上安裝 <a href="https://github.com/guysoft/OctoPi">OctoPi</a>。請使用OctoPi v0.17.0或更高版本，檢視 <a href="https://github.com/guysoft/OctoPi/releases">Octopi 發行版</a>來獲取最新發布版本。安裝完系統后，請先驗證 OctoPi 能正常啟動，並且 OctoPrint 網路伺服器正常執行。連線到 OctoPrint 網頁后，按照提示將 OctoPrint 更新到v1.4.2或更高版本。</p>
<p>在安裝 OctoPi 和升級 OctoPrint后，用 ssh 進入目標裝置，以執行少量的系統命令。如果使用Linux或MacOS系統，那麼 "ssh"軟體應該已經預裝在系統上。有一些免費的ssh客戶端可用於其他操作系統（例如，<a href="https://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a>）。使用ssh工具連線到Raspberry Pi（ssh pi@octopi --密碼是 "raspberry"），並執行以下命令：</p>
@@ -1337,11 +1341,12 @@
make menuconfig
</code></pre></div>
<p>選擇恰當的微控制器並複查提供的其他選項。配置好后，執行：</p>
<p>The comments at the top of the <a href="#obtain-a-klipper-configuration-file">printer configuration file</a> should describe the settings that need to be set during "make menuconfig". Open the file in a web browser or text editor and look for these instructions near the top of the file. Once the appropriate "menuconfig" settings have been configured, press "Q" to exit, and then "Y" to save. Then run:</p>
<div class="highlight"><pre><span></span><code>make
</code></pre></div>
<p>必須先確定連線到微控制器的串列埠。對於通過 USB 連線的微控制器，執行以下命令：</p>
<p>If the comments at the top of the <a href="#obtain-a-klipper-configuration-file">printer configuration file</a> describe custom steps for "flashing" the final image to the printer control board then follow those steps and then proceed to <a href="#configuring-octoprint-to-use-klipper">configuring OctoPrint</a>.</p>
<p>Otherwise, the following steps are often used to "flash" the printer control board. First, it is necessary to determine the serial port connected to the micro-controller. Run the following:</p>
<div class="highlight"><pre><span></span><code>ls /dev/serial/by-id/*
</code></pre></div>
@@ -1366,25 +1371,30 @@ sudo service klipper start
<p>在主頁上，在 "連線 "部分（在頁面的左上方），確保 "串列埠 "被設定為"/tmp/printer"，然後點選 "連線"。(如果"/tmp/printer "不是一個可用的選擇，那麼試著重新載入頁面)</p>
<p>連線后，導航到 "終端 "選項卡，在命令輸入框中輸入 "status"（不帶引號），然後點選 "發送"。終端視窗可能會報告在打開配置檔案時出現了錯誤--這意味著 OctoPrint 與 Klipper 成功地進行了通訊。繼續下一部分。</p>
<h2 id="klipper">配置 Klipper<a class="headerlink" href="#klipper" title="Permanent link">&para;</a></h2>
<p>Klipper 配置儲存在樹莓派上的一個文字檔案中。請檢視在<a href="https://github.com/Klipper3d/klipper/blob/master/config/">config資料夾</a>中的配置示例。<a href="Config_Reference.html">配置參考</a>中有配置參數的文件。</p>
<p>可以說，更新Klipper configuration 檔案的最簡單方法是使用一個支援通過 "scp "或 "sftp "協議編輯檔案的桌面編輯器。有一些免費的工具支援這個功能（例如，Notepad++、WinSCP和Cyberduck）。使用其中一個配置檔案的例子作為起點，並將其儲存為pi使用者的主目錄中名為 "printer.cfg "的檔案（例如，/home/pi/printer.cfg）。</p>
<p>另外，也可以通過ssh在Raspberry Pi上直接複製和編輯該檔案。比如說：</p>
<p>The next step is to copy the <a href="#obtain-a-klipper-configuration-file">printer configuration file</a> to the Raspberry Pi.</p>
<p>Arguably the easiest way to set the Klipper configuration file is to use a desktop editor that supports editing files over the "scp" and/or "sftp" protocols. There are freely available tools that support this (eg, Notepad++, WinSCP, and Cyberduck). Load the printer config file in the editor and then save it as a file named "printer.cfg" in the home directory of the pi user (ie, /home/pi/printer.cfg).</p>
<p>Alternatively, one can also copy and edit the file directly on the Raspberry Pi via ssh. That may look something like the following (be sure to update the command to use the appropriate printer config filename):</p>
<div class="highlight"><pre><span></span><code>cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
nano ~/printer.cfg
</code></pre></div>
<p>確保你檢查和更新每一個設定並且與硬體相符合。</p>
<p>通常每臺印表機都有自己獨特的微控制器名稱。刷寫Klipper后這個名字可能會改變，所以重新執行<code>ls /dev/serial/by-id/*</code>命令，然後用這個唯一的名字更新配置檔案。例如，更新"[mcu]"部分，看起來類似於:</p>
<p>It's common for each printer to have its own unique name for the micro-controller. The name may change after flashing Klipper, so rerun these steps again even if they were already done when flashing. Run:</p>
<div class="highlight"><pre><span></span><code>ls /dev/serial/by-id/*
</code></pre></div>
<p>它應該報告類似以下的內容：</p>
<div class="highlight"><pre><span></span><code>/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
</code></pre></div>
<p>Then update the config file with the unique name. For example, update the <code>[mcu]</code> section to look something similar to:</p>
<div class="highlight"><pre><span></span><code>[mcu]
serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
</code></pre></div>
<p>在建立和編輯該檔案后，有必要在OctoPrint網路終端發出 "restart"命令去重新載入config。"status" 命令將報告印表機已準備就緒。在初始設定期間出現配置錯誤是很正常的。更新印表機配置檔案併發出 "restart"命令，直到 "狀態 "報告印表機已準備就緒。</p>
<p>After creating and editing the file it will be necessary to issue a "restart" command in the OctoPrint web terminal to load the config. A "status" command will report the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.</p>
<p>When customizing the printer config file, it is not uncommon for Klipper to report a configuration error. If an error occurs, make any necessary corrections to the printer config file and issue "restart" until "status" reports the printer is ready.</p>
<p>Klipper通過OctoPrint終端標籤報告錯誤資訊。可以使用 "status "命令來重新報告錯誤資訊。預設的Klipper啟動指令碼也在<strong>/tmp/klippy.log</strong>中放置一個日誌，提供更詳細的資訊。</p>
<p>除此之外常見的g-code命令之外，Klipper還支援一些擴充套件命令"status "和 "restart "就是這些命令的例子。使用 "help "命令可以獲得其他擴充套件命令的列表。</p>
<p>在Klipper反饋印表機已經準備好后，進入<a href="Config_checks.html">config check document</a>對配置檔案中的引腳定義進行一些基本檢查。</p>
<h2 id="_4">聯繫開發者<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>
<p>請務必檢視<a href="FAQ.html">FAQ</a>，瞭解一些常見問題的答案。請參閱<a href="Contact.html">聯繫頁面</a>來報告一個錯誤或聯繫開發者。</p>
<p>After Klipper reports that the printer is ready, proceed to the <a href="Config_checks.html">config check document</a> to perform some basic checks on the definitions in the config file. See the main <a href="Overview.html">documentation reference</a> for other information.</p>
</article>

4
zh-Hant/Kinematics.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/MCU_Commands.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Manual_Level.html
View File

@@ -895,8 +895,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

66
zh-Hant/Measuring_Resonances.html
View File

@@ -977,8 +977,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1531,6 +1531,38 @@
</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>
<table>
<thead>
<tr>
<th align="center">MPU-9250 pin</th>
<th align="center">樹莓派引腳</th>
<th align="center">樹莓派引腳名稱</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center">3V3 或 VCC</td>
<td align="center">01</td>
<td align="center">3.3v 直流（DC）電源</td>
</tr>
<tr>
<td align="center">GND</td>
<td align="center">09</td>
<td align="center">地（GND）</td>
</tr>
<tr>
<td align="center">SDA</td>
<td align="center">03</td>
<td align="center">GPIO02 (SDA1)</td>
</tr>
<tr>
<td align="center">SCL</td>
<td align="center">05</td>
<td align="center">GPIO03 (SCL1)</td>
</tr>
</tbody>
</table>
<p>部分ADXL345開發板的Fritzing接線圖如下：</p>
<p><img alt="ADXL345-樹莓派" src="img/adxl345-fritzing.png" /></p>
<p>為避免損害樹莓派或加速度感測器，請再三確認接線正確再對樹莓派上電。</p>
@@ -1541,19 +1573,19 @@
<p>注意，滑床式印表機需要設計兩個固定件：一個安裝于列印頭，另一個用於熱床，並進行兩次測量。詳見 <a href="#bed-slinger-printers">對應分節</a>。</p>
<p><strong>注意</strong>：務必確保加速度感測器和任何螺絲都不應該接觸到印表機的金屬部分。緊韌體必須設計成在加速度感測器和印表機框體間形成電氣絕緣。錯誤的設計可能會形成短路，從而損毀電氣元件。</p>
<h3 id="_5">軟體設定<a class="headerlink" href="#_5" title="Permanent link">&para;</a></h3>
<p>共振測量和自動整形校正需要額外的依賴項，這些依賴在Klipper安裝時未作部署，因此，需要在樹莓派上執行下面的命令：</p>
<p>Note that resonance measurements and shaper auto-calibration require additional software dependencies not installed by default. First, run on your Raspberry Pi the following commands:</p>
<div class="highlight"><pre><span></span><code>sudo apt update
sudo apt install python3-numpy python3-matplotlib libatlas-base-dev
</code></pre></div>
<p>Next, in order to install NumPy in the Klipper environment, run the command:</p>
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v numpy
</code></pre></div>
<p>安裝<code>numpy</code>包。numpy需要在安裝時進行編譯。編譯時間據主機的CPU算力而異，需要<em>耗費大量時間</em>，最大可至半小時（PiZero），請耐心等待編譯安裝完成。少部分情況下，主機的RAM不足會導致安裝失敗，需要開啟swap功能以實現安裝。</p>
<p>接下來，運行以下命令來安裝其他依賴項：</p>
<div class="highlight"><pre><span></span><code>sudo apt update
sudo apt install python3-numpy python3-matplotlib
</code></pre></div>
<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>
<p>通過執行<code>sudo raspi-config</code> 后的 "Interfacing options"菜單中啟用 SPI 以確保Linux SPI 驅動已啟用。</p>
<p>在printer.cfg附上下面的內容：</p>
<p>For the ADXL345, add the following to the printer.cfg file:</p>
<div class="highlight"><pre><span></span><code>[mcu rpi]
serial: /tmp/klipper_host_mcu
@@ -1567,6 +1599,20 @@ 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>
<div class="highlight"><pre><span></span><code>[mcu rpi]
serial: /tmp/klipper_host_mcu
[mpu9250]
i2c_mcu: rpi
i2c_bus: i2c.1
[resonance_tester]
accel_chip: mpu9250
probe_points:
100, 100, 20 # an example
</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>

4
zh-Hant/Multi_MCU_Homing.html
View File

@@ -835,8 +835,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Navigation.html
View File

@@ -818,8 +818,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

5
zh-Hant/Overview.html
View File

@@ -885,8 +885,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1346,6 +1346,7 @@
<li><a href="Slicers.html">切片</a>：為 Klipper 配置切片軟體。</li>
<li><a href="Skew_Correction.html">偏斜校正</a>：調整不完全垂直的軸（不完美的方形）。</li>
<li><a href="Using_PWM_Tools.html">PWM 工具</a>：關於如何使用 PWM 控制的工具，例如鐳射器或電鉆頭。</li>
<li><a href="Exclude_Object.html">Exclude Object</a>: The guide to the Exclude Objecs implementation.</li>
</ul>
<h2 id="_4">開發者文件<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>
<ul>

4
zh-Hant/Packaging.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Pressure_Advance.html
View File

@@ -873,8 +873,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Probe_Calibrate.html
View File

@@ -896,8 +896,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Protocol.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

20
zh-Hant/RPi_microcontroller.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1155,6 +1155,13 @@
可選：啟用 SPI
</a>
</li>
<li class="md-nav__item">
<a href="#optional-enabling-i2c" class="md-nav__link">
Optional: Enabling I2C
</a>
</li>
<li class="md-nav__item">
@@ -1315,6 +1322,13 @@
可選：啟用 SPI
</a>
</li>
<li class="md-nav__item">
<a href="#optional-enabling-i2c" class="md-nav__link">
Optional: Enabling I2C
</a>
</li>
<li class="md-nav__item">
@@ -1382,6 +1396,8 @@ sudo service klipper start
<p>按照<a href="https://github.com/Klipper3d/klipper/blob/master/config/sample-raspberry-pi.cfg">RaspberryPi 參考配置</a>和<a href="https://github.com/Klipper3d/klipper/blob/master/config/sample-multi-mcu.cfg">多微控制器參考配置</a>中的說明配置Klipper 二級微控制器來完成安裝。</p>
<h2 id="spi">可選：啟用 SPI<a class="headerlink" href="#spi" title="Permanent link">&para;</a></h2>
<p>通過執行<code>sudo raspi-config</code> 后的 "Interfacing options"菜單中啟用 SPI 以確保Linux SPI 驅動已啟用。</p>
<h2 id="optional-enabling-i2c">Optional: Enabling I2C<a class="headerlink" href="#optional-enabling-i2c" title="Permanent link">&para;</a></h2>
<p>Make sure the Linux I2C driver is enabled by running <code>sudo raspi-config</code> and enabling I2C under the "Interfacing options" menu. If planning to use I2C for the MPU accelerometer, it is also required to set the baud rate to 400000 by: adding/uncommenting <code>dtparam=i2c_arm=on,i2c_arm_baudrate=400000</code> in <code>/boot/config.txt</code> (or <code>/boot/firmware/config.txt</code> in some distros).</p>
<h2 id="gpiochip">可選步驟：識別正確的 gpiochip<a class="headerlink" href="#gpiochip" title="Permanent link">&para;</a></h2>
<p>On Raspberry Pi and on many clones the pins exposed on the GPIO belong to the first gpiochip. They can therefore be used on klipper simply by referring them with the name <code>gpio0..n</code>. However, there are cases in which the exposed pins belong to gpiochips other than the first. For example in the case of some OrangePi models or if a Port Expander is used. In these cases it is useful to use the commands to access the <em>Linux GPIO character device</em> to verify the configuration.</p>
<p>要在基於 Debian 的發行版（如 OctoPi）上安裝 <em>Linux GPIO character device - binary</em>，請執行：</p>

4
zh-Hant/Releases.html
View File

@@ -933,8 +933,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Resonance_Compensation.html
View File

@@ -991,8 +991,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/Rotation_Distance.html
View File

@@ -916,8 +916,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/SDCard_Updates.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

8
zh-Hant/Skew_Correction.html
View File

@@ -894,8 +894,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1399,13 +1399,13 @@ Length AD = 99.8
<a href="Using_PWM_Tools.html" class="md-footer__link md-footer__link--next" aria-label="下一頁: 使用 PWM 工具" rel="next">
<a href="Exclude_Object.html" class="md-footer__link md-footer__link--next" aria-label="下一頁: Exclude Objects" rel="next">
<div class="md-footer__title">
<div class="md-ellipsis">
<span class="md-footer__direction">
下一頁
</span>
使用 PWM 工具
Exclude Objects
</div>
</div>
<div class="md-footer__button md-icon">

4
zh-Hant/Slicers.html
View File

@@ -908,8 +908,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

52
zh-Hant/Status_Reference.html
View File

@@ -816,6 +816,13 @@
endstop_phase
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object" class="md-nav__link">
exclude_object
</a>
</li>
<li class="md-nav__item">
@@ -1113,8 +1120,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1520,6 +1527,13 @@
endstop_phase
</a>
</li>
<li class="md-nav__item">
<a href="#exclude_object" class="md-nav__link">
exclude_object
</a>
</li>
<li class="md-nav__item">
@@ -1776,6 +1790,7 @@
<li><code>settings.&lt;分段&gt;.&lt;選項&gt;</code>：返回最後一次軟體啟動或重啟時給定的配置檔案設定（或預設值）。(不會反映執行時的修改。）</li>
<li><code>config.&lt;分段&gt;.&lt;選項&gt;</code>：返回Klipper在上次軟體啟動或重啟時讀取的原始配置檔案設定。(不會反映執行時的修改。)所有值都以字串形式返回。</li>
<li><code>save_config_pending</code>：如果存在可以通過 <code>SAVE_CONFIG</code> 命令儲存到配置檔案的更新，則返回 True。</li>
<li><code>save_config_pending_items</code>: Contains the sections and options that were changed and would be persisted by a <code>SAVE_CONFIG</code>.</li>
<li><code>warnings</code>：有關配置選項的警告列表。列表中的每個條目都將是一個 dictionary，其中包含 <code>type</code> 和 <code>message</code> 欄位（都是字串）。根據警告型別，可能還有其他可用欄位。</li>
</ul>
<h2 id="display_status">display_status<a class="headerlink" href="#display_status" title="Permanent link">&para;</a></h2>
@@ -1791,6 +1806,39 @@
<li><code>last_home.&lt;步進電機名稱&gt;.phase</code>：步進電機上可用的總相數。</li>
<li><code>last_home.&lt;步進電機名稱&gt;.mcu_position</code>：步進電機在上次歸位嘗試結束時的位置（由微控制器跟蹤）。該位置是自微控制器最後一次重啟以來，向前走的總步數減去反向走的總步數。</li>
</ul>
<h2 id="exclude_object">exclude_object<a class="headerlink" href="#exclude_object" title="Permanent link">&para;</a></h2>
<p>The following information is available in the <a href="Exclude_Object.html">exclude_object</a> object:</p>
<ul>
<li><code>objects</code>: An array of the known objects as provided by the <code>EXCLUDE_OBJECT_DEFINE</code> command. This is the same information provided by the <code>EXCLUDE_OBJECT VERBOSE=1</code> command. The <code>center</code> and <code>polygon</code> fields will only be present if provided in the original <code>EXCLUDE_OBJECT_DEFINE</code>Here is a JSON sample:</li>
</ul>
<div class="highlight"><pre><span></span><code>[
{
&quot;polygon&quot;: [
[ 156.25, 146.2511675 ],
[ 156.25, 153.7488325 ],
[ 163.75, 153.7488325 ],
[ 163.75, 146.2511675 ]
],
&quot;name&quot;: &quot;CYLINDER_2_STL_ID_2_COPY_0&quot;,
&quot;center&quot;: [ 160, 150 ]
},
{
&quot;polygon&quot;: [
[ 146.25, 146.2511675 ],
[ 146.25, 153.7488325 ],
[ 153.75, 153.7488325 ],
[ 153.75, 146.2511675 ]
],
&quot;name&quot;: &quot;CYLINDER_2_STL_ID_1_COPY_0&quot;,
&quot;center&quot;: [ 150, 150 ]
}
]
</code></pre></div>
<ul>
<li><code>excluded_objects</code>: An array of strings listing the names of excluded objects.</li>
<li><code>current_object</code>: The name of the object currently being printed.</li>
</ul>
<h2 id="fan">fan<a class="headerlink" href="#fan" title="Permanent link">&para;</a></h2>
<p><a href="Config_Reference.html#fan">fan</a>、<a href="Config_Reference.html#heater_fan">heater_fan some_name</a>和<a href="Config_Reference.html#controller_fan">controller_fan some_name</a>對像提供了以下資訊：</p>
<ul>

4
zh-Hant/TMC_Drivers.html
View File

@@ -1072,8 +1072,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

4
zh-Hant/TSL1401CL_Filament_Width_Sensor.html
View File

@@ -823,8 +823,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

8
zh-Hant/Using_PWM_Tools.html
View File

@@ -825,8 +825,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>
@@ -1361,7 +1361,7 @@ LASER INTENSITY: 鐳射強度
<nav class="md-footer__inner md-grid" aria-label="Footer">
<a href="Skew_Correction.html" class="md-footer__link md-footer__link--prev" aria-label="上一頁: 偏斜校正" rel="prev">
<a href="Exclude_Object.html" class="md-footer__link md-footer__link--prev" aria-label="上一頁: Exclude Objects" 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>
@@ -1370,7 +1370,7 @@ LASER INTENSITY: 鐳射強度
<span class="md-footer__direction">
上一頁
</span>
偏斜校正
Exclude Objects
</div>
</div>
</a>

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

Binary file not shown.

4
zh-Hant/index.html
View File

@@ -820,8 +820,8 @@
<li class="md-nav__item">
<a href="Exclude_Object.md" class="md-nav__link">
None
<a href="Exclude_Object.html" class="md-nav__link">
Exclude Objects
</a>
</li>

2
zh-Hant/search/search_index.json
View File

File diff suppressed because one or more lines are too long

101
zh-Hant/sitemap.xml
View File

@@ -2,242 +2,247 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-26</lastmod>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2022-06-27</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>

BIN
zh-Hant/sitemap.xml.gz
View File

Binary file not shown.