mirror of
https://github.com/Klipper3d/klipper.git
synced 2025-07-17 19:57:57 -06:00
Deploying to gh-pages from @ Klipper3d/klipper@cf3b0475da 🚀
This commit is contained in:
KevinOConnor
parent
ab5d75e656
commit
624e1f941a
83 changed files with 3167 additions and 1149 deletions
Binary file not shown.
|
|
@ -711,6 +711,33 @@
|
|||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1384,6 +1411,33 @@
|
|||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1420,19 +1474,43 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
|
|||
<blockquote>
|
||||
<p><strong>Tip:</strong> Make sure the <a href="Config_Reference.html#probe">probe X and Y offsets</a> are correctly set as they greatly influence calibration.</p>
|
||||
</blockquote>
|
||||
<h3 id="basic-usage-x-axis-calibration">Basic Usage: X-Axis Calibration<a class="headerlink" href="#basic-usage-x-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<ol>
|
||||
<li>Après avoir configuré le module [axis_twist_compensation], effectuez <code>AXIS_TWIST_COMPENSATION_CALIBRATE</code></li>
|
||||
<li>After setting up the <code>[axis_twist_compensation]</code> module, run:</li>
|
||||
</ol>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE
|
||||
</code></pre></div>
|
||||
|
||||
<p>This command will calibrate the X-axis by default. - The calibration wizard will prompt you to measure the probe Z offset at several points along the bed. - By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=<value></code></p>
|
||||
<ol>
|
||||
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).</li>
|
||||
<li>
|
||||
<p><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</p>
|
||||
<ul>
|
||||
<li>L'assistant de calibration vous invitera à calibrer la sonde de l'axe Z à quelques emplacements sur le plateau</li>
|
||||
<li>L'étalonnage est par défaut de 3 points mais vous pouvez utiliser l'option <code>SAMPLE_COUNT=</code> pour utiliser un nombre différent.</li>
|
||||
<li><a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a></li>
|
||||
<li><a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a></li>
|
||||
</ul>
|
||||
<ol>
|
||||
<li><a href="Probe_Calibrate.html#calibrating-probe-z-offset">Ajustez votre décalage de l'axe Z</a></li>
|
||||
<li>Perform automatic/probe-based bed tramming operations, such as <a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a>, <a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a> etc</li>
|
||||
<li>Home all axis, then perform a <a href="Bed_Mesh.html">Bed Mesh</a> if required</li>
|
||||
<li>Effectuez un test d'impression, suivi d'un <a href="Axis_Twist_Compensation.html#fine-tuning">réglage de précision</a> comme vous le souhaitez</li>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Finalize the Setup:</strong></p>
|
||||
<ul>
|
||||
<li>Home all axes, and perform a <a href="Bed_Mesh.html">Bed Mesh</a> if necessary.</li>
|
||||
<li>Run a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> if needed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h3 id="for-y-axis-calibration">For Y-Axis Calibration<a class="headerlink" href="#for-y-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<p>The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y
|
||||
</code></pre></div>
|
||||
|
||||
<p>This will guide you through the same measuring process as for the X-axis.</p>
|
||||
<h3 id="automatic-calibration-for-both-axes">Automatic Calibration for Both Axes<a class="headerlink" href="#automatic-calibration-for-both-axes" title="Permanent link">¶</a></h3>
|
||||
<p>To perform automatic calibration for both the X and Y axes without manual intervention, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
|
||||
</code></pre></div>
|
||||
|
||||
<p>In this mode, the calibration process will run for both axes automatically.</p>
|
||||
<blockquote>
|
||||
<p><strong>Conseil :</strong> La température du plateau ainsi que la température et la taille de la buse ne semblent pas avoir d'influence sur le processus de calibration.</p>
|
||||
</blockquote>
|
||||
|
|
|
|||
|
|
@ -1968,7 +1968,7 @@ fade_target: 0
|
|||
<li><code>fade_target : 0</code> <em>Valeur par défaut : la valeur Z moyenne du maillage</em> Le <code>fade_target</code> peut être considéré comme un décalage Z supplémentaire appliqué à l'ensemble du lit une fois l'interpolation terminée . L'idéal serait d'avoir cette valeur à 0, mais il y a des circonstances où elle ne peut pas l'être. Par exemple, supposons que votre position de référence sur le lit est une valeur aberrante, 0,2 mm inférieure à la hauteur moyenne sondée du lit. Si le <code>fade_target</code> est 0, le fondu réduira l'impression de 0,2 mm en moyenne sur le lit. En réglant <code>fade_target</code> sur 0,2, la zone référencée s'agrandira de 0,2 mm, cependant, le reste du lit sera dimensionné avec précision. Généralement, c'est une bonne idée de laisser <code>fade_target</code> hors de la configuration afin que la hauteur moyenne du maillage soit utilisée, cependant il peut être souhaitable d'ajuster manuellement cette valeur si l'on veut imprimer sur une partie spécifique du lit.</li>
|
||||
</ul>
|
||||
<h3 id="configuration-de-la-position-dorigine">Configuration de la position d'origine<a class="headerlink" href="#configuration-de-la-position-dorigine" title="Permanent link">¶</a></h3>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="./Manual_Level#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="Manual_Level.html#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<div class="highlight"><pre><span></span><code>[bed_mesh]
|
||||
speed: 120
|
||||
horizontal_move_z: 5
|
||||
|
|
|
|||
|
|
@ -1195,6 +1195,13 @@
|
|||
Test du taux de pas sur SAMD51
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1205,8 +1212,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#test-du-taux-de-pas-sur-rp2040" class="md-nav__link">
|
||||
Test du taux de pas sur RP2040
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1613,6 +1620,13 @@
|
|||
Test du taux de pas sur SAMD51
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1623,8 +1637,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#test-du-taux-de-pas-sur-rp2040" class="md-nav__link">
|
||||
Test du taux de pas sur RP2040
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -2122,6 +2136,34 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="same70-step-rate-benchmark">SAME70 step rate benchmark<a class="headerlink" href="#same70-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the SAME70:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=PC18 dir_pin=PB5 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=PC16 dir_pin=PD10 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=2 step_pin=PC28 dir_pin=PA4 invert_step=-1 step_pulse_ticks=0
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>34e9ea55</code> with gcc version <code>arm-none-eabi-gcc (NixOS 10.3-2021.10) 10.3.1</code> on a SAME70Q20B micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>same70</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1 moteur pas à pas</td>
|
||||
<td>45</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 moteurs pas à pas</td>
|
||||
<td>190</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="test-du-taux-de-pas-de-lar100">Test du taux de pas de l'AR100<a class="headerlink" href="#test-du-taux-de-pas-de-lar100" title="Permanent link">¶</a></h3>
|
||||
<p>La séquence de configuration suivante est utilisée sur le processeur AR100 (Allwinner A64) :</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2131,7 +2173,7 @@ config_stepper oid=2 step_pin=PL12 dir_pin=PE16 invert_step=-1 step_pulse_ticks=
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>Le test a été exécuté pour la dernière fois sur le commit <code>08d037c6</code> avec la version de gcc <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> sur un microcontrôleur Allwinner A64-H.</p>
|
||||
<p>The test was last run on commit <code>b7978d37</code> with gcc version <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> on an Allwinner A64-H micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -2150,8 +2192,8 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="test-du-taux-de-pas-sur-rp2040">Test du taux de pas sur RP2040<a class="headerlink" href="#test-du-taux-de-pas-sur-rp2040" title="Permanent link">¶</a></h3>
|
||||
<p>La séquence de configuration suivante est utilisée sur le RP2040 :</p>
|
||||
<h3 id="rpxxxx-step-rate-benchmark">RPxxxx step rate benchmark<a class="headerlink" href="#rpxxxx-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040 and RP2350:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=gpio25 dir_pin=gpio3 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=gpio26 dir_pin=gpio4 invert_step=-1 step_pulse_ticks=0
|
||||
|
|
@ -2159,11 +2201,11 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>Le test a été exécuté pour la dernière fois sur le commit <code>59314d99</code> avec la version gcc <code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code> sur une carte Raspberry Pi Pico.</p>
|
||||
<p>The test was last run on commit <code>f6718291</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2040</th>
|
||||
<th>rp2040 (*)</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
|
@ -2178,6 +2220,25 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2350</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1 moteur pas à pas</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 moteurs pas à pas</td>
|
||||
<td>169</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 125Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM core cycles.</p>
|
||||
<h3 id="test-du-taux-de-pas-pour-le-mcu-linux">Test du taux de pas pour le MCU Linux<a class="headerlink" href="#test-du-taux-de-pas-pour-le-mcu-linux" title="Permanent link">¶</a></h3>
|
||||
<p>La séquence de configuration suivante est utilisée sur un Raspberry Pi :</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2311,9 +2372,15 @@ get_uptime
|
|||
</tr>
|
||||
<tr>
|
||||
<td>rp2040 (USB)</td>
|
||||
<td>873K</td>
|
||||
<td>c5667193</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2350 (USB)</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
|
|||
|
|
@ -1580,7 +1580,7 @@
|
|||
<li>Passez en revue les classes cinématiques existantes dans le répertoire klippy/kinematics/. Les classes cinématiques sont chargées de convertir le mouvement en coordonnées cartésiennes en un mouvement sur chaque moteur. On devrait être capable de copier un de ces fichiers comme point de départ.</li>
|
||||
<li>Implémentez les fonctions de position cinématique du moteur en C pour chaque moteur si elles ne sont pas déjà disponibles (voir kin_cart.c, kin_corexy.c, et kin_delta.c dans klippy/chelper/). La fonction doit appeler <code>move_get_coord()</code> pour convertir une durée de déplacement donnée (en secondes) en coordonnées cartésiennes (en millimètres), et ensuite calculer la position souhaitée du moteur (en millimètres) à partir de ces coordonnées cartésiennes.</li>
|
||||
<li>Implémentez la méthode <code>calc_position()</code> dans la nouvelle classe cinématique. Cette méthode calcule la position de la tête de l'outil en coordonnées cartésiennes à partir de la position de chaque moteur. Elle n'a pas besoin d'être efficace car elle n'est typiquement appelée que pendant les opérations de mise à l'origine et de palpage.</li>
|
||||
<li>Autres méthodes. Implémentez les méthodes <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, et <code>set_position()</code>. Ces fonctions sont typiquement utilisées pour fournir des vérifications spécifiques à la cinématique. Cependant, au début du développement, on peut utiliser du code passe-partout ici.</li>
|
||||
<li>Other methods. Implement the <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>clear_homing_state()</code>, and <code>set_position()</code> methods. These functions are typically used to provide kinematic specific checks. However, at the start of development one can use boiler-plate code here.</li>
|
||||
<li>Implémenter des cas de test. Créez un fichier g-code avec une série de mouvements pouvant tester des cas importants pour la cinématique donnée. Suivez la <a href="Debugging.html">documentation de débogage</a> pour convertir ce fichier g-code en commandes de micro-contrôleur. Ceci est utile pour tester les cas extrêmes et vérifier les régressions.</li>
|
||||
</ol>
|
||||
<h2 id="portage-sur-un-nouveau-microcontroleur">Portage sur un nouveau microcontrôleur<a class="headerlink" href="#portage-sur-un-nouveau-microcontroleur" title="Permanent link">¶</a></h2>
|
||||
|
|
|
|||
|
|
@ -1396,6 +1396,11 @@
|
|||
<p>Ce document couvre les modifications logicielles apportées au fichier de configuration qui ne sont pas rétro compatibles. Il est conseillé de consulter ce document lors de la mise à jour du logiciel Klipper.</p>
|
||||
<p>Toutes les dates de ce document sont approximatives.</p>
|
||||
<h2 id="changements">Changements<a class="headerlink" href="#changements" title="Permanent link">¶</a></h2>
|
||||
<p>20241203: The resonance test has been changed to include slow sweeping moves. This change requires that testing point(s) have some clearance in X/Y plane (+/- 30 mm from the test point should suffice when using the default settings). The new test should generally produce more accurate and reliable test results. However, if required, the previous test behavior can be restored by adding options <code>sweeping_period: 0</code> and <code>accel_per_hz: 75</code> to the <code>[resonance_tester]</code> config section.</p>
|
||||
<p>20241201: In some cases Klipper may have ignored leading characters or spaces in a traditional G-Code command. For example, "99M123" may have been interpreted as "M123" and "M 321" may have been interpreted as "M321". Klipper will now report these cases with an "Unknown command" warning.</p>
|
||||
<p>20241112: Option <code>CHIPS=<chip_name></code> in <code>TEST_RESONANCES</code> and <code>SHAPER_CALIBRATE</code> requires specifying the full name(s) of the accel chip(s). For example, <code>adxl345 rpi</code> instead of short name - <code>rpi</code>.</p>
|
||||
<p>20240912: <code>SET_PIN</code>, <code>SET_SERVO</code>, <code>SET_FAN_SPEED</code>, <code>M106</code>, and <code>M107</code> commands are now collated. Previously, if many updates to the same object were issued faster than the minimum scheduling time (typically 100ms) then actual updates could be queued far into the future. Now if many updates are issued in rapid succession then it is possible that only the latest request will be applied. If the previous behavior is requried then consider adding explicit <code>G4</code> delay commands between updates.</p>
|
||||
<p>20240912: Support for <code>maximum_mcu_duration</code> and <code>static_value</code> parameters in <code>[output_pin]</code> config sections have been removed. These options have been deprecated since 20240123.</p>
|
||||
<p>20240415: The <code>on_error_gcode</code> parameter in the <code>[virtual_sdcard]</code> config section now has a default. If this parameter is not specified it now defaults to <code>TURN_OFF_HEATERS</code>. If the previous behavior is desired (take no default action on an error during a virtual_sdcard print) then define <code>on_error_gcode</code> with an empty value.</p>
|
||||
<p>20240313: The <code>max_accel_to_decel</code> parameter in the <code>[printer]</code> config section has been deprecated. The <code>ACCEL_TO_DECEL</code> parameter of the <code>SET_VELOCITY_LIMIT</code> command has been deprecated. The <code>printer.toolhead.max_accel_to_decel</code> status has been removed. Use the <a href="Config_Reference.html#printer">minimum_cruise_ratio parameter</a> instead. The deprecated features will be removed in the near future, and using them in the interim may result in subtly different behavior.</p>
|
||||
<p>20240215: Several deprecated features have been removed. Using "NTC 100K beta 3950" as a thermistor name has been removed (deprecated on 20211110). The <code>SYNC_STEPPER_TO_EXTRUDER</code> and <code>SET_EXTRUDER_STEP_DISTANCE</code> commands have been removed, and the extruder <code>shared_heater</code> config option has been removed (deprecated on 20220210). The bed_mesh <code>relative_reference_index</code> option has been removed (deprecated on 20230619).</p>
|
||||
|
|
|
|||
|
|
@ -938,6 +938,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1188,8 +1195,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#bmp180bmp280bme280bmp388bme680-temperature-sensor" class="md-nav__link">
|
||||
BMP180/BMP280/BME280/BMP388/BME680 temperature sensor
|
||||
<a href="#capteur-de-temperature-bmp180bmp280bme280bmp388bme680" class="md-nav__link">
|
||||
Capteur de température BMP180/BMP280/BME280/BMP388/BME680
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1244,8 +1251,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#combined-temperature-sensor" class="md-nav__link">
|
||||
Combined temperature sensor
|
||||
<a href="#capteur-de-temperature-combine" class="md-nav__link">
|
||||
Capteur de température combiné
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1537,6 +1544,13 @@
|
|||
écran hd44780_spi
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1654,11 +1668,11 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#load-cells" class="md-nav__link">
|
||||
Load Cells
|
||||
<a href="#cellules-de-charge" class="md-nav__link">
|
||||
Cellules de charge
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Load Cells">
|
||||
<nav class="md-nav" aria-label="Cellules de charge">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1670,8 +1684,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -3032,6 +3046,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3282,8 +3303,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#bmp180bmp280bme280bmp388bme680-temperature-sensor" class="md-nav__link">
|
||||
BMP180/BMP280/BME280/BMP388/BME680 temperature sensor
|
||||
<a href="#capteur-de-temperature-bmp180bmp280bme280bmp388bme680" class="md-nav__link">
|
||||
Capteur de température BMP180/BMP280/BME280/BMP388/BME680
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -3338,8 +3359,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#combined-temperature-sensor" class="md-nav__link">
|
||||
Combined temperature sensor
|
||||
<a href="#capteur-de-temperature-combine" class="md-nav__link">
|
||||
Capteur de température combiné
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -3631,6 +3652,13 @@
|
|||
écran hd44780_spi
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3748,11 +3776,11 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#load-cells" class="md-nav__link">
|
||||
Load Cells
|
||||
<a href="#cellules-de-charge" class="md-nav__link">
|
||||
Cellules de charge
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Load Cells">
|
||||
<nav class="md-nav" aria-label="Cellules de charge">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3764,8 +3792,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -5245,8 +5273,9 @@ cs_pin :
|
|||
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS2DW accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis2dw]
|
||||
cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
|
|
@ -5256,6 +5285,43 @@ cs_pin:
|
|||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="lis3dh">[lis3dh]<a class="headerlink" href="#lis3dh" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS3DH accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis3dh]
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
|
@ -5280,43 +5346,58 @@ cs_pin:
|
|||
<p>Prise en charge du test de résonance et du calibrage automatique du façonneur d'entrée (input shaper). Pour utiliser la plupart des fonctionnalités de ce module, des dépendances logicielles supplémentaires doivent être installées ; reportez-vous à <a href="Measuring_Resonances.html">Mesurer les résonances</a> et à la <a href="G-Codes.html#resonance_tester">référence de commande</a> pour plus d'informations. Voir la section <a href="Measuring_Resonances.html#max-smoothing">Adoucissement Max</a> du guide de mesure des résonances pour plus d'informations sur le paramètre <code>max_smoothing</code> et son utilisation.</p>
|
||||
<div class="highlight"><pre><span></span><code>[resonance_tester]
|
||||
#probe_points:
|
||||
# Une liste de coordonnées X, Y, Z de points (un point par ligne) à tester.
|
||||
# Au moins un point est requis. Assurez-vous que tous les points avec une certaine marge
|
||||
# de sécurité dans le plan XY (~ quelques centimètres) sont accessibles par la tête de l'outil.
|
||||
# A list of X, Y, Z coordinates of points (one point per line) to test
|
||||
# resonances at. At least one point is required. Make sure that all
|
||||
# points with some safety margin in XY plane (~a few centimeters)
|
||||
# are reachable by the toolhead.
|
||||
#accel_chip:
|
||||
# Nom de la puce d'accéléromètre à utiliser pour les mesures. Si la puce adxl345 a été définie
|
||||
# sans un nom explicite, ce paramètre peut simplement la référencer en tant que
|
||||
# "accel_chip : adxl345", sinon un nom explicite doit être fourni, par exemple
|
||||
# "accel_chip : adxl345 my_chip_name". Soit ce paramètre seul, soit les deux paramètres
|
||||
# suivants doivent être définis.
|
||||
# A name of the accelerometer chip to use for measurements. If
|
||||
# adxl345 chip was defined without an explicit name, this parameter
|
||||
# can simply reference it as "accel_chip: adxl345", otherwise an
|
||||
# explicit name must be supplied as well, e.g. "accel_chip: adxl345
|
||||
# my_chip_name". Either this, or the next two parameters must be
|
||||
# set.
|
||||
#accel_chip_x:
|
||||
#accel_chip_y:
|
||||
# Noms des puces d'accéléromètre à utiliser pour les mesures de chaque axe.
|
||||
# Peut être utile, par exemple, sur une imprimante de type "bed slinger", si deux accéléromètres
|
||||
# séparés sont montés, un sur le lit (pour l'axe Y), l'autre sur la tête de l'outil (pour l'axe X).
|
||||
# Ces paramètres ont le même format que le paramètre 'accel_chip'. Soit le paramètre
|
||||
# 'accel_chip' soit ces deux paramètres doivent être fournis.
|
||||
# Names of the accelerometer chips to use for measurements for each
|
||||
# of the axis. Can be useful, for instance, on bed slinger printer,
|
||||
# if two separate accelerometers are mounted on the bed (for Y axis)
|
||||
# and on the toolhead (for X axis). These parameters have the same
|
||||
# format as 'accel_chip' parameter. Only 'accel_chip' or these two
|
||||
# parameters must be provided.
|
||||
#max_smoothing:
|
||||
# Lissage maximal du façonneur (shaper) d'entrée à autoriser pour chaque axe pendant
|
||||
# l'auto-calibration (avec la commande 'SHAPER_CALIBRATE'). Par défaut, aucun lissage
|
||||
# maximal n'est spécifié. Reportez-vous au guide Measuring_Resonances pour plus de détails
|
||||
# sur l'utilisation de cette fonction.
|
||||
# Maximum input shaper smoothing to allow for each axis during shaper
|
||||
# auto-calibration (with 'SHAPER_CALIBRATE' command). By default no
|
||||
# maximum smoothing is specified. Refer to Measuring_Resonances guide
|
||||
# for more details on using this feature.
|
||||
#move_speed: 50
|
||||
# The speed (in mm/s) to move the toolhead to and between test points
|
||||
# during the calibration. The default is 50.
|
||||
#min_freq: 5
|
||||
# Fréquence minimale de test des résonances. La valeur par défaut est 5 Hz.
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 133.33
|
||||
# Fréquence maximale de test des résonances. La valeur par défaut est 133,33 Hz.
|
||||
#accel_per_hz: 75
|
||||
# Ce paramètre permet de déterminer l'accélération à utiliser pour tester une fréquence
|
||||
# spécifique: accel = accel_per_hz * freq. Plus haute est cette valeur, plus l'énergie des
|
||||
# oscillations est élevée. Peut être fixé à une valeur inférieure à celle par défaut si les
|
||||
# résonances deviennent trop fortes sur l'imprimante. Cependant, des valeurs plus faibles
|
||||
# rendent les mesures des résonances à haute fréquence moins précises. La valeur par
|
||||
# défaut est de 75 (mm/sec).
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 60
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
# value, the higher is the energy of the oscillations. Can be set to
|
||||
# a lower than the default value if the resonances get too strong on
|
||||
# the printer. However, lower values make measurements of
|
||||
# high-frequency resonances less precise. The default value is 75
|
||||
# (mm/sec).
|
||||
#hz_per_sec: 1
|
||||
# Détermine la vitesse de l'essai. Lors du test de toutes les fréquences dans la plage [min_freq,
|
||||
# max_freq], chaque seconde, la fréquence augmente de hz_per_sec.
|
||||
# De faibles valeurs rendent le test lent, de grandes valeurs diminueront la précision du test.
|
||||
# La valeur par défaut est 1.0 (Hz/sec == sec^-2).
|
||||
# Determines the speed of the test. When testing all frequencies in
|
||||
# range [min_freq, max_freq], each second the frequency increases by
|
||||
# hz_per_sec. Small values make the test slow, and the large values
|
||||
# will decrease the precision of the test. The default value is 1.0
|
||||
# (Hz/sec == sec^-2).
|
||||
#sweeping_accel: 400
|
||||
# An acceleration of slow sweeping moves. The default is 400 mm/sec^2.
|
||||
#sweeping_period: 1.2
|
||||
# A period of slow sweeping moves. Setting this parameter to 0
|
||||
# disables slow sweeping moves. Avoid setting it to a too small
|
||||
# non-zero value in order to not poison the measurements.
|
||||
# The default is 1.2 sec which is a good all-round choice.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="assistants-de-fichiers-de-configuration">Assistants de fichiers de configuration<a class="headerlink" href="#assistants-de-fichiers-de-configuration" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5539,27 +5620,44 @@ sensor_type: ldc1612
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">¶</a></h3>
|
||||
<p>Un outil pour compenser les lectures inexactes de la sonde en raison de la torsion de la structure en X. Voir le <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> pour des informations plus détaillées sur les symptômes, la configuration et la mise en service.</p>
|
||||
<p>A tool to compensate for inaccurate probe readings due to twist in X or Y gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
|
||||
<div class="highlight"><pre><span></span><code>[axis_twist_compensation]
|
||||
#speed: 50
|
||||
# Vitesse (en mm/s) des déplacements sans mesures pendant l'étape d'étalonnage.
|
||||
# La valeur par défaut est de 50.
|
||||
# The speed (in mm/s) of non-probing moves during the calibration.
|
||||
# The default is 50.
|
||||
#horizontal_move_z: 5
|
||||
# La hauteur (en mm) à laquelle la tête doit se positionner
|
||||
# avant de commencer une mesure. La valeur par défaut est de 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
|
||||
# Définit la coordonnée minimum en X pour les mesures
|
||||
# Ce doit être la coordonnée X qui positionne la buse à la position de
|
||||
# départ des mesures. Ce paramètre est obligatoire.
|
||||
# Defines the minimum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the starting
|
||||
# calibration position.
|
||||
calibrate_end_x: 200
|
||||
# Définit la coordonnée maximum en X pour les mesures
|
||||
# Ce doit être la coordonnée X qui positionne la buse à la position de
|
||||
# fin des mesures. Ce paramètre est obligatoire.
|
||||
# Defines the maximum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the ending
|
||||
# calibration position.
|
||||
calibrate_y: 112.5
|
||||
# Définit la coordonnée Y de mesure
|
||||
# Ce doit être la coordonnée Y qui positionne la buse à la position de
|
||||
# mesures. Ce paramètre est obligatoire et il est conseillé de mettre une mesure
|
||||
# proche du centre du plateau
|
||||
# Defines the Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle during the
|
||||
# calibration process. This parameter is recommended to
|
||||
# be near the center of the bed
|
||||
|
||||
# For Y-axis twist compensation, specify the following parameters:
|
||||
calibrate_start_y: ...
|
||||
# Defines the minimum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the starting
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_end_y: ...
|
||||
# Defines the maximum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the ending
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_x: ...
|
||||
# Defines the X coordinate of the calibration for Y axis twist compensation
|
||||
# This should be the X coordinate that positions the nozzle during the
|
||||
# calibration process for Y axis twist compensation. This parameter must be
|
||||
# provided and is recommended to be near the center of the bed.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="moteurs-pas-a-pas-et-extrudeurs-additionnels">Moteurs pas à pas et extrudeurs additionnels<a class="headerlink" href="#moteurs-pas-a-pas-et-extrudeurs-additionnels" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5841,6 +5939,10 @@ extruder:
|
|||
# "calibration_extruder_temp" option is set. Its recommended to heat
|
||||
# the extruder some distance from the bed to minimize its impact on
|
||||
# the probe coil temperature. The default is 50.
|
||||
#max_validation_temp: 60.
|
||||
# The maximum temperature used to validate the calibration. It is
|
||||
# recommended to set this to a value between 100 and 120 for enclosed
|
||||
# printers. The default is 60.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="capteurs-de-temperature">Capteurs de température<a class="headerlink" href="#capteurs-de-temperature" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5920,7 +6022,7 @@ sensor_pin:
|
|||
# dans la liste ci-dessus.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="bmp180bmp280bme280bmp388bme680-temperature-sensor">BMP180/BMP280/BME280/BMP388/BME680 temperature sensor<a class="headerlink" href="#bmp180bmp280bme280bmp388bme680-temperature-sensor" title="Permanent link">¶</a></h3>
|
||||
<h3 id="capteur-de-temperature-bmp180bmp280bme280bmp388bme680">Capteur de température BMP180/BMP280/BME280/BMP388/BME680<a class="headerlink" href="#capteur-de-temperature-bmp180bmp280bme280bmp388bme680" title="Permanent link">¶</a></h3>
|
||||
<p>BMP180/BMP280/BME280/BMP388/BME680 two wire interface (I2C) environmental sensors. Note that these sensors are not intended for use with extruders and heater beds, but rather for monitoring ambient temperature (C), pressure (hPa), relative humidity and in case of the BME680 gas level. See <a href="https://github.com/Klipper3d/klipper/blob/master/config/sample-macros.cfg">sample-macros.cfg</a> for a gcode_macro that may be used to report pressure and humidity in addition to temperature.</p>
|
||||
<div class="highlight"><pre><span></span><code>sensor_type: BME280
|
||||
#i2c_address:
|
||||
|
|
@ -6061,8 +6163,8 @@ serial_no:
|
|||
# Le micro-contrôleur à lire. Doit être le host_mcu
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="combined-temperature-sensor">Combined temperature sensor<a class="headerlink" href="#combined-temperature-sensor" title="Permanent link">¶</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>
|
||||
<h3 id="capteur-de-temperature-combine">Capteur de température combiné<a class="headerlink" href="#capteur-de-temperature-combine" title="Permanent link">¶</a></h3>
|
||||
<p>Le capteur de température combiné est un capteur virtuel basé sur plusieurs autres capteurs Ce capteur peut être utilisé avec des extrudeurs, des chauffages génériques et des plateaux chauffants.</p>
|
||||
<div class="highlight"><pre><span></span><code>sensor_type: temperature_combined
|
||||
#sensor_list:
|
||||
# Must be provided. List of sensors to combine to new "virtual"
|
||||
|
|
@ -6933,6 +7035,7 @@ run_current:
|
|||
#driver_SEIMIN: 0
|
||||
#driver_SFILT: 0
|
||||
#driver_SG4_ANGLE_OFFSET: 1
|
||||
#driver_SLOPE_CONTROL: 0
|
||||
# Set the given register during the configuration of the TMC2240
|
||||
# chip. This may be used to set custom motor parameters. The
|
||||
# defaults for each parameter are next to the parameter name in the
|
||||
|
|
@ -7202,73 +7305,83 @@ wiper:
|
|||
<h3 id="display">[display]<a class="headerlink" href="#display" title="Permanent link">¶</a></h3>
|
||||
<p>Prise en charge d'un écran relié au microcontrôleur.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type :
|
||||
# Le type de puce LCD utilisé. Cela peut être "hd44780", "hd44780_spi", "st7920",
|
||||
# "emulated_st7920", "uc1701", "ssd1306", ou "sh1106".
|
||||
# Voir les sections d'affichage ci-dessous pour plus d'informations sur chaque type
|
||||
# et les paramètres supplémentaires qu'ils fournissent. Ce paramètre doit être
|
||||
# fourni.
|
||||
#display_group :
|
||||
# Le nom du groupe de données à afficher sur l'écran. Cela contrôle le contenu de
|
||||
# l'écran (voir la section "display_data" pour plus d'informations). La valeur par
|
||||
# défaut est _default_20x4 pour les écrans hd44780 et _default_16x4 pour les
|
||||
# autres affichages.
|
||||
#menu_timeout :
|
||||
# Délai d'attente pour le menu. Le fait d'être inactif pendant ce nombre de secondes
|
||||
# déclenchera la sortie du menu ou le retour au menu racine si l'autorun est activé.
|
||||
# La valeur par défaut est 0 seconde (désactivé)
|
||||
#menu_root :
|
||||
# Nom de la section du menu principal à afficher lorsque vous cliquez sur l'encodeur
|
||||
# de l'écran d'accueil. La valeur par défaut est __main, et cela affiche les menus par
|
||||
# défaut tels que définis dans klippy/extras/display/menu.cfg
|
||||
#menu_reverse_navigation :
|
||||
# Lorsque activé, inverse les directions vers le haut et vers le bas de la liste.
|
||||
# La valeur par défaut est False. Ce paramètre est optionnel.
|
||||
#encoder_pins :
|
||||
# Les broches connectées à l'encodeur. 2 broches doivent être fournies lorsque vous
|
||||
# utilisez l'encodeur. Ce paramètre doit être fourni lors de l'utilisation du menu.
|
||||
#encoder_steps_per_detent :
|
||||
# Combien de pas l'encodeur émet par cran ("clic"). Si l'encodeur prend deux crans pour
|
||||
# se déplacer entre les entrées ou déplace deux entrées à partir d'un seul cran, essayez de
|
||||
# modifier cette valeur. Les valeurs autorisées sont 2 (demi-step) ou 4 (full-step).
|
||||
# La valeur par défaut est 4.
|
||||
#click_pin :
|
||||
# La broche connectée au bouton 'entrée' ou au 'clic' de l'encodeur. Ce paramètre doit
|
||||
# être fourni lors de l'utilisation du menu. La présence d'un paramètre de configuration
|
||||
# 'analog_range_click_pin' fait passer ce paramètre de numérique à analogique.
|
||||
#back_pin :
|
||||
# La broche connectée au bouton 'retour'. Ce paramètre est facultatif, le menu peut être utilisé
|
||||
# sans lui. La présence d'un paramètre de configuration 'analog_range_back_pin' transforme
|
||||
# ce paramètre de numérique à analogique.
|
||||
#up_pin :
|
||||
# La broche connectée au bouton 'haut'. Ce paramètre doit être fourni lorsque vous utilisez un
|
||||
# menu sans encodeur. La présence d'un paramètre de configuration 'analog_range_up_pin'
|
||||
# transforme ce paramètre de numérique à analogique.
|
||||
#down_pin :
|
||||
# La broche connectée au bouton 'bas'. Ce paramètre doit être fourni lorsque vous utilisez un
|
||||
# menu sans encodeur. La présence d'un paramètre de configuration 'analog_range_down_pin'
|
||||
# transforme ce paramètre de numérique à analogique.
|
||||
#kill_pin :
|
||||
# La broche connectée au bouton 'kill'. Ce bouton appellera l'arrêt d'urgence. La présence d'un
|
||||
# paramètre 'analog_range_kill_pin' fait passer ce paramètre de numérique à analogique.
|
||||
#analog_pullup_resistor : 4700
|
||||
# La résistance (en ohms) du pullup attaché au bouton analogique.
|
||||
# La valeur par défaut est de 4700 ohms.
|
||||
#analog_range_click_pin :
|
||||
# La plage de résistances du bouton 'entrée'. Les valeurs minimale et maximale de la plage
|
||||
# séparées par des virgules doivent être fournies lors de l'utilisation du bouton analogique.
|
||||
#analog_range_back_pin :
|
||||
# La plage de résistances du bouton 'retour'. Les valeurs minimale et maximale de la plage
|
||||
# séparées par des virgules doivent être fournies lors de l'utilisation du bouton analogique.
|
||||
#analog_range_up_pin :
|
||||
# La plage de résistances du bouton 'haut'. Les valeurs minimale et maximale de la plage
|
||||
# séparées par des virgules doivent être fournies lors de l'utilisation du bouton analogique.
|
||||
#analog_range_down_pin :
|
||||
# La plage de résistances du bouton 'bas'. Les valeurs minimale et maximale de la plage
|
||||
# séparées par des virgules doivent être fournies lors de l'utilisation du bouton analogique.
|
||||
#analog_range_kill_pin :
|
||||
# La plage de résistances du bouton 'kill'. Les valeurs minimale et maximale de la plage
|
||||
# séparées par des virgules doivent être fournies lors de l'utilisation du bouton analogique.
|
||||
lcd_type:
|
||||
# The type of LCD chip in use. This may be "hd44780", "hd44780_spi",
|
||||
# "aip31068_spi", "st7920", "emulated_st7920", "uc1701", "ssd1306", or
|
||||
# "sh1106".
|
||||
# See the display sections below for information on each type and
|
||||
# additional parameters they provide. This parameter must be
|
||||
# provided.
|
||||
#display_group:
|
||||
# The name of the display_data group to show on the display. This
|
||||
# controls the content of the screen (see the "display_data" section
|
||||
# for more information). The default is _default_20x4 for hd44780 or
|
||||
# aip31068_spi displays and _default_16x4 for other displays.
|
||||
#menu_timeout:
|
||||
# Timeout for menu. Being inactive this amount of seconds will
|
||||
# trigger menu exit or return to root menu when having autorun
|
||||
# enabled. The default is 0 seconds (disabled)
|
||||
#menu_root:
|
||||
# Name of the main menu section to show when clicking the encoder
|
||||
# on the home screen. The defaults is __main, and this shows the
|
||||
# the default menus as defined in klippy/extras/display/menu.cfg
|
||||
#menu_reverse_navigation:
|
||||
# When enabled it will reverse up and down directions for list
|
||||
# navigation. The default is False. This parameter is optional.
|
||||
#encoder_pins:
|
||||
# The pins connected to encoder. 2 pins must be provided when using
|
||||
# encoder. This parameter must be provided when using menu.
|
||||
#encoder_steps_per_detent:
|
||||
# How many steps the encoder emits per detent ("click"). If the
|
||||
# encoder takes two detents to move between entries or moves two
|
||||
# entries from one detent, try changing this. Allowed values are 2
|
||||
# (half-stepping) or 4 (full-stepping). The default is 4.
|
||||
#click_pin:
|
||||
# The pin connected to 'enter' button or encoder 'click'. This
|
||||
# parameter must be provided when using menu. The presence of an
|
||||
# 'analog_range_click_pin' config parameter turns this parameter
|
||||
# from digital to analog.
|
||||
#back_pin:
|
||||
# The pin connected to 'back' button. This parameter is optional,
|
||||
# menu can be used without it. The presence of an
|
||||
# 'analog_range_back_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#up_pin:
|
||||
# The pin connected to 'up' button. This parameter must be provided
|
||||
# when using menu without encoder. The presence of an
|
||||
# 'analog_range_up_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#down_pin:
|
||||
# The pin connected to 'down' button. This parameter must be
|
||||
# provided when using menu without encoder. The presence of an
|
||||
# 'analog_range_down_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#kill_pin:
|
||||
# The pin connected to 'kill' button. This button will call
|
||||
# emergency stop. The presence of an 'analog_range_kill_pin' config
|
||||
# parameter turns this parameter from digital to analog.
|
||||
#analog_pullup_resistor: 4700
|
||||
# The resistance (in ohms) of the pullup attached to the analog
|
||||
# button. The default is 4700 ohms.
|
||||
#analog_range_click_pin:
|
||||
# The resistance range for a 'enter' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_back_pin:
|
||||
# The resistance range for a 'back' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_up_pin:
|
||||
# The resistance range for a 'up' button. Range minimum and maximum
|
||||
# comma-separated values must be provided when using analog button.
|
||||
#analog_range_down_pin:
|
||||
# The resistance range for a 'down' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_kill_pin:
|
||||
# The resistance range for a 'kill' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="ecran-hd44780">écran hd44780<a class="headerlink" href="#ecran-hd44780" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -7320,6 +7433,26 @@ spi_software_miso_pin:
|
|||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="aip31068_spi-display">aip31068_spi display<a class="headerlink" href="#aip31068_spi-display" title="Permanent link">¶</a></h4>
|
||||
<p>Information on configuring an aip31068_spi display - a very similar to hd44780_spi a 20x04 (20 symbols by 4 lines) display with slightly different internal protocol.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type: aip31068_spi
|
||||
latch_pin:
|
||||
spi_software_sclk_pin:
|
||||
spi_software_mosi_pin:
|
||||
spi_software_miso_pin:
|
||||
# The pins connected to the shift register controlling the display.
|
||||
# The spi_software_miso_pin needs to be set to an unused pin of the
|
||||
# printer mainboard as the shift register does not have a MISO pin,
|
||||
# but the software spi implementation requires this pin to be
|
||||
# configured.
|
||||
#line_length:
|
||||
# Set the number of characters per line for an hd44780 type lcd.
|
||||
# Possible values are 20 (default) and 16. The number of lines is
|
||||
# fixed to 4.
|
||||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="ecran-st7920">écran st7920<a class="headerlink" href="#ecran-st7920" title="Permanent link">¶</a></h4>
|
||||
<p>Informations de configuration des écrans st7920 (utilisés dans les écrans de type "RepRapDiscount 12864 Full Graphic Smart Controller").</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
|
|
@ -7657,7 +7790,7 @@ adc2:
|
|||
# paramètres ci-dessus.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="load-cells">Load Cells<a class="headerlink" href="#load-cells" title="Permanent link">¶</a></h2>
|
||||
<h2 id="cellules-de-charge">Cellules de charge<a class="headerlink" href="#cellules-de-charge" title="Permanent link">¶</a></h2>
|
||||
<h3 id="load_cell">[load_cell]<a class="headerlink" href="#load_cell" title="Permanent link">¶</a></h3>
|
||||
<p>Load Cell. Uses an ADC sensor attached to a load cell to create a digital scale.</p>
|
||||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
|
|
@ -7665,7 +7798,7 @@ sensor_type:
|
|||
# This must be one of the supported sensor types, see below.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="xh711">XH711<a class="headerlink" href="#xh711" title="Permanent link">¶</a></h4>
|
||||
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">¶</a></h4>
|
||||
<p>This is a 24 bit low sample rate chip using "bit-bang" communications. It is suitable for filament scales.</p>
|
||||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
sensor_type: hx711
|
||||
|
|
@ -7728,13 +7861,30 @@ data_ready_pin:
|
|||
#gain: 128
|
||||
# Valid gain values are 128, 64, 32, 16, 8, 4, 2, 1
|
||||
# The default is 128
|
||||
#pga_bypass: False
|
||||
# Disable the internal Programmable Gain Amplifier. If
|
||||
# True the PGA will be disabled for gains 1, 2, and 4. The PGA is always
|
||||
# enabled for gain settings 8 to 128, regardless of the pga_bypass setting.
|
||||
# If AVSS is used as an input pga_bypass is forced to True.
|
||||
# The default is False.
|
||||
#sample_rate: 660
|
||||
# This chip supports two ranges of sample rates, Normal and Turbo. In turbo
|
||||
# mode the chips c internal clock runs twice as fast and the SPI communication
|
||||
# mode the chip's internal clock runs twice as fast and the SPI communication
|
||||
# speed is also doubled.
|
||||
# Normal sample rates: 20, 45, 90, 175, 330, 600, 1000
|
||||
# Turbo sample rates: 40, 90, 180, 350, 660, 1200, 2000
|
||||
# The default is 660
|
||||
#input_mux:
|
||||
# Input multiplexer configuration, select a pair of pins to use. The first pin
|
||||
# is the positive, AINP, and the second pin is the negative, AINN. Valid
|
||||
# values are: 'AIN0_AIN1', 'AIN0_AIN2', 'AIN0_AIN3', 'AIN1_AIN2', 'AIN1_AIN3',
|
||||
# 'AIN2_AIN3', 'AIN1_AIN0', 'AIN3_AIN2', 'AIN0_AVSS', 'AIN1_AVSS', 'AIN2_AVSS'
|
||||
# and 'AIN3_AVSS'. If AVSS is used the PGA is bypassed and the pga_bypass
|
||||
# setting will be forced to True.
|
||||
# The default is AIN0_AIN1.
|
||||
#vref:
|
||||
# The selected voltage reference. Valid values are: 'internal', 'REF0', 'REF1'
|
||||
# and 'analog_supply'. Default is 'internal'.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="support-materiel-specifique-a-une-carte">Support matériel spécifique à une carte<a class="headerlink" href="#support-materiel-specifique-a-une-carte" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -7875,28 +8025,30 @@ serial:
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<p>Prise en charge du capteur d'angle Hall magnétique pour la lecture des mesures de l'angle de l'arbre du moteur pas à pas à l'aide des puces SPI a1333, as5047d ou tle5012b. Les mesures sont disponibles via le <a href="API_Server.html">serveur API</a> et l'<a href="Debugging.html#motion-analysis-and-data-logging">outil d'analyse de mouvement</a>. Voir la <a href="G-Codes.html#angle">référence G-Code</a> pour les commandes disponibles.</p>
|
||||
<p>Magnetic hall angle sensor support for reading stepper motor angle shaft measurements using a1333, as5047d, mt6816, mt6826s, or tle5012b SPI chips. The measurements are available via the <a href="API_Server.html">API Server</a> and <a href="Debugging.html#motion-analysis-and-data-logging">motion analysis tool</a>. See the <a href="G-Codes.html#angle">G-Code reference</a> for available commands.</p>
|
||||
<div class="highlight"><pre><span></span><code>[angle my_angle_sensor]
|
||||
sensor_type:
|
||||
# Le type de la puce du capteur magnétique à effet Hall. Les choix disponibles
|
||||
# sont "a1333", "as5047d" et "tle5012b". Ce paramètre doit être spécifié.
|
||||
# The type of the magnetic hall sensor chip. Available choices are
|
||||
# "a1333", "as5047d", "mt6816", "mt6826s", and "tle5012b". This parameter must be
|
||||
# specified.
|
||||
#sample_period: 0.000400
|
||||
# La période de requête (en secondes) à utiliser lors des mesures. La valeur par
|
||||
# défaut est de 0.000400 (ce qui correspond à 2500 échantillons par seconde).
|
||||
# The query period (in seconds) to use during measurements. The
|
||||
# default is 0.000400 (which is 2500 samples per second).
|
||||
#stepper:
|
||||
# Le nom du pilote moteur pas à pas auquel le capteur d'angle est attaché (ex,
|
||||
# "stepper_x"). La définition de cette valeur active un étalonnage d'angle.
|
||||
# Pour utiliser cette fonction, le paquet Python "numpy" doit être installé.
|
||||
# Par défaut, l'étalonnage d'angle n'est pas activé pour un capteur d'angle.
|
||||
# The name of the stepper that the angle sensor is attached to (eg,
|
||||
# "stepper_x"). Setting this value enables an angle calibration
|
||||
# tool. To use this feature, the Python "numpy" package must be
|
||||
# installed. The default is to not enable angle calibration for the
|
||||
# angle sensor.
|
||||
cs_pin:
|
||||
# La broche d'activation SPI du capteur. Ce paramètre doit être fourni.
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#spi_speed:
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# Voir la section "paramètres SPI communs" pour une description des
|
||||
# paramètres ci-dessus.
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="parametres-communs-aux-bus">Paramètres communs aux bus<a class="headerlink" href="#parametres-communs-aux-bus" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -7921,7 +8073,7 @@ cs_pin:
|
|||
<h3 id="parametres-i2c-communs">Paramètres I2C communs<a class="headerlink" href="#parametres-i2c-communs" title="Permanent link">¶</a></h3>
|
||||
<p>Les paramètres suivants sont généralement disponibles pour les dispositifs utilisant un bus I2C.</p>
|
||||
<p>La prise en charge actuelle du microcontrôleur de Klipper pour I2C n'est généralement pas tolérante au bruit de ligne. Des erreurs inattendues sur les fils I2C peuvent amener Klipper à générer une erreur d'exécution. La prise en charge de Klipper pour la récupération d'erreur varie selon chaque type de microcontrôleur. Il est généralement recommandé de n'utiliser que des appareils I2C qui se trouvent sur la même carte de circuit imprimé que le microcontrôleur.</p>
|
||||
<p>La plupart des implémentations de microcontrôleurs Klipper ne prennent en charge qu'une <code>i2c_speed</code> de 100000 (<em>mode standard</em>, 100kbit/s). Le micro-contrôleur Klipper "Linux" supporte une vitesse de 400000 (<em>fast mode</em>, 400kbit/s), mais il doit être <a href="RPi_microcontroller.html#optional-enabling-i2c">défini dans le système d'exploitation</a> sinon le paramètre <code>i2c_speed</code> sera ignoré. Le microcontrôleur Klipper "RP2040" et la famille ATmega AVR supportent un taux de 400000 via le paramètre <code>i2c_speed</code>. Tous les autres microcontrôleurs Klipper utilisent un taux de 100000 et ignorent le paramètre <code>i2c_speed</code>.</p>
|
||||
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000 (<em>standard mode</em>, 100kbit/s). The Klipper "Linux" micro-controller supports a 400000 speed (<em>fast mode</em>, 400kbit/s), but it must be <a href="RPi_microcontroller.html#optional-enabling-i2c">set in the operating system</a> and the <code>i2c_speed</code> parameter is otherwise ignored. The Klipper "RP2040" micro-controller and ATmega AVR family and some STM32 (F0, G0, G4, L4, F7, H7) support a rate of 400000 via the <code>i2c_speed</code> parameter. All other Klipper micro-controllers use a 100000 rate and ignore the <code>i2c_speed</code> parameter.</p>
|
||||
<div class="highlight"><pre><span></span><code>#i2c_address:
|
||||
# The i2c address of the device. This must specified as a decimal
|
||||
# number (not in hex). The default depends on the type of device.
|
||||
|
|
|
|||
|
|
@ -1412,7 +1412,7 @@
|
|||
# temperature probe configuration...
|
||||
</code></pre></div>
|
||||
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below.</p>
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below. If the printer to be calibrated is enclosed, it is strongly recommended to set the <code>max_validation_temp</code> option to a value between 100 and 120.</p>
|
||||
<p>Eddy probe manufacturers may offer a stock drift calibration that can be manually added to <code>drift_calibration</code> option of the <code>[probe_eddy_current]</code> section. If they do not, or if the stock calibration does not perform well on your system, the <code>temperature_probe</code> module offers a manual calibration procedure via the <code>TEMPERATURE_PROBE_CALIBRATE</code> gcode command.</p>
|
||||
<p>Prior to performing calibration the user should have an idea of what the maximum attainable temperature probe coil temperature is. This temperature should be used to set the <code>TARGET</code> parameter of the <code>TEMPERATURE_PROBE_CALIBRATE</code> command. The goal is to calibrate across the widest temperature range possible, thus its desirable to start with the printer cold and finish with the coil at the maximum temperature it can reach.</p>
|
||||
<p>Once a <code>[temperature_probe]</code> is configured, the following steps may be taken to perform thermal drift calibration:</p>
|
||||
|
|
|
|||
|
|
@ -1542,6 +1542,16 @@
|
|||
<td>2634K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>RP2350</td>
|
||||
<td>4167K</td>
|
||||
<td>2663K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SAME70</td>
|
||||
<td>6667K</td>
|
||||
<td>4737K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>STM32H743</td>
|
||||
<td>9091K</td>
|
||||
<td>6061K</td>
|
||||
|
|
|
|||
|
|
@ -869,6 +869,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1958,6 +1965,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3089,6 +3116,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4178,6 +4212,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4750,6 +4804,11 @@
|
|||
<p>Les commandes suivantes sont disponibles lorsqu'une section <a href="Config_Reference.html#angle">angle config</a> est activée.</p>
|
||||
<h4 id="angle_calibrate">ANGLE_CALIBRATE<a class="headerlink" href="#angle_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CALIBRATE CHIP=<nom_de_la_puce></code> : Effectue une calibration d'angle sur le capteur donné (il doit y avoir une section de configuration <code>[angle nom_de_la_puce]</code> qui a indiqué un paramètre <code>stepper</code>). IMPORTANT - cet outil commandera au moteur pas à pas de se déplacer sans vérifier les limites normales de la cinématique. Idéalement, le moteur devrait être déconnecté de tout chariot d'imprimante avant d'effectuer le calibrage. Si le moteur pas à pas ne peut pas être déconnecté de l'imprimante, assurez-vous que le chariot est proche du centre de son rail avant de commencer l'étalonnage. (Le moteur pas à pas peut se déplacer vers l'avant ou l'arrière de deux rotations complètes durant ce test). Après avoir terminé ce test, utilisez la commande <code>SAVE_CONFIG</code> pour sauvegarder les données de calibration dans le fichier de configuration. Afin d'utiliser cet outil, le paquetage Python "numpy" doit être installé (voir le document <a href="Measuring_Resonances.html#software-installation">mesurer les résonances</a> pour plus d'informations).</p>
|
||||
<h4 id="angle_chip_calibrate">ANGLE_CHIP_CALIBRATE<a class="headerlink" href="#angle_chip_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CHIP_CALIBRATE CHIP=<chip_name></code>: Perform internal sensor calibration, if implemented (MT6826S/MT6835).</p>
|
||||
<ul>
|
||||
<li><strong>MT68XX</strong>: The motor should be disconnected from any printer carriage before performing calibration. After calibration, the sensor should be reset by disconnecting the power.</li>
|
||||
</ul>
|
||||
<h4 id="angle_debug_read">ANGLE_DEBUG_READ<a class="headerlink" href="#angle_debug_read" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_DEBUG_READ CHIP=<nom_de_la_configuration> REG=<registre></code> : Interroge le registre "registre" du capteur (par exemple 44 ou 0x2C). Peut être utile à des fins de débogage. Ceci n'est disponible que pour les puces tle5012b.</p>
|
||||
<h4 id="angle_debug_write">ANGLE_DEBUG_WRITE<a class="headerlink" href="#angle_debug_write" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4758,7 +4817,12 @@
|
|||
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
|
||||
section</a> is enabled.</p>
|
||||
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=<value>]</code>: Initiates the X twist calibration wizard. <code>SAMPLE_COUNT</code> specifies the number of points along the X axis to calibrate at and defaults to 3.</p>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]</code></p>
|
||||
<p>Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.</p>
|
||||
<ul>
|
||||
<li><strong>AXIS:</strong> Define the axis (<code>X</code> or <code>Y</code>) for which the twist compensation will be calibrated. If not specified, the axis defaults to <code>'X'</code>.</li>
|
||||
<li><strong>AUTO:</strong> Enables automatic calibration mode. When <code>AUTO=True</code>, the calibration will run for both the X and Y axes. In this mode, <code>AXIS</code> cannot be specified. If both <code>AXIS</code> and <code>AUTO</code> are provided, an error will be raised.</li>
|
||||
</ul>
|
||||
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">¶</a></h3>
|
||||
<p>Les commandes suivantes sont disponibles lorsque la section <a href="Config_Reference.html#bed_mesh">configuration de bed_mesh</a> est activée (voir également le <a href="Bed_Mesh.html">guide de bed_mesh</a>).</p>
|
||||
<h4 id="bed_mesh_calibrate">BED_MESH_CALIBRATE<a class="headerlink" href="#bed_mesh_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4862,6 +4926,7 @@ section</a> is enabled.</p>
|
|||
<p>La commande suivante est disponible lorsqu'une section <a href="Config_Reference.html#fan_generic">fan_generic config</a> est activée.</p>
|
||||
<h4 id="set_fan_speed">SET_FAN_SPEED<a class="headerlink" href="#set_fan_speed" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_FAN_SPEED FAN=nom_config SPEED=<vitesse></code> Cette commande définit la vitesse d'un ventilateur. La valeur de "vitesse" doit être comprise entre 0,0 et 1,0.</p>
|
||||
<p><code>SET_FAN_SPEED PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given fan. For example, if one defined a <code>[display_template my_fan_template]</code> config section then one could assign <code>TEMPLATE=my_fan_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the fan will be automatically set to the resulting speed. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_FAN_SPEED</code> commands to manage the values directly).</p>
|
||||
<h3 id="filament_switch_sensor">[filament_switch_sensor]<a class="headerlink" href="#filament_switch_sensor" title="Permanent link">¶</a></h3>
|
||||
<p>La commande suivante est disponible lorsqu'une section de configuration <a href="Config_Reference.html#filament_switch_sensor">filament_switch_sensor</a> ou <a href="Config_Reference.html#filament_motion_sensor">filament_motion_sensor</a> est activée.</p>
|
||||
<h4 id="query_filament_sensor">QUERY_FILAMENT_SENSOR<a class="headerlink" href="#query_filament_sensor" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4886,7 +4951,7 @@ section</a> is enabled.</p>
|
|||
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>FORCE_MOVE STEPPER=<nom_de_la_configuration> DISTANCE=<valeur> VELOCITE=<valeur> [ACCEL=<valeur>]</code> : Cette commande forcera le déplacement du stepper donné sur la distance donnée (en mm) à la vitesse constante donnée (en mm/s). Si ACCEL est spécifié et est supérieur à zéro, alors l'accélération donnée (en mm/s^2) sera utilisée ; sinon, aucune accélération n'est effectuée. Aucune vérification des limites n'est effectuée ; aucune mise à jour cinématique n'est faite ; les autres steppers parallèles sur un axe ne seront pas déplacés. Soyez prudent car une commande incorrecte pourrait endommager le matériel ! L'utilisation de cette commande placera presque certainement la cinématique de bas niveau dans un état incorrect ; émettez ensuite un G28 pour réinitialiser la cinématique. Cette commande est destinée aux diagnostics de bas niveau et au débogage.</p>
|
||||
<h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>]</code> : Force le code cinématique de bas niveau à croire que la tête d'outil est à la position cartésienne donnée. Il s'agit d'une commande de diagnostic et de débogage ; utilisez SET_GCODE_OFFSET et/ou G92 pour des transformations d'axe régulières. Si un axe n'est pas spécifié, la position par défaut sera celle de la dernière commande de la tête. La définition d'une position incorrecte ou invalide peut entraîner des erreurs logicielles internes. Cette commande peut invalider les futures vérifications de limites ; émettez ensuite un G28 pour réinitialiser la cinématique.</p>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an axis is not specified then it will default to the position that the head was last commanded to. Setting an incorrect or invalid position may lead to internal software errors. Use the CLEAR parameter to forget the homing state for the given axes. Note that CLEAR will not override the previous functionality; if an axis is not specified to CLEAR it will have its kinematic position set as per above. This command may invalidate future boundary checks; issue a G28 afterwards to reset the kinematics.</p>
|
||||
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">¶</a></h3>
|
||||
<p>Le module gcode est automatiquement chargé.</p>
|
||||
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4980,6 +5045,7 @@ section</a> is enabled.</p>
|
|||
<p>La commande suivante est disponible lorsqu'une section <a href="Config_Reference.html#output_pin">output_pin config</a> est activée.</p>
|
||||
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value></code>: Set the pin to the given output <code>VALUE</code>. VALUE should be 0 or 1 for "digital" output pins. For PWM pins, set to a value between 0.0 and 1.0, or between 0.0 and <code>scale</code> if a scale is configured in the output_pin config section.</p>
|
||||
<p><code>SET_PIN PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given pin. For example, if one defined a <code>[display_template my_pin_template]</code> config section then one could assign <code>TEMPLATE=my_pin_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the pin will be automatically set to the resulting value. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_PIN</code> commands to manage the values directly).</p>
|
||||
<h3 id="palette2">[palette2]<a class="headerlink" href="#palette2" title="Permanent link">¶</a></h3>
|
||||
<p>Les commandes suivantes sont disponibles lorsque la section <a href="Config_Reference.html#palette2">palette2 config</a> est activée.</p>
|
||||
<p>Les impressions avec Palette fonctionnent en intégrant des OCodes (Omega Codes) spéciaux dans le fichier GCode :</p>
|
||||
|
|
@ -5037,6 +5103,10 @@ section</a> is enabled.</p>
|
|||
<p>The following command is available when a <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time config section</a> is enabled.</p>
|
||||
<h4 id="set_pin_1">SET_PIN<a class="headerlink" href="#set_pin_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value> [CYCLE_TIME=<cycle_time>]</code>: This command works similarly to <a href="#output_pin">output_pin</a> SET_PIN commands. The command here supports setting an explicit cycle time using the CYCLE_TIME parameter (specified in seconds). Note that the CYCLE_TIME parameter is not stored between SET_PIN commands (any SET_PIN command without an explicit CYCLE_TIME parameter will use the <code>cycle_time</code> specified in the pwm_cycle_time config section).</p>
|
||||
<h3 id="quad_gantry_level">[quad_gantry_level]<a class="headerlink" href="#quad_gantry_level" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#quad_gantry_level">quad_gantry_level config section</a> is enabled.</p>
|
||||
<h4 id="quad_gantry_level_1">QUAD_GANTRY_LEVEL<a class="headerlink" href="#quad_gantry_level_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>QUAD_GANTRY_LEVEL [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">¶</a></h3>
|
||||
<p>Le module query_adc est automatiquement chargé.</p>
|
||||
<h4 id="query_adc_1">QUERY_ADC<a class="headerlink" href="#query_adc_1" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -5053,9 +5123,9 @@ section</a> is enabled.</p>
|
|||
<h4 id="measure_axes_noise">MEASURE_AXES_NOISE<a class="headerlink" href="#measure_axes_noise" title="Permanent link">¶</a></h4>
|
||||
<p><code>MEASURE_AXES_NOISE</code>: Mesure et affiche le bruit pour tous les axes de toutes les puces accélérométriques activées.</p>
|
||||
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">¶</a></h4>
|
||||
<p><code>TEST_RESONANCES AXE=<axe> OUTPUT=<resonances,raw_data> [NOM=<nom>] [FREQ_START=<freq_min>] [FREQ_END=<freq_max>] [HZ_PER_SEC=<hz_par_sec>] [CHIPS=<nom_puce_adxl345>] [POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]</code> : Exécute le test de résonance dans tous les points de sonde configurés pour l'"axe" demandé et mesure l'accélération en utilisant les puces accélérométres configurées pour l'axe respectif. L'"axe" peut être X ou Y, ou spécifier une direction arbitraire comme <code>AXIS=dx,dy</code>, où dx et dy sont des nombres à virgule flottante définissant un vecteur de direction (par exemple, <code>AXIS=X</code>, <code>AXIS=Y</code>, ou <code>AXIS=1,-1</code> pour définir une direction diagonale). Notez que <code>AXIS=dx,dy</code> et <code>AXIS=-dx,-dy</code> sont équivalents. <code>nom_puce_adxl345</code> peut être une ou plusieurs puces adxl345 configurées, délimitées par des virgules, par exemple <code>CHIPS="adxl345, adxl345 rpi"</code>. Notez que le terme <code>adxl345</code> peut être omis pour les puces adxl345 nommées. Si POINT est indiqué, il remplacera le(s) point(s) configuré(s) dans <code>[resonance_tester]</code>. Si <code>INPUT_SHAPING=0</code> ou non défini (par défaut), désactive la mise en forme de l'entrée pour le test de résonance, car il n'est pas valide d'exécuter le test de résonance avec la mise en forme de l'entrée active. Le paramètre <code>OUTPUT</code> consiste en une liste séparée par des virgules des sorties qui seront écrites. Si <code>raw_data</code> est demandé, alors les données brutes de l'accéléromètre sont écrites dans un fichier ou une série de fichiers <code>/tmp/raw_data_<axe>_[<nom_puce>_][<point>_]<nom>.csv</code> avec (la partie <code><point>_</code> du nom générée seulement si plus d'un point de sonde est configuré ou si POINT est spécifié). Si <code>resonances</code> est spécifié, la réponse en fréquence est calculée (à travers tous les points de sonde) et écrite dans le fichier <code>/tmp/resonances_<axe>_<nom>.csv</code>. S'il n'est pas défini, OUTPUT prend par défaut la valeur de <code>resonances</code>, et NAME prend par défaut la valeur de l'heure actuelle au format "AAAAMMJJ_HHMMSS".</p>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> [OUTPUT=<resonances,raw_data>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [POINT=x,y,z] [INPUT_SHAPING=<0:1>]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>chip_name</code> can be one or more configured accel chips, delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<h4 id="shaper_calibrate">SHAPER_CALIBRATE<a class="headerlink" href="#shaper_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [MAX_SMOOTHING=<max_smoothing>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>][HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [MAX_SMOOTHING=<max_smoothing>] [INPUT_SHAPING=<0:1>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">¶</a></h3>
|
||||
<p>Les commandes G-Code standard suivantes sont disponibles lorsque la section <a href="Config_Reference.html#respond">respond config</a> est activée :</p>
|
||||
<ul>
|
||||
|
|
@ -5161,7 +5231,7 @@ section</a> is enabled.</p>
|
|||
<h3 id="z_tilt">[z_tilt]<a class="headerlink" href="#z_tilt" title="Permanent link">¶</a></h3>
|
||||
<p>Les commandes suivantes sont disponibles lorsque la section <a href="Config_Reference.html#z_tilt">z_tilt config</a> est activée.</p>
|
||||
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">¶</a></h4>
|
||||
<p><code>Z_TILT_ADJUST [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: Cette commande sondera les points spécifiés dans la configuration, puis effectuera des ajustements indépendants sur chaque stepper Z pour compenser l'inclinaison. Voir la commande PROBE pour plus de détails sur les paramètres de sonde facultatifs. La valeur facultative <code>HORIZONTAL_MOVE_Z</code> remplace l'option <code>horizontal_move_z</code> spécifiée dans le fichier de configuration.</p>
|
||||
<p><code>Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when a <a href="Config_Reference.html#temperature_probe">temperature_probe config section</a> is enabled.</p>
|
||||
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
|
|||
|
|
@ -912,8 +912,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#configure-lis2dw-series" class="md-nav__link">
|
||||
Configure LIS2DW series
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -990,6 +990,13 @@
|
|||
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>
|
||||
|
|
|
|||
|
|
@ -1447,7 +1447,7 @@ git clone https://github.com/Klipper3d/klipper
|
|||
<h2 id="configuring-octoprint-to-use-klipper">Configuring OctoPrint to use Klipper<a class="headerlink" href="#configuring-octoprint-to-use-klipper" title="Permanent link">¶</a></h2>
|
||||
<p>The OctoPrint web server needs to be configured to communicate with the Klipper host software. Using a web browser, login to the OctoPrint web page and then configure the following items:</p>
|
||||
<p>Navigate to the Settings tab (the wrench icon at the top of the page). Under "Serial Connection" in "Additional serial ports" add:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.sock
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.serial
|
||||
</code></pre></div>
|
||||
|
||||
<p>Then click "Save".</p>
|
||||
|
|
|
|||
|
|
@ -1480,7 +1480,7 @@
|
|||
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" style="margin:25px"/></a></p>
|
||||
<p>BIGTREETECH est le sponsor officiel de cartes mères pour Klipper. BIGTREETECH s’engage à développer des produits innovants et compétitifs pour mieux servir la communauté de l’impression 3D. Suivez-les sur <a href="https://www.facebook.com/BIGTREETECH">Facebook</a> ou <a href="https://twitter.com/BigTreeTech">Twitter</a>.</p>
|
||||
<h2 id="sponsors_1">Sponsors<a class="headerlink" href="#sponsors_1" title="Permanent link">¶</a></h2>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a> <a href="https://peopoly.net"><img src="./img/sponsors/peopoly-logo.png" width="200" style="margin:25px" /></a></p>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a></p>
|
||||
<h2 id="developpeurs-klipper">Développeurs Klipper<a class="headerlink" href="#developpeurs-klipper" title="Permanent link">¶</a></h2>
|
||||
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">¶</a></h3>
|
||||
<p>Kevin est l'auteur original et le mainteneur actuel de Klipper. Faites un don sur : <a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> ou <a href="https://www.patreon.com/koconnor">https://www.patreon.com/koconnor</a></p>
|
||||
|
|
|
|||
Binary file not shown.
File diff suppressed because one or more lines are too long
110
fr/sitemap.xml
110
fr/sitemap.xml
|
|
@ -2,277 +2,277 @@
|
|||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
|
|
@ -711,6 +711,33 @@
|
|||
A kompenzációs használat áttekintése
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="A kompenzációs használat áttekintése">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1384,6 +1411,33 @@
|
|||
A kompenzációs használat áttekintése
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="A kompenzációs használat áttekintése">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1420,19 +1474,43 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
|
|||
<blockquote>
|
||||
<p><strong>Tip:</strong> Győződj meg róla, hogy az <a href="Config_Reference.html#probe"> X és Y eltolás</a> megfelelően van beállítva, mivel nagymértékben befolyásolják a kalibrálást.</p>
|
||||
</blockquote>
|
||||
<h3 id="basic-usage-x-axis-calibration">Basic Usage: X-Axis Calibration<a class="headerlink" href="#basic-usage-x-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<ol>
|
||||
<li>Az [axis_twist_compensation] modul beállítása után hajtsd végre az alábbi parancsot <code>AXIS_TWIST_COMPENSATION_CALIBRATE</code></li>
|
||||
<li>After setting up the <code>[axis_twist_compensation]</code> module, run:</li>
|
||||
</ol>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE
|
||||
</code></pre></div>
|
||||
|
||||
<p>This command will calibrate the X-axis by default. - The calibration wizard will prompt you to measure the probe Z offset at several points along the bed. - By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=<value></code></p>
|
||||
<ol>
|
||||
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).</li>
|
||||
<li>
|
||||
<p><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</p>
|
||||
<ul>
|
||||
<li>A kalibrációs varázsló felszólít Téged, hogy mérd meg a szonda Z eltolását az ágy mentén néhány ponton</li>
|
||||
<li>A kalibrálás alapértelmezett értéke 3 pont, de a <code>SAMPLE_COUNT=</code> opcióval más számot is használhatsz.</li>
|
||||
<li><a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a></li>
|
||||
<li><a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a></li>
|
||||
</ul>
|
||||
<ol>
|
||||
<li><a href="Probe_Calibrate.html#calibrating-probe-z-offset">Z eltolás beállítása</a></li>
|
||||
<li>Automatikus/szondás szintezési műveletek végrehajtása, például <a href="G-Codes.html#screws_tilt_adjust">Orsók dőlésbeállítása</a>, <a href="G-Codes.html#z_tilt_adjust">Z dőlésbeállítása</a> stb</li>
|
||||
<li>Kezdőpont minden tengelyen, majd szükség esetén végezzünk egy <a href="Bed_Mesh.html"> Ágyháló</a> műveletet</li>
|
||||
<li>Végezz el egy próbanyomtatást, majd a kívánt <a href="Axis_Twist_Compensation.html#fine-tuning">finomhangolást</a></li>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Finalize the Setup:</strong></p>
|
||||
<ul>
|
||||
<li>Home all axes, and perform a <a href="Bed_Mesh.html">Bed Mesh</a> if necessary.</li>
|
||||
<li>Run a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> if needed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h3 id="for-y-axis-calibration">For Y-Axis Calibration<a class="headerlink" href="#for-y-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<p>The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y
|
||||
</code></pre></div>
|
||||
|
||||
<p>This will guide you through the same measuring process as for the X-axis.</p>
|
||||
<h3 id="automatic-calibration-for-both-axes">Automatic Calibration for Both Axes<a class="headerlink" href="#automatic-calibration-for-both-axes" title="Permanent link">¶</a></h3>
|
||||
<p>To perform automatic calibration for both the X and Y axes without manual intervention, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
|
||||
</code></pre></div>
|
||||
|
||||
<p>In this mode, the calibration process will run for both axes automatically.</p>
|
||||
<blockquote>
|
||||
<p><strong>Tipp:</strong> Úgy tűnik, hogy az ágy hőmérséklete és a fúvóka hőmérséklete és mértéke nem befolyásolja a kalibrálási folyamatot.</p>
|
||||
</blockquote>
|
||||
|
|
|
|||
|
|
@ -1968,7 +1968,7 @@ fade_target: 0
|
|||
<li><code>fade_target: 0</code> <em>Alapértelmezett érték: A háló átlagos Z-értéke</em> A <code>fade_target</code> úgy tekinthető, mint egy további Z-eltolás, amelyet a teljes ágyra alkalmaznak a fade befejezése után. Általánosságban azt szeretnénk, ha ez az érték 0 lenne, azonban vannak olyan körülmények, amikor ez nem kell, hogy így legyen. Tegyük fel például, hogy az ágyon a kezdőpont pozíciója egy kiugró érték, amely 0,2 mm-rel alacsonyabb, mint az ágy átlagos mért magassága. Ha a <code>fade_target</code> értéke 0, akkor a fade átlagosan 0,2 mm-rel zsugorítja a nyomtatást az ágyon. Ha a <code>fade_target</code> értéket .2-re állítja, a homed terület .2 mm-rel fog tágulni, azonban az ágy többi része pontosan lesz mérve. Általában jó ötlet a <code>fade_target</code> elhagyása a konfigurációból, így a háló átlagos magassága kerül felhasználásra, azonban kívánatos lehet a fade target kézi beállítása, ha az ágy egy bizonyos részére szeretnénk nyomtatni.</li>
|
||||
</ul>
|
||||
<h3 id="a-nulla-referenciapozicio-beallitasa">A nulla referenciapozíció beállítása<a class="headerlink" href="#a-nulla-referenciapozicio-beallitasa" title="Permanent link">¶</a></h3>
|
||||
<p>Sok szonda hajlamos a "driftre", azaz: a hő vagy interferencia által okozott pontatlanságokra. Ez kihívássá teheti a szonda Z-eltolásának kiszámítását, különösen különböző ágyhőmérsékleteken. Ezért egyes nyomtatók a Z tengely beállításához végállást, a háló kalibrálásához pedig szondát használnak. Ebben a konfigurációban lehetséges a háló eltolása úgy, hogy az (X, Y) <code>referenciapozíció</code> nullpontbeállításra vonatkozik. A <code>referenciapozíciónak</code> az ágyon annak a helynek kell lennie, ahol a <a href="./Manual_Level#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> papírtesztet végzik. A bed_mesh modul biztosítja a <code>zero_reference_position</code> opciót e koordináta megadásához:</p>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="Manual_Level.html#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<div class="highlight"><pre><span></span><code>[bed_mesh]
|
||||
speed: 120
|
||||
horizontal_move_z: 5
|
||||
|
|
|
|||
|
|
@ -1195,6 +1195,13 @@
|
|||
SAMD51 lépési sebesség referencia
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1205,8 +1212,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040-leptetesi-referencia" class="md-nav__link">
|
||||
RP2040 léptetési referencia
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1613,6 +1620,13 @@
|
|||
SAMD51 lépési sebesség referencia
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1623,8 +1637,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040-leptetesi-referencia" class="md-nav__link">
|
||||
RP2040 léptetési referencia
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -2122,6 +2136,34 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="same70-step-rate-benchmark">SAME70 step rate benchmark<a class="headerlink" href="#same70-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the SAME70:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=PC18 dir_pin=PB5 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=PC16 dir_pin=PD10 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=2 step_pin=PC28 dir_pin=PA4 invert_step=-1 step_pulse_ticks=0
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>34e9ea55</code> with gcc version <code>arm-none-eabi-gcc (NixOS 10.3-2021.10) 10.3.1</code> on a SAME70Q20B micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>same70</th>
|
||||
<th>trükkök</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1 léptető</td>
|
||||
<td>45</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 léptető</td>
|
||||
<td>190</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="ar100-lepesi-sebesseg-referencia">AR100 lépési sebesség referencia<a class="headerlink" href="#ar100-lepesi-sebesseg-referencia" title="Permanent link">¶</a></h3>
|
||||
<p>Az AR100 CPU (Allwinner A64) esetében a következő konfigurációs sorrend használatos:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2131,7 +2173,7 @@ config_stepper oid=2 step_pin=PL12 dir_pin=PE16 invert_step=-1 step_pulse_ticks=
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>A tesztet utoljára a <code>08d037c6</code> <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> gcc verzióval futtatták egy Allwinner A64-H mikrokontrollerrel.</p>
|
||||
<p>The test was last run on commit <code>b7978d37</code> with gcc version <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> on an Allwinner A64-H micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -2150,8 +2192,8 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="rp2040-leptetesi-referencia">RP2040 léptetési referencia<a class="headerlink" href="#rp2040-leptetesi-referencia" title="Permanent link">¶</a></h3>
|
||||
<p>Az RP2040 esetében a következő konfigurációs sorrendet kell alkalmazni:</p>
|
||||
<h3 id="rpxxxx-step-rate-benchmark">RPxxxx step rate benchmark<a class="headerlink" href="#rpxxxx-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040 and RP2350:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=gpio25 dir_pin=gpio3 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=gpio26 dir_pin=gpio4 invert_step=-1 step_pulse_ticks=0
|
||||
|
|
@ -2159,11 +2201,11 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>A tesztet legutóbb a <code>59314d99</code> megbízási gcc verzióval <code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code> Raspberry Pi Pico kártyán futtattuk.</p>
|
||||
<p>The test was last run on commit <code>f6718291</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2040</th>
|
||||
<th>rp2040 (*)</th>
|
||||
<th>trükkök</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
|
@ -2178,6 +2220,25 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2350</th>
|
||||
<th>trükkök</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1 léptető</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 léptető</td>
|
||||
<td>169</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 125Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM core cycles.</p>
|
||||
<h3 id="linux-mcu-lepesszam-referencia">Linux MCU lépésszám referencia<a class="headerlink" href="#linux-mcu-lepesszam-referencia" title="Permanent link">¶</a></h3>
|
||||
<p>A következő konfigurációs sorrendet egy Raspberry Pi esetében használjuk:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2311,9 +2372,15 @@ get_uptime
|
|||
</tr>
|
||||
<tr>
|
||||
<td>rp2040 (USB)</td>
|
||||
<td>873K</td>
|
||||
<td>c5667193</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2350 (USB)</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
|
|||
|
|
@ -1580,7 +1580,7 @@
|
|||
<li>Tekintsd át a klippy/kinematics/ könyvtárban található kinematikai osztályokat. A kinematikai osztályok feladata egy cartesian koordinátákban megadott mozgás átalakítása az egyes léptetőkön történő mozgássá. Kiindulópontként le kell tudni másolni az egyik ilyen fájlt.</li>
|
||||
<li>Implementáljuk a C léptetőket kinematikai pozíciófüggvényeit minden léptetőhöz, ha azok még nem állnak rendelkezésre (lásd a kin_cart.c, kin_corexy.c és kin_delta.c fájlokat a klippy/chelper/ állományban). A függvénynek meg kell hívnia <code>move_get_coord()</code>, hogy egy adott mozgásidőt (másodpercben) cartesian koordinátává (milliméterben) konvertáljon, majd ebből a cartesian koordinátából kiszámítsa a kívánt léptető pozíciót (milliméterben).</li>
|
||||
<li>Az új kinematikai osztályban implementáljuk a <code>calc_position()</code> módszert. Ez a metódus kiszámítja a nyomtatófej pozícióját cartesian koordinátákban az egyes léptetőmotorok pozíciójából. Nem kell, hogy hatékony legyen, mivel jellemzően csak a kezdőpont és az érintési műveletek során hívjuk meg.</li>
|
||||
<li>Egyéb módszerek. Implementálja a <code>check_move()</code>, <code>get_status()</code> metódusokat, <code>get_steppers()</code>, <code>home()</code> és <code>set_position()</code> módszereket. Ezeket a függvényeket általában kinematikai specifikus ellenőrzések biztosítására használják. A fejlesztés kezdetén azonban használhatunk itt kazán-lemez szerű kódot.</li>
|
||||
<li>Other methods. Implement the <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>clear_homing_state()</code>, and <code>set_position()</code> methods. These functions are typically used to provide kinematic specific checks. However, at the start of development one can use boiler-plate code here.</li>
|
||||
<li>Tesztelési esetek végrehajtása. Készíts egy G-kód fájlt egy sor olyan mozgással, amelyekkel az adott kinematika fontos eseteit tesztelheted. Kövesd a <a href="Debugging.html">Hibakeresési dokumentációt</a>, hogy ezt a G-kód fájlt mikrokontroller parancsokká alakítsd át. Ez hasznos a sarokesetek gyakorlására és a regressziók ellenőrzésére.</li>
|
||||
</ol>
|
||||
<h2 id="portolas-uj-mikrokontrollerre">Portolás új mikrokontrollerre<a class="headerlink" href="#portolas-uj-mikrokontrollerre" title="Permanent link">¶</a></h2>
|
||||
|
|
|
|||
|
|
@ -1396,6 +1396,11 @@
|
|||
<p>Ez a dokumentum a konfigurációs fájl legújabb szoftveres változtatásait tartalmazza, amelyek nem kompatibilisek visszafelé. A Klipper szoftver frissítésekor érdemes áttanulmányozni ezt a dokumentumot.</p>
|
||||
<p>A dokumentumban szereplő valamennyi dátum hozzávetőleges.</p>
|
||||
<h2 id="valtozasok">Változások<a class="headerlink" href="#valtozasok" title="Permanent link">¶</a></h2>
|
||||
<p>20241203: The resonance test has been changed to include slow sweeping moves. This change requires that testing point(s) have some clearance in X/Y plane (+/- 30 mm from the test point should suffice when using the default settings). The new test should generally produce more accurate and reliable test results. However, if required, the previous test behavior can be restored by adding options <code>sweeping_period: 0</code> and <code>accel_per_hz: 75</code> to the <code>[resonance_tester]</code> config section.</p>
|
||||
<p>20241201: In some cases Klipper may have ignored leading characters or spaces in a traditional G-Code command. For example, "99M123" may have been interpreted as "M123" and "M 321" may have been interpreted as "M321". Klipper will now report these cases with an "Unknown command" warning.</p>
|
||||
<p>20241112: Option <code>CHIPS=<chip_name></code> in <code>TEST_RESONANCES</code> and <code>SHAPER_CALIBRATE</code> requires specifying the full name(s) of the accel chip(s). For example, <code>adxl345 rpi</code> instead of short name - <code>rpi</code>.</p>
|
||||
<p>20240912: <code>SET_PIN</code>, <code>SET_SERVO</code>, <code>SET_FAN_SPEED</code>, <code>M106</code>, and <code>M107</code> commands are now collated. Previously, if many updates to the same object were issued faster than the minimum scheduling time (typically 100ms) then actual updates could be queued far into the future. Now if many updates are issued in rapid succession then it is possible that only the latest request will be applied. If the previous behavior is requried then consider adding explicit <code>G4</code> delay commands between updates.</p>
|
||||
<p>20240912: Support for <code>maximum_mcu_duration</code> and <code>static_value</code> parameters in <code>[output_pin]</code> config sections have been removed. These options have been deprecated since 20240123.</p>
|
||||
<p>20240415: A <code>[virtual_sdcard]</code> konfigurációs szakaszban az <code>on_error_gcode</code> paraméter mostantól alapértelmezett. Ha ez a paraméter nincs megadva, az alapértelmezett érték mostantól <code>TURN_OFF_HEATERS</code>. Ha a korábbi viselkedést szeretnénk (hiba esetén a virtual_sdcard nyomtatása során nem teszünk alapértelmezett lépéseket), akkor a <code>on_error_gcode</code> paramétert üres értékkel definiáljuk.</p>
|
||||
<p>20240313: A <code>[nyomtató]</code> konfigurációs szakaszban található <code>max_accel_to_decel</code> paramétert elavultnak nyilvánítottuk. A <code>SET_VELOCITY_LIMIT</code> parancs <code>ACCEL_TO_DECEL</code> paramétere elavult. A <code>printer.toolhead.max_accel_to_decel</code> állapot eltávolításra került. Használd helyette a <a href="Config_Reference.html#printer">minimum_cruise_ratio paramétert</a>. Az elavult funkciók a közeljövőben eltávolításra kerülnek, és az időközbeni használatuk finoman eltérő viselkedést eredményezhet.</p>
|
||||
<p>20240215: Számos elavult funkciót eltávolítottunk. Az "NTC 100K beta 3950" használata termisztor névként megszűnt (elavult a 20211110 oldalon). A <code>SYNC_STEPPER_TO_EXTRUDER</code> és a <code>SET_EXTRUDER_STEP_DISTANCE</code> parancsok eltávolításra kerültek, és az extruder <code>shared_heater</code> konfigurációs opciója eltávolításra került (deprecated on 20220210). A bed_mesh <code>relative_reference_index</code> opció eltávolításra került (deprecated on 20230619).</p>
|
||||
|
|
|
|||
|
|
@ -938,6 +938,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1537,6 +1544,13 @@
|
|||
hd44780_spi kijelző
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1670,8 +1684,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -3032,6 +3046,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3631,6 +3652,13 @@
|
|||
hd44780_spi kijelző
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3764,8 +3792,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -5264,18 +5292,57 @@ cs_pin:
|
|||
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">¶</a></h3>
|
||||
<p>LIS2DW gyorsulásmérők támogatása.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis2dw]
|
||||
cs_pin:
|
||||
# Az érzékelő SPI engedélyező tűje. Ezt a paramétert meg kell adni.
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# A chippel való kommunikáció során használandó SPI-sebesség (hz-ben).
|
||||
# Az alapértelmezett érték 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:
|
||||
# A fenti paraméterek leírását az "általános SPI-beállítások" részben találod.
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# Lásd az "adxl345" részt a paraméterrel kapcsolatos információkért.
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="lis3dh">[lis3dh]<a class="headerlink" href="#lis3dh" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS3DH accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis3dh]
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="mpu9250">[mpu9250]<a class="headerlink" href="#mpu9250" title="Permanent link">¶</a></h3>
|
||||
|
|
@ -5301,53 +5368,58 @@ cs_pin:
|
|||
<p>A rezonancia tesztelés és az automatikus bemeneti alakító kalibráció támogatása. A modul legtöbb funkciójának használatához további szoftverfüggőségeket kell telepíteni; további információkért olvasd el a <a href="Measuring_Resonances.html">Rezonanciák mérése</a> és a <a href="G-Codes.html#resonance_tester">parancs hivatkozás</a> című dokumentumot. A rezonanciák mérése című útmutató <a href="Measuring_Resonances.html#max-smoothing">Max simítás</a> szakaszában további információkat talál a <code>max_smoothing</code> paraméterről és annak használatáról.</p>
|
||||
<div class="highlight"><pre><span></span><code>[resonance_tester]
|
||||
#probe_points:
|
||||
# A rezonanciák teszteléséhez szükséges pontok X, Y, Z koordinátáinak
|
||||
# listája (soronként egy pont). Legalább egy pont szükséges.
|
||||
# Győződj meg róla, hogy minden pont az X-Y síkban némi
|
||||
# biztonsági tartalékkal rendelkezik és (~ néhány centiméter)
|
||||
# elérhetőek a nyomtatófejjel.
|
||||
# A list of X, Y, Z coordinates of points (one point per line) to test
|
||||
# resonances at. At least one point is required. Make sure that all
|
||||
# points with some safety margin in XY plane (~a few centimeters)
|
||||
# are reachable by the toolhead.
|
||||
#accel_chip:
|
||||
# A mérésekhez használt gyorsulásmérő chip neve. Ha adxl345 chipet
|
||||
# explicit név nélkül definiálták, ez a paraméter egyszerűen
|
||||
# hivatkozhat rá "accel_chip: adxl345"-ként, ellenkező esetben egy
|
||||
# "accel_chip: adxl345" paramétert kell megadni. Explicit nevet is meg
|
||||
# kell adni, pl. "accel_chip: adxl345" my_chip_név".
|
||||
# Vagy ezt, vagy a következő két paramétert kell beállítani.
|
||||
# A name of the accelerometer chip to use for measurements. If
|
||||
# adxl345 chip was defined without an explicit name, this parameter
|
||||
# can simply reference it as "accel_chip: adxl345", otherwise an
|
||||
# explicit name must be supplied as well, e.g. "accel_chip: adxl345
|
||||
# my_chip_name". Either this, or the next two parameters must be
|
||||
# set.
|
||||
#accel_chip_x:
|
||||
#accel_chip_y:
|
||||
# Az egyes tengelyek méréséhez használandó gyorsulásmérő chipek
|
||||
# neve. Hasznos lehet például a tárgyasztal csúsztatós nyomtatónál, ha két
|
||||
# külön gyorsulásmérő van felszerelve a tárgyasztalra (az Y tengelyhez) és a
|
||||
# nyomtatófejre (az X tengelyhez). Ezek a paraméterek ugyanolyan
|
||||
# formátumúak, mint az "accel_chip" paraméter. Csak az 'accel_chip'
|
||||
# vagy ez a két paramétert kell megadni.
|
||||
# Names of the accelerometer chips to use for measurements for each
|
||||
# of the axis. Can be useful, for instance, on bed slinger printer,
|
||||
# if two separate accelerometers are mounted on the bed (for Y axis)
|
||||
# and on the toolhead (for X axis). These parameters have the same
|
||||
# format as 'accel_chip' parameter. Only 'accel_chip' or these two
|
||||
# parameters must be provided.
|
||||
#max_smoothing:
|
||||
# Az egyes tengelyek maximális bemeneti alakító simítása az alakító
|
||||
# automatikus kalibrálása során (a 'SHAPER_CALIBRATE' paranccsal).
|
||||
# Alapértelmezés szerint nincs megadva maximális simítás.
|
||||
# Lásd a Measuring_Resonances útmutatót. a funkció használatának
|
||||
# további részleteiért.
|
||||
# Maximum input shaper smoothing to allow for each axis during shaper
|
||||
# auto-calibration (with 'SHAPER_CALIBRATE' command). By default no
|
||||
# maximum smoothing is specified. Refer to Measuring_Resonances guide
|
||||
# for more details on using this feature.
|
||||
#move_speed: 50
|
||||
# The speed (in mm/s) to move the toolhead to and between test points
|
||||
# during the calibration. The default is 50.
|
||||
#min_freq: 5
|
||||
# Minimális frekvencia a rezonancia vizsgálatához.
|
||||
# Az alapértelmezett érték 5 Hz.
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 133.33
|
||||
# Maximális frekvencia a rezonancia vizsgálatához.
|
||||
# Az alapértelmezett érték 133,33 Hz.
|
||||
#accel_per_hz: 75
|
||||
# Ez a paraméter annak meghatározására szolgál, hogy egy adott
|
||||
# frekvencia teszteléséhez milyen gyorsulást használjunk:
|
||||
# accel = accel_per_hz * freq. Minél nagyobb az érték, annál nagyobb
|
||||
# a rezgések energiája. Az alapértelmezett értéknél alacsonyabbra is
|
||||
# beállítható, ha a rezonanciák túl erősek lesznek a nyomtatón.
|
||||
# Az alacsonyabb értékek azonban a nagyfrekvenciás rezonanciák
|
||||
# mérését pontatlanabbá teszik.
|
||||
# Az alapértelmezett érték 75 (mm/sec).
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 60
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
# value, the higher is the energy of the oscillations. Can be set to
|
||||
# a lower than the default value if the resonances get too strong on
|
||||
# the printer. However, lower values make measurements of
|
||||
# high-frequency resonances less precise. The default value is 75
|
||||
# (mm/sec).
|
||||
#hz_per_sec: 1
|
||||
# Meghatározza a teszt sebességét. A [min_freq, max_freq]
|
||||
# tartományban lévő összes frekvencia tesztelésekor a frekvencia
|
||||
# minden másodpercben hz_per_sec értékkel nő. A kis értékek
|
||||
# lassúvá teszik a tesztet, a nagy értékek pedig csökkentik a teszt
|
||||
# pontosságát. Az alapértelmezett érték 1.0 (Hz/sec == sec^-2).
|
||||
# Determines the speed of the test. When testing all frequencies in
|
||||
# range [min_freq, max_freq], each second the frequency increases by
|
||||
# hz_per_sec. Small values make the test slow, and the large values
|
||||
# will decrease the precision of the test. The default value is 1.0
|
||||
# (Hz/sec == sec^-2).
|
||||
#sweeping_accel: 400
|
||||
# An acceleration of slow sweeping moves. The default is 400 mm/sec^2.
|
||||
#sweeping_period: 1.2
|
||||
# A period of slow sweeping moves. Setting this parameter to 0
|
||||
# disables slow sweeping moves. Avoid setting it to a too small
|
||||
# non-zero value in order to not poison the measurements.
|
||||
# The default is 1.2 sec which is a good all-round choice.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="konfiguracios-fajl-segedletek">Konfigurációs fájl segédletek<a class="headerlink" href="#konfiguracios-fajl-segedletek" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5595,28 +5667,44 @@ sensor_type: ldc1612
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">¶</a></h3>
|
||||
<p>Eszköz az X portál csavarodása miatti pontatlan szondaleolvasások kompenzálására. Tekintsd meg az <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Útmutató</a> című dokumentumot a tünetekkel, a konfigurációval és a beállítással kapcsolatos részletesebb információkért.</p>
|
||||
<p>A tool to compensate for inaccurate probe readings due to twist in X or Y gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
|
||||
<div class="highlight"><pre><span></span><code>[axis_twist_compensation]
|
||||
#speed: 50
|
||||
# A nem tapintó mozgás sebessége (mm/s-ban) a kalibrálás során.
|
||||
# Az alapértelmezett 50.
|
||||
# The speed (in mm/s) of non-probing moves during the calibration.
|
||||
# The default is 50.
|
||||
#horizontal_move_z: 5
|
||||
# Az a magasság (mm-ben), ameddig a fejnek utasítani kell,
|
||||
# hogy mozogjon közvetlenül a tapintóművelet megkezdése előtt.
|
||||
# Az alapértelmezett az 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
|
||||
# Meghatározza a kalibrálás minimális X koordinátáját
|
||||
# Ennek az X koordinátának kell lennie, amely a fúvókát a kiindulási
|
||||
# kalibrációs pozícióba pozícionálja. Ezt a paramétert meg kell adni.
|
||||
# Defines the minimum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the starting
|
||||
# calibration position.
|
||||
calibrate_end_x: 200
|
||||
# Meghatározza a kalibrálás maximális X koordinátáját
|
||||
# Ennek az X-koordinátának kell lennie, amely a fúvókát a kalibrációs
|
||||
# véghelyzetbe pozícionálja. Ezt a paramétert meg kell adni.
|
||||
calibrate_y: 112,5
|
||||
# Meghatározza a kalibrálás Y koordinátáját. Ennek az Y koordinátának
|
||||
# kell lennie, amely a fúvókát pozícionálja a kalibrálási folyamat során.
|
||||
# Ezt a paramétert meg kell adni, és ajánlott, hogy az ágy
|
||||
# közepe közelében legyen
|
||||
# Defines the maximum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the ending
|
||||
# calibration position.
|
||||
calibrate_y: 112.5
|
||||
# Defines the Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle during the
|
||||
# calibration process. This parameter is recommended to
|
||||
# be near the center of the bed
|
||||
|
||||
# For Y-axis twist compensation, specify the following parameters:
|
||||
calibrate_start_y: ...
|
||||
# Defines the minimum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the starting
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_end_y: ...
|
||||
# Defines the maximum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the ending
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_x: ...
|
||||
# Defines the X coordinate of the calibration for Y axis twist compensation
|
||||
# This should be the X coordinate that positions the nozzle during the
|
||||
# calibration process for Y axis twist compensation. This parameter must be
|
||||
# provided and is recommended to be near the center of the bed.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="tovabbi-leptetomotorok-es-extruderek">További léptetőmotorok és extruderek<a class="headerlink" href="#tovabbi-leptetomotorok-es-extruderek" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5858,49 +5946,54 @@ extruder:
|
|||
#sensor_pin:
|
||||
#min_temp:
|
||||
#max_temp:
|
||||
# Hőmérsékletérzékelő konfigurációja.
|
||||
# A fenti paraméterek meghatározását lásd az „extruder” szakaszban.
|
||||
# Temperature sensor configuration.
|
||||
# See the "extruder" section for the definition of the above
|
||||
# parameters.
|
||||
#smooth_time:
|
||||
# Egy időérték (másodpercben), amely alatt a hőmérsékletmérések simításra
|
||||
# kerülnek a mérési zaj hatásának csökkentése érdekében.
|
||||
# Az alapértelmezett érték 2,0 másodperc.
|
||||
# A time value (in seconds) over which temperature measurements will
|
||||
# be smoothed to reduce the impact of measurement noise. The default
|
||||
# is 2.0 seconds.
|
||||
#gcode_id:
|
||||
# A paraméter definícióját lásd a „heater_generic” szakaszban.
|
||||
# See the "heater_generic" section for the definition of this
|
||||
# parameter.
|
||||
#speed:
|
||||
# A kalibrálás során az X-Y mozgások utazási sebessége [mm/s].
|
||||
# Az alapértelmezett a szonda által meghatározott sebesség.
|
||||
# The travel speed [mm/s] for xy moves during calibration. Default
|
||||
# is the speed defined by the probe.
|
||||
#horizontal_move_z:
|
||||
# A Z távolság [mm] az ágytól, amelyen az X-Y mozgások a
|
||||
# kalibrálás során történnek. Az alapértelmezett érték 2 mm.
|
||||
# The z distance [mm] from the bed at which xy moves will occur
|
||||
# during calibration. Default is 2mm.
|
||||
#resting_z:
|
||||
# A Z távolság [mm] az ágytól, amelyen a fej megpihen a
|
||||
# szondatekercs fűtése érdekében a kalibrálás során.
|
||||
# Az alapértelmezett érték .4mm
|
||||
# The z distance [mm] from the bed at which the tool will rest
|
||||
# to heat the probe coil during calibration. Default is .4mm
|
||||
#calibration_position:
|
||||
# Az X, Y, Z pozíció, ahová a fejet a szonda sodródás kalibrációjának
|
||||
# inicializálásakor mozgatni kell. Ez az a hely, ahol az első kézi mérés
|
||||
# történik. Ha elhagyod, az alapértelmezett viselkedés az, hogy a
|
||||
# fejet nem mozgatja az első kézi mérés előtt.
|
||||
# The X, Y, Z position where the tool should be moved when
|
||||
# probe drift calibration initializes. This is the location
|
||||
# where the first manual probe will occur. If omitted, the
|
||||
# default behavior is not to move the tool prior to the first
|
||||
# manual probe.
|
||||
#calibration_bed_temp:
|
||||
# A maximális biztonságos ágyhőmérséklet (C-ban), amelyet a szonda
|
||||
# melegítésére használnak a szonda sodródás kalibrálásakor. Ha be van
|
||||
# állítva, a kalibrációs eljárás az ágyfűtést az első mérés után bekapcsolja.
|
||||
# A kalibrációs eljárás befejeztével az ágy hőmérséklete nullára áll be.
|
||||
# Ha kihagyod, az alapértelmezett viselkedés az, hogy nem
|
||||
# állítja be az ágyhőmérsékletet.
|
||||
# The maximum safe bed temperature (in C) used to heat the probe
|
||||
# during probe drift calibration. When set, the calibration
|
||||
# procedure will turn on the bed after the first sample is
|
||||
# taken. When the calibration procedure is complete the bed
|
||||
# temperature will be set to zero. When omitted the default
|
||||
# behavior is not to set the bed temperature.
|
||||
#calibration_extruder_temp:
|
||||
# Az extruder hőmérséklete (C-ban), amelyet a sodródás kalibrálás során a
|
||||
# szonda beállít. Ha ezt az opciót megadjuk, az eljárás megvárja a megadott
|
||||
# hőmérséklet elérését, mielőtt az első kézi mérést kérné.
|
||||
# A kalibrációs eljárás befejezésekor az extruder hőmérséklete 0-ra áll be.
|
||||
# Ha elhagyod, az alapértelmezett viselkedés az, hogy nem
|
||||
# állítja be az extruder hőmérsékletét.
|
||||
# The extruder temperature (in C) set probe during drift calibration.
|
||||
# When this option is supplied the procedure will wait for until the
|
||||
# specified temperature is reached before requesting the first manual
|
||||
# probe. When the calibration procedure is complete the extruder
|
||||
# temperature will be set to 0. When omitted the default behavior is
|
||||
# not to set the extruder temperature.
|
||||
#extruder_heating_z: 50.
|
||||
# Az a Z hely, ahol az extruder fűtése bekapcsol, ha a
|
||||
# „calibration_extruder_temp” opció be van állítva.
|
||||
# Ajánlott az extruder fűtése az ágytól némi távolságra, hogy minimalizálja a
|
||||
# szondatekercs hőmérsékletére gyakorolt hatását.
|
||||
# Az alapértelmezett érték 50.
|
||||
# The Z location where extruder heating will occur if the
|
||||
# "calibration_extruder_temp" option is set. Its recommended to heat
|
||||
# the extruder some distance from the bed to minimize its impact on
|
||||
# the probe coil temperature. The default is 50.
|
||||
#max_validation_temp: 60.
|
||||
# The maximum temperature used to validate the calibration. It is
|
||||
# recommended to set this to a value between 100 and 120 for enclosed
|
||||
# printers. The default is 60.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="homerseklet-erzekelok">Hőmérséklet-érzékelők<a class="headerlink" href="#homerseklet-erzekelok" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -6914,59 +7007,56 @@ run_current:
|
|||
<p>Konfigurálj egy TMC2240 léptetőmotor-vezérlőt SPI buszon vagy UART-on keresztül. A funkció használatához adj meg egy konfigurációs részt egy "tmc2240" előtaggal, amelyet a megfelelő léptető konfigurációs szakasz neve követ (például "[tmc2240 stepper_x]").</p>
|
||||
<div class="highlight"><pre><span></span><code>[tmc2240 stepper_x]
|
||||
cs_pin:
|
||||
# A TMC2240 chip select vonalnak megfelelő tű. Ez a tű az
|
||||
# SPI-üzenetek kezdetekor alacsony értékre kerül, és az üzenet
|
||||
# befejezése után magas értékre emelkedik.
|
||||
# Ezt a paramétert meg kell adni.
|
||||
# The pin corresponding to the TMC2240 chip select line. This pin
|
||||
# will be set to low at the start of SPI messages and raised to high
|
||||
# after the message completes. This parameter must be provided.
|
||||
#spi_speed:
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# A fenti paraméterek leírását lásd a „közös SPI-beállítások”
|
||||
# szakaszban.
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#uart_pin:
|
||||
# A TMC2240 DIAG1/SW vonalához csatlakozó tű. Ha ez a
|
||||
# paraméter meg van adva, akkor SPI helyett UART
|
||||
# kommunikációt használnak.
|
||||
# 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:
|
||||
# Ezek a paraméterek egy SPI daisy chain konfigurálására
|
||||
# szolgálnak. A két paraméter meghatározza a léptető pozícióját
|
||||
# a láncban és a lánc teljes hosszát. Az 1. pozíció a MOSI jelre
|
||||
# csatlakozó léptetőnek felel meg. Az alapértelmezett
|
||||
# beállítás szerint nem használ SPI daisy chain-et.
|
||||
# These parameters configure an SPI daisy chain. The two parameters
|
||||
# define the stepper position in the chain and the total chain length.
|
||||
# Position 1 corresponds to the stepper that connects to the MOSI signal.
|
||||
# The default is to not use an SPI daisy chain.
|
||||
#interpolate: True
|
||||
# Ha igaz, engedélyezi a lépésinterpolációt (a meghajtó belsőleg
|
||||
# 256 mikrolépéses sebességgel lépked). Az alapértelmezett érték True.
|
||||
# If true, enable step interpolation (the driver will internally
|
||||
# step at a rate of 256 micro-steps). The default is True.
|
||||
run_current:
|
||||
# Az áram mennyisége (amperben RMS), amelyet a meghajtó a léptető
|
||||
# mozgatása során használjon. Ezt a paramétert meg kell adni.
|
||||
# The amount of current (in amps RMS) to configure the driver to use
|
||||
# during stepper movement. This parameter must be provided.
|
||||
#hold_current:
|
||||
# Az áram mennyisége (amperben RMS), amelyet a meghajtó akkor
|
||||
# használjon, amikor a léptető nem mozog. A hold_current beállítása
|
||||
# nem ajánlott (a részletekért lásd TMC_Drivers.md).
|
||||
# Az alapértelmezett érték nem csökkenti az áramot.
|
||||
# The amount of current (in amps RMS) to configure the driver to use
|
||||
# when the stepper is not moving. Setting a hold_current is not
|
||||
# recommended (see TMC_Drivers.md for details). The default is to
|
||||
# not reduce the current.
|
||||
#rref: 12000
|
||||
# Az IREF és GND közötti ellenállás ellenállása (ohmban).
|
||||
# Az alapértelmezett érték 12000.
|
||||
# The resistance (in ohms) of the resistor between IREF and GND. The
|
||||
# default is 12000.
|
||||
#stealthchop_threshold: 0
|
||||
# A sebesség (mm/s-ban), amelyre a „stealthChop” küszöbértéket
|
||||
# állítani kell. Amikor az alapértelmezett érték 0, ami kikapcsolja a
|
||||
# „stealthChop” üzemmódot.
|
||||
# The velocity (in mm/s) to set the "stealthChop" threshold to. When
|
||||
# set, "stealthChop" mode will be enabled if the stepper motor
|
||||
# velocity is below this value. The default is 0, which disables
|
||||
# "stealthChop" mode.
|
||||
#coolstep_threshold:
|
||||
# A sebesség (mm/s-ban), amelyre a TMC-meghajtó belső „CoolStep”
|
||||
# küszöbértékét állítani kell. Ha be van állítva, a CoolStep funkció akkor
|
||||
# lesz engedélyezve, ha a léptetőmotor sebessége ennek az értéknek a
|
||||
# közelében vagy fölött van. Fontos - ha a coolstep_threshold be van állítva
|
||||
# és „érzékelő nélküli kezdőpont” használatban van, akkor biztosítani kell,
|
||||
# hogy a kezdőpont sebesség a CoolStep küszöbérték felett legyen!
|
||||
# Alapértelmezés szerint a CoolStep funkciót nem engedélyezzük.
|
||||
# The velocity (in mm/s) to set the TMC driver internal "CoolStep"
|
||||
# threshold to. If set, the coolstep feature will be enabled when
|
||||
# the stepper motor velocity is near or above this value. Important
|
||||
# - if coolstep_threshold is set and "sensorless homing" is used,
|
||||
# then one must ensure that the homing speed is above the coolstep
|
||||
# threshold! The default is to not enable the coolstep feature.
|
||||
#high_velocity_threshold:
|
||||
# A sebesség (mm/s-ban), amelyre a TMC-meghajtó belső „nagy sebességű”
|
||||
# küszöbértékét (THIGH) kell beállítani. Ezt általában a „CoolStep” funkció
|
||||
# kikapcsolására használják nagy sebességeknél. Az alapértelmezés szerint
|
||||
# a TMC „nagy sebességű” küszöbértéket nem állítjuk be.
|
||||
# The velocity (in mm/s) to set the TMC driver internal "high
|
||||
# velocity" threshold (THIGH) to. This is typically used to disable
|
||||
# the "CoolStep" feature at high speeds. The default is to not set a
|
||||
# TMC "high velocity" threshold.
|
||||
#driver_MSLUT0: 2863314260
|
||||
#driver_MSLUT1: 1251300522
|
||||
#driver_MSLUT2: 608774441
|
||||
|
|
@ -6985,17 +7075,17 @@ run_current:
|
|||
#driver_START_SIN: 0
|
||||
#driver_START_SIN90: 247
|
||||
#driver_OFFSET_SIN90: 0
|
||||
# Ezek a mezők közvetlenül a Microstep Table regisztereit vezérlik. Az optimális
|
||||
# hullámtábla minden motorra jellemző, és az áramtól függően változhat.
|
||||
# Az optimális konfigurációban minimális lesz a nem lineáris léptetőmozgás
|
||||
# okozta nyomtatási lelet. A fent megadott értékek a meghajtó által használt
|
||||
# alapértelmezett értékek. Az értéket decimális egész számként kell megadni
|
||||
# (a hexa alak nem támogatott). A hullámtábla mezőinek kiszámításához lásd
|
||||
# a tmc2130 „Calculation Sheet” (számítási lap) című dokumentumot a Trinamic
|
||||
# weboldalán. Ezenkívül ez a meghajtó rendelkezik az OFFSET_SIN90 mezővel is,
|
||||
# amely a kiegyensúlyozatlan tekercsekkel rendelkező motorok hangolásához
|
||||
# használható. Lásd az adatlap „Szinuszhullám keresési táblázat” című szakaszát
|
||||
# az erről a mezőről és a hangolásról szóló információkért.
|
||||
# These fields control the Microstep Table registers directly. The optimal
|
||||
# wave table is specific to each motor and might vary with current. An
|
||||
# optimal configuration will have minimal print artifacts caused by
|
||||
# non-linear stepper movement. The values specified above are the default
|
||||
# values used by the driver. The value must be specified as a decimal integer
|
||||
# (hex form is not supported). In order to compute the wave table fields,
|
||||
# see the tmc2130 "Calculation Sheet" from the Trinamic website.
|
||||
# Additionally, this driver also has the OFFSET_SIN90 field which can be used
|
||||
# to tune a motor with unbalanced coils. See the `Sine Wave Lookup Table`
|
||||
# section in the datasheet for information about this field and how to tune
|
||||
# it.
|
||||
#driver_MULTISTEP_FILT: True
|
||||
#driver_IHOLDDELAY: 6
|
||||
#driver_IRUNDELAY: 4
|
||||
|
|
@ -7027,20 +7117,21 @@ run_current:
|
|||
#driver_SEIMIN: 0
|
||||
#driver_SFILT: 0
|
||||
#driver_SG4_ANGLE_OFFSET: 1
|
||||
# Állítsd be az adott regisztert a TMC2240 chip konfigurálása során.
|
||||
# Ez egyéni motorparaméterek beállítására használható. Az egyes
|
||||
# paraméterek alapértelmezett értékei a fenti listában a paraméter
|
||||
# neve mellett találhatók.
|
||||
#driver_SLOPE_CONTROL: 0
|
||||
# Set the given register during the configuration of the TMC2240
|
||||
# chip. This may be used to set custom motor parameters. The
|
||||
# defaults for each parameter are next to the parameter name in the
|
||||
# above list.
|
||||
#diag0_pin:
|
||||
#diag1_pin:
|
||||
# A TMC2240 chip egyik DIAG vonalához csatlakoztatott mikrokontrollertű.
|
||||
# Csak egyetlen diag tűt kell megadni. A tű „aktív alacsony”, ezért általában a
|
||||
# „^!” előtagot kell használni. Ennek beállítása létrehoz egy
|
||||
# „tmc2240_stepper_x:virtual_endstop” virtuális tűt, amely a stepper
|
||||
# endstop_pin-jeként használható. Ez lehetővé teszi a
|
||||
# „szenzor nélküli kezdőpont felvételt”. (Győződj meg róla, hogy a
|
||||
# driver_SGT-t is megfelelő érzékenységi értékre állítottad be.)
|
||||
# Az alapértelmezett beállítás nem engedélyezi az érzékelő nélküli kezdőpont.
|
||||
# The micro-controller pin attached to one of the DIAG lines of the
|
||||
# TMC2240 chip. Only a single diag pin should be specified. The pin
|
||||
# is "active low" and is thus normally prefaced with "^!". Setting
|
||||
# this creates a "tmc2240_stepper_x:virtual_endstop" virtual pin
|
||||
# which may be used as the stepper's endstop_pin. Doing this enables
|
||||
# "sensorless homing". (Be sure to also set driver_SGT to an
|
||||
# appropriate sensitivity value.) The default is to not enable
|
||||
# sensorless homing.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="tmc5160">[tmc5160]<a class="headerlink" href="#tmc5160" title="Permanent link">¶</a></h3>
|
||||
|
|
@ -7302,83 +7393,82 @@ wiper:
|
|||
<p>A mikrokontrollerhez csatlakoztatott kijelző támogatása.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type:
|
||||
# A használt LCD chip típusa. Ez lehet "hd44780", "hd44780_spi", "st7920",
|
||||
# "emulated_st7920", "uc1701", "ssd1306" vagy "sh1106". Az egyes
|
||||
# típusokról és az általuk biztosított további paraméterekről az alábbi
|
||||
# képernyőszakaszokban talál információkat.
|
||||
# Ezt a paramétert meg kell adni.
|
||||
# The type of LCD chip in use. This may be "hd44780", "hd44780_spi",
|
||||
# "aip31068_spi", "st7920", "emulated_st7920", "uc1701", "ssd1306", or
|
||||
# "sh1106".
|
||||
# See the display sections below for information on each type and
|
||||
# additional parameters they provide. This parameter must be
|
||||
# provided.
|
||||
#display_group:
|
||||
# A kijelzőn megjelenítendő display_data csoport neve. Ez szabályozza a
|
||||
# képernyő tartalmát (további információért lásd a „display_data” részt).
|
||||
# Az alapértelmezett _default_20x4 a hd44780-as kijelzőknél és a
|
||||
# _default_16x4 a többi képernyőnél.
|
||||
# The name of the display_data group to show on the display. This
|
||||
# controls the content of the screen (see the "display_data" section
|
||||
# for more information). The default is _default_20x4 for hd44780 or
|
||||
# aip31068_spi displays and _default_16x4 for other displays.
|
||||
#menu_timeout:
|
||||
# Időkorlát a menühöz. Ha ennyi másodpercig inaktív, az automatikusan
|
||||
# kilép a menüből, vagy visszatér a főmenübe, ha az automatikus indítás
|
||||
# engedélyezve van. Az alapértelmezett 0 másodperc (letiltva)
|
||||
# Timeout for menu. Being inactive this amount of seconds will
|
||||
# trigger menu exit or return to root menu when having autorun
|
||||
# enabled. The default is 0 seconds (disabled)
|
||||
#menu_root:
|
||||
# A főmenü rész neve, amely akkor jelenik meg, amikor a kódolóra kattint
|
||||
# a kezdőképernyőn. Az alapértelmezett érték a __main, és ez a
|
||||
# klippy/extras/display/menu.cfg fájlban meghatározott alapértelmezett
|
||||
# menüket mutatja.
|
||||
# Name of the main menu section to show when clicking the encoder
|
||||
# on the home screen. The defaults is __main, and this shows the
|
||||
# the default menus as defined in klippy/extras/display/menu.cfg
|
||||
#menu_reverse_navigation:
|
||||
# Ha engedélyezve van, a listában történő navigáció fel és lefelé irányát
|
||||
# váltja. Az alapértelmezett érték False. Ez a paraméter nem kötelező.
|
||||
# When enabled it will reverse up and down directions for list
|
||||
# navigation. The default is False. This parameter is optional.
|
||||
#encoder_pins:
|
||||
# A kódolóhoz csatlakoztatott érintkezők. A kódoló használatakor 2
|
||||
# érintkezőt kell biztosítani. Ezt a paramétert a menü használatakor kell
|
||||
# megadni.
|
||||
# The pins connected to encoder. 2 pins must be provided when using
|
||||
# encoder. This parameter must be provided when using menu.
|
||||
#encoder_steps_per_detent:
|
||||
# Hány lépést ad ki a kódoló reteszelésenként ("kattintás"). Ha a
|
||||
# kódolónak két reteszre van szüksége a bejegyzések közötti mozgáshoz,
|
||||
# vagy két bejegyzést mozgat meg egy rögzítésből, próbáld meg ezt
|
||||
# megváltoztatni. A megengedett értékek 2 (féllépcsős) vagy
|
||||
# 4 (teljes lépés). Az alapértelmezett érték a 4.
|
||||
# How many steps the encoder emits per detent ("click"). If the
|
||||
# encoder takes two detents to move between entries or moves two
|
||||
# entries from one detent, try changing this. Allowed values are 2
|
||||
# (half-stepping) or 4 (full-stepping). The default is 4.
|
||||
#click_pin:
|
||||
# Az „Enter” gombhoz vagy a kódoló „kattintásához” csatlakoztatott tű.
|
||||
# Ezt a paramétert a menü használatakor kell megadni.
|
||||
# Az „analog_range_click_pin” konfigurációs paraméter jelenléte ezt a
|
||||
# paramétert digitálisról analógra változtatja.
|
||||
# The pin connected to 'enter' button or encoder 'click'. This
|
||||
# parameter must be provided when using menu. The presence of an
|
||||
# 'analog_range_click_pin' config parameter turns this parameter
|
||||
# from digital to analog.
|
||||
#back_pin:
|
||||
# A „vissza” gombhoz csatlakoztatott tű. Ez a paraméter nem kötelező,
|
||||
# a menü enélkül is használható. Az „analog_range_back_pin”
|
||||
# konfigurációs paraméter jelenléte ezt a paramétert digitálisról
|
||||
# analógra változtatja.
|
||||
# The pin connected to 'back' button. This parameter is optional,
|
||||
# menu can be used without it. The presence of an
|
||||
# 'analog_range_back_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#up_pin:
|
||||
# A tű a „fel” gombhoz csatlakozik. Ezt a paramétert kódoló nélküli menü
|
||||
# használatakor kell megadni. Az „analog_range_up_pin” konfigurációs
|
||||
# paraméter jelenléte ezt a paramétert digitálisról analógra változtatja.
|
||||
# The pin connected to 'up' button. This parameter must be provided
|
||||
# when using menu without encoder. The presence of an
|
||||
# 'analog_range_up_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#down_pin:
|
||||
# A tű a „le” gombhoz csatlakozik. Ezt a paramétert kódoló nélküli menü
|
||||
# használatakor kell megadni. Az „analog_range_down_pin” konfigurációs
|
||||
# paraméter jelenléte ezt a paramétert digitálisról analógra változtatja.
|
||||
# The pin connected to 'down' button. This parameter must be
|
||||
# provided when using menu without encoder. The presence of an
|
||||
# 'analog_range_down_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#kill_pin:
|
||||
# A tű a „kill” gombhoz csatlakozik. Ez a gomb vészleállítást hív.
|
||||
# Az „analog_range_kill_pin” konfigurációs paraméter jelenléte ezt a
|
||||
# paramétert digitálisról analógra változtatja.
|
||||
# The pin connected to 'kill' button. This button will call
|
||||
# emergency stop. The presence of an 'analog_range_kill_pin' config
|
||||
# parameter turns this parameter from digital to analog.
|
||||
#analog_pullup_resistor: 4700
|
||||
# Az analóg gombhoz csatlakoztatott felhúzó ellenállása (ohmban).
|
||||
# Az alapértelmezett érték 4700 ohm.
|
||||
# The resistance (in ohms) of the pullup attached to the analog
|
||||
# button. The default is 4700 ohms.
|
||||
#analog_range_click_pin:
|
||||
# Az „Enter” gomb ellenállási tartománya.
|
||||
# Analóg gomb használata esetén a tartomány minimális és
|
||||
# maximális értékeit vesszővel elválasztva kell megadni.
|
||||
# The resistance range for a 'enter' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_back_pin:
|
||||
# A „vissza” gomb ellenállási tartománya.
|
||||
# Analóg gomb használata esetén a tartomány minimális és
|
||||
# maximális értékeit vesszővel elválasztva kell megadni.
|
||||
# The resistance range for a 'back' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_up_pin:
|
||||
# A „fel” gomb ellenállási tartománya.
|
||||
# Analóg gomb használata esetén a tartomány minimális és
|
||||
# maximális értékeit vesszővel elválasztva kell megadni.
|
||||
# The resistance range for a 'up' button. Range minimum and maximum
|
||||
# comma-separated values must be provided when using analog button.
|
||||
#analog_range_down_pin:
|
||||
# A „le” gomb ellenállási tartománya.
|
||||
# Analóg gomb használata esetén a tartomány minimális és
|
||||
# maximális értékeit vesszővel elválasztva kell megadni.
|
||||
# The resistance range for a 'down' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_kill_pin:
|
||||
# A „kill” gomb ellenállási tartománya.
|
||||
# Analóg gomb használata esetén a tartomány minimális és
|
||||
# maximális értékeit vesszővel elválasztva kell megadni.
|
||||
# The resistance range for a 'kill' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="hd44780-kijelzo">hd44780 kijelző<a class="headerlink" href="#hd44780-kijelzo" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -7431,6 +7521,26 @@ spi_software_miso_pin:
|
|||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="aip31068_spi-display">aip31068_spi display<a class="headerlink" href="#aip31068_spi-display" title="Permanent link">¶</a></h4>
|
||||
<p>Information on configuring an aip31068_spi display - a very similar to hd44780_spi a 20x04 (20 symbols by 4 lines) display with slightly different internal protocol.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type: aip31068_spi
|
||||
latch_pin:
|
||||
spi_software_sclk_pin:
|
||||
spi_software_mosi_pin:
|
||||
spi_software_miso_pin:
|
||||
# The pins connected to the shift register controlling the display.
|
||||
# The spi_software_miso_pin needs to be set to an unused pin of the
|
||||
# printer mainboard as the shift register does not have a MISO pin,
|
||||
# but the software spi implementation requires this pin to be
|
||||
# configured.
|
||||
#line_length:
|
||||
# Set the number of characters per line for an hd44780 type lcd.
|
||||
# Possible values are 20 (default) and 16. The number of lines is
|
||||
# fixed to 4.
|
||||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="st7920-kijelzo">st7920 kijelző<a class="headerlink" href="#st7920-kijelzo" title="Permanent link">¶</a></h4>
|
||||
<p>Információk az ST7920 kijelzők konfigurálásáról (amelyet a "RepRapDiscount 12864 Full Graphic Smart Controller" típusú kijelzőknél használnak).</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
|
|
@ -7793,7 +7903,7 @@ sensor_type:
|
|||
# lásd alább.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="xh711">XH711<a class="headerlink" href="#xh711" title="Permanent link">¶</a></h4>
|
||||
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">¶</a></h4>
|
||||
<p>Ez egy 24 bites alacsony mintavételi sebességű chip, amely "bit-bang" kommunikációt használ. Nyomtatószál mérlegekhez alkalmas.</p>
|
||||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
sensor_type: hx711
|
||||
|
|
@ -7838,30 +7948,48 @@ dout_pin:
|
|||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
sensor_type: ads1220
|
||||
cs_pin:
|
||||
# Az ADS1220 chipkiválasztó vonalához csatlakozó tű.
|
||||
# Ezt a paramétert meg kell adni.
|
||||
# The pin connected to the ADS1220 chip select line. This parameter must
|
||||
# be provided.
|
||||
#spi_speed: 512000
|
||||
# Ez a chip 2 sebességet támogat: 256000 vagy 512000. A gyorsabb sebesség
|
||||
# csak a Turbo mintavételi sebességek egyikének használata esetén engedélyezett.
|
||||
# A megfelelő spi_speed a mintavételi sebesség alapján kerül kiválasztásra.
|
||||
# This chip supports 2 speeds: 256000 or 512000. The faster speed is only
|
||||
# enabled when one of the Turbo sample rates is used. The correct spi_speed
|
||||
# is selected based on the sample rate.
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# Lásd a "közös SPI-beállítások" című fejezetben a fenti paraméterek leírását.
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
data_ready_pin:
|
||||
# Az ADS1220 adatkész vonalához csatlakoztatott tű.
|
||||
# Ezt a paramétert meg kell adni.
|
||||
# Pin connected to the ADS1220 data ready line. This parameter must be
|
||||
# provided.
|
||||
#gain: 128
|
||||
# Érvényes erősítési értékek a következők: 128, 64, 32, 16, 8, 4, 2, 1
|
||||
# Az alapértelmezett érték 128
|
||||
# Valid gain values are 128, 64, 32, 16, 8, 4, 2, 1
|
||||
# The default is 128
|
||||
#pga_bypass: False
|
||||
# Disable the internal Programmable Gain Amplifier. If
|
||||
# True the PGA will be disabled for gains 1, 2, and 4. The PGA is always
|
||||
# enabled for gain settings 8 to 128, regardless of the pga_bypass setting.
|
||||
# If AVSS is used as an input pga_bypass is forced to True.
|
||||
# The default is False.
|
||||
#sample_rate: 660
|
||||
# Ez a chip kétféle mintavételi sebességtartományt támogat: Normál és Turbo.
|
||||
# Turbo üzemmódban a chip c belső órája kétszer olyan gyorsan jár, és az SPI
|
||||
# kommunikációs sebesség is megduplázódik.
|
||||
# Normál mintavételi sebességek: 20, 45, 90, 175, 330, 600, 1000
|
||||
# Turbó mintavételi sebességek: 40, 90, 180, 350, 660, 1200, 2000
|
||||
# Az alapértelmezett érték 660.
|
||||
# This chip supports two ranges of sample rates, Normal and Turbo. In turbo
|
||||
# mode the chip's internal clock runs twice as fast and the SPI communication
|
||||
# speed is also doubled.
|
||||
# Normal sample rates: 20, 45, 90, 175, 330, 600, 1000
|
||||
# Turbo sample rates: 40, 90, 180, 350, 660, 1200, 2000
|
||||
# The default is 660
|
||||
#input_mux:
|
||||
# Input multiplexer configuration, select a pair of pins to use. The first pin
|
||||
# is the positive, AINP, and the second pin is the negative, AINN. Valid
|
||||
# values are: 'AIN0_AIN1', 'AIN0_AIN2', 'AIN0_AIN3', 'AIN1_AIN2', 'AIN1_AIN3',
|
||||
# 'AIN2_AIN3', 'AIN1_AIN0', 'AIN3_AIN2', 'AIN0_AVSS', 'AIN1_AVSS', 'AIN2_AVSS'
|
||||
# and 'AIN3_AVSS'. If AVSS is used the PGA is bypassed and the pga_bypass
|
||||
# setting will be forced to True.
|
||||
# The default is AIN0_AIN1.
|
||||
#vref:
|
||||
# The selected voltage reference. Valid values are: 'internal', 'REF0', 'REF1'
|
||||
# and 'analog_supply'. Default is 'internal'.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="alaplap-specifikus-hardvertamogatas">Alaplap specifikus hardvertámogatás<a class="headerlink" href="#alaplap-specifikus-hardvertamogatas" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -8007,30 +8135,30 @@ serial:
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<p>Mágneses Hall-szögérzékelő támogatása A1333, AS5047D vagy TLE5012B SPI-chipek használatával a léptetőmotorok szögtengelyének méréseinek leolvasásához. A mérések az <a href="API_Server.html">API Szerver</a> és a <a href="Debugging.html#motion-analysis-and-data-logging">mozgáselemző eszköz</a> segítségével érhetők el. A rendelkezésre álló parancsokat lásd a <a href="G-Codes.html#angle">G-kód hivatkozásban</a>.</p>
|
||||
<p>Magnetic hall angle sensor support for reading stepper motor angle shaft measurements using a1333, as5047d, mt6816, mt6826s, or tle5012b SPI chips. The measurements are available via the <a href="API_Server.html">API Server</a> and <a href="Debugging.html#motion-analysis-and-data-logging">motion analysis tool</a>. See the <a href="G-Codes.html#angle">G-Code reference</a> for available commands.</p>
|
||||
<div class="highlight"><pre><span></span><code>[angle my_angle_sensor]
|
||||
sensor_type:
|
||||
# A mágneses Hall érzékelő chip típusa. A választható lehetőségek:
|
||||
# „a1333”, „as5047d” és „tle5012b”. Ezt a paramétert meg kell adni.
|
||||
# The type of the magnetic hall sensor chip. Available choices are
|
||||
# "a1333", "as5047d", "mt6816", "mt6826s", and "tle5012b". This parameter must be
|
||||
# specified.
|
||||
#sample_period: 0.000400
|
||||
# A mérések során használandó lekérdezési időszak (másodpercben).
|
||||
# Az alapértelmezett érték 0,000400 (ami másodpercenként
|
||||
# 2500 minta).
|
||||
# The query period (in seconds) to use during measurements. The
|
||||
# default is 0.000400 (which is 2500 samples per second).
|
||||
#stepper:
|
||||
# Annak a léptetőnek a neve, amelyhez a szögérzékelő csatlakoztatva
|
||||
# van (pl. "stepper_x"). Ennek az értéknek a beállítása engedélyezi a
|
||||
# szögkalibráló eszközt. A funkció használatához telepíteni kell a
|
||||
# Python "numpy" csomagot. Az alapértelmezett beállítás nem
|
||||
# engedélyezi a szögérzékelő szögkalibrálását.
|
||||
# The name of the stepper that the angle sensor is attached to (eg,
|
||||
# "stepper_x"). Setting this value enables an angle calibration
|
||||
# tool. To use this feature, the Python "numpy" package must be
|
||||
# installed. The default is to not enable angle calibration for the
|
||||
# angle sensor.
|
||||
cs_pin:
|
||||
# Az érzékelő SPI engedélyező tűje. Ezt a paramétert meg kell adni.
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#spi_speed:
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# A fenti paraméterek leírását az „általános SPI-beállítások”
|
||||
# részben találja.
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="gyakori-buszparameterek">Gyakori buszparaméterek<a class="headerlink" href="#gyakori-buszparameterek" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -8056,7 +8184,7 @@ cs_pin:
|
|||
<h3 id="gyakori-i2c-beallitasok">Gyakori I2C beállítások<a class="headerlink" href="#gyakori-i2c-beallitasok" title="Permanent link">¶</a></h3>
|
||||
<p>A következő paraméterek általában az I2C-buszt használó eszközökhöz állnak rendelkezésre.</p>
|
||||
<p>Vedd figyelembe, hogy a Klipper jelenlegi mikrokontroller I2C támogatása általában nem tolerálja a hálózati zajt. Az I2C vezetékek nem várt hibái a Klipper futásidejű hibaüzenetét eredményezhetik. A Klipper hibaelhárítási támogatása az egyes mikrokontroller-típusoknál eltérő. Általában csak olyan I2C eszközök használata ajánlott, amelyek ugyanazon a nyomtatott áramköri lapon vannak, mint a mikrokontroller.</p>
|
||||
<p>A legtöbb Klipper mikrokontroller implementáció csak az <code>i2c_speed</code> 100000 (<em>standard mód</em>, 100kbit/s) sebességet támogatja. A Klipper "Linux" mikrokontroller támogatja a 400000 sebességet (<em>fast mode</em>, 400kbit/s), de ezt <a href="RPi_microcontroller.html#optional-enabling-i2c">z operációs rendszerben</a> kell beállítani, és az <code>i2c_speed</code> paramétert egyébként figyelmen kívül hagyja. A Klipper "RP2040" mikrokontroller és az ATmega AVR család 400000-es sebességet támogat az <code>i2c_speed</code> paraméteren keresztül. Az összes többi Klipper mikrovezérlő 100000-es sebességet használ, és figyelmen kívül hagyja az <code>i2c_speed</code> paramétert.</p>
|
||||
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000 (<em>standard mode</em>, 100kbit/s). The Klipper "Linux" micro-controller supports a 400000 speed (<em>fast mode</em>, 400kbit/s), but it must be <a href="RPi_microcontroller.html#optional-enabling-i2c">set in the operating system</a> and the <code>i2c_speed</code> parameter is otherwise ignored. The Klipper "RP2040" micro-controller and ATmega AVR family and some STM32 (F0, G0, G4, L4, F7, H7) support a rate of 400000 via the <code>i2c_speed</code> parameter. All other Klipper micro-controllers use a 100000 rate and ignore the <code>i2c_speed</code> parameter.</p>
|
||||
<div class="highlight"><pre><span></span><code>#i2c_address:
|
||||
# Az eszköz I2C címe. Ezt decimális számként kell megadni (nem
|
||||
# hexadecimális formában).
|
||||
|
|
|
|||
|
|
@ -1412,7 +1412,7 @@
|
|||
# temperature probe configuration...
|
||||
</code></pre></div>
|
||||
|
||||
<p>A <a href="Config_Reference.html#temperature_probe">konfigurációs hivatkozás</a> további részleteket tartalmaz a <code>temperature_probe</code> konfigurálásáról. Javasoljuk a <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code> és <code>calibration_bed_temp</code> opciók konfigurálását, mivel ez automatizálja az alább ismertetett lépések egy részét.</p>
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below. If the printer to be calibrated is enclosed, it is strongly recommended to set the <code>max_validation_temp</code> option to a value between 100 and 120.</p>
|
||||
<p>Az örvényszondák gyártói kínálhatnak készleten lévő elhajlás kalibrációt, amelyet manuálisan hozzá lehet adni a <code>[probe_eddy_current]</code> szakasz <code>drift_calibration</code> opciójához. Ha nem, vagy ha a készletkalibráció nem működik jól a rendszereden, a <code>temperature_probe</code> modul a <code>TEMPERATURE_PROBE_CALIBRATE</code> G-kód parancs segítségével manuális kalibrálási eljárást kínál.</p>
|
||||
<p>A kalibrálás elvégzése előtt a felhasználónak tudnia kell, hogy mi a maximálisan elérhető hőmérsékletű szondatekercs hőmérséklete. Ezt a hőmérsékletet kell használni a <code>TEMPERATURE_PROBE_CALIBRATE</code> parancs <code>TARGET</code> paraméterének beállításához. A cél a lehető legszélesebb hőmérséklet-tartományban történő kalibrálás, ezért ajánlatos, hogy hidegen kezdjük, és a tekercset a maximálisan elérhető hőmérsékleten fejezzük be a kalibrálást.</p>
|
||||
<p>Miután a <code>[temperature_probe]</code>-t konfiguráltuk, a következő lépésekkel végezhető el a termikus elhajlás kalibrálás:</p>
|
||||
|
|
|
|||
|
|
@ -1542,6 +1542,16 @@
|
|||
<td>2634K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>RP2350</td>
|
||||
<td>4167K</td>
|
||||
<td>2663K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SAME70</td>
|
||||
<td>6667K</td>
|
||||
<td>4737K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>STM32H743</td>
|
||||
<td>9091K</td>
|
||||
<td>6061K</td>
|
||||
|
|
|
|||
|
|
@ -869,6 +869,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1958,6 +1965,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3089,6 +3116,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4178,6 +4212,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4750,6 +4804,11 @@
|
|||
<p>A következő parancsok akkor érhetők el, ha az <a href="Config_Reference.html#angle">szög konfigurációs szakasz</a> engedélyezve van.</p>
|
||||
<h4 id="angle_calibrate">ANGLE_CALIBRATE<a class="headerlink" href="#angle_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CALIBRATE CHIP=<chip_name></code>: Szögkalibrálás végrehajtása az adott érzékelőn (kell lennie egy <code>[angle chip_name]</code> konfigurációs szakasznak, amely megadta a <code>stepper</code> paramétert). FONTOS! Ez az eszköz a normál kinematikai határértékek ellenőrzése nélkül adja ki a léptetőmotor mozgását. Ideális esetben a motort a kalibrálás elvégzése előtt le kell választani az adott kocsiról. Ha a léptetőmotor nem kapcsolható le a nyomtatóról, győződj meg róla, hogy a kocsi a kalibrálás megkezdése előtt a sín közepénél van. (A léptetőmotor két teljes fordulatot előre vagy hátra mozoghat a teszt során.) A teszt elvégzése után használd a <code>SAVE_CONFIG</code> parancsot a kalibrációs adatok printer.cfg fájlba történő mentéséhez. Az eszköz használatához telepíteni kell a Python "numpy" csomagot (további információkért lásd a <a href="Measuring_Resonances.html#software-installation">rezonancia mérése dokumentumot</a>.</p>
|
||||
<h4 id="angle_chip_calibrate">ANGLE_CHIP_CALIBRATE<a class="headerlink" href="#angle_chip_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CHIP_CALIBRATE CHIP=<chip_name></code>: Perform internal sensor calibration, if implemented (MT6826S/MT6835).</p>
|
||||
<ul>
|
||||
<li><strong>MT68XX</strong>: The motor should be disconnected from any printer carriage before performing calibration. After calibration, the sensor should be reset by disconnecting the power.</li>
|
||||
</ul>
|
||||
<h4 id="angle_debug_read">ANGLE_DEBUG_READ<a class="headerlink" href="#angle_debug_read" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_DEBUG_READ CHIP=<config_name> REG=<register></code>: A "regiszter" (pl. 44 vagy 0x2C) érzékelőregiszter lekérdezése. Hasznos lehet hibakeresési célokra. Ez csak a TLE5012B chipek esetében érhető el.</p>
|
||||
<h4 id="angle_debug_write">ANGLE_DEBUG_WRITE<a class="headerlink" href="#angle_debug_write" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4758,7 +4817,12 @@
|
|||
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
|
||||
section</a> is enabled.</p>
|
||||
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=<value>]</code>: Elindítja az X twist kalibrációs varázslót. A "SAMPLE_COUNT" meghatározza az X tengely mentén a kalibráláshoz szükséges pontok számát, az alapértelmezett érték pedig 3.</p>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]</code></p>
|
||||
<p>Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.</p>
|
||||
<ul>
|
||||
<li><strong>AXIS:</strong> Define the axis (<code>X</code> or <code>Y</code>) for which the twist compensation will be calibrated. If not specified, the axis defaults to <code>'X'</code>.</li>
|
||||
<li><strong>AUTO:</strong> Enables automatic calibration mode. When <code>AUTO=True</code>, the calibration will run for both the X and Y axes. In this mode, <code>AXIS</code> cannot be specified. If both <code>AXIS</code> and <code>AUTO</code> are provided, an error will be raised.</li>
|
||||
</ul>
|
||||
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">¶</a></h3>
|
||||
<p>A következő parancsok akkor érhetők el, ha a <a href="Config_Reference.html#bed_mesh">bed_mesh konfigurációs szakasz</a> engedélyezve van (lásd még a <a href="Bed_Mesh.html">tárgyasztal háló útmutatót</a>).</p>
|
||||
<h4 id="bed_mesh_calibrate">BED_MESH_CALIBRATE<a class="headerlink" href="#bed_mesh_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4862,6 +4926,7 @@ section</a> is enabled.</p>
|
|||
<p>A következő parancs akkor érhető el, ha a <a href="Config_Reference.html#fan_generic">fan_generic konfigurációs szakasz</a> engedélyezve van.</p>
|
||||
<h4 id="set_fan_speed">SET_FAN_SPEED<a class="headerlink" href="#set_fan_speed" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_FAN_SPEED FAN=config_name SPEED=<speed></code> Ez a parancs beállítja a ventilátor sebességét. "speed" 0.0 és 1.0 között kell lennie.</p>
|
||||
<p><code>SET_FAN_SPEED PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given fan. For example, if one defined a <code>[display_template my_fan_template]</code> config section then one could assign <code>TEMPLATE=my_fan_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the fan will be automatically set to the resulting speed. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_FAN_SPEED</code> commands to manage the values directly).</p>
|
||||
<h3 id="filament_switch_sensor">[filament_switch_sensor]<a class="headerlink" href="#filament_switch_sensor" title="Permanent link">¶</a></h3>
|
||||
<p>A következő parancs akkor érhető el, ha a <a href="Config_Reference.html#filament_switch_sensor">filament_switch_sensor</a> vagy <a href="Config_Reference.html#filament_motion_sensor">filament_motion_sensor</a> konfigurációs szakasz engedélyezve van.</p>
|
||||
<h4 id="query_filament_sensor">QUERY_FILAMENT_SENSOR<a class="headerlink" href="#query_filament_sensor" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4886,7 +4951,7 @@ section</a> is enabled.</p>
|
|||
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>FORCE_MOVE STEPPER=<config_name> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]</code>: Ez a parancs az adott léptetőmotort az adott távolságon (mm-ben) a megadott állandó sebességgel (mm/sec-ben) kényszerrel mozgatja. Ha az ACCEL meg van adva, és nagyobb, mint nulla, akkor a megadott gyorsulás (mm/sec^2-en) kerül alkalmazásra; egyébként nem történik gyorsítás. Nem történik határérték ellenőrzés; nem történik kinematikai frissítés; a tengelyen lévő más párhuzamos léptetők nem kerülnek mozgatásra. Legyél óvatos, mert a helytelen parancs kárt okozhat! A parancs használata szinte biztosan helytelen állapotba hozza az alacsony szintű kinematikát; a kinematika visszaállításához adj ki utána egy G28 parancsot. Ez a parancs alacsony szintű diagnosztikára és hibakeresésre szolgál.</p>
|
||||
<h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>]</code>: Kényszeríti az alacsony szintű kinematikai kódot, hogy azt higgye, a nyomtatófej a megadott cartesian pozícióban van. Ez egy diagnosztikai és hibakeresési parancs; használd a SET_GCODE_OFFSET és/vagy a G92 parancsot a normál tengelytranszformációkhoz. Ha egy tengely nincs megadva, akkor alapértelmezés szerint az a pozíció lesz, ahová a fejet utoljára parancsolták. A helytelen vagy érvénytelen pozíció beállítása belső szoftverhibához vezethet. Ez a parancs érvénytelenítheti a későbbi határérték ellenőrzéseket; a kinematika visszaállításához adj ki egy G28 parancsot.</p>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an axis is not specified then it will default to the position that the head was last commanded to. Setting an incorrect or invalid position may lead to internal software errors. Use the CLEAR parameter to forget the homing state for the given axes. Note that CLEAR will not override the previous functionality; if an axis is not specified to CLEAR it will have its kinematic position set as per above. This command may invalidate future boundary checks; issue a G28 afterwards to reset the kinematics.</p>
|
||||
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">¶</a></h3>
|
||||
<p>A G-kód modul automatikusan betöltődik.</p>
|
||||
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4980,6 +5045,7 @@ section</a> is enabled.</p>
|
|||
<p>A következő parancs akkor érhető el, ha az <a href="Config_Reference.html#output_pin">output_pin konfigurációs szakasz</a> engedélyezve van.</p>
|
||||
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value></code>: A tűt a megadott kimeneti <code>VALUE</code> értékre állítja. A VALUE-nak 0-nak vagy 1-nek kell lennie a "digitális" kimeneti tűk esetében. PWM tűk esetén 0.0 és 1.0 közötti értékre állítsuk be, vagy 0.0 és <code>scale</code> közötti értékre, ha az output_pin konfigurációs szakaszban van beállítva a skála.</p>
|
||||
<p><code>SET_PIN PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given pin. For example, if one defined a <code>[display_template my_pin_template]</code> config section then one could assign <code>TEMPLATE=my_pin_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the pin will be automatically set to the resulting value. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_PIN</code> commands to manage the values directly).</p>
|
||||
<h3 id="palette2">[palette2]<a class="headerlink" href="#palette2" title="Permanent link">¶</a></h3>
|
||||
<p>A következő parancsok akkor érhetők el, ha a <a href="Config_Reference.html#palette2">palette2 konfigurációs szakasz</a> engedélyezve van.</p>
|
||||
<p>A paletta nyomtatások speciális OCode-ok (Omega-kódok) beágyazásával működnek a G-kód fájlban:</p>
|
||||
|
|
@ -5037,6 +5103,10 @@ section</a> is enabled.</p>
|
|||
<p>A következő parancs akkor érhető el, ha a <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time config section</a> engedélyezve van.</p>
|
||||
<h4 id="set_pin_1">SET_PIN<a class="headerlink" href="#set_pin_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value> [CYCLE_TIME=<cycle_time>]</code>: Ez a parancs hasonlóan működik, mint a <a href="#output_pin">output_pin</a> SET_PIN parancsok. A parancs itt támogatja egy explicit ciklusidő beállítását a CYCLE_TIME paraméter segítségével (másodpercben megadva). Megjegyzendő, hogy a CYCLE_TIME paraméter nem tárolódik a SET_PIN parancsok között (minden explicit CYCLE_TIME paraméter nélküli SET_PIN parancs a pwm_cycle_time config szakaszban megadott <code>cycle_time</code> értéket használja).</p>
|
||||
<h3 id="quad_gantry_level">[quad_gantry_level]<a class="headerlink" href="#quad_gantry_level" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#quad_gantry_level">quad_gantry_level config section</a> is enabled.</p>
|
||||
<h4 id="quad_gantry_level_1">QUAD_GANTRY_LEVEL<a class="headerlink" href="#quad_gantry_level_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>QUAD_GANTRY_LEVEL [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">¶</a></h3>
|
||||
<p>A query_adc modul automatikusan betöltődik.</p>
|
||||
<h4 id="query_adc_1">QUERY_ADC<a class="headerlink" href="#query_adc_1" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -5053,9 +5123,9 @@ section</a> is enabled.</p>
|
|||
<h4 id="measure_axes_noise">MEASURE_AXES_NOISE<a class="headerlink" href="#measure_axes_noise" title="Permanent link">¶</a></h4>
|
||||
<p><code>MEASURE_AXES_NOISE</code>: Az összes engedélyezett gyorsulásmérő chip összes tengelyének zaját méri és adja ki.</p>
|
||||
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">¶</a></h4>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> OUTPUT=<resonances,raw_data> [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]</code>: Lefuttatja a rezonanciatesztet a kért "tengely" összes konfigurált mérőpontjában, és méri a gyorsulást az adott tengelyhez konfigurált gyorsulásmérő chipek segítségével. A "tengely" lehet X vagy Y, vagy megadhat egy tetszőleges irányt <code>AXIS=dx,dy</code>, ahol dx és dy egy irányvektort meghatározó lebegőpontos szám (pl. <code>AXIS=X</code>, <code>AXIS=Y</code>, vagy <code>AXIS=1,-1</code> az átlós irány meghatározásához). Vegyük figyelembe, hogy az <code>AXIS=dx,dy</code> és az <code>AXIS=-dx,-dy</code> egyenértékű. Az <code>adxl345_chip_name</code> lehet egy vagy több konfigurált adxl345 chip, vesszővel elválasztva, például <code>CHIPS="adxl345, adxl345 rpi"</code>. Megjegyzendő, hogy az <code>adxl345</code> elhagyható a nevesített adxl345 chipeknél. Ha POINT van megadva, az felülírja a <code>[resonance_tester]</code> alatt konfigurált pontokat. Ha <code>INPUT_SHAPING=0</code> vagy nincs beállítva (alapértelmezett), letiltja a bemeneti alakítást a rezonancia teszteléshez, mert a rezonancia tesztelés nem érvényes a bemeneti alakító engedélyezésével. Az <code>OUTPUT</code> paraméter egy vesszővel elválasztott lista arról, hogy mely kimenetek kerülnek kiírásra. Ha <code>raw_data</code> paramétert kér, akkor a nyers gyorsulásmérő adatok egy <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> fájlba vagy fájlsorozatba íródnak. A (<code><point>_</code> név részével, amely csak akkor generálódik, ha 1-nél több mérőpont van konfigurálva vagy POINT van megadva). Ha <code>resonances</code> van megadva, a frekvenciaválasz kiszámításra kerül (az összes mérőpontra vonatkozóan), és a <code>/tmp/resonances_<axis>_<name>.csv</code> fájlba íródik. Ha nincs beállítva, az OUTPUT alapértelmezés szerinti <code>resonances</code>, a NAME pedig alapértelmezés szerint az aktuális időpontot jelenti "ÉÉÉÉHHNN_ÓÓPPMPMP" formátumban.</p>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> [OUTPUT=<resonances,raw_data>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [POINT=x,y,z] [INPUT_SHAPING=<0:1>]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>chip_name</code> can be one or more configured accel chips, delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<h4 id="shaper_calibrate">SHAPER_CALIBRATE<a class="headerlink" href="#shaper_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [CHIPS=<adxl345_chip_name>] ]</code>: Hasonlóan a <code>TEST_RESONANCES'-hoz, a beállított rezonanciatesztet futtatja, és megpróbálja megtalálni az optimális paramétereket a bemeneti alakítóhoz a kért tengelyen (vagy az X és Y tengelyen, ha az 'AXIS' paraméter nincs beállítva). Ha a</code>MAX_SMOOTHING<code>nincs beállítva, akkor az értéke a</code>[resonance_tester] szakaszból származik, és az alapértelmezett érték nincs beállítva. A funkció használatával kapcsolatos további információkért tekintsd meg a Rezonancia mérési útmutató <a href="Measuring_Resonances.html#max-smoothing">Maximális simítás</a> részét. A hangolás eredményét a rendszer kiírja a konzolra, a frekvenciaválaszokat és a különböző bemeneti formáló értékeket pedig egy CSV-fájl(ok)ba írja <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Ha nincs megadva, a NAME alapértelmezés szerint az aktuális időt „ÉÉÉÉHHNN_ÓÓPP” formátumban használja. Vedd figyelembe, hogy a javasolt bemeneti alakító paraméterek a <code>SAVE_CONFIG</code> parancs kiadásával megőrizhetők a konfigurációban, és ha az <code>[input_shaper]</code> már korábban engedélyezve volt, ezek a paraméterek azonnal érvénybe lépnek.</p>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>][HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [MAX_SMOOTHING=<max_smoothing>] [INPUT_SHAPING=<0:1>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">¶</a></h3>
|
||||
<p>A következő szabványos G-kódú parancsok állnak rendelkezésre, ha a <a href="Config_Reference.html#respond">respond konfigurációs szakasz</a> engedélyezve van:</p>
|
||||
<ul>
|
||||
|
|
@ -5161,7 +5231,7 @@ section</a> is enabled.</p>
|
|||
<h3 id="z_tilt">[z_tilt]<a class="headerlink" href="#z_tilt" title="Permanent link">¶</a></h3>
|
||||
<p>A következő parancsok akkor érhetők el, ha a <a href="Config_Reference.html#z_tilt">z_tilt konfigurációs szakasz</a> engedélyezve van.</p>
|
||||
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">¶</a></h4>
|
||||
<p><code>Z_TILT_ADJUST [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: Ez a parancs a konfigurációban megadott pontokat szondázza, majd független beállításokat végez az egyes Z léptetőkön a dőlés kompenzálása érdekében. Az opcionális szondázó paraméterekkel kapcsolatos részletekért lásd a PROBE parancsot. Az opcionális <code>HORIZONTAL_MOVE_Z</code> érték felülírja a config fájlban megadott <code>horizontal_move_z</code> opciót.</p>
|
||||
<p><code>Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">¶</a></h3>
|
||||
<p>A következő parancsok akkor érhetők el, ha a <a href="Config_Reference.html#temperature_probe">temperature_probe konfigurációs szakasz</a> engedélyezve van.</p>
|
||||
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
|
|||
|
|
@ -912,8 +912,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis2dw-sorozat-konfiguralasa" class="md-nav__link">
|
||||
LIS2DW sorozat konfigurálása
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -990,6 +990,13 @@
|
|||
A max_accel kiválasztása
|
||||
</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="#lis2dw-sorozat-konfiguralasa" class="md-nav__link">
|
||||
LIS2DW sorozat konfigurálása
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1852,6 +1859,13 @@
|
|||
A max_accel kiválasztása
|
||||
</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="rezonanciak-merese">Rezonanciák mérése<a class="headerlink" href="#rezonanciak-merese" title="Permanent link">¶</a></h1>
|
||||
<p>A Klipper beépített támogatással rendelkezik az ADXL345, MPU-9250 és LIS2DW kompatibilis gyorsulásmérőkhöz, amelyek segítségével a nyomtató különböző tengelyek rezonanciafrekvenciái mérhetők, és a rezonanciák kompenzálására a <a href="Resonance_Compensation.html">bemeneti alakítók</a> automatikus beállítása használható. Vedd figyelembe, hogy a gyorsulásmérők használata némi forrasztást és krimpelést igényel. Az ADXL345/LIS2DW csatlakoztatható egy Raspberry Pi vagy MCU lap SPI interfészéhez (viszonylag gyorsnak kell lennie). Az MPU-család közvetlenül csatlakoztatható egy Raspberry Pi I2C-interfészéhez, vagy egy MCU-kártya I2C-interfészéhez, amely támogatja a Klipper 400kbit/s <em>gyors üzemmódot</em>.</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>A gyorsulásmérők beszerzésekor vedd figyelembe, hogy számos különböző nyomtatott áramköri lapkakialakítás és különböző klónok léteznek. Ha 5V-os nyomtató MCU-hoz csatlakozik, győződj meg róla, hogy rendelkezel feszültségszabályozóval és szintválasztóval.</p>
|
||||
<p>Az ADXL345s/LIS2DW-k esetében győződj meg róla, hogy a kártya támogatja az SPI módot (úgy tűnik, hogy néhány kártya keményen I2C-re van konfigurálva az SDO GND-re húzásával).</p>
|
||||
<p>Az MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500-asok esetében is vannak különböző lapkakialakítások és klónok különböző I2C pull-up ellenállásokkal, amelyeket ki kell egészíteni.</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="mcu-k-klipper-i2c-gyors-uzemmodu-tamogatassal">MCU-k Klipper I2C <em>gyors üzemmódú</em> támogatással<a class="headerlink" href="#mcu-k-klipper-i2c-gyors-uzemmodu-tamogatassal" 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="telepitesi-utasitasok">Telepítési utasítások<a class="headerlink" href="#telepitesi-utasitasok" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
|
|||
</code></pre></div>
|
||||
|
||||
<p>Ezután a NumPy telepítéséhez a Klipper környezetbe futtassuk a parancsot:</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>Vedd figyelembe, hogy a CPU teljesítményétől függően ez <em>sok</em> időt vehet igénybe, akár 10-20 percet is. Legyél türelmes, és várd meg a telepítés befejezését. Bizonyos esetekben, ha a kártyán túl kevés RAM van, a telepítés meghiúsulhat, és engedélyezned kell a swapot.</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="adxl345-konfiguralasa-rpi-vel">ADXL345 konfigurálása RPi-vel<a class="headerlink" href="#adxl345-konfiguralasa-rpi-vel" title="Permanent link">¶</a></h4>
|
||||
<p>Először is, ellenőrizd és kövesd az <a href="RPi_microcontroller.html">RPi Microcontroller dokumentum</a> utasításait a "linux mcu" beállításához a Raspberry Pi-n. Ez egy második Klipper példányt fog konfigurálni, amely a Pi-n fut.</p>
|
||||
<p>Győződjünk meg róla, hogy a Linux SPI-illesztőprogram engedélyezve van a <code>sudo raspi-config</code> futtatásával és az SPI engedélyezésével az "Interfacing options" menüben.</p>
|
||||
|
|
@ -2257,7 +2281,7 @@ pin: adxl:gpio23
|
|||
</code></pre></div>
|
||||
|
||||
<p>Indítsd újra a Klippert a <code>RESTART</code> paranccsal.</p>
|
||||
<h4 id="lis2dw-sorozat-konfiguralasa">LIS2DW sorozat konfigurálása<a class="headerlink" href="#lis2dw-sorozat-konfiguralasa" 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]
|
||||
# Változtasd meg a <mySerial> értéket arra, amit fentebb találtál. Például,
|
||||
# usb-Klipper_rp2040_E661640843545B2E-if00
|
||||
|
|
@ -2482,6 +2506,8 @@ max_smoothing: 0.25 # egy példa
|
|||
|
||||
<p>hogy helyesen tudd kiszámítani a maximális gyorsulási ajánlásokat. Vedd figyelembe, hogy a <code>SHAPER_CALIBRATE</code> parancs már figyelembe veszi a konfigurált <code>square_corner_velocity</code> paramétert, és nincs szükség annak explicit megadására.</p>
|
||||
<p>Ha a formázó újrakalibrálását végzi, és a javasolt formázó konfigurációhoz tartozó simítás majdnem megegyezik az előző kalibrálás során kapott értékkel, ez a lépés kihagyható.</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="egyeni-tengelyek-tesztelese">Egyéni tengelyek tesztelése<a class="headerlink" href="#egyeni-tengelyek-tesztelese" title="Permanent link">¶</a></h3>
|
||||
<p><code>TEST_RESONANCES</code> parancs támogatja az egyéni tengelyeket. Bár ez nem igazán hasznos a bemeneti alakító kalibrálásához, a nyomtató rezonanciáinak alapos tanulmányozására és például a szíjfeszítés ellenőrzésére használható.</p>
|
||||
<p>A CoreXY nyomtatókon a szíjfeszítés ellenőrzéséhez hajtsd végre a következőt</p>
|
||||
|
|
|
|||
|
|
@ -1447,7 +1447,7 @@ git clone https://github.com/Klipper3d/klipper
|
|||
<h2 id="octoprint-beallitasa-a-klipper-hasznalatahoz">OctoPrint beállítása a Klipper használatához<a class="headerlink" href="#octoprint-beallitasa-a-klipper-hasznalatahoz" title="Permanent link">¶</a></h2>
|
||||
<p>Az OctoPrint webszerverét úgy kell konfigurálni, hogy kommunikálni tudjon a Klipper gazda szoftverrel. Egy webböngésző segítségével jelentkezz be az OctoPrint weboldalára, majd konfiguráld a következő elemeket:</p>
|
||||
<p>Navigálj a Beállítások fülre (a csavarkulcs ikon az oldal tetején). A "Soros kapcsolat" alatt a "További soros portok" alatt add hozzá:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.sock
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.serial
|
||||
</code></pre></div>
|
||||
|
||||
<p>Ezután kattints a "Mentés" gombra.</p>
|
||||
|
|
|
|||
|
|
@ -1480,7 +1480,7 @@
|
|||
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" style="margin:25px"/></a></p>
|
||||
<p>A BIGTREETECH a Klipper hivatalos alaplapszponzora. A BIGTREETECH elkötelezett az innovatív és versenyképes termékek fejlesztése mellett, hogy a 3D nyomtatási közösséget jobban szolgálják. Kövesd őket a <a href="https://www.facebook.com/BIGTREETECH">Facebookon</a> vagy a <a href="https://twitter.com/BigTreeTech">Twitteren</a>.</p>
|
||||
<h2 id="szponzorok_1">Szponzorok<a class="headerlink" href="#szponzorok_1" title="Permanent link">¶</a></h2>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a> <a href="https://peopoly.net"><img src="./img/sponsors/peopoly-logo.png" width="200" style="margin:25px" /></a></p>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a></p>
|
||||
<h2 id="klipper-fejlesztok">Klipper fejlesztők<a class="headerlink" href="#klipper-fejlesztok" title="Permanent link">¶</a></h2>
|
||||
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">¶</a></h3>
|
||||
<p>Kevin a Klipper eredeti szerzője és jelenlegi karbantartója. Adományozhatsz a következő címen: <a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> vagy <a href="https://www.patreon.com/koconnor">https://www.patreon.com/koconnor</a></p>
|
||||
|
|
|
|||
Binary file not shown.
File diff suppressed because one or more lines are too long
110
hu/sitemap.xml
110
hu/sitemap.xml
|
|
@ -2,277 +2,277 @@
|
|||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
|
|
@ -711,6 +711,33 @@
|
|||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1384,6 +1411,33 @@
|
|||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1420,19 +1474,43 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
|
|||
<blockquote>
|
||||
<p><strong>Tip:</strong> Make sure the <a href="Config_Reference.html#probe">probe X and Y offsets</a> are correctly set as they greatly influence calibration.</p>
|
||||
</blockquote>
|
||||
<h3 id="basic-usage-x-axis-calibration">Basic Usage: X-Axis Calibration<a class="headerlink" href="#basic-usage-x-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<ol>
|
||||
<li>After setting up the [axis_twist_compensation] module, perform <code>AXIS_TWIST_COMPENSATION_CALIBRATE</code></li>
|
||||
<li>After setting up the <code>[axis_twist_compensation]</code> module, run:</li>
|
||||
</ol>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE
|
||||
</code></pre></div>
|
||||
|
||||
<p>This command will calibrate the X-axis by default. - The calibration wizard will prompt you to measure the probe Z offset at several points along the bed. - By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=<value></code></p>
|
||||
<ol>
|
||||
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).</li>
|
||||
<li>
|
||||
<p><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</p>
|
||||
<ul>
|
||||
<li>The calibration wizard will prompt you to measure the probe Z offset at a few points along the bed</li>
|
||||
<li>The calibration defaults to 3 points but you can use the option <code>SAMPLE_COUNT=</code> to use a different number.</li>
|
||||
<li><a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a></li>
|
||||
<li><a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a></li>
|
||||
</ul>
|
||||
<ol>
|
||||
<li><a href="Probe_Calibrate.html#calibrating-probe-z-offset">Adjust your Z offset</a></li>
|
||||
<li>Perform automatic/probe-based bed tramming operations, such as <a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a>, <a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a> etc</li>
|
||||
<li>Home all axis, then perform a <a href="Bed_Mesh.html">Bed Mesh</a> if required</li>
|
||||
<li>Perform a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> as desired</li>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Finalize the Setup:</strong></p>
|
||||
<ul>
|
||||
<li>Home all axes, and perform a <a href="Bed_Mesh.html">Bed Mesh</a> if necessary.</li>
|
||||
<li>Run a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> if needed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h3 id="for-y-axis-calibration">For Y-Axis Calibration<a class="headerlink" href="#for-y-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<p>The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y
|
||||
</code></pre></div>
|
||||
|
||||
<p>This will guide you through the same measuring process as for the X-axis.</p>
|
||||
<h3 id="automatic-calibration-for-both-axes">Automatic Calibration for Both Axes<a class="headerlink" href="#automatic-calibration-for-both-axes" title="Permanent link">¶</a></h3>
|
||||
<p>To perform automatic calibration for both the X and Y axes without manual intervention, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
|
||||
</code></pre></div>
|
||||
|
||||
<p>In this mode, the calibration process will run for both axes automatically.</p>
|
||||
<blockquote>
|
||||
<p><strong>Tip:</strong> Bed temperature and nozzle temperature and size do not seem to have an influence to the calibration process.</p>
|
||||
</blockquote>
|
||||
|
|
|
|||
|
|
@ -1968,7 +1968,7 @@ fade_target: 0
|
|||
<li><code>fade_target: 0</code> <em>Valore predefinito: il valore Z medio della mesh</em> Il <code>fade_target</code> può essere considerato come un offset Z aggiuntivo applicato all'intero piatto una volta completata la dissolvenza. In generale vorremmo che questo valore fosse 0, tuttavia ci sono circostanze in cui non dovrebbe esserlo. Ad esempio, supponiamo che la posizione di homing sul piatto sia un valore anomalo, ovvero 0,2 mm inferiore all'altezza media rilevata del piatto. Se <code>fade_target</code> è 0, la dissolvenza ridurrà la stampa in media di 0,2 mm sul piano. Impostando <code>fade_target</code> su .2, l'area home si espanderà di 0,2 mm, tuttavia, il resto del piatto verrà dimensionato accuratamente. Generalmente è una buona idea lasciare "fade_target" fuori dalla configurazione in modo da utilizzare l'altezza media della mesh, tuttavia potrebbe essere preferibile regolare manualmente il target di dissolvenza se si desidera stampare su una porzione specifica del piano.</li>
|
||||
</ul>
|
||||
<h3 id="configuring-the-zero-reference-position">Configuring the zero reference position<a class="headerlink" href="#configuring-the-zero-reference-position" title="Permanent link">¶</a></h3>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="./Manual_Level#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="Manual_Level.html#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<div class="highlight"><pre><span></span><code>[bed_mesh]
|
||||
speed: 120
|
||||
horizontal_move_z: 5
|
||||
|
|
|
|||
|
|
@ -1195,6 +1195,13 @@
|
|||
Benchmark step rate SAMD51
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1205,8 +1212,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#benchmark-step-rate-rp2040" class="md-nav__link">
|
||||
Benchmark step rate RP2040
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1613,6 +1620,13 @@
|
|||
Benchmark step rate SAMD51
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1623,8 +1637,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#benchmark-step-rate-rp2040" class="md-nav__link">
|
||||
Benchmark step rate RP2040
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -2122,6 +2136,34 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="same70-step-rate-benchmark">SAME70 step rate benchmark<a class="headerlink" href="#same70-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the SAME70:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=PC18 dir_pin=PB5 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=PC16 dir_pin=PD10 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=2 step_pin=PC28 dir_pin=PA4 invert_step=-1 step_pulse_ticks=0
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>34e9ea55</code> with gcc version <code>arm-none-eabi-gcc (NixOS 10.3-2021.10) 10.3.1</code> on a SAME70Q20B micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>same70</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1 stepper</td>
|
||||
<td>45</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 stepper</td>
|
||||
<td>190</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="benchmark-della-velocita-di-passo-ar100">Benchmark della velocità di passo AR100<a class="headerlink" href="#benchmark-della-velocita-di-passo-ar100" title="Permanent link">¶</a></h3>
|
||||
<p>La seguente sequenza di configurazione viene utilizzata sulla CPU AR100 (Allwinner A64):</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2131,7 +2173,7 @@ config_stepper oid=2 step_pin=PL12 dir_pin=PE16 invert_step=-1 step_pulse_ticks=
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>Il test è stato eseguito l'ultima volta sul commit <code>08d037c6</code> con la versione gcc <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> su un microcontrollore Allwinner A64-H.</p>
|
||||
<p>The test was last run on commit <code>b7978d37</code> with gcc version <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> on an Allwinner A64-H micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -2150,8 +2192,8 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="benchmark-step-rate-rp2040">Benchmark step rate RP2040<a class="headerlink" href="#benchmark-step-rate-rp2040" title="Permanent link">¶</a></h3>
|
||||
<p>Sull'RP2040 viene utilizzata la seguente sequenza di configurazione:</p>
|
||||
<h3 id="rpxxxx-step-rate-benchmark">RPxxxx step rate benchmark<a class="headerlink" href="#rpxxxx-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040 and RP2350:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=gpio25 dir_pin=gpio3 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=gpio26 dir_pin=gpio4 invert_step=-1 step_pulse_ticks=0
|
||||
|
|
@ -2159,11 +2201,11 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>Il test è stato eseguito l'ultima volta su commit <code>59314d99</code> con versione gcc <code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code> su una scheda Raspberry Pi Pico.</p>
|
||||
<p>The test was last run on commit <code>f6718291</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2040</th>
|
||||
<th>rp2040 (*)</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
|
@ -2178,6 +2220,25 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2350</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1 stepper</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 stepper</td>
|
||||
<td>169</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 125Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM core cycles.</p>
|
||||
<h3 id="benchmark-step-rate-mcu-linux">Benchmark step rate MCU Linux<a class="headerlink" href="#benchmark-step-rate-mcu-linux" title="Permanent link">¶</a></h3>
|
||||
<p>La seguente sequenza di configurazione viene utilizzata su un Raspberry Pi:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2311,9 +2372,15 @@ get_uptime
|
|||
</tr>
|
||||
<tr>
|
||||
<td>rp2040 (USB)</td>
|
||||
<td>873K</td>
|
||||
<td>c5667193</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2350 (USB)</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
|
|||
|
|
@ -1580,7 +1580,7 @@
|
|||
<li>Esaminare le classi cinematiche esistenti nella directory klippy/kinematics/. Le classi cinematiche hanno il compito di convertire una mossa in coordinate cartesiane nel movimento su ogni stepper. Si dovrebbe essere in grado di copiare uno di questi file come punto di partenza.</li>
|
||||
<li>Implementa in C le funzioni di posizione cinematica dello stepper per ogni stepper se non sono già disponibili (vedi kin_cart.c, kin_corexy.c e kin_delta.c in klippy/chelper/). La funzione dovrebbe chiamare <code>move_get_coord()</code> per convertire un dato tempo di spostamento (in secondi) in una coordinata cartesiana (in millimetri), e quindi calcolare la posizione dello stepper desiderata (in millimetri) da quella coordinata cartesiana.</li>
|
||||
<li>Implementa il metodo <code>calc_position()</code> nella nuova classe cinematica. Questo metodo calcola la posizione della testa di stampa in coordinate cartesiane dalla posizione di ogni stepper. Non è necessario che sia efficiente poiché in genere viene chiamato solo durante le operazioni di homing e probing.</li>
|
||||
<li>Altri metodi. Implementa i metodi <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code> e <code>set_position()</code>. Queste funzioni sono in genere utilizzate per fornire verifiche cinematiche specifiche. Tuttavia, all'inizio dello sviluppo è possibile utilizzare il codice boilerplate qui.</li>
|
||||
<li>Other methods. Implement the <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>clear_homing_state()</code>, and <code>set_position()</code> methods. These functions are typically used to provide kinematic specific checks. However, at the start of development one can use boiler-plate code here.</li>
|
||||
<li>Implementare casi di prova. Crea un file g-code con una serie di movimenti che possono testare casi importanti per la cinematica data. Segui la <a href="Debugging.html">documentazione di debug</a> per convertire questo file di codice G in comandi del microcontrollore. Questo è utile per esercitare corner case e per verificare la presenza di regressioni.</li>
|
||||
</ol>
|
||||
<h2 id="porting-su-un-nuovo-microcontrollore">Porting su un nuovo microcontrollore<a class="headerlink" href="#porting-su-un-nuovo-microcontrollore" title="Permanent link">¶</a></h2>
|
||||
|
|
|
|||
|
|
@ -1396,6 +1396,11 @@
|
|||
<p>Questo documento copre le modifiche software recenti al file di configurazione che non sono compatibili con le versioni precedenti. È una buona idea rivedere questo documento durante l'aggiornamento del software Klipper.</p>
|
||||
<p>Tutte le date in questo documento sono approssimative.</p>
|
||||
<h2 id="cambiamenti">Cambiamenti<a class="headerlink" href="#cambiamenti" title="Permanent link">¶</a></h2>
|
||||
<p>20241203: The resonance test has been changed to include slow sweeping moves. This change requires that testing point(s) have some clearance in X/Y plane (+/- 30 mm from the test point should suffice when using the default settings). The new test should generally produce more accurate and reliable test results. However, if required, the previous test behavior can be restored by adding options <code>sweeping_period: 0</code> and <code>accel_per_hz: 75</code> to the <code>[resonance_tester]</code> config section.</p>
|
||||
<p>20241201: In some cases Klipper may have ignored leading characters or spaces in a traditional G-Code command. For example, "99M123" may have been interpreted as "M123" and "M 321" may have been interpreted as "M321". Klipper will now report these cases with an "Unknown command" warning.</p>
|
||||
<p>20241112: Option <code>CHIPS=<chip_name></code> in <code>TEST_RESONANCES</code> and <code>SHAPER_CALIBRATE</code> requires specifying the full name(s) of the accel chip(s). For example, <code>adxl345 rpi</code> instead of short name - <code>rpi</code>.</p>
|
||||
<p>20240912: <code>SET_PIN</code>, <code>SET_SERVO</code>, <code>SET_FAN_SPEED</code>, <code>M106</code>, and <code>M107</code> commands are now collated. Previously, if many updates to the same object were issued faster than the minimum scheduling time (typically 100ms) then actual updates could be queued far into the future. Now if many updates are issued in rapid succession then it is possible that only the latest request will be applied. If the previous behavior is requried then consider adding explicit <code>G4</code> delay commands between updates.</p>
|
||||
<p>20240912: Support for <code>maximum_mcu_duration</code> and <code>static_value</code> parameters in <code>[output_pin]</code> config sections have been removed. These options have been deprecated since 20240123.</p>
|
||||
<p>20240415: The <code>on_error_gcode</code> parameter in the <code>[virtual_sdcard]</code> config section now has a default. If this parameter is not specified it now defaults to <code>TURN_OFF_HEATERS</code>. If the previous behavior is desired (take no default action on an error during a virtual_sdcard print) then define <code>on_error_gcode</code> with an empty value.</p>
|
||||
<p>20240313: The <code>max_accel_to_decel</code> parameter in the <code>[printer]</code> config section has been deprecated. The <code>ACCEL_TO_DECEL</code> parameter of the <code>SET_VELOCITY_LIMIT</code> command has been deprecated. The <code>printer.toolhead.max_accel_to_decel</code> status has been removed. Use the <a href="Config_Reference.html#printer">minimum_cruise_ratio parameter</a> instead. The deprecated features will be removed in the near future, and using them in the interim may result in subtly different behavior.</p>
|
||||
<p>20240215: Several deprecated features have been removed. Using "NTC 100K beta 3950" as a thermistor name has been removed (deprecated on 20211110). The <code>SYNC_STEPPER_TO_EXTRUDER</code> and <code>SET_EXTRUDER_STEP_DISTANCE</code> commands have been removed, and the extruder <code>shared_heater</code> config option has been removed (deprecated on 20220210). The bed_mesh <code>relative_reference_index</code> option has been removed (deprecated on 20230619).</p>
|
||||
|
|
|
|||
|
|
@ -938,6 +938,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1537,6 +1544,13 @@
|
|||
display hd44780_spi
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1670,8 +1684,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -3032,6 +3046,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3631,6 +3652,13 @@
|
|||
display hd44780_spi
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3764,8 +3792,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -5292,8 +5320,9 @@ cs_pin:
|
|||
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS2DW accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis2dw]
|
||||
cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
|
|
@ -5303,6 +5332,43 @@ cs_pin:
|
|||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="lis3dh">[lis3dh]<a class="headerlink" href="#lis3dh" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS3DH accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis3dh]
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
|
@ -5327,47 +5393,58 @@ cs_pin:
|
|||
<p>Supporto per test di risonanza e calibrazione automatica del input shaper. Per utilizzare la maggior parte delle funzionalità di questo modulo, devono essere installate dipendenze software aggiuntive; fare riferimento a <a href="Measuring_Resonances.html">Measuring Resonances</a> e al <a href="G-Codes.html#resonance_tester">command reference</a> per ulteriori informazioni. Per ulteriori informazioni sul parametro <code>max_smoothing</code> e sul suo utilizzo, vedere la sezione <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> della guida alla misurazione delle risonanze.</p>
|
||||
<div class="highlight"><pre><span></span><code>[resonance_tester]
|
||||
#probe_points:
|
||||
# Un elenco di coordinate X, Y, Z di punti (un punto per linea) in cui
|
||||
# testare le risonanze. Almeno un punto è richiesto. Assicurati che tutti
|
||||
# i punti con un margine di sicurezza nel piano XY (~ pochi centimetri)
|
||||
# siano raggiungibili dalla testa di stampa.
|
||||
# A list of X, Y, Z coordinates of points (one point per line) to test
|
||||
# resonances at. At least one point is required. Make sure that all
|
||||
# points with some safety margin in XY plane (~a few centimeters)
|
||||
# are reachable by the toolhead.
|
||||
#accel_chip:
|
||||
# Un nome del chip dell'accelerometro da utilizzare per le misurazioni.
|
||||
# Se il chip adxl345 è stato definito senza un nome esplicito, questo
|
||||
# parametro può semplicemente fare riferimento ad esso come
|
||||
# "accel_chip: adxl345", altrimenti deve essere fornito anche un nome
|
||||
# esplicito, ad es. "accel_chip: adxl345 mio_chip_nome". È necessario
|
||||
# impostare questo o i due parametri successivi.
|
||||
# A name of the accelerometer chip to use for measurements. If
|
||||
# adxl345 chip was defined without an explicit name, this parameter
|
||||
# can simply reference it as "accel_chip: adxl345", otherwise an
|
||||
# explicit name must be supplied as well, e.g. "accel_chip: adxl345
|
||||
# my_chip_name". Either this, or the next two parameters must be
|
||||
# set.
|
||||
#accel_chip_x:
|
||||
#accel_chip_y:
|
||||
# Nomi dei chip dell'accelerometro da utilizzare per le misurazioni per
|
||||
# ciascuno degli assi. Può essere utile, ad esempio, su una stampante con
|
||||
# piatto, se due accelerometri separati sono montati sul piatto (per l'asse Y)
|
||||
# e sulla testa di stampa (per l'asse X). Questi parametri hanno lo stesso
|
||||
# formato del parametro 'accel_chip'.
|
||||
# È necessario fornire solo 'accel_chip' o questi due parametri.
|
||||
# Names of the accelerometer chips to use for measurements for each
|
||||
# of the axis. Can be useful, for instance, on bed slinger printer,
|
||||
# if two separate accelerometers are mounted on the bed (for Y axis)
|
||||
# and on the toolhead (for X axis). These parameters have the same
|
||||
# format as 'accel_chip' parameter. Only 'accel_chip' or these two
|
||||
# parameters must be provided.
|
||||
#max_smoothing:
|
||||
# Maximum input shaper smoothing to allow for each axis during shaper
|
||||
# auto-calibration (with 'SHAPER_CALIBRATE' command). By default no
|
||||
# maximum smoothing is specified. Refer to Measuring_Resonances guide
|
||||
# for more details on using this feature.
|
||||
#move_speed: 50
|
||||
# The speed (in mm/s) to move the toolhead to and between test points
|
||||
# during the calibration. The default is 50.
|
||||
#min_freq: 5
|
||||
# Frequenza minima per testare le risonanze. L'impostazione è 5 Hz.
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 133.33
|
||||
# Frequenza massima per testare le risonanze. L'impostazione è 133,33 Hz.
|
||||
#accel_per_hz: 75
|
||||
# Questo parametro viene utilizzato per determinare quale accelerazione
|
||||
# utilizzare per testare una frequenza specifica: accel = accel_per_hz * freq.
|
||||
# Maggiore è il valore, maggiore è l'energia delle oscillazioni. Può essere
|
||||
# impostato su un valore inferiore al valore predefinito se le risonanze
|
||||
# diventano troppo forti sulla stampante. Tuttavia, valori più bassi rendono
|
||||
# le misurazioni delle risonanze ad alta frequenza meno precise.
|
||||
# Il valore predefinito è 75 (mm/sec).
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 60
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
# value, the higher is the energy of the oscillations. Can be set to
|
||||
# a lower than the default value if the resonances get too strong on
|
||||
# the printer. However, lower values make measurements of
|
||||
# high-frequency resonances less precise. The default value is 75
|
||||
# (mm/sec).
|
||||
#hz_per_sec: 1
|
||||
# Determina la velocità del test. Quando si testano tutte le frequenze
|
||||
# nell'intervallo [freq_min, freq_max], ogni secondo la frequenza aumenta
|
||||
# di hz_per_sec. Valori piccoli rallentano il test e valori grandi diminuiscono
|
||||
# la precisione del test. Il valore predefinito è 1,0 (Hz/sec == sec^-2).
|
||||
# Determines the speed of the test. When testing all frequencies in
|
||||
# range [min_freq, max_freq], each second the frequency increases by
|
||||
# hz_per_sec. Small values make the test slow, and the large values
|
||||
# will decrease the precision of the test. The default value is 1.0
|
||||
# (Hz/sec == sec^-2).
|
||||
#sweeping_accel: 400
|
||||
# An acceleration of slow sweeping moves. The default is 400 mm/sec^2.
|
||||
#sweeping_period: 1.2
|
||||
# A period of slow sweeping moves. Setting this parameter to 0
|
||||
# disables slow sweeping moves. Avoid setting it to a too small
|
||||
# non-zero value in order to not poison the measurements.
|
||||
# The default is 1.2 sec which is a good all-round choice.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="helper-per-i-file-di-configurazione">Helper per i file di configurazione<a class="headerlink" href="#helper-per-i-file-di-configurazione" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5600,8 +5677,44 @@ sensor_type: ldc1612
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">¶</a></h3>
|
||||
<p>Uno strumento per compensare letture imprecise della sonda dovute alla torsione nel portale X. Consultare la <a href="Axis_Twist_Compensation.html">Guida alla compensazione della torsione dell'asse</a> per informazioni più dettagliate su sintomi, configurazione e impostazione.</p>
|
||||
<div class="highlight"><pre><span></span><code>italiano
|
||||
<p>A tool to compensate for inaccurate probe readings due to twist in X or Y gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
|
||||
<div class="highlight"><pre><span></span><code>[axis_twist_compensation]
|
||||
#speed: 50
|
||||
# The speed (in mm/s) of non-probing moves during the calibration.
|
||||
# The default is 50.
|
||||
#horizontal_move_z: 5
|
||||
# The height (in mm) that the head should be commanded to move to
|
||||
# just prior to starting a probe operation. The default is 5.
|
||||
calibrate_start_x: 20
|
||||
# Defines the minimum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the starting
|
||||
# calibration position.
|
||||
calibrate_end_x: 200
|
||||
# Defines the maximum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the ending
|
||||
# calibration position.
|
||||
calibrate_y: 112.5
|
||||
# Defines the Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle during the
|
||||
# calibration process. This parameter is recommended to
|
||||
# be near the center of the bed
|
||||
|
||||
# For Y-axis twist compensation, specify the following parameters:
|
||||
calibrate_start_y: ...
|
||||
# Defines the minimum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the starting
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_end_y: ...
|
||||
# Defines the maximum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the ending
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_x: ...
|
||||
# Defines the X coordinate of the calibration for Y axis twist compensation
|
||||
# This should be the X coordinate that positions the nozzle during the
|
||||
# calibration process for Y axis twist compensation. This parameter must be
|
||||
# provided and is recommended to be near the center of the bed.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="motori-passo-passo-ed-estrusori-aggiuntivi">Motori passo-passo ed estrusori aggiuntivi<a class="headerlink" href="#motori-passo-passo-ed-estrusori-aggiuntivi" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5882,6 +5995,10 @@ extruder:
|
|||
# "calibration_extruder_temp" option is set. Its recommended to heat
|
||||
# the extruder some distance from the bed to minimize its impact on
|
||||
# the probe coil temperature. The default is 50.
|
||||
#max_validation_temp: 60.
|
||||
# The maximum temperature used to validate the calibration. It is
|
||||
# recommended to set this to a value between 100 and 120 for enclosed
|
||||
# printers. The default is 60.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="sensori-di-temperatura">Sensori di temperatura<a class="headerlink" href="#sensori-di-temperatura" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -6998,6 +7115,7 @@ run_current:
|
|||
#driver_SEIMIN: 0
|
||||
#driver_SFILT: 0
|
||||
#driver_SG4_ANGLE_OFFSET: 1
|
||||
#driver_SLOPE_CONTROL: 0
|
||||
# Set the given register during the configuration of the TMC2240
|
||||
# chip. This may be used to set custom motor parameters. The
|
||||
# defaults for each parameter are next to the parameter name in the
|
||||
|
|
@ -7273,15 +7391,16 @@ wiper:
|
|||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type:
|
||||
# The type of LCD chip in use. This may be "hd44780", "hd44780_spi",
|
||||
# "st7920", "emulated_st7920", "uc1701", "ssd1306", or "sh1106".
|
||||
# "aip31068_spi", "st7920", "emulated_st7920", "uc1701", "ssd1306", or
|
||||
# "sh1106".
|
||||
# See the display sections below for information on each type and
|
||||
# additional parameters they provide. This parameter must be
|
||||
# provided.
|
||||
#display_group:
|
||||
# The name of the display_data group to show on the display. This
|
||||
# controls the content of the screen (see the "display_data" section
|
||||
# for more information). The default is _default_20x4 for hd44780
|
||||
# displays and _default_16x4 for other displays.
|
||||
# for more information). The default is _default_20x4 for hd44780 or
|
||||
# aip31068_spi displays and _default_16x4 for other displays.
|
||||
#menu_timeout:
|
||||
# Timeout for menu. Being inactive this amount of seconds will
|
||||
# trigger menu exit or return to root menu when having autorun
|
||||
|
|
@ -7398,6 +7517,26 @@ spi_software_miso_pin:
|
|||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="aip31068_spi-display">aip31068_spi display<a class="headerlink" href="#aip31068_spi-display" title="Permanent link">¶</a></h4>
|
||||
<p>Information on configuring an aip31068_spi display - a very similar to hd44780_spi a 20x04 (20 symbols by 4 lines) display with slightly different internal protocol.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type: aip31068_spi
|
||||
latch_pin:
|
||||
spi_software_sclk_pin:
|
||||
spi_software_mosi_pin:
|
||||
spi_software_miso_pin:
|
||||
# The pins connected to the shift register controlling the display.
|
||||
# The spi_software_miso_pin needs to be set to an unused pin of the
|
||||
# printer mainboard as the shift register does not have a MISO pin,
|
||||
# but the software spi implementation requires this pin to be
|
||||
# configured.
|
||||
#line_length:
|
||||
# Set the number of characters per line for an hd44780 type lcd.
|
||||
# Possible values are 20 (default) and 16. The number of lines is
|
||||
# fixed to 4.
|
||||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="display-st7920">display st7920<a class="headerlink" href="#display-st7920" title="Permanent link">¶</a></h4>
|
||||
<p>Informazioni sulla configurazione dei display st7920 (utilizzati nei display di tipo "RepRapDiscount 12864 Full Graphic Smart Controller").</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
|
|
@ -7756,7 +7895,7 @@ sensor_type:
|
|||
# This must be one of the supported sensor types, see below.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="xh711">XH711<a class="headerlink" href="#xh711" title="Permanent link">¶</a></h4>
|
||||
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">¶</a></h4>
|
||||
<p>This is a 24 bit low sample rate chip using "bit-bang" communications. It is suitable for filament scales.</p>
|
||||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
sensor_type: hx711
|
||||
|
|
@ -7819,13 +7958,30 @@ data_ready_pin:
|
|||
#gain: 128
|
||||
# Valid gain values are 128, 64, 32, 16, 8, 4, 2, 1
|
||||
# The default is 128
|
||||
#pga_bypass: False
|
||||
# Disable the internal Programmable Gain Amplifier. If
|
||||
# True the PGA will be disabled for gains 1, 2, and 4. The PGA is always
|
||||
# enabled for gain settings 8 to 128, regardless of the pga_bypass setting.
|
||||
# If AVSS is used as an input pga_bypass is forced to True.
|
||||
# The default is False.
|
||||
#sample_rate: 660
|
||||
# This chip supports two ranges of sample rates, Normal and Turbo. In turbo
|
||||
# mode the chips c internal clock runs twice as fast and the SPI communication
|
||||
# mode the chip's internal clock runs twice as fast and the SPI communication
|
||||
# speed is also doubled.
|
||||
# Normal sample rates: 20, 45, 90, 175, 330, 600, 1000
|
||||
# Turbo sample rates: 40, 90, 180, 350, 660, 1200, 2000
|
||||
# The default is 660
|
||||
#input_mux:
|
||||
# Input multiplexer configuration, select a pair of pins to use. The first pin
|
||||
# is the positive, AINP, and the second pin is the negative, AINN. Valid
|
||||
# values are: 'AIN0_AIN1', 'AIN0_AIN2', 'AIN0_AIN3', 'AIN1_AIN2', 'AIN1_AIN3',
|
||||
# 'AIN2_AIN3', 'AIN1_AIN0', 'AIN3_AIN2', 'AIN0_AVSS', 'AIN1_AVSS', 'AIN2_AVSS'
|
||||
# and 'AIN3_AVSS'. If AVSS is used the PGA is bypassed and the pga_bypass
|
||||
# setting will be forced to True.
|
||||
# The default is AIN0_AIN1.
|
||||
#vref:
|
||||
# The selected voltage reference. Valid values are: 'internal', 'REF0', 'REF1'
|
||||
# and 'analog_supply'. Default is 'internal'.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="supporto-hardware-per-specifica-scheda">Supporto hardware per specifica scheda<a class="headerlink" href="#supporto-hardware-per-specifica-scheda" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -7972,11 +8128,11 @@ serial:
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<p>Supporto per sensore magnetico Hall per la lettura delle misurazioni dell'angolo del motore passo-passo utilizzando i chip SPI a1333, as5047d o tle5012b. Le misurazioni sono disponibili tramite <a href="API_Server.html">Server API</a> e <a href="Debugging.html#motion-analysis-and-data-logging">strumento di analisi del movimento</a>. Vedere il <a href="G-Codes.html#angle">Riferimento G-Code</a> per i comandi disponibili.</p>
|
||||
<p>Magnetic hall angle sensor support for reading stepper motor angle shaft measurements using a1333, as5047d, mt6816, mt6826s, or tle5012b SPI chips. The measurements are available via the <a href="API_Server.html">API Server</a> and <a href="Debugging.html#motion-analysis-and-data-logging">motion analysis tool</a>. See the <a href="G-Codes.html#angle">G-Code reference</a> for available commands.</p>
|
||||
<div class="highlight"><pre><span></span><code>[angle my_angle_sensor]
|
||||
sensor_type:
|
||||
# The type of the magnetic hall sensor chip. Available choices are
|
||||
# "a1333", "as5047d", and "tle5012b". This parameter must be
|
||||
# "a1333", "as5047d", "mt6816", "mt6826s", and "tle5012b". This parameter must be
|
||||
# specified.
|
||||
#sample_period: 0.000400
|
||||
# The query period (in seconds) to use during measurements. The
|
||||
|
|
@ -8020,7 +8176,7 @@ cs_pin:
|
|||
<h3 id="impostazioni-i2c-comuni">Impostazioni I2C comuni<a class="headerlink" href="#impostazioni-i2c-comuni" title="Permanent link">¶</a></h3>
|
||||
<p>I seguenti parametri sono generalmente disponibili per i dispositivi che utilizzano un bus I2C.</p>
|
||||
<p>Tieni presente che l'attuale supporto del microcontrollore di Klipper per I2C generalmente non tollera il rumore di linea. Errori imprevisti sui cavi I2C potrebbero far sì che Klipper sollevi un errore di runtime. Il supporto di Klipper per il ripristino degli errori varia a seconda del tipo di microcontrollore. In genere si consiglia di utilizzare solo dispositivi I2C che si trovano sullo stesso circuito stampato del microcontrollore.</p>
|
||||
<p>La maggior parte delle implementazioni del microcontrollore Klipper supportano solo una <code>i2c_speed</code> di 100000 (<em>modalità standard</em>, 100kbit/s). Il microcontrollore Klipper "Linux" supporta una velocità 400000 (<em>modalità veloce</em>, 400kbit/s), ma deve essere <a href="RPi_microcontroller.html#optional-enabling-i2c">impostato nel sistema operativo</a> e <code>i2c_speed</code> il parametro viene altrimenti ignorato. Il microcontrollore Klipper "RP2040" e la famiglia ATmega AVR supportano una velocità di 400000 tramite il parametro <code>i2c_speed</code>. Tutti gli altri microcontrollori Klipper utilizzano una velocità 100000 e ignorano il parametro "i2c_speed".</p>
|
||||
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000 (<em>standard mode</em>, 100kbit/s). The Klipper "Linux" micro-controller supports a 400000 speed (<em>fast mode</em>, 400kbit/s), but it must be <a href="RPi_microcontroller.html#optional-enabling-i2c">set in the operating system</a> and the <code>i2c_speed</code> parameter is otherwise ignored. The Klipper "RP2040" micro-controller and ATmega AVR family and some STM32 (F0, G0, G4, L4, F7, H7) support a rate of 400000 via the <code>i2c_speed</code> parameter. All other Klipper micro-controllers use a 100000 rate and ignore the <code>i2c_speed</code> parameter.</p>
|
||||
<div class="highlight"><pre><span></span><code>#i2c_address:
|
||||
# The i2c address of the device. This must specified as a decimal
|
||||
# number (not in hex). The default depends on the type of device.
|
||||
|
|
|
|||
|
|
@ -1412,7 +1412,7 @@
|
|||
# temperature probe configuration...
|
||||
</code></pre></div>
|
||||
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below.</p>
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below. If the printer to be calibrated is enclosed, it is strongly recommended to set the <code>max_validation_temp</code> option to a value between 100 and 120.</p>
|
||||
<p>Eddy probe manufacturers may offer a stock drift calibration that can be manually added to <code>drift_calibration</code> option of the <code>[probe_eddy_current]</code> section. If they do not, or if the stock calibration does not perform well on your system, the <code>temperature_probe</code> module offers a manual calibration procedure via the <code>TEMPERATURE_PROBE_CALIBRATE</code> gcode command.</p>
|
||||
<p>Prior to performing calibration the user should have an idea of what the maximum attainable temperature probe coil temperature is. This temperature should be used to set the <code>TARGET</code> parameter of the <code>TEMPERATURE_PROBE_CALIBRATE</code> command. The goal is to calibrate across the widest temperature range possible, thus its desirable to start with the printer cold and finish with the coil at the maximum temperature it can reach.</p>
|
||||
<p>Once a <code>[temperature_probe]</code> is configured, the following steps may be taken to perform thermal drift calibration:</p>
|
||||
|
|
|
|||
|
|
@ -1542,6 +1542,16 @@
|
|||
<td>2634K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>RP2350</td>
|
||||
<td>4167K</td>
|
||||
<td>2663K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SAME70</td>
|
||||
<td>6667K</td>
|
||||
<td>4737K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>STM32H743</td>
|
||||
<td>9091K</td>
|
||||
<td>6061K</td>
|
||||
|
|
|
|||
|
|
@ -869,6 +869,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1958,6 +1965,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3089,6 +3116,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4178,6 +4212,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4750,6 +4804,11 @@
|
|||
<p>I seguenti comandi sono disponibili quando una <a href="Config_Reference.html#angle">sezione di configurazione dell'angolo</a> è abilitata.</p>
|
||||
<h4 id="angle_calibrate">ANGLE_CALIBRATE<a class="headerlink" href="#angle_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CALIBRATE CHIP=<chip_name></code>: Esegue la calibrazione dell'angolo sul sensore dato (deve esserci una sezione di configurazione <code>[angle chip_name]</code> che ha specificato un parametro <code>stepper</code>). IMPORTANTE - questo strumento comanderà al motore passo-passo di muoversi senza controllare i normali limiti della cinematica. Idealmente, il motore dovrebbe essere scollegato da qualsiasi carrello della stampante prima di eseguire la calibrazione. Se non è possibile scollegare lo stepper dalla stampante, assicurarsi che il carrello sia vicino al centro della sua guida prima di iniziare la calibrazione. (Il motore passo-passo può spostarsi avanti o indietro di due rotazioni complete durante questo test.) Dopo aver completato questo test, utilizzare il comando <code>SAVE_CONFIG</code> per salvare i dati di calibrazione nel file di configurazione. Per utilizzare questo strumento è necessario installare il pacchetto Python "numpy" (consultare il <a href="Measuring_Resonances.html#software-installation">measuring resonance document</a> per ulteriori informazioni).</p>
|
||||
<h4 id="angle_chip_calibrate">ANGLE_CHIP_CALIBRATE<a class="headerlink" href="#angle_chip_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CHIP_CALIBRATE CHIP=<chip_name></code>: Perform internal sensor calibration, if implemented (MT6826S/MT6835).</p>
|
||||
<ul>
|
||||
<li><strong>MT68XX</strong>: The motor should be disconnected from any printer carriage before performing calibration. After calibration, the sensor should be reset by disconnecting the power.</li>
|
||||
</ul>
|
||||
<h4 id="angle_debug_read">ANGLE_DEBUG_READ<a class="headerlink" href="#angle_debug_read" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_DEBUG_READ CHIP=<config_name> REG=<register></code>: Interroga il registro del sensore "register" (ad es. 44 o 0x2C). Può essere utile per scopi di debug. Questo è disponibile solo per i chip tle5012b.</p>
|
||||
<h4 id="angle_debug_write">ANGLE_DEBUG_WRITE<a class="headerlink" href="#angle_debug_write" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4758,7 +4817,12 @@
|
|||
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
|
||||
section</a> is enabled.</p>
|
||||
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=<value>]</code>: Initiates the X twist calibration wizard. <code>SAMPLE_COUNT</code> specifies the number of points along the X axis to calibrate at and defaults to 3.</p>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]</code></p>
|
||||
<p>Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.</p>
|
||||
<ul>
|
||||
<li><strong>AXIS:</strong> Define the axis (<code>X</code> or <code>Y</code>) for which the twist compensation will be calibrated. If not specified, the axis defaults to <code>'X'</code>.</li>
|
||||
<li><strong>AUTO:</strong> Enables automatic calibration mode. When <code>AUTO=True</code>, the calibration will run for both the X and Y axes. In this mode, <code>AXIS</code> cannot be specified. If both <code>AXIS</code> and <code>AUTO</code> are provided, an error will be raised.</li>
|
||||
</ul>
|
||||
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">¶</a></h3>
|
||||
<p>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#bed_mesh">sezione di configurazione bed_mesh</a> è abilitata (consultare anche la <a href="Bed_Mesh.html">guida della mesh del letto</a>).</p>
|
||||
<h4 id="bed_mesh_calibrate">BED_MESH_CALIBRATE<a class="headerlink" href="#bed_mesh_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4862,6 +4926,7 @@ section</a> is enabled.</p>
|
|||
<p>Il comando seguente è disponibile quando una <a href="Config_Reference.html#fan_generic">sezione di configurazione fan_generic</a> è abilitata.</p>
|
||||
<h4 id="set_fan_speed">SET_FAN_SPEED<a class="headerlink" href="#set_fan_speed" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_FAN_SPEED FAN=config_name SPEED=<velocità></code> Questo comando imposta la velocità di una ventola. "velocità" deve essere compresa tra 0.0 e 1.0.</p>
|
||||
<p><code>SET_FAN_SPEED PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given fan. For example, if one defined a <code>[display_template my_fan_template]</code> config section then one could assign <code>TEMPLATE=my_fan_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the fan will be automatically set to the resulting speed. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_FAN_SPEED</code> commands to manage the values directly).</p>
|
||||
<h3 id="filament_switch_sensor">[filament_switch_sensor]<a class="headerlink" href="#filament_switch_sensor" title="Permanent link">¶</a></h3>
|
||||
<p>Il comando seguente è disponibile quando è abilitata una sezione di configurazione <a href="Config_Reference.html#filament_switch_sensor">filament_switch_sensor</a> o <a href="Config_Reference.html#filament_motion_sensor">filament_motion_sensor</a>.</p>
|
||||
<h4 id="query_filament_sensor">QUERY_FILAMENT_SENSOR<a class="headerlink" href="#query_filament_sensor" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4886,7 +4951,7 @@ section</a> is enabled.</p>
|
|||
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>FORCE_MOVE STEPPER=<nome_config> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]</code>: Questo comando sposterà forzatamente lo stepper dato della distanza data (in mm) alla velocità costante data (in mm/ S). Se viene specificato ACCEL ed è maggiore di zero, verrà utilizzata l'accelerazione data (in mm/s^2); altrimenti non viene eseguita alcuna accelerazione. Non vengono effettuati controlli sui limiti; non vengono effettuati aggiornamenti cinematici; altri stepper paralleli su un asse non verranno spostati. Prestare attenzione poiché un comando errato potrebbe causare danni! L'uso di questo comando metterà quasi sicuramente la cinematica di basso livello in uno stato errato; emettere un G28 in seguito per ripristinare la cinematica. Questo comando è destinato alla diagnostica e al debug di basso livello.</p>
|
||||
<h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<valore>] [Y=<valore>] [Z=<valore>]</code>: forza il codice cinematico di basso livello a credere che la testa di stampa si trovi nella posizione cartesiana data. Questo è un comando diagnostico e di debug; utilizzare SET_GCODE_OFFSET e/o G92 per le normali trasformazioni degli assi. Se un asse non è specificato, verrà impostato automaticamente sulla posizione in cui la testa è stata comandata l'ultima volta. L'impostazione di una posizione errata o non valida può causare errori software interni. Questo comando potrebbe invalidare futuri controlli sui confini; emettere un G28 in seguito per ripristinare la cinematica.</p>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an axis is not specified then it will default to the position that the head was last commanded to. Setting an incorrect or invalid position may lead to internal software errors. Use the CLEAR parameter to forget the homing state for the given axes. Note that CLEAR will not override the previous functionality; if an axis is not specified to CLEAR it will have its kinematic position set as per above. This command may invalidate future boundary checks; issue a G28 afterwards to reset the kinematics.</p>
|
||||
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">¶</a></h3>
|
||||
<p>Il modulo gcode viene caricato automaticamente.</p>
|
||||
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4980,6 +5045,7 @@ section</a> is enabled.</p>
|
|||
<p>Il comando seguente è disponibile quando una <a href="Config_Reference.html#pin_output">sezione di configurazione pin_output</a> è abilitata.</p>
|
||||
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value></code>: Set the pin to the given output <code>VALUE</code>. VALUE should be 0 or 1 for "digital" output pins. For PWM pins, set to a value between 0.0 and 1.0, or between 0.0 and <code>scale</code> if a scale is configured in the output_pin config section.</p>
|
||||
<p><code>SET_PIN PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given pin. For example, if one defined a <code>[display_template my_pin_template]</code> config section then one could assign <code>TEMPLATE=my_pin_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the pin will be automatically set to the resulting value. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_PIN</code> commands to manage the values directly).</p>
|
||||
<h3 id="palette2">[palette2]<a class="headerlink" href="#palette2" title="Permanent link">¶</a></h3>
|
||||
<p>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#palette2">sezione di configurazione della palette2</a> è abilitata.</p>
|
||||
<p>Le stampe di Palette funzionano incorporando speciali OCodes (Codici Omega) nel file GCode:</p>
|
||||
|
|
@ -5037,6 +5103,10 @@ section</a> is enabled.</p>
|
|||
<p>The following command is available when a <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time config section</a> is enabled.</p>
|
||||
<h4 id="set_pin_1">SET_PIN<a class="headerlink" href="#set_pin_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value> [CYCLE_TIME=<cycle_time>]</code>: This command works similarly to <a href="#output_pin">output_pin</a> SET_PIN commands. The command here supports setting an explicit cycle time using the CYCLE_TIME parameter (specified in seconds). Note that the CYCLE_TIME parameter is not stored between SET_PIN commands (any SET_PIN command without an explicit CYCLE_TIME parameter will use the <code>cycle_time</code> specified in the pwm_cycle_time config section).</p>
|
||||
<h3 id="quad_gantry_level">[quad_gantry_level]<a class="headerlink" href="#quad_gantry_level" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#quad_gantry_level">quad_gantry_level config section</a> is enabled.</p>
|
||||
<h4 id="quad_gantry_level_1">QUAD_GANTRY_LEVEL<a class="headerlink" href="#quad_gantry_level_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>QUAD_GANTRY_LEVEL [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">¶</a></h3>
|
||||
<p>Il modulo query_adc viene caricato automaticamente.</p>
|
||||
<h4 id="query_adc_1">QUERY_ADC<a class="headerlink" href="#query_adc_1" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -5053,9 +5123,9 @@ section</a> is enabled.</p>
|
|||
<h4 id="measure_axes_noise">MEASURE_AXES_NOISE<a class="headerlink" href="#measure_axes_noise" title="Permanent link">¶</a></h4>
|
||||
<p><code>MEASURE_AXES_NOISE</code>: misura ed riporta il rumore per tutti gli assi di tutti i chip dell'accelerometro abilitati.</p>
|
||||
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">¶</a></h4>
|
||||
<p><code>TEST_RESONANCES AXIS=<asse> OUTPUT=<risonanze,dati_grezzi> [NAME=<nome>] [FREQ_START=<freq_min>] [FREQ_END=<freq_max>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [ POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]</code>: esegue il test di risonanza in tutti i punti sonda configurati per l'"asse" richiesto e misura l'accelerazione utilizzando i chip dell'accelerometro configurati per il rispettivo asse. "asse" può essere X o Y, oppure specificare una direzione arbitraria come <code>AXIS=dx,dy</code>, dove dx e dy sono numeri in virgola mobile che definiscono un vettore di direzione (es. <code>AXIS=X</code>, <code>AXIS=Y</code>, o <code>AXIS=1,-1</code> per definire una direzione diagonale). Nota che <code>AXIS=dx,dy</code> e <code>AXIS=-dx,-dy</code> sono equivalenti. <code>adxl345_chip_name</code> può essere uno o più chip adxl345 configurati, delimitati da virgole, ad esempio <code>CHIPS="adxl345, adxl345 rpi"</code>. Nota che <code>adxl345</code> può essere omesso dai chip adxl345 denominati. Se POINT è specificato, sovrascriverà i punti configurati in <code>[resonance_tester]</code>. Se <code>INPUT_SHAPING=0</code> o non impostato (predefinito), disabilita l'input shaping per il test di risonanza, perché non è valido eseguire il test di risonanza con input shaper abilitato. Il parametro <code>OUTPUT</code> è un elenco separato da virgole di cui verranno scritti gli output. Se viene richiesto <code>raw_data</code>, i dati grezzi dell'accelerometro vengono scritti in un file o in una serie di file <code>/tmp/raw_data_<asse>_[<nome_chip>_][<punto>_]<nome>.csv</code> con (<code><punto>_</code> parte del nome generata solo se è configurato più di 1 punto sonda o è specificato PUNTO). Se viene specificato <code>resonances</code>, la risposta in frequenza viene calcolata (su tutti i punti sonda) e scritta nel file <code>/tmp/resonances_<asse>_<nome>.csv</code>. Se non è impostato, OUTPUT è impostato su <code>risonanze</code> e NAME è impostato sull'ora corrente nel formato "AAAAMMGG_HHMMSS".</p>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> [OUTPUT=<resonances,raw_data>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [POINT=x,y,z] [INPUT_SHAPING=<0:1>]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>chip_name</code> can be one or more configured accel chips, delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<h4 id="shaper_calibrate">SHAPER_CALIBRATE<a class="headerlink" href="#shaper_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [MAX_SMOOTHING=<max_smoothing>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>][HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [MAX_SMOOTHING=<max_smoothing>] [INPUT_SHAPING=<0:1>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">¶</a></h3>
|
||||
<p>I seguenti comandi G-Code standard sono disponibili quando la <a href="Config_Reference.html#respond">sezione di configurazione di risposta</a> è abilitata:</p>
|
||||
<ul>
|
||||
|
|
@ -5161,7 +5231,7 @@ section</a> is enabled.</p>
|
|||
<h3 id="z_tilt">[z_tilt]<a class="headerlink" href="#z_tilt" title="Permanent link">¶</a></h3>
|
||||
<p>I seguenti comandi sono disponibili quando la <a href="Config_Reference.html#z_tilt">sezione z_tilt config</a> è abilitata.</p>
|
||||
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">¶</a></h4>
|
||||
<p><code>Z_TILT_ADJUST [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: questo comando sonda i punti specificati nella configurazione e quindi apporta regolazioni indipendenti a ciascun stepper Z per compensare l'inclinazione. Vedere il comando PROBE per i dettagli sui parametri opzionali della sonda. Il valore opzionale <code>HORIZONTAL_MOVE_Z</code> sovrascrive l'opzione <code>horizontal_move_z</code> specificata nel file di configurazione.</p>
|
||||
<p><code>Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when a <a href="Config_Reference.html#temperature_probe">temperature_probe config section</a> is enabled.</p>
|
||||
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
|
|||
|
|
@ -912,8 +912,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#configure-lis2dw-series" class="md-nav__link">
|
||||
Configure LIS2DW series
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -990,6 +990,13 @@
|
|||
Seleziona max_accel
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#unreliable-measurements-of-resonance-frequencies" class="md-nav__link">
|
||||
Unreliable measurements of resonance frequencies
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1774,8 +1781,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#configure-lis2dw-series" class="md-nav__link">
|
||||
Configure LIS2DW series
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1852,6 +1859,13 @@
|
|||
Seleziona max_accel
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#unreliable-measurements-of-resonance-frequencies" class="md-nav__link">
|
||||
Unreliable measurements of resonance frequencies
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1911,10 +1925,10 @@
|
|||
|
||||
|
||||
<h1 id="misurazione-delle-risonanze">Misurazione delle risonanze<a class="headerlink" href="#misurazione-delle-risonanze" title="Permanent link">¶</a></h1>
|
||||
<p>Klipper has built-in support for the ADXL345, MPU-9250 and LIS2DW compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345/LIS2DW can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper.</p>
|
||||
<p>Klipper has built-in support for the ADXL345, MPU-9250, LIS2DW and LIS3DH compatible accelerometers which can be used to measure resonance frequencies of the printer for different axes, and auto-tune <a href="Resonance_Compensation.html">input shapers</a> to compensate for resonances. Note that using accelerometers requires some soldering and crimping. The ADXL345 can be connected to the SPI interface of a Raspberry Pi or MCU board (it needs to be reasonably fast). The MPU family can be connected to the I2C interface of a Raspberry Pi directly, or to an I2C interface of an MCU board that supports 400kbit/s <em>fast mode</em> in Klipper. The LIS2DW and LIS3DH can be connected to either SPI or I2C with the same considerations as above.</p>
|
||||
<p>When sourcing accelerometers, be aware that there are a variety of different PCB board designs and different clones of them. If it is going to be connected to a 5V printer MCU ensure it has a voltage regulator and level shifters.</p>
|
||||
<p>For ADXL345s/LIS2DWs, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
|
||||
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
|
||||
<p>For ADXL345s, make sure that the board supports SPI mode (a small number of boards appear to be hard-configured for I2C by pulling SDO to GND).</p>
|
||||
<p>For MPU-9250/MPU-9255/MPU-6515/MPU-6050/MPU-6500s and LIS2DW/LIS3DH there are also a variety of board designs and clones with different I2C pull-up resistors which will need supplementing.</p>
|
||||
<h2 id="mcus-with-klipper-i2c-fast-mode-support">MCUs with Klipper I2C <em>fast-mode</em> Support<a class="headerlink" href="#mcus-with-klipper-i2c-fast-mode-support" title="Permanent link">¶</a></h2>
|
||||
<table>
|
||||
<thead>
|
||||
|
|
@ -1940,6 +1954,11 @@
|
|||
<td align="left">-</td>
|
||||
<td align="left">AT90usb646, AT90usb1286</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center">SAMD</td>
|
||||
<td align="left">SAMC21G18</td>
|
||||
<td align="left">SAMC21G18, SAMD21G18, SAMD21E18, SAMD21J18, SAMD21E15, SAMD51G19, SAMD51J19, SAMD51N19, SAMD51P20, SAME51J19, SAME51N19, SAME54P20</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="istruzioni-per-linstallazione">Istruzioni per l'installazione<a class="headerlink" href="#istruzioni-per-linstallazione" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
|
|||
</code></pre></div>
|
||||
|
||||
<p>Quindi, per installare NumPy nell'ambiente Klipper, esegui il comando:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v numpy
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/pip install -v "numpy<1.26"
|
||||
</code></pre></div>
|
||||
|
||||
<p>Nota che, a seconda delle prestazioni della CPU, potrebbe volerci <em>molto</em> tempo, fino a 10-20 minuti. Sii paziente e attendi il completamento dell'installazione. In alcune occasioni, se la scheda ha poca RAM, l'installazione potrebbe non riuscire e sarà necessario abilitare la swap.</p>
|
||||
<p>Note that, depending on the performance of the CPU, it may take <em>a lot</em> of time, up to 10-20 minutes. Be patient and wait for the completion of the installation. On some occasions, if the board has too little RAM the installation may fail and you will need to enable swap. Also note the forced version, due to newer versions of NumPY having requirements that may not be satisfied in some klipper python environments.</p>
|
||||
<p>Once installed please check that no errors show from the command:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/klippy-env/bin/python -c 'import numpy;'
|
||||
</code></pre></div>
|
||||
|
||||
<p>The correct output should simply be a new line.</p>
|
||||
<h4 id="configura-adxl345-con-rpi">Configura ADXL345 con RPi<a class="headerlink" href="#configura-adxl345-con-rpi" title="Permanent link">¶</a></h4>
|
||||
<p>First, check and follow the instructions in the <a href="RPi_microcontroller.html">RPi Microcontroller document</a> to setup the "linux mcu" on the Raspberry Pi. This will configure a second Klipper instance that runs on your Pi.</p>
|
||||
<p>Assicurati che il driver SPI di Linux sia abilitato eseguendo <code>sudo raspi-config</code> e abilitando SPI nel menu "Opzioni di interfaccia".</p>
|
||||
|
|
@ -2257,7 +2281,7 @@ pin: adxl:gpio23
|
|||
</code></pre></div>
|
||||
|
||||
<p>Riavvia Klipper tramite il comando <code>RESTART</code>.</p>
|
||||
<h4 id="configure-lis2dw-series">Configure LIS2DW series<a class="headerlink" href="#configure-lis2dw-series" title="Permanent link">¶</a></h4>
|
||||
<h4 id="configure-lis2dw-series-over-spi">Configure LIS2DW series over SPI<a class="headerlink" href="#configure-lis2dw-series-over-spi" title="Permanent link">¶</a></h4>
|
||||
<div class="highlight"><pre><span></span><code>[mcu lis]
|
||||
# Change <mySerial> to whatever you found above. For example,
|
||||
# usb-Klipper_rp2040_E661640843545B2E-if00
|
||||
|
|
@ -2482,6 +2506,8 @@ max_smoothing: 0.25 # un esempio
|
|||
|
||||
<p>so that it can calculate the maximum acceleration recommendations correctly. Note that the <code>SHAPER_CALIBRATE</code> command already takes the configured <code>square_corner_velocity</code> parameter into account, and there is no need to specify it explicitly.</p>
|
||||
<p>Se stai eseguendo una ricalibrazione dello shaper e lo smoothing riportato per la configurazione dello shaper suggerita è quasi lo stesso di quello ottenuto durante la calibrazione precedente, questo passaggio può essere saltato.</p>
|
||||
<h3 id="unreliable-measurements-of-resonance-frequencies">Unreliable measurements of resonance frequencies<a class="headerlink" href="#unreliable-measurements-of-resonance-frequencies" title="Permanent link">¶</a></h3>
|
||||
<p>Sometimes the resonance measurements can produce bogus results, leading to the incorrect suggestions for the input shapers. This can be caused by a variety of reasons, including running fans on the toolhead, incorrect position or non-rigid mounting of the accelerometer, or mechanical problems such as loose belts or binding or bumpy axis. Keep in mind that all fans should be disabled for resonance testing, especially the noisy ones, and that the accelerometer should be rigidly mounted on the corresponding moving part (e.g. on the bed itself for the bed slinger, or on the extruder of the printer itself and not the carriage, and some people get better results by mounting the accelerometer on the nozzle itself). As for mechanical problems, the user should inspect if there is any fault that can be fixed with a moving axis (e.g. linear guide rails cleaned up and lubricated and V-slot wheels tension adjusted correctly). If none of that helps, a user may try the other shapers from the produced list besides the one recommended by default.</p>
|
||||
<h3 id="test-di-assi-personalizzati">Test di assi personalizzati<a class="headerlink" href="#test-di-assi-personalizzati" title="Permanent link">¶</a></h3>
|
||||
<p>Il comando <code>TEST_RESONANCES</code> supporta assi personalizzati. Anche se questo non è molto utile per la calibrazione del input shaper, può essere utilizzato per studiare in profondità le risonanze della stampante e per controllare, ad esempio, la tensione della cinghia.</p>
|
||||
<p>Per controllare la tensione della cinghia sulle stampanti CoreXY, eseguire</p>
|
||||
|
|
|
|||
|
|
@ -1447,7 +1447,7 @@ git clone https://github.com/Klipper3d/klipper
|
|||
<h2 id="configuring-octoprint-to-use-klipper">Configuring OctoPrint to use Klipper<a class="headerlink" href="#configuring-octoprint-to-use-klipper" title="Permanent link">¶</a></h2>
|
||||
<p>The OctoPrint web server needs to be configured to communicate with the Klipper host software. Using a web browser, login to the OctoPrint web page and then configure the following items:</p>
|
||||
<p>Navigate to the Settings tab (the wrench icon at the top of the page). Under "Serial Connection" in "Additional serial ports" add:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.sock
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.serial
|
||||
</code></pre></div>
|
||||
|
||||
<p>Then click "Save".</p>
|
||||
|
|
|
|||
|
|
@ -1480,7 +1480,7 @@
|
|||
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" style="margin:25px"/></a></p>
|
||||
<p>BIGTREETECH è lo sponsor ufficiale della scheda madre di Klipper. BIGTREETECH si impegna a sviluppare prodotti innovativi e competitivi per servire meglio la comunità della stampa 3D. Seguili su <a href="https://www.facebook.com/BIGTREETECH">Facebook</a> o <a href="https://twitter.com/BigTreeTech">Twitter</a>.</p>
|
||||
<h2 id="sponsors_1">Sponsors<a class="headerlink" href="#sponsors_1" title="Permanent link">¶</a></h2>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a> <a href="https://peopoly.net"><img src="./img/sponsors/peopoly-logo.png" width="200" style="margin:25px" /></a></p>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a></p>
|
||||
<h2 id="sviluppatori-klipper">Sviluppatori Klipper<a class="headerlink" href="#sviluppatori-klipper" title="Permanent link">¶</a></h2>
|
||||
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">¶</a></h3>
|
||||
<p>Kevin è l'autore originale e l'attuale manutentore di Klipper. Fai una donazione su: <a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> o <a href="https://www.patreon.com/koconnor">https://www.patreon.com/koconnor</a></p>
|
||||
|
|
|
|||
Binary file not shown.
File diff suppressed because one or more lines are too long
110
it/sitemap.xml
110
it/sitemap.xml
|
|
@ -2,277 +2,277 @@
|
|||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
108
sitemap.xml
108
sitemap.xml
|
|
@ -2,272 +2,272 @@
|
|||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
BIN
sitemap.xml.gz
BIN
sitemap.xml.gz
Binary file not shown.
|
|
@ -711,6 +711,33 @@
|
|||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1384,6 +1411,33 @@
|
|||
Overview of compensation usage
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="Overview of compensation usage">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1420,19 +1474,43 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
|
|||
<blockquote>
|
||||
<p><strong>Tip:</strong> Make sure the <a href="Config_Reference.html#probe">probe X and Y offsets</a> are correctly set as they greatly influence calibration.</p>
|
||||
</blockquote>
|
||||
<h3 id="basic-usage-x-axis-calibration">Basic Usage: X-Axis Calibration<a class="headerlink" href="#basic-usage-x-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<ol>
|
||||
<li>After setting up the [axis_twist_compensation] module, perform <code>AXIS_TWIST_COMPENSATION_CALIBRATE</code></li>
|
||||
<li>After setting up the <code>[axis_twist_compensation]</code> module, run:</li>
|
||||
</ol>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE
|
||||
</code></pre></div>
|
||||
|
||||
<p>This command will calibrate the X-axis by default. - The calibration wizard will prompt you to measure the probe Z offset at several points along the bed. - By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=<value></code></p>
|
||||
<ol>
|
||||
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).</li>
|
||||
<li>
|
||||
<p><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</p>
|
||||
<ul>
|
||||
<li>The calibration wizard will prompt you to measure the probe Z offset at a few points along the bed</li>
|
||||
<li>The calibration defaults to 3 points but you can use the option <code>SAMPLE_COUNT=</code> to use a different number.</li>
|
||||
<li><a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a></li>
|
||||
<li><a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a></li>
|
||||
</ul>
|
||||
<ol>
|
||||
<li><a href="Probe_Calibrate.html#calibrating-probe-z-offset">Adjust your Z offset</a></li>
|
||||
<li>Perform automatic/probe-based bed tramming operations, such as <a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a>, <a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a> etc</li>
|
||||
<li>Home all axis, then perform a <a href="Bed_Mesh.html">Bed Mesh</a> if required</li>
|
||||
<li>Perform a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> as desired</li>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Finalize the Setup:</strong></p>
|
||||
<ul>
|
||||
<li>Home all axes, and perform a <a href="Bed_Mesh.html">Bed Mesh</a> if necessary.</li>
|
||||
<li>Run a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> if needed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h3 id="for-y-axis-calibration">For Y-Axis Calibration<a class="headerlink" href="#for-y-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<p>The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y
|
||||
</code></pre></div>
|
||||
|
||||
<p>This will guide you through the same measuring process as for the X-axis.</p>
|
||||
<h3 id="automatic-calibration-for-both-axes">Automatic Calibration for Both Axes<a class="headerlink" href="#automatic-calibration-for-both-axes" title="Permanent link">¶</a></h3>
|
||||
<p>To perform automatic calibration for both the X and Y axes without manual intervention, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
|
||||
</code></pre></div>
|
||||
|
||||
<p>In this mode, the calibration process will run for both axes automatically.</p>
|
||||
<blockquote>
|
||||
<p><strong>Tip:</strong> Bed temperature and nozzle temperature and size do not seem to have an influence to the calibration process.</p>
|
||||
</blockquote>
|
||||
|
|
|
|||
|
|
@ -1968,7 +1968,7 @@ fade_target: 0
|
|||
<li><code>fade_target: 0</code> <em>Default Value: The average Z value of the mesh</em> The <code>fade_target</code> can be thought of as an additional Z offset applied to the entire bed after fade completes. Generally speaking we would like this value to be 0, however there are circumstances where it should not be. For example, lets assume your homing position on the bed is an outlier, its .2 mm lower than the average probed height of the bed. If the <code>fade_target</code> is 0, fade will shrink the print by an average of .2 mm across the bed. By setting the <code>fade_target</code> to .2, the homed area will expand by .2 mm, however, the rest of the bed will be accurately sized. Generally its a good idea to leave <code>fade_target</code> out of the configuration so the average height of the mesh is used, however it may be desirable to manually adjust the fade target if one wants to print on a specific portion of the bed.</li>
|
||||
</ul>
|
||||
<h3 id="configuring-the-zero-reference-position">Configuring the zero reference position<a class="headerlink" href="#configuring-the-zero-reference-position" title="Permanent link">¶</a></h3>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="./Manual_Level#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="Manual_Level.html#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<div class="highlight"><pre><span></span><code>[bed_mesh]
|
||||
speed: 120
|
||||
horizontal_move_z: 5
|
||||
|
|
|
|||
|
|
@ -1195,6 +1195,13 @@
|
|||
SAMD51 步速率基準測試
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1205,8 +1212,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040" class="md-nav__link">
|
||||
RP2040 步速率基準測試
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1613,6 +1620,13 @@
|
|||
SAMD51 步速率基準測試
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1623,8 +1637,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040" class="md-nav__link">
|
||||
RP2040 步速率基準測試
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -2122,6 +2136,34 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="same70-step-rate-benchmark">SAME70 step rate benchmark<a class="headerlink" href="#same70-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the SAME70:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=PC18 dir_pin=PB5 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=PC16 dir_pin=PD10 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=2 step_pin=PC28 dir_pin=PA4 invert_step=-1 step_pulse_ticks=0
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>34e9ea55</code> with gcc version <code>arm-none-eabi-gcc (NixOS 10.3-2021.10) 10.3.1</code> on a SAME70Q20B micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>same70</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1個步進電機</td>
|
||||
<td>45</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3個步進電機</td>
|
||||
<td>190</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="ar100-step-rate-benchmark">AR100 step rate benchmark<a class="headerlink" href="#ar100-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on AR100 CPU (Allwinner A64):</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2131,7 +2173,7 @@ config_stepper oid=2 step_pin=PL12 dir_pin=PE16 invert_step=-1 step_pulse_ticks=
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>08d037c6</code> with gcc version <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> on an Allwinner A64-H micro-controller.</p>
|
||||
<p>The test was last run on commit <code>b7978d37</code> with gcc version <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> on an Allwinner A64-H micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -2150,8 +2192,8 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="rp2040">RP2040 步速率基準測試<a class="headerlink" href="#rp2040" title="Permanent link">¶</a></h3>
|
||||
<p>RP2040 上使用以下配置序列：</p>
|
||||
<h3 id="rpxxxx-step-rate-benchmark">RPxxxx step rate benchmark<a class="headerlink" href="#rpxxxx-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040 and RP2350:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=gpio25 dir_pin=gpio3 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=gpio26 dir_pin=gpio4 invert_step=-1 step_pulse_ticks=0
|
||||
|
|
@ -2159,11 +2201,11 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>該測試最後一次在 Raspberry Pi Pico 板上使用 gcc 版本 <code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code>和提交 <code>59314d99</code> 執行。</p>
|
||||
<p>The test was last run on commit <code>f6718291</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2040</th>
|
||||
<th>rp2040 (*)</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
|
@ -2178,6 +2220,25 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2350</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1個步進電機</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3個步進電機</td>
|
||||
<td>169</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 125Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM core cycles.</p>
|
||||
<h3 id="linux-mcu">Linux MCU 步速率基準測試<a class="headerlink" href="#linux-mcu" title="Permanent link">¶</a></h3>
|
||||
<p>樹莓派上使用以下配置序列：</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2311,9 +2372,15 @@ get_uptime
|
|||
</tr>
|
||||
<tr>
|
||||
<td>rp2040 (USB)</td>
|
||||
<td>873K</td>
|
||||
<td>c5667193</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2350 (USB)</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
|
|||
|
|
@ -1580,7 +1580,7 @@
|
|||
<li>參考位於klippy/kinematics/目錄已有的運動學類。動力學類旨在將一個笛卡爾座標系中的運動轉化為各個步進電機的運動。建議複製已有的程式碼，並在其基礎上進行修改。</li>
|
||||
<li>若需要的運動學方程未被Klipper涵蓋，則應使用C語言實現新動力學體系中各個步進電機的位置方程（見klippy/chelper/，如kin_cart.c, kin_corexy.c, and kin_delta.c）。位置方程中應呼叫<code>move_get_coord()</code>以將運動的時間點（單位 ：秒）轉化為對應的笛卡爾座標位置（單位：毫米），進而計算目標步進電機運動目標位置（單位：毫米）。</li>
|
||||
<li>在新的運動學類中實現<code>calc_position</code>方法。該方法將通過各個步進電機的位置計算笛卡爾座標系下的列印頭位置；同時該方法通常只在回零和z探測時使用，因此無需過分追求效率。</li>
|
||||
<li>之後實現<code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>set_position()</code>方法。這些函式用於特定的運動學檢查。在開發的初期，可以直接使用已有程式碼。</li>
|
||||
<li>Other methods. Implement the <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>clear_homing_state()</code>, and <code>set_position()</code> methods. These functions are typically used to provide kinematic specific checks. However, at the start of development one can use boiler-plate code here.</li>
|
||||
<li>新增測試實例。建立一個G程式碼檔案，其中包含一系列的運動命令用於測試新增的運動學模型。 按照<a href="Debugging.html">除錯文件</a>將該G程式碼檔案轉換為微控制器命令。在遭遇困難狀況和檢查數據傳遞相當有用。</li>
|
||||
</ol>
|
||||
<h2 id="_8">移植到新的微控制器<a class="headerlink" href="#_8" title="Permanent link">¶</a></h2>
|
||||
|
|
|
|||
|
|
@ -1396,6 +1396,11 @@
|
|||
<p>本文件涵蓋了軟體更新中對配置檔案不向后相容的部分。在升級 Klipper 時，最好也檢視一下這份文件。</p>
|
||||
<p>本文件中的所有日期都是不精確的。</p>
|
||||
<h2 id="_2">變更<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
<p>20241203: The resonance test has been changed to include slow sweeping moves. This change requires that testing point(s) have some clearance in X/Y plane (+/- 30 mm from the test point should suffice when using the default settings). The new test should generally produce more accurate and reliable test results. However, if required, the previous test behavior can be restored by adding options <code>sweeping_period: 0</code> and <code>accel_per_hz: 75</code> to the <code>[resonance_tester]</code> config section.</p>
|
||||
<p>20241201: In some cases Klipper may have ignored leading characters or spaces in a traditional G-Code command. For example, "99M123" may have been interpreted as "M123" and "M 321" may have been interpreted as "M321". Klipper will now report these cases with an "Unknown command" warning.</p>
|
||||
<p>20241112: Option <code>CHIPS=<chip_name></code> in <code>TEST_RESONANCES</code> and <code>SHAPER_CALIBRATE</code> requires specifying the full name(s) of the accel chip(s). For example, <code>adxl345 rpi</code> instead of short name - <code>rpi</code>.</p>
|
||||
<p>20240912: <code>SET_PIN</code>, <code>SET_SERVO</code>, <code>SET_FAN_SPEED</code>, <code>M106</code>, and <code>M107</code> commands are now collated. Previously, if many updates to the same object were issued faster than the minimum scheduling time (typically 100ms) then actual updates could be queued far into the future. Now if many updates are issued in rapid succession then it is possible that only the latest request will be applied. If the previous behavior is requried then consider adding explicit <code>G4</code> delay commands between updates.</p>
|
||||
<p>20240912: Support for <code>maximum_mcu_duration</code> and <code>static_value</code> parameters in <code>[output_pin]</code> config sections have been removed. These options have been deprecated since 20240123.</p>
|
||||
<p>20240415: The <code>on_error_gcode</code> parameter in the <code>[virtual_sdcard]</code> config section now has a default. If this parameter is not specified it now defaults to <code>TURN_OFF_HEATERS</code>. If the previous behavior is desired (take no default action on an error during a virtual_sdcard print) then define <code>on_error_gcode</code> with an empty value.</p>
|
||||
<p>20240313: The <code>max_accel_to_decel</code> parameter in the <code>[printer]</code> config section has been deprecated. The <code>ACCEL_TO_DECEL</code> parameter of the <code>SET_VELOCITY_LIMIT</code> command has been deprecated. The <code>printer.toolhead.max_accel_to_decel</code> status has been removed. Use the <a href="Config_Reference.html#printer">minimum_cruise_ratio parameter</a> instead. The deprecated features will be removed in the near future, and using them in the interim may result in subtly different behavior.</p>
|
||||
<p>20240215: Several deprecated features have been removed. Using "NTC 100K beta 3950" as a thermistor name has been removed (deprecated on 20211110). The <code>SYNC_STEPPER_TO_EXTRUDER</code> and <code>SET_EXTRUDER_STEP_DISTANCE</code> commands have been removed, and the extruder <code>shared_heater</code> config option has been removed (deprecated on 20220210). The bed_mesh <code>relative_reference_index</code> option has been removed (deprecated on 20230619).</p>
|
||||
|
|
|
|||
|
|
@ -938,6 +938,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1537,6 +1544,13 @@
|
|||
hd44780_spi顯示屏
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1670,8 +1684,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -3032,6 +3046,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3631,6 +3652,13 @@
|
|||
hd44780_spi顯示屏
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3764,8 +3792,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -5253,8 +5281,9 @@ cs_pin:
|
|||
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS2DW accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis2dw]
|
||||
cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
|
|
@ -5264,6 +5293,43 @@ cs_pin:
|
|||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="lis3dh">[lis3dh]<a class="headerlink" href="#lis3dh" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS3DH accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis3dh]
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
|
@ -5312,11 +5378,14 @@ cs_pin:
|
|||
# auto-calibration (with 'SHAPER_CALIBRATE' command). By default no
|
||||
# maximum smoothing is specified. Refer to Measuring_Resonances guide
|
||||
# for more details on using this feature.
|
||||
#move_speed: 50
|
||||
# The speed (in mm/s) to move the toolhead to and between test points
|
||||
# during the calibration. The default is 50.
|
||||
#min_freq: 5
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 133.33
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 75
|
||||
#accel_per_hz: 60
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
# value, the higher is the energy of the oscillations. Can be set to
|
||||
|
|
@ -5330,6 +5399,13 @@ cs_pin:
|
|||
# hz_per_sec. Small values make the test slow, and the large values
|
||||
# will decrease the precision of the test. The default value is 1.0
|
||||
# (Hz/sec == sec^-2).
|
||||
#sweeping_accel: 400
|
||||
# An acceleration of slow sweeping moves. The default is 400 mm/sec^2.
|
||||
#sweeping_period: 1.2
|
||||
# A period of slow sweeping moves. Setting this parameter to 0
|
||||
# disables slow sweeping moves. Avoid setting it to a too small
|
||||
# non-zero value in order to not poison the measurements.
|
||||
# The default is 1.2 sec which is a good all-round choice.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_14">配置檔案助手<a class="headerlink" href="#_14" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5553,7 +5629,7 @@ sensor_type: ldc1612
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">¶</a></h3>
|
||||
<p>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>
|
||||
<p>A tool to compensate for inaccurate probe readings due to twist in X or Y gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
|
||||
<div class="highlight"><pre><span></span><code>[axis_twist_compensation]
|
||||
#speed: 50
|
||||
# The speed (in mm/s) of non-probing moves during the calibration.
|
||||
|
|
@ -5564,16 +5640,33 @@ sensor_type: ldc1612
|
|||
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.
|
||||
# calibration position.
|
||||
calibrate_end_x: 200
|
||||
# Defines the maximum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the ending
|
||||
# calibration position. This parameter must be provided.
|
||||
# calibration position.
|
||||
calibrate_y: 112.5
|
||||
# Defines the Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle during the
|
||||
# calibration process. This parameter must be provided and is recommended to
|
||||
# calibration process. This parameter is recommended to
|
||||
# be near the center of the bed
|
||||
|
||||
# For Y-axis twist compensation, specify the following parameters:
|
||||
calibrate_start_y: ...
|
||||
# Defines the minimum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the starting
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_end_y: ...
|
||||
# Defines the maximum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the ending
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_x: ...
|
||||
# Defines the X coordinate of the calibration for Y axis twist compensation
|
||||
# This should be the X coordinate that positions the nozzle during the
|
||||
# calibration process for Y axis twist compensation. This parameter must be
|
||||
# provided and is recommended to be near the center of the bed.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_16">額外的步進電機和擠出機<a class="headerlink" href="#_16" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5851,6 +5944,10 @@ extruder:
|
|||
# "calibration_extruder_temp" option is set. Its recommended to heat
|
||||
# the extruder some distance from the bed to minimize its impact on
|
||||
# the probe coil temperature. The default is 50.
|
||||
#max_validation_temp: 60.
|
||||
# The maximum temperature used to validate the calibration. It is
|
||||
# recommended to set this to a value between 100 and 120 for enclosed
|
||||
# printers. The default is 60.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_18">溫度傳感器<a class="headerlink" href="#_18" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -6953,6 +7050,7 @@ run_current:
|
|||
#driver_SEIMIN: 0
|
||||
#driver_SFILT: 0
|
||||
#driver_SG4_ANGLE_OFFSET: 1
|
||||
#driver_SLOPE_CONTROL: 0
|
||||
# Set the given register during the configuration of the TMC2240
|
||||
# chip. This may be used to set custom motor parameters. The
|
||||
# defaults for each parameter are next to the parameter name in the
|
||||
|
|
@ -7223,72 +7321,82 @@ wiper:
|
|||
<p>支持連接到微控制器的顯示屏。</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type:
|
||||
# 使用的 LCD 晶片型別。這可以是「hd44780」、「hd44780_spi」、
|
||||
# 「st7920」、「emulated_st7920」、「uc1701」、「ssd1306」、或「sh1106」。
|
||||
# 有關不同的LCD晶片型別和它們特有的參數，請檢視下面的顯示屏分段。
|
||||
# 必須提供此參數。
|
||||
# The type of LCD chip in use. This may be "hd44780", "hd44780_spi",
|
||||
# "aip31068_spi", "st7920", "emulated_st7920", "uc1701", "ssd1306", or
|
||||
# "sh1106".
|
||||
# See the display sections below for information on each type and
|
||||
# additional parameters they provide. This parameter must be
|
||||
# provided.
|
||||
#display_group:
|
||||
# 顯示在這個顯示屏上的 display_data 組。它決定了這個螢幕顯示
|
||||
# 的內容（詳見「display_data」分段）。
|
||||
# hd44780 預設使用 _default_20x4，其他顯示屏則預設使用 _default_16x4。
|
||||
# The name of the display_data group to show on the display. This
|
||||
# controls the content of the screen (see the "display_data" section
|
||||
# for more information). The default is _default_20x4 for hd44780 or
|
||||
# aip31068_spi displays and _default_16x4 for other displays.
|
||||
#menu_timeout:
|
||||
# 菜單超時時間。在不活躍給定時間后將會退出菜單或在 autorun 啟用時
|
||||
# 回到根菜單。
|
||||
# 預設為 0 秒（禁用）。
|
||||
# Timeout for menu. Being inactive this amount of seconds will
|
||||
# trigger menu exit or return to root menu when having autorun
|
||||
# enabled. The default is 0 seconds (disabled)
|
||||
#menu_root:
|
||||
# 在主螢幕按下編碼器時顯示的主菜單段名稱。
|
||||
# 預設為 __main，這會顯示在 klippy/extras/display/menu.cfg中定義的主菜單。
|
||||
# Name of the main menu section to show when clicking the encoder
|
||||
# on the home screen. The defaults is __main, and this shows the
|
||||
# the default menus as defined in klippy/extras/display/menu.cfg
|
||||
#menu_reverse_navigation:
|
||||
# 啟用時反轉上滾動和下滾動。
|
||||
# 預設為False。這是一個可選參數。
|
||||
# When enabled it will reverse up and down directions for list
|
||||
# navigation. The default is False. This parameter is optional.
|
||||
#encoder_pins:
|
||||
# 連線到編碼器的引腳。使用編碼器時必須提供兩個引腳。
|
||||
# 使用菜單時必須提供此參數。
|
||||
# The pins connected to encoder. 2 pins must be provided when using
|
||||
# encoder. This parameter must be provided when using menu.
|
||||
#encoder_steps_per_detent:
|
||||
# 編碼器在每一個凹陷處（"click"）發出多少步。如果編碼器需要轉過兩個凹
|
||||
# 陷才能在條目之間移動，或者轉過一個凹痕會在兩個詞條之間移動/跳過
|
||||
# 一個詞條，可以嘗試改變這個值。
|
||||
# 允許的值是2 （半步）或 4（全步）。
|
||||
# 預設為 4。
|
||||
# How many steps the encoder emits per detent ("click"). If the
|
||||
# encoder takes two detents to move between entries or moves two
|
||||
# entries from one detent, try changing this. Allowed values are 2
|
||||
# (half-stepping) or 4 (full-stepping). The default is 4.
|
||||
#click_pin:
|
||||
# 連線到 "enter" 按鈕或編碼器按壓的引腳。
|
||||
# 使用菜單時必須提供此參數。
|
||||
# 如果定義了 「analog_range_click_pin」配置參數，則這個參數的引腳需要
|
||||
# 是模擬引腳。
|
||||
# The pin connected to 'enter' button or encoder 'click'. This
|
||||
# parameter must be provided when using menu. The presence of an
|
||||
# 'analog_range_click_pin' config parameter turns this parameter
|
||||
# from digital to analog.
|
||||
#back_pin:
|
||||
# 連線到「back」按鈕的引腳。這是一個可選參數，菜單不需要這個按鈕。
|
||||
# 如果定義了 「analog_range_back_pin」配置參數，則這個參數的引腳需要
|
||||
# 是模擬引腳。
|
||||
# The pin connected to 'back' button. This parameter is optional,
|
||||
# menu can be used without it. The presence of an
|
||||
# 'analog_range_back_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#up_pin:
|
||||
# 連線到「up」按鈕的引腳。在不使用編碼器時使用菜單必須提供這個參數。
|
||||
# 如果定義了 「analog_range_up_pin」配置參數，則這個參數的引腳需要
|
||||
# 是模擬引腳。
|
||||
# The pin connected to 'up' button. This parameter must be provided
|
||||
# when using menu without encoder. The presence of an
|
||||
# 'analog_range_up_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#down_pin:
|
||||
# 連線到「down」按鈕的引腳。 在不使用編碼器時使用菜單必須提供這個參數。
|
||||
# 如果定義了 「analog_range_down_pin」配置參數，則這個參數的引腳需要
|
||||
# 是模擬引腳。
|
||||
# The pin connected to 'down' button. This parameter must be
|
||||
# provided when using menu without encoder. The presence of an
|
||||
# 'analog_range_down_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#kill_pin:
|
||||
# 連線到「kill」按鈕的引腳。 這個按鈕將會觸發緊急停止。
|
||||
# 如果定義了 「analog_range_kill_pin」配置參數，則這個參數的引腳需要
|
||||
# 是模擬引腳。
|
||||
# The pin connected to 'kill' button. This button will call
|
||||
# emergency stop. The presence of an 'analog_range_kill_pin' config
|
||||
# parameter turns this parameter from digital to analog.
|
||||
#analog_pullup_resistor: 4700
|
||||
# 連線到模擬按鈕的拉高電阻阻值(ohms)
|
||||
# 預設為 4700 ohms。
|
||||
# The resistance (in ohms) of the pullup attached to the analog
|
||||
# button. The default is 4700 ohms.
|
||||
#analog_range_click_pin:
|
||||
# 'enter'按鈕的阻值範圍。
|
||||
# 在使用模擬按鈕時必須提供由逗號分隔最小和最大值。
|
||||
# The resistance range for a 'enter' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_back_pin:
|
||||
# 'back'按鈕的阻值範圍。
|
||||
# 在使用模擬按鈕時必須提供由逗號分隔最小和最大值。
|
||||
# The resistance range for a 'back' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_up_pin:
|
||||
# 'up'按鈕的阻值範圍。
|
||||
# 在使用模擬按鈕時必須提供由逗號分隔最小和最大值。
|
||||
# The resistance range for a 'up' button. Range minimum and maximum
|
||||
# comma-separated values must be provided when using analog button.
|
||||
#analog_range_down_pin:
|
||||
# 'down'按鈕的阻值範圍。
|
||||
# 在使用模擬按鈕時必須提供由逗號分隔最小和最大值。
|
||||
# The resistance range for a 'down' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_kill_pin:
|
||||
# 'kill'按鈕的阻值範圍。
|
||||
# 在使用模擬按鈕時必須提供由逗號分隔最小和最大值。
|
||||
# The resistance range for a 'kill' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="hd44780">hd44780顯示屏<a class="headerlink" href="#hd44780" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -7339,6 +7447,26 @@ spi_software_miso_pin:
|
|||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="aip31068_spi-display">aip31068_spi display<a class="headerlink" href="#aip31068_spi-display" title="Permanent link">¶</a></h4>
|
||||
<p>Information on configuring an aip31068_spi display - a very similar to hd44780_spi a 20x04 (20 symbols by 4 lines) display with slightly different internal protocol.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type: aip31068_spi
|
||||
latch_pin:
|
||||
spi_software_sclk_pin:
|
||||
spi_software_mosi_pin:
|
||||
spi_software_miso_pin:
|
||||
# The pins connected to the shift register controlling the display.
|
||||
# The spi_software_miso_pin needs to be set to an unused pin of the
|
||||
# printer mainboard as the shift register does not have a MISO pin,
|
||||
# but the software spi implementation requires this pin to be
|
||||
# configured.
|
||||
#line_length:
|
||||
# Set the number of characters per line for an hd44780 type lcd.
|
||||
# Possible values are 20 (default) and 16. The number of lines is
|
||||
# fixed to 4.
|
||||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="st7920">st7920 顯示屏<a class="headerlink" href="#st7920" title="Permanent link">¶</a></h4>
|
||||
<p>有關配置 st7920 類顯示屏的資訊（可用於 "RepRapDiscount 12864 Full Graphic Smart Controller" 型別的顯示屏）。</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
|
|
@ -7682,7 +7810,7 @@ sensor_type:
|
|||
# This must be one of the supported sensor types, see below.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="xh711">XH711<a class="headerlink" href="#xh711" title="Permanent link">¶</a></h4>
|
||||
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">¶</a></h4>
|
||||
<p>This is a 24 bit low sample rate chip using "bit-bang" communications. It is suitable for filament scales.</p>
|
||||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
sensor_type: hx711
|
||||
|
|
@ -7745,13 +7873,30 @@ data_ready_pin:
|
|||
#gain: 128
|
||||
# Valid gain values are 128, 64, 32, 16, 8, 4, 2, 1
|
||||
# The default is 128
|
||||
#pga_bypass: False
|
||||
# Disable the internal Programmable Gain Amplifier. If
|
||||
# True the PGA will be disabled for gains 1, 2, and 4. The PGA is always
|
||||
# enabled for gain settings 8 to 128, regardless of the pga_bypass setting.
|
||||
# If AVSS is used as an input pga_bypass is forced to True.
|
||||
# The default is False.
|
||||
#sample_rate: 660
|
||||
# This chip supports two ranges of sample rates, Normal and Turbo. In turbo
|
||||
# mode the chips c internal clock runs twice as fast and the SPI communication
|
||||
# mode the chip's internal clock runs twice as fast and the SPI communication
|
||||
# speed is also doubled.
|
||||
# Normal sample rates: 20, 45, 90, 175, 330, 600, 1000
|
||||
# Turbo sample rates: 40, 90, 180, 350, 660, 1200, 2000
|
||||
# The default is 660
|
||||
#input_mux:
|
||||
# Input multiplexer configuration, select a pair of pins to use. The first pin
|
||||
# is the positive, AINP, and the second pin is the negative, AINN. Valid
|
||||
# values are: 'AIN0_AIN1', 'AIN0_AIN2', 'AIN0_AIN3', 'AIN1_AIN2', 'AIN1_AIN3',
|
||||
# 'AIN2_AIN3', 'AIN1_AIN0', 'AIN3_AIN2', 'AIN0_AVSS', 'AIN1_AVSS', 'AIN2_AVSS'
|
||||
# and 'AIN3_AVSS'. If AVSS is used the PGA is bypassed and the pga_bypass
|
||||
# setting will be forced to True.
|
||||
# The default is AIN0_AIN1.
|
||||
#vref:
|
||||
# The selected voltage reference. Valid values are: 'internal', 'REF0', 'REF1'
|
||||
# and 'analog_supply'. Default is 'internal'.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_27">控制板特定硬體支援<a class="headerlink" href="#_27" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -7890,11 +8035,11 @@ serial:
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<p>Magnetic hall angle sensor support for reading stepper motor angle shaft measurements using a1333, as5047d, or tle5012b SPI chips. The measurements are available via the <a href="API_Server.html">API Server</a> and <a href="Debugging.html#motion-analysis-and-data-logging">motion analysis tool</a>. See the <a href="G-Codes.html#angle">G-Code reference</a> for available commands.</p>
|
||||
<p>Magnetic hall angle sensor support for reading stepper motor angle shaft measurements using a1333, as5047d, mt6816, mt6826s, or tle5012b SPI chips. The measurements are available via the <a href="API_Server.html">API Server</a> and <a href="Debugging.html#motion-analysis-and-data-logging">motion analysis tool</a>. See the <a href="G-Codes.html#angle">G-Code reference</a> for available commands.</p>
|
||||
<div class="highlight"><pre><span></span><code>[angle my_angle_sensor]
|
||||
sensor_type:
|
||||
# The type of the magnetic hall sensor chip. Available choices are
|
||||
# "a1333", "as5047d", and "tle5012b". This parameter must be
|
||||
# "a1333", "as5047d", "mt6816", "mt6826s", and "tle5012b". This parameter must be
|
||||
# specified.
|
||||
#sample_period: 0.000400
|
||||
# The query period (in seconds) to use during measurements. The
|
||||
|
|
@ -7938,7 +8083,7 @@ cs_pin:
|
|||
<h3 id="i2c">通用 I2C 設定<a class="headerlink" href="#i2c" title="Permanent link">¶</a></h3>
|
||||
<p>以下參數通常適用於使用 I2C 總線的設備。</p>
|
||||
<p>Note that Klipper's current micro-controller support for I2C is generally not tolerant to line noise. Unexpected errors on the I2C wires may result in Klipper raising a run-time error. Klipper's support for error recovery varies between each micro-controller type. It is generally recommended to only use I2C devices that are on the same printed circuit board as the micro-controller.</p>
|
||||
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000 (<em>standard mode</em>, 100kbit/s). The Klipper "Linux" micro-controller supports a 400000 speed (<em>fast mode</em>, 400kbit/s), but it must be <a href="RPi_microcontroller.html#optional-enabling-i2c">set in the operating system</a> and the <code>i2c_speed</code> parameter is otherwise ignored. The Klipper "RP2040" micro-controller and ATmega AVR family support a rate of 400000 via the <code>i2c_speed</code> parameter. All other Klipper micro-controllers use a 100000 rate and ignore the <code>i2c_speed</code> parameter.</p>
|
||||
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000 (<em>standard mode</em>, 100kbit/s). The Klipper "Linux" micro-controller supports a 400000 speed (<em>fast mode</em>, 400kbit/s), but it must be <a href="RPi_microcontroller.html#optional-enabling-i2c">set in the operating system</a> and the <code>i2c_speed</code> parameter is otherwise ignored. The Klipper "RP2040" micro-controller and ATmega AVR family and some STM32 (F0, G0, G4, L4, F7, H7) support a rate of 400000 via the <code>i2c_speed</code> parameter. All other Klipper micro-controllers use a 100000 rate and ignore the <code>i2c_speed</code> parameter.</p>
|
||||
<div class="highlight"><pre><span></span><code>#i2c_address:
|
||||
# The i2c address of the device. This must specified as a decimal
|
||||
# number (not in hex). The default depends on the type of device.
|
||||
|
|
|
|||
|
|
@ -1412,7 +1412,7 @@
|
|||
# 溫度感測器設定...
|
||||
</code></pre></div>
|
||||
|
||||
<p>更多關於設定 <code>temperature_probe</code> 相關細節請見<a href="https://www.klipper3d.org/zh-Hant/Config_Reference.html#_18">配置參考</a>。建議先行設定 <code>calibration_position</code>、<code>calibration_extruder_temp</code>、<code>extruder_heating_z</code>、<code>calibration_bed_temp</code> 部分，便能自動化下述一些步驟。若要校準的列印機是封閉式的，強烈建議將 <code>max_validation_temp</code> 設定在 100\~120 之間。</p>
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below. If the printer to be calibrated is enclosed, it is strongly recommended to set the <code>max_validation_temp</code> option to a value between 100 and 120.</p>
|
||||
<p>渦電流探針的製造商可能會提供預設的飄移補償，可以將它手動添加到 <code>[probe_eddy_current]</code> 部分中的 <code>drift_calibration</code> 設定。若是沒有、或預設補償效果不佳，可以輸入 <code>TEMPERATURE_PROBE_CALIBRATE</code> 指令以使用 <code>[temperature_probe]</code> 功能中的手動校準流程。</p>
|
||||
<p>在開始校準之前，使用者必須知道探針線圈可能達到的最高溫度，這個溫度會在 <code>TEMPERATURE_PROBE_CALIBRATE</code> 指令中作為 <code>TARGET</code> 。校準的目標是涵蓋最大的溫度範圍，因此應在列印機冷卻後開始；並在線圈達到最高溫度時結束。</p>
|
||||
<p>在 <code>[temperature_probe]</code> 設定完成後，按照下列步驟執行熱飄移校準：</p>
|
||||
|
|
|
|||
|
|
@ -1542,6 +1542,16 @@
|
|||
<td>2634K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>RP2350</td>
|
||||
<td>4167K</td>
|
||||
<td>2663K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SAME70</td>
|
||||
<td>6667K</td>
|
||||
<td>4737K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>STM32H743</td>
|
||||
<td>9091K</td>
|
||||
<td>6061K</td>
|
||||
|
|
|
|||
|
|
@ -869,6 +869,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1958,6 +1965,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3089,6 +3116,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4178,6 +4212,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4750,6 +4804,11 @@
|
|||
<p>The following commands are available when an <a href="Config_Reference.html#angle">angle config section</a> is enabled.</p>
|
||||
<h4 id="angle_calibrate">ANGLE_CALIBRATE<a class="headerlink" href="#angle_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CALIBRATE CHIP=<chip_name></code>: Perform angle calibration on the given sensor (there must be an <code>[angle chip_name]</code> config section that has specified a <code>stepper</code> parameter). IMPORTANT - this tool will command the stepper motor to move without checking the normal kinematic boundary limits. Ideally the motor should be disconnected from any printer carriage before performing calibration. If the stepper can not be disconnected from the printer, make sure the carriage is near the center of its rail before starting calibration. (The stepper motor may move forwards or backwards two full rotations during this test.) After completing this test use the <code>SAVE_CONFIG</code> command to save the calibration data to the config file. In order to use this tool the Python "numpy" package must be installed (see the <a href="Measuring_Resonances.html#software-installation">measuring resonance document</a> for more information).</p>
|
||||
<h4 id="angle_chip_calibrate">ANGLE_CHIP_CALIBRATE<a class="headerlink" href="#angle_chip_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CHIP_CALIBRATE CHIP=<chip_name></code>: Perform internal sensor calibration, if implemented (MT6826S/MT6835).</p>
|
||||
<ul>
|
||||
<li><strong>MT68XX</strong>: The motor should be disconnected from any printer carriage before performing calibration. After calibration, the sensor should be reset by disconnecting the power.</li>
|
||||
</ul>
|
||||
<h4 id="angle_debug_read">ANGLE_DEBUG_READ<a class="headerlink" href="#angle_debug_read" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_DEBUG_READ CHIP=<config_name> REG=<register></code>: Queries sensor register "register" (e.g. 44 or 0x2C). Can be useful for debugging purposes. This is only available for tle5012b chips.</p>
|
||||
<h4 id="angle_debug_write">ANGLE_DEBUG_WRITE<a class="headerlink" href="#angle_debug_write" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4758,7 +4817,12 @@
|
|||
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
|
||||
section</a> is enabled.</p>
|
||||
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=<value>]</code>: Initiates the X twist calibration wizard. <code>SAMPLE_COUNT</code> specifies the number of points along the X axis to calibrate at and defaults to 3.</p>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]</code></p>
|
||||
<p>Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.</p>
|
||||
<ul>
|
||||
<li><strong>AXIS:</strong> Define the axis (<code>X</code> or <code>Y</code>) for which the twist compensation will be calibrated. If not specified, the axis defaults to <code>'X'</code>.</li>
|
||||
<li><strong>AUTO:</strong> Enables automatic calibration mode. When <code>AUTO=True</code>, the calibration will run for both the X and Y axes. In this mode, <code>AXIS</code> cannot be specified. If both <code>AXIS</code> and <code>AUTO</code> are provided, an error will be raised.</li>
|
||||
</ul>
|
||||
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">¶</a></h3>
|
||||
<p>當啟用 <a href="Config_Reference.html#bed_mesh">bed_mesh config section</a> 時，以下命令可用（另請參閱 <a href="Bed_Mesh.html">bed mesh guide</a>）。</p>
|
||||
<h4 id="bed_mesh_calibrate">BED_MESH_CALIBRATE<a class="headerlink" href="#bed_mesh_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4862,6 +4926,7 @@ section</a> is enabled.</p>
|
|||
<p>當啟用 <a href="Config_Reference.html#fan_generic">fan_generic config section</a> 時，以下命令可用。</p>
|
||||
<h4 id="set_fan_speed">SET_FAN_SPEED<a class="headerlink" href="#set_fan_speed" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_FAN_SPEED FAN=config_name SPEED=<速度></code>該命令設定風扇的速度。"速度" 必須在0.0到1.0之間。</p>
|
||||
<p><code>SET_FAN_SPEED PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given fan. For example, if one defined a <code>[display_template my_fan_template]</code> config section then one could assign <code>TEMPLATE=my_fan_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the fan will be automatically set to the resulting speed. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_FAN_SPEED</code> commands to manage the values directly).</p>
|
||||
<h3 id="filament_switch_sensor">[filament_switch_sensor]<a class="headerlink" href="#filament_switch_sensor" title="Permanent link">¶</a></h3>
|
||||
<p>當啟用 <a href="Config_Reference.html#filament_switch_sensor">filament_switch_sensor</a> 或 <a href="Config_Reference.html#filament_motion_sensor">filament_motion_sensor</a> 配置部分時，以下命令可用。</p>
|
||||
<h4 id="query_filament_sensor">QUERY_FILAMENT_SENSOR<a class="headerlink" href="#query_filament_sensor" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4886,7 +4951,7 @@ section</a> is enabled.</p>
|
|||
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>FORCE_MOVE STEPPER=<config_name> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]</code> 。該命令將以給定的恒定速度（mm/s）強制移動給定的步進器，移動距離（mm）。如果指定了ACCEL並且大於零，那麼將使用給定的加速度（單位：mm/s^2）；否則不進行加速。不執行邊界檢查；不進行運動學更新；一個軸上的其他平行步進器將不會被移動。請謹慎使用，因為不正確的命令可能會導致損壞使用該命令幾乎肯定會使低階運動學處於不正確的狀態；隨後發出G28命令以重置運動學。該命令用於低階別的診斷和除錯。</p>
|
||||
<h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<值>] [Y=<值>] [Z=<值>]</code>：強制設定低階運動學程式碼使用的列印頭位置。這是一個診斷和除錯工具，常規的軸轉換應該使用 SET_GCODE_OFFSET 和/或 G92指令。如果沒有指定一個軸，則使用上一次命令的列印頭位置。設定一個不合理的數值可能會導致內部程式問題。這個命令可能會使邊界檢查失效，使用后發送 G28 來重置運動學。</p>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an axis is not specified then it will default to the position that the head was last commanded to. Setting an incorrect or invalid position may lead to internal software errors. Use the CLEAR parameter to forget the homing state for the given axes. Note that CLEAR will not override the previous functionality; if an axis is not specified to CLEAR it will have its kinematic position set as per above. This command may invalidate future boundary checks; issue a G28 afterwards to reset the kinematics.</p>
|
||||
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">¶</a></h3>
|
||||
<p>模組gcode module已自動載入.</p>
|
||||
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4980,6 +5045,7 @@ section</a> is enabled.</p>
|
|||
<p>當啟用 <a href="Config_Reference.html#output_pin">output_pin config section</a> 時，以下命令可用。</p>
|
||||
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value></code>: Set the pin to the given output <code>VALUE</code>. VALUE should be 0 or 1 for "digital" output pins. For PWM pins, set to a value between 0.0 and 1.0, or between 0.0 and <code>scale</code> if a scale is configured in the output_pin config section.</p>
|
||||
<p><code>SET_PIN PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given pin. For example, if one defined a <code>[display_template my_pin_template]</code> config section then one could assign <code>TEMPLATE=my_pin_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the pin will be automatically set to the resulting value. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_PIN</code> commands to manage the values directly).</p>
|
||||
<h3 id="palette2">[palette2]<a class="headerlink" href="#palette2" title="Permanent link">¶</a></h3>
|
||||
<p>啟用 <a href="Config_Reference.html#palette2">palette2 config section</a> 時，以下命令可用。</p>
|
||||
<p>Palette列印通過在GCode檔案中嵌入特殊的OCodes（Omega Codes）來工作:</p>
|
||||
|
|
@ -5037,6 +5103,10 @@ section</a> is enabled.</p>
|
|||
<p>The following command is available when a <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time config section</a> is enabled.</p>
|
||||
<h4 id="set_pin_1">SET_PIN<a class="headerlink" href="#set_pin_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value> [CYCLE_TIME=<cycle_time>]</code>: This command works similarly to <a href="#output_pin">output_pin</a> SET_PIN commands. The command here supports setting an explicit cycle time using the CYCLE_TIME parameter (specified in seconds). Note that the CYCLE_TIME parameter is not stored between SET_PIN commands (any SET_PIN command without an explicit CYCLE_TIME parameter will use the <code>cycle_time</code> specified in the pwm_cycle_time config section).</p>
|
||||
<h3 id="quad_gantry_level">[quad_gantry_level]<a class="headerlink" href="#quad_gantry_level" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#quad_gantry_level">quad_gantry_level config section</a> is enabled.</p>
|
||||
<h4 id="quad_gantry_level_1">QUAD_GANTRY_LEVEL<a class="headerlink" href="#quad_gantry_level_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>QUAD_GANTRY_LEVEL [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">¶</a></h3>
|
||||
<p>The query_adc module is automatically loaded.</p>
|
||||
<h4 id="query_adc_1">QUERY_ADC<a class="headerlink" href="#query_adc_1" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -5053,9 +5123,9 @@ section</a> is enabled.</p>
|
|||
<h4 id="measure_axes_noise">MEASURE_AXES_NOISE<a class="headerlink" href="#measure_axes_noise" title="Permanent link">¶</a></h4>
|
||||
<p><code>MEASURE_AXES_NOISE</code>：測量並輸出所有啟用的加速度計晶片的所有軸的噪聲。</p>
|
||||
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">¶</a></h4>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> OUTPUT=<resonances,raw_data> [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>adxl345_chip_name</code> can be one or more configured adxl345 chip,delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. Note that <code>adxl345</code> can be omitted from named adxl345 chips. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> [OUTPUT=<resonances,raw_data>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [POINT=x,y,z] [INPUT_SHAPING=<0:1>]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>chip_name</code> can be one or more configured accel chips, delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<h4 id="shaper_calibrate">SHAPER_CALIBRATE<a class="headerlink" href="#shaper_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [MAX_SMOOTHING=<max_smoothing>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>][HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [MAX_SMOOTHING=<max_smoothing>] [INPUT_SHAPING=<0:1>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">¶</a></h3>
|
||||
<p>當啟用 <a href="Config_Reference.html#respond">respond config section</a> 時，以下標準 G-Code 命令可用：</p>
|
||||
<ul>
|
||||
|
|
@ -5161,7 +5231,7 @@ section</a> is enabled.</p>
|
|||
<h3 id="z_tilt">[z_tilt]<a class="headerlink" href="#z_tilt" title="Permanent link">¶</a></h3>
|
||||
<p>當啟用 <a href="Config_Reference.html#z_tilt">z_tilt config section</a> 時，以下命令可用。</p>
|
||||
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">¶</a></h4>
|
||||
<p><code>Z_TILT_ADJUST [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>HORIZONTAL_MOVE_Z</code> value overrides the <code>horizontal_move_z</code> option specified in the config file.</p>
|
||||
<p><code>Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when a <a href="Config_Reference.html#temperature_probe">temperature_probe config section</a> is enabled.</p>
|
||||
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
|
|||
|
|
@ -912,8 +912,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#configure-lis2dw-series" class="md-nav__link">
|
||||
Configure LIS2DW series
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -990,6 +990,13 @@
|
|||
選擇 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 @@
|
|||
選擇 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="_1">共振值測量<a class="headerlink" href="#_1" 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="_2">安裝指南<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
|
|||
</code></pre></div>
|
||||
|
||||
<p>Next, in order to install NumPy in the Klipper environment, run the command:</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>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.</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="configure-adxl345-with-rpi">Configure ADXL345 With RPi<a class="headerlink" href="#configure-adxl345-with-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>通過執行<code>sudo raspi-config</code> 后的 "Interfacing options"菜單中啟用 SPI 以確保Linux SPI 驅動已啟用。</p>
|
||||
|
|
@ -2257,7 +2281,7 @@ pin: adxl:gpio23
|
|||
</code></pre></div>
|
||||
|
||||
<p>通過<code>RESTART</code>命令重啟Klipper。</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 # an example
|
|||
|
||||
<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>如果您正在重新校準整形器，並且建議的整形器配置報告的平滑度與您在之前校準期間得到的幾乎相同，則可以跳過此步驟。</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="_10">測試自定義軸<a class="headerlink" href="#_10" title="Permanent link">¶</a></h3>
|
||||
<p><code>TEST_RESONANCES</code> 命令支持自定義軸。雖然這對於輸入整形器校準並不是很有用，但它可用於深入研究打印機共振並檢查皮帶張力等。</p>
|
||||
<p>要檢查 CoreXY 打印機上的皮帶張力，請執行</p>
|
||||
|
|
|
|||
|
|
@ -1447,7 +1447,7 @@ git clone https://github.com/Klipper3d/klipper
|
|||
<h2 id="configuring-octoprint-to-use-klipper">Configuring OctoPrint to use Klipper<a class="headerlink" href="#configuring-octoprint-to-use-klipper" title="Permanent link">¶</a></h2>
|
||||
<p>The OctoPrint web server needs to be configured to communicate with the Klipper host software. Using a web browser, login to the OctoPrint web page and then configure the following items:</p>
|
||||
<p>Navigate to the Settings tab (the wrench icon at the top of the page). Under "Serial Connection" in "Additional serial ports" add:</p>
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.sock
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.serial
|
||||
</code></pre></div>
|
||||
|
||||
<p>Then click "Save".</p>
|
||||
|
|
|
|||
|
|
@ -1480,7 +1480,7 @@
|
|||
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" style="margin:25px"/></a></p>
|
||||
<p>BIGTREETECH 是 Klipper 的主板官方贊助商。 BIGTREETECH 致力於開發具有創新性和競爭力的產品，以更好地服務於 3D 打印社區。在 <a href="https://www.facebook.com/BIGTREETECH">Facebook</a> 或 <a href="https://twitter.com/BigTreeTech">Twitter</a> 上關注他們。</p>
|
||||
<h2 id="_2">贊助商<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a> <a href="https://peopoly.net"><img src="./img/sponsors/peopoly-logo.png" width="200" style="margin:25px" /></a></p>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a></p>
|
||||
<h2 id="klipper">Klipper開發人員<a class="headerlink" href="#klipper" title="Permanent link">¶</a></h2>
|
||||
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">¶</a></h3>
|
||||
<p>Kevin 是 Klipper 的原創作者及現任維護者。捐款支持請至：<a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> 或 <a href="https://www.patreon.com/koconnor">https://www.patreon.com/koconnor</a></p>
|
||||
|
|
|
|||
Binary file not shown.
File diff suppressed because one or more lines are too long
|
|
@ -2,277 +2,277 @@
|
|||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
|
|
@ -711,6 +711,33 @@
|
|||
薪酬使用概览
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="薪酬使用概览">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1384,6 +1411,33 @@
|
|||
薪酬使用概览
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="薪酬使用概览">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#basic-usage-x-axis-calibration" class="md-nav__link">
|
||||
Basic Usage: X-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#for-y-axis-calibration" class="md-nav__link">
|
||||
For Y-Axis Calibration
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#automatic-calibration-for-both-axes" class="md-nav__link">
|
||||
Automatic Calibration for Both Axes
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1420,19 +1474,43 @@ bias</a>. It may result in probe operations such as <a href="Bed_Mesh.html">Bed
|
|||
<blockquote>
|
||||
<p><strong>提示：</strong>请确保正确设置<a href="Config_Reference.html#Probe">Probe X和Y Offset</a>，因为它们对校准影响很大。</p>
|
||||
</blockquote>
|
||||
<h3 id="basic-usage-x-axis-calibration">Basic Usage: X-Axis Calibration<a class="headerlink" href="#basic-usage-x-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<ol>
|
||||
<li>设置好[AXIS_TWIST_COMPOMENT]模块后，执行<code>AXIS_TWIST_COMCOMPATION_CALIBRATE</code></li>
|
||||
<li>After setting up the <code>[axis_twist_compensation]</code> module, run:</li>
|
||||
</ol>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE
|
||||
</code></pre></div>
|
||||
|
||||
<p>This command will calibrate the X-axis by default. - The calibration wizard will prompt you to measure the probe Z offset at several points along the bed. - By default, the calibration uses 3 points, but you can specify a different number with the option: <code>SAMPLE_COUNT=<value></code></p>
|
||||
<ol>
|
||||
<li><strong>Adjust Your Z Offset:</strong> After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).</li>
|
||||
<li>
|
||||
<p><strong>Perform Bed Leveling Operations:</strong> Use probe-based operations as needed, such as:</p>
|
||||
<ul>
|
||||
<li>校准向导将提示您在床上的几个点上测量探头Z偏移量</li>
|
||||
<li>该校准默认为3分，但您可以使用选项<code>SAMPLE_COUNT=</code>来使用不同的数字。</li>
|
||||
<li><a href="G-Codes.html#screws_tilt_adjust">Screws Tilt Adjust</a></li>
|
||||
<li><a href="G-Codes.html#z_tilt_adjust">Z Tilt Adjust</a></li>
|
||||
</ul>
|
||||
<ol>
|
||||
<li><a href="Probe_Calibrate.html#calibrating-probe-z-offset">调整您的Z offset</a></li>
|
||||
<li>执行自动/探针式床铺操作，如<a href="G-Codes.html#螺旋倾斜调整">螺旋倾斜调整</a>、<a href="G-Codes.html#z_倾斜调整">Z倾斜调整</a>等</li>
|
||||
<li>原点所有轴，然后根据需要执行<a href="Bed_Mesh.html">Bed Mesh</a></li>
|
||||
<li>执行测试打印，然后根据需要执行任何<a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a></li>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>Finalize the Setup:</strong></p>
|
||||
<ul>
|
||||
<li>Home all axes, and perform a <a href="Bed_Mesh.html">Bed Mesh</a> if necessary.</li>
|
||||
<li>Run a test print, followed by any <a href="Axis_Twist_Compensation.html#fine-tuning">fine-tuning</a> if needed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ol>
|
||||
<h3 id="for-y-axis-calibration">For Y-Axis Calibration<a class="headerlink" href="#for-y-axis-calibration" title="Permanent link">¶</a></h3>
|
||||
<p>The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y
|
||||
</code></pre></div>
|
||||
|
||||
<p>This will guide you through the same measuring process as for the X-axis.</p>
|
||||
<h3 id="automatic-calibration-for-both-axes">Automatic Calibration for Both Axes<a class="headerlink" href="#automatic-calibration-for-both-axes" title="Permanent link">¶</a></h3>
|
||||
<p>To perform automatic calibration for both the X and Y axes without manual intervention, use:</p>
|
||||
<div class="highlight"><pre><span></span><code>AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
|
||||
</code></pre></div>
|
||||
|
||||
<p>In this mode, the calibration process will run for both axes automatically.</p>
|
||||
<blockquote>
|
||||
<p><strong>提示：</strong>床温、喷嘴温度和尺寸似乎对校准过程没有影响。</p>
|
||||
</blockquote>
|
||||
|
|
|
|||
|
|
@ -1968,7 +1968,7 @@ fade_target: 0
|
|||
<li><code>fade_target: 0</code> <em>默认值：网格的平均 Z 值</em> <code>fade_target</code> 可以被视为在淡化完成后应用于整个床面的额外 Z 偏移量。一般来说，我们希望这个值为 0，但有些情况下不应该是这样的。例如，假设您在床上的归位位置是一个异常值，比床面的平均探测高度低 0.2 毫米。如果 <code>fade_target</code> 为 0，淡化将会使整个床面平均降低 0.2 毫米。通过将 <code>fade_target</code> 设置为 0.2，淡化区域将会提高到 0.2 毫米，但是，床面的其余部分将保持原大小。通常最好将 <code>fade_target</code> 留在配置中，以便使用网格的平均高度，但是如果您想在床面的特定部分上打印，则可能需要手动调整淡化目标。</li>
|
||||
</ul>
|
||||
<h3 id="_9">配置零点参考位置<a class="headerlink" href="#_9" title="Permanent link">¶</a></h3>
|
||||
<p>许多探头容易出现“漂移”，即：由于热或干扰而引起的探头不准确。这使得计算探测器的z偏移量具有挑战性，特别是在不同床温的情况下。因此，一些打印机使用端止器来定位Z轴，并使用探头来校准网格。在这种配置中，可以对网格进行偏移，从而使(X，Y)<code>参考位置‘应用零点调整。‘参考位置’应该是床上进行[Z_ENDSTOP_CALIBRATE](./Manual_Level#calibrating-a-z-endstop)试纸测试的位置。Bed_Mesh模块提供了</code>ZERO_REFERENCE_Position`选项来指定该坐标：</p>
|
||||
<p>Many probes are susceptible to "drift", ie: inaccuracies in probing introduced by heat or interference. This can make calculating the probe's z-offset challenging, particularly at different bed temperatures. As such, some printers use an endstop for homing the Z axis and a probe for calibrating the mesh. In this configuration it is possible offset the mesh so that the (X, Y) <code>reference position</code> applies zero adjustment. The <code>reference postion</code> should be the location on the bed where a <a href="Manual_Level.html#calibrating-a-z-endstop">Z_ENDSTOP_CALIBRATE</a> paper test is performed. The bed_mesh module provides the <code>zero_reference_position</code> option for specifying this coordinate:</p>
|
||||
<div class="highlight"><pre><span></span><code>[bed_mesh]
|
||||
speed: 120
|
||||
horizontal_move_z: 5
|
||||
|
|
|
|||
|
|
@ -1195,6 +1195,13 @@
|
|||
SAMD51 步速率基准测试
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1205,8 +1212,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040" class="md-nav__link">
|
||||
RP2040 步速率基准测试
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1613,6 +1620,13 @@
|
|||
SAMD51 步速率基准测试
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#same70-step-rate-benchmark" class="md-nav__link">
|
||||
SAME70 step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1623,8 +1637,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040" class="md-nav__link">
|
||||
RP2040 步速率基准测试
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -2122,6 +2136,34 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="same70-step-rate-benchmark">SAME70 step rate benchmark<a class="headerlink" href="#same70-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the SAME70:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=PC18 dir_pin=PB5 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=PC16 dir_pin=PD10 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=2 step_pin=PC28 dir_pin=PA4 invert_step=-1 step_pulse_ticks=0
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>34e9ea55</code> with gcc version <code>arm-none-eabi-gcc (NixOS 10.3-2021.10) 10.3.1</code> on a SAME70Q20B micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>same70</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1个步进电机</td>
|
||||
<td>45</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3个步进电机</td>
|
||||
<td>190</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="ar100">AR100 步进率基准测试<a class="headerlink" href="#ar100" title="Permanent link">¶</a></h3>
|
||||
<p>以下配置顺序被用于AR100 CPU（全志A64）：</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2131,7 +2173,7 @@ config_stepper oid=2 step_pin=PL12 dir_pin=PE16 invert_step=-1 step_pulse_ticks=
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>该测试最后一次运行在提交<code>08d037c6</code> ，gcc版本<code>or1k-linux-musl-gcc（GCC）9.2.0</code> ，全志A64-H微控制器上进行。</p>
|
||||
<p>The test was last run on commit <code>b7978d37</code> with gcc version <code>or1k-linux-musl-gcc (GCC) 9.2.0</code> on an Allwinner A64-H micro-controller.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
|
|
@ -2150,8 +2192,8 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="rp2040">RP2040 步速率基准测试<a class="headerlink" href="#rp2040" title="Permanent link">¶</a></h3>
|
||||
<p>RP2040 上使用以下配置序列：</p>
|
||||
<h3 id="rpxxxx-step-rate-benchmark">RPxxxx step rate benchmark<a class="headerlink" href="#rpxxxx-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040 and RP2350:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=gpio25 dir_pin=gpio3 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=gpio26 dir_pin=gpio4 invert_step=-1 step_pulse_ticks=0
|
||||
|
|
@ -2159,11 +2201,11 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
|
|||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>该测试最后一次在 Raspberry Pi Pico 板上使用 gcc 版本 <code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code>和提交 <code>59314d99</code> 运行。</p>
|
||||
<p>The test was last run on commit <code>f6718291</code> with gcc version <code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi Pico and Pico 2 boards.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2040</th>
|
||||
<th>rp2040 (*)</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
|
|
@ -2178,6 +2220,25 @@ finalize_config crc=0
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2350</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1个步进电机</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3个步进电机</td>
|
||||
<td>169</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 125Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM core cycles.</p>
|
||||
<h3 id="linux-mcu">Linux MCU 步速率基准测试<a class="headerlink" href="#linux-mcu" title="Permanent link">¶</a></h3>
|
||||
<p>树莓派上使用以下配置序列：</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
|
|
@ -2311,9 +2372,15 @@ get_uptime
|
|||
</tr>
|
||||
<tr>
|
||||
<td>rp2040 (USB)</td>
|
||||
<td>873K</td>
|
||||
<td>c5667193</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2350 (USB)</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
|
|||
|
|
@ -1580,7 +1580,7 @@
|
|||
<li>参考位于klippy/kinematics/目录已有的运动学类。动力学类旨在将一个笛卡尔坐标系中的运动转化为各个步进电机的运动。建议复制已有的代码，并在其基础上进行修改。</li>
|
||||
<li>若需要的运动学方程未被Klipper涵盖，则应使用C语言实现新动力学体系中各个步进电机的位置方程（见klippy/chelper/，如kin_cart.c, kin_corexy.c, and kin_delta.c）。位置方程中应调用<code>move_get_coord()</code>以将运动的时间点（单位 ：秒）转化为对应的笛卡尔坐标位置（单位：毫米），进而计算目标步进电机运动目标位置（单位：毫米）。</li>
|
||||
<li>在新的运动学类中实现<code>calc_position</code>方法。该方法将通过各个步进电机的位置计算笛卡尔坐标系下的打印头位置；同时该方法通常只在回零和z探测时使用，因此无需过分追求效率。</li>
|
||||
<li>之后实现<code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>set_position()</code>方法。这些函数用于特定的运动学检查。在开发的初期，可以直接使用已有代码。</li>
|
||||
<li>Other methods. Implement the <code>check_move()</code>, <code>get_status()</code>, <code>get_steppers()</code>, <code>home()</code>, <code>clear_homing_state()</code>, and <code>set_position()</code> methods. These functions are typically used to provide kinematic specific checks. However, at the start of development one can use boiler-plate code here.</li>
|
||||
<li>添加测试实例。创建一个G代码文件，其中包含一系列的运动命令用于测试新增的运动学模型。 按照<a href="Debugging.html">调试文档</a>将该G代码文件转换为微控制器命令。在遭遇困难状况和检查数据传递相当有用。</li>
|
||||
</ol>
|
||||
<h2 id="_8">移植到新的微控制器<a class="headerlink" href="#_8" title="Permanent link">¶</a></h2>
|
||||
|
|
|
|||
|
|
@ -1396,6 +1396,11 @@
|
|||
<p>本文档涵盖了软件更新中对配置文件不向后兼容的部分。在升级 Klipper 时，最好也查看一下这份文档。</p>
|
||||
<p>文档的所有日期都是大概时间。</p>
|
||||
<h2 id="_2">变更<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
<p>20241203: The resonance test has been changed to include slow sweeping moves. This change requires that testing point(s) have some clearance in X/Y plane (+/- 30 mm from the test point should suffice when using the default settings). The new test should generally produce more accurate and reliable test results. However, if required, the previous test behavior can be restored by adding options <code>sweeping_period: 0</code> and <code>accel_per_hz: 75</code> to the <code>[resonance_tester]</code> config section.</p>
|
||||
<p>20241201: In some cases Klipper may have ignored leading characters or spaces in a traditional G-Code command. For example, "99M123" may have been interpreted as "M123" and "M 321" may have been interpreted as "M321". Klipper will now report these cases with an "Unknown command" warning.</p>
|
||||
<p>20241112: Option <code>CHIPS=<chip_name></code> in <code>TEST_RESONANCES</code> and <code>SHAPER_CALIBRATE</code> requires specifying the full name(s) of the accel chip(s). For example, <code>adxl345 rpi</code> instead of short name - <code>rpi</code>.</p>
|
||||
<p>20240912: <code>SET_PIN</code>, <code>SET_SERVO</code>, <code>SET_FAN_SPEED</code>, <code>M106</code>, and <code>M107</code> commands are now collated. Previously, if many updates to the same object were issued faster than the minimum scheduling time (typically 100ms) then actual updates could be queued far into the future. Now if many updates are issued in rapid succession then it is possible that only the latest request will be applied. If the previous behavior is requried then consider adding explicit <code>G4</code> delay commands between updates.</p>
|
||||
<p>20240912: Support for <code>maximum_mcu_duration</code> and <code>static_value</code> parameters in <code>[output_pin]</code> config sections have been removed. These options have been deprecated since 20240123.</p>
|
||||
<p>20240415: The <code>on_error_gcode</code> parameter in the <code>[virtual_sdcard]</code> config section now has a default. If this parameter is not specified it now defaults to <code>TURN_OFF_HEATERS</code>. If the previous behavior is desired (take no default action on an error during a virtual_sdcard print) then define <code>on_error_gcode</code> with an empty value.</p>
|
||||
<p>20240313: The <code>max_accel_to_decel</code> parameter in the <code>[printer]</code> config section has been deprecated. The <code>ACCEL_TO_DECEL</code> parameter of the <code>SET_VELOCITY_LIMIT</code> command has been deprecated. The <code>printer.toolhead.max_accel_to_decel</code> status has been removed. Use the <a href="Config_Reference.html#printer">minimum_cruise_ratio parameter</a> instead. The deprecated features will be removed in the near future, and using them in the interim may result in subtly different behavior.</p>
|
||||
<p>20240215: Several deprecated features have been removed. Using "NTC 100K beta 3950" as a thermistor name has been removed (deprecated on 20211110). The <code>SYNC_STEPPER_TO_EXTRUDER</code> and <code>SET_EXTRUDER_STEP_DISTANCE</code> commands have been removed, and the extruder <code>shared_heater</code> config option has been removed (deprecated on 20220210). The bed_mesh <code>relative_reference_index</code> option has been removed (deprecated on 20230619).</p>
|
||||
|
|
|
|||
|
|
@ -938,6 +938,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1537,6 +1544,13 @@
|
|||
hd44780_spi显示器
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1670,8 +1684,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -3032,6 +3046,13 @@
|
|||
[lis2dw]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis3dh" class="md-nav__link">
|
||||
[lis3dh]
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3631,6 +3652,13 @@
|
|||
hd44780_spi显示器
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#aip31068_spi-display" class="md-nav__link">
|
||||
aip31068_spi display
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3764,8 +3792,8 @@
|
|||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#xh711" class="md-nav__link">
|
||||
XH711
|
||||
<a href="#hx711" class="md-nav__link">
|
||||
HX711
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -5173,8 +5201,9 @@ cs_pin:
|
|||
<h3 id="lis2dw">[lis2dw]<a class="headerlink" href="#lis2dw" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS2DW accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis2dw]
|
||||
cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
|
|
@ -5184,6 +5213,43 @@ cs_pin:
|
|||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
||||
<h3 id="lis3dh">[lis3dh]<a class="headerlink" href="#lis3dh" title="Permanent link">¶</a></h3>
|
||||
<p>Support for LIS3DH accelerometers.</p>
|
||||
<div class="highlight"><pre><span></span><code>[lis3dh]
|
||||
#cs_pin:
|
||||
# The SPI enable pin for the sensor. This parameter must be provided
|
||||
# if using SPI.
|
||||
#spi_speed: 5000000
|
||||
# The SPI speed (in hz) to use when communicating with the chip.
|
||||
# The default is 5000000.
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
#i2c_address:
|
||||
# Default is 25 (0x19). If SA0 is high, it would be 24 (0x18) instead.
|
||||
#i2c_mcu:
|
||||
#i2c_bus:
|
||||
#i2c_software_scl_pin:
|
||||
#i2c_software_sda_pin:
|
||||
#i2c_speed: 400000
|
||||
# See the "common I2C settings" section for a description of the
|
||||
# above parameters. The default "i2c_speed" is 400000.
|
||||
#axes_map: x, y, z
|
||||
# See the "adxl345" section for information on this parameter.
|
||||
</code></pre></div>
|
||||
|
|
@ -5208,38 +5274,58 @@ cs_pin:
|
|||
<p>支持共振测试和自动输入整形器校准。为了使用该模块的大多数功能，必须安装额外的软件依赖项；参考<a href="Measuring_Resonances.html">测量共振</a>和<a href="G-Codes.html#resonance_tester">命令参考</a>以获取更多信息。有关 <code>max_smoothing</code> 参数及其用途的更多信息，请查阅测量共振指南的 <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> 章节。</p>
|
||||
<div class="highlight"><pre><span></span><code>[resonance_tester]
|
||||
#probe_points:
|
||||
# 共振测试点的列表（每行一个X,Y,Z坐标点），至少指定一个点。请确保
|
||||
# 所有点在XY平面上都有足够容许打印头移动头移动的安全余量（约几厘米）。
|
||||
# A list of X, Y, Z coordinates of points (one point per line) to test
|
||||
# resonances at. At least one point is required. Make sure that all
|
||||
# points with some safety margin in XY plane (~a few centimeters)
|
||||
# are reachable by the toolhead.
|
||||
#accel_chip:
|
||||
# 一个用于测量的加速度计芯片的名称。如果adxl345芯片定义时没有明确指定
|
||||
# 名称，这个参数可以直接引用 "accel_chip: adxl345"，否则必须提供一个明确
|
||||
# 的名称，例如 "accel_chip: adxl345 my_chip_name"。
|
||||
# 必须被提供这个参数或下面的两个参数。
|
||||
# A name of the accelerometer chip to use for measurements. If
|
||||
# adxl345 chip was defined without an explicit name, this parameter
|
||||
# can simply reference it as "accel_chip: adxl345", otherwise an
|
||||
# explicit name must be supplied as well, e.g. "accel_chip: adxl345
|
||||
# my_chip_name". Either this, or the next two parameters must be
|
||||
# set.
|
||||
#accel_chip_x:
|
||||
#accel_chip_y:
|
||||
# 用于测量每个轴的加速计芯片的名称。在平移热床的打印机上可能很有用，
|
||||
# 如果两个单独的加速度计分别被安装在打印床（用于Y轴）和工具头（X轴）上。
|
||||
# 这些参数的格式与 “accel_chip” 参数相同。
|
||||
# 必须提供“accel_chip”或这两个参数。
|
||||
# Names of the accelerometer chips to use for measurements for each
|
||||
# of the axis. Can be useful, for instance, on bed slinger printer,
|
||||
# if two separate accelerometers are mounted on the bed (for Y axis)
|
||||
# and on the toolhead (for X axis). These parameters have the same
|
||||
# format as 'accel_chip' parameter. Only 'accel_chip' or these two
|
||||
# parameters must be provided.
|
||||
#max_smoothing:
|
||||
# 在自动校准整形(使用'SHAPER_CALIBRATE' 命令)的过程中允许每个轴的最大输
|
||||
# 入整形器平滑度。
|
||||
# 默认不指定最大的平滑度。
|
||||
# 请参考共振校准指南以了解有关使用此功能的更多细节。
|
||||
# Maximum input shaper smoothing to allow for each axis during shaper
|
||||
# auto-calibration (with 'SHAPER_CALIBRATE' command). By default no
|
||||
# maximum smoothing is specified. Refer to Measuring_Resonances guide
|
||||
# for more details on using this feature.
|
||||
#move_speed: 50
|
||||
# The speed (in mm/s) to move the toolhead to and between test points
|
||||
# during the calibration. The default is 50.
|
||||
#min_freq: 5
|
||||
# 测试谐振的最小频率。默认为5Hz。
|
||||
# Minimum frequency to test for resonances. The default is 5 Hz.
|
||||
#max_freq: 133.33
|
||||
# 测试谐振的最大频率。默认为133.33 Hz。
|
||||
#accel_per_hz: 75
|
||||
# 这个参数用于决定测试一个特定的频率的加速度： accel = accel_per_hz * freq。
|
||||
# 数值越大加速度越高，振荡的能量就越大。如果打印机上的共振太强，可以
|
||||
# 设置为比默认值更低的值。然而，较低的值会使高频共振的测量不那么精确。
|
||||
# 默认为75mm/s。
|
||||
# Maximum frequency to test for resonances. The default is 133.33 Hz.
|
||||
#accel_per_hz: 60
|
||||
# This parameter is used to determine which acceleration to use to
|
||||
# test a specific frequency: accel = accel_per_hz * freq. Higher the
|
||||
# value, the higher is the energy of the oscillations. Can be set to
|
||||
# a lower than the default value if the resonances get too strong on
|
||||
# the printer. However, lower values make measurements of
|
||||
# high-frequency resonances less precise. The default value is 75
|
||||
# (mm/sec).
|
||||
#hz_per_sec: 1
|
||||
# 决定测试的速度。当测试所有频率在范围[min_freq, max_freq]内时，每秒钟
|
||||
# 频率都会增加 hz_per_sec。更小的数值会使测试变慢，更大的数值会降低测
|
||||
# 试的精度。
|
||||
# 默认值是1.0（Hz/sec == sec^-2）。
|
||||
# Determines the speed of the test. When testing all frequencies in
|
||||
# range [min_freq, max_freq], each second the frequency increases by
|
||||
# hz_per_sec. Small values make the test slow, and the large values
|
||||
# will decrease the precision of the test. The default value is 1.0
|
||||
# (Hz/sec == sec^-2).
|
||||
#sweeping_accel: 400
|
||||
# An acceleration of slow sweeping moves. The default is 400 mm/sec^2.
|
||||
#sweeping_period: 1.2
|
||||
# A period of slow sweeping moves. Setting this parameter to 0
|
||||
# disables slow sweeping moves. Avoid setting it to a too small
|
||||
# non-zero value in order to not poison the measurements.
|
||||
# The default is 1.2 sec which is a good all-round choice.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_14">配置文件助手<a class="headerlink" href="#_14" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5456,7 +5542,7 @@ sensor_type: ldc1612
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="axis_twist_compensation">[axis_twist_compensation]<a class="headerlink" href="#axis_twist_compensation" title="Permanent link">¶</a></h3>
|
||||
<p>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>
|
||||
<p>A tool to compensate for inaccurate probe readings due to twist in X or Y gantry. See the <a href="Axis_Twist_Compensation.html">Axis Twist Compensation Guide</a> for more detailed information regarding symptoms, configuration and setup.</p>
|
||||
<div class="highlight"><pre><span></span><code>[axis_twist_compensation]
|
||||
#speed: 50
|
||||
# The speed (in mm/s) of non-probing moves during the calibration.
|
||||
|
|
@ -5467,16 +5553,33 @@ sensor_type: ldc1612
|
|||
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.
|
||||
# calibration position.
|
||||
calibrate_end_x: 200
|
||||
# Defines the maximum X coordinate of the calibration
|
||||
# This should be the X coordinate that positions the nozzle at the ending
|
||||
# calibration position. This parameter must be provided.
|
||||
# calibration position.
|
||||
calibrate_y: 112.5
|
||||
# Defines the Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle during the
|
||||
# calibration process. This parameter must be provided and is recommended to
|
||||
# calibration process. This parameter is recommended to
|
||||
# be near the center of the bed
|
||||
|
||||
# For Y-axis twist compensation, specify the following parameters:
|
||||
calibrate_start_y: ...
|
||||
# Defines the minimum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the starting
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_end_y: ...
|
||||
# Defines the maximum Y coordinate of the calibration
|
||||
# This should be the Y coordinate that positions the nozzle at the ending
|
||||
# calibration position for the Y axis. This parameter must be provided if
|
||||
# compensating for Y axis twist.
|
||||
calibrate_x: ...
|
||||
# Defines the X coordinate of the calibration for Y axis twist compensation
|
||||
# This should be the X coordinate that positions the nozzle during the
|
||||
# calibration process for Y axis twist compensation. This parameter must be
|
||||
# provided and is recommended to be near the center of the bed.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_16">额外的步进电机和挤出机<a class="headerlink" href="#_16" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -5742,6 +5845,10 @@ extruder:
|
|||
# "calibration_extruder_temp" option is set. Its recommended to heat
|
||||
# the extruder some distance from the bed to minimize its impact on
|
||||
# the probe coil temperature. The default is 50.
|
||||
#max_validation_temp: 60.
|
||||
# The maximum temperature used to validate the calibration. It is
|
||||
# recommended to set this to a value between 100 and 120 for enclosed
|
||||
# printers. The default is 60.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_18">温度传感器<a class="headerlink" href="#_18" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -6817,6 +6924,7 @@ run_current:
|
|||
#driver_SEIMIN: 0
|
||||
#driver_SFILT: 0
|
||||
#driver_SG4_ANGLE_OFFSET: 1
|
||||
#driver_SLOPE_CONTROL: 0
|
||||
# Set the given register during the configuration of the TMC2240
|
||||
# chip. This may be used to set custom motor parameters. The
|
||||
# defaults for each parameter are next to the parameter name in the
|
||||
|
|
@ -7084,72 +7192,82 @@ wiper:
|
|||
<p>支持一个连接到微控制器的屏幕</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type:
|
||||
# 使用的 LCD 芯片类型。这可以是“hd44780”、“hd44780_spi”、
|
||||
# “st7920”、“emulated_st7920”、“uc1701”、“ssd1306”、或“sh1106”。
|
||||
# 有关不同的LCD芯片类型和它们特有的参数，请查看下面的显示屏分段。
|
||||
# 必须提供此参数。
|
||||
# The type of LCD chip in use. This may be "hd44780", "hd44780_spi",
|
||||
# "aip31068_spi", "st7920", "emulated_st7920", "uc1701", "ssd1306", or
|
||||
# "sh1106".
|
||||
# See the display sections below for information on each type and
|
||||
# additional parameters they provide. This parameter must be
|
||||
# provided.
|
||||
#display_group:
|
||||
# 显示在这个显示屏上的 display_data 组。它决定了这个屏幕显示
|
||||
# 的内容（详见“display_data”分段）。
|
||||
# hd44780 默认使用 _default_20x4，其他显示屏则默认使用 _default_16x4。
|
||||
# The name of the display_data group to show on the display. This
|
||||
# controls the content of the screen (see the "display_data" section
|
||||
# for more information). The default is _default_20x4 for hd44780 or
|
||||
# aip31068_spi displays and _default_16x4 for other displays.
|
||||
#menu_timeout:
|
||||
# 菜单超时时间。在不活跃给定时间后将会退出菜单或在 autorun 启用时
|
||||
# 回到根菜单。
|
||||
# 默认为 0 秒（禁用）。
|
||||
# Timeout for menu. Being inactive this amount of seconds will
|
||||
# trigger menu exit or return to root menu when having autorun
|
||||
# enabled. The default is 0 seconds (disabled)
|
||||
#menu_root:
|
||||
# 在主屏幕按下编码器时显示的主菜单段名称。
|
||||
# 默认为 __main，这会显示在 klippy/extras/display/menu.cfg中定义的主菜单。
|
||||
# Name of the main menu section to show when clicking the encoder
|
||||
# on the home screen. The defaults is __main, and this shows the
|
||||
# the default menus as defined in klippy/extras/display/menu.cfg
|
||||
#menu_reverse_navigation:
|
||||
# 启用时反转上滚动和下滚动。
|
||||
# 默认为False。这是一个可选参数。
|
||||
# When enabled it will reverse up and down directions for list
|
||||
# navigation. The default is False. This parameter is optional.
|
||||
#encoder_pins:
|
||||
# 连接到编码器的引脚。使用编码器时必须提供两个引脚。
|
||||
# 使用菜单时必须提供此参数。
|
||||
# The pins connected to encoder. 2 pins must be provided when using
|
||||
# encoder. This parameter must be provided when using menu.
|
||||
#encoder_steps_per_detent:
|
||||
# 编码器在每一个凹陷处（"click"）发出多少步。如果编码器需要转过两个凹
|
||||
# 陷才能在条目之间移动，或者转过一个凹痕会在两个词条之间移动/跳过
|
||||
# 一个词条，可以尝试改变这个值。
|
||||
# 允许的值是2 （半步）或 4（全步）。
|
||||
# 默认为 4。
|
||||
# How many steps the encoder emits per detent ("click"). If the
|
||||
# encoder takes two detents to move between entries or moves two
|
||||
# entries from one detent, try changing this. Allowed values are 2
|
||||
# (half-stepping) or 4 (full-stepping). The default is 4.
|
||||
#click_pin:
|
||||
# 连接到 "enter" 按钮或编码器按压的引脚。
|
||||
# 使用菜单时必须提供此参数。
|
||||
# 如果定义了 “analog_range_click_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'enter' button or encoder 'click'. This
|
||||
# parameter must be provided when using menu. The presence of an
|
||||
# 'analog_range_click_pin' config parameter turns this parameter
|
||||
# from digital to analog.
|
||||
#back_pin:
|
||||
# 连接到“back”按钮的引脚。这是一个可选参数，菜单不需要这个按钮。
|
||||
# 如果定义了 “analog_range_back_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'back' button. This parameter is optional,
|
||||
# menu can be used without it. The presence of an
|
||||
# 'analog_range_back_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#up_pin:
|
||||
# 连接到“up”按钮的引脚。在不使用编码器时使用菜单必须提供这个参数。
|
||||
# 如果定义了 “analog_range_up_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'up' button. This parameter must be provided
|
||||
# when using menu without encoder. The presence of an
|
||||
# 'analog_range_up_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#down_pin:
|
||||
# 连接到“down”按钮的引脚。 在不使用编码器时使用菜单必须提供这个参数。
|
||||
# 如果定义了 “analog_range_down_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'down' button. This parameter must be
|
||||
# provided when using menu without encoder. The presence of an
|
||||
# 'analog_range_down_pin' config parameter turns this parameter from
|
||||
# digital to analog.
|
||||
#kill_pin:
|
||||
# 连接到“kill”按钮的引脚。 这个按钮将会触发紧急停止。
|
||||
# 如果定义了 “analog_range_kill_pin”配置参数，则这个参数的引脚需要
|
||||
# 是模拟引脚。
|
||||
# The pin connected to 'kill' button. This button will call
|
||||
# emergency stop. The presence of an 'analog_range_kill_pin' config
|
||||
# parameter turns this parameter from digital to analog.
|
||||
#analog_pullup_resistor: 4700
|
||||
# 连接到模拟按钮的拉高电阻阻值(ohms)
|
||||
# 默认为 4700 ohms。
|
||||
# The resistance (in ohms) of the pullup attached to the analog
|
||||
# button. The default is 4700 ohms.
|
||||
#analog_range_click_pin:
|
||||
# 'enter'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'enter' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_back_pin:
|
||||
# 'back'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'back' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_up_pin:
|
||||
# 'up'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'up' button. Range minimum and maximum
|
||||
# comma-separated values must be provided when using analog button.
|
||||
#analog_range_down_pin:
|
||||
# 'down'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'down' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
#analog_range_kill_pin:
|
||||
# 'kill'按钮的阻值范围。
|
||||
# 在使用模拟按钮时必须提供由逗号分隔最小和最大值。
|
||||
# The resistance range for a 'kill' button. Range minimum and
|
||||
# maximum comma-separated values must be provided when using analog
|
||||
# button.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="hd44780">hd44780显示器<a class="headerlink" href="#hd44780" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -7200,6 +7318,26 @@ spi_software_miso_pin:
|
|||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="aip31068_spi-display">aip31068_spi display<a class="headerlink" href="#aip31068_spi-display" title="Permanent link">¶</a></h4>
|
||||
<p>Information on configuring an aip31068_spi display - a very similar to hd44780_spi a 20x04 (20 symbols by 4 lines) display with slightly different internal protocol.</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
lcd_type: aip31068_spi
|
||||
latch_pin:
|
||||
spi_software_sclk_pin:
|
||||
spi_software_mosi_pin:
|
||||
spi_software_miso_pin:
|
||||
# The pins connected to the shift register controlling the display.
|
||||
# The spi_software_miso_pin needs to be set to an unused pin of the
|
||||
# printer mainboard as the shift register does not have a MISO pin,
|
||||
# but the software spi implementation requires this pin to be
|
||||
# configured.
|
||||
#line_length:
|
||||
# Set the number of characters per line for an hd44780 type lcd.
|
||||
# Possible values are 20 (default) and 16. The number of lines is
|
||||
# fixed to 4.
|
||||
...
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="st7920">st7920屏幕<a class="headerlink" href="#st7920" title="Permanent link">¶</a></h4>
|
||||
<p>有关配置 st7920 类显示屏的信息（可用于 "RepRapDiscount 12864 Full Graphic Smart Controller" 类型的显示器）。</p>
|
||||
<div class="highlight"><pre><span></span><code>[display]
|
||||
|
|
@ -7543,7 +7681,7 @@ sensor_type:
|
|||
# This must be one of the supported sensor types, see below.
|
||||
</code></pre></div>
|
||||
|
||||
<h4 id="xh711">XH711<a class="headerlink" href="#xh711" title="Permanent link">¶</a></h4>
|
||||
<h4 id="hx711">HX711<a class="headerlink" href="#hx711" title="Permanent link">¶</a></h4>
|
||||
<p>This is a 24 bit low sample rate chip using "bit-bang" communications. It is suitable for filament scales.</p>
|
||||
<div class="highlight"><pre><span></span><code>[load_cell]
|
||||
sensor_type: hx711
|
||||
|
|
@ -7606,13 +7744,30 @@ data_ready_pin:
|
|||
#gain: 128
|
||||
# Valid gain values are 128, 64, 32, 16, 8, 4, 2, 1
|
||||
# The default is 128
|
||||
#pga_bypass: False
|
||||
# Disable the internal Programmable Gain Amplifier. If
|
||||
# True the PGA will be disabled for gains 1, 2, and 4. The PGA is always
|
||||
# enabled for gain settings 8 to 128, regardless of the pga_bypass setting.
|
||||
# If AVSS is used as an input pga_bypass is forced to True.
|
||||
# The default is False.
|
||||
#sample_rate: 660
|
||||
# This chip supports two ranges of sample rates, Normal and Turbo. In turbo
|
||||
# mode the chips c internal clock runs twice as fast and the SPI communication
|
||||
# mode the chip's internal clock runs twice as fast and the SPI communication
|
||||
# speed is also doubled.
|
||||
# Normal sample rates: 20, 45, 90, 175, 330, 600, 1000
|
||||
# Turbo sample rates: 40, 90, 180, 350, 660, 1200, 2000
|
||||
# The default is 660
|
||||
#input_mux:
|
||||
# Input multiplexer configuration, select a pair of pins to use. The first pin
|
||||
# is the positive, AINP, and the second pin is the negative, AINN. Valid
|
||||
# values are: 'AIN0_AIN1', 'AIN0_AIN2', 'AIN0_AIN3', 'AIN1_AIN2', 'AIN1_AIN3',
|
||||
# 'AIN2_AIN3', 'AIN1_AIN0', 'AIN3_AIN2', 'AIN0_AVSS', 'AIN1_AVSS', 'AIN2_AVSS'
|
||||
# and 'AIN3_AVSS'. If AVSS is used the PGA is bypassed and the pga_bypass
|
||||
# setting will be forced to True.
|
||||
# The default is AIN0_AIN1.
|
||||
#vref:
|
||||
# The selected voltage reference. Valid values are: 'internal', 'REF0', 'REF1'
|
||||
# and 'analog_supply'. Default is 'internal'.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_28">控制板特定硬件支持<a class="headerlink" href="#_28" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -7750,28 +7905,30 @@ serial:
|
|||
</code></pre></div>
|
||||
|
||||
<h3 id="angle">[angle]<a class="headerlink" href="#angle" title="Permanent link">¶</a></h3>
|
||||
<p>支持使用a1333、as5047d或tle5012b SPI芯片的磁性霍尔角度传感器测量并读取步进电机的角度。测量结果可以通过<a href="API_Server.html">API服务器</a>和<a href="Debugging.html#motion-analysis-and-data-logging">运动分析工具</a>获取。可用的命令请见<a href="G-Codes.html#angle">G代码参考</a>。</p>
|
||||
<p>Magnetic hall angle sensor support for reading stepper motor angle shaft measurements using a1333, as5047d, mt6816, mt6826s, or tle5012b SPI chips. The measurements are available via the <a href="API_Server.html">API Server</a> and <a href="Debugging.html#motion-analysis-and-data-logging">motion analysis tool</a>. See the <a href="G-Codes.html#angle">G-Code reference</a> for available commands.</p>
|
||||
<div class="highlight"><pre><span></span><code>[angle my_angle_sensor]
|
||||
sensor_type:
|
||||
# 磁性霍尔传感器芯片的类型。
|
||||
# 可用的选择是 "a1333" "as5047d "和 "tle5012b"。
|
||||
# 这个参数必须被指定。
|
||||
# The type of the magnetic hall sensor chip. Available choices are
|
||||
# "a1333", "as5047d", "mt6816", "mt6826s", and "tle5012b". This parameter must be
|
||||
# specified.
|
||||
#sample_period: 0.000400
|
||||
# 测量时使用的查询周期（以秒为单位）。
|
||||
# 默认值是 0.000400 （每秒钟2500个样本）
|
||||
# The query period (in seconds) to use during measurements. The
|
||||
# default is 0.000400 (which is 2500 samples per second).
|
||||
#stepper:
|
||||
# 角度传感器连接的步进电机名称（例如，"stepper_x"）。
|
||||
# 设置这个值可以启用一个角度校准工具
|
||||
# 要使用这个功能需要安装Python "numpy "包。
|
||||
# 默认是不启用角度传感器的角度校准。
|
||||
# The name of the stepper that the angle sensor is attached to (eg,
|
||||
# "stepper_x"). Setting this value enables an angle calibration
|
||||
# tool. To use this feature, the Python "numpy" package must be
|
||||
# installed. The default is to not enable angle calibration for the
|
||||
# angle sensor.
|
||||
cs_pin:
|
||||
# 传感器的SPI引脚。必须提供此参数。
|
||||
# The SPI enable pin for the sensor. This parameter must be provided.
|
||||
#spi_speed:
|
||||
#spi_bus:
|
||||
#spi_software_sclk_pin:
|
||||
#spi_software_mosi_pin:
|
||||
#spi_software_miso_pin:
|
||||
# 有关上述参数的描述，参考 "common SPI settings "
|
||||
# See the "common SPI settings" section for a description of the
|
||||
# above parameters.
|
||||
</code></pre></div>
|
||||
|
||||
<h2 id="_30">常见的总线参数<a class="headerlink" href="#_30" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -7794,7 +7951,7 @@ cs_pin:
|
|||
<h3 id="i2c">常见的I2C设置<a class="headerlink" href="#i2c" title="Permanent link">¶</a></h3>
|
||||
<p>以下参数一般适用于使用I2C总线的设备。</p>
|
||||
<p>请注意，Klipper当前的微控制器对I2C的支持通常不能容忍线路噪声。I2C线路上的意外错误可能会导致Klipper产生运行时错误。Klipper 对错误恢复的支持在每种微控制器类型之间有所不同。通常建议只使用与微控制器位于同一印刷电路板上的I2C设备。</p>
|
||||
<p>大多数Klipper微控制器实现只支持100000的<code>i2c_speed</code>（<em>标准模式</em>，100kbit/s）。Klipper的"Linux"微控制器支持400000的速度（<em>快速模式</em>，400kbit/s），但它必须<a href="RPi_microcontroller.html#optional-enabling-i2c">在操作系统中设置</a>，否则会忽略<code>i2c_speed</code>参数。Klipper的"RP2040"微控制器和ATmega AVR系列通过<code>i2c_speed</code>参数支持400000的速率。所有其他Klipper微控制器使用100000的速率并忽略<code>i2c_speed</code>参数。</p>
|
||||
<p>Most Klipper micro-controller implementations only support an <code>i2c_speed</code> of 100000 (<em>standard mode</em>, 100kbit/s). The Klipper "Linux" micro-controller supports a 400000 speed (<em>fast mode</em>, 400kbit/s), but it must be <a href="RPi_microcontroller.html#optional-enabling-i2c">set in the operating system</a> and the <code>i2c_speed</code> parameter is otherwise ignored. The Klipper "RP2040" micro-controller and ATmega AVR family and some STM32 (F0, G0, G4, L4, F7, H7) support a rate of 400000 via the <code>i2c_speed</code> parameter. All other Klipper micro-controllers use a 100000 rate and ignore the <code>i2c_speed</code> parameter.</p>
|
||||
<div class="highlight"><pre><span></span><code>#i2c_address:
|
||||
# The i2c address of the device. This must specified as a decimal
|
||||
# number (not in hex). The default depends on the type of device.
|
||||
|
|
|
|||
|
|
@ -1412,7 +1412,7 @@
|
|||
# 温度探针配置文件
|
||||
</code></pre></div>
|
||||
|
||||
<p>在<a href="Config_Reference.html#temperature_probe">configuration reference</a>有更多关于如何配置<code>temperature_probe</code>的内容。建议配置<code>calibration_position</code>， <code>calibration_extruder_temp</code>， <code>extruder_heating_z</code>, 和 <code>calibration_bed_temp</code>选项，这会在接下来的校准过程中自动完成一些步骤。</p>
|
||||
<p>See the <a href="Config_Reference.html#temperature_probe">configuration reference</a> for further details on how to configure a <code>temperature_probe</code>. It is advised to configure the <code>calibration_position</code>, <code>calibration_extruder_temp</code>, <code>extruder_heating_z</code>, and <code>calibration_bed_temp</code> options, as doing so will automate some of the steps outlined below. If the printer to be calibrated is enclosed, it is strongly recommended to set the <code>max_validation_temp</code> option to a value between 100 and 120.</p>
|
||||
<p>Eddy probe的制造商提供了一些可以使用的校准预设可以手动添加到<code>[probe_eddy_current]</code>中到<code>drift_calibration</code>选项中。如果他们没提供预设的校准文件或者预设的校准文件不适用于你的系统，<code>temperature_probe</code>模块可以使用TEMPERATURE_PROBE_CALIBRATE`命令来进行手动校准。</p>
|
||||
<p>在进行校准前，用户应该知道大概的探针线圈最大温度。这个温度应该被配置到<code>TEMPERATURE_PROBE_CALIBRATE</code>命令的<code>TARGET</code>选项中。校准的目的是尽量有一个最宽的温度范围，因此最好在打印机冷却后进行校准，并且在线圈到达最高温度的时候停止。</p>
|
||||
<p>当<code>[temperature_probe]</code> 被配置后，可以使用以下步骤进行热偏移校准：</p>
|
||||
|
|
|
|||
|
|
@ -1542,6 +1542,16 @@
|
|||
<td>2634K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>RP2350</td>
|
||||
<td>4167K</td>
|
||||
<td>2663K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SAME70</td>
|
||||
<td>6667K</td>
|
||||
<td>4737K</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>STM32H743</td>
|
||||
<td>9091K</td>
|
||||
<td>6061K</td>
|
||||
|
|
|
|||
|
|
@ -869,6 +869,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -1958,6 +1965,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -3089,6 +3116,13 @@
|
|||
ANGLE_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#angle_chip_calibrate" class="md-nav__link">
|
||||
ANGLE_CHIP_CALIBRATE
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4178,6 +4212,26 @@
|
|||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level" class="md-nav__link">
|
||||
[quad_gantry_level]
|
||||
</a>
|
||||
|
||||
<nav class="md-nav" aria-label="[quad_gantry_level]">
|
||||
<ul class="md-nav__list">
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#quad_gantry_level_1" class="md-nav__link">
|
||||
QUAD_GANTRY_LEVEL
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
</nav>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
|
|
@ -4750,6 +4804,11 @@
|
|||
<p>The following commands are available when an <a href="Config_Reference.html#angle">angle config section</a> is enabled.</p>
|
||||
<h4 id="angle_calibrate">ANGLE_CALIBRATE<a class="headerlink" href="#angle_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CALIBRATE CHIP=<芯片名></code>：在指定传感器上执行角度校准（必须有一个<code>[angle 芯片名]</code>的配置分段，并指定一个<code>stepper</code>参数）。重要的是 - 这个工具将命令步进电机移动而不检查正常的运动学边界限制。理想情况下，在执行校准之前，电机不应被连接到任何打印机的滑块。如果不能断开步进电机和打印机滑块的连接，在开始校准之前，确保滑车接近其轨道的中心。(在这个测试中，步进电机可能会向前或向后移动两圈）。完成这个测试后，使用<code>SAVE_CONFIG</code>命令，将校准数据保存到配置文件中。为了使用这个工具，必须安装Python "numpy"软件包（更多信息见<a href="Measuring_Resonances.html#software-installation">测量谐振文档</a>）。</p>
|
||||
<h4 id="angle_chip_calibrate">ANGLE_CHIP_CALIBRATE<a class="headerlink" href="#angle_chip_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_CHIP_CALIBRATE CHIP=<chip_name></code>: Perform internal sensor calibration, if implemented (MT6826S/MT6835).</p>
|
||||
<ul>
|
||||
<li><strong>MT68XX</strong>: The motor should be disconnected from any printer carriage before performing calibration. After calibration, the sensor should be reset by disconnecting the power.</li>
|
||||
</ul>
|
||||
<h4 id="angle_debug_read">ANGLE_DEBUG_READ<a class="headerlink" href="#angle_debug_read" title="Permanent link">¶</a></h4>
|
||||
<p><code>ANGLE_DEBUG_READ CHIP=<配置名> REG=<寄存器></code>：查询传感器寄存器"寄存器"（例如：44或0x2C）。该命令常用于调试，仅适用于tle5012b芯片。</p>
|
||||
<h4 id="angle_debug_write">ANGLE_DEBUG_WRITE<a class="headerlink" href="#angle_debug_write" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4758,7 +4817,12 @@
|
|||
<p>The following commands are available when the <a href="Config_Reference.html#axis_twist_compensation">axis_twist_compensation config
|
||||
section</a> is enabled.</p>
|
||||
<h4 id="axis_twist_compensation_calibrate">AXIS_TWIST_COMPENSATION_CALIBRATE<a class="headerlink" href="#axis_twist_compensation_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [SAMPLE_COUNT=<value>]</code>: 启动X轴扭转校准向导。 <code>SAMPLE_COUNT</code> 指定沿着X轴进行校准的点数，默认为3个。</p>
|
||||
<p><code>AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]</code></p>
|
||||
<p>Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.</p>
|
||||
<ul>
|
||||
<li><strong>AXIS:</strong> Define the axis (<code>X</code> or <code>Y</code>) for which the twist compensation will be calibrated. If not specified, the axis defaults to <code>'X'</code>.</li>
|
||||
<li><strong>AUTO:</strong> Enables automatic calibration mode. When <code>AUTO=True</code>, the calibration will run for both the X and Y axes. In this mode, <code>AXIS</code> cannot be specified. If both <code>AXIS</code> and <code>AUTO</code> are provided, an error will be raised.</li>
|
||||
</ul>
|
||||
<h3 id="bed_mesh">[bed_mesh]<a class="headerlink" href="#bed_mesh" title="Permanent link">¶</a></h3>
|
||||
<p>启用[床网格配置部分]（config_Reference.md#bed_mesh）时，以下命令可用（另请参阅[床网格指南]（bed_mesh.md））。</p>
|
||||
<h4 id="bed_mesh_calibrate">BED_MESH_CALIBRATE<a class="headerlink" href="#bed_mesh_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4862,6 +4926,7 @@ section</a> is enabled.</p>
|
|||
<p>当<a href="Config_Reference.html#fan_generic">fan_generic 配置分段</a>被启用时，以下命令可用：</p>
|
||||
<h4 id="set_fan_speed">SET_FAN_SPEED<a class="headerlink" href="#set_fan_speed" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_FAN_SPEED FAN=config_name SPEED=<速度></code>该命令设置风扇的速度。"速度" 必须在0.0到1.0之间。</p>
|
||||
<p><code>SET_FAN_SPEED PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given fan. For example, if one defined a <code>[display_template my_fan_template]</code> config section then one could assign <code>TEMPLATE=my_fan_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the fan will be automatically set to the resulting speed. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_FAN_SPEED</code> commands to manage the values directly).</p>
|
||||
<h3 id="filament_switch_sensor">[filament_switch_sensor]<a class="headerlink" href="#filament_switch_sensor" title="Permanent link">¶</a></h3>
|
||||
<p>启用<a href="Config_Reference.html#filament_switch_sensor">filament_switch_sensor</a>或<a href="Config_Reference.html#filament_motion_sensor">filament_motion_sensor</a>配置分段后，可使用以下命令：</p>
|
||||
<h4 id="query_filament_sensor">QUERY_FILAMENT_SENSOR<a class="headerlink" href="#query_filament_sensor" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4886,7 +4951,7 @@ section</a> is enabled.</p>
|
|||
<h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>FORCE_MOVE STEPPER=<config_name> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]</code> 。该命令将以给定的恒定速度（mm/s）强制移动给定的步进器，移动距离（mm）。如果指定了ACCEL并且大于零，那么将使用给定的加速度（单位：mm/s^2）；否则不进行加速。不执行边界检查；不进行运动学更新；一个轴上的其他平行步进器将不会被移动。请谨慎使用，因为不正确的命令可能会导致损坏使用该命令几乎肯定会使低级运动学处于不正确的状态；随后发出G28命令以重置运动学。该命令用于低级别的诊断和调试。</p>
|
||||
<h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<值>] [Y=<值>] [Z=<值>]</code>：强制设定低级运动学代码使用的打印头位置。这是一个诊断和调试工具，常规的轴转换应该使用 SET_GCODE_OFFSET 和/或 G92指令。如果没有指定一个轴，则使用上一次命令的打印头位置。设定一个不合理的数值可能会导致内部程序问题。这个命令可能会使边界检查失效，使用后发送 G28 来重置运动学。</p>
|
||||
<p><code>SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]</code>: Force the low-level kinematic code to believe the toolhead is at the given cartesian position. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an axis is not specified then it will default to the position that the head was last commanded to. Setting an incorrect or invalid position may lead to internal software errors. Use the CLEAR parameter to forget the homing state for the given axes. Note that CLEAR will not override the previous functionality; if an axis is not specified to CLEAR it will have its kinematic position set as per above. This command may invalidate future boundary checks; issue a G28 afterwards to reset the kinematics.</p>
|
||||
<h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">¶</a></h3>
|
||||
<p>The gcode module is automatically loaded.</p>
|
||||
<h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -4980,6 +5045,7 @@ section</a> is enabled.</p>
|
|||
<p>使用<a href="Config_Reference.html#output_pin">output_pin 配置分段</a>时，以下命令可用：</p>
|
||||
<h4 id="set_pin">SET_PIN<a class="headerlink" href="#set_pin" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value></code>: Set the pin to the given output <code>VALUE</code>. VALUE should be 0 or 1 for "digital" output pins. For PWM pins, set to a value between 0.0 and 1.0, or between 0.0 and <code>scale</code> if a scale is configured in the output_pin config section.</p>
|
||||
<p><code>SET_PIN PIN=config_name TEMPLATE=<template_name> [<param_x>=<literal>]</code>: If <code>TEMPLATE</code> is specified then it assigns a <a href="Config_Reference.html#display_template">display_template</a> to the given pin. For example, if one defined a <code>[display_template my_pin_template]</code> config section then one could assign <code>TEMPLATE=my_pin_template</code> here. The display_template should produce a string containing a floating point number with the desired value. The template will be continuously evaluated and the pin will be automatically set to the resulting value. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If TEMPLATE is an empty string then this command will clear any previous template assigned to the pin (one can then use <code>SET_PIN</code> commands to manage the values directly).</p>
|
||||
<h3 id="palette2">[palette2]<a class="headerlink" href="#palette2" title="Permanent link">¶</a></h3>
|
||||
<p>当<a href="Config_Reference.html#palette2">palette2 配置分段</a>被启用时，以下命令可用：</p>
|
||||
<p>Palette打印通过在GCode文件中嵌入特殊的OCodes（Omega Codes）来工作。</p>
|
||||
|
|
@ -5037,6 +5103,10 @@ section</a> is enabled.</p>
|
|||
<p>The following command is available when a <a href="Config_Reference.html#pwm_cycle_time">pwm_cycle_time config section</a> is enabled.</p>
|
||||
<h4 id="set_pin_1">SET_PIN<a class="headerlink" href="#set_pin_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>SET_PIN PIN=config_name VALUE=<value> [CYCLE_TIME=<cycle_time>]</code>: This command works similarly to <a href="#output_pin">output_pin</a> SET_PIN commands. The command here supports setting an explicit cycle time using the CYCLE_TIME parameter (specified in seconds). Note that the CYCLE_TIME parameter is not stored between SET_PIN commands (any SET_PIN command without an explicit CYCLE_TIME parameter will use the <code>cycle_time</code> specified in the pwm_cycle_time config section).</p>
|
||||
<h3 id="quad_gantry_level">[quad_gantry_level]<a class="headerlink" href="#quad_gantry_level" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#quad_gantry_level">quad_gantry_level config section</a> is enabled.</p>
|
||||
<h4 id="quad_gantry_level_1">QUAD_GANTRY_LEVEL<a class="headerlink" href="#quad_gantry_level_1" title="Permanent link">¶</a></h4>
|
||||
<p><code>QUAD_GANTRY_LEVEL [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="query_adc">[query_adc]<a class="headerlink" href="#query_adc" title="Permanent link">¶</a></h3>
|
||||
<p>The query_adc module is automatically loaded.</p>
|
||||
<h4 id="query_adc_1">QUERY_ADC<a class="headerlink" href="#query_adc_1" title="Permanent link">¶</a></h4>
|
||||
|
|
@ -5053,9 +5123,9 @@ section</a> is enabled.</p>
|
|||
<h4 id="measure_axes_noise">MEASURE_AXES_NOISE<a class="headerlink" href="#measure_axes_noise" title="Permanent link">¶</a></h4>
|
||||
<p><code>MEASURE_AXES_NOISE</code>：测量并输出所有启用的加速度计芯片的所有轴的噪声。</p>
|
||||
<h4 id="test_resonances">TEST_RESONANCES<a class="headerlink" href="#test_resonances" title="Permanent link">¶</a></h4>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> OUTPUT=<resonances,raw_data> [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [POINT=x,y,z] [INPUT_SHAPING=[<0:1>]]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>adxl345_chip_name</code> can be one or more configured adxl345 chip,delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. Note that <code>adxl345</code> can be omitted from named adxl345 chips. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<p><code>TEST_RESONANCES AXIS=<axis> [OUTPUT=<resonances,raw_data>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [POINT=x,y,z] [INPUT_SHAPING=<0:1>]</code>: Runs the resonance test in all configured probe points for the requested "axis" and measures the acceleration using the accelerometer chips configured for the respective axis. "axis" can either be X or Y, or specify an arbitrary direction as <code>AXIS=dx,dy</code>, where dx and dy are floating point numbers defining a direction vector (e.g. <code>AXIS=X</code>, <code>AXIS=Y</code>, or <code>AXIS=1,-1</code> to define a diagonal direction). Note that <code>AXIS=dx,dy</code> and <code>AXIS=-dx,-dy</code> is equivalent. <code>chip_name</code> can be one or more configured accel chips, delimited with comma, for example <code>CHIPS="adxl345, adxl345 rpi"</code>. If POINT is specified it will override the point(s) configured in <code>[resonance_tester]</code>. If <code>INPUT_SHAPING=0</code> or not set(default), disables input shaping for the resonance testing, because it is not valid to run the resonance testing with the input shaper enabled. <code>OUTPUT</code> parameter is a comma-separated list of which outputs will be written. If <code>raw_data</code> is requested, then the raw accelerometer data is written into a file or a series of files <code>/tmp/raw_data_<axis>_[<chip_name>_][<point>_]<name>.csv</code> with (<code><point>_</code> part of the name generated only if more than 1 probe point is configured or POINT is specified). If <code>resonances</code> is specified, the frequency response is calculated (across all probe points) and written into <code>/tmp/resonances_<axis>_<name>.csv</code> file. If unset, OUTPUT defaults to <code>resonances</code>, and NAME defaults to the current time in "YYYYMMDD_HHMMSS" format.</p>
|
||||
<h4 id="shaper_calibrate">SHAPER_CALIBRATE<a class="headerlink" href="#shaper_calibrate" title="Permanent link">¶</a></h4>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [HZ_PER_SEC=<hz_per_sec>] [CHIPS=<adxl345_chip_name>] [MAX_SMOOTHING=<max_smoothing>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<p><code>SHAPER_CALIBRATE [AXIS=<axis>] [NAME=<name>] [FREQ_START=<min_freq>] [FREQ_END=<max_freq>] [ACCEL_PER_HZ=<accel_per_hz>][HZ_PER_SEC=<hz_per_sec>] [CHIPS=<chip_name>] [MAX_SMOOTHING=<max_smoothing>] [INPUT_SHAPING=<0:1>]</code>: Similarly to <code>TEST_RESONANCES</code>, runs the resonance test as configured, and tries to find the optimal parameters for the input shaper for the requested axis (or both X and Y axes if <code>AXIS</code> parameter is unset). If <code>MAX_SMOOTHING</code> is unset, its value is taken from <code>[resonance_tester]</code> section, with the default being unset. See the <a href="Measuring_Resonances.html#max-smoothing">Max smoothing</a> of the measuring resonances guide for more information on the use of this feature. The results of the tuning are printed to the console, and the frequency responses and the different input shapers values are written to a CSV file(s) <code>/tmp/calibration_data_<axis>_<name>.csv</code>. Unless specified, NAME defaults to the current time in "YYYYMMDD_HHMMSS" format. Note that the suggested input shaper parameters can be persisted in the config by issuing <code>SAVE_CONFIG</code> command, and if <code>[input_shaper]</code> was already enabled previously, these parameters take effect immediately.</p>
|
||||
<h3 id="respond">[respond]<a class="headerlink" href="#respond" title="Permanent link">¶</a></h3>
|
||||
<p>The following standard G-Code commands are available when the <a href="Config_Reference.html#respond">respond config section</a> is enabled:</p>
|
||||
<ul>
|
||||
|
|
@ -5161,7 +5231,7 @@ section</a> is enabled.</p>
|
|||
<h3 id="z_tilt">[z_tilt]<a class="headerlink" href="#z_tilt" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when the <a href="Config_Reference.html#z_tilt">z_tilt config section</a> is enabled.</p>
|
||||
<h4 id="z_tilt_adjust">Z_TILT_ADJUST<a class="headerlink" href="#z_tilt_adjust" title="Permanent link">¶</a></h4>
|
||||
<p>`Z_TILT_ADJUST[HORIZONTAL_MOVE_Z=<value>][<probe_parameter>=<value>>：此命令将探测配置中指定的点，然后对每个Z步进器进行独立调整以补偿倾斜。有关可选探测参数的详细信息，请参阅PROBE命令。可选的“HORIZONTAL_MOVE_Z”值将覆盖配置文件中指定的“HORIZONTAL_MOVE_Z”选项。</p>
|
||||
<p><code>Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]</code>: This command will probe the points specified in the config and then make independent adjustments to each Z stepper to compensate for tilt. See the PROBE command for details on the optional probe parameters. The optional <code>RETRIES</code>, <code>RETRY_TOLERANCE</code>, and <code>HORIZONTAL_MOVE_Z</code> values override those options specified in the config file.</p>
|
||||
<h3 id="temperature_probe">[temperature_probe]<a class="headerlink" href="#temperature_probe" title="Permanent link">¶</a></h3>
|
||||
<p>The following commands are available when a <a href="Config_Reference.html#temperature_probe">temperature_probe config section</a> is enabled.</p>
|
||||
<h4 id="temperature_probe_calibrate">TEMPERATURE_PROBE_CALIBRATE<a class="headerlink" href="#temperature_probe_calibrate" title="Permanent link">¶</a></h4>
|
||||
|
|
|
|||
|
|
@ -912,8 +912,8 @@
|
|||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#lis2dw" class="md-nav__link">
|
||||
配置LIS2DW系列
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -990,6 +990,13 @@
|
|||
选择 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="#lis2dw" class="md-nav__link">
|
||||
配置LIS2DW系列
|
||||
<a href="#configure-lis2dw-series-over-spi" class="md-nav__link">
|
||||
Configure LIS2DW series over SPI
|
||||
</a>
|
||||
|
||||
</li>
|
||||
|
|
@ -1852,6 +1859,13 @@
|
|||
选择 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="_1">共振值测量<a class="headerlink" href="#_1" 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="_2">安装指南<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
|
|
@ -2195,10 +2214,15 @@ sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-
|
|||
</code></pre></div>
|
||||
|
||||
<p>接下来，为了在Klipper环境中安装NumPy，运行命令：</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>请注意，根据CPU性能的不同，这可能需要<em>很长</em>时间，最长可达10-20分钟。请耐心等待安装完成。在某些情况下，如果主板的RAM太少，安装可能会失败，您需要启用交换。</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="rpiadxl345">使用RPI配置ADXL345<a class="headerlink" href="#rpiadxl345" title="Permanent link">¶</a></h4>
|
||||
<p>首先，检查并按照<a href="rpi_微控制器.md">RPI微控制器文档</a>中的说明在Raspberry PI上设置“Linux MCU”。这将配置在您的PI上运行的第二个Klipper实例。</p>
|
||||
<p>通过运行<code>sudo raspi-config</code> 后的 "Interfacing options"菜单中启用 SPI 以确保Linux SPI 驱动已启用。</p>
|
||||
|
|
@ -2257,7 +2281,7 @@ pin: adxl:gpio23
|
|||
</code></pre></div>
|
||||
|
||||
<p>通过<code>RESTART</code>命令重启Klipper。</p>
|
||||
<h4 id="lis2dw">配置LIS2DW系列<a class="headerlink" href="#lis2dw" 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列表]。
|
||||
#将<mySerial>更改为您在上面找到的任何内容。例如,。
|
||||
#usb-klipper_rp2040_E661640843545B2E-if00。
|
||||
|
|
@ -2482,6 +2506,8 @@ max_smoothing: 0.25 # an example
|
|||
|
||||
<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>如果重新校准一个整形器，并且建议的整形器配置的报告平滑度与你在以前的校准中得到的几乎相同，这个步骤可以被跳过。</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="_11">自定义测试轴<a class="headerlink" href="#_11" title="Permanent link">¶</a></h3>
|
||||
<p><code>TEST_RESONANCES</code>命令支持自定义轴。虽然这对输入整形器校准并不真正有用，但它可用于深入研究打印机共振，并检查皮带张力等。</p>
|
||||
<p>要检查CoreXY打印机上的皮带张力，请执行</p>
|
||||
|
|
|
|||
|
|
@ -1447,7 +1447,7 @@ git clone https://github.com/Klipper3d/klipper
|
|||
<h2 id="octoprint-klipper">配置OctoPrint 去使用Klipper<a class="headerlink" href="#octoprint-klipper" title="Permanent link">¶</a></h2>
|
||||
<p>OctoPrint 网页服务器需要配置和Klipper Host 软件的连接。使用浏览器登录到 OctoPrint 网页并且配置以下内容：</p>
|
||||
<p>浏览到设置界面（在网页顶部的扳手图标）。在"Serial Connection" 下的 "Additional serial ports" 添加：</p>
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.sock
|
||||
<div class="highlight"><pre><span></span><code>~/printer_data/comms/klippy.serial
|
||||
</code></pre></div>
|
||||
|
||||
<p>然后点击"保存"。</p>
|
||||
|
|
|
|||
|
|
@ -1480,7 +1480,7 @@
|
|||
<p><a href="https://bigtree-tech.com/collections/all-products"><img src="./img/sponsors/BTT_BTT.png" width="200" style="margin:25px"/></a></p>
|
||||
<p>BIGTREETECH是Klipper的官方主板赞助商。BIGTREETECH致力于开发创新和有竞争力的产品，更好地服务于3D打印社区。在<a href="https://www.facebook.com/BIGTREETECH">Facebook</a>或<a href="https://twitter.com/BigTreeTech">Twitter</a>上关注他们。</p>
|
||||
<h2 id="_2">赞助<a class="headerlink" href="#_2" title="Permanent link">¶</a></h2>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a> <a href="https://peopoly.net"><img src="./img/sponsors/peopoly-logo.png" width="200" style="margin:25px" /></a></p>
|
||||
<p><a href="https://obico.io/klipper.html?source=klipper_sponsor"><img src="./img/sponsors/obico-light-horizontal.png" width="200" style="margin:25px" /></a></p>
|
||||
<h2 id="klipper">Klipper的开发者们<a class="headerlink" href="#klipper" title="Permanent link">¶</a></h2>
|
||||
<h3 id="kevin-oconnor">Kevin O'Connor<a class="headerlink" href="#kevin-oconnor" title="Permanent link">¶</a></h3>
|
||||
<p>Kevin 是项目原作者和当前Klipper的维护。支持链接在<a href="https://ko-fi.com/koconnor">https://ko-fi.com/koconnor</a> 或者 <a href="https://www.patreon.com/koconnor">https://www.patreon.com/koconnor</a></p>
|
||||
|
|
|
|||
Binary file not shown.
File diff suppressed because one or more lines are too long
110
zh/sitemap.xml
110
zh/sitemap.xml
|
|
@ -2,277 +2,277 @@
|
|||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2025-01-16</lastmod>
|
||||
<lastmod>2025-01-17</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Loading…
Add table
Add a link
Reference in a new issue