Deploying to gh-pages from @ Klipper3d/klipper@d9daeb0803 🚀
This commit is contained in:
KevinOConnor
@@ -1592,6 +1592,7 @@
|
||||
</code></pre></div>
|
||||
|
||||
<p>上述操作会使主机创建一个Unix本地套接字。之后，客户应用程序可以创建一个套接字链接，从而给Klipper发送命令。</p>
|
||||
<p>See the <a href="https://github.com/Arksine/moonraker">Moonraker</a> project for a popular tool that can forward HTTP requests to Klipper's API Server Unix Domain Socket.</p>
|
||||
<h2 id="_1">请求格式<a class="headerlink" href="#_1" title="Permanent link">¶</a></h2>
|
||||
<p>套接字进出的数据包应使用JSON编码的字符串，并以ASCII字符0x03作为结尾：</p>
|
||||
<div class="highlight"><pre><span></span><code><json_object_1><0x03><json_object_2><0x03>...
|
||||
|
||||
@@ -1232,6 +1232,13 @@
|
||||
带有 HID 引导程序的STM32F103
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#stm32f103stm32f072-with-msc-bootloader" class="md-nav__link">
|
||||
STM32F103/STM32F072 with MSC bootloader
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -1473,6 +1480,13 @@
|
||||
带有 HID 引导程序的STM32F103
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#stm32f103stm32f072-with-msc-bootloader" class="md-nav__link">
|
||||
STM32F103/STM32F072 with MSC bootloader
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -1761,6 +1775,15 @@ make
|
||||
</code></pre></div>
|
||||
|
||||
<p>可能需要手动进入引导程序，这可以通过设置 "boot 0 "的低电平和 "boot 1 "的高电平来完成。在SKR Mini E3上，"Boot 1 "是不可用的，所以如果你写入过"hid_btt_skr_mini_e3.bin"，可以通过设置PA2的低电平来完成。在SKR Mini E3的 "PIN "文件中，这个引脚在TFT插座上被标记为 "TX0"。在PA2旁边有一个接地引脚，你可以用它来把PA2拉低。</p>
|
||||
<h3 id="stm32f103stm32f072-with-msc-bootloader">STM32F103/STM32F072 with MSC bootloader<a class="headerlink" href="#stm32f103stm32f072-with-msc-bootloader" title="Permanent link">¶</a></h3>
|
||||
<p>The <a href="https://github.com/Telekatz/MSC-stm32f103-bootloader">MSC bootloader</a> is a driverless bootloader capable of flashing over USB.</p>
|
||||
<p>It is possible to flash the bootloader via 3.3v serial using stm32flash as noted in the stm32duino section above, substituting the file name for the desired MSC bootloader binary (ie: MSCboot-Bluepill.bin for the blue pill).</p>
|
||||
<p>For STM32F072 boards it is also possible to flash the bootloader over USB (via DFU) with something like:</p>
|
||||
<div class="highlight"><pre><span></span><code> dfu-util -d 0483:df11 -a 0 -R -D MSCboot-STM32F072.bin -s0x08000000:leave
|
||||
</code></pre></div>
|
||||
|
||||
<p>This bootloader uses 8KiB or 16KiB of flash space, see description of the bootloader (the application must be compiled with with the corresponding starting address).</p>
|
||||
<p>The bootloader can be activated by pressing the reset button of the board twice. As soon as the bootloader is activated, the board appears as a USB flash drive onto which the klipper.bin file can be copied.</p>
|
||||
<h2 id="stm32f4-skr-pro-11">STM32F4 微控制器 (SKR Pro 1.1)<a class="headerlink" href="#stm32f4-skr-pro-11" title="Permanent link">¶</a></h2>
|
||||
<p>STM32F4微控制器配备了一个内置的系统引导程序，能够通过USB（通过DFU）、3.3v串口和其他各种方法进行刷写（更多信息见STM文件AN2606）。一些STM32F4板，如SKR Pro 1.1，不能进入DFU引导程序。基于STM32F405/407的板子可以使用HID引导程序，如果用户愿意通过USB刷写而不是使用SD卡。请注意，你可能需针对你的板子配置和构建一个特定的版本，<a href="https://github.com/Arksine/STM32_HID_Bootloader/releases/latest">针对SKR Pro 1.1的构建可以在这里找到</a>。</p>
|
||||
<p>除非你的板子有DFU功能，否则最容易的写入方法可能是通过3.3v的串口，这与<a href="#stm32f103-micro-controllers-blue-pill-devices">使用stm32flash刷写STM32F103</a>的步骤相同。例如：</p>
|
||||
|
||||
@@ -919,6 +919,13 @@
|
||||
[bltouch]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#smart_effector" class="md-nav__link">
|
||||
[smart_effector]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -2776,6 +2783,13 @@
|
||||
[bltouch]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#smart_effector" class="md-nav__link">
|
||||
[smart_effector]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
@@ -4283,10 +4297,10 @@ max_temp:
|
||||
<div class="highlight"><pre><span></span><code>[screws_tilt_adjust]
|
||||
#screw1:
|
||||
# The (X, Y) coordinate of the first bed leveling screw. This is a
|
||||
# position to command the nozzle to that is directly above the bed
|
||||
# screw (or as close as possible while still being above the bed).
|
||||
# This is the base screw used in calculations. This parameter must
|
||||
# be provided.
|
||||
# position to command the nozzle to so that the probe is directly
|
||||
# above the bed screw (or as close as possible while still being
|
||||
# above the bed). This is the base screw used in calculations. This
|
||||
# parameter must be provided.
|
||||
#screw1_name:
|
||||
# An arbitrary name for the given screw. This name is displayed when
|
||||
# the helper script runs. The default is to use a name based upon
|
||||
@@ -4689,8 +4703,8 @@ cs_pin:
|
||||
# for more details on using this feature.
|
||||
#min_freq: 5
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 120
|
||||
# Maximum frequency to test for resonances. The default is 120 Hz.
|
||||
#max_freq: 133.33
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 75
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
@@ -4848,6 +4862,53 @@ control_pin:
|
||||
# 有关这些参数的信息，请参见"probe"分段。
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="smart_effector">[smart_effector]<a class="headerlink" href="#smart_effector" title="Permanent link">¶</a></h3>
|
||||
<p>The "Smart Effector" from Duet3d implements a Z probe using a force sensor. One may define this section instead of <code>[probe]</code> to enable the Smart Effector specific features. This also enables <a href="G-Codes.html#smart_effector">runtime commands</a> to adjust the parameters of the Smart Effector at run time.</p>
|
||||
<div class="highlight"><pre><span></span><code>[smart_effector]
|
||||
pin:
|
||||
# Pin connected to the Smart Effector Z Probe output pin (pin 5). Note that
|
||||
# pullup resistor on the board is generally not required. However, if the
|
||||
# output pin is connected to the board pin with a pullup resistor, that
|
||||
# resistor must be high value (e.g. 10K Ohm or more). Some boards have a low
|
||||
# value pullup resistor on the Z probe input, which will likely result in an
|
||||
# always-triggered probe state. In this case, connect the Smart Effector to
|
||||
# a different pin on the board. This parameter is required.
|
||||
#control_pin:
|
||||
# Pin connected to the Smart Effector control input pin (pin 7). If provided,
|
||||
# Smart Effector sensitivity programming commands become available.
|
||||
#probe_accel:
|
||||
# If set, limits the acceleration of the probing moves (in mm/sec^2).
|
||||
# A sudden large acceleration at the beginning of the probing move may
|
||||
# cause spurious probe triggering, especially if the hotend is heavy.
|
||||
# To prevent that, it may be necessary to reduce the acceleration of
|
||||
# the probing moves via this parameter.
|
||||
#recovery_time: 0.4
|
||||
# A delay between the travel moves and the probing moves in seconds. A fast
|
||||
# travel move prior to probing may result in a spurious probe triggering.
|
||||
# This may cause 'Probe triggered prior to movement' errors if no delay
|
||||
# is set. Value 0 disables the recovery delay.
|
||||
# Default value is 0.4.
|
||||
#x_offset:
|
||||
#y_offset:
|
||||
# Should be left unset (or set to 0).
|
||||
z_offset:
|
||||
# Trigger height of the probe. Start with -0.1 (mm), and adjust later using
|
||||
# `PROBE_CALIBRATE` command. This parameter must be provided.
|
||||
#speed:
|
||||
# Speed (in mm/s) of the Z axis when probing. It is recommended to start
|
||||
# with the probing speed of 20 mm/s and adjust it as necessary to improve
|
||||
# the accuracy and repeatability of the probe triggering.
|
||||
#samples:
|
||||
#sample_retract_dist:
|
||||
#samples_result:
|
||||
#samples_tolerance:
|
||||
#samples_tolerance_retries:
|
||||
#activate_gcode:
|
||||
#deactivate_gcode:
|
||||
#deactivate_on_each_sample:
|
||||
# See the "probe" section for more information on the parameters above.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_16">额外的步进电机和挤出机<a class="headerlink" href="#_16" title="Permanent link">¶</a></h2>
|
||||
<h3 id="stepper_z1">[stepper_z1]<a class="headerlink" href="#stepper_z1" title="Permanent link">¶</a></h3>
|
||||
<p>Multi-stepper axes. On a cartesian style printer, the stepper controlling a given axis may have additional config blocks defining steppers that should be stepped in concert with the primary stepper. One may define any number of sections with a numeric suffix starting at 1 (for example, "stepper_z1", "stepper_z2", etc.).</p>
|
||||
@@ -5388,14 +5449,25 @@ pin:
|
||||
#sensor_type:
|
||||
#sensor_pin:
|
||||
#control:
|
||||
#pid_Kp:
|
||||
#pid_Ki:
|
||||
#pid_Kd:
|
||||
#pid_deriv_time:
|
||||
#max_delta:
|
||||
#min_temp:
|
||||
#max_temp:
|
||||
# See the "extruder" section for a description of the above parameters.
|
||||
#pid_Kp:
|
||||
#pid_Ki:
|
||||
#pid_Kd:
|
||||
# The proportional (pid_Kp), integral (pid_Ki), and derivative
|
||||
# (pid_Kd) settings for the PID feedback control system. Klipper
|
||||
# evaluates the PID settings with the following general formula:
|
||||
# fan_pwm = max_power - (Kp*e + Ki*integral(e) - Kd*derivative(e)) / 255
|
||||
# Where "e" is "target_temperature - measured_temperature" and
|
||||
# "fan_pwm" is the requested fan rate with 0.0 being full off and
|
||||
# 1.0 being full on. The pid_Kp, pid_Ki, and pid_Kd parameters must
|
||||
# be provided when the PID control algorithm is enabled.
|
||||
#pid_deriv_time: 2.0
|
||||
# A time value (in seconds) over which temperature measurements will
|
||||
# be smoothed when using the PID control algorithm. This may reduce
|
||||
# the impact of measurement noise. The default is 2 seconds.
|
||||
#target_temp: 40.0
|
||||
# A temperature (in Celsius) that will be the target temperature.
|
||||
# The default is 40 degrees.
|
||||
@@ -5457,7 +5529,7 @@ pin:
|
||||
|
||||
<h3 id="neopixel">[neopixel]<a class="headerlink" href="#neopixel" title="Permanent link">¶</a></h3>
|
||||
<p>Neopixel (aka WS2812) LED support (one may define any number of sections with a "neopixel" prefix). See the <a href="G-Codes.html#led">command reference</a> for more information.</p>
|
||||
<p>Note that the <a href="RPi_microcontroller.html">linux mcu</a> implementation does not currently support directly connected neopixels.</p>
|
||||
<p>Note that the <a href="RPi_microcontroller.html">linux mcu</a> implementation does not currently support directly connected neopixels. The current design using the Linux kernel interface does not allow this scenario because the kernel GPIO interface is not fast enough to provide the required pulse rates.</p>
|
||||
<div class="highlight"><pre><span></span><code>[neopixel my_neopixel]
|
||||
pin:
|
||||
# The pin connected to the neopixel. This parameter must be
|
||||
@@ -5468,8 +5540,9 @@ pin:
|
||||
# Neopixel is connected to the pin).
|
||||
#color_order: GRB
|
||||
# Set the pixel order required by the LED hardware (using a string
|
||||
# containing the letters R, G, B, W with W optional). The default is
|
||||
# GRB.
|
||||
# containing the letters R, G, B, W with W optional). Alternatively,
|
||||
# this may be a comma separated list of pixel orders - one for each
|
||||
# LED in the chain. The default is GRB.
|
||||
#initial_RED: 0.0
|
||||
#initial_GREEN: 0.0
|
||||
#initial_BLUE: 0.0
|
||||
|
||||
@@ -1966,6 +1966,33 @@
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#smart_effector" class="md-nav__link">
|
||||
[smart_effector]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[smart_effector]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#set_smart_effector" class="md-nav__link">
|
||||
SET_SMART_EFFECTOR
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#reset_smart_effector" class="md-nav__link">
|
||||
RESET_SMART_EFFECTOR
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -3872,6 +3899,33 @@
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#smart_effector" class="md-nav__link">
|
||||
[smart_effector]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[smart_effector]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#set_smart_effector" class="md-nav__link">
|
||||
SET_SMART_EFFECTOR
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#reset_smart_effector" class="md-nav__link">
|
||||
RESET_SMART_EFFECTOR
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
@@ -4359,7 +4413,7 @@
|
||||
<h4 id="z_offset_apply_probe">Z_OFFSET_APPLY_PROBE<a class="headerlink" href="#z_offset_apply_probe" title="Permanent link">¶</a></h4>
|
||||
<p><code>Z_OFFSET_APPLY_PROBE</code>：将当前的Z 的 G 代码偏移量（就是 babystepping）从 probe 的 z_offset 中减去。该命令将持久化一个常用babystepping 微调值。需要执行 <code>SAVE_CONFIG</code>才能生效。</p>
|
||||
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">¶</a></h3>
|
||||
<p>The query_endstops module is automatically loaded.</p>
|
||||
<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>
|
||||
<p><code>QUERY_ADC [NAME=<config_name>] [PULLUP=<value>]</code> ：返回为配置的模拟引脚收到的最后一个模拟值。如果NAME没有被提供，将报告可用的adc名称列表。如果提供了PULLUP（以欧姆为单位的数值），将会返回原始模拟值和给定的等效电阻。</p>
|
||||
<h3 id="query_endstops">[query_endstops]<a class="headerlink" href="#query_endstops" title="Permanent link">¶</a></h3>
|
||||
@@ -4421,6 +4475,12 @@
|
||||
<p><code>CALC_MEASURED_SKEW [AC=<ac 长度>] [BD=<bd 长度>] [AD=<ad 长度>]</code>：计算并报告基于一个打印件测量的偏斜度（以弧度和角度为单位）。它可以用来验证应用校正后打印机的当前偏斜度。它也可以用来确定是否有必要进行偏斜矫正。有关偏斜矫正打印模型和测量方法详见<a href="Skew_Correction.html">偏斜校正文档</a>。</p>
|
||||
<h4 id="skew_profile">SKEW_PROFILE<a class="headerlink" href="#skew_profile" title="Permanent link">¶</a></h4>
|
||||
<p><code>SKEW_PROFILE [LOAD=<名称>] [SAVE=<名称>] [REMOVE=<名称>]</code>：skew_correction 配置管理命令。 LOAD 将从与提供的名称匹配的配置中载入偏斜状态。 SAVE 会将当前偏斜状态保存到与提供的名称匹配的配置中。 REMOVE 将从持久内存中删除与提供的名称匹配的配置。请注意，在运行 SAVE 或 REMOVE 操作后，必须运行 SAVE_CONFIG G代码才能保存更改。</p>
|
||||
<h3 id="smart_effector">[smart_effector]<a class="headerlink" href="#smart_effector" title="Permanent link">¶</a></h3>
|
||||
<p>Several commands are available when a <a href="Config_Reference.html#smart_effector">smart_effector config section</a> is enabled. Be sure to check the official documentation for the Smart Effector on the <a href="https://duet3d.dozuki.com/Wiki/Smart_effector_and_carriage_adapters_for_delta_printer">Duet3D Wiki</a> before changing the Smart Effector parameters. Also check the <a href="Probe_Calibrate.html">probe calibration guide</a>.</p>
|
||||
<h4 id="set_smart_effector">SET_SMART_EFFECTOR<a class="headerlink" href="#set_smart_effector" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_SMART_EFFECTOR [SENSITIVITY=<sensitivity>] [ACCEL=<accel>] [RECOVERY_TIME=<time>]</code>: Set the Smart Effector parameters. When <code>SENSITIVITY</code> is specified, the respective value is written to the SmartEffector EEPROM (requires <code>control_pin</code> to be provided). Acceptable <code><sensitivity></code> values are 0..255, the default is 50. Lower values require less nozzle contact force to trigger (but there is a higher risk of false triggering due to vibrations during probing), and higher values reduce false triggering (but require larger contact force to trigger). Since the sensitivity is written to EEPROM, it is preserved after the shutdown, and so it does not need to be configured on every printer startup. <code>ACCEL</code> and <code>RECOVERY_TIME</code> allow to override the corresponding parameters at run-time, see the <a href="Config_Reference.html#smart_effector">config section</a> of Smart Effector for more info on those parameters.</p>
|
||||
<h4 id="reset_smart_effector">RESET_SMART_EFFECTOR<a class="headerlink" href="#reset_smart_effector" title="Permanent link">¶</a></h4>
|
||||
<p><code>RESET_SMART_EFFECTOR</code>: Resets Smart Effector sensitivity to its factory settings. Requires <code>control_pin</code> to be provided in the config section.</p>
|
||||
<h3 id="stepper_enable">[stepper_enable]<a class="headerlink" href="#stepper_enable" title="Permanent link">¶</a></h3>
|
||||
<p>The stepper_enable module is automatically loaded.</p>
|
||||
<h4 id="set_stepper_enable">SET_STEPPER_ENABLE<a class="headerlink" href="#set_stepper_enable" title="Permanent link">¶</a></h4>
|
||||
|
||||
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-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2022-04-28</lastmod>
|
||||
<lastmod>2022-04-29</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in New Issue
Block a user