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

Deploying to gh-pages from @ Klipper3d/klipper@7b490f3ec1 🚀

Browse Source
This commit is contained in:
KevinOConnor
2024-04-28 00:05:14 +00:00
parent 15e16ec351
commit 03f81ee535
83 changed files with 1973 additions and 1233 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
zh-Hant/Bed_Mesh.html
View File

@@ -712,6 +712,13 @@
故障區域
</a>
</li>
<li class="md-nav__item">
<a href="#adaptive-meshes" class="md-nav__link">
Adaptive Meshes
</a>
</li>
</ul>
@@ -1548,6 +1555,13 @@
故障區域
</a>
</li>
<li class="md-nav__item">
<a href="#adaptive-meshes" class="md-nav__link">
Adaptive Meshes
</a>
</li>
</ul>
@@ -1782,9 +1796,29 @@ faulty_region_4_max: 45.0, 210.0
</ul>
<p>下面的圖片說明了當一個產生的探測點位於一個故障區域內時，如何產生替代探測點。所顯示的區域與上述樣本配置中的區域一致。替代點和它們的座標以綠色標識。</p>
<p><img alt="bedmesh_interpolated" src="img/bedmesh_faulty_regions.svg" /></p>
<h3 id="adaptive-meshes">Adaptive Meshes<a class="headerlink" href="#adaptive-meshes" title="Permanent link">&para;</a></h3>
<p>Adaptive bed meshing is a way to speed up the bed mesh generation by only probing the area of the bed used by the objects being printed. When used, the method will automatically adjust the mesh parameters based on the area occupied by the defined print objects.</p>
<p>The adapted mesh area will be computed from the area defined by the boundaries of all the defined print objects so it covers every object, including any margins defined in the configuration. After the area is computed, the number of probe points will be scaled down based on the ratio of the default mesh area and the adapted mesh area. To illustrate this consider the following example:</p>
<p>For a 150mmx150mm bed with <code>mesh_min</code> set to <code>25,25</code> and <code>mesh_max</code> set to <code>125,125</code>, the default mesh area is a 100mmx100mm square. An adapted mesh area of <code>50,50</code> means a ratio of <code>0.5x0.5</code> between the adapted area and default mesh area.</p>
<p>If the <code>bed_mesh</code> configuration specified <code>probe_count</code> as <code>7x7</code>, the adapted bed mesh will use 4x4 probe points (7 * 0.5 rounded up).</p>
<p><img alt="adaptive_bedmesh" src="img/adaptive_bed_mesh.svg" /></p>
<div class="highlight"><pre><span></span><code>[bed_mesh]
speed: 120
horizontal_move_z: 5
mesh_min: 35, 6
mesh_max: 240, 198
probe_count: 5, 3
adaptive_margin: 5
</code></pre></div>
<ul>
<li><code>adaptive_margin</code> <em>Default Value: 0</em> Margin (in mm) to add around the area of the bed used by the defined objects. The diagram below shows the adapted bed mesh area with an <code>adaptive_margin</code> of 5mm. The adapted mesh area (area in green) is computed as the used bed area (area in blue) plus the defined margin.<img alt="adaptive_bedmesh_margin" src="img/adaptive_bed_mesh_margin.svg" /></li>
</ul>
<p>By nature, adaptive bed meshes use the objects defined by the Gcode file being printed. Therefore, it is expected that each Gcode file will generate a mesh that probes a different area of the print bed. Therefore, adapted bed meshes should not be re-used. The expectation is that a new mesh will be generated for each print if adaptive meshing is used.</p>
<p>It is also important to consider that adaptive bed meshing is best used on machines that can normally probe the entire bed and achieve a maximum variance less than or equal to 1 layer height. Machines with mechanical issues that a full bed mesh normally compensates for may have undesirable results when attempting print moves <strong>outside</strong> of the probed area. If a full bed mesh has a variance greater than 1 layer height, caution must be taken when using adaptive bed meshes and attempting print moves outside of the meshed area.</p>
<h2 id="g">床網 G程式碼<a class="headerlink" href="#g" title="Permanent link">&para;</a></h2>
<h3 id="_10">校準<a class="headerlink" href="#_10" title="Permanent link">&para;</a></h3>
<p><code>BED_MESH_CALIBRATE PROFILE=&lt;名稱&gt; METHOD=[manual | automatic] [&lt;probe_parameter&gt;=&lt;值&gt;] [&lt;mesh_parameter&gt;=&lt;值&gt;]</code> <em>預設配置：default</em> <em>預設方法：如果檢測到探針則自動，否則手動</em></p>
<p><code>BED_MESH_CALIBRATE PROFILE=&lt;name&gt; METHOD=[manual | automatic] [&lt;probe_parameter&gt;=&lt;value&gt;] [&lt;mesh_parameter&gt;=&lt;value&gt;] [ADAPTIVE=[0|1] [ADAPTIVE_MARGIN=&lt;value&gt;]</code> <em>Default Profile: default</em> <em>Default Method: automatic if a probe is detected, otherwise manual</em> <em>Default Adaptive: 0</em> <em>Default Adaptive Margin: 0</em></p>
<p>啟動床網校準的探測程式。</p>
<p>網格將被儲存到由 <code>PROFILE</code> 參數指定的配置中，如果沒有指定，則使用 <code>default</code>。如果選擇了 <code>METHOD=manual</code> ，那麼將進行手動探測。在自動和手動探測之間切換時，產生的網格點會自動調整。</p>
<p>可以通過指定網格參數來修改探測區域。以下參數可用：</p>
@@ -1803,6 +1837,8 @@ faulty_region_4_max: 45.0, 210.0
</li>
<li>全部列印床：<ul>
<li><code>ALGORITHM</code></li>
<li><code>ADAPTIVE</code></li>
<li><code>ADAPTIVE_MARGIN</code></li>
</ul>
</li>
</ul>
@@ -1851,8 +1887,9 @@ faulty_region_4_max: 45.0, 210.0
<p><code>BED_MESH_CLEAR</code></p>
<p>此 gcode 可用於清除內部網格狀態。</p>
<h3 id="xy">應用X/Y偏移量<a class="headerlink" href="#xy" title="Permanent link">&para;</a></h3>
<p><code>BED_MESH_OFFSET [X=&lt;value&gt;] [Y=&lt;value&gt;]</code></p>
<p>這對有多個獨立擠出頭的印表機很有用，因為偏移量是必要的，以便在更換工具后產生正確的Z調整。應指定它們相對於主擠出頭的偏移量。也就是說，如果第二個擠出頭安裝在第一個擠出頭的右邊，應指定一個正的X偏移量，如果第二個擠出頭安裝在第一個擠出頭的 "後面"，應指定一個正的Y偏移量。</p>
<p><code>BED_MESH_OFFSET [X=&lt;value&gt;] [Y=&lt;value&gt;] [ZFADE=&lt;value&gt;]</code></p>
<p>This is useful for printers with multiple independent extruders, as an offset is necessary to produce correct Z adjustment after a tool change. Offsets should be specified relative to the primary extruder. That is, a positive X offset should be specified if the secondary extruder is mounted to the right of the primary extruder, a positive Y offset should be specified if the secondary extruder is mounted "behind" the primary extruder, and a positive ZFADE offset should be specified if the secondary extruder's nozzle is above the primary extruder's.</p>
<p>Note that a ZFADE offset does <em>NOT</em> directly apply additional adjustment. It is intended to compensate for a <code>gcode offset</code> when <a href="#mesh-fade">mesh fade</a> is enabled. For example, if a secondary extruder is higher than the primary and needs a negative gcode offset, ie: <code>SET_GCODE_OFFSET Z=-.2</code>, it can be accounted for in <code>bed_mesh</code> with <code>BED_MESH_OFFSET ZFADE=.2</code>.</p>
</article>

8
zh-Hant/Code_Overview.html
View File

@@ -1484,16 +1484,16 @@
<p>典型的印表機運動始於klipper上位機接收到"G1"命令，並在微控制器發出對應的步進脈衝結束。本節將簡述典型運動命令的程式碼流。<a href="Kinematics.html">運動學</a>文件將更為細緻的描述運動的機械原理。</p>
<ul>
<li>移動命令的處理始於gcode.py，該程式碼將G程式碼轉化為內部呼叫。G1命令將呼叫klippy/extras/gcode_move.py中的cmd_G1()函式。gcode_move.py中的程式碼將處理 原點變換（G92），絕對座標模式（G90）和單位變換（如F6000=100mm/s）。一個移動命令的處理路徑為：<code>_process_data() -&gt; _process_commands() -&gt; cmd_G1()</code>。最終將呼叫ToolHead類的方法實現移動 <code>cmd_G1() -&gt; ToolHead.move()</code>。</li>
<li>ToolHead類（位於toolhead.py）處理「前瞻」行為和記錄列印的時間點。移動命令的程式碼路徑為 <code>ToolHead.move() -&gt; MoveQueue.add_move() -&gt; MoveQueue.flush() -&gt; Move.set_junction() -&gt; ToolHead._process_moves()</code>。<ul>
<li>The ToolHead class (in toolhead.py) handles "look-ahead" and tracks the timing of printing actions. The main codepath for a move is: <code>ToolHead.move() -&gt; LookAheadQueue.add_move() -&gt; LookAheadQueue.flush() -&gt; Move.set_junction() -&gt; ToolHead._process_moves()</code>.<ul>
<li>ToolHead.move()將建立一個Move()對像實例，其中將包含移動的參數（在笛卡爾空間中，並這些參數以mm和s為單位）。</li>
<li>kinematics類將檢查每個運動命令（<code>ToolHead.move() -&gt; kin.check_move()</code>）。各種kinematics類存放于 klippy/kinematics/ 目錄。check_move()能在運動命令不合理時拋出錯誤。如果 check_move()成功，這意味著印表機必定能完成運動命令。</li>
<li>MoveQueue.add_move()將一個move實例新增到「前瞻」佇列。</li>
<li>MoveQueue.flush()將進行每次運動 起始和結束 速度。</li>
<li>LookAheadQueue.add_move() places the move object on the "look-ahead" queue.</li>
<li>LookAheadQueue.flush() determines the start and end velocities of each move.</li>
<li>Move.set_junction()實現移動的「梯形加減速（trapezoid generator）」。「梯形加減速」將每次移動拆分為三部分：恒加速度加速階段、恒速度階段、恒加速度減速階段。所有移動均含有上述三個階段，但單個階段的持續時間可能為0。</li>
<li>當ToolHead._process_moves()被呼叫時，一次移動的所有要素均已就緒——移動的起始位置、結束位置、加速度、起始/巡航/結束速度、以及起始/巡航/結束的距離。所有資訊以笛卡爾座標的形式儲存在Move()實例中，單位為mm和s。</li>
</ul>
</li>
<li>Klipper使用<a href="https://en.wikipedia.org/wiki/Root-finding_algorithm">迭代求解</a>的方式產生步進電機的每步的時長。爲了提高效率，步進脈衝時間是以C語言程式碼產生。一個運動先經過「梯形運動佇列化」 ：<code>ToolHead._process_moves() -&gt; trapq_append()</code> (位於 klippy/chelper/trapq.c)，然後產生步進時間 <code>ToolHead._process_moves() -&gt; ToolHead._update_move_time() -&gt; MCU_Stepper.generate_steps() -&gt; itersolve_generate_steps() -&gt; itersolve_gen_steps_range()</code> (位於 klippy/chelper/itersolve.c)。迭代求解器通過一個時間-位置方程計算出步進時間。求解時通過「假定」時間點，以時間-位置方程計算出下一步的位置。如果計算結果與實際需求的下一步位置一致，假定值將用於實際運動；否則，通過計算結果對「假定時間」進行修正，並進行下一次試算。這種反饋方式會使迭代快速收斂。運動學所使用的時間-位置函式位於 klippy/chelper/ 目錄 (例如, kin_cart.c, kin_corexy.c, kin_delta.c, kin_extruder.c)。</li>
<li>Klipper uses an <a href="https://en.wikipedia.org/wiki/Root-finding_algorithm">iterative solver</a> to generate the step times for each stepper. For efficiency reasons, the stepper pulse times are generated in C code. The moves are first placed on a "trapezoid motion queue": <code>ToolHead._process_moves() -&gt; trapq_append()</code> (in klippy/chelper/trapq.c). The step times are then generated: <code>ToolHead._process_moves() -&gt; ToolHead._advance_move_time() -&gt; ToolHead._advance_flush_time() -&gt; MCU_Stepper.generate_steps() -&gt; itersolve_generate_steps() -&gt; itersolve_gen_steps_range()</code> (in klippy/chelper/itersolve.c). The goal of the iterative solver is to find step times given a function that calculates a stepper position from a time. This is done by repeatedly "guessing" various times until the stepper position formula returns the desired position of the next step on the stepper. The feedback produced from each guess is used to improve future guesses so that the process rapidly converges to the desired time. The kinematic stepper position formulas are located in the klippy/chelper/ directory (eg, kin_cart.c, kin_corexy.c, kin_delta.c, kin_extruder.c).</li>
<li>需要注意，擠出機有獨特的運動學模型，使用<code>ToolHead._process_moves() -&gt; PrinterExtruder.move()</code>類繼續寧處理。儘管擠出機使用了獨立的Move()類，由於Move() 實例包含了實際運動的時間，並且脈衝時間的裝置是定時發送到微控制器上，因此由擠出機類產生的步進運動將與列印頭的運動同步。</li>
<li>當迭代計算器計算出步進時長后，計算結果將被置於一個陣列中：<code>itersolve_gen_steps_range() -&gt; stepcompress_append()</code> (位於 klippy/chelper/stepcompress.c)。陣列(結構體 stepcompress.queue)儲存每一步對應的微處理器時鐘計數器時間。上述的「微處理器計數器」的值指的是微處理器硬體上的計數器——其值基於微處理器最後一次上電而定。</li>
<li>接下來重要的是，對步進數據進行壓縮： <code>stepcompress_flush() -&gt; compress_bisect_add()</code> (位於 klippy/chelper/stepcompress.c)。上述程式碼將基於前述的 步進時間列表 產生和編碼一系列的微控制器"queue_step"（佇列步進）命令。這些"queue_step"命令將被佇列化，優先處理，併發送到微控制器中（上位機通過 stepcompress.c:steppersync；下位機通過serialqueue.c:serialqueue)）。</li>

9
zh-Hant/Config_Changes.html
View File

@@ -1349,6 +1349,15 @@
<p>本文件涵蓋了軟體更新中對配置檔案不向后相容的部分。在升級 Klipper 時，最好也檢視一下這份文件。</p>
<p>本文件中的所有日期都是不精確的。</p>
<h2 id="_2">變更<a class="headerlink" href="#_2" title="Permanent link">&para;</a></h2>
<p>20240313: The <code>max_accel_to_decel</code> parameter in the <code>[printer]</code> config section has been deprecated. The <code>ACCEL_TO_DECEL</code> parameter of the <code>SET_VELOCITY_LIMIT</code> command has been deprecated. The <code>printer.toolhead.max_accel_to_decel</code> status has been removed. Use the <a href="Config_Reference.html#printer">minimum_cruise_ratio parameter</a> instead. The deprecated features will be removed in the near future, and using them in the interim may result in subtly different behavior.</p>
<p>20240215: Several deprecated features have been removed. Using "NTC 100K beta 3950" as a thermistor name has been removed (deprecated on 20211110). The <code>SYNC_STEPPER_TO_EXTRUDER</code> and <code>SET_EXTRUDER_STEP_DISTANCE</code> commands have been removed, and the extruder <code>shared_heater</code> config option has been removed (deprecated on 20220210). The bed_mesh <code>relative_reference_index</code> option has been removed (deprecated on 20230619).</p>
<p>20240123: The output_pin SET_PIN CYCLE_TIME parameter has been removed. Use the new <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time</a> module if it is necessary to dynamically change a pwm pin's cycle time.</p>
<p>20240123: The output_pin <code>maximum_mcu_duration</code> parameter is deprecated. Use a <a href="Config_Reference.html#pwm_tool">pwm_tool config section</a> instead. The option will be removed in the near future.</p>
<p>20240123: The output_pin <code>static_value</code> parameter is deprecated. Replace with <code>value</code> and <code>shutdown_value</code> parameters. The option will be removed in the near future.</p>
<p>20231216: The <code>[hall_filament_width_sensor]</code> is changed to trigger filament runout when the thickness of the filament exceeds <code>max_diameter</code>. The maximum diameter defaults to <code>default_nominal_filament_diameter + max_difference</code>. See <a href="Config_Reference.html#hall_filament_width_sensor">[hall_filament_width_sensor] configuration
reference</a> for more details.</p>
<p>20231207: Several undocumented config parameters in the <code>[printer]</code> config section have been removed (the buffer_time_low, buffer_time_high, buffer_time_start, and move_flush_time parameters).</p>
<p>20231110: Klipper v0.12.0 released.</p>
<p>20230826: If <code>safe_distance</code> is set or calculated to be 0 in <code>[dual_carriage]</code>, the carriages proximity checks will be disabled as per documentation. A user may wish to configure <code>safe_distance</code> explicitly to prevent accidental crashes of the carriages with each other. Additionally, the homing order of the primary and the dual carriage is changed in some configurations (certain configurations when both carriages home in the same direction, see <a href="Config_Reference.html#dual_carriage">[dual_carriage] configuration reference</a> for more details).</p>
<p>20230810: The flash-sdcard.sh script now supports both variants of the Bigtreetech SKR-3, STM32H743 and STM32H723. For this, the original tag of btt-skr-3 now has changed to be either btt-skr-3-h743 or btt-skr-3-h723.</p>
<p>20230729: The exported status for <code>dual_carriage</code> is changed. Instead of exporting <code>mode</code> and <code>active_carriage</code>, the individual modes for each carriage are exported as <code>printer.dual_carriage.carriage_0</code> and <code>printer.dual_carriage.carriage_1</code>.</p>

118
zh-Hant/Config_Reference.html
View File

@@ -1310,6 +1310,20 @@
[output_pin]
</a>
</li>
<li class="md-nav__item">
<a href="#pwm_tool" class="md-nav__link">
[pwm_tool]
</a>
</li>
<li class="md-nav__item">
<a href="#pwm_cycle_time" class="md-nav__link">
[pwm_cycle_time]
</a>
</li>
<li class="md-nav__item">
@@ -3322,6 +3336,20 @@
[output_pin]
</a>
</li>
<li class="md-nav__item">
<a href="#pwm_tool" class="md-nav__link">
[pwm_tool]
</a>
</li>
<li class="md-nav__item">
<a href="#pwm_cycle_time" class="md-nav__link">
[pwm_cycle_time]
</a>
</li>
<li class="md-nav__item">
@@ -3753,13 +3781,27 @@ max_velocity:
# print). This parameter must be specified.
max_accel:
# Maximum acceleration (in mm/s^2) of the toolhead (relative to the
# print). This parameter must be specified.
#max_accel_to_decel:
# A pseudo acceleration (in mm/s^2) controlling how fast the
# toolhead may go from acceleration to deceleration. It is used to
# reduce the top speed of short zig-zag moves (and thus reduce
# printer vibration from these moves). The default is half of
# max_accel.
# print). Although this parameter is described as a &quot;maximum&quot;
# acceleration, in practice most moves that accelerate or decelerate
# will do so at the rate specified here. The value specified here
# may be changed at runtime using the SET_VELOCITY_LIMIT command.
# This parameter must be specified.
#minimum_cruise_ratio: 0.5
# Most moves will accelerate to a cruising speed, travel at that
# cruising speed, and then decelerate. However, some moves that
# travel a short distance could nominally accelerate and then
# immediately decelerate. This option reduces the top speed of these
# moves to ensure there is always a minimum distance traveled at a
# cruising speed. That is, it enforces a minimum distance traveled
# at cruising speed relative to the total distance traveled. It is
# intended to reduce the top speed of short zigzag moves (and thus
# reduce printer vibration from these moves). For example, a
# minimum_cruise_ratio of 0.5 would ensure that a standalone 1.5mm
# move would have a minimum cruising distance of 0.75mm. Specify a
# ratio of 0.0 to disable this feature (there would be no minimum
# cruising distance enforced between acceleration and deceleration).
# The value specified here may be changed at runtime using the
# SET_VELOCITY_LIMIT command. The default is 0.5.
#square_corner_velocity: 5.0
# The maximum velocity (in mm/s) that the toolhead may travel a 90
# degree corner at. A non-zero value can reduce changes in extruder
@@ -3769,7 +3811,11 @@ max_accel:
# larger than 90 degrees will have a higher cornering velocity while
# corners with angles less than 90 degrees will have a lower
# cornering velocity. If this is set to zero then the toolhead will
# decelerate to zero at each corner. The default is 5mm/s.
# decelerate to zero at each corner. The value specified here may be
# changed at runtime using the SET_VELOCITY_LIMIT command. The
# default is 5mm/s.
#max_accel_to_decel:
# This parameter is deprecated and should no longer be used.
</code></pre></div>
<h3 id="stepper">[stepper]<a class="headerlink" href="#stepper" title="Permanent link">&para;</a></h3>
@@ -4513,18 +4559,14 @@ max_temp:
# where Z = 0. When this option is specified the mesh will be offset
# so that zero Z adjustment occurs at this location. The default is
# no zero reference.
#relative_reference_index:
# **DEPRECATED, use the &quot;zero_reference_position&quot; option**
# The legacy option superceded by the &quot;zero reference position&quot;.
# Rather than a coordinate this option takes an integer &quot;index&quot; that
# refers to the location of one of the generated points. It is recommended
# to use the &quot;zero_reference_position&quot; instead of this option for new
# configurations. The default is no relative reference index.
#faulty_region_1_min:
#faulty_region_1_max:
# Optional points that define a faulty region. See docs/Bed_Mesh.md
# for details on faulty regions. Up to 99 faulty regions may be added.
# By default no faulty regions are set.
#adaptive_margin:
# An optional margin (in mm) to be added around the bed area used by
# the defined print objects when generating an adaptive mesh.
</code></pre></div>
<h3 id="bed_tilt">[bed_tilt]<a class="headerlink" href="#bed_tilt" title="Permanent link">&para;</a></h3>
@@ -6135,24 +6177,12 @@ pin:
# If this is true, the value fields should be between 0 and 1; if it
# is false the value fields should be either 0 or 1. The default is
# False.
#static_value:
# If this is set, then the pin is assigned to this value at startup
# and the pin can not be changed during runtime. A static pin uses
# slightly less ram in the micro-controller. The default is to use
# runtime configuration of pins.
#value:
# The value to initially set the pin to during MCU configuration.
# The default is 0 (for low voltage).
#shutdown_value:
# The value to set the pin to on an MCU shutdown event. The default
# is 0 (for low voltage).
#maximum_mcu_duration:
# The maximum duration a non-shutdown value may be driven by the MCU
# without an acknowledge from the host.
# If host can not keep up with an update, the MCU will shutdown
# and set all pins to their respective shutdown values.
# Default: 0 (disabled)
# Usual values are around 5 seconds.
#cycle_time: 0.100
# The amount of time (in seconds) per PWM cycle. It is recommended
# this be 10 milliseconds or greater when using software based PWM.
@@ -6172,6 +6202,40 @@ pin:
# then the &#39;value&#39; parameter can be specified using the desired
# amperage for the stepper. The default is to not scale the &#39;value&#39;
# parameter.
#maximum_mcu_duration:
#static_value:
# These options are deprecated and should no longer be specified.
</code></pre></div>
<h3 id="pwm_tool">[pwm_tool]<a class="headerlink" href="#pwm_tool" title="Permanent link">&para;</a></h3>
<p>Pulse width modulation digital output pins capable of high speed updates (one may define any number of sections with an "output_pin" prefix). Pins configured here will be setup as output pins and one may modify them at run-time using "SET_PIN PIN=my_pin VALUE=.1" type extended <a href="G-Codes.html#output_pin">g-code commands</a>.</p>
<div class="highlight"><pre><span></span><code>[pwm_tool my_tool]
pin:
# The pin to configure as an output. This parameter must be provided.
#maximum_mcu_duration:
# The maximum duration a non-shutdown value may be driven by the MCU
# without an acknowledge from the host.
# If host can not keep up with an update, the MCU will shutdown
# and set all pins to their respective shutdown values.
# Default: 0 (disabled)
# Usual values are around 5 seconds.
#value:
#shutdown_value:
#cycle_time: 0.100
#hardware_pwm: False
#scale:
# See the &quot;output_pin&quot; section for the definition of these parameters.
</code></pre></div>
<h3 id="pwm_cycle_time">[pwm_cycle_time]<a class="headerlink" href="#pwm_cycle_time" title="Permanent link">&para;</a></h3>
<p>Run-time configurable output pins with dynamic pwm cycle timing (one may define any number of sections with an "pwm_cycle_time" prefix). Pins configured here will be setup as output pins and one may modify them at run-time using "SET_PIN PIN=my_pin VALUE=.1 CYCLE_TIME=0.100" type extended <a href="G-Codes.html#pwm_cycle_time">g-code commands</a>.</p>
<div class="highlight"><pre><span></span><code>[pwm_cycle_time my_pin]
pin:
#value:
#shutdown_value:
#cycle_time: 0.100
#scale:
# See the &quot;output_pin&quot; section for information on these parameters.
</code></pre></div>
<h3 id="static_digital_output">[static_digital_output]<a class="headerlink" href="#static_digital_output" title="Permanent link">&para;</a></h3>

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

@@ -841,6 +841,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
<nav class="md-nav" aria-label="[axis_twist_compensation]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#axis_twist_compensation_calibrate" class="md-nav__link">
AXIS_TWIST_COMPENSATION_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -1188,20 +1208,6 @@
SYNC_EXTRUDER_MOTION
</a>
</li>
<li class="md-nav__item">
<a href="#set_extruder_step_distance" class="md-nav__link">
SET_EXTRUDER_STEP_DISTANCE
</a>
</li>
<li class="md-nav__item">
<a href="#sync_stepper_to_extruder" class="md-nav__link">
SYNC_STEPPER_TO_EXTRUDER
</a>
</li>
</ul>
@@ -1858,6 +1864,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pwm_cycle_time" class="md-nav__link">
[pwm_cycle_time]
</a>
<nav class="md-nav" aria-label="[pwm_cycle_time]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_pin_1" class="md-nav__link">
SET_PIN
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -2262,26 +2288,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
<nav class="md-nav" aria-label="[axis_twist_compensation]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#axis_twist_compensation_calibrate" class="md-nav__link">
AXIS_TWIST_COMPENSATION_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -2980,6 +2986,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
<nav class="md-nav" aria-label="[axis_twist_compensation]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#axis_twist_compensation_calibrate" class="md-nav__link">
AXIS_TWIST_COMPENSATION_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -3327,20 +3353,6 @@
SYNC_EXTRUDER_MOTION
</a>
</li>
<li class="md-nav__item">
<a href="#set_extruder_step_distance" class="md-nav__link">
SET_EXTRUDER_STEP_DISTANCE
</a>
</li>
<li class="md-nav__item">
<a href="#sync_stepper_to_extruder" class="md-nav__link">
SYNC_STEPPER_TO_EXTRUDER
</a>
</li>
</ul>
@@ -3997,6 +4009,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pwm_cycle_time" class="md-nav__link">
[pwm_cycle_time]
</a>
<nav class="md-nav" aria-label="[pwm_cycle_time]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_pin_1" class="md-nav__link">
SET_PIN
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4401,26 +4433,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
<nav class="md-nav" aria-label="[axis_twist_compensation]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#axis_twist_compensation_calibrate" class="md-nav__link">
AXIS_TWIST_COMPENSATION_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4545,10 +4557,15 @@
<p><code>ANGLE_DEBUG_READ CHIP=&lt;config_name&gt; REG=&lt;register&gt;</code>: Queries sensor register "register" (e.g. 44 or 0x2C). Can be useful for debugging purposes. This is only available for tle5012b chips.</p>
<h4 id="angle_debug_write">ANGLE_DEBUG_WRITE<a class="headerlink" href="#angle_debug_write" title="Permanent link">&para;</a></h4>
<p><code>ANGLE_DEBUG_WRITE CHIP=&lt;config_name&gt; REG=&lt;register&gt; VAL=&lt;value&gt;</code>: Writes raw "value" into register "register". Both "value" and "register" can be a decimal or a hexadecimal integer. Use with care, and refer to sensor data sheet for the reference. This is only available for tle5012b chips.</p>
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">&para;</a></h3>
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
section</a> is enabled.</p>
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">&para;</a></h4>
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=&lt;value&gt;]</code>: Initiates the X twist calibration wizard. <code>SAMPLE_COUNT</code> specifies the number of points along the X axis to calibrate at and defaults to 3.</p>
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">&para;</a></h3>
<p>當啟用 <a href="Config_Reference.html#bed_mesh">bed_mesh config section</a> 時，以下命令可用（另請參閱 <a href="Bed_Mesh.html">bed mesh guide</a>）。</p>
<h4 id="bed_mesh_calibrate">BED_MESH_CALIBRATE<a class="headerlink" href="#bed_mesh_calibrate" title="Permanent link">&para;</a></h4>
<p><code>BED_MESH_CALIBRATE [METHOD=manual] [HORIZONTAL_MOVE_Z=&lt;value&gt;] [&lt;probe_parameter&gt;=&lt;value&gt;] [&lt;mesh_parameter&gt;=&lt;value&gt;]</code>: This command probes the bed using generated points specified by the parameters in the config. After probing, a mesh is generated and z-movement is adjusted according to the mesh. See the PROBE command for details on the optional probe parameters. If METHOD=manual is specified then the manual probing tool is activated - see the MANUAL_PROBE command above for details on the additional commands available while this tool is active. The optional <code>HORIZONTAL_MOVE_Z</code> value overrides the <code>horizontal_move_z</code> option specified in the config file.</p>
<p><code>BED_MESH_CALIBRATE [PROFILE=&lt;name&gt;] [METHOD=manual] [HORIZONTAL_MOVE_Z=&lt;value&gt;] [&lt;probe_parameter&gt;=&lt;value&gt;] [&lt;mesh_parameter&gt;=&lt;value&gt;] [ADAPTIVE=1] [ADAPTIVE_MARGIN=&lt;value&gt;]</code>: This command probes the bed using generated points specified by the parameters in the config. After probing, a mesh is generated and z-movement is adjusted according to the mesh. The mesh will be saved into a profile specified by the <code>PROFILE</code> parameter, or <code>default</code> if unspecified. See the PROBE command for details on the optional probe parameters. If METHOD=manual is specified then the manual probing tool is activated - see the MANUAL_PROBE command above for details on the additional commands available while this tool is active. The optional <code>HORIZONTAL_MOVE_Z</code> value overrides the <code>horizontal_move_z</code> option specified in the config file. If ADAPTIVE=1 is specified then the objects defined by the Gcode file being printed will be used to define the probed area. The optional <code>ADAPTIVE_MARGIN</code> value overrides the <code>adaptive_margin</code> option specified in the config file.</p>
<h4 id="bed_mesh_output">BED_MESH_OUTPUT<a class="headerlink" href="#bed_mesh_output" title="Permanent link">&para;</a></h4>
<p><code>BED_MESH_OUTPUT PGP=[&lt;0:1&gt;]</code>：該命令將目前探測到的 Z 值和目前網格的值輸出到終端。如果指定 PGP=1，則將bed_mesh產生的X、Y座標，以及它們關聯的指數，輸出到終端。</p>
<h4 id="bed_mesh_map">BED_MESH_MAP<a class="headerlink" href="#bed_mesh_map" title="Permanent link">&para;</a></h4>
@@ -4558,7 +4575,7 @@
<h4 id="bed_mesh_profile">BED_MESH_PROFILE<a class="headerlink" href="#bed_mesh_profile" title="Permanent link">&para;</a></h4>
<p><code>BED_MESH_PROFILE LOAD=&lt;名稱&gt; SAVE=&lt;名稱&gt; REMOVE=&lt;名稱&gt;</code>：此命令提供了網床配置管理功能。LOAD 將從與所提供的名稱相符的配置檔案中恢復網格狀態。SAVE 將會把目前的網格狀態儲存到與提供的名稱相符的配置檔案中。REMOVE（移除）將從永續性記憶體中刪除與所提供名稱相符的配置檔案。請注意，在 SAVE 或 REMOVE 操作后，必須發送SAVE_CONFIG G程式碼，以儲存變更到永續性記憶體。</p>
<h4 id="bed_mesh_offset">BED_MESH_OFFSET<a class="headerlink" href="#bed_mesh_offset" title="Permanent link">&para;</a></h4>
<p><code>BED_MESH_OFFSET [X=&lt;value&gt;] [Y=&lt;value&gt;]</code>。將X和/或Y的偏移量應用於網格查詢。這對具有多個獨立擠出頭的印表機很有用，因為偏移量對切換工具頭后產生正確的 Z 值調整是至關重要的。</p>
<p><code>BED_MESH_OFFSET [X=&lt;value&gt;] [Y=&lt;value&gt;] [ZFADE=&lt;value]</code>: Applies X, Y, and/or ZFADE offsets to the mesh lookup. This is useful for printers with independent extruders, as an offset is necessary to produce correct Z adjustment after a tool change. Note that a ZFADE offset does not apply additional z-adjustment directly, it is used to correct the <code>fade</code> calculation when a <code>gcode offset</code> has been applied to the Z axis.</p>
<h3 id="bed_screws">[bed_screws]<a class="headerlink" href="#bed_screws" title="Permanent link">&para;</a></h3>
<p>當啟用 <a href="Config_Reference.html#bed_screws">bed_screws config section</a> 時，以下命令可用（另請參閱 <a href="Manual_Level.html#adjusting-bed-leveling-screws">manual level guide</a>）。</p>
<h4 id="bed_screws_adjust">BED_SCREWS_ADJUST<a class="headerlink" href="#bed_screws_adjust" title="Permanent link">&para;</a></h4>
@@ -4644,10 +4661,6 @@
<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>: 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>
<p>此命令已棄用，並將在不久的將來被刪除。</p>
<h3 id="fan_generic">[fan_generic]<a class="headerlink" href="#fan_generic" title="Permanent link">&para;</a></h3>
<p>當啟用 <a href="Config_Reference.html#fan_generic">fan_generic config section</a> 時，以下命令可用。</p>
<h4 id="set_fan_speed">SET_FAN_SPEED<a class="headerlink" href="#set_fan_speed" title="Permanent link">&para;</a></h4>
@@ -4769,8 +4782,7 @@
<h3 id="output_pin">[output_pin]<a class="headerlink" href="#output_pin" title="Permanent link">&para;</a></h3>
<p>當啟用 <a href="Config_Reference.html#output_pin">output_pin config section</a> 時，以下命令可用。</p>
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">&para;</a></h4>
<p><code>SET_PIN PIN=config_name VALUE=&lt;value&gt; [CYCLE_TIME=&lt;cycle_time&gt;]</code>: Set the pin to the given output <code>VALUE</code>. VALUE should be 0 or 1 for "digital" output pins. For PWM pins, set to a value between 0.0 and 1.0, or between 0.0 and <code>scale</code> if a scale is configured in the output_pin config section.</p>
<p>Some pins (currently only "soft PWM" pins) support setting an explicit cycle time using the CYCLE_TIME parameter (specified in seconds). Note that the CYCLE_TIME parameter is not stored between SET_PIN commands (any SET_PIN command without an explicit CYCLE_TIME parameter will use the <code>cycle_time</code> specified in the output_pin config section).</p>
<p><code>SET_PIN PIN=config_name VALUE=&lt;value&gt;</code>: Set the pin to the given output <code>VALUE</code>. VALUE should be 0 or 1 for "digital" output pins. For PWM pins, set to a value between 0.0 and 1.0, or between 0.0 and <code>scale</code> if a scale is configured in the output_pin config section.</p>
<h3 id="palette2">[palette2]<a class="headerlink" href="#palette2" title="Permanent link">&para;</a></h3>
<p>啟用 <a href="Config_Reference.html#palette2">palette2 config section</a> 時，以下命令可用。</p>
<p>Palette列印通過在GCode檔案中嵌入特殊的OCodes（Omega Codes）來工作:</p>
@@ -4818,6 +4830,10 @@
<p><code>PROBE_CALIBRATE [SPEED=&lt;speed&gt;] [&lt;probe_parameter&gt;=&lt;value&gt;]</code>:執行一個對校準測頭的z_offset有用的輔助指令碼。有關可選測頭參數的詳細資訊，請參見PROBE命令。參見MANUAL_PROBE命令，瞭解SPEED參數和工具啟用時可用的附加命令的詳細資訊。請注意，PROBE_CALIBRATE命令使用速度變數在XY方向以及Z方向上移動。</p>
<h4 id="z_offset_apply_probe">Z_OFFSET_APPLY_PROBE<a class="headerlink" href="#z_offset_apply_probe" title="Permanent link">&para;</a></h4>
<p><code>Z_OFFSET_APPLY_PROBE</code>：將目前的Z 的 G 程式碼偏移量（就是 babystepping）從 probe 的 z_offset 中減去。該命令將持久化一個常用babystepping 微調值。需要執行 <code>SAVE_CONFIG</code>才能生效。</p>
<h3 id="pwm_cycle_time">[pwm_cycle_time]<a class="headerlink" href="#pwm_cycle_time" title="Permanent link">&para;</a></h3>
<p>The following command is available when a <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time config section</a> is enabled.</p>
<h4 id="set_pin_1">SET_PIN<a class="headerlink" href="#set_pin_1" title="Permanent link">&para;</a></h4>
<p><code>SET_PIN PIN=config_name VALUE=&lt;value&gt; [CYCLE_TIME=&lt;cycle_time&gt;]</code>: This command works similarly to <a href="#output_pin">output_pin</a> SET_PIN commands. The command here supports setting an explicit cycle time using the CYCLE_TIME parameter (specified in seconds). Note that the CYCLE_TIME parameter is not stored between SET_PIN commands (any SET_PIN command without an explicit CYCLE_TIME parameter will use the <code>cycle_time</code> specified in the pwm_cycle_time config section).</p>
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">&para;</a></h3>
<p>The query_adc module is automatically loaded.</p>
<h4 id="query_adc_1">QUERY_ADC<a class="headerlink" href="#query_adc_1" title="Permanent link">&para;</a></h4>
@@ -4909,7 +4925,7 @@
<h3 id="toolhead">[toolhead]<a class="headerlink" href="#toolhead" title="Permanent link">&para;</a></h3>
<p>模組toolhead已自動載入.</p>
<h4 id="set_velocity_limit">SET_VELOCITY_LIMIT<a class="headerlink" href="#set_velocity_limit" title="Permanent link">&para;</a></h4>
<p><code>SET_VELOCITY_LIMIT [VELOCITY=&lt;值&gt;] [ACCEL=&lt;值&gt;] [ACCEL_TO_DECEL=&lt;值&gt;] [SQUARE_CORNER_VELOCITY=&lt;值&gt;]</code>：修改印表機速度限制。</p>
<p><code>SET_VELOCITY_LIMIT [VELOCITY=&lt;value&gt;] [ACCEL=&lt;value&gt;] [MINIMUM_CRUISE_RATIO=&lt;value&gt;] [SQUARE_CORNER_VELOCITY=&lt;value&gt;]</code>: This command can alter the velocity limits that were specified in the printer config file. See the <a href="Config_Reference.html#printer">printer config section</a> for a description of each parameter.</p>
<h3 id="tuning_tower">[tuning_tower]<a class="headerlink" href="#tuning_tower" title="Permanent link">&para;</a></h3>
<p>模組 tuning_tower已自動載入.</p>
<h4 id="tuning_tower_1">TUNING_TOWER<a class="headerlink" href="#tuning_tower_1" title="Permanent link">&para;</a></h4>
@@ -4935,11 +4951,6 @@
<p><code>SDCARD_PRINT_FILE FILENAME=&lt;檔名&gt;</code>：載入一個檔案並開始 SD 列印.</p>
<h4 id="sdcard_reset_file">SDCARD_RESET_FILE<a class="headerlink" href="#sdcard_reset_file" title="Permanent link">&para;</a></h4>
<p><code>SDCARD_RESET_FILE</code>：解除安裝檔案並清除SD狀態。</p>
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">&para;</a></h3>
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
section</a> is enabled.</p>
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">&para;</a></h4>
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=&lt;value&gt;]</code>: Initiates the X twist calibration wizard. <code>SAMPLE_COUNT</code> specifies the number of points along the X axis to calibrate at and defaults to 3.</p>
<h3 id="z_thermal_adjust">[z_thermal_adjust]<a class="headerlink" href="#z_thermal_adjust" title="Permanent link">&para;</a></h3>
<p>The following commands are available when the <a href="Config_Reference.html#z_thermal_adjust">z_thermal_adjust config section</a> is enabled.</p>
<h4 id="set_z_thermal_adjust">SET_Z_THERMAL_ADJUST<a class="headerlink" href="#set_z_thermal_adjust" title="Permanent link">&para;</a></h4>

40
zh-Hant/Kinematics.html
View File

@@ -983,8 +983,8 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#_4" class="md-nav__link">
預計算結果平滑
<a href="#minimum-cruise-ratio" class="md-nav__link">
Minimum cruise ratio
</a>
</li>
@@ -995,7 +995,7 @@
</li>
<li class="md-nav__item">
<a href="#_5" class="md-nav__link">
<a href="#_4" class="md-nav__link">
生成步驟
</a>
@@ -1017,21 +1017,21 @@
</li>
<li class="md-nav__item">
<a href="#_6" class="md-nav__link">
<a href="#_5" class="md-nav__link">
三角洲機型
</a>
</li>
<li class="md-nav__item">
<a href="#_7" class="md-nav__link">
<a href="#_6" class="md-nav__link">
步進電機加速度限制
</a>
</li>
<li class="md-nav__item">
<a href="#_8" class="md-nav__link">
<a href="#_7" class="md-nav__link">
擠出機動作
</a>
@@ -1428,8 +1428,8 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#_4" class="md-nav__link">
預計算結果平滑
<a href="#minimum-cruise-ratio" class="md-nav__link">
Minimum cruise ratio
</a>
</li>
@@ -1440,7 +1440,7 @@
</li>
<li class="md-nav__item">
<a href="#_5" class="md-nav__link">
<a href="#_4" class="md-nav__link">
生成步驟
</a>
@@ -1462,21 +1462,21 @@
</li>
<li class="md-nav__item">
<a href="#_6" class="md-nav__link">
<a href="#_5" class="md-nav__link">
三角洲機型
</a>
</li>
<li class="md-nav__item">
<a href="#_7" class="md-nav__link">
<a href="#_6" class="md-nav__link">
步進電機加速度限制
</a>
</li>
<li class="md-nav__item">
<a href="#_8" class="md-nav__link">
<a href="#_7" class="md-nav__link">
擠出機動作
</a>
@@ -1540,13 +1540,15 @@
<div class="highlight"><pre><span></span><code>end_velocity^2 = start_velocity^2 + 2*accel*move_distance
</code></pre></div>
<h3 id="_4">預計算結果平滑<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h3>
<h3 id="minimum-cruise-ratio">Minimum cruise ratio<a class="headerlink" href="#minimum-cruise-ratio" title="Permanent link">&para;</a></h3>
<p>Klipper 實現了一種用於平滑短距離之字形移動的機制。參考以下移動：</p>
<p><img alt="zigzag" src="img/zigzag.svg.png" /></p>
<p>在上述情況下，從加速到減速的頻繁變化會導致機器振動，從而對機器造成壓力並增加噪音。為了減少這種情況，Klipper 跟踪常規移動加速度以及虛擬“加速到減速”率。使用這個系統，這些短的“之字形”移動的最高速度被限制為平滑打印機運動：</p>
<p>In the above, the frequent changes from acceleration to deceleration can cause the machine to vibrate which causes stress on the machine and increases the noise. Klipper implements a mechanism to ensure there is always some movement at a cruising speed between acceleration and deceleration. This is done by reducing the top speed of some moves (or sequence of moves) to ensure there is a minimum distance traveled at cruising speed relative to the distance traveled during acceleration and deceleration.</p>
<p>Klipper implements this feature by tracking both a regular move acceleration as well as a virtual "acceleration to deceleration" rate:</p>
<p><img alt="smoothed" src="img/smoothed.svg.png" /></p>
<p>具體來說，代碼計算每次移動的速度，如果它被限制在這個虛擬的“加速到減速”率（默認情況下為正常加速率的一半）。在上圖中，灰色虛線表示第一步的虛擬加速度。如果使用此虛擬加速度無法達到其全巡航速度，則其最高速度將降低到在此虛擬加速度下可以達到的最大速度。對於大多數移動，限制將等於或高於移動的現有限制，並且不會引起行為變化。然而，對於短的之字形移動，這個限制會降低最高速度。請注意，它不會改變移動中的實際加速度 - 移動將繼續使用正常加速方案，直至其調整後的最高速度。</p>
<h2 id="_5">生成步驟<a class="headerlink" href="#_5" title="Permanent link">&para;</a></h2>
<p>Specifically, the code calculates what the velocity of each move would be if it were limited to this virtual "acceleration to deceleration" rate. In the above picture the dashed gray lines represent this virtual acceleration rate for the first move. If a move can not reach its full cruising speed using this virtual acceleration rate then its top speed is reduced to the maximum speed it could obtain at this virtual acceleration rate.</p>
<p>For most moves the limit will be at or above the move's existing limits and no change in behavior is induced. For short zigzag moves, however, this limit reduces the top speed. Note that it does not change the actual acceleration within the move - the move continues to use the normal acceleration scheme up to its adjusted top-speed.</p>
<h2 id="_4">生成步驟<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>
<p>一旦前瞻過程完成，給定移動的打印頭移動是完全已知的（時間、開始位置、結束位置、每個點的速度），並且可以生成移動的步進時間。此過程在 Klipper 代碼中的“運動學類”中完成。在這些運動學類之外，一切都以毫米、秒和笛卡爾坐標空間為單位進行跟踪。運動學類的任務是將通用坐標系轉換為特定打印機的硬件細節。</p>
<p>Klipper 使用 <a href="https://en.wikipedia.org/wiki/Root-finding_algorithm">iterative solver</a> 為每個步進器生成步進時間。該代碼包含計算每個時刻頭部理想XYZ坐標的公式，並且它具有根據這些XYZ坐標計算理想步進器位置的動作公式。通過這些公式，Klipper 可以確定步進器應該在每個步進位置的理想時間。然後在這些計算的時間安排給定的步驟。</p>
<p>確定在恆定加速度下移動應該行進多遠的關鍵公式是：</p>
@@ -1578,7 +1580,7 @@ stepper_b_position = cartesian_x_position - cartesian_y_position
stepper_z_position = cartesian_z_position
</code></pre></div>
<h3 id="_6">三角洲機型<a class="headerlink" href="#_6" title="Permanent link">&para;</a></h3>
<h3 id="_5">三角洲機型<a class="headerlink" href="#_5" title="Permanent link">&para;</a></h3>
<p>三角洲機型的動作生成基於畢達哥拉斯定理：</p>
<div class="highlight"><pre><span></span><code>stepper_position = (sqrt(arm_length^2
@@ -1587,10 +1589,10 @@ stepper_z_position = cartesian_z_position
+ cartesian_z_position)
</code></pre></div>
<h3 id="_7">步進電機加速度限制<a class="headerlink" href="#_7" title="Permanent link">&para;</a></h3>
<h3 id="_6">步進電機加速度限制<a class="headerlink" href="#_6" title="Permanent link">&para;</a></h3>
<p>使用三角洲機型時，在XYZ空間中加速的動作可能需要特定步進電機上的加速度大於運動的加速度。當步進臂比垂直更水平並且運動線通過步進器塔附近時，可能會發生這種情況。儘管這些移動可能需要一個大於打印機配置的最大移動加速度的步進電機加速度，但該步進電機移動的有效質量會更小。因此，更高的步進加速度不會導致顯著更高的步進扭矩，因此被認為是無害的。</p>
<p>但是，為避免極端情況，Klipper 將步進加速度的最大上限設置為打印機配置的最大移動加速度的三倍。 （類似地，步進器的最大速度被限制為最大移動速度的三倍。）為了強制執行此限制，在構建包絡的最邊緣（步進器臂可能幾乎水平）的移動將具有較低的最大加速度和速度。</p>
<h3 id="_8">擠出機動作<a class="headerlink" href="#_8" title="Permanent link">&para;</a></h3>
<h3 id="_7">擠出機動作<a class="headerlink" href="#_7" title="Permanent link">&para;</a></h3>
<p>Klipper 在其自己的動作類別中實現了擠出機動作。由於每個打印頭移動的時間和速度對於每次移動都是完全已知的，因此可以獨立於打印頭移動的步進時間計算來計算擠出機的步進時間。</p>
<p>基本的擠出機運動很容易計算。步時間生成使用與笛卡爾機器人相同的公式：</p>
<div class="highlight"><pre><span></span><code>stepper_position = requested_e_position

7
zh-Hant/Measuring_Resonances.html
View File

@@ -2144,7 +2144,7 @@ GND+SCL
<h3 id="_5">軟體設定<a class="headerlink" href="#_5" title="Permanent link">&para;</a></h3>
<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
sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-dev
</code></pre></div>
<p>Next, in order to install NumPy in the Klipper environment, run the command:</p>
@@ -2429,6 +2429,11 @@ max_smoothing: 0.25 # an example
<p>由於輸入整形器可以在零件中創建一些平滑，尤其是在高加速度時，您仍然需要選擇不會在打印零件中創建太多平滑的“max_accel”值。校準腳本提供了“max_accel”參數的估計值，該參數不應產生過多的平滑。請注意，校準腳本顯示的“max_accel”只是理論上的最大值，在該最大值時，各個整形器仍然能夠工作而不會產生過多的平滑。絕對不建議為打印設置此加速。您的打印機能夠承受的最大加速度取決於其機械性能和所用步進電機的最大扭矩。因此，建議在 <code>[printer]</code> 部分設置不超過 X 和 Y 軸的估計值的 <code>max_accel</code>，可能有一些保守的安全餘量。</p>
<p>或者，按照輸入整形器調整指南的 <a href="Resonance_Compensation.html#selecting-max_accel">this</a> 部分並打印測試模型以實驗性地選擇“max_accel”參數。</p>
<p>相同的注意事項適用於使用 <code>SHAPER_CALIBRATE</code> 命令的輸入整形器 <a href="#input-shaper-auto-calibration">auto-calibration</a>：自動校准後仍然需要選擇正確的 <code>max_accel</code> 值，建議加速度限制不會自動應用。</p>
<p>Keep in mind that the maximum acceleration without too much smoothing depends on the <code>square_corner_velocity</code>. The general recommendation is not to change it from its default value 5.0, and this is the value used by default by the <code>calibrate_shaper.py</code> script. If you did change it though, you should inform the script about it by passing <code>--square_corner_velocity=...</code> parameter, e.g.</p>
<div class="highlight"><pre><span></span><code>~/klipper/scripts/calibrate_shaper.py /tmp/resonances_x_*.csv -o /tmp/shaper_calibrate_x.png --square_corner_velocity=10.0
</code></pre></div>
<p>so that it can calculate the maximum acceleration recommendations correctly. Note that the <code>SHAPER_CALIBRATE</code> command already takes the configured <code>square_corner_velocity</code> parameter into account, and there is no need to specify it explicitly.</p>
<p>如果您正在重新校準整形器，並且建議的整形器配置報告的平滑度與您在之前校準期間得到的幾乎相同，則可以跳過此步驟。</p>
<h3 id="_10">測試自定義軸<a class="headerlink" href="#_10" title="Permanent link">&para;</a></h3>
<p><code>TEST_RESONANCES</code> 命令支持自定義軸。雖然這對於輸入整形器校準並不是很有用，但它可用於深入研究打印機共振並檢查皮帶張力等。</p>

3
zh-Hant/Multi_MCU_Homing.html
View File

@@ -1307,7 +1307,8 @@
<p>過度運動的可能成因是，控制步進電機運動的微控制器 和 監控限位開關的微控制器之間的資訊傳遞存在延時。Klipper在設計上將延時壓縮到25ms以下。（在使用複數微控制器時，各個微控制器會通過週期性發送狀態資訊確定與上位機的延時不超過25ms。）</p>
<p>例如，如果歸零速度為10 mm/s則可能的過運動的量為0.25mm（10mm/s * .025s == 0.250mm）。在進行復數微控制器的歸零配置時應充分考慮過運動的影響。使用低速歸零可以有效減少過運動。</p>
<p>步進電機的過運動不太可能對歸零和探高的精度產生很大的影響。Klippe程式碼上會考慮通訊延時校正歸零的結果。但是，過運動對硬體穩固性有要求，因為過運動發生時有可能會損壞硬體。</p>
<p>對配置有複數微控制器歸零的Klipper，如在進行歸零時遭遇通訊錯誤，軟體將會拋出"Communication timeout during homing"（歸零時，控制器通訊超時）錯誤資訊。</p>
<p>In order to use this "multi-mcu homing" capability the hardware must have predictably low latency between the host computer and all of the micro-controllers. Typically the round-trip time must be consistently less than 10ms. High latency (even for short periods) is likely to result in homing failures.</p>
<p>Should high latency result in a failure (or if some other communication issue is detected) then Klipper will raise a "Communication timeout during homing" error.</p>
<p>要注意，當一個軸由多個步進電機控制（如<code>stepper_z</code>和<code>stepper_z1</code>），這些電機必須連線到同一微控制器上以實現複數微控制器歸零。詳細來說，即Z限位開關位於微控制器1， <code>stepper_z</code>連線到微控制器2，則<code>stepper_z1</code>必須連線到微控制器2。</p>

2
zh-Hant/Probe_Calibrate.html
View File

@@ -1429,7 +1429,7 @@
<p>準確的探針 z 偏移(z_offset)是高質量列印的基礎。z 偏移是探針觸發時探針和噴嘴之間的高度差。Klipper 中的 <code>PROBE_CALIBRATE</code>（探針校準）工具可用於測量這個值——首先，該工具會執行一次自動探測以獲取探針的 z 觸發位置，然後需要手動調整Z座標以獲取噴嘴碰觸到熱床時的 z 高度。然後將根據這些測量值計算探針的 z 偏移。</p>
<p>首先進行三軸的歸零，然後將噴嘴移動到熱床的中央位置。轉到OctoPrint的「命令列（Terminal）」子頁，輸入 <code>PROBE_CALIBRATE</code>以啟動z_offset校準工具。</p>
<p>工具首先會令探針進行一次自動探測，獲取觸發探針的z位置，之後，控制噴嘴上升，並將噴嘴的X/Y位置移動到探針對應位置上，並開始手動調平流程。如果噴嘴沒有移動到探針進行自動探測的位置，輸入<code>ABORT</code>以停止手動調平，並上文根據X、y偏移校準流程進行探針X、Y校準。</p>
<p>進入手動調平的過程后，請按照<a href="Bed_Level.html#the-paper-test">「紙片測試」</a>的流程，確定在探針探測位置上，噴嘴與熱床之間的距離。完成上述流程后，使用<code>ACCEPT</code>命令將測量到的z_offset應用到目前配置，如需要儲存配置到檔案，則鍵入：</p>
<p>Once the manual probe tool starts, follow the steps described at <a href="Bed_Level.html#the-paper-test">"the paper test"</a> to determine the actual distance between the nozzle and bed at the given location. Once those steps are complete one can <code>ACCEPT</code> the position and save the results to the config file with:</p>
<div class="highlight"><pre><span></span><code>SAVE_CONFIG
</code></pre></div>

8
zh-Hant/Resonance_Compensation.html
View File

@@ -1616,7 +1616,7 @@
<p>首先，測量<strong>振紋頻率</strong>。</p>
<ol>
<li>如果 <code>square_corner_velocity</code> 參數已更改，請將其恢復為 5.0。使用input shaper時不建議增加它，因為它會導致零件更平滑 - 最好使用更高的加速度值。</li>
<li>通過發出以下命令增加 <code>max_accel_to_decel</code>：<code>SET_VELOCITY_LIMIT ACCEL_TO_DECEL=7000</code></li>
<li>Disable the <code>miminum_cruise_ratio</code> feature by issuing the following command: <code>SET_VELOCITY_LIMIT MINIMUM_CRUISE_RATIO=0</code></li>
<li>禁用Pressure Advance：<code>SET_PRESSURE_ADVANCE ADVANCE=0</code></li>
<li>如果你已經將<code>[input_shaper]</code>分段新增到print.cfg中，執行<code>SET_INPUT_SHAPER SHAPER_FREQ_X=0 SHAPER_FREQ_Y=0</code>命令。如果你得到"未知命令"錯誤，此時你可以安全地忽略它，繼續進行測量。</li>
<li>執行命令： <code>TUNING_TOWER COMMAND=SET_VELOCITY_LIMIT PARAMETER=ACCEL START=1500 STEP_DELTA=500 STEP_HEIGHT=5</code> 基本上，我們嘗試通過設置不同的大加速度值來使環紋更加明顯。此命令將從 1500 mm/sec^2 開始每 5 mm 增加加速度：1500 mm/sec^2、2000 mm/sec^2、2500 mm/sec^2 等等，直到 7000 mm/sec^2最後一個區域。</li>
@@ -1657,7 +1657,7 @@ shaper_freq_y: ... # frequency for the Y mark of the test model
<p>打印環形測試模型如下：</p>
<ol>
<li>重啟固件：<code>RESTART</code></li>
<li>準備測試：<code>SET_VELOCITY_LIMIT ACCEL_TO_DECEL=7000</code></li>
<li>Prepare for test: <code>SET_VELOCITY_LIMIT MINIMUM_CRUISE_RATIO=0</code></li>
<li>禁用Pressure Advance：<code>SET_PRESSURE_ADVANCE ADVANCE=0</code></li>
<li>執行：<code>SET_INPUT_SHAPER SHAPER_TYPE=MZV</code></li>
<li>執行命令：<code>TUNING_TOWER COMMAND=SET_VELOCITY_LIMIT PARAMETER=ACCEL START=1500 STEP_DELTA=500 STEP_HEIGHT=5</code></li>
@@ -1695,7 +1695,7 @@ shaper_type: mzv
<p>請注意，使用環紋測試模型的諧振頻率測量精度足以滿足大多數目的，因此不建議進一步調整。如果您仍想嘗試仔細檢查您的結果（例如，如果您在使用您選擇的input shaper打印一個測試模型後仍然看到一些環紋，您選擇的input shaper與您之前測量的頻率相同），您可以按照本文中的步驟操作部分。請注意，如果您在啟用 [input_shaper] 後看到不同頻率的環紋，則本節將無濟於事。</p>
<p>假設您已使用建議的參數對環紋模型進行切片，請針對 X 軸和 Y 軸中的每一個完成以下步驟：</p>
<ol>
<li>準備測試：<code>SET_VELOCITY_LIMIT ACCEL_TO_DECEL=7000</code></li>
<li>Prepare for test: <code>SET_VELOCITY_LIMIT MINIMUM_CRUISE_RATIO=0</code></li>
<li>確保Pressure Advance被禁用：<code>SET_PRESSURE_ADVANCE ADVANCE=0</code></li>
<li>執行：<code>SET_INPUT_SHAPER SHAPER_TYPE=ZV</code></li>
<li>從具有您選擇的 input shaper的現有環紋測試模型中選擇顯示環紋足夠好的加速度，並將其設置為：<code>SET_VELOCITY_LIMIT ACCEL=...</code></li>
@@ -1716,7 +1716,7 @@ shaper_type: mzv
<p>要進行調整，請將空的 <code>[input_shaper]</code> 部分添加到您的 <code>printer.cfg</code>。然後，假設您已使用建議的參數對環紋模型進行切片，按如下方式打印測試模型 3 次。第一次，在打印之前，運行</p>
<ol>
<li><code>RESTART</code></li>
<li><code>SET_VELOCITY_LIMIT ACCEL_TO_DECEL=7000</code></li>
<li><code>SET_VELOCITY_LIMIT MINIMUM_CRUISE_RATIO=0</code></li>
<li><code>SET_PRESSURE_ADVANCE ADVANCE=0</code></li>
<li><code>SET_INPUT_SHAPER SHAPER_TYPE=2HUMP_EI SHAPER_FREQ_X=60 SHAPER_FREQ_Y=60</code></li>
<li><code>TUNING_TOWER COMMAND=SET_VELOCITY_LIMIT PARAMETER=ACCEL START=1500 STEP_DELTA=500 STEP_HEIGHT=5</code></li>

2
zh-Hant/Skew_Correction.html
View File

@@ -1409,7 +1409,7 @@
<p>糾正偏斜的第一步是沿著你要糾正的平面列印一個<a href="https://www.thingiverse.com/thing:2563185/files">校準物件</a>。還有一個<a href="https://www.thingiverse.com/thing:2972743">校準物件</a>包括了一個模型中的所有平面。你需要旋轉這個物件，使角A朝向平面的原點。</p>
<p>不要在這次列印中應用傾斜校正。你可以通過從printer.cfg中刪除<code>[skew_correction]</code>模組或發送 <code>SET_SKEW CLEAR=1</code>G-Code 來實現。</p>
<h2 id="_3">進行測量<a class="headerlink" href="#_3" title="Permanent link">&para;</a></h2>
<p><code>[skew_correcton]</code> 模組需要三次對校準平面的測量值；從角 A 到角 C 的距離，從角 B 到角 D 的距離，以及從角 A 到角 D 的距離。當測量距離 AD 時，不包括一些測試物件的角上的平面。</p>
<p>The <code>[skew_correction]</code> module requires 3 measurements for each plane you want to correct; the length from Corner A to Corner C, the length from Corner B to Corner D, and the length from Corner A to Corner D. When measuring length AD do not include the flats on the corners that some test objects provide.</p>
<p><img alt="skew_lengths" src="img/skew_lengths.png" /></p>
<h2 id="_4">配置偏斜<a class="headerlink" href="#_4" title="Permanent link">&para;</a></h2>
<p>確保 <code>[skew_correction]</code> 已經在 printer.cfg 中。現在可以使用<code>SET_SKEW</code> G-Code 來配置 skew_correcton。例如，如果對 XY 平面測量的距離結果如下：</p>

21
zh-Hant/Status_Reference.html
View File

@@ -1003,6 +1003,13 @@
probe
</a>
</li>
<li class="md-nav__item">
<a href="#pwm_cycle_time" class="md-nav__link">
pwm_cycle_time
</a>
</li>
<li class="md-nav__item">
@@ -1820,6 +1827,13 @@
probe
</a>
</li>
<li class="md-nav__item">
<a href="#pwm_cycle_time" class="md-nav__link">
pwm_cycle_time
</a>
</li>
<li class="md-nav__item">
@@ -2167,6 +2181,11 @@
<li><code>last_query</code>：如果探針在上一個 QUERY_PROBE 命令期間報告為"已觸發"，則返回 True。請注意，如果在宏中使用它，根據模板展開的順序，必須在包含此引用的宏之前執行 QUERY_PROBE 命令。</li>
<li><code>last_z_result</code>：返回上一次 PROBE 命令的結果 Z 值。請注意，由於模板展開的順序，在宏中使用時必須在包含此引用的宏之前執行 PROBE（或類似）命令。</li>
</ul>
<h2 id="pwm_cycle_time">pwm_cycle_time<a class="headerlink" href="#pwm_cycle_time" title="Permanent link">&para;</a></h2>
<p>The following information is available in <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time some_name</a> objects:</p>
<ul>
<li><code>value</code>：由<code>SET_PIN</code>指令設定的引腳「值」。</li>
</ul>
<h2 id="quad_gantry_level">quad_gantry_level<a class="headerlink" href="#quad_gantry_level" title="Permanent link">&para;</a></h2>
<p><code>quad_gantry_level</code> 對像提供了以下資訊（如果定義了 quad_gantry_level，則該對象可用）：</p>
<ul>
@@ -2242,7 +2261,7 @@
<li><code>homed_axes</code>：目前被認為處於「已歸位」狀態的車軸。這是一個包含一個或多個"x"、"y"、"z"的字串。</li>
<li><code>axis_minimum</code>、<code>axis_maximum</code>：歸位后的軸的行程限制（毫米）。可以訪問此極限值的 x、y、z 份量（例如，<code>axis_minimum.x</code>、<code>axis_maximum.z</code>）。</li>
<li>For Delta printers the <code>cone_start_z</code> is the max z height at maximum radius (<code>printer.toolhead.cone_start_z</code>).</li>
<li><code>max_velocity</code>、<code>max_accel</code>、<code>max_accel_to_decel</code>和<code>square_corner_velocity</code>：目前生效的印表機限制。如果 <code>SET_VELOCITY_LIMIT</code>（或 <code>M204</code>）命令在執行時改變它們，這些值可能與配置檔案設定不同。</li>
<li><code>max_velocity</code>, <code>max_accel</code>, <code>minimum_cruise_ratio</code>, <code>square_corner_velocity</code>: The current printing limits that are in effect. This may differ from the config file settings if a <code>SET_VELOCITY_LIMIT</code> (or <code>M204</code>) command alters them at run-time.</li>
<li><code>stalls</code>：由於工具頭移動速度快于從 G 程式碼輸入讀取的移動速度，因此印表機必須暫停的總次數（自上次重新啟動以來）。</li>
</ul>
<h2 id="dual_carriage">dual_carriage<a class="headerlink" href="#dual_carriage" title="Permanent link">&para;</a></h2>

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

Binary file not shown.

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

File diff suppressed because one or more lines are too long

106
zh-Hant/sitemap.xml
View File

@@ -2,267 +2,267 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2024-04-27</lastmod>
<lastmod>2024-04-28</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>

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

Binary file not shown.