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

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

Browse Source
This commit is contained in:
KevinOConnor
2025-01-17 00:05:15 +00:00
parent ab5d75e656
commit 624e1f941a
83 changed files with 3167 additions and 1149 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
it/Measuring_Resonances.html
View File

@@ -912,8 +912,8 @@
</li>
<li class="md-nav__item">
<a href="#configure-lis2dw-series" class="md-nav__link">
Configure LIS2DW series
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
Configure LIS2DW series over SPI
</a>
</li>
@@ -990,6 +990,13 @@
Seleziona max_accel
</a>
</li>
<li class="md-nav__item">
<a href="#unreliable-measurements-of-resonance-frequencies" class="md-nav__link">
Unreliable measurements of resonance frequencies
</a>
</li>
<li class="md-nav__item">
@@ -1774,8 +1781,8 @@
</li>
<li class="md-nav__item">
<a href="#configure-lis2dw-series" class="md-nav__link">
Configure LIS2DW series
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
Configure LIS2DW series over SPI
</a>
</li>
@@ -1852,6 +1859,13 @@
Seleziona max_accel
</a>
</li>
<li class="md-nav__item">
<a href="#unreliable-measurements-of-resonance-frequencies" class="md-nav__link">
Unreliable measurements of resonance frequencies
</a>
</li>
<li class="md-nav__item">
@@ -1911,10 +1925,10 @@
<h1 id="misurazione-delle-risonanze">Misurazione delle risonanze<a class="headerlink" href="#misurazione-delle-risonanze" title="Permanent link">&para;</a></h1>
<p>Klipper has built-in support for the ADXL345, MPU-9250 and LIS2DW compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345/LIS2DW can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper.</p>
<p>Klipper has built-in support for the ADXL345, MPU-9250, LIS2DW and LIS3DH compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345 can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper. The LIS2DW and LIS3DH can be connected to either SPI or I2C with the same considerations as above.</p>
<p>When sourcing accelerometers, be aware that there are a variety of different PCB board designs and different clones of them. If it is going to be connected to a 5V printer MCU ensure it has a voltage regulator and level shifters.</p>
<p>For ADXL345s/LIS2DWs, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
<p>For ADXL345s, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s and LIS2DW/LIS3DH there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
<h2 id="mcus-with-klipper-i2c-fast-mode-support">MCUs with Klipper I2C <em>fast-mode</em> Support<a class="headerlink" href="#mcus-with-klipper-i2c-fast-mode-support" title="Permanent link">&para;</a></h2>
<table>
<thead>
@@ -1940,6 +1954,11 @@
<td align="left">-</td>
<td align="left">AT90usb646, AT90usb1286</td>
</tr>
<tr>
<td align="center">SAMD</td>
<td align="left">SAMC21G18</td>
<td align="left">SAMC21G18, SAMD21G18, SAMD21E18, SAMD21J18, SAMD21E15, SAMD51G19, SAMD51J19, SAMD51N19, SAMD51P20, SAME51J19, SAME51N19, SAME54P20</td>
</tr>
</tbody>
</table>
<h2 id="istruzioni-per-linstallazione">Istruzioni per l'installazione<a class="headerlink" href="#istruzioni-per-linstallazione" title="Permanent link">&para;</a></h2>
@@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
</code></pre></div>
<p>Quindi, per installare NumPy nell'ambiente Klipper, esegui il comando:</p>
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v numpy
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v &quot;numpy&lt;1.26&quot;
</code></pre></div>
<p>Nota che, a seconda delle prestazioni della CPU, potrebbe volerci <em>molto</em> tempo, fino a 10-20 minuti. Sii paziente e attendi il completamento dell'installazione. In alcune occasioni, se la scheda ha poca RAM, l'installazione potrebbe non riuscire e sarà necessario abilitare la swap.</p>
<p>Note that, depending on the performance of the CPU, it may take <em>a lot</em> of time, up to 10-20 minutes. Be patient and wait for the completion of the installation. On some occasions, if the board has too little RAM the installation may fail and you will need to enable swap. Also note the forced version, due to newer versions of NumPY having requirements that may not be satisfied in some klipper python environments.</p>
<p>Once installed please check that no errors show from the command:</p>
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/python -c &#39;import numpy;&#39;
</code></pre></div>
<p>The correct output should simply be a new line.</p>
<h4 id="configura-adxl345-con-rpi">Configura ADXL345 con RPi<a class="headerlink" href="#configura-adxl345-con-rpi" title="Permanent link">&para;</a></h4>
<p>First, check and follow the instructions in the <a href="RPi_microcontroller.html">RPi Microcontroller document</a> to setup the "linux mcu" on the Raspberry Pi. This will configure a second Klipper instance that runs on your Pi.</p>
<p>Assicurati che il driver SPI di Linux sia abilitato eseguendo <code>sudo raspi-config</code> e abilitando SPI nel menu "Opzioni di interfaccia".</p>
@@ -2257,7 +2281,7 @@ pin: adxl:gpio23
</code></pre></div>
<p>Riavvia Klipper tramite il comando <code>RESTART</code>.</p>
<h4 id="configure-lis2dw-series">Configure LIS2DW series<a class="headerlink" href="#configure-lis2dw-series" title="Permanent link">&para;</a></h4>
<h4 id="configure-lis2dw-series-over-spi">Configure LIS2DW series over SPI<a class="headerlink" href="#configure-lis2dw-series-over-spi" title="Permanent link">&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
@@ -2482,6 +2506,8 @@ max_smoothing: 0.25 # un esempio
<p>so that it can calculate the maximum acceleration recommendations correctly. Note that the <code>SHAPER_CALIBRATE</code> command already takes the configured <code>square_corner_velocity</code> parameter into account, and there is no need to specify it explicitly.</p>
<p>Se stai eseguendo una ricalibrazione dello shaper e lo smoothing riportato per la configurazione dello shaper suggerita è quasi lo stesso di quello ottenuto durante la calibrazione precedente, questo passaggio può essere saltato.</p>
<h3 id="unreliable-measurements-of-resonance-frequencies">Unreliable measurements of resonance frequencies<a class="headerlink" href="#unreliable-measurements-of-resonance-frequencies" title="Permanent link">&para;</a></h3>
<p>Sometimes the resonance measurements can produce bogus results, leading to the incorrect suggestions for the input shapers. This can be caused by a variety of reasons, including running fans on the toolhead, incorrect position or non-rigid mounting of the accelerometer, or mechanical problems such as loose belts or binding or bumpy axis. Keep in mind that all fans should be disabled for resonance testing, especially the noisy ones, and that the accelerometer should be rigidly mounted on the corresponding moving part (e.g. on the bed itself for the bed slinger, or on the extruder of the printer itself and not the carriage, and some people get better results by mounting the accelerometer on the nozzle itself). As for mechanical problems, the user should inspect if there is any fault that can be fixed with a moving axis (e.g. linear guide rails cleaned up and lubricated and V-slot wheels tension adjusted correctly). If none of that helps, a user may try the other shapers from the produced list besides the one recommended by default.</p>
<h3 id="test-di-assi-personalizzati">Test di assi personalizzati<a class="headerlink" href="#test-di-assi-personalizzati" title="Permanent link">&para;</a></h3>
<p>Il comando <code>TEST_RESONANCES</code> supporta assi personalizzati. Anche se questo non è molto utile per la calibrazione del input shaper, può essere utilizzato per studiare in profondità le risonanze della stampante e per controllare, ad esempio, la tensione della cinghia.</p>
<p>Per controllare la tensione della cinghia sulle stampanti CoreXY, eseguire</p>