Deploying to gh-pages from @ Klipper3d/klipper@cf3b0475da 🚀
This commit is contained in:
KevinOConnor
@@ -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 @@
|
||||
Sélection de 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 @@
|
||||
Sélection de 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="mesurer-la-resonance">Mesurer la résonance<a class="headerlink" href="#mesurer-la-resonance" title="Permanent link">¶</a></h1>
|
||||
<p>Klipper has built-in support for the ADXL345, MPU-9250 and LIS2DW compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345/LIS2DW can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper.</p>
|
||||
<p>Klipper has built-in support for the ADXL345, MPU-9250, LIS2DW and LIS3DH compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345 can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper. The LIS2DW and LIS3DH can be connected to either SPI or I2C with the same considerations as above.</p>
|
||||
<p>When sourcing accelerometers, be aware that there are a variety of different PCB board designs and different clones of them. If it is going to be connected to a 5V printer MCU ensure it has a voltage regulator and level shifters.</p>
|
||||
<p>For ADXL345s/LIS2DWs, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
|
||||
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
|
||||
<p>For ADXL345s, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
|
||||
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s and LIS2DW/LIS3DH there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
|
||||
<h2 id="mcus-with-klipper-i2c-fast-mode-support">MCUs with Klipper I2C <em>fast-mode</em> Support<a class="headerlink" href="#mcus-with-klipper-i2c-fast-mode-support" title="Permanent link">¶</a></h2>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -1940,6 +1954,11 @@
|
||||
<td align="left">-</td>
|
||||
<td align="left">AT90usb646, AT90usb1286</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center">SAMD</td>
|
||||
<td align="left">SAMC21G18</td>
|
||||
<td align="left">SAMC21G18, SAMD21G18, SAMD21E18, SAMD21J18, SAMD21E15, SAMD51G19, SAMD51J19, SAMD51N19, SAMD51P20, SAME51J19, SAME51N19, SAME54P20</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="instructions-dinstallation">Instructions d’installation<a class="headerlink" href="#instructions-dinstallation" title="Permanent link">¶</a></h2>
|
||||
@@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
|
||||
</code></pre></div>
|
||||
|
||||
<p>Ensuite, pour installer NumPy dans l’environnement Klipper, exécutez la commande :</p>
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v numpy
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v "numpy<1.26"
|
||||
</code></pre></div>
|
||||
|
||||
<p>Selon les performances du processeur, cette opération peut prendre jusqu’à 20 minutes. Soyez patient et attendez la fin de l’installation. Dans certains cas, si la carte a trop peu de mémoire, l’installation peut échouer et vous devrez activer le fichier d’échange.</p>
|
||||
<p>Note that, depending on the performance of the CPU, it may take <em>a lot</em> of time, up to 10-20 minutes. Be patient and wait for the completion of the installation. On some occasions, if the board has too little RAM the installation may fail and you will need to enable swap. Also note the forced version, due to newer versions of NumPY having requirements that may not be satisfied in some klipper python environments.</p>
|
||||
<p>Once installed please check that no errors show from the command:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/python -c 'import numpy;'
|
||||
</code></pre></div>
|
||||
|
||||
<p>The correct output should simply be a new line.</p>
|
||||
<h4 id="configurer-ladxl345-avec-le-rpi">Configurer l'ADXL345 avec le RPi<a class="headerlink" href="#configurer-ladxl345-avec-le-rpi" title="Permanent link">¶</a></h4>
|
||||
<p>First, check and follow the instructions in the <a href="RPi_microcontroller.html">RPi Microcontroller document</a> to setup the "linux mcu" on the Raspberry Pi. This will configure a second Klipper instance that runs on your Pi.</p>
|
||||
<p>Assurez-vous que le pilote SPI Linux est activé en exécutant <code>sudo raspi-config</code> et en activant SPI dans le menu « Options d’interface ».</p>
|
||||
@@ -2257,7 +2281,7 @@ pin: adxl:gpio23
|
||||
</code></pre></div>
|
||||
|
||||
<p>Redémarrez Klipper avec la commande <code>RESTART</code>.</p>
|
||||
<h4 id="configure-lis2dw-series">Configure LIS2DW series<a class="headerlink" href="#configure-lis2dw-series" title="Permanent link">¶</a></h4>
|
||||
<h4 id="configure-lis2dw-series-over-spi">Configure LIS2DW series over SPI<a class="headerlink" href="#configure-lis2dw-series-over-spi" title="Permanent link">¶</a></h4>
|
||||
<div class="highlight"><pre><span></span><code>[mcu lis]
|
||||
# Change <mySerial> to whatever you found above. For example,
|
||||
# usb-Klipper_rp2040_E661640843545B2E-if00
|
||||
@@ -2482,6 +2506,8 @@ max_smoothing: 0.25 # valeur exemple
|
||||
|
||||
<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>Si vous effectuez un ré-étalonnage du formateur d'entrée et que le lissage indiqué pour la configuration de formateur suggérée est pratiquement le même que celui obtenu lors du calibrage précédent, cette étape peut être ignorée.</p>
|
||||
<h3 id="unreliable-measurements-of-resonance-frequencies">Unreliable measurements of resonance frequencies<a class="headerlink" href="#unreliable-measurements-of-resonance-frequencies" title="Permanent link">¶</a></h3>
|
||||
<p>Sometimes the resonance measurements can produce bogus results, leading to the incorrect suggestions for the input shapers. This can be caused by a variety of reasons, including running fans on the toolhead, incorrect position or non-rigid mounting of the accelerometer, or mechanical problems such as loose belts or binding or bumpy axis. Keep in mind that all fans should be disabled for resonance testing, especially the noisy ones, and that the accelerometer should be rigidly mounted on the corresponding moving part (e.g. on the bed itself for the bed slinger, or on the extruder of the printer itself and not the carriage, and some people get better results by mounting the accelerometer on the nozzle itself). As for mechanical problems, the user should inspect if there is any fault that can be fixed with a moving axis (e.g. linear guide rails cleaned up and lubricated and V-slot wheels tension adjusted correctly). If none of that helps, a user may try the other shapers from the produced list besides the one recommended by default.</p>
|
||||
<h3 id="test-des-axes-personnalises">Test des axes personnalisés<a class="headerlink" href="#test-des-axes-personnalises" title="Permanent link">¶</a></h3>
|
||||
<p>la commande <code>TEST_RESONANCES</code> prend en charge les axes personnalisés. Bien que cela ne soit pas vraiment utile pour l’étalonnage des input shaper, cela peut être utilisé pour étudier en profondeur les résonances de l’imprimante et vérifier, par exemple, la tension de la courroie.</p>
|
||||
<p>Pour vérifier la tension de la courroie sur les imprimantes CoreXY, exécutez</p>
|
||||
|
||||
Reference in New Issue
Block a user