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

Deploying to gh-pages from @ Klipper3d/klipper@1cc6398074 🚀

Browse Source
This commit is contained in:
KevinOConnor
2025-05-04 00:06:21 +00:00
parent 9d64784cd9
commit 06b88075fb
308 changed files with 12816 additions and 2971 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
it/404.html
View File

@@ -1281,8 +1281,8 @@
<li class="md-nav__item">
<a href="/Load_Cell.md" class="md-nav__link">
None
<a href="/Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

36
it/API_Server.html
View File

@@ -1177,15 +1177,8 @@
</li>
<li class="md-nav__item">
<a href="#hx71xdump_hx71x" class="md-nav__link">
hx71x/dump_hx71x
</a>
</li>
<li class="md-nav__item">
<a href="#ads1220dump_ads1220" class="md-nav__link">
ads1220/dump_ads1220
<a href="#load_celldump_force" class="md-nav__link">
load_cell/dump_force
</a>
</li>
@@ -1517,8 +1510,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1714,15 +1707,8 @@
</li>
<li class="md-nav__item">
<a href="#hx71xdump_hx71x" class="md-nav__link">
hx71x/dump_hx71x
</a>
</li>
<li class="md-nav__item">
<a href="#ads1220dump_ads1220" class="md-nav__link">
ads1220/dump_ads1220
<a href="#load_celldump_force" class="md-nav__link">
load_cell/dump_force
</a>
</li>
@@ -1881,12 +1867,10 @@ gcode:
<p>Questo endpoint viene utilizzato per iscriversi a <a href="Config_Reference.html#angle">dati del sensore angolare</a>. L'ottenimento di questi aggiornamenti di movimento di basso livello può essere utile per scopi diagnostici e di debug. L'utilizzo di questo endpoint può aumentare il carico di sistema di Klipper.</p>
<p>Una richiesta può essere simile a: <code>{"id": 123, "method":"angle/dump_angle", "params": {"sensor": "my_angle_sensor", "response_template": {}}}</code> e potrebbe restituire: <code>{"id": 123,"result":{"header":["time","angle"]}}</code> e potrebbe in seguito produrre messaggi asincroni come: <code>{"params":{"position_offset":3.151562 ,"errori":0, "dati":[[1290.951905,-5063],[1290.952321,-5065]]}}</code></p>
<p>Il campo "intestazione" nella risposta alla query iniziale viene utilizzato per descrivere i campi trovati nelle risposte "dati" successive.</p>
<h3 id="hx71xdump_hx71x">hx71x/dump_hx71x<a class="headerlink" href="#hx71xdump_hx71x" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to raw HX711 and HX717 ADC data. Obtaining these low-level ADC updates may be useful for diagnostic and debugging purposes. Using this endpoint may increase Klipper's system load.</p>
<p>A request may look like: <code>{"id": 123, "method":"hx71x/dump_hx71x", "params": {"sensor": "load_cell", "response_template": {}}}</code> and might return: <code>{"id": 123,"result":{"header":["time","counts","value"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"data":[[3292.432935, 562534, 0.067059278], [3292.4394937, 5625322, 0.670590639]]}}</code></p>
<h3 id="ads1220dump_ads1220">ads1220/dump_ads1220<a class="headerlink" href="#ads1220dump_ads1220" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to raw ADS1220 ADC data. Obtaining these low-level ADC updates may be useful for diagnostic and debugging purposes. Using this endpoint may increase Klipper's system load.</p>
<p>A request may look like: <code>{"id": 123, "method":"ads1220/dump_ads1220", "params": {"sensor": "load_cell", "response_template": {}}}</code> and might return: <code>{"id": 123,"result":{"header":["time","counts","value"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"data":[[3292.432935, 562534, 0.067059278], [3292.4394937, 5625322, 0.670590639]]}}</code></p>
<h3 id="load_celldump_force">load_cell/dump_force<a class="headerlink" href="#load_celldump_force" title="Permanent link">&para;</a></h3>
<p>This endpoint is used to subscribe to force data produced by a load_cell. Using this endpoint may increase Klipper's system load.</p>
<p>A request may look like: <code>{"id": 123, "method":"load_cell/dump_force", "params": {"sensor": "load_cell", "response_template": {}}}</code> and might return: <code>{"id": 123,"result":{"header":["time", "force (g)", "counts", "tare_counts"]}}</code> and might later produce asynchronous messages such as: <code>{"params":{"data":[[3292.432935, 40.65, 562534, -234467]]}}</code></p>
<p>Il campo "intestazione" nella risposta alla query iniziale viene utilizzato per descrivere i campi trovati nelle risposte "dati" successive.</p>
<h3 id="pause_resumecancel">pause_resume/cancel<a class="headerlink" href="#pause_resumecancel" title="Permanent link">&para;</a></h3>
<p>Questo endpoint è simile all'esecuzione del comando G-Code "PRINT_CANCEL". Ad esempio: <code>{"id": 123, "method": "pause_resume/cancel"}</code></p>
<p>Come con l'endpoint "gcode/script", questo endpoint viene completato solo dopo il completamento di tutti i comandi G-Code in sospeso.</p>

50
it/Axis_Twist_Compensation.html
View File

@@ -726,13 +726,6 @@
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>
@@ -1365,8 +1358,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1440,13 +1433,6 @@
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>
@@ -1479,7 +1465,7 @@
<h1 id="compensazione-torsione-assi">Compensazione torsione assi<a class="headerlink" href="#compensazione-torsione-assi" title="Permanent link">&para;</a></h1>
<p>Questo documento descrive il modulo [axis_twist_compensation].</p>
<p>This document describes the <code>[axis_twist_compensation]</code> module.</p>
<p>Some printers may have a small twist in their X rail which can skew the results of a probe attached to the X carriage. This is common in printers with designs like the Prusa MK3, Sovol SV06 etc and is further described under <a href="Probe_Calibrate.html#location-bias-check">probe location
bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed Mesh</a>, <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 returning inaccurate representations of the bed.</p>
<p>Questo modulo utilizza misurazioni manuali da parte dell'utente per correggere i risultati della sonda. Tieni presente che se l'asse è notevolmente distorto, ti consigliamo vivamente di utilizzare mezzi meccanici per ripararlo prima di applicare le correzioni del software.</p>
@@ -1495,42 +1481,38 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
<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=&lt;value&gt;</code></p>
<p>This command will calibrate the X-axis by default.</p>
<ul>
<li>The calibration wizard will prompt you to measure the probe Z offset at several points along the bed.</li>
<li>By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=&lt;value&gt;</code></li>
</ul>
<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>
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to <a href="Probe_Calibrate.html#calibrating-probe-z-offset">adjust your Z offset</a>.</li>
<li><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</li>
</ol>
<ul>
<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>
</li>
<li>
<p><strong>Finalize the Setup:</strong></p>
<ol>
<li><strong>Finalize the Setup:</strong></li>
</ol>
<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">&para;</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">&para;</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>
<h2 id="axis_twist_compensation-setup-and-commands">[axis_twist_compensation] setup and commands<a class="headerlink" href="#axis_twist_compensation-setup-and-commands" title="Permanent link">&para;</a></h2>
<p>Configuration options for [axis_twist_compensation] can be found in the <a href="Config_Reference.html#axis_twist_compensation">Configuration Reference</a>.</p>
<p>Commands for [axis_twist_compensation] can be found in the <a href="G-Codes.html#axis_twist_compensation">G-Codes Reference</a></p>
<p>Configuration options for <code>[axis_twist_compensation]</code> can be found in the <a href="Config_Reference.html#axis_twist_compensation">Configuration Reference</a>.</p>
<p>Commands for <code>[axis_twist_compensation]</code> can be found in the <a href="G-Codes.html#axis_twist_compensation">G-Codes Reference</a></p>
</article>

4
it/BLTouch.html
View File

@@ -1380,8 +1380,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Beaglebone.html
View File

@@ -1399,8 +1399,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Bed_Level.html
View File

@@ -1345,8 +1345,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Bed_Mesh.html
View File

@@ -1568,8 +1568,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

28
it/Benchmarks.html
View File

@@ -1475,8 +1475,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1985,30 +1985,30 @@ finalize_config crc=0
</tbody>
</table>
<h3 id="stm32h7-benchmark-della-velocita-di-step">STM32H7 benchmark della velocità di step<a class="headerlink" href="#stm32h7-benchmark-della-velocita-di-step" title="Permanent link">&para;</a></h3>
<p>La seguente sequenza di configurazione viene utilizzata su un STM32H743VIT6:</p>
<p>The following configuration sequence is used on STM32H723:</p>
<div class="highlight"><pre><span></span><code>allocate_oids count=3
config_stepper oid=0 step_pin=PD4 dir_pin=PD3 invert_step=-1 step_pulse_ticks=0
config_stepper oid=1 step_pin=PA15 dir_pin=PA8 invert_step=-1 step_pulse_ticks=0
config_stepper oid=2 step_pin=PE2 dir_pin=PE3 invert_step=-1 step_pulse_ticks=0
config_stepper oid=0 step_pin=PA13 dir_pin=PB5 invert_step=-1 step_pulse_ticks=52
config_stepper oid=1 step_pin=PB2 dir_pin=PB6 invert_step=-1 step_pulse_ticks=52
config_stepper oid=2 step_pin=PB3 dir_pin=PB7 invert_step=-1 step_pulse_ticks=52
finalize_config crc=0
</code></pre></div>
<p>Il test è stato eseguito l'ultima volta su commit <code>00191b5c</code> con versione gcc <code>arm-none-eabi-gcc (15:8-2019-q3-1+b1) 8.3.1 20190703 (release) [gcc-8-branch revisione 273027]</code>.</p>
<p>The test was last run on commit <code>554ae78d</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code>.</p>
<table>
<thead>
<tr>
<th>stm32h7</th>
<th>stm32h723</th>
<th>ticks</th>
</tr>
</thead>
<tbody>
<tr>
<td>1 stepper</td>
<td>44</td>
<td>70</td>
</tr>
<tr>
<td>3 stepper</td>
<td>198</td>
<td>181</td>
</tr>
</tbody>
</table>
@@ -2215,7 +2215,7 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
finalize_config crc=0
</code></pre></div>
<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>
<p>The test was last run on commit <code>14c105b8</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>
@@ -2226,11 +2226,11 @@ finalize_config crc=0
<tbody>
<tr>
<td>1 stepper</td>
<td>5</td>
<td>3</td>
</tr>
<tr>
<td>3 stepper</td>
<td>22</td>
<td>14</td>
</tr>
</tbody>
</table>
@@ -2252,7 +2252,7 @@ finalize_config crc=0
</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>
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 200Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 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">&para;</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

4
it/Bootloader_Entry.html
View File

@@ -1429,8 +1429,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Bootloaders.html
View File

@@ -1501,8 +1501,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

5
it/CANBUS.html
View File

@@ -1371,8 +1371,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1549,6 +1549,7 @@ iface can0 can static
</li>
</ul>
<ul>
<li>It is only valid to use USB to CAN bridge mode if there is a functioning CAN bus with at least one other node available (in addition to the bridge node itself). Use a standard USB configuration if the goal is to communicate only with the single USB device. Using USB to CAN bridge mode without a fully functioning CAN bus (including terminating resistors and an additional node) may result in sporadic errors even when communicating with the bridge node.</li>
<li>A USB to CAN bridge board will not appear as a USB serial device, it will not show up when running <code>ls /dev/serial/by-id</code>, and it can not be configured in Klipper's printer.cfg file with a <code>serial:</code> parameter. The bridge board appears as a "USB CAN adapter" and it is configured in the printer.cfg as a <a href="#configuring-klipper">CAN node</a>.</li>
</ul>
<h2 id="tips-for-troubleshooting">Tips for troubleshooting<a class="headerlink" href="#tips-for-troubleshooting" title="Permanent link">&para;</a></h2>

38
it/CANBUS_Troubleshooting.html
View File

@@ -1284,6 +1284,13 @@
Use an appropriate txqueuelen setting
</a>
</li>
<li class="md-nav__item">
<a href="#use-canbus_querypy-only-to-identify-nodes-never-previously-seen" class="md-nav__link">
Use canbus_query.py only to identify nodes never previously seen
</a>
</li>
<li class="md-nav__item">
@@ -1370,8 +1377,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1444,6 +1451,13 @@
Use an appropriate txqueuelen setting
</a>
</li>
<li class="md-nav__item">
<a href="#use-canbus_querypy-only-to-identify-nodes-never-previously-seen" class="md-nav__link">
Use canbus_query.py only to identify nodes never previously seen
</a>
</li>
<li class="md-nav__item">
@@ -1500,12 +1514,16 @@ resistors</a> on the CAN bus. If the resistors are not properly installed then m
<p>Verify that all plugs and wire crimps on the CAN bus wiring are fully secured. Movement of the printer toolhead may jostle the CAN bus wiring causing a bad wire crimp or unsecured plug to result in intermittent communication errors.</p>
<h2 id="check-for-incrementing-bytes_invalid-counter">Check for incrementing bytes_invalid counter<a class="headerlink" href="#check-for-incrementing-bytes_invalid-counter" title="Permanent link">&para;</a></h2>
<p>The Klipper log file will report a <code>Stats</code> line once a second when the printer is active. These "Stats" lines will have a <code>bytes_invalid</code> counter for each micro-controller. This counter should not increment during normal printer operation (it is normal for the counter to be non-zero after a RESTART and it is not a concern if the counter increments once a month or so). If this counter increments on a CAN bus micro-controller during normal printing (it increments every few hours or more frequently) then it is an indication of a severe problem.</p>
<p>Incrementing <code>bytes_invalid</code> on a CAN bus connection is a symptom of reordered messages on the CAN bus. There are two known causes of reordered messages:</p>
<ol>
<li>Old versions of the popular candlight_firmware for USB CAN adapters had a bug that could cause reordered messages. If using a USB CAN adapter running this firmware then make sure to update to the latest firmware if incrementing <code>bytes_invalid</code> is observed.</li>
<li>Some Linux kernel builds for embedded devices have been known to reorder CAN bus messages. It may be necessary to use an alternative Linux kernel or to use alternative hardware that supports mainstream Linux kernels that do not exhibit this problem.</li>
</ol>
<p>Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print.</p>
<p>Incrementing <code>bytes_invalid</code> on a CAN bus connection is a symptom of reordered messages on the CAN bus. If seen, make sure to:</p>
<ul>
<li>Use a Linux kernel version 6.6.0 or later.</li>
<li>If using a USB-to-CANBUS adapter running candlelight firmware, use v2.0 or later of candleLight_fw.</li>
<li>If using Klipper's USB-to-CANBUS bridge mode, make sure the bridge node is flashed with Klipper v0.12.0 or later.</li>
</ul>
<p>Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print. An incrementing <code>bytes_invalid</code> is not caused by wiring or similar hardware issues and can only be fixed by identifying and updating the faulty software.</p>
<p>Older versions of the Linux kernel had a bug in the gs_usb canbus driver code that could cause reordered canbus packets. The issue is thought to be fixed in <a href="https://github.com/torvalds/linux/commit/24bc41b4558347672a3db61009c339b1f5692169">Linux commit 24bc41b4</a> which was released in v6.6.0. In some cases, older Linux versions may not show the problem (due to how hardware interrupts are configured), however if problems are seen the recommended solution is to upgrade to a newer kernel.</p>
<p>Older versions of candlelight firmware could reorder canbus packets, and the issue is thought to be fixed in <a href="https://github.com/candle-usb/candleLight_fw/commit/8b3a7b4565a3c9521b762b154c94c72c5acb2bcf">candlelight_fw commit 8b3a7b45</a>.</p>
<p>Older versions of Klipper's USB-to-CANBUS bridge code could incorrectly drop canbus messages. This is not as severe as reordering messages, but it should still be fixed. It is thought to be fixed with <a href="https://github.com/Klipper3d/klipper/pull/6175">Klipper PR #6175</a>.</p>
<h2 id="use-an-appropriate-txqueuelen-setting">Use an appropriate txqueuelen setting<a class="headerlink" href="#use-an-appropriate-txqueuelen-setting" title="Permanent link">&para;</a></h2>
<p>The Klipper code uses the Linux kernel to manage CAN bus traffic. By default, the kernel will only queue 10 CAN transmit packets. It is recommended to <a href="CANBUS.html#host-hardware">configure the can0 device</a> with a <code>txqueuelen 128</code> to increase that size.</p>
<p>If Klipper transmits a packet and Linux has filled all of its transmit queue space then Linux will drop that packet and messages like the following will appear in the Klipper log:</p>
@@ -1517,6 +1535,10 @@ resistors</a> on the CAN bus. If the resistors are not properly installed then m
<p>One may check the current queue size by running the Linux command <code>ip link show can0</code>. It should report a bunch of text including the snippet <code>qlen 128</code>. If one sees something like <code>qlen 10</code> then it indicates the CAN device has not been properly configured.</p>
<p>It is not recommended to use a <code>txqueuelen</code> significantly larger than 128. A CAN bus running at a frequency of 1000000 will typically take around 120us to transmit a CAN packet. Thus a queue of 128 packets is likely to take around 15-20ms to drain. A substantially larger queue could cause excessive spikes in message round-trip-time which could lead to unrecoverable errors. Said another way, Klipper's application retransmit system is more robust if it does not have to wait for Linux to drain an excessively large queue of possibly stale data. This is analogous to the problem of <a href="https://en.wikipedia.org/wiki/Bufferbloat">bufferbloat</a> on internet routers.</p>
<p>Under normal circumstances Klipper may utilize ~25 queue slots per MCU - typically only utilizing more slots during retransmits. (Specifically, the Klipper host may transmit up to 192 bytes to each Klipper MCU before receiving an acknowledgment from that MCU.) If a single CAN bus has 5 or more Klipper MCUs on it, then it might be necessary to increase the <code>txqueuelen</code> above the recommended value of 128. However, as above, care should be taken when selecting a new value to avoid excessive round-trip-time latency.</p>
<h2 id="use-canbus_querypy-only-to-identify-nodes-never-previously-seen">Use <code>canbus_query.py</code> only to identify nodes never previously seen<a class="headerlink" href="#use-canbus_querypy-only-to-identify-nodes-never-previously-seen" title="Permanent link">&para;</a></h2>
<p>It is only valid to use the <a href="CANBUS.html#finding-the-canbus_uuid-for-new-micro-controllers"><code>canbus_query.py</code> tool</a> to identify micro-controllers that have never been previously identified. Once all nodes on a bus are identified, record the resulting uuids in the printer.cfg, and avoid running the tool unnecessarily.</p>
<p>The tool is implemented using a low-level mechanism that can cause nodes to internally observe bus errors. These internal errors may result in communication interruptions and may result is some nodes disconnecting from the bus.</p>
<p>It is not valid to use the tool to "ping" if a node is connected. Do not run the tool during an active print.</p>
<h2 id="obtaining-candump-logs">Obtaining candump logs<a class="headerlink" href="#obtaining-candump-logs" title="Permanent link">&para;</a></h2>
<p>The CAN bus messages sent to and from the micro-controller are handled by the Linux kernel. It is possible to capture these messages from the kernel for debugging purposes. A log of these messages may be of use in diagnostics.</p>
<p>The Linux <a href="https://github.com/linux-can/can-utils">can-utils</a> tool provides the capture software. It is typically installed on a machine by running:</p>

4
it/CANBUS_protocol.html
View File

@@ -1370,8 +1370,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/CONTRIBUTING.html
View File

@@ -1370,8 +1370,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Code_Overview.html
View File

@@ -1385,8 +1385,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Command_Templates.html
View File

@@ -1421,8 +1421,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

10
it/Config_Changes.html
View File

@@ -1327,8 +1327,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1410,6 +1410,12 @@
<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">&para;</a></h2>
<p>20250428: The maximum <code>cycle_time</code> for pwm <code>[output_pin]</code>, <code>[pwm_cycle_time]</code>, <code>[pwm_tool]</code>, and similar config sections is now 3 seconds (reduced from 5 seconds). The <code>maximum_mcu_duration</code> in <code>[pwm_tool]</code> is now also 3 seconds.</p>
<p>20250418: The manual_stepper <code>STOP_ON_ENDSTOP</code> feature may now take less time to complete. Previously, the command would wait the entire time the move could possibly take even if the endstop triggered earlier. Now, the command finishes shortly after the endstop trigger.</p>
<p>20250417: SPI devices using "software SPI" are now rate limited. Previously, the <code>spi_speed</code> in the config was ignored and the transmission speed was only limited by the processing speed of the micro-controller. Now, speeds are limited by the <code>spi_speed</code> config parameter (actual hardware speeds are likely to be lower than the configured value due to software overhead).</p>
<p>20250411: Klipper v0.13.0 released.</p>
<p>20250308: The <code>AUTO</code> parameter of the <code>AXIS_TWIST_COMPENSATION_CALIBRATE</code> command has been removed.</p>
<p>20250131: Option <code>VARIABLE=&lt;name&gt;</code> in <code>SAVE_VARIABLE</code> requires lowercase value. For example, <code>extruder</code> instead of mixedcase <code>Extruder</code> or uppercase <code>EXTRUDER</code>. Using any uppercase letter will raise an error.</p>
<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=&lt;chip_name&gt;</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>

196
it/Config_Reference.html
View File

@@ -931,6 +931,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#icm20948" class="md-nav__link">
[icm20948]
</a>
</li>
<li class="md-nav__item">
@@ -1741,6 +1748,13 @@
[adc_scaled]
</a>
</li>
<li class="md-nav__item">
<a href="#ads1x1x" class="md-nav__link">
[ads1x1x]
</a>
</li>
<li class="md-nav__item">
@@ -2600,8 +2614,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -3053,6 +3067,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#icm20948" class="md-nav__link">
[icm20948]
</a>
</li>
<li class="md-nav__item">
@@ -3863,6 +3884,13 @@
[adc_scaled]
</a>
</li>
<li class="md-nav__item">
<a href="#ads1x1x" class="md-nav__link">
[ads1x1x]
</a>
</li>
<li class="md-nav__item">
@@ -5331,6 +5359,22 @@ cs_pin:
# measurements.
</code></pre></div>
<h3 id="icm20948">[icm20948]<a class="headerlink" href="#icm20948" title="Permanent link">&para;</a></h3>
<p>Support for icm20948 accelerometers.</p>
<div class="highlight"><pre><span></span><code>[icm20948]
#i2c_address:
# Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
#i2c_mcu:
#i2c_bus:
#i2c_software_scl_pin:
#i2c_software_sda_pin:
#i2c_speed: 400000
# See the &quot;common I2C settings&quot; section for a description of the
# above parameters. The default &quot;i2c_speed&quot; is 400000.
#axes_map: x, y, z
# See the &quot;adxl345&quot; section for information on this parameter.
</code></pre></div>
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">&para;</a></h3>
<p>Support for LIS2DW accelerometers.</p>
<div class="highlight"><pre><span></span><code>[lis2dw]
@@ -5664,6 +5708,9 @@ z_offset:
sensor_type: ldc1612
# The sensor chip used to perform eddy current measurements. This
# parameter must be provided and must be set to ldc1612.
#frequency:
# The external crystal frequency (in Hz) of the LDC1612 chip.
# The default is 12000000.
#intb_pin:
# MCU gpio pin connected to the ldc1612 sensor&#39;s INTB pin (if
# available). The default is to not use the INTB pin.
@@ -6613,22 +6660,27 @@ pin:
<p>Esegui gcode quando un pulsante viene premuto o rilasciato (o quando un pin cambia stato). Puoi controllare lo stato del pulsante usando <code>QUERY_BUTTON button=my_gcode_button</code>.</p>
<div class="highlight"><pre><span></span><code>[gcode_button my_gcode_button]
pin:
# Il pin su cui è collegato il pulsante. Questo parametro deve essere fornito.
# The pin on which the button is connected. This parameter must be
# provided.
#analog_range:
# Due resistenze separate da virgole (in Ohm) che specificano l&#39;intervallo
# di resistenza minimo e massimo per il pulsante. Se viene fornito
# analog_range, il pin deve essere un pin con capacità analogica.
# L&#39;impostazione predefinita è utilizzare digital gpio per il pulsante.
# Two comma separated resistances (in Ohms) specifying the minimum
# and maximum resistance range for the button. If analog_range is
# provided then the pin must be an analog capable pin. The default
# is to use digital gpio for the button.
#analog_pullup_resistor:
# La resistenza di pullup (in Ohm) quando è specificato analog_range.
# Il valore predefinito è 4700 ohm.
# The pullup resistance (in Ohms) when analog_range is specified.
# The default is 4700 ohms.
#press_gcode:
# Un elenco di comandi G-Code da eseguire quando si preme il pulsante.
# I modelli G-Code sono supportati. Questo parametro deve essere fornito.
# A list of G-Code commands to execute when the button is pressed.
# G-Code templates are supported. This parameter must be provided.
#release_gcode:
# Un elenco di comandi G-Code da eseguire quando il pulsante viene
# rilasciato. I modelli G-Code sono supportati. L&#39;impostazione predefinita
# è di non eseguire alcun comando al rilascio di un pulsante.
# A list of G-Code commands to execute when the button is released.
# G-Code templates are supported. The default is to not run any
# commands on a button release.
#debounce_delay:
# A period of time in seconds to debounce events prior to running the
# button gcode. If the button is pressed and released during this
# delay, the entire button press is ignored. Default is 0.
</code></pre></div>
<h3 id="output_pin">[output_pin]<a class="headerlink" href="#output_pin" title="Permanent link">&para;</a></h3>
@@ -6762,8 +6814,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#coolstep_threshold:
# The velocity (in mm/s) to set the TMC driver internal &quot;CoolStep&quot;
# threshold to. If set, the coolstep feature will be enabled when
@@ -6812,6 +6865,7 @@ run_current:
#driver_PWM_FREQ: 1
#driver_PWM_GRAD: 4
#driver_PWM_AMPL: 128
#driver_FREEWHEEL: 0
#driver_SGT: 0
#driver_SEMIN: 0
#driver_SEUP: 0
@@ -6869,8 +6923,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#driver_MULTISTEP_FILT: True
#driver_IHOLDDELAY: 8
#driver_TPOWERDOWN: 20
@@ -6885,6 +6940,7 @@ run_current:
#driver_PWM_FREQ: 1
#driver_PWM_GRAD: 14
#driver_PWM_OFS: 36
#driver_FREEWHEEL: 0
# Set the given register during the configuration of the TMC2208
# chip. This may be used to set custom motor parameters. The
# defaults for each parameter are next to the parameter name in the
@@ -6928,6 +6984,7 @@ run_current:
#driver_PWM_FREQ: 1
#driver_PWM_GRAD: 14
#driver_PWM_OFS: 36
#driver_FREEWHEEL: 0
#driver_SGTHRS: 0
#driver_SEMIN: 0
#driver_SEUP: 0
@@ -7055,8 +7112,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#coolstep_threshold:
# The velocity (in mm/s) to set the TMC driver internal &quot;CoolStep&quot;
# threshold to. If set, the coolstep feature will be enabled when
@@ -7183,8 +7241,9 @@ run_current:
#stealthchop_threshold: 0
# The velocity (in mm/s) to set the &quot;stealthChop&quot; threshold to. When
# set, &quot;stealthChop&quot; mode will be enabled if the stepper motor
# velocity is below this value. The default is 0, which disables
# &quot;stealthChop&quot; mode.
# velocity is below this value. Note that the &quot;sensorless homing&quot;
# code may temporarily override this setting during homing
# operations. The default is 0, which disables &quot;stealthChop&quot; mode.
#coolstep_threshold:
# The velocity (in mm/s) to set the TMC driver internal &quot;CoolStep&quot;
# threshold to. If set, the coolstep feature will be enabled when
@@ -7785,34 +7844,37 @@ text:
<p>Per ulteriori informazioni, vedere <a href="G-Codes.html#filament_switch_sensor">command reference</a>.</p>
<div class="highlight"><pre><span></span><code>[filament_switch_sensor my_sensor]
#pause_on_runout: True
# Se impostato su True, verrà eseguita una PAUSA immediatamente
# dopo il rilevamento di un&#39;eccentricità. Si noti che se pause_on_runout
# è False e runout_gcode viene omesso, il rilevamento dell&#39;eccentricità
# è disabilitato. L&#39;impostazione predefinita è Vero.
# When set to True, a PAUSE will execute immediately after a runout
# is detected. Note that if pause_on_runout is False and the
# runout_gcode is omitted then runout detection is disabled. Default
# is True.
#runout_gcode:
# Un elenco di comandi G-Code da eseguire dopo il rilevamento di
# un&#39;esaurimento del filamento. Vedi docs/Command_Templates.md
# per il formato G-Code. Se pause_on_runout è impostato su True,
# questo codice G verrà eseguito al termine della PAUSA.
# L&#39;impostazione predefinita è di non eseguire alcun comando G-Code.
# A list of G-Code commands to execute after a filament runout is
# detected. See docs/Command_Templates.md for G-Code format. If
# pause_on_runout is set to True this G-Code will run after the
# PAUSE is complete. The default is not to run any G-Code commands.
#insert_gcode:
# Un elenco di comandi G-Code da eseguire dopo il rilevamento
# dell&#39;inserimento di filamento. Vedi docs/Command_Templates.md
# per il formato G-Code. L&#39;impostazione predefinita non prevede
# l&#39;esecuzione di alcun comando G-Code, che disabilita il rilevamento
# dell&#39;inserimento.
# A list of G-Code commands to execute after a filament insert is
# detected. See docs/Command_Templates.md for G-Code format. The
# default is not to run any G-Code commands, which disables insert
# detection.
#event_delay: 3.0
# Il tempo minimo in secondi per ritardare tra gli eventi. Gli eventi
# attivati durante questo periodo di tempo verranno ignorati
# silenziosamente. L&#39;impostazione predefinita è 3 secondi.
# The minimum amount of time in seconds to delay between events.
# Events triggered during this time period will be silently
# ignored. The default is 3 seconds.
#pause_delay: 0.5
# Il tempo di ritardo, in secondi, tra l&#39;invio del comando pause e
# l&#39;esecuzione di runout_gcode. Potrebbe essere utile aumentare
# questo ritardo se OctoPrint mostra uno strano comportamento
# di pausa. Il valore predefinito è 0,5 secondi.
# The amount of time to delay, in seconds, between the pause command
# dispatch and execution of the runout_gcode. It may be useful to
# increase this delay if OctoPrint exhibits strange pause behavior.
# Default is 0.5 seconds.
#debounce_delay:
# A period of time in seconds to debounce events prior to running the
# switch gcode. The switch must he held in a single state for at least
# this long to activate. If the switch is toggled on/off during this delay,
# the event is ignored. Default is 0.
#switch_pin:
# Il pin su cui è collegato l&#39;interruttore.
# Questo parametro deve essere fornito.
# The pin on which the switch is connected. This parameter must be
# provided.
</code></pre></div>
<h3 id="filament_motion_sensor">[filament_motion_sensor]<a class="headerlink" href="#filament_motion_sensor" title="Permanent link">&para;</a></h3>
@@ -7907,6 +7969,16 @@ L&#39;impostazione predefinita è disabilitare.
<div class="highlight"><pre><span></span><code>[load_cell]
sensor_type:
# This must be one of the supported sensor types, see below.
#counts_per_gram:
# The floating point number of sensor counts that indicates 1 gram of force.
# This value is calculated by the LOAD_CELL_CALIBRATE command.
#reference_tare_counts:
# The integer tare value, in raw sensor counts, taken when LOAD_CELL_CALIBRATE
# is run. This is the default tare value when klipper starts up.
#sensor_orientation:
# Change the sensor&#39;s orientation. Can be either &#39;normal&#39; or &#39;inverted&#39;.
# The default is &#39;normal&#39;. Use &#39;inverted&#39; if the sensor reports a
# decreasing force value when placed under load.
</code></pre></div>
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">&para;</a></h4>
@@ -8056,6 +8128,38 @@ vssa_pin:
# noise. The default is 2 seconds.
</code></pre></div>
<h3 id="ads1x1x">[ads1x1x]<a class="headerlink" href="#ads1x1x" title="Permanent link">&para;</a></h3>
<p>ADS1013, ADS1014, ADS1015, ADS1113, ADS1114 and ADS1115 are I2C based Analog to Digital Converters that can be used for temperature sensors. They provide 4 analog input pins either as single line or as differential input.</p>
<p>Note: Use caution if using this sensor to control heaters. The heater min_temp and max_temp are only verified in the host and only if the host is running and operating normally. (ADC inputs directly connected to the micro-controller verify min_temp and max_temp within the micro-controller and do not require a working connection to the host.)</p>
<div class="highlight"><pre><span></span><code>[ads1x1x my_ads1x1x]
chip: ADS1115
#pga: 4.096V
# Default value is 4.096V. The maximum voltage range used for the input. This
# scales all values read from the ADC. Options are: 6.144V, 4.096V, 2.048V,
# 1.024V, 0.512V, 0.256V
#adc_voltage: 3.3
# The suppy voltage for the device. This allows additional software scaling
# for all values read from the ADC.
i2c_mcu: host
i2c_bus: i2c.1
#address_pin: GND
# Default value is GND. There can be up to four addressed devices depending
# upon wiring of the device. Check the datasheet for details. The i2c_address
# can be specified directly instead of using the address_pin.
</code></pre></div>
<p>The chip provides pins that can be used on other sensors.</p>
<div class="highlight"><pre><span></span><code>sensor_type: ...
# Can be any thermistor or adc_temperature.
sensor_pin: my_ads1x1x:AIN0
# A combination of the name of the ads1x1x chip and the pin. Possible
# pin values are AIN0, AIN1, AIN2 and AIN3 for single ended lines and
# DIFF01, DIFF03, DIFF13 and DIFF23 for differential between their
# correspoding lines. For example
# DIFF03 measures the differential between line 0 and 3. Only specific
# combinations for the differentials are allowed.
</code></pre></div>
<h3 id="replicape">[replicape]<a class="headerlink" href="#replicape" title="Permanent link">&para;</a></h3>
<p>Supporto per Replicape: vedere la <a href="Beaglebone.html">guida beaglebone</a> e il file <a href="https://github.com/Klipper3d/klipper/blob/master/config/generic-replicape.cfg">generic-replicape.cfg</a> per un esempio.</p>
<div class="highlight"><pre><span></span><code># La sezione di configurazione &quot;replicape&quot; aggiunge i pin di abilitazione
@@ -8125,7 +8229,7 @@ host_mcu:
<p>Supporto multimateriale Palette 2: fornisce un'integrazione più stretta supportando i dispositivi Palette 2 in modalità connessa.</p>
<p>Questo modulo richiede anche <code>[virtual_sdcard]</code> e <code>[pause_resume]</code> per la piena funzionalità.</p>
<p>Se si utilizza questo modulo, non utilizzare il plug-in Palette 2 per Octoprint poiché entreranno in conflitto e 1 non si inizializzerà correttamente, probabilmente interrompendo la stampa.</p>
<p>Se utilizzi Octoprint e esegui lo streaming di gcode sulla porta seriale invece di stampare da virtual_sd, rimuovere <strong>M1</strong> e <strong>M0</strong> da <em>Pausa dei comandi</em> in <em>Impostazioni &gt; Connessione seriale &gt; Firmware e protocollo</em> eviterà la necessità per avviare la stampa sulla tavolozza 2 e riattivare la pausa in Octoprint per avviare la stampa.</p>
<p>If you use Octoprint and stream gcode over the serial port instead of printing from virtual_sd, then remove <strong>M1</strong> and <strong>M0</strong> from <em>Pausing commands</em> in <em>Settings &gt; Serial Connection &gt; Firmware &amp; protocol</em> will prevent the need to start print on the Palette 2 and unpausing in Octoprint for your print to begin.</p>
<div class="highlight"><pre><span></span><code>[palette2]
serial:
# The serial port to connect to the Palette 2.

4
it/Config_checks.html
View File

@@ -1385,8 +1385,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

19
it/Contact.html
View File

@@ -451,8 +451,8 @@
</li>
<li class="md-nav__item">
<a href="#klipper-github" class="md-nav__link">
Klipper github
<a href="#professional-services" class="md-nav__link">
Professional Services
</a>
</li>
@@ -1376,8 +1376,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1481,8 +1481,8 @@
</li>
<li class="md-nav__item">
<a href="#klipper-github" class="md-nav__link">
Klipper github
<a href="#professional-services" class="md-nav__link">
Professional Services
</a>
</li>
@@ -1558,9 +1558,10 @@
<h2 id="sto-apportando-modifiche-che-vorrei-includere-in-klipper">Sto apportando modifiche che vorrei includere in Klipper<a class="headerlink" href="#sto-apportando-modifiche-che-vorrei-includere-in-klipper" title="Permanent link">&para;</a></h2>
<p>Klipper è un software open-source e apprezziamo i nuovi contributi.</p>
<p>I nuovi contributi (sia per il codice che per la documentazione) vengono inviati tramite Github Pull Requests. Vedere [<a href="CONTRIBUTING.html">CONTRIBUTING document</a> per informazioni importanti.</p>
<p>Ci sono diversi <a href="Overview.html#developer-documentation">documenti per sviluppatori</a>. Se hai domande sul codice, puoi anche chiedere nel <a href="#community-forum">Klipper Community Forum</a> o nella <a href="#discord-chat">Klipper Community Discord</a>.</p>
<h2 id="klipper-github">Klipper github<a class="headerlink" href="#klipper-github" title="Permanent link">&para;</a></h2>
<p>Klipper github può essere utilizzato dai contributori per condividere lo stato del loro lavoro per migliorare Klipper. Ci si aspetta che la persona che apre un ticket github stia lavorando attivamente all'attività specificata e sarà quella che eseguirà tutto il lavoro necessario per realizzarla. Il github di Klipper non viene utilizzato per richieste, né per segnalare bug, né per porre domande. Usa invece il <a href="#community-forum">Klipper Community Forum</a> o la <a href="#discord-chat">Klipper Community Discord</a>.</p>
<p>There are several <a href="Overview.html#developer-documentation">documents for developers</a>. If you have questions on the code then you can also ask in the <a href="#discourse-forum">Klipper Discourse Forum</a> or on the <a href="#discord-chat">Klipper Discord Chat</a>.</p>
<h2 id="professional-services">Professional Services<a class="headerlink" href="#professional-services" title="Permanent link">&para;</a></h2>
<p><img alt="" src="img/klipper-logo-small.png" /></p>
<p>Custom software development, software support, and solutions: <a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a></p>
</article>

4
it/Debugging.html
View File

@@ -1384,8 +1384,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Delta_Calibrate.html
View File

@@ -1365,8 +1365,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

8
it/Eddy_Probe.html
View File

@@ -1329,8 +1329,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1487,13 +1487,13 @@
<a href="Sponsors.html" class="md-footer__link md-footer__link--next" aria-label="Prossimo: Sponsors" rel="next">
<a href="Load_Cell.html" class="md-footer__link md-footer__link--next" aria-label="Prossimo: Load Cells" rel="next">
<div class="md-footer__title">
<div class="md-ellipsis">
<span class="md-footer__direction">
Prossimo
</span>
Sponsors
Load Cells
</div>
</div>
<div class="md-footer__button md-icon">

4
it/Endstop_Phase.html
View File

@@ -1344,8 +1344,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Example_Configs.html
View File

@@ -1329,8 +1329,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Exclude_Object.html
View File

@@ -1356,8 +1356,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/FAQ.html
View File

@@ -1488,8 +1488,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

28
it/Features.html
View File

@@ -1334,8 +1334,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1443,18 +1443,18 @@
<li>Supporto G-code standard. Sono supportati i comandi G-code comuni prodotti dai tipici "slicer" (SuperSlicer, Cura, PrusaSlicer, ecc.).</li>
<li>Supporto per più estrusori. Sono supportati anche estrusori con riscaldatori condivisi ed estrusori su carrelli indipendenti (IDEX).</li>
<li>Supporto per stampanti cartesiane, delta, corexy, corexz, hybrid-corexy, hybrid-corexz, deltesian, rotary delta, polar e cable winch.</li>
<li>Supporto per il livellamento automatico del letto. Klipper può essere configurato per il rilevamento di base dell'inclinazione del piatto o per il livellamento del piatto a mesh completa. Se il piatto utilizza più stepper Z, Klipper può anche livellare manipolando in modo indipendente gli stepper Z. Sono supportate la maggior parte delle sonde di altezza Z, comprese le sonde BL-Touch e le sonde servoattivate.</li>
<li>Automatic bed leveling support. Klipper can be configured for basic bed tilt detection or full mesh bed leveling. The bed mesh can be customized to the print size (adaptive bed mesh). If the bed uses multiple Z steppers then Klipper can also level by independently manipulating the Z steppers. Most Z height probes are supported, including BL-Touch probes and servo activated probes. Probes may be calibrated for axis twist compensation. If using an "eddy current probe" then one can utilize fast bed mesh scanning,</li>
<li>Supporto per la calibrazione delta automatica. Lo strumento di calibrazione può eseguire la calibrazione dell'altezza di base e una calibrazione avanzata delle dimensioni X e Y. La calibrazione può essere eseguita con una sonda di altezza Z o tramite tastatura manuale.</li>
<li>Supporto "escludi oggetto" in fase di esecuzione. Se configurato, questo modulo può facilitare l'annullamento di un solo oggetto in una stampa multiparte.</li>
<li>Supporto per sensori di temperatura comuni (ad es. termistori comuni, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20 e LM75). È inoltre possibile configurare termistori personalizzati e sensori di temperatura analogici personalizzati. È possibile monitorare il sensore di temperatura del microcontrollore interno e il sensore di temperatura interna di un Raspberry Pi.</li>
<li>Support for common temperature sensors (eg, common thermistors, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20, AHT10, SHT3x, and LM75). Custom thermistors and custom analog temperature sensors can also be configured. One can monitor the internal micro-controller temperature sensor and the internal temperature sensor of a Raspberry Pi.</li>
<li>Protezione del riscaldatore termico di base abilitata di default.</li>
<li>Supporto per ventole standard, ventole per ugelli e ventole a temperatura controllata. Non è necessario mantenere le ventole in funzione quando la stampante è inattiva. La velocità della ventola può essere monitorata su ventole dotate di contagiri.</li>
<li>Support for standard fans, nozzle fans, and temperature controlled fans. No need to keep fans running when the printer is idle. Fan speed can be monitored on fans that have a tachometer. One can assign a "math formula" to a fan for automatic fan speed updating.</li>
<li>Supporto per la configurazione in fase di esecuzione dei driver per motori passo-passo TMC2130, TMC2208/TMC2224, TMC2209, TMC2660 e TMC5160. È inoltre disponibile il supporto per il controllo corrente dei tradizionali driver passo-passo tramite i pin AD5206, DAC084S085, MCP4451, MCP4728, MCP4018 e PWM.</li>
<li>Supporto per comuni display LCD collegati direttamente alla stampante. È disponibile anche un menu predefinito. Il contenuto del display e del menu può essere completamente personalizzato tramite il file di configurazione.</li>
<li>Accelerazione costante e supporto "look-ahead". Tutti i movimenti della stampante accelereranno gradualmente dall'arresto alla velocità di crociera, quindi decelereranno fino all'arresto. Il flusso in entrata dei comandi di movimento del G-code viene messo in coda e analizzato: l'accelerazione tra i movimenti in una direzione simile sarà ottimizzata per ridurre gli arresti di stampa e migliorare il tempo di stampa complessivo.</li>
<li>Klipper implementa un algoritmo "stepper phase endstop" che può migliorare la precisione dei tipici interruttori endstop. Se regolato correttamente, può migliorare l'adesione del primo strato di stampa.</li>
<li>Supporto per sensori di presenza del filamento, sensori di movimento del filamento e sensori di larghezza del filamento.</li>
<li>Supporto per misurare e registrare l'accelerazione utilizzando gli accelerometri adxl345, mpu9250 e mpu6050.</li>
<li>Support for measuring and recording acceleration using adxl345, mpu9250, mpu6050, lis2dw12, lis3dh, and icm20948 accelerometers.</li>
<li>Supporto per limitare la velocità massima di brevi spostamenti a "zigzag" per ridurre le vibrazioni e il rumore della stampante. Per ulteriori informazioni, vedere il documento <a href="Kinematics.html">cinematica</a>.</li>
<li>Sono disponibili file di configurazione di esempio per molte stampanti comuni. Controllare la <a href="https://github.com/Klipper3d/klipper/blob/master/config/">directory di configurazione</a> per un elenco.</li>
</ul>
@@ -1526,11 +1526,6 @@
<td>1622K</td>
</tr>
<tr>
<td>RP2040</td>
<td>2400K</td>
<td>1636K</td>
</tr>
<tr>
<td>SAM4E8E</td>
<td>2500K</td>
<td>1674K</td>
@@ -1556,6 +1551,11 @@
<td>2634K</td>
</tr>
<tr>
<td>RP2040</td>
<td>4000K</td>
<td>2571K</td>
</tr>
<tr>
<td>RP2350</td>
<td>4167K</td>
<td>2663K</td>
@@ -1566,9 +1566,9 @@
<td>4737K</td>
</tr>
<tr>
<td>STM32H743</td>
<td>9091K</td>
<td>6061K</td>
<td>STM32H723</td>
<td>7429K</td>
<td>8619K</td>
</tr>
</tbody>
</table>

524
it/G-Codes.html
View File

@@ -1620,6 +1620,68 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
[load_cell]
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_diagnostic" class="md-nav__link">
LOAD_CELL_DIAGNOSTIC
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_calibrate" class="md-nav__link">
LOAD_CELL_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_tare" class="md-nav__link">
LOAD_CELL_TARE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_read-load_cellname" class="md-nav__link">
LOAD_CELL_READ load_cell="name"
</a>
</li>
<li class="md-nav__item">
@@ -1694,33 +1756,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -1789,26 +1824,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -1850,6 +1865,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -2281,6 +2316,54 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#abort" class="md-nav__link">
ABORT
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
<li class="md-nav__item">
@@ -2429,54 +2512,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#abort" class="md-nav__link">
ABORT
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
</ul>
@@ -3006,8 +3041,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -3881,6 +3916,68 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
[load_cell]
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_diagnostic" class="md-nav__link">
LOAD_CELL_DIAGNOSTIC
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_calibrate" class="md-nav__link">
LOAD_CELL_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_tare" class="md-nav__link">
LOAD_CELL_TARE
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell_read-load_cellname" class="md-nav__link">
LOAD_CELL_READ load_cell="name"
</a>
</li>
<li class="md-nav__item">
@@ -3955,33 +4052,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#led" class="md-nav__link">
[led]
</a>
<nav class="md-nav" aria-label="[led]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#set_led" class="md-nav__link">
SET_LED
</a>
</li>
<li class="md-nav__item">
<a href="#set_led_template" class="md-nav__link">
SET_LED_TEMPLATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4050,26 +4120,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4111,6 +4161,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#pid_calibrate" class="md-nav__link">
[pid_calibrate]
</a>
<nav class="md-nav" aria-label="[pid_calibrate]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#pid_calibrate_1" class="md-nav__link">
PID_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4542,6 +4612,54 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#abort" class="md-nav__link">
ABORT
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
<li class="md-nav__item">
@@ -4690,54 +4808,6 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe" class="md-nav__link">
[temperature_probe]
</a>
<nav class="md-nav" aria-label="[temperature_probe]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#temperature_probe_calibrate" class="md-nav__link">
TEMPERATURE_PROBE_CALIBRATE
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_next" class="md-nav__link">
TEMPERATURE_PROBE_NEXT
</a>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_complete" class="md-nav__link">
TEMPERATURE_PROBE_COMPLETE:
</a>
</li>
<li class="md-nav__item">
<a href="#abort" class="md-nav__link">
ABORT
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#temperature_probe_enable" class="md-nav__link">
TEMPERATURE_PROBE_ENABLE
</a>
</li>
</ul>
@@ -4831,11 +4901,10 @@
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
section</a> is enabled.</p>
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">&para;</a></h4>
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=&lt;X|Y&gt;] [AUTO=&lt;True|False&gt;] [SAMPLE_COUNT=&lt;value&gt;]</code></p>
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=&lt;X|Y&gt;] [SAMPLE_COUNT=&lt;value&gt;]</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">&para;</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>
@@ -4965,7 +5034,10 @@ section</a> is enabled.</p>
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">&para;</a></h4>
<p><code>FORCE_MOVE STEPPER=&lt;nome_config&gt; DISTANCE=&lt;value&gt; VELOCITY=&lt;value&gt; [ACCEL=&lt;value&gt;]</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">&para;</a></h4>
<p><code>SET_KINEMATIC_POSITION [X=&lt;value&gt;] [Y=&lt;value&gt;] [Z=&lt;value&gt;] [CLEAR=&lt;[X][Y][Z]&gt;]</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>
<p><code>SET_KINEMATIC_POSITION [X=&lt;value&gt;] [Y=&lt;value&gt;] [Z=&lt;value&gt;] [SET_HOMED=&lt;[X][Y][Z]&gt;] [CLEAR_HOMED=&lt;[X][Y][Z]&gt;]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position and set/clear homed status. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. Setting an incorrect or invalid position may lead to internal software errors.</p>
<p>The <code>X</code>, <code>Y</code>, and <code>Z</code> parameters are used to alter the low-level kinematic position tracking. If any of these parameters are not set then the position is not changed - for example <code>SET_KINEMATIC_POSITION Z=10</code> would set all axes as homed, set the internal Z position to 10, and leave the X and Y positions unchanged. Changing the internal position tracking is not dependent on the internal homing state - one may alter the position for both homed and not homed axes, and similarly one may set or clear the homing state of an axis without altering its internal position.</p>
<p>The <code>SET_HOMED</code> parameter defaults to <code>XYZ</code> which instructs the kinematics to consider all axes as homed. A bare <code>SET_KINEMATIC_POSITION</code> command will result in all axes being considered homed (and not change its current position). If it is not desired to change the state of homed axes then assign <code>SET_HOMED</code> to an empty string - for example: <code>SET_KINEMATIC_POSITION SET_HOMED= X=10</code>. It is also possible to request an individual axis be considered homed (eg, <code>SET_HOMED=X</code>), but note that non-cartesian style kinematics (such as delta kinematics) may not support setting an individual axis as homed.</p>
<p>The <code>CLEAR_HOMED</code> parameter instructs the kinematics to consider the given axes as not homed. For example, <code>CLEAR_HOMED=XYZ</code> would request all axes to be considered not homed (and thus require homing prior to movement on those axes). The default is <code>SET_HOMED=XYZ</code> even if <code>CLEAR_HOMED</code> is present, so the command <code>SET_KINEMATIC_POSITION CLEAR_HOMED=Z</code> will set X and Y as homed and clear the homing state for Z. Use <code>SET_KINEMATIC_POSITION SET_HOMED= CLEAR_HOMED=Z</code> if the goal is to clear only the Z homing state. If an axis is specified in neither <code>SET_HOMED</code> nor <code>CLEAR_HOMED</code> then its homing state is not changed and if it is specified in both then <code>CLEAR_HOMED</code> has precedence. It is possible to request clearing of an individual axis, but on non-cartesian style kinematics (such as delta kinematics) doing so may result in clearing the homing state of additional axes. Note the <code>CLEAR</code> parameter is currently an alias for the <code>CLEAR_HOMED</code> parameter, but this alias will be removed in the future.</p>
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">&para;</a></h3>
<p>Il modulo gcode viene caricato automaticamente.</p>
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">&para;</a></h4>
@@ -5028,6 +5100,28 @@ section</a> is enabled.</p>
<p>Il comando seguente è abilitato se è stata abilitata una <a href="Config_Reference.html#input_shaper">sezione di configurazione di input_shaper</a> (consultare anche la <a href="Resonance_Compensation.html">guida alla compensazione della risonanza</a>).</p>
<h4 id="set_input_shaper">SET_INPUT_SHAPER<a class="headerlink" href="#set_input_shaper" title="Permanent link">&para;</a></h4>
<p><code>SET_INPUT_SHAPER [SHAPER_FREQ_X=&lt;shaper_freq_x&gt;] [SHAPER_FREQ_Y=&lt;shaper_freq_y&gt;] [DAMPING_RATIO_X=&lt;damping_ratio_x&gt;] [DAMPING_RATIO_Y=&lt;damping_ratio_y&gt;] [SHAPER_TYPE=&lt;shaper&gt;] [SHAPER_TYPE_X=&lt;shaper_type_x&gt;] [SHAPER_TYPE=&lt;shaper_TYPE_X=&lt;shaper_type_x&gt;] [SHAPER_TYPE=&lt;shaper_type_y=&lt;shaper_type_x&gt; ]</code>: Modifica i parametri dell'input shaper. Si noti che il parametro SHAPER_TYPE reimposta l'input shaper per entrambi gli assi X e Y anche se sono stati configurati tipi di shaper diversi nella sezione [input_shaper]. SHAPER_TYPE non può essere utilizzato insieme a uno dei parametri SHAPER_TYPE_X e SHAPER_TYPE_Y. Vedere <a href="Config_Reference.html#input_shaper">config reference</a> per maggiori dettagli su ciascuno di questi parametri.</p>
<h3 id="led">[led]<a class="headerlink" href="#led" title="Permanent link">&para;</a></h3>
<p>Il comando seguente è disponibile quando una qualsiasi delle <a href="Config_Reference.html#leds">sezioni di configurazione led</a> è abilitata.</p>
<h4 id="set_led">SET_LED<a class="headerlink" href="#set_led" title="Permanent link">&para;</a></h4>
<p><code>SET_LED LED=&lt;nome_config&gt; ROSSO=&lt;valore&gt; VERDE=&lt;valore&gt; BLU=&lt;valore&gt; BIANCO=&lt;valore&gt; [INDEX=&lt;indice&gt;] [TRANSMIT=0] [SYNC=1]</code>: Imposta il LED in output. Ogni colore <code>&lt;valore&gt;</code> deve essere compreso tra 0,0 e 1,0. L'opzione BIANCO è valida solo su LED RGBW. Se il LED supporta più chip in una catena daisy-chain, è possibile specificare INDEX per modificare il colore del solo chip specificato (1 per il primo chip, 2 per il secondo, ecc.). Se INDEX non viene fornito, tutti i LED nella catena verranno impostati sul colore fornito. Se viene specificato TRANSMIT=0, il cambio colore verrà effettuato solo sul successivo comando SET_LED che non specifica TRANSMIT=0; questo può essere utile in combinazione con il parametro INDEX per raggruppare più aggiornamenti in una catena. Per impostazione predefinita, il comando SET_LED sincronizzerà le modifiche con altri comandi gcode in corso. Ciò può comportare un comportamento indesiderato se i LED vengono impostati mentre la stampante non sta stampando in quanto reimposta il timeout di inattività. Se non è necessaria una tempistica attenta, è possibile specificare il parametro SYNC=0 opzionale per applicare le modifiche senza ripristinare il timeout di inattività.</p>
<h4 id="set_led_template">SET_LED_TEMPLATE<a class="headerlink" href="#set_led_template" title="Permanent link">&para;</a></h4>
<p><code>SET_LED_TEMPLATE LED=&lt;nome_led&gt; TEMPLATE=&lt;nome_modello&gt; [&lt;param_x&gt;=&lt;letterale&gt;] [INDEX=&lt;indice&gt;]</code>: Assegna un <a href="Config_Reference.html#modello_visualizzazione">modello_visualizzazione</a> a un dato <a href="Riferimento_Configurazione .md#led">LED</a>. Ad esempio, se si definisce una sezione di configurazione <code>[display_template my_led_template]</code> allora si potrebbe assegnare <code>TEMPLATE=my_led_template</code> qui. Il display_template dovrebbe produrre una stringa separata da virgole contenente quattro numeri in virgola mobile corrispondenti alle impostazioni dei colori rosso, verde, blu e bianco. Il modello verrà continuamente valutato e il LED verrà impostato automaticamente sui colori risultanti. È possibile impostare i parametri display_template da utilizzare durante la valutazione del modello (i parametri verranno analizzati come valori letterali Python). Se INDEX non è specificato, tutti i chip nella catena dei LED verranno impostati sul modello, altrimenti verrà aggiornato solo il chip con l'indice specificato. Se TEMPLATE è una stringa vuota, questo comando cancellerà qualsiasi modello precedente assegnato al LED (è quindi possibile utilizzare i comandi <code>SET_LED</code> per gestire le impostazioni del colore del LED).</p>
<h3 id="load_cell">[load_cell]<a class="headerlink" href="#load_cell" title="Permanent link">&para;</a></h3>
<p>The following commands are enabled if a <a href="Config_Reference.html#load_cell">load_cell config section</a> has been enabled.</p>
<h3 id="load_cell_diagnostic">LOAD_CELL_DIAGNOSTIC<a class="headerlink" href="#load_cell_diagnostic" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_DIAGNOSTIC [LOAD_CELL=&lt;config_name&gt;]</code>: This command collects 10 seconds of load cell data and reports statistics that can help you verify proper operation of the load cell. This command can be run on both calibrated and uncalibrated load cells.</p>
<h3 id="load_cell_calibrate">LOAD_CELL_CALIBRATE<a class="headerlink" href="#load_cell_calibrate" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_CALIBRATE [LOAD_CELL=&lt;config_name&gt;]</code>: Start the guided calibration utility. Calibration is a 3 step process:</p>
<ol>
<li>First you remove all load from the load cell and run the <code>TARE</code> command</li>
<li>Next you apply a known load to the load cell and run the <code>CALIBRATE GRAMS=nnn</code> command</li>
<li>Finally use the <code>ACCEPT</code> command to save the results</li>
</ol>
<p>You can cancel the calibration process at any time with <code>ABORT</code>.</p>
<h3 id="load_cell_tare">LOAD_CELL_TARE<a class="headerlink" href="#load_cell_tare" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_TARE [LOAD_CELL=&lt;config_name&gt;]</code>: This works just like the tare button on digital scale. It sets the current raw reading of the load cell to be the zero point reference value. The response is the percentage of the sensors range that was read and the raw value in counts.</p>
<h3 id="load_cell_read-load_cellname">LOAD_CELL_READ load_cell="name"<a class="headerlink" href="#load_cell_read-load_cellname" title="Permanent link">&para;</a></h3>
<p><code>LOAD_CELL_READ [LOAD_CELL=&lt;config_name&gt;]</code>: This command takes a reading from the load cell. The response is the percentage of the sensors range that was read and the raw value in counts. If the load cell is calibrated a force in grams is also reported.</p>
<h3 id="manual_probe">[manual_probe]<a class="headerlink" href="#manual_probe" title="Permanent link">&para;</a></h3>
<p>Il modulo manual_probe viene caricato automaticamente.</p>
<h4 id="manual_probe_1">MANUAL_PROBE<a class="headerlink" href="#manual_probe_1" title="Permanent link">&para;</a></h4>
@@ -5049,12 +5143,6 @@ section</a> is enabled.</p>
<p>Il comando seguente è disponibile quando una <a href="Config_Reference.html#mcp4018">sezione di configurazione mcp4018</a> è abilitata.</p>
<h4 id="set_digipot">SET_DIGIPOT<a class="headerlink" href="#set_digipot" title="Permanent link">&para;</a></h4>
<p><code>SET_DIGIPOT DIGIPOT=config_name WIPER=&lt;value&gt;</code>: Questo comando cambierà il valore corrente del digipot. Questo valore dovrebbe essere in genere compreso tra 0.0 e 1.0, a meno che non sia definita una 'scale' nella configurazione. Quando viene definita 'scale', questo valore dovrebbe essere compreso tra 0,0 e 'scale'.</p>
<h3 id="led">[led]<a class="headerlink" href="#led" title="Permanent link">&para;</a></h3>
<p>Il comando seguente è disponibile quando una qualsiasi delle <a href="Config_Reference.html#leds">sezioni di configurazione led</a> è abilitata.</p>
<h4 id="set_led">SET_LED<a class="headerlink" href="#set_led" title="Permanent link">&para;</a></h4>
<p><code>SET_LED LED=&lt;nome_config&gt; ROSSO=&lt;valore&gt; VERDE=&lt;valore&gt; BLU=&lt;valore&gt; BIANCO=&lt;valore&gt; [INDEX=&lt;indice&gt;] [TRANSMIT=0] [SYNC=1]</code>: Imposta il LED in output. Ogni colore <code>&lt;valore&gt;</code> deve essere compreso tra 0,0 e 1,0. L'opzione BIANCO è valida solo su LED RGBW. Se il LED supporta più chip in una catena daisy-chain, è possibile specificare INDEX per modificare il colore del solo chip specificato (1 per il primo chip, 2 per il secondo, ecc.). Se INDEX non viene fornito, tutti i LED nella catena verranno impostati sul colore fornito. Se viene specificato TRANSMIT=0, il cambio colore verrà effettuato solo sul successivo comando SET_LED che non specifica TRANSMIT=0; questo può essere utile in combinazione con il parametro INDEX per raggruppare più aggiornamenti in una catena. Per impostazione predefinita, il comando SET_LED sincronizzerà le modifiche con altri comandi gcode in corso. Ciò può comportare un comportamento indesiderato se i LED vengono impostati mentre la stampante non sta stampando in quanto reimposta il timeout di inattività. Se non è necessaria una tempistica attenta, è possibile specificare il parametro SYNC=0 opzionale per applicare le modifiche senza ripristinare il timeout di inattività.</p>
<h4 id="set_led_template">SET_LED_TEMPLATE<a class="headerlink" href="#set_led_template" title="Permanent link">&para;</a></h4>
<p><code>SET_LED_TEMPLATE LED=&lt;nome_led&gt; TEMPLATE=&lt;nome_modello&gt; [&lt;param_x&gt;=&lt;letterale&gt;] [INDEX=&lt;indice&gt;]</code>: Assegna un <a href="Config_Reference.html#modello_visualizzazione">modello_visualizzazione</a> a un dato <a href="Riferimento_Configurazione .md#led">LED</a>. Ad esempio, se si definisce una sezione di configurazione <code>[display_template my_led_template]</code> allora si potrebbe assegnare <code>TEMPLATE=my_led_template</code> qui. Il display_template dovrebbe produrre una stringa separata da virgole contenente quattro numeri in virgola mobile corrispondenti alle impostazioni dei colori rosso, verde, blu e bianco. Il modello verrà continuamente valutato e il LED verrà impostato automaticamente sui colori risultanti. È possibile impostare i parametri display_template da utilizzare durante la valutazione del modello (i parametri verranno analizzati come valori letterali Python). Se INDEX non è specificato, tutti i chip nella catena dei LED verranno impostati sul modello, altrimenti verrà aggiornato solo il chip con l'indice specificato. Se TEMPLATE è una stringa vuota, questo comando cancellerà qualsiasi modello precedente assegnato al LED (è quindi possibile utilizzare i comandi <code>SET_LED</code> per gestire le impostazioni del colore del LED).</p>
<h3 id="output_pin">[output_pin]<a class="headerlink" href="#output_pin" title="Permanent link">&para;</a></h3>
<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">&para;</a></h4>
@@ -5077,10 +5165,6 @@ section</a> is enabled.</p>
<p><code>PALETTE_CUT</code>: Questo comando indica alla Palette 2 di tagliare il filamento attualmente caricato nello splice core.</p>
<h4 id="palette_smart_load">PALETTE_SMART_LOAD<a class="headerlink" href="#palette_smart_load" title="Permanent link">&para;</a></h4>
<p><code>PALETTE_SMART_LOAD</code>: Questo comando avvia la sequenza di caricamento intelligente sulla Palette 2. Il filamento viene caricato automaticamente estrudendolo alla distanza calibrata sul dispositivo per la stampante e istruisce la Palette 2 una volta completato il caricamento. Questo comando equivale a premere <strong>Smart Load</strong> direttamente sullo schermo della Palette 2 dopo che il caricamento del filamento è stato completato.</p>
<h3 id="pid_calibrate">[pid_calibrate]<a class="headerlink" href="#pid_calibrate" title="Permanent link">&para;</a></h3>
<p>Il modulo pid_calibrate viene caricato automaticamente se nel file di configurazione è definito un riscaldatore.</p>
<h4 id="pid_calibrate_1">PID_CALIBRATE<a class="headerlink" href="#pid_calibrate_1" title="Permanent link">&para;</a></h4>
<p><code>PID_CALIBRATE HEATER=&lt;nome_config&gt; TARGET=&lt;temperatura&gt; [WRITE_FILE=1]</code>: esegue un test di calibrazione PID. Il riscaldatore specificato verrà abilitato fino al raggiungimento della temperatura target specificata, quindi il riscaldatore verrà spento e acceso per diversi cicli. Se il parametro WRITE_FILE è abilitato, verrà creato il file /tmp/heattest.txt con un log di tutti i campioni di temperatura prelevati durante il test.</p>
<h3 id="pause_resume">[pause_resume]<a class="headerlink" href="#pause_resume" title="Permanent link">&para;</a></h3>
<p>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#pause_resume">pause_resume config section</a> è abilitata:</p>
<h4 id="pause">PAUSE<a class="headerlink" href="#pause" title="Permanent link">&para;</a></h4>
@@ -5091,6 +5175,10 @@ section</a> is enabled.</p>
<p><code>CLEAR_PAUSE</code>: cancella lo stato di pausa corrente senza riprendere la stampa. Questo è utile se si decide di annullare una stampa dopo un PAUSE. Si consiglia di aggiungerlo al gcode iniziale per assicurarsi che lo stato in pausa sia aggiornato per ogni stampa.</p>
<h4 id="cancel_print">CANCEL_PRINT<a class="headerlink" href="#cancel_print" title="Permanent link">&para;</a></h4>
<p><code>CANCEL_PRINT</code>: Annulla la stampa corrente.</p>
<h3 id="pid_calibrate">[pid_calibrate]<a class="headerlink" href="#pid_calibrate" title="Permanent link">&para;</a></h3>
<p>Il modulo pid_calibrate viene caricato automaticamente se nel file di configurazione è definito un riscaldatore.</p>
<h4 id="pid_calibrate_1">PID_CALIBRATE<a class="headerlink" href="#pid_calibrate_1" title="Permanent link">&para;</a></h4>
<p><code>PID_CALIBRATE HEATER=&lt;nome_config&gt; TARGET=&lt;temperatura&gt; [WRITE_FILE=1]</code>: esegue un test di calibrazione PID. Il riscaldatore specificato verrà abilitato fino al raggiungimento della temperatura target specificata, quindi il riscaldatore verrà spento e acceso per diversi cicli. Se il parametro WRITE_FILE è abilitato, verrà creato il file /tmp/heattest.txt con un log di tutti i campioni di temperatura prelevati durante il test.</p>
<h3 id="print_stats">[print_stats]<a class="headerlink" href="#print_stats" title="Permanent link">&para;</a></h3>
<p>Il modulo print_stats viene caricato automaticamente.</p>
<h4 id="set_print_stats_info">SET_PRINT_STATS_INFO<a class="headerlink" href="#set_print_stats_info" title="Permanent link">&para;</a></h4>
@@ -5158,7 +5246,7 @@ section</a> is enabled.</p>
<h3 id="save_variables">[save_variables]<a class="headerlink" href="#save_variables" title="Permanent link">&para;</a></h3>
<p>Il comando seguente è abilitato se è stata abilitata una <a href="Config_Reference.html#save_variables">sezione di configurazione save_variables</a>.</p>
<h4 id="save_variable">SAVE_VARIABLE<a class="headerlink" href="#save_variable" title="Permanent link">&para;</a></h4>
<p><code>SAVE_VARIABLE VARIABLE=&lt;nome&gt; VALUE=&lt;valore&gt;</code>: salva la variabile su disco in modo che possa essere utilizzata tra i riavvii. Tutte le variabili memorizzate vengono caricate nel dict <code>printer.save_variables.variables</code> all'avvio e possono essere utilizzate nelle macro gcode. Il VALUE fornito viene analizzato come un valore letterale Python.</p>
<p><code>SAVE_VARIABLE VARIABLE=&lt;name&gt; VALUE=&lt;value&gt;</code>: Saves the variable to disk so that it can be used across restarts. The VARIABLE must be lowercase. All stored variables are loaded into the <code>printer.save_variables.variables</code> dict at startup and can be used in gcode macros. The provided VALUE is parsed as a Python literal.</p>
<h3 id="screws_tilt_adjust">[screws_tilt_adjust]<a class="headerlink" href="#screws_tilt_adjust" title="Permanent link">&para;</a></h3>
<p>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#screws_tilt_adjust">sezione di configurazione viti_tilt_adjust</a> è abilitata (consultare anche la <a href="Manual_Level.html#adjusting-bed-leveling-screws-using-the-bed-probe">manual level guide</a>).</p>
<h4 id="screws_tilt_calculate">SCREWS_TILT_CALCULATE<a class="headerlink" href="#screws_tilt_calculate" title="Permanent link">&para;</a></h4>
@@ -5199,6 +5287,18 @@ section</a> is enabled.</p>
<p>Il comando seguente è disponibile quando una <a href="Config_Reference.html#ventola_temperatura">sezione di configurazione della ventola_temperatura</a> è abilitata.</p>
<h4 id="set_temperature_fan_target">SET_TEMPERATURE_FAN_TARGET<a class="headerlink" href="#set_temperature_fan_target" title="Permanent link">&para;</a></h4>
<p><code>SET_TEMPERATURE_FAN_TARGET temperature_fan=&lt;temperature_fan_name&gt; [target=&lt;target_temperature&gt;] [min_speed=&lt;min_speed&gt;] [max_speed=&lt;max_speed&gt;]</code>: Imposta la temperatura target per una temperature_fan. Se non viene fornito un target, viene impostato sulla temperatura specificata nel file di configurazione. Se le velocità non vengono fornite, non viene applicata alcuna modifica.</p>
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">&para;</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">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_CALIBRATE [PROBE=&lt;probe name&gt;] [TARGET=&lt;value&gt;] [STEP=&lt;value&gt;]</code>: Initiates probe drift calibration for eddy current based probes. The <code>TARGET</code> is a target temperature for the last sample. When the temperature recorded during a sample exceeds the <code>TARGET</code> calibration will complete. The <code>STEP</code> parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to <code>TEMPERATURE_PROBE_NEXT</code>. The default <code>STEP</code> is 2.</p>
<h4 id="temperature_probe_next">TEMPERATURE_PROBE_NEXT<a class="headerlink" href="#temperature_probe_next" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_NEXT</code>: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by <code>STEP</code> has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.</p>
<h4 id="temperature_probe_complete">TEMPERATURE_PROBE_COMPLETE:<a class="headerlink" href="#temperature_probe_complete" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_COMPLETE</code>: Can be used to end calibration and save the current result before the <code>TARGET</code> temperature is reached. This command is only available during calibration.</p>
<h4 id="abort">ABORT<a class="headerlink" href="#abort" title="Permanent link">&para;</a></h4>
<p><code>ABORT</code>: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.</p>
<h3 id="temperature_probe_enable">TEMPERATURE_PROBE_ENABLE<a class="headerlink" href="#temperature_probe_enable" title="Permanent link">&para;</a></h3>
<p><code>TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]</code>: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.</p>
<h3 id="tmcxxxx">[tmcXXXX]<a class="headerlink" href="#tmcxxxx" title="Permanent link">&para;</a></h3>
<p>I seguenti comandi sono disponibili quando una qualsiasi delle <a href="Config_Reference.html#tmc-stepper-driver-configuration">tmcXXXX config section</a> è abilitata.</p>
<h4 id="dump_tmc">DUMP_TMC<a class="headerlink" href="#dump_tmc" title="Permanent link">&para;</a></h4>
@@ -5246,18 +5346,6 @@ section</a> is enabled.</p>
<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">&para;</a></h4>
<p><code>Z_TILT_ADJUST [RETRIES=&lt;value&gt;] [RETRY_TOLERANCE=&lt;value&gt;] [HORIZONTAL_MOVE_Z=&lt;value&gt;] [&lt;probe_parameter&gt;=&lt;value&gt;]</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">&para;</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">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_CALIBRATE [PROBE=&lt;probe name&gt;] [TARGET=&lt;value&gt;] [STEP=&lt;value&gt;]</code>: Initiates probe drift calibration for eddy current based probes. The <code>TARGET</code> is a target temperature for the last sample. When the temperature recorded during a sample exceeds the <code>TARGET</code> calibration will complete. The <code>STEP</code> parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to <code>TEMPERATURE_PROBE_NEXT</code>. The default <code>STEP</code> is 2.</p>
<h4 id="temperature_probe_next">TEMPERATURE_PROBE_NEXT<a class="headerlink" href="#temperature_probe_next" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_NEXT</code>: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by <code>STEP</code> has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.</p>
<h4 id="temperature_probe_complete">TEMPERATURE_PROBE_COMPLETE:<a class="headerlink" href="#temperature_probe_complete" title="Permanent link">&para;</a></h4>
<p><code>TEMPERATURE_PROBE_COMPLETE</code>: Can be used to end calibration and save the current result before the <code>TARGET</code> temperature is reached. This command is only available during calibration.</p>
<h4 id="abort">ABORT<a class="headerlink" href="#abort" title="Permanent link">&para;</a></h4>
<p><code>ABORT</code>: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.</p>
<h3 id="temperature_probe_enable">TEMPERATURE_PROBE_ENABLE<a class="headerlink" href="#temperature_probe_enable" title="Permanent link">&para;</a></h3>
<p><code>TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]</code>: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.</p>
</article>

4
it/Hall_Filament_Width_Sensor.html
View File

@@ -1357,8 +1357,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

30
it/Installation.html
View File

@@ -1366,8 +1366,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1481,8 +1481,8 @@
<h1 id="installazione">Installazione<a class="headerlink" href="#installazione" title="Permanent link">&para;</a></h1>
<p>These instructions assume the software will run on a linux based host running a Klipper compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian based Linux device be used as the host machine (see the <a href="FAQ.html#can-i-run-klipper-on-something-other-than-a-raspberry-pi-3">FAQ</a> for other options).</p>
<p>For the purposes of these instructions host relates to the Linux device and mcu relates to the printboard. SBC relates to the term Small Board Computer such as the Raspberry Pi.</p>
<p>These instructions assume the software will run on a Linux-based host running a Klipper-compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian-based Linux device be used as the host machine (see the <a href="FAQ.html#can-i-run-klipper-on-something-other-than-a-raspberry-pi-3">FAQ</a> for other options).</p>
<p>For the purposes of these instructions, host relates to the Linux device and mcu relates to the printer board. SBC relates to the term Small Board Computer such as the Raspberry Pi.</p>
<h2 id="ottenere-un-file-di-configurazione-di-klipper">Ottenere un file di configurazione di Klipper<a class="headerlink" href="#ottenere-un-file-di-configurazione-di-klipper" title="Permanent link">&para;</a></h2>
<p>Most Klipper settings are determined by a "printer configuration file" printer.cfg, that will be stored on the host. An appropriate configuration file can often be found by looking in the Klipper <a href="https://github.com/Klipper3d/klipper/blob/master/config/">config directory</a> for a file starting with a "printer-" prefix that corresponds to the target printer. The Klipper configuration file contains technical information about the printer that will be needed during the installation.</p>
<p>Se non c'è un file di configurazione della stampante appropriato nella directory di configurazione di Klipper, prova a cercare nel sito web del produttore della stampante per vedere se hanno un file di configurazione di Klipper appropriato.</p>
@@ -1493,13 +1493,13 @@
<p>Currently the best choices are front ends that retrieve information through the <a href="https://moonraker.readthedocs.io/">Moonraker web API</a> and there is also the option to use <a href="https://octoprint.org/">Octoprint</a> to control Klipper.</p>
<p>The choice is up to the user on what to use, but the underlying Klipper is the same in all cases. We encourage users to research the options available and make an informed decision.</p>
<h2 id="obtaining-an-os-image-for-sbcs">Obtaining an OS image for SBC's<a class="headerlink" href="#obtaining-an-os-image-for-sbcs" title="Permanent link">&para;</a></h2>
<p>There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manafactures of these SBC boards also provide their own Klipper-centric images.</p>
<p>The two main Moonraker based front ends are <a href="https://docs.fluidd.xyz/">Fluidd</a> and <a href="https://docs.mainsail.xyz/">Mainsail</a>, the latter of which has a premade install image <a href="http://docs.mainsailOS.xyz">"MainsailOS"</a>, this has the option for Raspberry Pi and some OrangePi varianta.</p>
<p>There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manufacturers of these SBC boards also provide their own Klipper-centric images.</p>
<p>The two main Moonraker-based front ends are <a href="https://docs.fluidd.xyz/">Fluidd</a> and <a href="https://docs.mainsail.xyz/">Mainsail</a>, the latter of which has a premade install image <a href="https://docs-os.mainsail.xyz/">"MainsailOS"</a>, this has the option for Raspberry Pi and some OrangePi variants.</p>
<p>Fluidd can be installed via KIAUH(Klipper Install And Update Helper), which is explained below and is a 3rd party installer for all things Klipper.</p>
<p>OctoPrint can be installed via the popular OctoPi image or via KIAUH, this process is explained in <OctoPrint.md></p>
<h2 id="installing-via-kiauh">Installing via KIAUH<a class="headerlink" href="#installing-via-kiauh" title="Permanent link">&para;</a></h2>
<p>Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of a x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions working and even mask access to some print boards.</p>
<p>KIAUH can be used to install Klipper and its associated programs on a variety of Linux based systems that run a form of Debian. More information can be found at <a href="https://github.com/dw-0/kiauh">https://github.com/dw-0/kiauh</a></p>
<p>Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of an x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions from working and even mask access to some printer boards.</p>
<p>KIAUH can be used to install Klipper and its associated programs on a variety of Linux-based systems that run a form of Debian. More information can be found at <a href="https://github.com/dw-0/kiauh">https://github.com/dw-0/kiauh</a></p>
<h2 id="compilare-il-firmware-e-flashare-il-microcontrollore">Compilare il firmware e flashare il microcontrollore<a class="headerlink" href="#compilare-il-firmware-e-flashare-il-microcontrollore" title="Permanent link">&para;</a></h2>
<p>To compile the micro-controller code, start by running these commands on your host device:</p>
<div class="highlight"><pre><span></span><code>cd ~/klipper/
@@ -1510,7 +1510,7 @@ make menuconfig
<div class="highlight"><pre><span></span><code>make
</code></pre></div>
<p>Se i commenti nella parte superiore del <a href="#obtain-a-klipper-configuration-file">file di configurazione della stampante</a> descrivono i passaggi personalizzati per il "flash" dell'immagine finale sulla scheda di controllo della stampante, segui questi passaggi e poi procedi con <a href="#configuring-octoprint-to-use-klipper">configurazione OctoPrint</a>.</p>
<p>If the comments at the top of the <a href="#obtain-a-klipper-configuration-file">printer configuration file</a> describe custom steps for "flashing" the final image to the printer control board, then follow those steps and then proceed to <a href="#configuring-octoprint-to-use-klipper">configuring OctoPrint</a>.</p>
<p>In caso contrario, i seguenti passaggi vengono spesso utilizzati per eseguire il "flash" della scheda di controllo della stampante. Innanzitutto è necessario determinare la porta seriale collegata al microcontrollore. Esegui quanto segue:</p>
<div class="highlight"><pre><span></span><code>ls /dev/serial/by-id/*
</code></pre></div>
@@ -1520,8 +1520,8 @@ make menuconfig
</code></pre></div>
<p>It's common for each printer to have its own unique serial port name. This unique name will be used when flashing the micro-controller. It's possible there may be multiple lines in the above output - if so, choose the line corresponding to the micro-controller. If many items are listed and the choice is ambiguous, unplug the board and run the command again, the missing item will be your print board(see the <a href="FAQ.html#wheres-my-serial-port">FAQ</a> for more information).</p>
<p>For common micro-controllers with STM32 or clone chips, LPC chips and others it is usual that these need an initial Klipper flash via SD card.</p>
<p>When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occuring.</p>
<p>For common micro-controllers with STM32 or clone chips, LPC chips and others, it is usual that these need an initial Klipper flash via SD card.</p>
<p>When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring.</p>
<p>For common micro-controllers using Atmega chips, for example the 2560, the code can be flashed with something similar to:</p>
<div class="highlight"><pre><span></span><code>sudo service klipper stop
make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
@@ -1538,9 +1538,9 @@ sudo service klipper start
<p>It is important to note that RP2040 chips may need to be put into Boot mode before this operation.</p>
<h2 id="configurare-klipper">Configurare Klipper<a class="headerlink" href="#configurare-klipper" title="Permanent link">&para;</a></h2>
<p>The next step is to copy the <a href="#obtain-a-klipper-configuration-file">printer configuration file</a> to the host.</p>
<p>Arguably the easiest way to set the Klipper configuration file is using the built in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.</p>
<p>Arguably the easiest way to set the Klipper configuration file is using the built-in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.</p>
<p>Another option is to use a desktop editor that supports editing files over the "scp" and/or "sftp" protocols. There are freely available tools that support this (eg, Notepad++, WinSCP, and Cyberduck). Load the printer config file in the editor and then save it as a file named "printer.cfg" in the home directory of the pi user (ie, /home/pi/printer.cfg).</p>
<p>Alternatively, one can also copy and edit the file directly on the host via ssh. That may look something like the following (be sure to update the command to use the appropriate printer config filename):</p>
<p>Alternatively, one can also copy and edit the file directly on the host via SSH. That may look something like the following (be sure to update the command to use the appropriate printer config filename):</p>
<div class="highlight"><pre><span></span><code>cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
nano ~/printer.cfg
</code></pre></div>
@@ -1558,9 +1558,9 @@ nano ~/printer.cfg
serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
</code></pre></div>
<p>After creating and editing the file it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.</p>
<p>After creating and editing the file, it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report that the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.</p>
<p>Quando si personalizza il file di configurazione della stampante, non è raro che Klipper segnali un errore di configurazione. Se si verifica un errore, apportare le correzioni necessarie al file di configurazione della stampante ed eseguire il "restart" finché "status" non segnala che la stampante è pronta.</p>
<p>Klipper reports error messages via the command console and via pop up in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located in ~/printer_data/logs this is named klippy.log</p>
<p>Klipper reports error messages via the command console and pop-ups in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located at <code>~/printer_data/logs/klippy.log</code>.</p>
<p>Dopo che Klipper ha segnalato che la stampante è pronta, vai al <a href="Config_checks.html">config check document</a> per eseguire alcuni controlli di base sulle definizioni nel file di configurazione. Vedere i<a href="Overview.html">documentation reference</a> per altre informazioni.</p>

4
it/Kinematics.html
View File

@@ -1411,8 +1411,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

1635
it/Load_Cell.html Normal file
View File

File diff suppressed because it is too large Load Diff

4
it/MCU_Commands.html
View File

@@ -1383,8 +1383,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Manual_Level.html
View File

@@ -1358,8 +1358,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

23
it/Measuring_Resonances.html
View File

@@ -838,11 +838,11 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948
</a>
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500">
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948">
<ul class="md-nav__list">
<li class="md-nav__item">
@@ -1595,8 +1595,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1721,11 +1721,11 @@
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500
<a href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948" class="md-nav__link">
MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948
</a>
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500">
<nav class="md-nav" aria-label="MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948">
<ul class="md-nav__list">
<li class="md-nav__item">
@@ -1942,7 +1942,7 @@
<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, 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>
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948s 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">&para;</a></h2>
<table>
<thead>
@@ -2107,7 +2107,7 @@ GND+SCL
</code></pre></div>
<p>Note that unlike a cable shield, any GND(s) should be connected at both ends.</p>
<h4 id="mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500">MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500<a class="headerlink" href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500" title="Permanent link">&para;</a></h4>
<h4 id="mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948">MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500/ICM20948<a class="headerlink" href="#mpu-9250mpu-9255mpu-6515mpu-6050mpu-6500icm20948" title="Permanent link">&para;</a></h4>
<p>These accelerometers have been tested to work over I2C on the RPi, RP2040 (Pico) and AVR at 400kbit/s (<em>fast mode</em>). Some MPU accelerometer modules include pull-ups, but some are too large at 10K and must be changed or supplemented by smaller parallel resistors.</p>
<p>Schema di connessione consigliato per I2C su Raspberry Pi:</p>
<table>
@@ -2328,6 +2328,7 @@ probe_points:
100, 100, 20 # un esempio
</code></pre></div>
<p>If you are using the ICM20948, replace instances of "mpu9250" with "icm20948".</p>
<h4 id="configure-mpu-9520-compatibles-with-pico">Configure MPU-9520 Compatibles With Pico<a class="headerlink" href="#configure-mpu-9520-compatibles-with-pico" title="Permanent link">&para;</a></h4>
<p>Pico I2C is set to 400000 on default. Simply add the following to the printer.cfg:</p>
<div class="highlight"><pre><span></span><code>[mcu pico]
@@ -2346,6 +2347,7 @@ probe_points:
pins: pico:gpio23
</code></pre></div>
<p>If you are using the ICM20948, replace instances of "mpu9250" with "icm20948".</p>
<h4 id="configure-mpu-9520-compatibles-with-avr">Configure MPU-9520 Compatibles with AVR<a class="headerlink" href="#configure-mpu-9520-compatibles-with-avr" title="Permanent link">&para;</a></h4>
<p>AVR I2C will be set to 400000 by the mpu9250 option. Simply add the following to the printer.cfg:</p>
<div class="highlight"><pre><span></span><code>[mcu nano]
@@ -2360,6 +2362,7 @@ probe_points:
100, 100, 20 # an example
</code></pre></div>
<p>If you are using the ICM20948, replace instances of "mpu9250" with "icm20948".</p>
<p>Riavvia Klipper tramite il comando <code>RESTART</code>.</p>
<h2 id="misurare-le-risonanze">Misurare le risonanze<a class="headerlink" href="#misurare-le-risonanze" title="Permanent link">&para;</a></h2>
<h3 id="controllo-della-configurazione">Controllo della configurazione<a class="headerlink" href="#controllo-della-configurazione" title="Permanent link">&para;</a></h3>

4
it/Multi_MCU_Homing.html
View File

@@ -1298,8 +1298,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Navigation.html
View File

@@ -1281,8 +1281,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/OctoPrint.html
View File

@@ -1345,8 +1345,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

5
it/Overview.html
View File

@@ -1348,8 +1348,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1524,6 +1524,7 @@
<li><a href="TSL1401CL_Filament_Width_Sensor.html">Sensore larghezza filamento TSL1401CL</a></li>
<li><a href="HallFilamentWidthSensor.md">Sensore di larghezza del filamento Hall</a></li>
<li><a href="Eddy_Probe.html">Eddy Current Inductive probe</a></li>
<li><a href="Load_Cell.html">Load Cells</a></li>
</ul>

4
it/Packaging.html
View File

@@ -1350,8 +1350,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

6
it/Pressure_Advance.html
View File

@@ -1336,8 +1336,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1427,7 +1427,7 @@
<h2 id="regolazione-della-pressure-advance">Regolazione della pressure advance<a class="headerlink" href="#regolazione-della-pressure-advance" title="Permanent link">&para;</a></h2>
<p>Pressure advance fa due cose utili: riduce le colature durante i movimenti senza estrusione e riduce il blobbing durante le curve. Questa guida utilizza la seconda funzione (riduzione del blobbing durante le curve) come meccanismo per la messa a punto.</p>
<p>Per calibrare la pressure advance, la stampante deve essere configurata e operativa poiché il test di ottimizzazione prevede la stampa e l'ispezione di un oggetto di prova. È una buona idea leggere questo documento per intero prima di eseguire il test.</p>
<p>Usa uno slicer per generare il codice G per il grande cubo vuoto che si trova in <a href="prints/square_tower.stl">docs/prints/square_tower.stl</a>. Utilizzare una velocità elevata (ad es. 100 mm/s), riempimento zero e un'altezza dello strato grossolana (l'altezza dello strato dovrebbe essere circa il 75% del diametro dell'ugello). Assicurati che qualsiasi "controllo dinamico dell'accelerazione" sia disabilitato nello slicer.</p>
<p>Use a slicer to generate g-code for the large hollow square found in <a href="prints/square_tower.stl">docs/prints/square_tower.stl</a>. Use a high speed (eg, 100mm/s), zero infill, and a coarse layer height (the layer height should be around 75% of the nozzle diameter). Make sure any "dynamic acceleration control" and "scarf joint" seams are disabled in the slicer.</p>
<p>Prepararsi per il test emettendo il seguente comando G-Code:</p>
<div class="highlight"><pre><span></span><code>SET_VELOCITY_LIMIT SQUARE_CORNER_VELOCITY=1 ACCEL=500
</code></pre></div>

4
it/Probe_Calibrate.html
View File

@@ -1359,8 +1359,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Protocol.html
View File

@@ -1437,8 +1437,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/RPi_microcontroller.html
View File

@@ -1378,8 +1378,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

74
it/Releases.html
View File

@@ -371,6 +371,20 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#klipper-0130" class="md-nav__link">
Klipper 0.13.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0120" class="md-nav__link">
Klipper 0.12.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0110" class="md-nav__link">
Klipper 0.11.0
@@ -1403,8 +1417,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1458,6 +1472,20 @@
</label>
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
<li class="md-nav__item">
<a href="#klipper-0130" class="md-nav__link">
Klipper 0.13.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0120" class="md-nav__link">
Klipper 0.12.0
</a>
</li>
<li class="md-nav__item">
<a href="#klipper-0110" class="md-nav__link">
Klipper 0.11.0
@@ -1560,6 +1588,48 @@
<h1 id="versioni">Versioni<a class="headerlink" href="#versioni" title="Permanent link">&para;</a></h1>
<p>Storico delle versioni di Klipper. Vedi <a href="Installation.html">installation</a> per informazioni sull'installazione di Klipper.</p>
<h2 id="klipper-0130">Klipper 0.13.0<a class="headerlink" href="#klipper-0130" title="Permanent link">&para;</a></h2>
<p>Available on 20250411. Major changes in this release:</p>
<ul>
<li>New "sweeping vibrations" resonance testing mechanism for input shaper.</li>
<li>Fans and GPIO pins can now be assigned a formula (via Jinja2 "templates").</li>
<li>The bed_mesh code now supports "adaptive bed mesh". The area probed can be adjusted for the size of the print.</li>
<li>A new <code>minimum_cruise_ratio</code> kinematic parameter has been added (it replaces the previous <code>max_accel_to_decel</code> parameter).</li>
<li>Several new sensors added:<ul>
<li>Support for ldc1612 "eddy" current sensors. This includes probing support, fast "scan" probing, and temperature calibration.</li>
<li>New support for "load cell" measurements. Support for connecting these load cells to hx71x and ads1220 ADC sensors.</li>
<li>Support for BMP180, BMP388, and SHT3x temperature sensors. Support for measuring temperature with ADS1x1x ADC chips.</li>
<li>New lis3dh and icm20948 accelerometer support.</li>
<li>Support for mt6816 and mt6826s "hall angle" sensors.</li>
</ul>
</li>
<li>New micro-controller improvements:<ul>
<li>New support for rp2350 micro-controllers.</li>
<li>Existing rp2040 chips now run at 200MHz (up from 125Mhz).</li>
<li>The micro-controller code can now define many more commands (up to 16384 from 128).</li>
</ul>
</li>
<li>Other modules added: aip31068_spi, canbus_stats, error_mcu, garbage_collection, pwm_cycle_time, pwm_tool, garbage_collection.</li>
<li>Correzione di diversi bug e pulizia del codice.</li>
</ul>
<h2 id="klipper-0120">Klipper 0.12.0<a class="headerlink" href="#klipper-0120" title="Permanent link">&para;</a></h2>
<p>Available on 20231110. Major changes in this release:</p>
<ul>
<li>Support for COPY and MIRROR modes on IDEX printers.</li>
<li>Several micro-controller improvements:<ul>
<li>Support for new ar100 and hc32f460 architectures.</li>
<li>Support for stm32f7, stm32g0b0, stm32g07x, stm32g4, stm32h723, n32g45x, samc21, and samd21j18 chip variants.</li>
<li>Improved DFU and Katapult reboot handling.</li>
<li>Improved performance on USB to CANbus bridge mode.</li>
<li>Improved performance on "linux mcu".</li>
<li>New support for software based i2c.</li>
</ul>
</li>
<li>New hardware support for tmc2240 stepper motor drivers, lis2dw12 accelerometers, and aht10 temperature sensors.</li>
<li>New axis_twist_compensation and temperature_combined modules added.</li>
<li>New support for gcode arcs in XY, XZ, and YZ planes.</li>
<li>Correzione di diversi bug e pulizia del codice.</li>
</ul>
<h2 id="klipper-0110">Klipper 0.11.0<a class="headerlink" href="#klipper-0110" title="Permanent link">&para;</a></h2>
<p>Disponibile su 20221128. Modifiche principali in questa versione:</p>
<ul>

4
it/Resonance_Compensation.html
View File

@@ -1454,8 +1454,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Rotation_Distance.html
View File

@@ -1379,8 +1379,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/SDCard_Updates.html
View File

@@ -1384,8 +1384,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Skew_Correction.html
View File

@@ -1357,8 +1357,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Slicers.html
View File

@@ -1378,8 +1378,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

8
it/Sponsors.html
View File

@@ -1286,8 +1286,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1527,7 +1527,7 @@
<nav class="md-footer__inner md-grid" aria-label="Piede">
<a href="Eddy_Probe.html" class="md-footer__link md-footer__link--prev" aria-label="Precedente: Eddy Current Inductive probe" rel="prev">
<a href="Load_Cell.html" class="md-footer__link md-footer__link--prev" aria-label="Precedente: Load Cells" rel="prev">
<div class="md-footer__button md-icon">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11h12z"/></svg>
</div>
@@ -1536,7 +1536,7 @@
<span class="md-footer__direction">
Precedente
</span>
Eddy Current Inductive probe
Load Cells
</div>
</div>
</a>

74
it/Status_Reference.html
View File

@@ -875,6 +875,13 @@
bed_screws
</a>
</li>
<li class="md-nav__item">
<a href="#canbus_stats" class="md-nav__link">
canbus_stats
</a>
</li>
<li class="md-nav__item">
@@ -994,6 +1001,13 @@
led
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
load_cell
</a>
</li>
<li class="md-nav__item">
@@ -1085,6 +1099,13 @@
servo
</a>
</li>
<li class="md-nav__item">
<a href="#skew_correctionpy" class="md-nav__link">
skew_correction.py
</a>
</li>
<li class="md-nav__item">
@@ -1639,8 +1660,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1713,6 +1734,13 @@
bed_screws
</a>
</li>
<li class="md-nav__item">
<a href="#canbus_stats" class="md-nav__link">
canbus_stats
</a>
</li>
<li class="md-nav__item">
@@ -1832,6 +1860,13 @@
led
</a>
</li>
<li class="md-nav__item">
<a href="#load_cell" class="md-nav__link">
load_cell
</a>
</li>
<li class="md-nav__item">
@@ -1923,6 +1958,13 @@
servo
</a>
</li>
<li class="md-nav__item">
<a href="#skew_correctionpy" class="md-nav__link">
skew_correction.py
</a>
</li>
<li class="md-nav__item">
@@ -2041,13 +2083,22 @@
<li><code>profiles</code>: l'insieme dei profili attualmente definiti come setup usando BED_MESH_PROFILE.</li>
</ul>
<h2 id="bed_screws">bed_screws<a class="headerlink" href="#bed_screws" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili nell'oggetto <code>Config_Reference.md#bed_screws</code>:</p>
<p>The following information is available in the <a href="Config_Reference.html#bed_screws">bed_screws</a> object:</p>
<ul>
<li><code>is_active</code>: Restituisce True se lo strumento di regolazione delle viti del letto è attualmente attivo.</li>
<li><code>state</code>: lo stato dello strumento di regolazione delle viti del piatto. È una delle seguenti stringhe: "adjust", "fine".</li>
<li><code>current_screw</code>: l'indice per la vite corrente in corso di regolazione.</li>
<li><code>accepted_screws</code>: il numero di viti accettate.</li>
</ul>
<h2 id="canbus_stats">canbus_stats<a class="headerlink" href="#canbus_stats" title="Permanent link">&para;</a></h2>
<p>The following information is available in the <code>canbus_stats some_mcu_name</code> object (this object is automatically available if an mcu is configured to use canbus):</p>
<ul>
<li><code>rx_error</code>: The number of receive errors detected by the micro-controller canbus hardware.</li>
<li><code>tx_error</code>: The number of transmit errors detected by the micro-controller canbus hardware.</li>
<li><code>tx_retries</code>: The number of transmit attempts that were retried due to bus contention or errors.</li>
<li><code>bus_state</code>: The status of the interface (typically "active" for a bus in normal operation, "warn" for a bus with recent errors, "passive" for a bus that will no longer transmit canbus error frames, or "off" for a bus that will no longer transmit or receive messages).</li>
</ul>
<p>Note that only the rp2XXX micro-controllers report a non-zero <code>tx_retries</code> field and the rp2XXX micro-controllers always report <code>tx_error</code> as zero and <code>bus_state</code> as "active".</p>
<h2 id="configfile">configfile<a class="headerlink" href="#configfile" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili nell'oggetto <code>configfile</code> (questo oggetto è sempre disponibile):</p>
<ul>
@@ -2161,6 +2212,7 @@
<h2 id="hall_filament_width_sensor">hall_filament_width_sensor<a class="headerlink" href="#hall_filament_width_sensor" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili nell'oggetto <a href="Config_Reference.html#hall_filament_width_sensor">hall_filament_width_sensor</a>:</p>
<ul>
<li>all items from <a href="Status_Reference.html#filament_switch_sensor">filament_switch_sensor</a></li>
<li><code>is_active</code>: Restituisce True se il sensore è attualmente attivo.</li>
<li><code>Diameter</code>: l'ultima lettura dal sensore in mm.</li>
<li><code>Raw</code>: l'ultima lettura grezza dell'ADC dal sensore.</li>
@@ -2191,6 +2243,17 @@
<ul>
<li><code>color_data</code>: un elenco di lista di colori contenenti i valori RGBW per ogni led nella catena. Ogni valore è rappresentato come un float da 0,0 a 1,0. Ciascuna lista di colori contiene 4 voci (rosso, verde, blu, bianco) anche se il LED sottostante supporta meno canali di colore. Ad esempio, è possibile accedere al valore blu (3° elemento nell'elenco dei colori) del secondo neopixel in una catena in <code>printer["neopixel &lt;config_name&gt;"].color_data[1][2]</code>.</li>
</ul>
<h2 id="load_cell">load_cell<a class="headerlink" href="#load_cell" title="Permanent link">&para;</a></h2>
<p>The following information is available for each <code>[load_cell name]</code>:</p>
<ul>
<li>'is_calibrated': True/False is the load cell calibrated</li>
<li>'counts_per_gram': The number of raw sensor counts that equals 1 gram of force</li>
<li>'reference_tare_counts': The reference number of raw sensor counts for 0 force</li>
<li>'tare_counts': The current number of raw sensor counts for 0 force</li>
<li>'force_g': The force in grams, averaged over the last polling period.</li>
<li>'min_force_g': The minimum force in grams, over the last polling period.</li>
<li>'max_force_g': The maximum force in grams, over the last polling period.</li>
</ul>
<h2 id="manual_probe">manual_probe<a class="headerlink" href="#manual_probe" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili nell'oggetto <code>manual_probe</code>:</p>
<ul>
@@ -2278,6 +2341,11 @@
<ul>
<li><code>printer["servo &lt;config_name&gt;"].value</code>: l'ultima impostazione del pin PWM (un valore compreso tra 0.0 e 1.0) associata al servo.</li>
</ul>
<h2 id="skew_correctionpy">skew_correction.py<a class="headerlink" href="#skew_correctionpy" title="Permanent link">&para;</a></h2>
<p>The following information is available in the <code>skew_correction</code> object (this object is available if any skew_correction is defined):</p>
<ul>
<li><code>current_profile_name</code>: Returns the name of the currently loaded SKEW_PROFILE.</li>
</ul>
<h2 id="stepper_enable">stepper_enable<a class="headerlink" href="#stepper_enable" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili nell'oggetto <code>stepper_enable</code> (questo oggetto è disponibile se è definito uno stepper):</p>
<ul>

5
it/TMC_Drivers.html
View File

@@ -1535,8 +1535,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>
@@ -1837,6 +1837,7 @@
<p>In generale, la modalità SpreadCycle fornisce una coppia maggiore e una maggiore precisione di posizionamento rispetto alla modalità StealthChop. Tuttavia, la modalità StealthChop può produrre un rumore udibile notevolmente inferiore su alcune stampanti.</p>
<p>I test di confronto delle modalità hanno mostrato un "ritardo posizionale" aumentato di circa il 75% di un passo completo durante i movimenti a velocità costante quando si utilizza la modalità StealthChop (ad esempio, su una stampante con distanza_rotazione di 40 mm e 200 passi_per_rotazione, la deviazione di posizione dei movimenti a velocità costante è aumentata di ~0,150 mm). Tuttavia, questo "ritardo nell'ottenimento della posizione richiesta" potrebbe non manifestarsi come un difetto di stampa significativo e si potrebbe preferire il comportamento più silenzioso della modalità stealthChop.</p>
<p>Si consiglia di utilizzare sempre la modalità "spreadCycle" (non specificando <code>stealthchop_threshold</code>) o di utilizzare sempre la modalità "stealthChop" (impostando <code>stealthchop_threshold</code> su 999999). Sfortunatamente, i driver spesso producono risultati scadenti e confusi se la modalità cambia mentre il motore è a una velocità diversa da zero.</p>
<p>Note that the <code>stealthchop_threshold</code> config option does not impact sensorless homing as Klipper automatically switches the TMC driver to an appropriate mode during sensorless homing operations.</p>
<h2 id="limpostazione-dellinterpolazione-tmc-introduce-una-piccola-deviazione-di-posizione">L'impostazione dell'interpolazione TMC introduce una piccola deviazione di posizione<a class="headerlink" href="#limpostazione-dellinterpolazione-tmc-introduce-una-piccola-deviazione-di-posizione" title="Permanent link">&para;</a></h2>
<p>L'impostazione <code>interpolate</code> del driver TMC può ridurre il rumore udibile del movimento della stampante a costo di introdurre un piccolo errore di posizione sistemico. Questo errore di posizione sistematico deriva dal ritardo del driver nell'esecuzione dei "passi" inviati da Klipper. Durante i movimenti a velocità costante, questo ritardo si traduce in un errore di posizione di quasi mezzo micropasso configurato (più precisamente, l'errore è di mezzo micropasso meno un 512esimo di un passo intero). Ad esempio, su un asse con una distanza_rotazione di 40 mm, 200 passi_per_rotazione e 16 micropassi, l'errore sistemico introdotto durante i movimenti a velocità costante è ~0,006 mm.</p>
<p>Per una migliore precisione di posizionamento, considerare l'utilizzo della modalità SpreadCycle e disabilitare l'interpolazione (impostare <code>interpolate: False</code> nella configurazione del driver TMC). Se configurato in questo modo, è possibile aumentare l'impostazione <code>microstep</code> per ridurre il rumore udibile durante il movimento del passo-passo. Tipicamente, un'impostazione microstep di <code>64</code> o <code>128</code> avrà un rumore udibile simile all'interpolazione e lo farà senza introdurre un errore posizionale sistemico.</p>

4
it/TSL1401CL_Filament_Width_Sensor.html
View File

@@ -1336,8 +1336,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

4
it/Using_PWM_Tools.html
View File

@@ -1350,8 +1350,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

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

Binary file not shown.

4
it/index.html
View File

@@ -1283,8 +1283,8 @@
<li class="md-nav__item">
<a href="Load_Cell.md" class="md-nav__link">
None
<a href="Load_Cell.html" class="md-nav__link">
Load Cells
</a>
</li>

2
it/search/search_index.json
View File

File diff suppressed because one or more lines are too long

115
it/sitemap.xml
View File

@@ -2,277 +2,282 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-03</lastmod>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2025-05-04</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>

BIN
it/sitemap.xml.gz
View File

Binary file not shown.