Deploying to gh-pages from @ Klipper3d/klipper@cf3b0475da 🚀
This commit is contained in:
KevinOConnor
@@ -711,6 +711,33 @@
|
||||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<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 @@
|
||||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<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>Tip:</strong> Make sure the <a href="Config_Reference.html#probe">probe X and Y offsets</a> are correctly set as they greatly influence calibration.</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>After setting up the [axis_twist_compensation] module, perform <code>AXIS_TWIST_COMPENSATION_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>The calibration wizard will prompt you to measure the probe Z offset at a few points along the bed</li>
|
||||
<li>The calibration defaults to 3 points but you can use the option <code>SAMPLE_COUNT=</code> to use a different number.</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">Adjust your Z offset</a></li>
|
||||
<li>Perform automatic/probe-based bed tramming operations, such as <a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a>, <a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a> etc</li>
|
||||
<li>Home all axis, then perform a <a href="Bed_Mesh.html">Bed Mesh</a> if required</li>
|
||||
<li>Perform a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> as desired</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>Tip:</strong> Bed temperature and nozzle temperature and size do not seem to have an influence to the calibration process.</p>
|
||||
</blockquote>
|
||||
|
||||
@@ -1968,7 +1968,7 @@ fade_target: 0
|
||||
<li><code>fade_target: 0</code> <em>Valore predefinito: il valore Z medio della mesh</em> Il <code>fade_target</code> può essere considerato come un offset Z aggiuntivo applicato all'intero piatto una volta completata la dissolvenza. In generale vorremmo che questo valore fosse 0, tuttavia ci sono circostanze in cui non dovrebbe esserlo. Ad esempio, supponiamo che la posizione di homing sul piatto sia un valore anomalo, ovvero 0,2 mm inferiore all'altezza media rilevata del piatto. Se <code>fade_target</code> è 0, la dissolvenza ridurrà la stampa in media di 0,2 mm sul piano. Impostando <code>fade_target</code> su .2, l'area home si espanderà di 0,2 mm, tuttavia, il resto del piatto verrà dimensionato accuratamente. Generalmente è una buona idea lasciare "fade_target" fuori dalla configurazione in modo da utilizzare l'altezza media della mesh, tuttavia potrebbe essere preferibile regolare manualmente il target di dissolvenza se si desidera stampare su una porzione specifica del piano.</li>
|
||||
</ul>
|
||||
<h3 id="configuring-the-zero-reference-position">Configuring the zero reference position<a class="headerlink" href="#configuring-the-zero-reference-position" title="Permanent link">¶</a></h3>
|
||||
<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#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>
|
||||
<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 @@
|
||||
Benchmark step rate 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="#benchmark-step-rate-rp2040" class="md-nav__link">
|
||||
Benchmark step rate RP2040
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -1613,6 +1620,13 @@
|
||||
Benchmark step rate 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="#benchmark-step-rate-rp2040" class="md-nav__link">
|
||||
Benchmark step rate 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 stepper</td>
|
||||
<td>45</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 stepper</td>
|
||||
<td>190</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="benchmark-della-velocita-di-passo-ar100">Benchmark della velocità di passo AR100<a class="headerlink" href="#benchmark-della-velocita-di-passo-ar100" title="Permanent link">¶</a></h3>
|
||||
<p>La seguente sequenza di configurazione viene utilizzata sulla CPU AR100 (Allwinner 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>Il test è stato eseguito l'ultima volta sul commit <code>08d037c6</code> con la versione gcc <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> su un microcontrollore Allwinner 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="benchmark-step-rate-rp2040">Benchmark step rate RP2040<a class="headerlink" href="#benchmark-step-rate-rp2040" title="Permanent link">¶</a></h3>
|
||||
<p>Sull'RP2040 viene utilizzata la seguente sequenza di configurazione:</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>Il test è stato eseguito l'ultima volta su commit <code>59314d99</code> con versione gcc <code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code> su una scheda Raspberry Pi Pico.</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 stepper</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 stepper</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="benchmark-step-rate-mcu-linux">Benchmark step rate MCU Linux<a class="headerlink" href="#benchmark-step-rate-mcu-linux" title="Permanent link">¶</a></h3>
|
||||
<p>La seguente sequenza di configurazione viene utilizzata su un Raspberry Pi:</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>Esaminare le classi cinematiche esistenti nella directory klippy/kinematics/. Le classi cinematiche hanno il compito di convertire una mossa in coordinate cartesiane nel movimento su ogni stepper. Si dovrebbe essere in grado di copiare uno di questi file come punto di partenza.</li>
|
||||
<li>Implementa in C le funzioni di posizione cinematica dello stepper per ogni stepper se non sono già disponibili (vedi kin_cart.c, kin_corexy.c e kin_delta.c in klippy/chelper/). La funzione dovrebbe chiamare <code>move_get_coord()</code> per convertire un dato tempo di spostamento (in secondi) in una coordinata cartesiana (in millimetri), e quindi calcolare la posizione dello stepper desiderata (in millimetri) da quella coordinata cartesiana.</li>
|
||||
<li>Implementa il metodo <code>calc_position()</code> nella nuova classe cinematica. Questo metodo calcola la posizione della testa di stampa in coordinate cartesiane dalla posizione di ogni stepper. Non è necessario che sia efficiente poiché in genere viene chiamato solo durante le operazioni di homing e probing.</li>
|
||||
<li>Altri metodi. Implementa i metodi <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code> e <code>set_position()</code>. Queste funzioni sono in genere utilizzate per fornire verifiche cinematiche specifiche. Tuttavia, all'inizio dello sviluppo è possibile utilizzare il codice boilerplate qui.</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>Implementare casi di prova. Crea un file g-code con una serie di movimenti che possono testare casi importanti per la cinematica data. Segui la <a href="Debugging.html">documentazione di debug</a> per convertire questo file di codice G in comandi del microcontrollore. Questo è utile per esercitare corner case e per verificare la presenza di regressioni.</li>
|
||||
</ol>
|
||||
<h2 id="porting-su-un-nuovo-microcontrollore">Porting su un nuovo microcontrollore<a class="headerlink" href="#porting-su-un-nuovo-microcontrollore" title="Permanent link">¶</a></h2>
|
||||
|
||||
@@ -1396,6 +1396,11 @@
|
||||
<p>Questo documento copre le modifiche software recenti al file di configurazione che non sono compatibili con le versioni precedenti. È una buona idea rivedere questo documento durante l'aggiornamento del software Klipper.</p>
|
||||
<p>Tutte le date in questo documento sono approssimative.</p>
|
||||
<h2 id="cambiamenti">Cambiamenti<a class="headerlink" href="#cambiamenti" 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 @@
|
||||
display 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 @@
|
||||
display 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>
|
||||
@@ -5292,8 +5320,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.
|
||||
@@ -5303,6 +5332,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>
|
||||
@@ -5327,47 +5393,58 @@ cs_pin:
|
||||
<p>Supporto per test di risonanza e calibrazione automatica del input shaper. Per utilizzare la maggior parte delle funzionalità di questo modulo, devono essere installate dipendenze software aggiuntive; fare riferimento a <a href="Measuring_Resonances.html">Measuring Resonances</a> e al <a href="G-Codes.html#resonance_tester">command reference</a> per ulteriori informazioni. Per ulteriori informazioni sul parametro <code>max_smoothing</code> e sul suo utilizzo, vedere la sezione <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> della guida alla misurazione delle risonanze.</p>
|
||||
<div class="highlight"><pre><span></span><code>[resonance_tester]
|
||||
#probe_points:
|
||||
# Un elenco di coordinate X, Y, Z di punti (un punto per linea) in cui
|
||||
# testare le risonanze. Almeno un punto è richiesto. Assicurati che tutti
|
||||
# i punti con un margine di sicurezza nel piano XY (~ pochi centimetri)
|
||||
# siano raggiungibili dalla testa di stampa.
|
||||
# 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:
|
||||
# Un nome del chip dell'accelerometro da utilizzare per le misurazioni.
|
||||
# Se il chip adxl345 è stato definito senza un nome esplicito, questo
|
||||
# parametro può semplicemente fare riferimento ad esso come
|
||||
# "accel_chip: adxl345", altrimenti deve essere fornito anche un nome
|
||||
# esplicito, ad es. "accel_chip: adxl345 mio_chip_nome". È necessario
|
||||
# impostare questo o i due parametri successivi.
|
||||
# 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:
|
||||
# Nomi dei chip dell'accelerometro da utilizzare per le misurazioni per
|
||||
# ciascuno degli assi. Può essere utile, ad esempio, su una stampante con
|
||||
# piatto, se due accelerometri separati sono montati sul piatto (per l'asse Y)
|
||||
# e sulla testa di stampa (per l'asse X). Questi parametri hanno lo stesso
|
||||
# formato del parametro 'accel_chip'.
|
||||
# È necessario fornire solo 'accel_chip' o questi due parametri.
|
||||
# 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:
|
||||
# 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
|
||||
# Frequenza minima per testare le risonanze. L'impostazione è 5 Hz.
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 133.33
|
||||
# Frequenza massima per testare le risonanze. L'impostazione è 133,33 Hz.
|
||||
#accel_per_hz: 75
|
||||
# Questo parametro viene utilizzato per determinare quale accelerazione
|
||||
# utilizzare per testare una frequenza specifica: accel = accel_per_hz * freq.
|
||||
# Maggiore è il valore, maggiore è l'energia delle oscillazioni. Può essere
|
||||
# impostato su un valore inferiore al valore predefinito se le risonanze
|
||||
# diventano troppo forti sulla stampante. Tuttavia, valori più bassi rendono
|
||||
# le misurazioni delle risonanze ad alta frequenza meno precise.
|
||||
# Il valore predefinito è 75 (mm/sec).
|
||||
# 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
|
||||
# Determina la velocità del test. Quando si testano tutte le frequenze
|
||||
# nell'intervallo [freq_min, freq_max], ogni secondo la frequenza aumenta
|
||||
# di hz_per_sec. Valori piccoli rallentano il test e valori grandi diminuiscono
|
||||
# la precisione del test. Il valore predefinito è 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="helper-per-i-file-di-configurazione">Helper per i file di configurazione<a class="headerlink" href="#helper-per-i-file-di-configurazione" title="Permanent link">¶</a></h2>
|
||||
@@ -5600,8 +5677,44 @@ 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>Uno strumento per compensare letture imprecise della sonda dovute alla torsione nel portale X. Consultare la <a href="Axis_Twist_Compensation.html">Guida alla compensazione della torsione dell'asse</a> per informazioni più dettagliate su sintomi, configurazione e impostazione.</p>
|
||||
<div class="highlight"><pre><span></span><code>italiano
|
||||
<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.
|
||||
# The default is 50.
|
||||
#horizontal_move_z: 5
|
||||
# The height (in mm) that the head should be commanded to move to
|
||||
# just prior to starting a probe operation. The default is 5.
|
||||
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.
|
||||
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.
|
||||
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 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="motori-passo-passo-ed-estrusori-aggiuntivi">Motori passo-passo ed estrusori aggiuntivi<a class="headerlink" href="#motori-passo-passo-ed-estrusori-aggiuntivi" title="Permanent link">¶</a></h2>
|
||||
@@ -5882,6 +5995,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="sensori-di-temperatura">Sensori di temperatura<a class="headerlink" href="#sensori-di-temperatura" title="Permanent link">¶</a></h2>
|
||||
@@ -6998,6 +7115,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
|
||||
@@ -7273,15 +7391,16 @@ wiper:
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type:
|
||||
# The type of LCD chip in use. This may be "hd44780", "hd44780_spi",
|
||||
# "st7920", "emulated_st7920", "uc1701", "ssd1306", or "sh1106".
|
||||
# "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:
|
||||
# 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
|
||||
# displays and _default_16x4 for other displays.
|
||||
# for more information). The default is _default_20x4 for hd44780 or
|
||||
# aip31068_spi displays and _default_16x4 for other displays.
|
||||
#menu_timeout:
|
||||
# Timeout for menu. Being inactive this amount of seconds will
|
||||
# trigger menu exit or return to root menu when having autorun
|
||||
@@ -7398,6 +7517,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="display-st7920">display st7920<a class="headerlink" href="#display-st7920" title="Permanent link">¶</a></h4>
|
||||
<p>Informazioni sulla configurazione dei display st7920 (utilizzati nei display di tipo "RepRapDiscount 12864 Full Graphic Smart Controller").</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
@@ -7756,7 +7895,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
|
||||
@@ -7819,13 +7958,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="supporto-hardware-per-specifica-scheda">Supporto hardware per specifica scheda<a class="headerlink" href="#supporto-hardware-per-specifica-scheda" title="Permanent link">¶</a></h2>
|
||||
@@ -7972,11 +8128,11 @@ serial:
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<p>Supporto per sensore magnetico Hall per la lettura delle misurazioni dell'angolo del motore passo-passo utilizzando i chip SPI a1333, as5047d o tle5012b. Le misurazioni sono disponibili tramite <a href="API_Server.html">Server API</a> e <a href="Debugging.html#motion-analysis-and-data-logging">strumento di analisi del movimento</a>. Vedere il <a href="G-Codes.html#angle">Riferimento G-Code</a> per i comandi disponibili.</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:
|
||||
# The type of the magnetic hall sensor chip. Available choices are
|
||||
# "a1333", "as5047d", and "tle5012b". This parameter must be
|
||||
# "a1333", "as5047d", "mt6816", "mt6826s", and "tle5012b". This parameter must be
|
||||
# specified.
|
||||
#sample_period: 0.000400
|
||||
# The query period (in seconds) to use during measurements. The
|
||||
@@ -8020,7 +8176,7 @@ cs_pin:
|
||||
<h3 id="impostazioni-i2c-comuni">Impostazioni I2C comuni<a class="headerlink" href="#impostazioni-i2c-comuni" title="Permanent link">¶</a></h3>
|
||||
<p>I seguenti parametri sono generalmente disponibili per i dispositivi che utilizzano un bus I2C.</p>
|
||||
<p>Tieni presente che l'attuale supporto del microcontrollore di Klipper per I2C generalmente non tollera il rumore di linea. Errori imprevisti sui cavi I2C potrebbero far sì che Klipper sollevi un errore di runtime. Il supporto di Klipper per il ripristino degli errori varia a seconda del tipo di microcontrollore. In genere si consiglia di utilizzare solo dispositivi I2C che si trovano sullo stesso circuito stampato del microcontrollore.</p>
|
||||
<p>La maggior parte delle implementazioni del microcontrollore Klipper supportano solo una <code>i2c_speed</code> di 100000 (<em>modalità standard</em>, 100kbit/s). Il microcontrollore Klipper "Linux" supporta una velocità 400000 (<em>modalità veloce</em>, 400kbit/s), ma deve essere <a href="RPi_microcontroller.html#optional-enabling-i2c">impostato nel sistema operativo</a> e <code>i2c_speed</code> il parametro viene altrimenti ignorato. Il microcontrollore Klipper "RP2040" e la famiglia ATmega AVR supportano una velocità di 400000 tramite il parametro <code>i2c_speed</code>. Tutti gli altri microcontrollori Klipper utilizzano una velocità 100000 e ignorano il parametro "i2c_speed".</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 @@
|
||||
# temperature probe configuration...
|
||||
</code></pre></div>
|
||||
|
||||
<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.</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 manufacturers may offer a stock drift calibration that can be manually added to <code>drift_calibration</code> option of the <code>[probe_eddy_current]</code> section. If they do not, or if the stock calibration does not perform well on your system, the <code>temperature_probe</code> module offers a manual calibration procedure via the <code>TEMPERATURE_PROBE_CALIBRATE</code> gcode command.</p>
|
||||
<p>Prior to performing calibration the user should have an idea of what the maximum attainable temperature probe coil temperature is. This temperature should be used to set the <code>TARGET</code> parameter of the <code>TEMPERATURE_PROBE_CALIBRATE</code> command. The goal is to calibrate across the widest temperature range possible, thus its desirable to start with the printer cold and finish with the coil at the maximum temperature it can reach.</p>
|
||||
<p>Once a <code>[temperature_probe]</code> is configured, the following steps may be taken to perform thermal drift calibration:</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>I seguenti comandi sono disponibili quando una <a href="Config_Reference.html#angle">sezione di configurazione dell'angolo</a> è abilitata.</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>: Esegue la calibrazione dell'angolo sul sensore dato (deve esserci una sezione di configurazione <code>[angle chip_name]</code> che ha specificato un parametro <code>stepper</code>). IMPORTANTE - questo strumento comanderà al motore passo-passo di muoversi senza controllare i normali limiti della cinematica. Idealmente, il motore dovrebbe essere scollegato da qualsiasi carrello della stampante prima di eseguire la calibrazione. Se non è possibile scollegare lo stepper dalla stampante, assicurarsi che il carrello sia vicino al centro della sua guida prima di iniziare la calibrazione. (Il motore passo-passo può spostarsi avanti o indietro di due rotazioni complete durante questo test.) Dopo aver completato questo test, utilizzare il comando <code>SAVE_CONFIG</code> per salvare i dati di calibrazione nel file di configurazione. Per utilizzare questo strumento è necessario installare il pacchetto Python "numpy" (consultare il <a href="Measuring_Resonances.html#software-installation">measuring resonance document</a> per ulteriori informazioni).</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=<config_name> REG=<register></code>: Interroga il registro del sensore "register" (ad es. 44 o 0x2C). Può essere utile per scopi di debug. Questo è disponibile solo per i chip 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>: Initiates the X twist calibration wizard. <code>SAMPLE_COUNT</code> specifies the number of points along the X axis to calibrate at and defaults to 3.</p>
|
||||
<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>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#bed_mesh">sezione di configurazione bed_mesh</a> è abilitata (consultare anche la <a href="Bed_Mesh.html">guida della mesh del letto</a>).</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>Il comando seguente è disponibile quando una <a href="Config_Reference.html#fan_generic">sezione di configurazione fan_generic</a> è abilitata.</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=<velocità></code> Questo comando imposta la velocità di una ventola. "velocità" deve essere compresa tra 0.0 e 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>Il comando seguente è disponibile quando è abilitata una sezione di configurazione <a href="Config_Reference.html#filament_switch_sensor">filament_switch_sensor</a> o <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=<nome_config> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]</code>: Questo comando sposterà forzatamente lo stepper dato della distanza data (in mm) alla velocità costante data (in mm/ S). Se viene specificato ACCEL ed è maggiore di zero, verrà utilizzata l'accelerazione data (in mm/s^2); altrimenti non viene eseguita alcuna accelerazione. Non vengono effettuati controlli sui limiti; non vengono effettuati aggiornamenti cinematici; altri stepper paralleli su un asse non verranno spostati. Prestare attenzione poiché un comando errato potrebbe causare danni! L'uso di questo comando metterà quasi sicuramente la cinematica di basso livello in uno stato errato; emettere un G28 in seguito per ripristinare la cinematica. Questo comando è destinato alla diagnostica e al debug di basso livello.</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=<valore>] [Y=<valore>] [Z=<valore>]</code>: forza il codice cinematico di basso livello a credere che la testa di stampa si trovi nella posizione cartesiana data. Questo è un comando diagnostico e di debug; utilizzare SET_GCODE_OFFSET e/o G92 per le normali trasformazioni degli assi. Se un asse non è specificato, verrà impostato automaticamente sulla posizione in cui la testa è stata comandata l'ultima volta. L'impostazione di una posizione errata o non valida può causare errori software interni. Questo comando potrebbe invalidare futuri controlli sui confini; emettere un G28 in seguito per ripristinare la cinematica.</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>Il modulo gcode viene caricato automaticamente.</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>Il comando seguente è disponibile quando una <a href="Config_Reference.html#pin_output">sezione di configurazione pin_output</a> è abilitata.</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>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#palette2">sezione di configurazione della palette2</a> è abilitata.</p>
|
||||
<p>Le stampe di Palette funzionano incorporando speciali OCodes (Codici Omega) nel file GCode:</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>Il modulo query_adc viene caricato automaticamente.</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>: misura ed riporta il rumore per tutti gli assi di tutti i chip dell'accelerometro abilitati.</p>
|
||||
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">¶</a></h4>
|
||||
<p><code>TEST_RESONANCES AXIS=<asse> OUTPUT=<risonanze,dati_grezzi> [NAME=<nome>] [FREQ_START=<freq_min>] [FREQ_END=<freq_max>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [ POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]</code>: esegue il test di risonanza in tutti i punti sonda configurati per l'"asse" richiesto e misura l'accelerazione utilizzando i chip dell'accelerometro configurati per il rispettivo asse. "asse" può essere X o Y, oppure specificare una direzione arbitraria come <code>AXIS=dx,dy</code>, dove dx e dy sono numeri in virgola mobile che definiscono un vettore di direzione (es. <code>AXIS=X</code>, <code>AXIS=Y</code>, o <code>AXIS=1,-1</code> per definire una direzione diagonale). Nota che <code>AXIS=dx,dy</code> e <code>AXIS=-dx,-dy</code> sono equivalenti. <code>adxl345_chip_name</code> può essere uno o più chip adxl345 configurati, delimitati da virgole, ad esempio <code>CHIPS="adxl345, adxl345 rpi"</code>. Nota che <code>adxl345</code> può essere omesso dai chip adxl345 denominati. Se POINT è specificato, sovrascriverà i punti configurati in <code>[resonance_tester]</code>. Se <code>INPUT_SHAPING=0</code> o non impostato (predefinito), disabilita l'input shaping per il test di risonanza, perché non è valido eseguire il test di risonanza con input shaper abilitato. Il parametro <code>OUTPUT</code> è un elenco separato da virgole di cui verranno scritti gli output. Se viene richiesto <code>raw_data</code>, i dati grezzi dell'accelerometro vengono scritti in un file o in una serie di file <code>/tmp/raw_data_<asse>_[<nome_chip>_][<punto>_]<nome>.csv</code> con (<code><punto>_</code> parte del nome generata solo se è configurato più di 1 punto sonda o è specificato PUNTO). Se viene specificato <code>resonances</code>, la risposta in frequenza viene calcolata (su tutti i punti sonda) e scritta nel file <code>/tmp/resonances_<asse>_<nome>.csv</code>. Se non è impostato, OUTPUT è impostato su <code>risonanze</code> e NAME è impostato sull'ora corrente nel formato "AAAAMMGG_HHMMSS".</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>I seguenti comandi G-Code standard sono disponibili quando la <a href="Config_Reference.html#respond">sezione di configurazione di risposta</a> è abilitata:</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>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#z_tilt">sezione z_tilt config</a> è abilitata.</p>
|
||||
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">¶</a></h4>
|
||||
<p><code>Z_TILT_ADJUST [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: questo comando sonda i punti specificati nella configurazione e quindi apporta regolazioni indipendenti a ciascun stepper Z per compensare l'inclinazione. Vedere il comando PROBE per i dettagli sui parametri opzionali della sonda. Il valore opzionale <code>HORIZONTAL_MOVE_Z</code> sovrascrive l'opzione <code>horizontal_move_z</code> specificata nel file di configurazione.</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="#configure-lis2dw-series" class="md-nav__link">
|
||||
Configure LIS2DW series
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -990,6 +990,13 @@
|
||||
Seleziona 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="#configure-lis2dw-series" class="md-nav__link">
|
||||
Configure LIS2DW series
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -1852,6 +1859,13 @@
|
||||
Seleziona 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="misurazione-delle-risonanze">Misurazione delle risonanze<a class="headerlink" href="#misurazione-delle-risonanze" 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="istruzioni-per-linstallazione">Istruzioni per l'installazione<a class="headerlink" href="#istruzioni-per-linstallazione" title="Permanent link">¶</a></h2>
|
||||
@@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
|
||||
</code></pre></div>
|
||||
|
||||
<p>Quindi, per installare NumPy nell'ambiente Klipper, esegui il comando:</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>Nota che, a seconda delle prestazioni della CPU, potrebbe volerci <em>molto</em> tempo, fino a 10-20 minuti. Sii paziente e attendi il completamento dell'installazione. In alcune occasioni, se la scheda ha poca RAM, l'installazione potrebbe non riuscire e sarà necessario abilitare la swap.</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="configura-adxl345-con-rpi">Configura ADXL345 con RPi<a class="headerlink" href="#configura-adxl345-con-rpi" title="Permanent link">¶</a></h4>
|
||||
<p>First, check and follow the instructions in the <a href="RPi_microcontroller.html">RPi Microcontroller document</a> to setup the "linux mcu" on the Raspberry Pi. This will configure a second Klipper instance that runs on your Pi.</p>
|
||||
<p>Assicurati che il driver SPI di Linux sia abilitato eseguendo <code>sudo raspi-config</code> e abilitando SPI nel menu "Opzioni di interfaccia".</p>
|
||||
@@ -2257,7 +2281,7 @@ pin: adxl:gpio23
|
||||
</code></pre></div>
|
||||
|
||||
<p>Riavvia Klipper tramite il comando <code>RESTART</code>.</p>
|
||||
<h4 id="configure-lis2dw-series">Configure LIS2DW series<a class="headerlink" href="#configure-lis2dw-series" 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 lis]
|
||||
# Change <mySerial> to whatever you found above. For example,
|
||||
# usb-Klipper_rp2040_E661640843545B2E-if00
|
||||
@@ -2482,6 +2506,8 @@ max_smoothing: 0.25 # un esempio
|
||||
|
||||
<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>Se stai eseguendo una ricalibrazione dello shaper e lo smoothing riportato per la configurazione dello shaper suggerita è quasi lo stesso di quello ottenuto durante la calibrazione precedente, questo passaggio può essere saltato.</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="test-di-assi-personalizzati">Test di assi personalizzati<a class="headerlink" href="#test-di-assi-personalizzati" title="Permanent link">¶</a></h3>
|
||||
<p>Il comando <code>TEST_RESONANCES</code> supporta assi personalizzati. Anche se questo non è molto utile per la calibrazione del input shaper, può essere utilizzato per studiare in profondità le risonanze della stampante e per controllare, ad esempio, la tensione della cinghia.</p>
|
||||
<p>Per controllare la tensione della cinghia sulle stampanti CoreXY, eseguire</p>
|
||||
|
||||
@@ -1447,7 +1447,7 @@ git clone https://github.com/Klipper3d/klipper
|
||||
<h2 id="configuring-octoprint-to-use-klipper">Configuring OctoPrint to use Klipper<a class="headerlink" href="#configuring-octoprint-to-use-klipper" title="Permanent link">¶</a></h2>
|
||||
<p>The OctoPrint web server needs to be configured to communicate with the Klipper host software. Using a web browser, login to the OctoPrint web page and then configure the following items:</p>
|
||||
<p>Navigate to the Settings tab (the wrench icon at the top of the page). Under "Serial Connection" in "Additional serial ports" add:</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>Then click "Save".</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 è lo sponsor ufficiale della scheda madre di Klipper. BIGTREETECH si impegna a sviluppare prodotti innovativi e competitivi per servire meglio la comunità della stampa 3D. Seguili su <a href="https://www.facebook.com/BIGTREETECH">Facebook</a> o <a href="https://twitter.com/BigTreeTech">Twitter</a>.</p>
|
||||
<h2 id="sponsors_1">Sponsors<a class="headerlink" href="#sponsors_1" 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="sviluppatori-klipper">Sviluppatori Klipper<a class="headerlink" href="#sviluppatori-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 è l'autore originale e l'attuale manutentore di Klipper. Fai una donazione su: <a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> o <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
it/sitemap.xml
110
it/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