Deploying to gh-pages from @ Klipper3d/klipper@cf3b0475da 🚀
This commit is contained in:
KevinOConnor
@@ -711,6 +711,33 @@
|
||||
薪酬使用概览
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="薪酬使用概览">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1384,6 +1411,33 @@
|
||||
薪酬使用概览
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="薪酬使用概览">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1420,19 +1474,43 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
|
||||
<blockquote>
|
||||
<p><strong>提示：</strong>请确保正确设置<a href="Config_Reference.html#Probe">Probe X和Y Offset</a>，因为它们对校准影响很大。</p>
|
||||
</blockquote>
|
||||
<h3 id="basic-usage-x-axis-calibration">Basic Usage: X-Axis Calibration<a class="headerlink" href="#basic-usage-x-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<ol>
|
||||
<li>设置好[AXIS_TWIST_COMPOMENT]模块后，执行<code>AXIS_TWIST_COMCOMPATION_CALIBRATE</code></li>
|
||||
<li>After setting up the <code>[axis_twist_compensation]</code> module, run:</li>
|
||||
</ol>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE
|
||||
</code></pre></div>
|
||||
|
||||
<p>This command will calibrate the X-axis by default. - The calibration wizard will prompt you to measure the probe Z offset at several points along the bed. - By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=<value></code></p>
|
||||
<ol>
|
||||
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).</li>
|
||||
<li>
|
||||
<p><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</p>
|
||||
<ul>
|
||||
<li>校准向导将提示您在床上的几个点上测量探头Z偏移量</li>
|
||||
<li>该校准默认为3分，但您可以使用选项<code>SAMPLE_COUNT=</code>来使用不同的数字。</li>
|
||||
<li><a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a></li>
|
||||
<li><a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a></li>
|
||||
</ul>
|
||||
<ol>
|
||||
<li><a href="Probe_Calibrate.html#calibrating-probe-z-offset">调整您的Z offset</a></li>
|
||||
<li>执行自动/探针式床铺操作，如<a href="G-Codes.html#螺旋倾斜调整">螺旋倾斜调整</a>、<a href="G-Codes.html#z_倾斜调整">Z倾斜调整</a>等</li>
|
||||
<li>原点所有轴，然后根据需要执行<a href="Bed_Mesh.html">Bed Mesh</a></li>
|
||||
<li>执行测试打印，然后根据需要执行任何<a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a></li>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Finalize the Setup:</strong></p>
|
||||
<ul>
|
||||
<li>Home all axes, and perform a <a href="Bed_Mesh.html">Bed Mesh</a> if necessary.</li>
|
||||
<li>Run a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> if needed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h3 id="for-y-axis-calibration">For Y-Axis Calibration<a class="headerlink" href="#for-y-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<p>The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y
|
||||
</code></pre></div>
|
||||
|
||||
<p>This will guide you through the same measuring process as for the X-axis.</p>
|
||||
<h3 id="automatic-calibration-for-both-axes">Automatic Calibration for Both Axes<a class="headerlink" href="#automatic-calibration-for-both-axes" title="Permanent link">¶</a></h3>
|
||||
<p>To perform automatic calibration for both the X and Y axes without manual intervention, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
|
||||
</code></pre></div>
|
||||
|
||||
<p>In this mode, the calibration process will run for both axes automatically.</p>
|
||||
<blockquote>
|
||||
<p><strong>提示：</strong>床温、喷嘴温度和尺寸似乎对校准过程没有影响。</p>
|
||||
</blockquote>
|
||||
|
||||
@@ -1968,7 +1968,7 @@ fade_target: 0
|
||||
<li><code>fade_target: 0</code> <em>默认值：网格的平均 Z 值</em> <code>fade_target</code> 可以被视为在淡化完成后应用于整个床面的额外 Z 偏移量。一般来说，我们希望这个值为 0，但有些情况下不应该是这样的。例如，假设您在床上的归位位置是一个异常值，比床面的平均探测高度低 0.2 毫米。如果 <code>fade_target</code> 为 0，淡化将会使整个床面平均降低 0.2 毫米。通过将 <code>fade_target</code> 设置为 0.2，淡化区域将会提高到 0.2 毫米，但是，床面的其余部分将保持原大小。通常最好将 <code>fade_target</code> 留在配置中，以便使用网格的平均高度，但是如果您想在床面的特定部分上打印，则可能需要手动调整淡化目标。</li>
|
||||
</ul>
|
||||
<h3 id="_9">配置零点参考位置<a class="headerlink" href="#_9" title="Permanent link">¶</a></h3>
|
||||
<p>许多探头容易出现“漂移”，即：由于热或干扰而引起的探头不准确。这使得计算探测器的z偏移量具有挑战性，特别是在不同床温的情况下。因此，一些打印机使用端止器来定位Z轴，并使用探头来校准网格。在这种配置中，可以对网格进行偏移，从而使(X，Y)<code>参考位置‘应用零点调整。‘参考位置’应该是床上进行[Z_ENDSTOP_CALIBRATE](./Manual_Level#calibrating-a-z-endstop)试纸测试的位置。Bed_Mesh模块提供了</code>ZERO_REFERENCE_Position`选项来指定该坐标：</p>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="Manual_Level.html#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<div class="highlight"><pre><span></span><code>[bed_mesh]
|
||||
speed: 120
|
||||
horizontal_move_z: 5
|
||||
|
||||
@@ -1195,6 +1195,13 @@
|
||||
SAMD51 步速率基准测试
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1205,8 +1212,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040" class="md-nav__link">
|
||||
RP2040 步速率基准测试
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -1613,6 +1620,13 @@
|
||||
SAMD51 步速率基准测试
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1623,8 +1637,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040" class="md-nav__link">
|
||||
RP2040 步速率基准测试
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -2122,6 +2136,34 @@ finalize_config crc=0
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="same70-step-rate-benchmark">SAME70 step rate benchmark<a class="headerlink" href="#same70-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the SAME70:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=PC18 dir_pin=PB5 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=PC16 dir_pin=PD10 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=2 step_pin=PC28 dir_pin=PA4 invert_step=-1 step_pulse_ticks=0
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>34e9ea55</code> with gcc version <code>arm-none-eabi-gcc (NixOS 10.3-2021.10) 10.3.1</code> on a SAME70Q20B micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>same70</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1个步进电机</td>
|
||||
<td>45</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3个步进电机</td>
|
||||
<td>190</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="ar100">AR100 步进率基准测试<a class="headerlink" href="#ar100" title="Permanent link">¶</a></h3>
|
||||
<p>以下配置顺序被用于AR100 CPU（全志A64）：</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
@@ -2131,7 +2173,7 @@ config_stepper oid=2 step_pin=PL12 dir_pin=PE16 invert_step=-1 step_pulse_ticks=
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>该测试最后一次运行在提交<code>08d037c6</code> ，gcc版本<code>or1k-linux-musl-gcc（GCC）9.2.0</code> ，全志A64-H微控制器上进行。</p>
|
||||
<p>The test was last run on commit <code>b7978d37</code> with gcc version <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> on an Allwinner A64-H micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -2150,8 +2192,8 @@ finalize_config crc=0
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="rp2040">RP2040 步速率基准测试<a class="headerlink" href="#rp2040" title="Permanent link">¶</a></h3>
|
||||
<p>RP2040 上使用以下配置序列：</p>
|
||||
<h3 id="rpxxxx-step-rate-benchmark">RPxxxx step rate benchmark<a class="headerlink" href="#rpxxxx-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040 and RP2350:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=gpio25 dir_pin=gpio3 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=gpio26 dir_pin=gpio4 invert_step=-1 step_pulse_ticks=0
|
||||
@@ -2159,11 +2201,11 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>该测试最后一次在 Raspberry Pi Pico 板上使用 gcc 版本 <code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code>和提交 <code>59314d99</code> 运行。</p>
|
||||
<p>The test was last run on commit <code>f6718291</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2040</th>
|
||||
<th>rp2040 (*)</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
@@ -2178,6 +2220,25 @@ finalize_config crc=0
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2350</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1个步进电机</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3个步进电机</td>
|
||||
<td>169</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 125Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM core cycles.</p>
|
||||
<h3 id="linux-mcu">Linux MCU 步速率基准测试<a class="headerlink" href="#linux-mcu" title="Permanent link">¶</a></h3>
|
||||
<p>树莓派上使用以下配置序列：</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
@@ -2311,9 +2372,15 @@ get_uptime
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2040 (USB)</td>
|
||||
<td>873K</td>
|
||||
<td>c5667193</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2350 (USB)</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
@@ -1580,7 +1580,7 @@
|
||||
<li>参考位于klippy/kinematics/目录已有的运动学类。动力学类旨在将一个笛卡尔坐标系中的运动转化为各个步进电机的运动。建议复制已有的代码，并在其基础上进行修改。</li>
|
||||
<li>若需要的运动学方程未被Klipper涵盖，则应使用C语言实现新动力学体系中各个步进电机的位置方程（见klippy/chelper/，如kin_cart.c, kin_corexy.c, and kin_delta.c）。位置方程中应调用<code>move_get_coord()</code>以将运动的时间点（单位 ：秒）转化为对应的笛卡尔坐标位置（单位：毫米），进而计算目标步进电机运动目标位置（单位：毫米）。</li>
|
||||
<li>在新的运动学类中实现<code>calc_position</code>方法。该方法将通过各个步进电机的位置计算笛卡尔坐标系下的打印头位置；同时该方法通常只在回零和z探测时使用，因此无需过分追求效率。</li>
|
||||
<li>之后实现<code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>set_position()</code>方法。这些函数用于特定的运动学检查。在开发的初期，可以直接使用已有代码。</li>
|
||||
<li>Other methods. Implement the <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>clear_homing_state()</code>, and <code>set_position()</code> methods. These functions are typically used to provide kinematic specific checks. However, at the start of development one can use boiler-plate code here.</li>
|
||||
<li>添加测试实例。创建一个G代码文件，其中包含一系列的运动命令用于测试新增的运动学模型。 按照<a href="Debugging.html">调试文档</a>将该G代码文件转换为微控制器命令。在遭遇困难状况和检查数据传递相当有用。</li>
|
||||
</ol>
|
||||
<h2 id="_8">移植到新的微控制器<a class="headerlink" href="#_8" title="Permanent link">¶</a></h2>
|
||||
|
||||
@@ -1396,6 +1396,11 @@
|
||||
<p>本文档涵盖了软件更新中对配置文件不向后兼容的部分。在升级 Klipper 时，最好也查看一下这份文档。</p>
|
||||
<p>文档的所有日期都是大概时间。</p>
|
||||
<h2 id="_2">变更<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
<p>20241203: The resonance test has been changed to include slow sweeping moves. This change requires that testing point(s) have some clearance in X/Y plane (+/- 30 mm from the test point should suffice when using the default settings). The new test should generally produce more accurate and reliable test results. However, if required, the previous test behavior can be restored by adding options <code>sweeping_period: 0</code> and <code>accel_per_hz: 75</code> to the <code>[resonance_tester]</code> config section.</p>
|
||||
<p>20241201: In some cases Klipper may have ignored leading characters or spaces in a traditional G-Code command. For example, "99M123" may have been interpreted as "M123" and "M 321" may have been interpreted as "M321". Klipper will now report these cases with an "Unknown command" warning.</p>
|
||||
<p>20241112: Option <code>CHIPS=<chip_name></code> in <code>TEST_RESONANCES</code> and <code>SHAPER_CALIBRATE</code> requires specifying the full name(s) of the accel chip(s). For example, <code>adxl345 rpi</code> instead of short name - <code>rpi</code>.</p>
|
||||
<p>20240912: <code>SET_PIN</code>, <code>SET_SERVO</code>, <code>SET_FAN_SPEED</code>, <code>M106</code>, and <code>M107</code> commands are now collated. Previously, if many updates to the same object were issued faster than the minimum scheduling time (typically 100ms) then actual updates could be queued far into the future. Now if many updates are issued in rapid succession then it is possible that only the latest request will be applied. If the previous behavior is requried then consider adding explicit <code>G4</code> delay commands between updates.</p>
|
||||
<p>20240912: Support for <code>maximum_mcu_duration</code> and <code>static_value</code> parameters in <code>[output_pin]</code> config sections have been removed. These options have been deprecated since 20240123.</p>
|
||||
<p>20240415: The <code>on_error_gcode</code> parameter in the <code>[virtual_sdcard]</code> config section now has a default. If this parameter is not specified it now defaults to <code>TURN_OFF_HEATERS</code>. If the previous behavior is desired (take no default action on an error during a virtual_sdcard print) then define <code>on_error_gcode</code> with an empty value.</p>
|
||||
<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>
|
||||
|
||||
@@ -938,6 +938,13 @@
|
||||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1537,6 +1544,13 @@
|
||||
hd44780_spi显示器
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1670,8 +1684,8 @@
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -3032,6 +3046,13 @@
|
||||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -3631,6 +3652,13 @@
|
||||
hd44780_spi显示器
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -3764,8 +3792,8 @@
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -5173,8 +5201,9 @@ cs_pin:
|
||||
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS2DW accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis2dw]
|
||||
cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
@@ -5184,6 +5213,43 @@ cs_pin:
|
||||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="lis3dh">[lis3dh]<a class="headerlink" href="#lis3dh" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS3DH accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis3dh]
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
@@ -5208,38 +5274,58 @@ cs_pin:
|
||||
<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]
|
||||
#probe_points:
|
||||
# 共振测试点的列表（每行一个X,Y,Z坐标点），至少指定一个点。请确保
|
||||
# 所有点在XY平面上都有足够容许打印头移动头移动的安全余量（约几厘米）。
|
||||
# A list of X, Y, Z coordinates of points (one point per line) to test
|
||||
# resonances at. At least one point is required. Make sure that all
|
||||
# points with some safety margin in XY plane (~a few centimeters)
|
||||
# are reachable by the toolhead.
|
||||
#accel_chip:
|
||||
# 一个用于测量的加速度计芯片的名称。如果adxl345芯片定义时没有明确指定
|
||||
# 名称，这个参数可以直接引用 "accel_chip: adxl345"，否则必须提供一个明确
|
||||
# 的名称，例如 "accel_chip: adxl345 my_chip_name"。
|
||||
# 必须被提供这个参数或下面的两个参数。
|
||||
# A name of the accelerometer chip to use for measurements. If
|
||||
# adxl345 chip was defined without an explicit name, this parameter
|
||||
# can simply reference it as "accel_chip: adxl345", otherwise an
|
||||
# explicit name must be supplied as well, e.g. "accel_chip: adxl345
|
||||
# my_chip_name". Either this, or the next two parameters must be
|
||||
# set.
|
||||
#accel_chip_x:
|
||||
#accel_chip_y:
|
||||
# 用于测量每个轴的加速计芯片的名称。在平移热床的打印机上可能很有用，
|
||||
# 如果两个单独的加速度计分别被安装在打印床（用于Y轴）和工具头（X轴）上。
|
||||
# 这些参数的格式与 “accel_chip” 参数相同。
|
||||
# 必须提供“accel_chip”或这两个参数。
|
||||
# Names of the accelerometer chips to use for measurements for each
|
||||
# of the axis. Can be useful, for instance, on bed slinger printer,
|
||||
# if two separate accelerometers are mounted on the bed (for Y axis)
|
||||
# and on the toolhead (for X axis). These parameters have the same
|
||||
# format as 'accel_chip' parameter. Only 'accel_chip' or these two
|
||||
# parameters must be provided.
|
||||
#max_smoothing:
|
||||
# 在自动校准整形(使用'SHAPER_CALIBRATE' 命令)的过程中允许每个轴的最大输
|
||||
# 入整形器平滑度。
|
||||
# 默认不指定最大的平滑度。
|
||||
# 请参考共振校准指南以了解有关使用此功能的更多细节。
|
||||
# Maximum input shaper smoothing to allow for each axis during shaper
|
||||
# auto-calibration (with 'SHAPER_CALIBRATE' command). By default no
|
||||
# maximum smoothing is specified. Refer to Measuring_Resonances guide
|
||||
# for more details on using this feature.
|
||||
#move_speed: 50
|
||||
# The speed (in mm/s) to move the toolhead to and between test points
|
||||
# during the calibration. The default is 50.
|
||||
#min_freq: 5
|
||||
# 测试谐振的最小频率。默认为5Hz。
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 133.33
|
||||
# 测试谐振的最大频率。默认为133.33 Hz。
|
||||
#accel_per_hz: 75
|
||||
# 这个参数用于决定测试一个特定的频率的加速度： accel = accel_per_hz * freq。
|
||||
# 数值越大加速度越高，振荡的能量就越大。如果打印机上的共振太强，可以
|
||||
# 设置为比默认值更低的值。然而，较低的值会使高频共振的测量不那么精确。
|
||||
# 默认为75mm/s。
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 60
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
# value, the higher is the energy of the oscillations. Can be set to
|
||||
# a lower than the default value if the resonances get too strong on
|
||||
# the printer. However, lower values make measurements of
|
||||
# high-frequency resonances less precise. The default value is 75
|
||||
# (mm/sec).
|
||||
#hz_per_sec: 1
|
||||
# 决定测试的速度。当测试所有频率在范围[min_freq, max_freq]内时，每秒钟
|
||||
# 频率都会增加 hz_per_sec。更小的数值会使测试变慢，更大的数值会降低测
|
||||
# 试的精度。
|
||||
# 默认值是1.0（Hz/sec == sec^-2）。
|
||||
# Determines the speed of the test. When testing all frequencies in
|
||||
# range [min_freq, max_freq], each second the frequency increases by
|
||||
# hz_per_sec. Small values make the test slow, and the large values
|
||||
# will decrease the precision of the test. The default value is 1.0
|
||||
# (Hz/sec == sec^-2).
|
||||
#sweeping_accel: 400
|
||||
# An acceleration of slow sweeping moves. The default is 400 mm/sec^2.
|
||||
#sweeping_period: 1.2
|
||||
# A period of slow sweeping moves. Setting this parameter to 0
|
||||
# disables slow sweeping moves. Avoid setting it to a too small
|
||||
# non-zero value in order to not poison the measurements.
|
||||
# The default is 1.2 sec which is a good all-round choice.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_14">配置文件助手<a class="headerlink" href="#_14" title="Permanent link">¶</a></h2>
|
||||
@@ -5456,7 +5542,7 @@ sensor_type: ldc1612
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">¶</a></h3>
|
||||
<p>A tool to compensate for inaccurate probe readings due to twist in X gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
|
||||
<p>A tool to compensate for inaccurate probe readings due to twist in X or Y gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
|
||||
<div class="highlight"><pre><span></span><code>[axis_twist_compensation]
|
||||
#speed: 50
|
||||
# The speed (in mm/s) of non-probing moves during the calibration.
|
||||
@@ -5467,16 +5553,33 @@ sensor_type: ldc1612
|
||||
calibrate_start_x: 20
|
||||
# Defines the minimum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the starting
|
||||
# calibration position. This parameter must be provided.
|
||||
# calibration position.
|
||||
calibrate_end_x: 200
|
||||
# Defines the maximum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the ending
|
||||
# calibration position. This parameter must be provided.
|
||||
# calibration position.
|
||||
calibrate_y: 112.5
|
||||
# Defines the Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle during the
|
||||
# calibration process. This parameter must be provided and is recommended to
|
||||
# calibration process. This parameter is recommended to
|
||||
# be near the center of the bed
|
||||
|
||||
# For Y-axis twist compensation, specify the following parameters:
|
||||
calibrate_start_y: ...
|
||||
# Defines the minimum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the starting
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_end_y: ...
|
||||
# Defines the maximum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the ending
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_x: ...
|
||||
# Defines the X coordinate of the calibration for Y axis twist compensation
|
||||
# This should be the X coordinate that positions the nozzle during the
|
||||
# calibration process for Y axis twist compensation. This parameter must be
|
||||
# provided and is recommended to be near the center of the bed.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_16">额外的步进电机和挤出机<a class="headerlink" href="#_16" title="Permanent link">¶</a></h2>
|
||||
@@ -5742,6 +5845,10 @@ extruder:
|
||||
# "calibration_extruder_temp" option is set. Its recommended to heat
|
||||
# the extruder some distance from the bed to minimize its impact on
|
||||
# the probe coil temperature. The default is 50.
|
||||
#max_validation_temp: 60.
|
||||
# The maximum temperature used to validate the calibration. It is
|
||||
# recommended to set this to a value between 100 and 120 for enclosed
|
||||
# printers. The default is 60.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_18">温度传感器<a class="headerlink" href="#_18" title="Permanent link">¶</a></h2>
|
||||
@@ -6817,6 +6924,7 @@ run_current:
|
||||
#driver_SEIMIN: 0
|
||||
#driver_SFILT: 0
|
||||
#driver_SG4_ANGLE_OFFSET: 1
|
||||
#driver_SLOPE_CONTROL: 0
|
||||
# Set the given register during the configuration of the TMC2240
|
||||
# chip. This may be used to set custom motor parameters. The
|
||||
# defaults for each parameter are next to the parameter name in the
|
||||
@@ -7084,72 +7192,82 @@ wiper:
|
||||
<p>支持一个连接到微控制器的屏幕</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type:
|
||||
# 使用的 LCD 芯片类型。这可以是“hd44780”、“hd44780_spi”、
|
||||
# “st7920”、“emulated_st7920”、“uc1701”、“ssd1306”、或“sh1106”。
|
||||
# 有关不同的LCD芯片类型和它们特有的参数，请查看下面的显示屏分段。
|
||||
# 必须提供此参数。
|
||||
# The type of LCD chip in use. This may be "hd44780", "hd44780_spi",
|
||||
# "aip31068_spi", "st7920", "emulated_st7920", "uc1701", "ssd1306", or
|
||||
# "sh1106".
|
||||
# See the display sections below for information on each type and
|
||||
# additional parameters they provide. This parameter must be
|
||||
# provided.
|
||||
#display_group:
|
||||
# 显示在这个显示屏上的 display_data 组。它决定了这个屏幕显示
|
||||
# 的内容（详见“display_data”分段）。
|
||||
# hd44780 默认使用 _default_20x4，其他显示屏则默认使用 _default_16x4。
|
||||
# The name of the display_data group to show on the display. This
|
||||
# controls the content of the screen (see the "display_data" section
|
||||
# for more information). The default is _default_20x4 for hd44780 or
|
||||
# aip31068_spi displays and _default_16x4 for other displays.
|
||||
#menu_timeout:
|
||||
# 菜单超时时间。在不活跃给定时间后将会退出菜单或在 autorun 启用时
|
||||
# 回到根菜单。
|
||||
# 默认为 0 秒（禁用）。
|
||||
# Timeout for menu. Being inactive this amount of seconds will
|
||||
# trigger menu exit or return to root menu when having autorun
|
||||
# enabled. The default is 0 seconds (disabled)
|
||||
#menu_root:
|
||||
# 在主屏幕按下编码器时显示的主菜单段名称。
|
||||
# 默认为 __main，这会显示在 klippy/extras/display/menu.cfg中定义的主菜单。
|
||||
# Name of the main menu section to show when clicking the encoder
|
||||
# on the home screen. The defaults is __main, and this shows the
|
||||
# the default menus as defined in klippy/extras/display/menu.cfg
|
||||
#menu_reverse_navigation:
|
||||
# 启用时反转上滚动和下滚动。
|
||||
# 默认为False。这是一个可选参数。
|
||||
# When enabled it will reverse up and down directions for list
|
||||
# navigation. The default is False. This parameter is optional.
|
||||
#encoder_pins:
|
||||
# 连接到编码器的引脚。使用编码器时必须提供两个引脚。
|
||||
# 使用菜单时必须提供此参数。
|
||||
# The pins connected to encoder. 2 pins must be provided when using
|
||||
# encoder. This parameter must be provided when using menu.
|
||||
#encoder_steps_per_detent:
|
||||
# 编码器在每一个凹陷处（"click"）发出多少步。如果编码器需要转过两个凹
|
||||
# 陷才能在条目之间移动，或者转过一个凹痕会在两个词条之间移动/跳过
|
||||
# 一个词条，可以尝试改变这个值。
|
||||
# 允许的值是2 （半步）或 4（全步）。
|
||||
# 默认为 4。
|
||||
# How many steps the encoder emits per detent ("click"). If the
|
||||
# encoder takes two detents to move between entries or moves two
|
||||
# entries from one detent, try changing this. Allowed values are 2
|
||||
# (half-stepping) or 4 (full-stepping). The default is 4.
|
||||
#click_pin:
|
||||
# 连接到 "enter" 按钮或编码器按压的引脚。
|
||||
# 使用菜单时必须提供此参数。
|
||||
# 如果定义了 “analog_range_click_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'enter' button or encoder 'click'. This
|
||||
# parameter must be provided when using menu. The presence of an
|
||||
# 'analog_range_click_pin' config parameter turns this parameter
|
||||
# from digital to analog.
|
||||
#back_pin:
|
||||
# 连接到“back”按钮的引脚。这是一个可选参数，菜单不需要这个按钮。
|
||||
# 如果定义了 “analog_range_back_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'back' button. This parameter is optional,
|
||||
# menu can be used without it. The presence of an
|
||||
# 'analog_range_back_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#up_pin:
|
||||
# 连接到“up”按钮的引脚。在不使用编码器时使用菜单必须提供这个参数。
|
||||
# 如果定义了 “analog_range_up_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'up' button. This parameter must be provided
|
||||
# when using menu without encoder. The presence of an
|
||||
# 'analog_range_up_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#down_pin:
|
||||
# 连接到“down”按钮的引脚。 在不使用编码器时使用菜单必须提供这个参数。
|
||||
# 如果定义了 “analog_range_down_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'down' button. This parameter must be
|
||||
# provided when using menu without encoder. The presence of an
|
||||
# 'analog_range_down_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#kill_pin:
|
||||
# 连接到“kill”按钮的引脚。 这个按钮将会触发紧急停止。
|
||||
# 如果定义了 “analog_range_kill_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'kill' button. This button will call
|
||||
# emergency stop. The presence of an 'analog_range_kill_pin' config
|
||||
# parameter turns this parameter from digital to analog.
|
||||
#analog_pullup_resistor: 4700
|
||||
# 连接到模拟按钮的拉高电阻阻值(ohms)
|
||||
# 默认为 4700 ohms。
|
||||
# The resistance (in ohms) of the pullup attached to the analog
|
||||
# button. The default is 4700 ohms.
|
||||
#analog_range_click_pin:
|
||||
# 'enter'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'enter' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_back_pin:
|
||||
# 'back'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'back' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_up_pin:
|
||||
# 'up'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'up' button. Range minimum and maximum
|
||||
# comma-separated values must be provided when using analog button.
|
||||
#analog_range_down_pin:
|
||||
# 'down'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'down' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_kill_pin:
|
||||
# 'kill'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'kill' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="hd44780">hd44780显示器<a class="headerlink" href="#hd44780" title="Permanent link">¶</a></h4>
|
||||
@@ -7200,6 +7318,26 @@ spi_software_miso_pin:
|
||||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="aip31068_spi-display">aip31068_spi display<a class="headerlink" href="#aip31068_spi-display" title="Permanent link">¶</a></h4>
|
||||
<p>Information on configuring an aip31068_spi display - a very similar to hd44780_spi a 20x04 (20 symbols by 4 lines) display with slightly different internal protocol.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type: aip31068_spi
|
||||
latch_pin:
|
||||
spi_software_sclk_pin:
|
||||
spi_software_mosi_pin:
|
||||
spi_software_miso_pin:
|
||||
# The pins connected to the shift register controlling the display.
|
||||
# The spi_software_miso_pin needs to be set to an unused pin of the
|
||||
# printer mainboard as the shift register does not have a MISO pin,
|
||||
# but the software spi implementation requires this pin to be
|
||||
# configured.
|
||||
#line_length:
|
||||
# Set the number of characters per line for an hd44780 type lcd.
|
||||
# Possible values are 20 (default) and 16. The number of lines is
|
||||
# fixed to 4.
|
||||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="st7920">st7920屏幕<a class="headerlink" href="#st7920" title="Permanent link">¶</a></h4>
|
||||
<p>有关配置 st7920 类显示屏的信息（可用于 "RepRapDiscount 12864 Full Graphic Smart Controller" 类型的显示器）。</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
@@ -7543,7 +7681,7 @@ sensor_type:
|
||||
# This must be one of the supported sensor types, see below.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="xh711">XH711<a class="headerlink" href="#xh711" title="Permanent link">¶</a></h4>
|
||||
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">¶</a></h4>
|
||||
<p>This is a 24 bit low sample rate chip using "bit-bang" communications. It is suitable for filament scales.</p>
|
||||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
sensor_type: hx711
|
||||
@@ -7606,13 +7744,30 @@ data_ready_pin:
|
||||
#gain: 128
|
||||
# Valid gain values are 128, 64, 32, 16, 8, 4, 2, 1
|
||||
# The default is 128
|
||||
#pga_bypass: False
|
||||
# Disable the internal Programmable Gain Amplifier. If
|
||||
# True the PGA will be disabled for gains 1, 2, and 4. The PGA is always
|
||||
# enabled for gain settings 8 to 128, regardless of the pga_bypass setting.
|
||||
# If AVSS is used as an input pga_bypass is forced to True.
|
||||
# The default is False.
|
||||
#sample_rate: 660
|
||||
# This chip supports two ranges of sample rates, Normal and Turbo. In turbo
|
||||
# mode the chips c internal clock runs twice as fast and the SPI communication
|
||||
# mode the chip's internal clock runs twice as fast and the SPI communication
|
||||
# speed is also doubled.
|
||||
# Normal sample rates: 20, 45, 90, 175, 330, 600, 1000
|
||||
# Turbo sample rates: 40, 90, 180, 350, 660, 1200, 2000
|
||||
# The default is 660
|
||||
#input_mux:
|
||||
# Input multiplexer configuration, select a pair of pins to use. The first pin
|
||||
# is the positive, AINP, and the second pin is the negative, AINN. Valid
|
||||
# values are: 'AIN0_AIN1', 'AIN0_AIN2', 'AIN0_AIN3', 'AIN1_AIN2', 'AIN1_AIN3',
|
||||
# 'AIN2_AIN3', 'AIN1_AIN0', 'AIN3_AIN2', 'AIN0_AVSS', 'AIN1_AVSS', 'AIN2_AVSS'
|
||||
# and 'AIN3_AVSS'. If AVSS is used the PGA is bypassed and the pga_bypass
|
||||
# setting will be forced to True.
|
||||
# The default is AIN0_AIN1.
|
||||
#vref:
|
||||
# The selected voltage reference. Valid values are: 'internal', 'REF0', 'REF1'
|
||||
# and 'analog_supply'. Default is 'internal'.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_28">控制板特定硬件支持<a class="headerlink" href="#_28" title="Permanent link">¶</a></h2>
|
||||
@@ -7750,28 +7905,30 @@ serial:
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<p>支持使用a1333、as5047d或tle5012b SPI芯片的磁性霍尔角度传感器测量并读取步进电机的角度。测量结果可以通过<a href="API_Server.html">API服务器</a>和<a href="Debugging.html#motion-analysis-and-data-logging">运动分析工具</a>获取。可用的命令请见<a href="G-Codes.html#angle">G代码参考</a>。</p>
|
||||
<p>Magnetic hall angle sensor support for reading stepper motor angle shaft measurements using a1333, as5047d, mt6816, mt6826s, or tle5012b SPI chips. The measurements are available via the <a href="API_Server.html">API Server</a> and <a href="Debugging.html#motion-analysis-and-data-logging">motion analysis tool</a>. See the <a href="G-Codes.html#angle">G-Code reference</a> for available commands.</p>
|
||||
<div class="highlight"><pre><span></span><code>[angle my_angle_sensor]
|
||||
sensor_type:
|
||||
# 磁性霍尔传感器芯片的类型。
|
||||
# 可用的选择是 "a1333" "as5047d "和 "tle5012b"。
|
||||
# 这个参数必须被指定。
|
||||
# The type of the magnetic hall sensor chip. Available choices are
|
||||
# "a1333", "as5047d", "mt6816", "mt6826s", and "tle5012b". This parameter must be
|
||||
# specified.
|
||||
#sample_period: 0.000400
|
||||
# 测量时使用的查询周期（以秒为单位）。
|
||||
# 默认值是 0.000400 （每秒钟2500个样本）
|
||||
# The query period (in seconds) to use during measurements. The
|
||||
# default is 0.000400 (which is 2500 samples per second).
|
||||
#stepper:
|
||||
# 角度传感器连接的步进电机名称（例如，"stepper_x"）。
|
||||
# 设置这个值可以启用一个角度校准工具
|
||||
# 要使用这个功能需要安装Python "numpy "包。
|
||||
# 默认是不启用角度传感器的角度校准。
|
||||
# The name of the stepper that the angle sensor is attached to (eg,
|
||||
# "stepper_x"). Setting this value enables an angle calibration
|
||||
# tool. To use this feature, the Python "numpy" package must be
|
||||
# installed. The default is to not enable angle calibration for the
|
||||
# angle sensor.
|
||||
cs_pin:
|
||||
# 传感器的SPI引脚。必须提供此参数。
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#spi_speed:
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# 有关上述参数的描述，参考 "common SPI settings "
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_30">常见的总线参数<a class="headerlink" href="#_30" title="Permanent link">¶</a></h2>
|
||||
@@ -7794,7 +7951,7 @@ cs_pin:
|
||||
<h3 id="i2c">常见的I2C设置<a class="headerlink" href="#i2c" title="Permanent link">¶</a></h3>
|
||||
<p>以下参数一般适用于使用I2C总线的设备。</p>
|
||||
<p>请注意，Klipper当前的微控制器对I2C的支持通常不能容忍线路噪声。I2C线路上的意外错误可能会导致Klipper产生运行时错误。Klipper 对错误恢复的支持在每种微控制器类型之间有所不同。通常建议只使用与微控制器位于同一印刷电路板上的I2C设备。</p>
|
||||
<p>大多数Klipper微控制器实现只支持100000的<code>i2c_speed</code>（<em>标准模式</em>，100kbit/s）。Klipper的"Linux"微控制器支持400000的速度（<em>快速模式</em>，400kbit/s），但它必须<a href="RPi_microcontroller.html#optional-enabling-i2c">在操作系统中设置</a>，否则会忽略<code>i2c_speed</code>参数。Klipper的"RP2040"微控制器和ATmega AVR系列通过<code>i2c_speed</code>参数支持400000的速率。所有其他Klipper微控制器使用100000的速率并忽略<code>i2c_speed</code>参数。</p>
|
||||
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000 (<em>standard mode</em>, 100kbit/s). The Klipper "Linux" micro-controller supports a 400000 speed (<em>fast mode</em>, 400kbit/s), 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 and ATmega AVR family and some STM32 (F0, G0, G4, L4, F7, H7) support 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:
|
||||
# The i2c address of the device. This must specified as a decimal
|
||||
# number (not in hex). The default depends on the type of device.
|
||||
|
||||
@@ -1412,7 +1412,7 @@
|
||||
# 温度探针配置文件
|
||||
</code></pre></div>
|
||||
|
||||
<p>在<a href="Config_Reference.html#temperature_probe">configuration reference</a>有更多关于如何配置<code>temperature_probe</code>的内容。建议配置<code>calibration_position</code>， <code>calibration_extruder_temp</code>， <code>extruder_heating_z</code>, 和 <code>calibration_bed_temp</code>选项，这会在接下来的校准过程中自动完成一些步骤。</p>
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below. If the printer to be calibrated is enclosed, it is strongly recommended to set the <code>max_validation_temp</code> option to a value between 100 and 120.</p>
|
||||
<p>Eddy probe的制造商提供了一些可以使用的校准预设可以手动添加到<code>[probe_eddy_current]</code>中到<code>drift_calibration</code>选项中。如果他们没提供预设的校准文件或者预设的校准文件不适用于你的系统，<code>temperature_probe</code>模块可以使用TEMPERATURE_PROBE_CALIBRATE`命令来进行手动校准。</p>
|
||||
<p>在进行校准前，用户应该知道大概的探针线圈最大温度。这个温度应该被配置到<code>TEMPERATURE_PROBE_CALIBRATE</code>命令的<code>TARGET</code>选项中。校准的目的是尽量有一个最宽的温度范围，因此最好在打印机冷却后进行校准，并且在线圈到达最高温度的时候停止。</p>
|
||||
<p>当<code>[temperature_probe]</code> 被配置后，可以使用以下步骤进行热偏移校准：</p>
|
||||
|
||||
@@ -1542,6 +1542,16 @@
|
||||
<td>2634K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>RP2350</td>
|
||||
<td>4167K</td>
|
||||
<td>2663K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SAME70</td>
|
||||
<td>6667K</td>
|
||||
<td>4737K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>STM32H743</td>
|
||||
<td>9091K</td>
|
||||
<td>6061K</td>
|
||||
|
||||
@@ -869,6 +869,13 @@
|
||||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1958,6 +1965,26 @@
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -3089,6 +3116,13 @@
|
||||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -4178,6 +4212,26 @@
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -4750,6 +4804,11 @@
|
||||
<p>The following commands are available when an <a href="Config_Reference.html#angle">angle config section</a> is enabled.</p>
|
||||
<h4 id="angle_calibrate">ANGLE_CALIBRATE<a class="headerlink" href="#angle_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CALIBRATE CHIP=<芯片名></code>：在指定传感器上执行角度校准（必须有一个<code>[angle 芯片名]</code>的配置分段，并指定一个<code>stepper</code>参数）。重要的是 - 这个工具将命令步进电机移动而不检查正常的运动学边界限制。理想情况下，在执行校准之前，电机不应被连接到任何打印机的滑块。如果不能断开步进电机和打印机滑块的连接，在开始校准之前，确保滑车接近其轨道的中心。(在这个测试中，步进电机可能会向前或向后移动两圈）。完成这个测试后，使用<code>SAVE_CONFIG</code>命令，将校准数据保存到配置文件中。为了使用这个工具，必须安装Python "numpy"软件包（更多信息见<a href="Measuring_Resonances.html#software-installation">测量谐振文档</a>）。</p>
|
||||
<h4 id="angle_chip_calibrate">ANGLE_CHIP_CALIBRATE<a class="headerlink" href="#angle_chip_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CHIP_CALIBRATE CHIP=<chip_name></code>: Perform internal sensor calibration, if implemented (MT6826S/MT6835).</p>
|
||||
<ul>
|
||||
<li><strong>MT68XX</strong>: The motor should be disconnected from any printer carriage before performing calibration. After calibration, the sensor should be reset by disconnecting the power.</li>
|
||||
</ul>
|
||||
<h4 id="angle_debug_read">ANGLE_DEBUG_READ<a class="headerlink" href="#angle_debug_read" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_DEBUG_READ CHIP=<配置名> REG=<寄存器></code>：查询传感器寄存器"寄存器"（例如：44或0x2C）。该命令常用于调试，仅适用于tle5012b芯片。</p>
|
||||
<h4 id="angle_debug_write">ANGLE_DEBUG_WRITE<a class="headerlink" href="#angle_debug_write" title="Permanent link">¶</a></h4>
|
||||
@@ -4758,7 +4817,12 @@
|
||||
<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">¶</a></h4>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=<value>]</code>: 启动X轴扭转校准向导。 <code>SAMPLE_COUNT</code> 指定沿着X轴进行校准的点数，默认为3个。</p>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]</code></p>
|
||||
<p>Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.</p>
|
||||
<ul>
|
||||
<li><strong>AXIS:</strong> Define the axis (<code>X</code> or <code>Y</code>) for which the twist compensation will be calibrated. If not specified, the axis defaults to <code>'X'</code>.</li>
|
||||
<li><strong>AUTO:</strong> Enables automatic calibration mode. When <code>AUTO=True</code>, the calibration will run for both the X and Y axes. In this mode, <code>AXIS</code> cannot be specified. If both <code>AXIS</code> and <code>AUTO</code> are provided, an error will be raised.</li>
|
||||
</ul>
|
||||
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">¶</a></h3>
|
||||
<p>启用[床网格配置部分]（config_Reference.md#bed_mesh）时，以下命令可用（另请参阅[床网格指南]（bed_mesh.md））。</p>
|
||||
<h4 id="bed_mesh_calibrate">BED_MESH_CALIBRATE<a class="headerlink" href="#bed_mesh_calibrate" title="Permanent link">¶</a></h4>
|
||||
@@ -4862,6 +4926,7 @@ section</a> is enabled.</p>
|
||||
<p>当<a href="Config_Reference.html#fan_generic">fan_generic 配置分段</a>被启用时，以下命令可用：</p>
|
||||
<h4 id="set_fan_speed">SET_FAN_SPEED<a class="headerlink" href="#set_fan_speed" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_FAN_SPEED FAN=config_name SPEED=<速度></code>该命令设置风扇的速度。"速度" 必须在0.0到1.0之间。</p>
|
||||
<p><code>SET_FAN_SPEED PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given fan. For example, if one defined a <code>[display_template my_fan_template]</code> config section then one could assign <code>TEMPLATE=my_fan_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the fan will be automatically set to the resulting speed. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_FAN_SPEED</code> commands to manage the values directly).</p>
|
||||
<h3 id="filament_switch_sensor">[filament_switch_sensor]<a class="headerlink" href="#filament_switch_sensor" title="Permanent link">¶</a></h3>
|
||||
<p>启用<a href="Config_Reference.html#filament_switch_sensor">filament_switch_sensor</a>或<a href="Config_Reference.html#filament_motion_sensor">filament_motion_sensor</a>配置分段后，可使用以下命令：</p>
|
||||
<h4 id="query_filament_sensor">QUERY_FILAMENT_SENSOR<a class="headerlink" href="#query_filament_sensor" title="Permanent link">¶</a></h4>
|
||||
@@ -4886,7 +4951,7 @@ section</a> is enabled.</p>
|
||||
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>FORCE_MOVE STEPPER=<config_name> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]</code> 。该命令将以给定的恒定速度（mm/s）强制移动给定的步进器，移动距离（mm）。如果指定了ACCEL并且大于零，那么将使用给定的加速度（单位：mm/s^2）；否则不进行加速。不执行边界检查；不进行运动学更新；一个轴上的其他平行步进器将不会被移动。请谨慎使用，因为不正确的命令可能会导致损坏使用该命令几乎肯定会使低级运动学处于不正确的状态；随后发出G28命令以重置运动学。该命令用于低级别的诊断和调试。</p>
|
||||
<h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<值>] [Y=<值>] [Z=<值>]</code>：强制设定低级运动学代码使用的打印头位置。这是一个诊断和调试工具，常规的轴转换应该使用 SET_GCODE_OFFSET 和/或 G92指令。如果没有指定一个轴，则使用上一次命令的打印头位置。设定一个不合理的数值可能会导致内部程序问题。这个命令可能会使边界检查失效，使用后发送 G28 来重置运动学。</p>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an axis is not specified then it will default to the position that the head was last commanded to. Setting an incorrect or invalid position may lead to internal software errors. Use the CLEAR parameter to forget the homing state for the given axes. Note that CLEAR will not override the previous functionality; if an axis is not specified to CLEAR it will have its kinematic position set as per above. This command may invalidate future boundary checks; issue a G28 afterwards to reset the kinematics.</p>
|
||||
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">¶</a></h3>
|
||||
<p>The gcode module is automatically loaded.</p>
|
||||
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">¶</a></h4>
|
||||
@@ -4980,6 +5045,7 @@ section</a> is enabled.</p>
|
||||
<p>使用<a href="Config_Reference.html#output_pin">output_pin 配置分段</a>时，以下命令可用：</p>
|
||||
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value></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><code>SET_PIN PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given pin. For example, if one defined a <code>[display_template my_pin_template]</code> config section then one could assign <code>TEMPLATE=my_pin_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the pin will be automatically set to the resulting value. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_PIN</code> commands to manage the values directly).</p>
|
||||
<h3 id="palette2">[palette2]<a class="headerlink" href="#palette2" title="Permanent link">¶</a></h3>
|
||||
<p>当<a href="Config_Reference.html#palette2">palette2 配置分段</a>被启用时，以下命令可用：</p>
|
||||
<p>Palette打印通过在GCode文件中嵌入特殊的OCodes（Omega Codes）来工作。</p>
|
||||
@@ -5037,6 +5103,10 @@ section</a> is enabled.</p>
|
||||
<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">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value> [CYCLE_TIME=<cycle_time>]</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="quad_gantry_level">[quad_gantry_level]<a class="headerlink" href="#quad_gantry_level" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#quad_gantry_level">quad_gantry_level config section</a> is enabled.</p>
|
||||
<h4 id="quad_gantry_level_1">QUAD_GANTRY_LEVEL<a class="headerlink" href="#quad_gantry_level_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>QUAD_GANTRY_LEVEL [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">¶</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">¶</a></h4>
|
||||
@@ -5053,9 +5123,9 @@ section</a> is enabled.</p>
|
||||
<h4 id="measure_axes_noise">MEASURE_AXES_NOISE<a class="headerlink" href="#measure_axes_noise" title="Permanent link">¶</a></h4>
|
||||
<p><code>MEASURE_AXES_NOISE</code>：测量并输出所有启用的加速度计芯片的所有轴的噪声。</p>
|
||||
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">¶</a></h4>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> OUTPUT=<resonances,raw_data> [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]</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_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</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_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> [OUTPUT=<resonances,raw_data>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [POINT=x,y,z] [INPUT_SHAPING=<0:1>]</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>chip_name</code> can be one or more configured accel chips, delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. 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_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</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_<axis>_<name>.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">¶</a></h4>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [MAX_SMOOTHING=<max_smoothing>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>][HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [MAX_SMOOTHING=<max_smoothing>] [INPUT_SHAPING=<0:1>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">¶</a></h3>
|
||||
<p>The following standard G-Code commands are available when the <a href="Config_Reference.html#respond">respond config section</a> is enabled:</p>
|
||||
<ul>
|
||||
@@ -5161,7 +5231,7 @@ section</a> is enabled.</p>
|
||||
<h3 id="z_tilt">[z_tilt]<a class="headerlink" href="#z_tilt" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#z_tilt">z_tilt config section</a> is enabled.</p>
|
||||
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">¶</a></h4>
|
||||
<p>`Z_TILT_ADJUST[HORIZONTAL_MOVE_Z=<value>][<probe_parameter>=<value>>：此命令将探测配置中指定的点，然后对每个Z步进器进行独立调整以补偿倾斜。有关可选探测参数的详细信息，请参阅PROBE命令。可选的“HORIZONTAL_MOVE_Z”值将覆盖配置文件中指定的“HORIZONTAL_MOVE_Z”选项。</p>
|
||||
<p><code>Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when a <a href="Config_Reference.html#temperature_probe">temperature_probe config section</a> is enabled.</p>
|
||||
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
||||
@@ -912,8 +912,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis2dw" class="md-nav__link">
|
||||
配置LIS2DW系列
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -990,6 +990,13 @@
|
||||
选择 max_accel
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#unreliable-measurements-of-resonance-frequencies" class="md-nav__link">
|
||||
Unreliable measurements of resonance frequencies
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1774,8 +1781,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis2dw" class="md-nav__link">
|
||||
配置LIS2DW系列
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -1852,6 +1859,13 @@
|
||||
选择 max_accel
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#unreliable-measurements-of-resonance-frequencies" class="md-nav__link">
|
||||
Unreliable measurements of resonance frequencies
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -1911,10 +1925,10 @@
|
||||
|
||||
|
||||
<h1 id="_1">共振值测量<a class="headerlink" href="#_1" title="Permanent link">¶</a></h1>
|
||||
<p>Klipper has built-in support for the ADXL345, MPU-9250 and LIS2DW compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345/LIS2DW can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper.</p>
|
||||
<p>Klipper has built-in support for the ADXL345, MPU-9250, LIS2DW and LIS3DH compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345 can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper. The LIS2DW and LIS3DH can be connected to either SPI or I2C with the same considerations as above.</p>
|
||||
<p>When sourcing accelerometers, be aware that there are a variety of different PCB board designs and different clones of them. If it is going to be connected to a 5V printer MCU ensure it has a voltage regulator and level shifters.</p>
|
||||
<p>For ADXL345s/LIS2DWs, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
|
||||
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
|
||||
<p>For ADXL345s, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
|
||||
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s and LIS2DW/LIS3DH there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
|
||||
<h2 id="mcus-with-klipper-i2c-fast-mode-support">MCUs with Klipper I2C <em>fast-mode</em> Support<a class="headerlink" href="#mcus-with-klipper-i2c-fast-mode-support" title="Permanent link">¶</a></h2>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -1940,6 +1954,11 @@
|
||||
<td align="left">-</td>
|
||||
<td align="left">AT90usb646, AT90usb1286</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center">SAMD</td>
|
||||
<td align="left">SAMC21G18</td>
|
||||
<td align="left">SAMC21G18, SAMD21G18, SAMD21E18, SAMD21J18, SAMD21E15, SAMD51G19, SAMD51J19, SAMD51N19, SAMD51P20, SAME51J19, SAME51N19, SAME54P20</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="_2">安装指南<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
@@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
|
||||
</code></pre></div>
|
||||
|
||||
<p>接下来，为了在Klipper环境中安装NumPy，运行命令：</p>
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v numpy
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v "numpy<1.26"
|
||||
</code></pre></div>
|
||||
|
||||
<p>请注意，根据CPU性能的不同，这可能需要<em>很长</em>时间，最长可达10-20分钟。请耐心等待安装完成。在某些情况下，如果主板的RAM太少，安装可能会失败，您需要启用交换。</p>
|
||||
<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. Also note the forced version, due to newer versions of NumPY having requirements that may not be satisfied in some klipper python environments.</p>
|
||||
<p>Once installed please check that no errors show from the command:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/python -c 'import numpy;'
|
||||
</code></pre></div>
|
||||
|
||||
<p>The correct output should simply be a new line.</p>
|
||||
<h4 id="rpiadxl345">使用RPI配置ADXL345<a class="headerlink" href="#rpiadxl345" title="Permanent link">¶</a></h4>
|
||||
<p>首先，检查并按照<a href="rpi_微控制器.md">RPI微控制器文档</a>中的说明在Raspberry PI上设置“Linux MCU”。这将配置在您的PI上运行的第二个Klipper实例。</p>
|
||||
<p>通过运行<code>sudo raspi-config</code> 后的 "Interfacing options"菜单中启用 SPI 以确保Linux SPI 驱动已启用。</p>
|
||||
@@ -2257,7 +2281,7 @@ pin: adxl:gpio23
|
||||
</code></pre></div>
|
||||
|
||||
<p>通过<code>RESTART</code>命令重启Klipper。</p>
|
||||
<h4 id="lis2dw">配置LIS2DW系列<a class="headerlink" href="#lis2dw" title="Permanent link">¶</a></h4>
|
||||
<h4 id="configure-lis2dw-series-over-spi">Configure LIS2DW series over SPI<a class="headerlink" href="#configure-lis2dw-series-over-spi" title="Permanent link">¶</a></h4>
|
||||
<div class="highlight"><pre><span></span><code>[MCU列表]。
|
||||
#将<mySerial>更改为您在上面找到的任何内容。例如,。
|
||||
#usb-klipper_rp2040_E661640843545B2E-if00。
|
||||
@@ -2482,6 +2506,8 @@ max_smoothing: 0.25 # an example
|
||||
|
||||
<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="unreliable-measurements-of-resonance-frequencies">Unreliable measurements of resonance frequencies<a class="headerlink" href="#unreliable-measurements-of-resonance-frequencies" title="Permanent link">¶</a></h3>
|
||||
<p>Sometimes the resonance measurements can produce bogus results, leading to the incorrect suggestions for the input shapers. This can be caused by a variety of reasons, including running fans on the toolhead, incorrect position or non-rigid mounting of the accelerometer, or mechanical problems such as loose belts or binding or bumpy axis. Keep in mind that all fans should be disabled for resonance testing, especially the noisy ones, and that the accelerometer should be rigidly mounted on the corresponding moving part (e.g. on the bed itself for the bed slinger, or on the extruder of the printer itself and not the carriage, and some people get better results by mounting the accelerometer on the nozzle itself). As for mechanical problems, the user should inspect if there is any fault that can be fixed with a moving axis (e.g. linear guide rails cleaned up and lubricated and V-slot wheels tension adjusted correctly). If none of that helps, a user may try the other shapers from the produced list besides the one recommended by default.</p>
|
||||
<h3 id="_11">自定义测试轴<a class="headerlink" href="#_11" title="Permanent link">¶</a></h3>
|
||||
<p><code>TEST_RESONANCES</code>命令支持自定义轴。虽然这对输入整形器校准并不真正有用，但它可用于深入研究打印机共振，并检查皮带张力等。</p>
|
||||
<p>要检查CoreXY打印机上的皮带张力，请执行</p>
|
||||
|
||||
@@ -1447,7 +1447,7 @@ git clone https://github.com/Klipper3d/klipper
|
||||
<h2 id="octoprint-klipper">配置OctoPrint 去使用Klipper<a class="headerlink" href="#octoprint-klipper" title="Permanent link">¶</a></h2>
|
||||
<p>OctoPrint 网页服务器需要配置和Klipper Host 软件的连接。使用浏览器登录到 OctoPrint 网页并且配置以下内容：</p>
|
||||
<p>浏览到设置界面（在网页顶部的扳手图标）。在"Serial Connection" 下的 "Additional serial ports" 添加：</p>
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.sock
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.serial
|
||||
</code></pre></div>
|
||||
|
||||
<p>然后点击"保存"。</p>
|
||||
|
||||
@@ -1480,7 +1480,7 @@
|
||||
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" style="margin:25px"/></a></p>
|
||||
<p>BIGTREETECH是Klipper的官方主板赞助商。BIGTREETECH致力于开发创新和有竞争力的产品，更好地服务于3D打印社区。在<a href="https://www.facebook.com/BIGTREETECH">Facebook</a>或<a href="https://twitter.com/BigTreeTech">Twitter</a>上关注他们。</p>
|
||||
<h2 id="_2">赞助<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a> <a href="https://peopoly.net"><img src="./img/sponsors/peopoly-logo.png" width="200" style="margin:25px" /></a></p>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a></p>
|
||||
<h2 id="klipper">Klipper的开发者们<a class="headerlink" href="#klipper" title="Permanent link">¶</a></h2>
|
||||
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">¶</a></h3>
|
||||
<p>Kevin 是项目原作者和当前Klipper的维护。支持链接在<a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> 或者 <a href="https://www.patreon.com/koconnor">https://www.patreon.com/koconnor</a></p>
|
||||
|
||||
Binary file not shown.
File diff suppressed because one or more lines are too long
110
zh/sitemap.xml
110
zh/sitemap.xml
@@ -2,277 +2,277 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in New Issue
Block a user