Deploying to gh-pages from @ Klipper3d/klipper@f7567a0db9 🚀

This commit is contained in:
KevinOConnor
2023-10-23 00:04:07 +00:00
parent 396e728f2d
commit 8dff4c78b5
293 changed files with 18737 additions and 1567 deletions

View File

@@ -617,8 +617,8 @@
<li class="md-nav__item">
<a href="/Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="/Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1150,8 +1150,8 @@
<li class="md-nav__item">
<a href="/Bootloader_Entry.md" class="md-nav__link">
None
<a href="/Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1365,8 +1365,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

File diff suppressed because it is too large Load Diff

View File

@@ -716,8 +716,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1249,8 +1249,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1226,8 +1226,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -681,8 +681,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1214,8 +1214,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -809,8 +809,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1342,8 +1342,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1337,8 +1337,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

1666
it/Bootloader_Entry.html Normal file

File diff suppressed because it is too large Load Diff

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1236,6 +1236,13 @@
Microcontrollori SAM4 (Duet Wifi)
</a>
</li>
<li class="md-nav__item">
<a href="#samdc21-micro-controllers-duet3d-toolboard-1lc" class="md-nav__link">
SAMDC21 micro-controllers (Duet3D Toolboard 1LC)
</a>
</li>
<li class="md-nav__item">
@@ -1363,8 +1370,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1534,6 +1541,13 @@
Microcontrollori SAM4 (Duet Wifi)
</a>
</li>
<li class="md-nav__item">
<a href="#samdc21-micro-controllers-duet3d-toolboard-1lc" class="md-nav__link">
SAMDC21 micro-controllers (Duet3D Toolboard 1LC)
</a>
</li>
<li class="md-nav__item">
@@ -1754,6 +1768,39 @@ bossac -U -p /dev/ttyACM0 -R
<div class="highlight"><pre><span></span><code>bossac --port=/dev/ttyACM0 -b -U -e -w -v -R out/klipper.bin
</code></pre></div>
<h2 id="samdc21-micro-controllers-duet3d-toolboard-1lc">SAMDC21 micro-controllers (Duet3D Toolboard 1LC)<a class="headerlink" href="#samdc21-micro-controllers-duet3d-toolboard-1lc" title="Permanent link">&para;</a></h2>
<p>The SAMC21 is flashed via the ARM Serial Wire Debug (SWD) interface. This is commonly done with a dedicated SWD hardware dongle. Alternatively, one can use a <a href="#running-openocd-on-the-raspberry-pi">Raspberry Pi with OpenOCD</a>.</p>
<p>When using OpenOCD with the SAMC21, extra steps must be taken to first put the chip into Cold Plugging mode if the board makes use of the SWD pins for other purposes. If using OpenOCD on a Rasberry Pi, this can be done by running the following commands before invoking OpenOCD.</p>
<div class="highlight"><pre><span></span><code>SWCLK=25
SWDIO=24
SRST=18
echo &quot;Exporting SWCLK and SRST pins.&quot;
echo $SWCLK &gt; /sys/class/gpio/export
echo $SRST &gt; /sys/class/gpio/export
echo &quot;out&quot; &gt; /sys/class/gpio/gpio$SWCLK/direction
echo &quot;out&quot; &gt; /sys/class/gpio/gpio$SRST/direction
echo &quot;Setting SWCLK low and pulsing SRST.&quot;
echo &quot;0&quot; &gt; /sys/class/gpio/gpio$SWCLK/value
echo &quot;0&quot; &gt; /sys/class/gpio/gpio$SRST/value
echo &quot;1&quot; &gt; /sys/class/gpio/gpio$SRST/value
echo &quot;Unexporting SWCLK and SRST pins.&quot;
echo $SWCLK &gt; /sys/class/gpio/unexport
echo $SRST &gt; /sys/class/gpio/unexport
</code></pre></div>
<p>To flash a program with OpenOCD use the following chip config:</p>
<div class="highlight"><pre><span></span><code>source [find target/at91samdXX.cfg]
</code></pre></div>
<p>Obtain a program; for instance, klipper can be built for this chip. Flash with OpenOCD commands similar to:</p>
<div class="highlight"><pre><span></span><code>at91samd chip-erase
at91samd bootloader 0
program out/klipper.elf verify
</code></pre></div>
<h2 id="microcontrollori-samd21-arduino-zero">Microcontrollori SAMD21 (Arduino Zero)<a class="headerlink" href="#microcontrollori-samd21-arduino-zero" title="Permanent link">&para;</a></h2>
<p>Il bootloader SAMD21 viene caricato in memoria flashing tramite l'interfaccia ARM Serial Wire Debug (SWD). Questo viene fatto comunemente con un dongle hardware SWD dedicato. In alternativa, è possibile utilizzare un <a href="#running-openocd-on-the-raspberry-pi">Raspberry Pi con OpenOCD</a>.</p>
<p>Per eseguire il flashing di un bootloader con OpenOCD, utilizzare la seguente configurazione del chip:</p>
@@ -2022,13 +2069,13 @@ gdb out/klipper.elf
<a href="CANBUS.html" class="md-footer__link md-footer__link--next" aria-label="Prossimo: CANBUS" rel="next">
<a href="Bootloader_Entry.html" class="md-footer__link md-footer__link--next" aria-label="Prossimo: Bootloader Entry" rel="next">
<div class="md-footer__title">
<div class="md-ellipsis">
<span class="md-footer__direction">
Prossimo
</span>
CANBUS
Bootloader Entry
</div>
</div>
<div class="md-footer__button md-icon">

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1157,8 +1157,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1495,7 +1495,7 @@ iface can0 can static
<nav class="md-footer__inner md-grid" aria-label="Piede">
<a href="Bootloaders.html" class="md-footer__link md-footer__link--prev" aria-label="Precedente: Bootloader" rel="prev">
<a href="Bootloader_Entry.html" class="md-footer__link md-footer__link--prev" aria-label="Precedente: Bootloader Entry" 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>
@@ -1504,7 +1504,7 @@ iface can0 can static
<span class="md-footer__direction">
Precedente
</span>
Bootloader
Bootloader Entry
</div>
</div>
</a>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1157,8 +1157,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1239,8 +1239,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1239,8 +1239,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1254,8 +1254,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1290,8 +1290,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -663,8 +663,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1196,8 +1196,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1335,6 +1335,9 @@
<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>20230826: If <code>safe_distance</code> is set or calculated to be 0 in <code>[dual_carriage]</code>, the carriages proximity checks will be disabled as per documentation. A user may wish to configure <code>safe_distance</code> explicitly to prevent accidental crashes of the carriages with each other. Additionally, the homing order of the primary and the dual carriage is changed in some configurations (certain configurations when both carriages home in the same direction, see <a href="Config_Reference.html#dual_carriage">[dual_carriage] configuration reference</a> for more details).</p>
<p>20230810: The flash-sdcard.sh script now supports both variants of the Bigtreetech SKR-3, STM32H743 and STM32H723. For this, the original tag of btt-skr-3 now has changed to be either btt-skr-3-h743 or btt-skr-3-h723.</p>
<p>20230729: The exported status for <code>dual_carriage</code> is changed. Instead of exporting <code>mode</code> and <code>active_carriage</code>, the individual modes for each carriage are exported as <code>printer.dual_carriage.carriage_0</code> and <code>printer.dual_carriage.carriage_1</code>.</p>
<p>20230619: The <code>relative_reference_index</code> option has been deprecated and superceded by the <code>zero_reference_position</code> option. Refer to the <a href="Bed_Mesh.html#the-deprecated-relative_reference_index">Bed Mesh Documentation</a> for details on how to update the configuration. With this deprecation the <code>RELATIVE_REFERENCE_INDEX</code> is no longer available as a parameter for the <code>BED_MESH_CALIBRATE</code> gcode command.</p>
<p>20230530: The default canbus frequency in "make menuconfig" is now 1000000. If using canbus and using canbus with some other frequency is required, then be sure to select "Enable extra low-level configuration options" and specify the desired "CAN bus speed" in "make menuconfig" when compiling and flashing the micro-controller.</p>
<p>20230525: <code>SHAPER_CALIBRATE</code> command immediately applies input shaper parameters if <code>[input_shaper]</code> was enabled already.</p>

View File

@@ -884,6 +884,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#lis2dw" class="md-nav__link">
[lis2dw]
</a>
</li>
<li class="md-nav__item">
@@ -966,6 +973,13 @@
[smart_effector]
</a>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
</li>
</ul>
@@ -1159,6 +1173,13 @@
Sensore di temperatura DS18B20
</a>
</li>
<li class="md-nav__item">
<a href="#combined-temperature-sensor" class="md-nav__link">
Combined temperature sensor
</a>
</li>
</ul>
@@ -1819,8 +1840,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -2352,8 +2373,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -2861,6 +2882,13 @@
[adxl345]
</a>
</li>
<li class="md-nav__item">
<a href="#lis2dw" class="md-nav__link">
[lis2dw]
</a>
</li>
<li class="md-nav__item">
@@ -2943,6 +2971,13 @@
[smart_effector]
</a>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
</li>
</ul>
@@ -3136,6 +3171,13 @@
Sensore di temperatura DS18B20
</a>
</li>
<li class="md-nav__item">
<a href="#combined-temperature-sensor" class="md-nav__link">
Combined temperature sensor
</a>
</li>
</ul>
@@ -5002,6 +5044,24 @@ cs_pin:
# measurements.
</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]
cs_pin:
# The SPI enable pin for the sensor. This parameter must be provided.
#spi_speed: 5000000
# The SPI speed (in hz) to use when communicating with the chip.
# The default is 5000000.
#spi_bus:
#spi_software_sclk_pin:
#spi_software_mosi_pin:
#spi_software_miso_pin:
# See the &quot;common SPI settings&quot; section for a description of the
# above parameters.
#axes_map: x, y, z
# See the &quot;adxl345&quot; section for information on this parameter.
</code></pre></div>
<h3 id="mpu9250">[mpu9250]<a class="headerlink" href="#mpu9250" title="Permanent link">&para;</a></h3>
<p>Supporto per accelerometri MPU-9250, MPU-9255, MPU-6515, MPU-6050 e MPU-6500 (è possibile definire un numero qualsiasi di sezioni con un prefisso "mpu9250").</p>
<div class="highlight"><pre><span></span><code>[mpu9250 my_accelerometer]
@@ -5262,6 +5322,30 @@ z_offset:
# Vedere la sezione &quot;probe&quot; per ulteriori informazioni sui parametri di cui sopra.
</code></pre></div>
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">&para;</a></h3>
<p>A tool to compensate for inaccurate probe readings due to twist in X gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
<div class="highlight"><pre><span></span><code>[axis_twist_compensation]
#speed: 50
# The speed (in mm/s) of non-probing moves during the calibration.
# The default is 50.
#horizontal_move_z: 5
# The height (in mm) that the head should be commanded to move to
# just prior to starting a probe operation. The default is 5.
calibrate_start_x: 20
# Defines the minimum X coordinate of the calibration
# This should be the X coordinate that positions the nozzle at the starting
# calibration position. This parameter must be provided.
calibrate_end_x: 200
# Defines the maximum X coordinate of the calibration
# This should be the X coordinate that positions the nozzle at the ending
# calibration position. This parameter must be provided.
calibrate_y: 112.5
# Defines the Y coordinate of the calibration
# This should be the Y coordinate that positions the nozzle during the
# calibration process. This parameter must be provided and is recommended to
# be near the center of the bed
</code></pre></div>
<h2 id="motori-passo-passo-ed-estrusori-aggiuntivi">Motori passo-passo ed estrusori aggiuntivi<a class="headerlink" href="#motori-passo-passo-ed-estrusori-aggiuntivi" title="Permanent link">&para;</a></h2>
<h3 id="stepper_z1">[stepper_z1]<a class="headerlink" href="#stepper_z1" title="Permanent link">&para;</a></h3>
<p>Assi multi-stepper. Su una stampante in stile cartesiano, lo stepper che controlla un dato asse può avere blocchi di configurazione aggiuntivi che definiscono gli stepper che dovrebbero essere azionati insieme allo stepper primario. Si può definire un numero qualsiasi di sezioni con un suffisso numerico che inizia da 1 (ad esempio, "stepper_z1", "stepper_z2", ecc.).</p>
@@ -5293,12 +5377,22 @@ z_offset:
</code></pre></div>
<h3 id="dual_carriage">[dual_carriage]<a class="headerlink" href="#dual_carriage" title="Permanent link">&para;</a></h3>
<p>Supporto per stampanti cartesiane con doppi carrelli su un unico asse. Il carrello attivo viene impostato tramite il comando G-code esteso SET_DUAL_CARRIAGE. Il comando "SET_DUAL_CARRIAGE CARRIAGE=1" attiverà il carrello definito in questa sezione (CARRIAGE=0 riporterà l'attivazione al carrello principale). Il supporto del doppio carrello è in genere combinato con estrusori extra: il comando SET_DUAL_CARRIAGE viene spesso chiamato contemporaneamente al comando ACTIVATE_EXTRUDER. Assicurati di parcheggiare i carrelli durante la disattivazione.</p>
<p>Support for cartesian and hybrid_corexy/z printers with dual carriages on a single axis. The carriage mode can be set via the SET_DUAL_CARRIAGE extended g-code command. For example, "SET_DUAL_CARRIAGE CARRIAGE=1" command will activate the carriage defined in this section (CARRIAGE=0 will return activation to the primary carriage). Dual carriage support is typically combined with extra extruders - the SET_DUAL_CARRIAGE command is often called at the same time as the ACTIVATE_EXTRUDER command. Be sure to park the carriages during deactivation. Note that during G28 homing, typically the primary carriage is homed first followed by the carriage defined in the <code>[dual_carriage]</code> config section. However, the <code>[dual_carriage]</code> carriage will be homed first if both carriages home in a positive direction and the [dual_carriage] carriage has a <code>position_endstop</code> greater than the primary carriage, or if both carriages home in a negative direction and the <code>[dual_carriage]</code> carriage has a <code>position_endstop</code> less than the primary carriage.</p>
<p>Additionally, one could use "SET_DUAL_CARRIAGE CARRIAGE=1 MODE=COPY" or "SET_DUAL_CARRIAGE CARRIAGE=1 MODE=MIRROR" commands to activate either copying or mirroring mode of the dual carriage, in which case it will follow the motion of the carriage 0 accordingly. These commands can be used to print two parts simultaneously - either two identical parts (in COPY mode) or mirrored parts (in MIRROR mode). Note that COPY and MIRROR modes also require appropriate configuration of the extruder on the dual carriage, which can typically be achieved with "SYNC_EXTRUDER_MOTION MOTION_QUEUE=extruder EXTRUDER=<dual_carriage_extruder>" or a similar command.</p>
<p>Vedere <a href="https://github.com/Klipper3d/klipper/blob/master/config/sample-idex.cfg">sample-idex.cfg</a> per un esempio di configurazione.</p>
<div class="highlight"><pre><span></span><code>[dual_carriage]
axis:
# L&#39;asse su cui si trova questo carrello aggiuntivo (x o y). Questo parametro
# deve essere fornito
# The axis this extra carriage is on (either x or y). This parameter
# must be provided.
#safe_distance:
# The minimum distance (in mm) to enforce between the dual and the primary
# carriages. If a G-Code command is executed that will bring the carriages
# closer than the specified limit, such a command will be rejected with an
# error. If safe_distance is not provided, it will be inferred from
# position_min and position_max for the dual and primary carriages. If set
# to 0 (or safe_distance is unset and position_min and position_max are
# identical for the primary and dual carraiges), the carriages proximity
# checks will be disabled.
#step_pin:
#dir_pin:
#enable_pin:
@@ -5308,7 +5402,7 @@ axis:
#position_endstop:
#position_min:
#position_max:
# Vedere la sezione &quot;stepper&quot; per la definizione dei parametri di cui sopra.
# See the &quot;stepper&quot; section for the definition of the above parameters.
</code></pre></div>
<h3 id="extruder_stepper">[extruder_stepper]<a class="headerlink" href="#extruder_stepper" title="Permanent link">&para;</a></h3>
@@ -5690,6 +5784,21 @@ serial_no:
# Il microcontrollore da cui leggere. Deve essere host_mcu
</code></pre></div>
<h3 id="combined-temperature-sensor">Combined temperature sensor<a class="headerlink" href="#combined-temperature-sensor" title="Permanent link">&para;</a></h3>
<p>Combined temperature sensor is a virtual temperature sensor based on several other sensors. This sensor can be used with extruders, heater_generic and heater beds.</p>
<div class="highlight"><pre><span></span><code>sensor_type: temperature_combined
#sensor_list:
# Must be provided. List of sensors to combine to new &quot;virtual&quot;
# sensor.
# E.g. &#39;temperature_sensor sensor1,extruder,heater_bed&#39;
#combination_method:
# Must be provided. Combination method used for the sensor.
# Available options are &#39;max&#39;, &#39;min&#39;, &#39;mean&#39;.
#maximum_deviation:
# Must be provided. Maximum permissible deviation between the sensors
# to combine (e.g. 5 degrees). To disable it, use a large value (e.g. 999.9)
</code></pre></div>
<h2 id="ventole">Ventole<a class="headerlink" href="#ventole" title="Permanent link">&para;</a></h2>
<h3 id="fan">[fan]<a class="headerlink" href="#fan" title="Permanent link">&para;</a></h3>
<p>Ventola di raffreddamento della stampa.</p>
@@ -6397,7 +6506,7 @@ run_current:
</code></pre></div>
<h3 id="tmc2240">[tmc2240]<a class="headerlink" href="#tmc2240" title="Permanent link">&para;</a></h3>
<p>Configurare un driver del motore passo-passo TMC2240 tramite bus SPI. Per utilizzare questa funzionalità, definire una sezione di configurazione con un prefisso "tmc2240" seguito dal nome della sezione di configurazione dello stepper corrispondente (ad esempio, "[tmc2240 stepper_x]").</p>
<p>Configure a TMC2240 stepper motor driver via SPI bus or UART. To use this feature, define a config section with a "tmc2240" prefix followed by the name of the corresponding stepper config section (for example, "[tmc2240 stepper_x]").</p>
<div class="highlight"><pre><span></span><code>[tmc2240 stepper_x]
cs_pin:
# The pin corresponding to the TMC2240 chip select line. This pin
@@ -6410,6 +6519,9 @@ cs_pin:
#spi_software_miso_pin:
# See the &quot;common SPI settings&quot; section for a description of the
# above parameters.
#uart_pin:
# The pin connected to the TMC2240 DIAG1/SW line. If this parameter
# is provided UART communication is used rather then SPI.
#chain_position:
#chain_length:
# These parameters configure an SPI daisy chain. The two parameters

View File

@@ -721,8 +721,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1254,8 +1254,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1449,31 +1449,28 @@
<p>Questo documento fornisce una lista di step per confermare le impostazioni dei pin nel file printer.cfg di Klipper. È una buona idea eseguire questi passi dopo aver seguito i passi nel <a href="Installation.html">documento di installazione</a>.</p>
<p>In alcuni passaggi di questa guida, potrebbe essere necessario modificare il file di configurazione di Klipper. Assicuratevi di dare il comando RESTART, dopo ogni modifica al file di configurazione, per accertarsi che le modifiche abbiano effetto(scrivere "restart" nella scheda del terminale di Octoprint e cliccare su INVIA). E' anche consigliabile utilizzare il comando STATUS, dopo ogni RESTART, per verificare che il file di configurazione sia stato caricato correttamente.</p>
<h2 id="verifica-delle-temperature">Verifica delle temperature<a class="headerlink" href="#verifica-delle-temperature" title="Permanent link">&para;</a></h2>
<p>Iniziare verificando che le temperature siano correttamente riportate. Navigare alla scheda temperature di Octoprint.</p>
<p>eseguire l'istruzione <img alt="octoprint-temperature" src="img/octoprint-temperature.png" /></p>
<p>Verificare che la temperatura dell'ugello e del piatto(se presente) siano presenti e non stiano aumentando. Se stessero aumentando staccare l'alimentazione alla stampante. Se le temperature non sono precise, rivedere le impostazioni "sensor_type" e "sensor_pin" per l'ugello e/o il piatto.</p>
<p>Start by verifying that temperatures are being properly reported. Navigate to the temperature graph section in the user interface. Verify that the temperature of the nozzle and bed (if applicable) are present and not increasing. If it is increasing, remove power from the printer. If the temperatures are not accurate, review the "sensor_type" and "sensor_pin" settings for the nozzle and/or bed.</p>
<h2 id="verifica-m112">Verifica M112<a class="headerlink" href="#verifica-m112" title="Permanent link">&para;</a></h2>
<p>Da terminale dare il comando M112. Questo comando richiede a Klipper di porsi in uno stato di spengnimento. Questo causerà la disconnessione di Octoprint da Klipper - selezionate il menu connessione e premete il pulsante "Connetti" per riconnettere Octoprint. Selezionate poi la scheda temperatura e verificate che le temperature si stiano aggiornando e che non stiano aumentando. Se stanno aumentando, staccate l'alimentazione della stampante.</p>
<p>Il comando M112 mette Klipper in uno stato di spegnimento. Per farlo uscire da questo stato, dare il comando FIRMWARE_RESTART sempre da terminale di Octoprint.</p>
<p>Navigate to the command console and issue an M112 command in the terminal box. This command requests Klipper to go into a "shutdown" state. It will cause an error to show, which can be cleared with a FIRMWARE_RESTART command in the command console. Octoprint will also require a reconnect. Then navigate to the temperature graph section and verify that temperatures continue to update and the temperatures are not increasing. If temperatures are increasing, remove power from the printer.</p>
<h2 id="verifica-i-riscaldatori">Verifica i riscaldatori<a class="headerlink" href="#verifica-i-riscaldatori" title="Permanent link">&para;</a></h2>
<p>Passare alla pagina della temperatura su Octoprint . Nella casella della temperatura "Tool", digitare 50 seguito dal tasto enter .La temperatura dell'estrusore indicata nel grafico, dovrebbe iniziare ad aumentare (entro 30 secondi circa). Quindi vai alla casella a scorrimento della temperatura "Tool" e seleziona "Off". Dopo alcuni minuti la temperatura dovrebbe tornare al valore di temperatura ambiente iniziale. Se la temperatura non aumenta, verifica l'impostazione "heater_pin" nella configurazione.</p>
<p>Navigate to the temperature graph section and type in 50 followed by enter in the extruder/tool temperature box. The extruder temperature in the graph should start to increase (within about 30 seconds or so). Then go to the extruder temperature drop-down box and select "Off". After several minutes the temperature should start to return to its initial room temperature value. If the temperature does not increase then verify the "heater_pin" setting in the config.</p>
<p>Se la stampante ha il piatto riscaldato, eseguire nuovamente il test indicato in precedenza ma per il piatto.</p>
<h2 id="verifica-il-pin-di-abilitazione-del-motore-passo-passo">Verifica il pin di abilitazione del motore passo-passo<a class="headerlink" href="#verifica-il-pin-di-abilitazione-del-motore-passo-passo" title="Permanent link">&para;</a></h2>
<p>Verificare che tutti gli assi della stampante possano muoversi manualmente in modo libero (con i motori passo-passo sono disabilitati). In caso contrario, inserire un comando M84 per disabilitare i motori. Se uno degli assi non può ancora muoversi in modo libero, verificare la configurazione "enable_pin" del driver del motore passo-passo corrispondente. Sulla maggior parte dei driver per motori passo-passo, il pin di abilitazione del motore è "attivo basso" e quindi il pin di abilitazione dovrebbe avere un "!" prima del pin (ad esempio, "enable_pin: !ar38").</p>
<p>Verify that all of the printer axes can manually move freely (the stepper motors are disabled). If not, issue an M84 command to disable the motors. If any of the axes still can not move freely, then verify the stepper "enable_pin" configuration for the given axis. On most commodity stepper motor drivers, the motor enable pin is "active low" and therefore the enable pin should have a "!" before the pin (for example, "enable_pin: !PA1").</p>
<h2 id="verifica-i-finecorsa">Verifica i finecorsa<a class="headerlink" href="#verifica-i-finecorsa" title="Permanent link">&para;</a></h2>
<p>Spostare manualmente tutti gli assi della stampante in modo che nessuno di essi sia a contatto con un finecorsa. Invia un comando QUERY_ENDSTOPS tramite il terminale di Octoprint. Dovrebbe visualizzare lo stato corrente di tutti i finecorsa configurati e gli stessi dovrebbero essere nello stato di "aperto". Per ciascuno degli finecorsa, eseguire nuovamente il comando QUERY_ENDSTOPS mentre si attiva manualmente il finecorsa corrispondente, dovrebbe rispondere con "TRIGGERED".</p>
<p>Se il finecorsa è invertito (viene indicato "aperto" quando è attivato e viceversa), aggiungere un "!" alla definizione del pin (ad esempio, "endstop_pin: ^!ar3"), oppure togliere "!" se invece è presente.</p>
<p>Manually move all the printer axes so that none of them are in contact with an endstop. Send a QUERY_ENDSTOPS command via the command console. It should respond with the current state of all of the configured endstops and they should all report a state of "open". For each of the endstops, rerun the QUERY_ENDSTOPS command while manually triggering the endstop. The QUERY_ENDSTOPS command should report the endstop as "TRIGGERED".</p>
<p>If the endstop appears inverted (it reports "open" when triggered and vice-versa) then add a "!" to the pin definition (for example, "endstop_pin: ^PA2"), or remove the "!" if there is already one present.</p>
<p>Se il segnale del finecorsa non cambia , può significare che il fine corsa è collegato a un pin diverso. Tuttavia, potrebbe essere necessaria una modifica all'impostazione pullup del pin (il '^' all'inizio del istruzione "endstop_pin".La maggior parte delle stampanti utilizzano un resistore pullup e l'istruzione '^' dovrebbe essere presente).</p>
<h2 id="verifica-dei-motori-passo-passo">Verifica dei motori passo-passo<a class="headerlink" href="#verifica-dei-motori-passo-passo" title="Permanent link">&para;</a></h2>
<p>Utilizzare il comando STEPPER_BUZZ per verificare le connessioni di ciascun motore passo-passo. Inizia posizionando manualmente in un punto intermedio dell'asse, quindi esegui l'istruzione <code>STEPPER_BUZZ STEPPER=stepper_x</code>. Il comando STEPPER_BUZZ farà muovere il motore passo-passo di un millimetro in direzione avanti e poi tornerà in posizione iniziale. (Se il finecorsa è definito come position_endstop=0, all'inizio di ogni movimento lo motore passo-passo si allontanerà dal finecorsa.) Eseguirà questa movimento oscillatorio per dieci volte.</p>
<p>Use the STEPPER_BUZZ command to verify the connectivity of each stepper motor. Start by manually positioning the given axis to a midway point and then run <code>STEPPER_BUZZ STEPPER=stepper_x</code> in the command console. The STEPPER_BUZZ command will cause the given stepper to move one millimeter in a positive direction and then it will return to its starting position. (If the endstop is defined at position_endstop=0 then at the start of each movement the stepper will move away from the endstop.) It will perform this oscillation ten times.</p>
<p>Se il motore passo-passo non si muove , verifica le impostazioni "enable_pin" e "step_pin" sul driver. Se il motore passo-passo si muove ma non torna nella sua posizione originale, verificare l'impostazione "dir_pin". Se il motore passo-passo oscilla in una direzione errata, generalmente sta a significare che è necessario invertire il "dir_pin" del l'asse. Questo viene fatto aggiungendo un istruzione '!' alla "dir_pin" nel file di configurazione della stampante (o rimuovendolo se ne esiste già presente). Se il motore passo-passo si muove di più o di meno di un millimetro, verificare l'impostazione "rotation_distance".</p>
<p>Eseguire il test sopra descritto per ogni motore passo-passo definito nel file di configurazione. (Impostare il parametro STEPPER del comando STEPPER_BUZZ sul nome della sezione di configurazione da testare.) Se non è presente il filamento nell'estrusore, è possibile utilizzare STEPPER_BUZZ per verificare la connessione del motore dell'estrusore (usare STEPPER=estrusore). In caso contrario, è meglio testare il motore dell'estrusore per conto suo (vedere la sezione successiva).</p>
<p>Dopo aver verificato tutti i finecorsa e aver verificato tutti i motori passo-passo, è necessario testare il sistema di homing. Scrivere un comando G28 per portare a home tutti gli assi. Rimuovere l'alimentazione dalla stampante se l'istruzione non funziona correttamente. Se necessario, ripetere i passaggi di verifica del finecorsa e del motore passo-passo.</p>
<h2 id="verifica-il-motore-dellestrusore">Verifica il motore dell'estrusore<a class="headerlink" href="#verifica-il-motore-dellestrusore" title="Permanent link">&para;</a></h2>
<p>Per testare il motore dell'estrusore sarà necessario riscaldare l'estrusore alla temperatura di stampa. Passare alla pagina della temperatura Octoprint e selezionare una temperatura di target nel menù a tendina della temperatura (o inserire manualmente una temperatura opportuna). Attendere che la stampante raggiunga la temperatura desiderata. Quindi vai alla pagina di controllo di Octoprint e fai clic sul pulsante "Estrudi". Verificare che il motore dell'estrusore giri nella direzione corretta. In caso contrario, vedere i suggerimenti per la risoluzione dei problemi nella sezione precedente per verificare le impostazioni "enable_pin", "step_pin" e "dir_pin" per l'estrusore.</p>
<p>To test the extruder motor it will be necessary to heat the extruder to a printing temperature. Navigate to the temperature graph section and select a target temperature from the temperature drop-down box (or manually enter an appropriate temperature). Wait for the printer to reach the desired temperature. Then navigate to the command console and click the "Extrude" button. Verify that the extruder motor turns in the correct direction. If it does not, see the troubleshooting tips in the previous section to confirm the "enable_pin", "step_pin", and "dir_pin" settings for the extruder.</p>
<h2 id="calibrare-le-impostazioni-del-pid">Calibrare le impostazioni del PID<a class="headerlink" href="#calibrare-le-impostazioni-del-pid" title="Permanent link">&para;</a></h2>
<p>Klipper supporta il sistema <a href="https://en.wikipedia.org/wiki/PID_controller">controllo PID</a> per iriscaldatori dell'estrusore e del piatto. Per utilizzare questo sistema di controllo, è necessario calibrare le impostazioni PID su ciascuna stampante (le impostazioni PID presenti in altri firmware o nei file di configurazione di esempio spesso funzionano male).</p>
<p>Per calibrare il PID dell'estrusore, accedere alla pagina del terminale OctoPrint ed eseguire il comando PID_CALIBRATE. Ad esempio: <code>PID_CALIBRATE HEATER=estrusore TARGET=170</code></p>
<p>To calibrate the extruder, navigate to the command console and run the PID_CALIBRATE command. For example: <code>PID_CALIBRATE HEATER=extruder TARGET=170</code></p>
<p>Al termine del test di ottimizzazione, eseguire l'istruzione <code>SAVE_CONFIG</code> per aggiornare il file printer.cfg con le nuove impostazioni PID.</p>
<p>Se la stampante ha un piatto riscaldato ed è dotato di azionamento con funzione PWM (Pulse Width Modulation), si consiglia di utilizzare il controllo PID anche per il piatto. (Quando il riscaldatore del piatto è controllato utilizzando l'algoritmo PID, potrebbe accendersi e spegnersi dieci volte al secondo, il che potrebbe non essere adatto per i riscaldatori che utilizzano un relè elettromeccanico.) Un tipico comando per calibrazione PID del piatto è: <code>PID_CALIBRATE HEATER=heater_bed TARGET= 60</code></p>
<h2 id="passi-sucessivi">Passi sucessivi<a class="headerlink" href="#passi-sucessivi" title="Permanent link">&para;</a></h2>

View File

@@ -712,8 +712,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1245,8 +1245,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1253,8 +1253,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -701,8 +701,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1234,8 +1234,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -680,8 +680,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1213,8 +1213,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1423,13 +1423,13 @@
<a href="Resonance_Compensation.html" class="md-footer__link md-footer__link--next" aria-label="Prossimo: Compensazione della risonanza" rel="next">
<a href="Axis_Twist_Compensation.html" class="md-footer__link md-footer__link--next" aria-label="Prossimo: Axis Twist Compensation" rel="next">
<div class="md-footer__title">
<div class="md-ellipsis">
<span class="md-footer__direction">
Prossimo
</span>
Compensazione della risonanza
Axis Twist Compensation
</div>
</div>
<div class="md-footer__button md-icon">

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1198,8 +1198,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1225,8 +1225,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -824,8 +824,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1357,8 +1357,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -670,8 +670,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1203,8 +1203,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1072,6 +1072,20 @@
SET_DUAL_CARRIAGE
</a>
</li>
<li class="md-nav__item">
<a href="#save_dual_carriage_state" class="md-nav__link">
SAVE_DUAL_CARRIAGE_STATE
</a>
</li>
<li class="md-nav__item">
<a href="#restore_dual_carriage_state" class="md-nav__link">
RESTORE_DUAL_CARRIAGE_STATE
</a>
</li>
</ul>
@@ -2248,6 +2262,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
<nav class="md-nav" aria-label="[axis_twist_compensation]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#axis_twist_compensation_calibrate" class="md-nav__link">
AXIS_TWIST_COMPENSATION_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -2733,8 +2767,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -3163,6 +3197,20 @@
SET_DUAL_CARRIAGE
</a>
</li>
<li class="md-nav__item">
<a href="#save_dual_carriage_state" class="md-nav__link">
SAVE_DUAL_CARRIAGE_STATE
</a>
</li>
<li class="md-nav__item">
<a href="#restore_dual_carriage_state" class="md-nav__link">
RESTORE_DUAL_CARRIAGE_STATE
</a>
</li>
</ul>
@@ -4339,6 +4387,26 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#axis_twist_compensation" class="md-nav__link">
[axis_twist_compensation]
</a>
<nav class="md-nav" aria-label="[axis_twist_compensation]">
<ul class="md-nav__list">
<li class="md-nav__item">
<a href="#axis_twist_compensation_calibrate" class="md-nav__link">
AXIS_TWIST_COMPENSATION_CALIBRATE
</a>
</li>
</ul>
</nav>
</li>
<li class="md-nav__item">
@@ -4522,7 +4590,11 @@
<h3 id="dual_carriage">[dual_carriage]<a class="headerlink" href="#dual_carriage" title="Permanent link">&para;</a></h3>
<p>Il comando seguente è disponibile quando la <a href="Config_Reference.html#dual_carriage">sezione di configurazione dual_carriage</a> è abilitata.</p>
<h4 id="set_dual_carriage">SET_DUAL_CARRIAGE<a class="headerlink" href="#set_dual_carriage" title="Permanent link">&para;</a></h4>
<p><code>SET_DUAL_CARRIAGE CARRIAGE=[0|1]</code>: Questo comando imposterà il carrello attivo. Viene in genere richiamato dai campi activate_gcode e deactivate_gcode in una configurazione a più estrusori.</p>
<p><code>SET_DUAL_CARRIAGE CARRIAGE=[0|1] [MODE=[PRIMARY|COPY|MIRROR]]</code>: This command will change the mode of the specified carriage. If no <code>MODE</code> is provided it defaults to <code>PRIMARY</code>. Setting the mode to <code>PRIMARY</code> deactivates the other carriage and makes the specified carriage execute subsequent G-Code commands as-is. <code>COPY</code> and <code>MIRROR</code> modes are supported only for <code>CARRIAGE=1</code>. When set to either of these modes, carriage 1 will then track the subsequent moves of the carriage 0 and either copy relative movements of it (in <code>COPY</code> mode) or execute them in the opposite (mirror) direction (in <code>MIRROR</code> mode).</p>
<h4 id="save_dual_carriage_state">SAVE_DUAL_CARRIAGE_STATE<a class="headerlink" href="#save_dual_carriage_state" title="Permanent link">&para;</a></h4>
<p><code>SAVE_DUAL_CARRIAGE_STATE [NAME=&lt;state_name&gt;]</code>: Save the current positions of the dual carriages and their modes. Saving and restoring DUAL_CARRIAGE state can be useful in scripts and macros, as well as in homing routine overrides. If NAME is provided it allows one to name the saved state to the given string. If NAME is not provided it defaults to "default".</p>
<h4 id="restore_dual_carriage_state">RESTORE_DUAL_CARRIAGE_STATE<a class="headerlink" href="#restore_dual_carriage_state" title="Permanent link">&para;</a></h4>
<p><code>RESTORE_DUAL_CARRIAGE_STATE [NAME=&lt;state_name&gt;] [MOVE=[0|1] [MOVE_SPEED=&lt;speed&gt;]]</code>: Restore the previously saved positions of the dual carriages and their modes, unless "MOVE=0" is specified, in which case only the saved modes will be restored, but not the positions of the carriages. If positions are being restored and "MOVE_SPEED" is specified, then the toolhead moves will be performed with the given speed (in mm/s); otherwise the toolhead move will use the rail homing speed. Note that the carriages restore their positions only over their own axis, which may be necessary to correctly restore COPY and MIRROR mode of the dual carraige.</p>
<h3 id="endstop_phase">[endstop_phase]<a class="headerlink" href="#endstop_phase" title="Permanent link">&para;</a></h3>
<p>I seguenti comandi sono disponibili quando una <a href="Config_Reference.html#endstop_phase">sezione di configurazione endstop_phase</a> è abilitata (consultare anche la <a href="Endstop_Phase.html">guida alla fase endstop</a>).</p>
<h4 id="endstop_phase_calibrate">ENDSTOP_PHASE_CALIBRATE<a class="headerlink" href="#endstop_phase_calibrate" title="Permanent link">&para;</a></h4>
@@ -4849,6 +4921,11 @@
<p><code>SDCARD_PRINT_FILE FILENAME=&lt;nomefile&gt;</code>: carica un file e avvia la stampa SD.</p>
<h4 id="sdcard_reset_file">SDCARD_RESET_FILE<a class="headerlink" href="#sdcard_reset_file" title="Permanent link">&para;</a></h4>
<p><code>SDCARD_RESET_FILE</code>: Scarica il file e cancella lo stato SD.</p>
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">&para;</a></h3>
<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 [SAMPLE_COUNT=&lt;value&gt;]</code>: Initiates the X twist calibration wizard. <code>SAMPLE_COUNT</code> specifies the number of points along the X axis to calibrate at and defaults to 3.</p>
<h3 id="z_thermal_adjust">[z_thermal_adjust]<a class="headerlink" href="#z_thermal_adjust" title="Permanent link">&para;</a></h3>
<p>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#z_thermal_adjust">sezione z_thermal_adjust config</a> è abilitata.</p>
<h4 id="set_z_thermal_adjust">SET_Z_THERMAL_ADJUST<a class="headerlink" href="#set_z_thermal_adjust" title="Permanent link">&para;</a></h4>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1157,8 +1157,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -693,8 +693,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1226,8 +1226,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1280,8 +1280,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1252,8 +1252,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -694,8 +694,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1227,8 +1227,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -862,6 +862,13 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#configure-lis2dw-series" class="md-nav__link">
Configure LIS2DW series
</a>
</li>
<li class="md-nav__item">
@@ -1450,8 +1457,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1703,6 +1710,13 @@
</ul>
</nav>
</li>
<li class="md-nav__item">
<a href="#configure-lis2dw-series" class="md-nav__link">
Configure LIS2DW series
</a>
</li>
<li class="md-nav__item">
@@ -1836,9 +1850,9 @@
<h1 id="misurazione-delle-risonanze">Misurazione delle risonanze<a class="headerlink" href="#misurazione-delle-risonanze" title="Permanent link">&para;</a></h1>
<p>Klipper has built-in support for the ADXL345 and MPU-9250 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.</p>
<p>Klipper has built-in support for the ADXL345, MPU-9250 and LIS2DW compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345/LIS2DW can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper.</p>
<p>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 ADXL345s/LIS2DWs, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
<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>
@@ -2182,6 +2196,24 @@ pin: adxl:gpio23
</code></pre></div>
<p>Riavvia Klipper tramite il comando <code>RESTART</code>.</p>
<h4 id="configure-lis2dw-series">Configure LIS2DW series<a class="headerlink" href="#configure-lis2dw-series" title="Permanent link">&para;</a></h4>
<div class="highlight"><pre><span></span><code>[mcu lis]
# Change &lt;mySerial&gt; to whatever you found above. For example,
# usb-Klipper_rp2040_E661640843545B2E-if00
serial: /dev/serial/by-id/usb-Klipper_rp2040_&lt;mySerial&gt;
[lis2dw]
cs_pin: lis:gpio1
spi_bus: spi0a
axes_map: x,z,y
[resonance_tester]
accel_chip: lis2dw
probe_points:
# Somewhere slightly above the middle of your print bed
147,154, 20
</code></pre></div>
<h4 id="configura-la-serie-mpu-60009000-con-rpi">Configura la serie MPU-6000/9000 con RPi<a class="headerlink" href="#configura-la-serie-mpu-60009000-con-rpi" title="Permanent link">&para;</a></h4>
<p>Assicurati che il driver Linux I2C sia abilitato e che la velocità di trasmissione sia impostata su 400000 (consulta la sezione <a href="RPi_microcontroller.html#optional-enabling-i2c">Abilitazione di I2C</a> per ulteriori dettagli). Quindi, aggiungi quanto segue a printer.cfg:</p>
<div class="highlight"><pre><span></span><code>[mcu rpi]

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1167,8 +1167,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -617,8 +617,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1150,8 +1150,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -684,8 +684,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1217,8 +1217,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1398,6 +1398,7 @@
<li><a href="Manual_Level.html">Livello manuale</a>: Calibrazione dei finecorsa Z (e simili).</li>
<li><a href="Bed_Mesh.html">Maglia del letto</a>: Correzione dell'altezza del piatto basata sulle posizioni XY.</li>
<li><a href="Endstop_Phase.html">Endstop phase</a>: Posizionamento finecorsa Z assistito da stepper.</li>
<li><a href="Axis_Twist_Compensation.html">Axis Twist Compensation</a>: A tool to compensate for inaccurate probe readings due to twist in X gantry.</li>
</ul>
</li>
<li><a href="Resonance_Compensation.html">Compensazione della risonanza</a>: Uno strumento per ridurre le risonanze nelle stampe.<ul>
@@ -1437,6 +1438,7 @@
<li><a href="RPi_microcontroller.html">Raspberry Pi come microcontrollore</a>: Dettagli per controllare i dispositivi collegati ai pin GPIO di un Raspberry Pi.</li>
<li><a href="beaglebone.md">Beaglebone</a>: Dettagli per l'esecuzione di Klipper sulla PRU Beaglebone.</li>
<li><a href="Bootloaders.html">Bootloaders</a>: Informazioni per gli sviluppatori sul flashing del microcontrollore.</li>
<li><a href="Bootloader_Entry.html">Bootloader Entry</a>: Requesting the bootloader.</li>
<li><a href="CANBUS.html">CAN bus</a>: Informazioni sull'uso del CAN bus con Klipper.<ul>
<li><a href="CANBUS_Troubleshooting.html">CAN bus troubleshooting</a>: Tips for troubleshooting CAN bus.</li>
</ul>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1219,8 +1219,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1205,8 +1205,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -695,8 +695,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1228,8 +1228,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1306,8 +1306,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1247,8 +1247,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1561,21 +1561,40 @@ gpiochip1 - 8 lines:
dtoverlay=pwm,pin=12,func=4
</code></pre></div>
<p>Questo esempio abilita solo PWM0 e lo indirizza a gpio12. Se entrambi i canali PWM devono essere abilitati potete usare <code>pwm-2chan</code>.</p>
<p>L'overlay non espone la riga pwm sui sysfs all'avvio e deve essere esportata facendo eco al numero del canale pwm in <code>/sys/class/pwm/pwmchip0/export</code>:</p>
<div class="highlight"><pre><span></span><code>echo 0 &gt; /sys/class/pwm/pwmchip0/export
<p>This example enables only PWM0 and routes it to gpio12. If both PWM channels need to be enabled you can use <code>pwm-2chan</code>:</p>
<div class="highlight"><pre><span></span><code># Enable pwmchip sysfs interface
dtoverlay=pwm-2chan,pin=12,func=4,pin2=13,func2=4
</code></pre></div>
<p>This example additionally enables PWM1 and routes it to gpio13.</p>
<p>The overlay does not expose the pwm line on sysfs on boot and needs to be exported by echo'ing the number of the pwm channel to <code>/sys/class/pwm/pwmchip0/export</code>. This will create device <code>/sys/class/pwm/pwmchip0/pwm0</code> in the filesystem. The easiest way to do this is by adding this to <code>/etc/rc.local</code> before the <code>exit 0</code> line:</p>
<div class="highlight"><pre><span></span><code># Enable pwmchip sysfs interface
echo 0 &gt; /sys/class/pwm/pwmchip0/export
</code></pre></div>
<p>When using both PWM channels, the number of the second channel needs to be echo'd as well:</p>
<div class="highlight"><pre><span></span><code># Enable pwmchip sysfs interface
echo 0 &gt; /sys/class/pwm/pwmchip0/export
echo 1 &gt; /sys/class/pwm/pwmchip0/export
</code></pre></div>
<p>Questo creerà il dispositivo <code>/sys/class/pwm/pwmchip0/pwm0</code> nel filesystem. Il modo più semplice per farlo è aggiungerlo a <code>/etc/rc.local</code> prima della riga <code>exit 0</code>.</p>
<p>Con il sysfs a posto, potete ora utilizzare il canale o i canali pwm aggiungendo il seguente pezzo di configurazione al vostro <code>printer.cfg</code>:</p>
<div class="highlight"><pre><span></span><code>[output_pin caselight]
pin: host:pwmchip0/pwm0
pwm: True
hardware_pwm: True
cycle_time: 0.000001
[output_pin beeper]
pin: host:pwmchip0/pwm1
pwm: True
hardware_pwm: True
value: 0
shutdown_value: 0
cycle_time: 0.0005
</code></pre></div>
<p>Questo aggiungerà il controllo pwm hardware a gpio12 sul Pi (perché l'overlay è stato configurato per instradare pwm0 a pin = 12).</p>
<p>This will add hardware pwm control to gpio12 and gpio13 on the Pi (because the overlay was configured to route pwm0 to pin=12 and pwm1 to pin=13).</p>
<p>PWM0 può essere indirizzato su gpio12 e gpio18, PWM1 può essere indirizzato su gpio13 e gpio19:</p>
<table>
<thead>

View File

@@ -739,8 +739,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1272,8 +1272,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1323,8 +1323,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1748,12 +1748,21 @@ shaper_type: 2hump_ei
<h3 id="dopo-aver-stampato-correttamente-per-un-po-di-tempo-senza-ringing-sembra-tornare">Dopo aver stampato correttamente per un po' di tempo senza ringing, sembra tornare<a class="headerlink" href="#dopo-aver-stampato-correttamente-per-un-po-di-tempo-senza-ringing-sembra-tornare" title="Permanent link">&para;</a></h3>
<p>È possibile che dopo qualche tempo le frequenze di risonanza siano cambiate. Per esempio. forse la tensione delle cinghie è cambiata (le cinghie si sono allentate di più), ecc. È una buona idea controllare e rimisurare le frequenze di ringing come descritto nella sezione <a href="#ringing-frequency">Frequenza di ringing</a> e aggiornare il file di configurazione se necessario .</p>
<h3 id="la-configurazione-a-doppio-carrello-e-supportata-con-gli-input-shaper">La configurazione a doppio carrello è supportata con gli input shaper?<a class="headerlink" href="#la-configurazione-a-doppio-carrello-e-supportata-con-gli-input-shaper" title="Permanent link">&para;</a></h3>
<p>Non esiste un supporto dedicato per doppi carrelli con input shaper, ma ciò non significa che questa configurazione non funzionerà. Si dovrebbe eseguire la messa a punto due volte per ciascuno dei carrelli e calcolare le frequenze di ringing per gli assi X e Y per ciascuno dei carrelli in modo indipendente. Quindi inserisci i valori per il carrello 0 nella sezione [input_shaper] e modifica i valori al volo quando si cambiano i carrelli, ad es. come parte di alcune macro:</p>
<div class="highlight"><pre><span></span><code>SET_DUAL_CARRIAGE CARRIAGE=1
SET_INPUT_SHAPER SHAPER_FREQ_X=... SHAPER_FREQ_Y=...
<p>Yes. In this case, one should measure the resonances twice for each carriage. For example, if the second (dual) carriage is installed on X axis, it is possible to set different input shapers for X axis for the primary and dual carriages. However, the input shaper for Y axis should be the same for both carriages (as ultimately this axis is driven by one or more stepper motors each commanded to perform exactly the same steps). One possibility to configure the input shaper for such setups is to keep <code>[input_shaper]</code> section empty and additionally define a <code>[delayed_gcode]</code> section in the <code>printer.cfg</code> as follows:</p>
<div class="highlight"><pre><span></span><code>[input_shaper]
# Intentionally empty
[delayed_gcode init_shaper]
initial_duration: 0.1
gcode:
SET_DUAL_CARRIAGE CARRIAGE=1
SET_INPUT_SHAPER SHAPER_TYPE_X=&lt;dual_carriage_shaper&gt; SHAPER_FREQ_X=&lt;dual_carriage_freq&gt; SHAPER_TYPE_Y=&lt;y_shaper&gt; SHAPER_FREQ_Y=&lt;y_freq&gt;
SET_DUAL_CARRIAGE CARRIAGE=0
SET_INPUT_SHAPER SHAPER_TYPE_X=&lt;primary_carriage_shaper&gt; SHAPER_FREQ_X=&lt;primary_carriage_freq&gt; SHAPER_TYPE_Y=&lt;y_shaper&gt; SHAPER_FREQ_Y=&lt;y_freq&gt;
</code></pre></div>
<p>E allo stesso modo quando si torna al carrello 0.</p>
<p>Note that <code>SHAPER_TYPE_Y</code> and <code>SHAPER_FREQ_Y</code> should be the same in both commands. It is also possible to put a similar snippet into the start g-code in the slicer, however then the shaper will not be enabled until any print is started.</p>
<p>Note that the input shaper only needs to be configured once. Subsequent changes of the carriages or their modes via <code>SET_DUAL_CARRIAGE</code> command will preserve the configured input shaper parameters.</p>
<h3 id="linput_shaper-influisce-sul-tempo-di-stampa">L'input_shaper influisce sul tempo di stampa?<a class="headerlink" href="#linput_shaper-influisce-sul-tempo-di-stampa" title="Permanent link">&para;</a></h3>
<p>No, la funzione <code>input_shaper</code> non ha praticamente alcun impatto sui tempi di stampa da sola. Tuttavia, il valore di <code>max_accel</code> lo fa certamente (regolazione di questo parametro descritta in <a href="#selecting-max_accel">questa sezione</a>).</p>
<h2 id="dettagli-tecnici">Dettagli tecnici<a class="headerlink" href="#dettagli-tecnici" title="Permanent link">&para;</a></h2>
@@ -1834,7 +1843,7 @@ SET_INPUT_SHAPER SHAPER_FREQ_X=... SHAPER_FREQ_Y=...
<nav class="md-footer__inner md-grid" aria-label="Piede">
<a href="Endstop_Phase.html" class="md-footer__link md-footer__link--prev" aria-label="Precedente: Fase di fine corsa" rel="prev">
<a href="Axis_Twist_Compensation.html" class="md-footer__link md-footer__link--prev" aria-label="Precedente: Axis Twist Compensation" 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>
@@ -1843,7 +1852,7 @@ SET_INPUT_SHAPER SHAPER_FREQ_X=... SHAPER_FREQ_Y=...
<span class="md-footer__direction">
Precedente
</span>
Fase di fine corsa
Axis Twist Compensation
</div>
</div>
</a>

View File

@@ -715,8 +715,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1248,8 +1248,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1253,8 +1253,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1226,8 +1226,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1247,8 +1247,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1155,8 +1155,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -1416,10 +1416,10 @@
<h1 id="sponsors">Sponsors<a class="headerlink" href="#sponsors" title="Permanent link">&para;</a></h1>
<p>Klipper è un software libero. Dipendiamo dal generoso supporto degli sponsor. Considera la possibilità di sponsorizzare Klipper o di supportare i nostri sponsor.</p>
<h2 id="bigtreetech">BIGTREETECH<a class="headerlink" href="#bigtreetech" title="Permanent link">&para;</a></h2>
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" /></a></p>
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" style="margin:25px"/></a></p>
<p>BIGTREETECH è lo sponsor ufficiale della scheda madre di Klipper. BIGTREETECH si impegna a sviluppare prodotti innovativi e competitivi per servire meglio la comunità della stampa 3D. Seguili su <a href="https://www.facebook.com/BIGTREETECH">Facebook</a> o <a href="https://twitter.com/BigTreeTech">Twitter</a>.</p>
<h2 id="sponsors_1">Sponsors<a class="headerlink" href="#sponsors_1" title="Permanent link">&para;</a></h2>
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" /></a></p>
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a> <a href="https://peopoly.net"><img src="./img/sponsors/peopoly-logo.png" width="200" style="margin:25px" /></a></p>
<h2 id="sviluppatori-klipper">Sviluppatori Klipper<a class="headerlink" href="#sviluppatori-klipper" title="Permanent link">&para;</a></h2>
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">&para;</a></h3>
<p>Kevin è l'autore originale e l'attuale manutentore di Klipper. Fai una donazione su: <a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> o <a href="https://www.patreon.com/koconnor">https://www.patreon.com/koconnor</a></p>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1501,8 +1501,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>
@@ -2086,6 +2086,7 @@
<ul>
<li><code>disponibili_riscaldatori</code>: restituisce un elenco di tutti i riscaldatori attualmente disponibili in base ai nomi completi delle sezioni di configurazione, ad es. <code>["extruder", "heater_bed", "heater_generic my_custom_heater"]</code>.</li>
<li><code>available_sensors</code>: restituisce un elenco di tutti i riscaldatori attualmente disponibili in base ai nomi completi delle sezioni di configurazione, ad es. <code>["extruder", "heater_bed", "heater_generic my_custom_heater"]</code>.</li>
<li><code>available_monitors</code>: Returns a list of all currently available temperature monitors by their full config section names, e.g. <code>["tmc2240 stepper_x"]</code>. While a temperature sensor is always available to read, a temperature monitor may not be available and will return null in such case.</li>
</ul>
<h2 id="idle_timeout">idle_timeout<a class="headerlink" href="#idle_timeout" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili nell'oggetto <a href="Config_Reference.html#idle_timeout">idle_timeout</a> (questo oggetto è sempre disponibile):</p>
@@ -2166,6 +2167,7 @@
<p>Le seguenti informazioni sono disponibili nell'oggetto <code>screws_tilt_adjust</code>:</p>
<ul>
<li><code>error</code>: restituisce True se il comando <code>SCREWS_TILT_CALCULATE</code> più recente includeva il parametro <code>MAX_DEVIATION</code> e uno qualsiasi dei punti della vite rilevati superava il <code>MAX_DEVIATION</code> specificato.</li>
<li><code>max_deviation</code>: Return the last <code>MAX_DEVIATION</code> value of the most recent <code>SCREWS_TILT_CALCULATE</code> command.</li>
<li><code>results["&lt;screw&gt;"]</code>: un dizionario contenente le seguenti chiavi:<ul>
<li><code>z</code>: L'altezza Z misurata della posizione della vite.</li>
<li><code>sign</code>: una stringa che specifica la direzione in cui ruotare la vite per la regolazione necessaria. O "CW" per senso orario o "CCW" per senso antiorario.</li>
@@ -2191,7 +2193,7 @@
</ul>
<h2 id="sensori-di-temperatura">sensori di temperatura<a class="headerlink" href="#sensori-di-temperatura" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili in</p>
<p><a href="Config_Reference.html#bmp280bme280bme680-temperature-sensor">bme280 config_section_name</a>, <a href="Config_Reference.html#htu21d-sensor">htu21d config_section_name</a>, <a href="Config_Reference.html#lm75-temperature-sensor">lm75 config_section_name</a> e <a href="Config_Reference.html#host-temperature-sensor">temperature_host config_section_name </a>:</p>
<p><a href="Config_Reference.html#bmp280bme280bme680-temperature-sensor">bme280 config_section_name</a>, <a href="Config_Reference.html#htu21d-sensor">htu21d config_section_name</a>, <a href="Config_Reference.html#lm75-temperature-sensor">lm75 config_section_name</a>, <a href="Config_Reference.html#host-temperature-sensor">temperature_host config_section_name</a> and <a href="Config_Reference.html#combined-temperature-sensor">temperature_combined config_section_name</a> objects:</p>
<ul>
<li><code>temperature</code>: l'ultima temperatura letta dal sensore.</li>
<li><code>humidity</code>, <code>pressure</code>, <code>gas</code>: gli ultimi valori letti dal sensore (solo sui sensori bme280, htu21d e lm75).</li>
@@ -2230,10 +2232,10 @@
<li><code>stalls</code>: il numero totale di volte (dall'ultimo riavvio) che la stampante ha dovuto essere messa in pausa perché la testina si muoveva più velocemente di quanto fosse possibile leggere i movimenti dall'input del G-code.</li>
</ul>
<h2 id="dual_carriage">dual_carriage<a class="headerlink" href="#dual_carriage" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili in <a href="Config_Reference.html#dual_carriage">dual_carriage</a> su una macchina hybrid_corexy o hybrid_corexz</p>
<p>The following information is available in <a href="Config_Reference.html#dual_carriage">dual_carriage</a> on a cartesian, hybrid_corexy or hybrid_corexz robot</p>
<ul>
<li><code>mode</code>: la modalità corrente. I valori possibili sono: "FULL_CONTROL"</li>
<li><code>active_carriage</code>: il carrello attivo corrente. I valori possibili sono: "CARRIAGE_0", "CARRIAGE_1"</li>
<li><code>carriage_0</code>: The mode of the carriage 0. Possible values are: "INACTIVE" and "PRIMARY".</li>
<li><code>carriage_1</code>: The mode of the carriage 1. Possible values are: "INACTIVE", "PRIMARY", "COPY", and "MIRROR".</li>
</ul>
<h2 id="virtual_sdcard">virtual_sdcard<a class="headerlink" href="#virtual_sdcard" title="Permanent link">&para;</a></h2>
<p>Le seguenti informazioni sono disponibili nell'oggetto <a href="Config_Reference.html#virtual_sdcard">virtual_sdcard</a>:</p>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1404,8 +1404,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -622,8 +622,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1157,8 +1157,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -624,8 +624,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1219,8 +1219,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

View File

@@ -619,8 +619,8 @@
<li class="md-nav__item">
<a href="Axis_Twist_Compensation.md" class="md-nav__link">
None
<a href="Axis_Twist_Compensation.html" class="md-nav__link">
Axis Twist Compensation
</a>
</li>
@@ -1152,8 +1152,8 @@
<li class="md-nav__item">
<a href="Bootloader_Entry.md" class="md-nav__link">
None
<a href="Bootloader_Entry.html" class="md-nav__link">
Bootloader Entry
</a>
</li>

File diff suppressed because one or more lines are too long

View File

@@ -2,257 +2,267 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-22</lastmod>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
<lastmod>2023-10-23</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>

Binary file not shown.