Deploying to gh-pages from @ Klipper3d/klipper@fb3bae4531 🚀
This commit is contained in:
KevinOConnor
@@ -4119,11 +4119,11 @@
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<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=<chip_name></code>: Perform angle calibration on the given sensor (there must be an <code>[angle chip_name]</code> config section that has specified a <code>stepper</code> parameter). IMPORTANT - this tool will command the stepper motor to move without checking the normal kinematic boundary limits. Ideally the motor should be disconnected from any printer carriage before performing calibration. If the stepper can not be disconnected from the printer, make sure the carriage is near the center of its rail before starting calibration. (The stepper motor may move forwards or backwards two full rotations during this test.) After completing this test use the <code>SAVE_CONFIG</code> command to save the calibration data to the config file. In order to use this tool the Python "numpy" package must be installed (see the <a href="Measuring_Resonances.html#software-installation">measuring resonance document</a> for more information).</p>
|
||||
<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_debug_read">ANGLE_DEBUG_READ<a class="headerlink" href="#angle_debug_read" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_DEBUG_READ CHIP=<config_name> REG=<register></code>: Queries sensor register "register" (e.g. 44 or 0x2C). Can be useful for debugging purposes. This is only available for tle5012b chips.</p>
|
||||
<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>
|
||||
<p><code>ANGLE_DEBUG_WRITE CHIP=<config_name> REG=<register> VAL=<value></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>
|
||||
<p><code>ANGLE_DEBUG_WRITE CHIP=<配置名> REG=<寄存器> VAL=<值></code>：将“值”写入“寄存器”。“值”和“寄存器”可以是十进制或十六进制整数。请小心使用，并参考传感器数据手册。仅适用于 tle5012b芯片。</p>
|
||||
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#bed_mesh">bed_mesh config section</a> is enabled (also see the <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">¶</a></h4>
|
||||
@@ -4187,7 +4187,7 @@
|
||||
<h3 id="extruder">[extruder]<a class="headerlink" href="#extruder" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available if an <a href="Config_Reference.html#extruder">extruder config section</a> is enabled:</p>
|
||||
<h4 id="activate_extruder">ACTIVATE_EXTRUDER<a class="headerlink" href="#activate_extruder" title="Permanent link">¶</a></h4>
|
||||
<p><code>ACTIVATE_EXTRUDER EXTRUDER=<config_name></code>: In a printer with multiple <a href="Config_Reference.html#extruder">extruder</a> config sections, this command changes the active hotend.</p>
|
||||
<p><code>ACTIVATE_EXTRUDER EXTRUDER=<配置名></code>：在有多个<a href="Config_Reference.html#extruder">extruder</a>配置分段的打印机中，该命令会改变活跃的热端。</p>
|
||||
<h4 id="set_pressure_advance">SET_PRESSURE_ADVANCE<a class="headerlink" href="#set_pressure_advance" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PRESSURE_ADVANCE [EXTRUDER=<config_name>] [ADVANCE=<pressure_advance>] [SMOOTH_TIME=<pressure_advance_smooth_time>]</code>: Set pressure advance parameters of an extruder stepper (as defined in an <a href="Config_Reference#extruder">extruder</a> or <a href="Config_Reference#extruder_stepper">extruder_stepper</a> config section). If EXTRUDER is not specified, it defaults to the stepper defined in the active hotend.</p>
|
||||
<h4 id="set_extruder_rotation_distance">SET_EXTRUDER_ROTATION_DISTANCE<a class="headerlink" href="#set_extruder_rotation_distance" title="Permanent link">¶</a></h4>
|
||||
@@ -4374,7 +4374,7 @@
|
||||
<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>] [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. 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>_[<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured). 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=<轴> OUTPUT=<resonance，raw_data> [NAME=<名称>] [FREQ_START=<开始频率>] [FREQ_END=<结束频率>] [HZ_PER_SEC=<hz每秒>] [INPUT_SHAPING=[<0:1>]]</code>：在指定“轴”所有配置的探测点上运行谐振测试，并使用为相应轴配置的加速度计芯片测量加速度。“轴”可以是 X 或 Y，也可以将任意方向指定为 <code>AXIS=dx，dy</code>，其中 dx 和 dy 是定义方向矢量的浮点数（例如 <code>AXIS=X</code>、<code>AXIS=Y</code>或 <code>AXIS=1，-1</code> 来定义对角线方向）。请注意，<code>AXIS=dx，dy</code> 和 <code>AXIS=-dx，-dy</code> 是等效的。如果 <code>INPUT_SHAPING=0</code> 或未设置（默认），则禁用谐振测试的输入整形，因为在启用输入整形器的情况下运行谐振测试是无效的。<code>OUTPUT</code> 参数是一个以逗号分隔的列表，其中将写入输出。如果请求 <code>raw_data</code>，则原始加速度计数据将写入一个文件或一系列文件 <code>/tmp/raw_data_<轴>_[<测试点>_]<名称>.csv</code> 且 （文件名中的<code><测试点>_</code> 部分仅在配置了 1 个以上的探测点时生成）。如果指定了 <code>resonance</code>，则计算频率响应（在所有探测点上），并将其写入 <code>/tmp/resonances_<轴>_<名称>.csv</code> 文件中。如果未设置，则 OUTPUT 默认为 <code>resonance</code>，NAME 默认为“YYYYMMDD_HHMMSS”格式的当前时间。</p>
|
||||
<h4 id="shaper_calibrate">SHAPER_CALIBRATE<a class="headerlink" href="#shaper_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<轴>] [NAME=<名称>] [FREQ_START=<最小频率>] [FREQ_END=<最大频率>] [HZ_PER_SEC=<hz_per_sec>] [MAX_SMOOTHING=<max_smoothing>]</code>：类似<code>TEST_RESONANCES</code>，该命令按配置运行共振测试并尝试寻找给定轴最佳的输入整形参数。如果没有选择<code>AXIS</code>，则测量X和Y轴。如果没有选择 <code>MAX_SMOOTHING</code> ，会使用 <code>[resonance_tester]</code> 的默认参数。有关该特性的使用方法，详见共振量测量指南中的 <a href="Measuring_Resonances.html#max-smoothing">最大平滑</a>章节。测试结果会被输出到终端，而频响和不同输入整形器的参数将被写入到一个或多个 CSV 文件中。它们的名称是<code>/tmp/calibration_data_<轴>_<名称>.csv</code>。如果没有指定，名称默认为“YYYYMMDD_HHMMSS”格式的当前时间。注意，可以通过请求 <code>SAVE_CONFIG</code> 命令将推荐的输入整形器参数直接保存到配置文件中。</p>
|
||||
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">¶</a></h3>
|
||||
|
||||
@@ -751,8 +751,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#bed-slinger-printers" class="md-nav__link">
|
||||
Bed-slinger printers
|
||||
<a href="#_9" class="md-nav__link">
|
||||
平行于喷嘴移动打印床的打印机
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -1394,8 +1394,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#bed-slinger-printers" class="md-nav__link">
|
||||
Bed-slinger printers
|
||||
<a href="#_9" class="md-nav__link">
|
||||
平行于喷嘴移动打印床的打印机
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -1589,8 +1589,8 @@ probe_points: ...
|
||||
~/klipper/scripts/calibrate_shaper.py /tmp/resonances_y_*.csv -o /tmp/shaper_calibrate_y.png
|
||||
</code></pre></div>
|
||||
|
||||
<p>This script will generate the charts <code>/tmp/shaper_calibrate_x.png</code> and <code>/tmp/shaper_calibrate_y.png</code> with frequency responses. You will also get the suggested frequencies for each input shaper, as well as which input shaper is recommended for your setup. For example:</p>
|
||||
<p><img alt="Resonances" src="img/calibrate-y.png" /></p>
|
||||
<p>此脚本将生成频率响应的图表 <code>/tmp/shaper_calibrate_x.png</code> 和 <code>/tmp/shaper_calibrate_y.png</code>。它还会给出每个输入整形器的建议频率，以及推荐的输入整形器。例如：</p>
|
||||
<p><img alt="共振" src="img/calibrate-y.png" /></p>
|
||||
<div class="highlight"><pre><span></span><code>Fitted shaper 'zv' frequency = 34.4 Hz (vibrations = 4.0%, smoothing ~= 0.132)
|
||||
To avoid too much smoothing with 'zv', suggested max_accel <= 4500 mm/sec^2
|
||||
Fitted shaper 'mzv' frequency = 34.6 Hz (vibrations = 0.0%, smoothing ~= 0.170)
|
||||
@@ -1604,7 +1604,7 @@ To avoid too much smoothing with '3hump_ei', suggested max_accel <= 2
|
||||
Recommended shaper is mzv @ 34.6 Hz
|
||||
</code></pre></div>
|
||||
|
||||
<p>The suggested configuration can be added to <code>[input_shaper]</code> section of <code>printer.cfg</code>, e.g.:</p>
|
||||
<p>推荐的配置可以添加到<code>[input_shaper]</code>的<code>printer.cfg</code>分段中，例如：</p>
|
||||
<div class="highlight"><pre><span></span><code>[input_shaper]
|
||||
shaper_freq_x: ...
|
||||
shaper_type_x: ...
|
||||
@@ -1615,10 +1615,10 @@ shaper_type_y: mzv
|
||||
max_accel: 3000 # should not exceed the estimated max_accel for X and Y axes
|
||||
</code></pre></div>
|
||||
|
||||
<p>or you can choose some other configuration yourself based on the generated charts: peaks in the power spectral density on the charts correspond to the resonance frequencies of the printer.</p>
|
||||
<p>Note that alternatively you can run the input shaper autocalibration from Klipper <a href="#input-shaper-auto-calibration">directly</a>, which can be convenient, for example, for the input shaper <a href="#input-shaper-re-calibration">re-calibration</a>.</p>
|
||||
<h3 id="bed-slinger-printers">Bed-slinger printers<a class="headerlink" href="#bed-slinger-printers" title="Permanent link">¶</a></h3>
|
||||
<p>If your printer is a bed slinger printer, you will need to change the location of the accelerometer between the measurements for X and Y axes: measure the resonances of X axis with the accelerometer attached to the toolhead and the resonances of Y axis - to the bed (the usual bed slinger setup).</p>
|
||||
<p>也可以根据生成的图表自己选择一些其他配置：图表上的功率谱密度的峰值对应于打印机的共振频率。</p>
|
||||
<p>请注意，可以<a href="#input-shaper-auto-calibration">直接</a>在Klipper中运行输入整形器自动校准，这可能更方便，例如，对于输入整形器<a href="#input-shaper-re-calibration">重新校准</a>。</p>
|
||||
<h3 id="_9">平行于喷嘴移动打印床的打印机<a class="headerlink" href="#_9" title="Permanent link">¶</a></h3>
|
||||
<p>如果打印机的打印床可以平行于喷嘴移动，测量X和Y轴时需要改变加速度计的安装位置。安装加速度计到打印头以测量X轴共振，安装到打印床以测量Y轴（该类打印机的常见配置）。</p>
|
||||
<p>However, you can also connect two accelerometers simultaneously, though they must be connected to different boards (say, to an RPi and printer MCU board), or to two different physical SPI interfaces on the same board (rarely available). Then they can be configured in the following manner:</p>
|
||||
<div class="highlight"><pre><span></span><code>[adxl345 hotend]
|
||||
# Assuming `hotend` chip is connected to an RPi
|
||||
|
||||
@@ -1847,7 +1847,7 @@
|
||||
<h2 id="led">led<a class="headerlink" href="#led" title="Permanent link">¶</a></h2>
|
||||
<p>以下信息适用于每个在printer.cfg中定义了的 <code>[led led_name]</code>、<code>[neopixel led_name]</code>、<code>[dotstar led_name]</code>、<code>[pca9533 led_name]</code> , 和 <code>[pca9632 led_name]</code> 配置分段：</p>
|
||||
<ul>
|
||||
<li><code>color_data</code>: A list of color lists containing the RGBW values for a led in the chain. Each value is represented as a float from 0.0 to 1.0. Each color list contains 4 items (red, green, blue, white) even if the underyling LED supports fewer color channels. For example, the blue value (3rd item in color list) of the second neopixel in a chain could be accessed at <code>printer["neopixel <config_name>"].color_data[1][2]</code>.</li>
|
||||
<li><code>color_data</code>：一个包含链中每个LED的RGBW值的颜色列表的列表。每个值都以0.0到1.0的浮点数表示。每个颜色列表包含4个项目（红、绿、蓝、白），即使底层的LED支持较少的颜色通道。例如，可以通过<code>printer["neopixel <配置名>"].color_data[1][2]</code>访问链中第二个neopixel的蓝色值（颜色列表中的第三项）。</li>
|
||||
</ul>
|
||||
<h2 id="mcu">mcu<a class="headerlink" href="#mcu" title="Permanent link">¶</a></h2>
|
||||
<p><a href="Config_Reference.html#mcu">mcu</a>和<a href="Config_Reference.html#mcu-my_extra_mcu">mcu some_name</a>对象提供了以下信息：</p>
|
||||
|
||||
Binary file not shown.
File diff suppressed because one or more lines are too long
@@ -2,237 +2,237 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-20</lastmod>
|
||||
<lastmod>2022-04-21</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in New Issue
Block a user