From 06b88075fb4f53e0ded41a3406be979f9ad3c1df Mon Sep 17 00:00:00 2001 From: KevinOConnor Date: Sun, 4 May 2025 00:06:21 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20Klipper3?= =?UTF-8?q?d/klipper@1cc63980747b80516f8fc4f022eedf18ae739086=20?= =?UTF-8?q?=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../__pycache__/mkdocs_hooks.cpython-38.pyc | Bin 983 -> 983 bytes fr/404.html | 4 +- fr/API_Server.html | 36 +- fr/Axis_Twist_Compensation.html | 50 +- fr/BLTouch.html | 4 +- fr/Beaglebone.html | 4 +- fr/Bed_Level.html | 4 +- fr/Bed_Mesh.html | 4 +- fr/Benchmarks.html | 28 +- fr/Bootloader_Entry.html | 4 +- fr/Bootloaders.html | 4 +- fr/CANBUS.html | 5 +- fr/CANBUS_Troubleshooting.html | 38 +- fr/CANBUS_protocol.html | 4 +- fr/CONTRIBUTING.html | 4 +- fr/Code_Overview.html | 4 +- fr/Command_Templates.html | 4 +- fr/Config_Changes.html | 10 +- fr/Config_Reference.html | 194 +- fr/Config_checks.html | 4 +- fr/Contact.html | 19 +- fr/Debugging.html | 4 +- fr/Delta_Calibrate.html | 4 +- fr/Eddy_Probe.html | 8 +- fr/Endstop_Phase.html | 4 +- fr/Example_Configs.html | 4 +- fr/Exclude_Object.html | 4 +- fr/FAQ.html | 4 +- fr/Features.html | 28 +- fr/G-Codes.html | 524 +++--- fr/Hall_Filament_Width_Sensor.html | 4 +- fr/Installation.html | 30 +- fr/Kinematics.html | 4 +- fr/Load_Cell.html | 1635 +++++++++++++++++ fr/MCU_Commands.html | 4 +- fr/Manual_Level.html | 4 +- fr/Measuring_Resonances.html | 23 +- fr/Multi_MCU_Homing.html | 4 +- fr/Navigation.html | 4 +- fr/OctoPrint.html | 4 +- fr/Overview.html | 5 +- fr/Packaging.html | 4 +- fr/Pressure_Advance.html | 6 +- fr/Probe_Calibrate.html | 4 +- fr/Protocol.html | 4 +- fr/RPi_microcontroller.html | 4 +- fr/Releases.html | 74 +- fr/Resonance_Compensation.html | 4 +- fr/Rotation_Distance.html | 4 +- fr/SDCard_Updates.html | 4 +- fr/Skew_Correction.html | 4 +- fr/Slicers.html | 4 +- fr/Sponsors.html | 8 +- fr/Status_Reference.html | 74 +- fr/TMC_Drivers.html | 5 +- fr/TSL1401CL_Filament_Width_Sensor.html | 4 +- fr/Using_PWM_Tools.html | 4 +- .../__pycache__/mkdocs_hooks.cpython-38.pyc | Bin 983 -> 983 bytes fr/index.html | 4 +- fr/search/search_index.json | 2 +- fr/sitemap.xml | 115 +- fr/sitemap.xml.gz | Bin 229 -> 229 bytes hu/404.html | 4 +- hu/API_Server.html | 36 +- hu/Axis_Twist_Compensation.html | 50 +- hu/BLTouch.html | 4 +- hu/Beaglebone.html | 4 +- hu/Bed_Level.html | 4 +- hu/Bed_Mesh.html | 4 +- hu/Benchmarks.html | 28 +- hu/Bootloader_Entry.html | 4 +- hu/Bootloaders.html | 4 +- hu/CANBUS.html | 5 +- hu/CANBUS_Troubleshooting.html | 38 +- hu/CANBUS_protocol.html | 4 +- hu/CONTRIBUTING.html | 4 +- hu/Code_Overview.html | 4 +- hu/Command_Templates.html | 4 +- hu/Config_Changes.html | 10 +- hu/Config_Reference.html | 538 +++--- hu/Config_checks.html | 4 +- hu/Contact.html | 19 +- hu/Debugging.html | 4 +- hu/Delta_Calibrate.html | 4 +- hu/Eddy_Probe.html | 8 +- hu/Endstop_Phase.html | 4 +- hu/Example_Configs.html | 4 +- hu/Exclude_Object.html | 4 +- hu/FAQ.html | 4 +- hu/Features.html | 28 +- hu/G-Codes.html | 524 +++--- hu/Hall_Filament_Width_Sensor.html | 4 +- hu/Installation.html | 30 +- hu/Kinematics.html | 4 +- hu/Load_Cell.html | 1635 +++++++++++++++++ hu/MCU_Commands.html | 4 +- hu/Manual_Level.html | 4 +- hu/Measuring_Resonances.html | 23 +- hu/Multi_MCU_Homing.html | 4 +- hu/Navigation.html | 4 +- hu/OctoPrint.html | 4 +- hu/Overview.html | 5 +- hu/Packaging.html | 4 +- hu/Pressure_Advance.html | 6 +- hu/Probe_Calibrate.html | 4 +- hu/Protocol.html | 4 +- hu/RPi_microcontroller.html | 4 +- hu/Releases.html | 74 +- hu/Resonance_Compensation.html | 4 +- hu/Rotation_Distance.html | 4 +- hu/SDCard_Updates.html | 4 +- hu/Skew_Correction.html | 4 +- hu/Slicers.html | 4 +- hu/Sponsors.html | 8 +- hu/Status_Reference.html | 74 +- hu/TMC_Drivers.html | 5 +- hu/TSL1401CL_Filament_Width_Sensor.html | 4 +- hu/Using_PWM_Tools.html | 4 +- .../__pycache__/mkdocs_hooks.cpython-38.pyc | Bin 983 -> 983 bytes hu/index.html | 4 +- hu/search/search_index.json | 2 +- hu/sitemap.xml | 115 +- hu/sitemap.xml.gz | Bin 229 -> 229 bytes it/404.html | 4 +- it/API_Server.html | 36 +- it/Axis_Twist_Compensation.html | 50 +- it/BLTouch.html | 4 +- it/Beaglebone.html | 4 +- it/Bed_Level.html | 4 +- it/Bed_Mesh.html | 4 +- it/Benchmarks.html | 28 +- it/Bootloader_Entry.html | 4 +- it/Bootloaders.html | 4 +- it/CANBUS.html | 5 +- it/CANBUS_Troubleshooting.html | 38 +- it/CANBUS_protocol.html | 4 +- it/CONTRIBUTING.html | 4 +- it/Code_Overview.html | 4 +- it/Command_Templates.html | 4 +- it/Config_Changes.html | 10 +- it/Config_Reference.html | 196 +- it/Config_checks.html | 4 +- it/Contact.html | 19 +- it/Debugging.html | 4 +- it/Delta_Calibrate.html | 4 +- it/Eddy_Probe.html | 8 +- it/Endstop_Phase.html | 4 +- it/Example_Configs.html | 4 +- it/Exclude_Object.html | 4 +- it/FAQ.html | 4 +- it/Features.html | 28 +- it/G-Codes.html | 524 +++--- it/Hall_Filament_Width_Sensor.html | 4 +- it/Installation.html | 30 +- it/Kinematics.html | 4 +- it/Load_Cell.html | 1635 +++++++++++++++++ it/MCU_Commands.html | 4 +- it/Manual_Level.html | 4 +- it/Measuring_Resonances.html | 23 +- it/Multi_MCU_Homing.html | 4 +- it/Navigation.html | 4 +- it/OctoPrint.html | 4 +- it/Overview.html | 5 +- it/Packaging.html | 4 +- it/Pressure_Advance.html | 6 +- it/Probe_Calibrate.html | 4 +- it/Protocol.html | 4 +- it/RPi_microcontroller.html | 4 +- it/Releases.html | 74 +- it/Resonance_Compensation.html | 4 +- it/Rotation_Distance.html | 4 +- it/SDCard_Updates.html | 4 +- it/Skew_Correction.html | 4 +- it/Slicers.html | 4 +- it/Sponsors.html | 8 +- it/Status_Reference.html | 74 +- it/TMC_Drivers.html | 5 +- it/TSL1401CL_Filament_Width_Sensor.html | 4 +- it/Using_PWM_Tools.html | 4 +- .../__pycache__/mkdocs_hooks.cpython-38.pyc | Bin 983 -> 983 bytes it/index.html | 4 +- it/search/search_index.json | 2 +- it/sitemap.xml | 115 +- it/sitemap.xml.gz | Bin 229 -> 229 bytes sitemap.xml | 110 +- sitemap.xml.gz | Bin 229 -> 229 bytes zh-Hant/404.html | 4 +- zh-Hant/API_Server.html | 36 +- zh-Hant/Axis_Twist_Compensation.html | 50 +- zh-Hant/BLTouch.html | 4 +- zh-Hant/Beaglebone.html | 4 +- zh-Hant/Bed_Level.html | 4 +- zh-Hant/Bed_Mesh.html | 4 +- zh-Hant/Benchmarks.html | 28 +- zh-Hant/Bootloader_Entry.html | 4 +- zh-Hant/Bootloaders.html | 4 +- zh-Hant/CANBUS.html | 5 +- zh-Hant/CANBUS_Troubleshooting.html | 38 +- zh-Hant/CANBUS_protocol.html | 4 +- zh-Hant/CONTRIBUTING.html | 4 +- zh-Hant/Code_Overview.html | 4 +- zh-Hant/Command_Templates.html | 4 +- zh-Hant/Config_Changes.html | 10 +- zh-Hant/Config_Reference.html | 197 +- zh-Hant/Config_checks.html | 4 +- zh-Hant/Contact.html | 19 +- zh-Hant/Debugging.html | 4 +- zh-Hant/Delta_Calibrate.html | 4 +- zh-Hant/Eddy_Probe.html | 8 +- zh-Hant/Endstop_Phase.html | 4 +- zh-Hant/Example_Configs.html | 4 +- zh-Hant/Exclude_Object.html | 4 +- zh-Hant/FAQ.html | 4 +- zh-Hant/Features.html | 28 +- zh-Hant/G-Codes.html | 524 +++--- zh-Hant/Hall_Filament_Width_Sensor.html | 4 +- zh-Hant/Installation.html | 30 +- zh-Hant/Kinematics.html | 4 +- zh-Hant/Load_Cell.html | 1635 +++++++++++++++++ zh-Hant/MCU_Commands.html | 4 +- zh-Hant/Manual_Level.html | 4 +- zh-Hant/Measuring_Resonances.html | 23 +- zh-Hant/Multi_MCU_Homing.html | 4 +- zh-Hant/Navigation.html | 4 +- zh-Hant/OctoPrint.html | 4 +- zh-Hant/Overview.html | 5 +- zh-Hant/Packaging.html | 4 +- zh-Hant/Pressure_Advance.html | 6 +- zh-Hant/Probe_Calibrate.html | 4 +- zh-Hant/Protocol.html | 4 +- zh-Hant/RPi_microcontroller.html | 4 +- zh-Hant/Releases.html | 74 +- zh-Hant/Resonance_Compensation.html | 4 +- zh-Hant/Rotation_Distance.html | 4 +- zh-Hant/SDCard_Updates.html | 4 +- zh-Hant/Skew_Correction.html | 4 +- zh-Hant/Slicers.html | 4 +- zh-Hant/Sponsors.html | 8 +- zh-Hant/Status_Reference.html | 74 +- zh-Hant/TMC_Drivers.html | 5 +- zh-Hant/TSL1401CL_Filament_Width_Sensor.html | 4 +- zh-Hant/Using_PWM_Tools.html | 4 +- .../__pycache__/mkdocs_hooks.cpython-38.pyc | Bin 983 -> 983 bytes zh-Hant/index.html | 4 +- zh-Hant/search/search_index.json | 2 +- zh-Hant/sitemap.xml | 115 +- zh-Hant/sitemap.xml.gz | Bin 229 -> 229 bytes zh/404.html | 4 +- zh/API_Server.html | 36 +- zh/Axis_Twist_Compensation.html | 50 +- zh/BLTouch.html | 4 +- zh/Beaglebone.html | 4 +- zh/Bed_Level.html | 4 +- zh/Bed_Mesh.html | 4 +- zh/Benchmarks.html | 28 +- zh/Bootloader_Entry.html | 4 +- zh/Bootloaders.html | 4 +- zh/CANBUS.html | 5 +- zh/CANBUS_Troubleshooting.html | 38 +- zh/CANBUS_protocol.html | 4 +- zh/CONTRIBUTING.html | 4 +- zh/Code_Overview.html | 4 +- zh/Command_Templates.html | 4 +- zh/Config_Changes.html | 10 +- zh/Config_Reference.html | 197 +- zh/Config_checks.html | 4 +- zh/Contact.html | 19 +- zh/Debugging.html | 4 +- zh/Delta_Calibrate.html | 4 +- zh/Eddy_Probe.html | 8 +- zh/Endstop_Phase.html | 4 +- zh/Example_Configs.html | 4 +- zh/Exclude_Object.html | 4 +- zh/FAQ.html | 4 +- zh/Features.html | 28 +- zh/G-Codes.html | 524 +++--- zh/Hall_Filament_Width_Sensor.html | 4 +- zh/Installation.html | 30 +- zh/Kinematics.html | 4 +- zh/Load_Cell.html | 1635 +++++++++++++++++ zh/MCU_Commands.html | 4 +- zh/Manual_Level.html | 4 +- zh/Measuring_Resonances.html | 23 +- zh/Multi_MCU_Homing.html | 4 +- zh/Navigation.html | 4 +- zh/OctoPrint.html | 4 +- zh/Overview.html | 5 +- zh/Packaging.html | 4 +- zh/Pressure_Advance.html | 6 +- zh/Probe_Calibrate.html | 4 +- zh/Protocol.html | 4 +- zh/RPi_microcontroller.html | 4 +- zh/Releases.html | 74 +- zh/Resonance_Compensation.html | 4 +- zh/Rotation_Distance.html | 4 +- zh/SDCard_Updates.html | 4 +- zh/Skew_Correction.html | 4 +- zh/Slicers.html | 4 +- zh/Sponsors.html | 8 +- zh/Status_Reference.html | 74 +- zh/TMC_Drivers.html | 5 +- zh/TSL1401CL_Filament_Width_Sensor.html | 4 +- zh/Using_PWM_Tools.html | 4 +- .../__pycache__/mkdocs_hooks.cpython-38.pyc | Bin 983 -> 983 bytes zh/index.html | 4 +- zh/search/search_index.json | 2 +- zh/sitemap.xml | 115 +- zh/sitemap.xml.gz | Bin 229 -> 229 bytes 308 files changed, 12816 insertions(+), 2971 deletions(-) create mode 100644 fr/Load_Cell.html create mode 100644 hu/Load_Cell.html create mode 100644 it/Load_Cell.html create mode 100644 zh-Hant/Load_Cell.html create mode 100644 zh/Load_Cell.html diff --git a/_klipper3d/__pycache__/mkdocs_hooks.cpython-38.pyc b/_klipper3d/__pycache__/mkdocs_hooks.cpython-38.pyc index b35d064afccd741ff7712f5330a447e1416d7442..5ff73a582d54e41ccc718ae6c104014e8811ccac 100644 GIT binary patch delta 20 acmcc4ex02=l$V!_0SIE(i*4jS!wdj44+QQ2 delta 20 acmcc4ex02=l$V!_0SFexif-gS!wdj3`UKwq diff --git a/fr/404.html b/fr/404.html index 2747d4c47..cfebc5d36 100644 --- a/fr/404.html +++ b/fr/404.html @@ -1281,8 +1281,8 @@
  • - - None + + Load Cells
    • diff --git a/fr/API_Server.html b/fr/API_Server.html index 3d7763918..31f565335 100644 --- a/fr/API_Server.html +++ b/fr/API_Server.html @@ -1177,15 +1177,8 @@
  • - - hx71x/dump_hx71x - - -
    • - -
  • - - ads1220/dump_ads1220 + + load_cell/dump_force
    • @@ -1517,8 +1510,8 @@
  • - - None + + Load Cells
    • @@ -1714,15 +1707,8 @@
  • - - hx71x/dump_hx71x - - -
    • - -
  • - - ads1220/dump_ads1220 + + load_cell/dump_force
    • @@ -1881,12 +1867,10 @@ gcode:

    Ce point de terminaison est utilisé pour s'abonner aux données du capteur d'angle. L'obtention de ces mises à jour de mouvement de bas niveau peut être utile à des fins de diagnostic et de débogage. L'utilisation de ce point de terminaison peut augmenter la charge système de Klipper.

    Une requête peut ressembler à : {"id": 123, "method":"angle/dump_angle", "params": {"sensor": "my_angle_sensor", "response_template": {}}} et peut renvoyer : {"id": 123,"result":{"header":["time","angle"]}} et peut produire ultérieurement des messages asynchrones tels que : { "params":{"position_offset":3.151562,"errors":0, "data":[[1290.951905,-5063],[1290.952321,-5065]]}}

    Le champ "en-tête" dans la réponse initiale à la requête est utilisé pour décrire les champs présents dans les réponses "données" ultérieures.

    -

    hx71x/dump_hx71x

    -

    This endpoint is used to subscribe to raw HX711 and HX717 ADC data. Obtaining these low-level ADC updates may be useful for diagnostic and debugging purposes. Using this endpoint may increase Klipper's system load.

    -

    A request may look like: {"id": 123, "method":"hx71x/dump_hx71x", "params": {"sensor": "load_cell", "response_template": {}}} and might return: {"id": 123,"result":{"header":["time","counts","value"]}} and might later produce asynchronous messages such as: {"params":{"data":[[3292.432935, 562534, 0.067059278], [3292.4394937, 5625322, 0.670590639]]}}

    -

    ads1220/dump_ads1220

    -

    This endpoint is used to subscribe to raw ADS1220 ADC data. Obtaining these low-level ADC updates may be useful for diagnostic and debugging purposes. Using this endpoint may increase Klipper's system load.

    -

    A request may look like: {"id": 123, "method":"ads1220/dump_ads1220", "params": {"sensor": "load_cell", "response_template": {}}} and might return: {"id": 123,"result":{"header":["time","counts","value"]}} and might later produce asynchronous messages such as: {"params":{"data":[[3292.432935, 562534, 0.067059278], [3292.4394937, 5625322, 0.670590639]]}}

    +

    load_cell/dump_force

    +

    This endpoint is used to subscribe to force data produced by a load_cell. Using this endpoint may increase Klipper's system load.

    +

    A request may look like: {"id": 123, "method":"load_cell/dump_force", "params": {"sensor": "load_cell", "response_template": {}}} and might return: {"id": 123,"result":{"header":["time", "force (g)", "counts", "tare_counts"]}} and might later produce asynchronous messages such as: {"params":{"data":[[3292.432935, 40.65, 562534, -234467]]}}

    +

    Le champ "en-tête" dans la réponse initiale à la requête est utilisé pour décrire les champs présents dans les réponses "données" ultérieures.

    pause_resume/cancel

    Ce point final est similaire à l'exécution de la commande G-Code "PRINT_CANCEL". Par exemple : {"id": 123, "method": "pause_resume/cancel"}

    Comme pour le point de terminaison "gcode/script", ce point de terminaison ne se termine qu'après la fin de toutes les commandes G-Code en attente.

    diff --git a/fr/Axis_Twist_Compensation.html b/fr/Axis_Twist_Compensation.html index e7c5c4126..dc091bb97 100644 --- a/fr/Axis_Twist_Compensation.html +++ b/fr/Axis_Twist_Compensation.html @@ -726,13 +726,6 @@ For Y-Axis Calibration - - -
  • - - Automatic Calibration for Both Axes - -
    • @@ -1365,8 +1358,8 @@
  • - - None + + Load Cells
    • @@ -1440,13 +1433,6 @@ For Y-Axis Calibration - - -
  • - - Automatic Calibration for Both Axes - -
    • @@ -1479,7 +1465,7 @@

    Compensation de torsion de l'axe

    -

    Ce document décrit le module [axis_twist_compensation].

    +

    This document describes the [axis_twist_compensation] module.

    Some printers may have a small twist in their X rail which can skew the results of a probe attached to the X carriage. This is common in printers with designs like the Prusa MK3, Sovol SV06 etc and is further described under probe location bias. It may result in probe operations such as Bed Mesh, Screws Tilt Adjust, Z Tilt Adjust etc returning inaccurate representations of the bed.

    Ce module utilise des mesures manuelles effectuées par l'utilisateur afin de corriger les résultats de la sonde. Notez que si votre axe est significativement tordu il est fortement recommandé d'utiliser en premier lieu des moyens mécaniques pour le corriger avant d'utiliser des solutions logicielles.

    @@ -1495,42 +1481,38 @@ bias. It may result in probe operations such as Bed 
    AXIS_TWIST_COMPENSATION_CALIBRATE
    -

    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: SAMPLE_COUNT=<value>

    +

    This command will calibrate the X-axis by default.

    +
      -
    1. Adjust Your Z Offset: After completing the calibration, be sure to [adjust your Z offset] (Probe_Calibrate.md#calibrating-probe-z-offset).
      2. -
    2. -

      Perform Bed Leveling Operations: Use probe-based operations as needed, such as:

      +
    3. Adjust Your Z Offset: After completing the calibration, be sure to adjust your Z offset.
      4. +
    4. Perform Bed Leveling Operations: Use probe-based operations as needed, such as:
      5. +
    - -
  • -

    Finalize the Setup:

    +
      +
    1. Finalize the Setup:
      2. +
    -
    • -

    For Y-Axis Calibration

    The calibration process for the Y-axis is similar to the X-axis. To calibrate the Y-axis, use:

    AXIS_TWIST_COMPENSATION_CALIBRATE AXIS=Y

    This will guide you through the same measuring process as for the X-axis.

    -

    Automatic Calibration for Both Axes

    -

    To perform automatic calibration for both the X and Y axes without manual intervention, use:

    -
    AXIS_TWIST_COMPENSATION_CALIBRATE AUTO=True
-
    - -

    In this mode, the calibration process will run for both axes automatically.

    Conseil : 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.

    [axis_twist_compensation] setup and commands

    -

    Configuration options for [axis_twist_compensation] can be found in the Configuration Reference.

    -

    Commands for [axis_twist_compensation] can be found in the G-Codes Reference

    +

    Configuration options for [axis_twist_compensation] can be found in the Configuration Reference.

    +

    Commands for [axis_twist_compensation] can be found in the G-Codes Reference

    diff --git a/fr/BLTouch.html b/fr/BLTouch.html index 8c101c3e9..00730f7d8 100644 --- a/fr/BLTouch.html +++ b/fr/BLTouch.html @@ -1380,8 +1380,8 @@
  • - - None + + Load Cells
    • diff --git a/fr/Beaglebone.html b/fr/Beaglebone.html index 21c077a30..9a65a9eda 100644 --- a/fr/Beaglebone.html +++ b/fr/Beaglebone.html @@ -1399,8 +1399,8 @@
  • - - None + + Load Cells
    • diff --git a/fr/Bed_Level.html b/fr/Bed_Level.html index 4824f6934..c592a3176 100644 --- a/fr/Bed_Level.html +++ b/fr/Bed_Level.html @@ -1345,8 +1345,8 @@
  • - - None + + Load Cells
    • diff --git a/fr/Bed_Mesh.html b/fr/Bed_Mesh.html index 99eb8d745..a8656433d 100644 --- a/fr/Bed_Mesh.html +++ b/fr/Bed_Mesh.html @@ -1568,8 +1568,8 @@
  • - - None + + Load Cells
    • diff --git a/fr/Benchmarks.html b/fr/Benchmarks.html index 441dab9da..a19d45b6c 100644 --- a/fr/Benchmarks.html +++ b/fr/Benchmarks.html @@ -1475,8 +1475,8 @@
  • - - None + + Load Cells
    • @@ -1985,30 +1985,30 @@ finalize_config crc=0

    Test du taux de pas sur STM32H7

    -

    La séquence de configuration suivante est utilisée sur un STM32H743VIT6 :

    +

    The following configuration sequence is used on STM32H723:

    allocate_oids count=3
-config_stepper oid=0 step_pin=PD4 dir_pin=PD3 invert_step=-1 step_pulse_ticks=0
-config_stepper oid=1 step_pin=PA15 dir_pin=PA8 invert_step=-1 step_pulse_ticks=0
-config_stepper oid=2 step_pin=PE2 dir_pin=PE3 invert_step=-1 step_pulse_ticks=0
+config_stepper oid=0 step_pin=PA13 dir_pin=PB5 invert_step=-1 step_pulse_ticks=52
+config_stepper oid=1 step_pin=PB2 dir_pin=PB6 invert_step=-1 step_pulse_ticks=52
+config_stepper oid=2 step_pin=PB3 dir_pin=PB7 invert_step=-1 step_pulse_ticks=52
 finalize_config crc=0
    -

    Le test a été exécuté pour la dernière fois sur le commit 00191b5c avec la version de gcc arm-none-eabi-gcc (15:8-2019-q3-1+b1) 8.3.1 20190703 (release) [gcc- 8 branches révision 273027].

    +

    The test was last run on commit 554ae78d with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0.

    - + - + - +
    stm32h7stm32h723 ticks
    1 moteur pas à pas4470
    3 moteurs pas à pas198181
    @@ -2215,7 +2215,7 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic finalize_config crc=0 -

    The test was last run on commit f6718291 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.

    +

    The test was last run on commit 14c105b8 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.

    @@ -2226,11 +2226,11 @@ finalize_config crc=0 - + - +
    1 moteur pas à pas53
    3 moteurs pas à pas2214
    @@ -2252,7 +2252,7 @@ finalize_config crc=0 -

    (*) 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.

    +

    (*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 200Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 ARM core cycles.

    Test du taux de pas pour le MCU Linux

    La séquence de configuration suivante est utilisée sur un Raspberry Pi :

    allocate_oids count=3
diff --git a/fr/Bootloader_Entry.html b/fr/Bootloader_Entry.html
index 8c0128da6..df0f88052 100644
--- a/fr/Bootloader_Entry.html
+++ b/fr/Bootloader_Entry.html
@@ -1429,8 +1429,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Bootloaders.html b/fr/Bootloaders.html
index 78c65321b..dc4ac5186 100644
--- a/fr/Bootloaders.html
+++ b/fr/Bootloaders.html
@@ -1501,8 +1501,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/CANBUS.html b/fr/CANBUS.html
index bc4b32992..b0e436efc 100644
--- a/fr/CANBUS.html
+++ b/fr/CANBUS.html
@@ -1371,8 +1371,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1549,6 +1549,7 @@ iface can0 can static
 
 
 
      
+
    • It is only valid to use USB to CAN bridge mode if there is a functioning CAN bus with at least one other node available (in addition to the bridge node itself). Use a standard USB configuration if the goal is to communicate only with the single USB device. Using USB to CAN bridge mode without a fully functioning CAN bus (including terminating resistors and an additional node) may result in sporadic errors even when communicating with the bridge node.
      • 
 
    • Une carte de pont USB à CAN n'apparaîtra pas en tant que périphérique série USB, elle ne s'affichera pas lors de l'execution de la commande ls /dev/serial/by-id, et elle ne peut pas être configurée dans le fichier Klipper avec un paramètre serial:. La carte pont apparaît comme un « adaptateur CAN USB » et est configuré dans le printer.cfg en tant que Nœud CAN.
      • 
 
    
 
    Conseils pour le dépannage
    
diff --git a/fr/CANBUS_Troubleshooting.html b/fr/CANBUS_Troubleshooting.html
index a8fbe5124..50e2483bf 100644
--- a/fr/CANBUS_Troubleshooting.html
+++ b/fr/CANBUS_Troubleshooting.html
@@ -1284,6 +1284,13 @@
     Use an appropriate txqueuelen setting
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1370,8 +1377,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1444,6 +1451,13 @@
     Use an appropriate txqueuelen setting
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1500,12 +1514,16 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    Vérifier que toutes les fiches et sertissages sur le câblage CAN sont entièrement sécurisés. Le mouvement de la tête d'outil d'imprimante peut faire bouger le câblage de bus CAN et provoquer des faux contacts - source d'erreurs de communication aléatoires.
    
 
    Vérification de l'augmentation du compteur octets_invalide
    
 
    Le fichier journal de Klipper affiche une ligne Stats une fois par seconde lorsque l'imprimante est active. Ces lignes "Stats" ont un compteur bytes_invalid pour chaque microcontrôleur. Ce compteur ne devrait pas augmenter au cours de l'utilisation normale de l'imprimante (il est normal que le compteur soit non nul après un RESTART et ce n'est pas une préoccupation si le compteur augmente une fois par mois). Si ce compteur augmente sur un microcontrôleur de bus CAN pendant un fonctionnement normal (s'il augmente toutes les heures ou plus fréquemment) alors c'est une indication d'un problème grave.
    
-
    L'augmentation du compteur bytes_invalid sur une connexion de bus CAN est un symptôme de messages réémis sur le bus CAN. Il existe deux causes connues de réémission de messages :
    
-
      
-
    1. Les anciennes versions du micrologiciel candlight ont un bug qui peut causer des réémissions de messages. Si vous utilisez un adaptateur USB CAN qui exécute ce micrologiciel, assurez-vous de mettre à jour le dernier micrologiciel si vous remarquez une incrémentation anormale du compteur bytes_invalid.
      2. 
-
    2. Certains noyaux Linux destinés à des périphériques embarqués sont connus pour réémettre les messages de bus CAN. Il peut être nécessaire d'utiliser un autre noyau Linux ou d'utiliser du matériel qui prend en charge les noyaux Linux courants qui ne présentent pas ce problème.
      3. 
-
    
-
    La réorganisation des messages est un problème grave qui doit être résolu. Cela entraînera un comportement instable et peut conduire à des erreurs déroutantes à n'importe quelle partie d'une impression.
    
+
    Incrementing bytes_invalid on a CAN bus connection is a symptom of reordered messages on the CAN bus. If seen, make sure to:
    
+
      
+
    • Use a Linux kernel version 6.6.0 or later.
      • 
+
    • If using a USB-to-CANBUS adapter running candlelight firmware, use v2.0 or later of candleLight_fw.
      • 
+
    • If using Klipper's USB-to-CANBUS bridge mode, make sure the bridge node is flashed with Klipper v0.12.0 or later.
      • 
+
    
+
    Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print. An incrementing bytes_invalid is not caused by wiring or similar hardware issues and can only be fixed by identifying and updating the faulty software.
    
+
    Older versions of the Linux kernel had a bug in the gs_usb canbus driver code that could cause reordered canbus packets. The issue is thought to be fixed in Linux commit 24bc41b4 which was released in v6.6.0. In some cases, older Linux versions may not show the problem (due to how hardware interrupts are configured), however if problems are seen the recommended solution is to upgrade to a newer kernel.
    
+
    Older versions of candlelight firmware could reorder canbus packets, and the issue is thought to be fixed in candlelight_fw commit 8b3a7b45.
    
+
    Older versions of Klipper's USB-to-CANBUS bridge code could incorrectly drop canbus messages. This is not as severe as reordering messages, but it should still be fixed. It is thought to be fixed with Klipper PR #6175.
    
 
    Use an appropriate txqueuelen setting
    
 
    The Klipper code uses the Linux kernel to manage CAN bus traffic. By default, the kernel will only queue 10 CAN transmit packets. It is recommended to configure the can0 device with a txqueuelen 128 to increase that size.
    
 
    If Klipper transmits a packet and Linux has filled all of its transmit queue space then Linux will drop that packet and messages like the following will appear in the Klipper log:
    
@@ -1517,6 +1535,10 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    One may check the current queue size by running the Linux command ip link show can0. It should report a bunch of text including the snippet qlen 128. If one sees something like qlen 10 then it indicates the CAN device has not been properly configured.
    
 
    It is not recommended to use a txqueuelen significantly larger than 128. A CAN bus running at a frequency of 1000000 will typically take around 120us to transmit a CAN packet. Thus a queue of 128 packets is likely to take around 15-20ms to drain. A substantially larger queue could cause excessive spikes in message round-trip-time which could lead to unrecoverable errors. Said another way, Klipper's application retransmit system is more robust if it does not have to wait for Linux to drain an excessively large queue of possibly stale data. This is analogous to the problem of bufferbloat on internet routers.
    
 
    Under normal circumstances Klipper may utilize ~25 queue slots per MCU - typically only utilizing more slots during retransmits. (Specifically, the Klipper host may transmit up to 192 bytes to each Klipper MCU before receiving an acknowledgment from that MCU.) If a single CAN bus has 5 or more Klipper MCUs on it, then it might be necessary to increase the txqueuelen above the recommended value of 128. However, as above, care should be taken when selecting a new value to avoid excessive round-trip-time latency.
    
+
    Use canbus_query.py only to identify nodes never previously seen
    
+
    It is only valid to use the canbus_query.py tool to identify micro-controllers that have never been previously identified. Once all nodes on a bus are identified, record the resulting uuids in the printer.cfg, and avoid running the tool unnecessarily.
    
+
    The tool is implemented using a low-level mechanism that can cause nodes to internally observe bus errors. These internal errors may result in communication interruptions and may result is some nodes disconnecting from the bus.
    
+
    It is not valid to use the tool to "ping" if a node is connected. Do not run the tool during an active print.
    
 
    Obtenir les journaux 'candump'
    
 
    Les messages de bus CAN envoyés au microcontrôleur sont gérés par le noyau Linux. Il est possible de capturer ces messages à des fins de débogage. Le journal de ces messages peut être utile lors des diagnostics.
    
 
    L'outil Linux can-utils fournit le logiciel de capture. Il peut être installé en exécutant :
    
diff --git a/fr/CANBUS_protocol.html b/fr/CANBUS_protocol.html
index 908dba198..b92d7f3a3 100644
--- a/fr/CANBUS_protocol.html
+++ b/fr/CANBUS_protocol.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/CONTRIBUTING.html b/fr/CONTRIBUTING.html
index c5de7e4c3..afa9515cc 100644
--- a/fr/CONTRIBUTING.html
+++ b/fr/CONTRIBUTING.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Code_Overview.html b/fr/Code_Overview.html
index db3c6949b..284bb8420 100644
--- a/fr/Code_Overview.html
+++ b/fr/Code_Overview.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Command_Templates.html b/fr/Command_Templates.html
index a31217a68..665632f65 100644
--- a/fr/Command_Templates.html
+++ b/fr/Command_Templates.html
@@ -1421,8 +1421,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Config_Changes.html b/fr/Config_Changes.html
index 72e51a102..cb8a91011 100644
--- a/fr/Config_Changes.html
+++ b/fr/Config_Changes.html
@@ -1327,8 +1327,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1410,6 +1410,12 @@
 
    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.
    
 
    Toutes les dates de ce document sont approximatives.
    
 
    Changements
    
+
    20250428: The maximum cycle_time for pwm [output_pin], [pwm_cycle_time], [pwm_tool], and similar config sections is now 3 seconds (reduced from 5 seconds). The maximum_mcu_duration in [pwm_tool] is now also 3 seconds.
    
+
    20250418: The manual_stepper STOP_ON_ENDSTOP feature may now take less time to complete. Previously, the command would wait the entire time the move could possibly take even if the endstop triggered earlier. Now, the command finishes shortly after the endstop trigger.
    
+
    20250417: SPI devices using "software SPI" are now rate limited. Previously, the spi_speed in the config was ignored and the transmission speed was only limited by the processing speed of the micro-controller. Now, speeds are limited by the spi_speed config parameter (actual hardware speeds are likely to be lower than the configured value due to software overhead).
    
+
    20250411: Klipper v0.13.0 released.
    
+
    20250308: The AUTO parameter of the AXIS_TWIST_COMPENSATION_CALIBRATE command has been removed.
    
+
    20250131: Option VARIABLE=<name> in SAVE_VARIABLE requires lowercase value. For example, extruder instead of mixedcase Extruder or uppercase EXTRUDER. Using any uppercase letter will raise an error.
    
 
    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 sweeping_period: 0 and accel_per_hz: 75 to the [resonance_tester] config section.
    
 
    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.
    
 
    20241112: Option CHIPS=<chip_name> in TEST_RESONANCES and SHAPER_CALIBRATE requires specifying the full name(s) of the accel chip(s). For example, adxl345 rpi instead of short name - rpi.
    
diff --git a/fr/Config_Reference.html b/fr/Config_Reference.html
index dcb9f1343..7d9a32746 100644
--- a/fr/Config_Reference.html
+++ b/fr/Config_Reference.html
@@ -931,6 +931,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -1741,6 +1748,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -2600,8 +2614,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3053,6 +3067,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -3863,6 +3884,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -5284,6 +5312,22 @@ cs_pin :
 #   de résonance.
    • +

    [icm20948]

    +

    Support for icm20948 accelerometers.

    +
    [icm20948]
+#i2c_address:
+#   Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
+#i2c_mcu:
+#i2c_bus:
+#i2c_software_scl_pin:
+#i2c_software_sda_pin:
+#i2c_speed: 400000
+#   See the "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.
+
    +

    [lis2dw]

    Support for LIS2DW accelerometers.

    [lis2dw]
@@ -5607,6 +5651,9 @@ z_offset:
 sensor_type: ldc1612
 #   The sensor chip used to perform eddy current measurements. This
 #   parameter must be provided and must be set to ldc1612.
+#frequency:
+#   The external crystal frequency (in Hz) of the LDC1612 chip.
+#   The default is 12000000.
 #intb_pin:
 #   MCU gpio pin connected to the ldc1612 sensor's INTB pin (if
 #   available). The default is to not use the INTB pin.
@@ -6536,23 +6583,27 @@ pin:
 
    Exécute le gcode quand un bouton est pressé ou relâché (ou quand une broche change d'état). Vous pouvez vérifier l'état du bouton en utilisant QUERY_BUTTON button=my_gcode_button.
    
 
    [gcode_button my_gcode_button]
 pin:
-#    La broche sur laquelle le bouton est connecté. Ce paramètre doit être
-#    fourni.
+#   The pin on which the button is connected. This parameter must be
+#   provided.
 #analog_range:
-#    Deux résistances séparées par des virgules (en Ohms) spécifiant la plage de
-#    résistance minimale et maximale de la résistance du bouton. Si le paramètre
-#    analog_range est fourni, la broche doit être une broche à capacité analogique.
-#    La valeur par défaut est d'utiliser un gpio numérique pour le bouton.
+#   Two comma separated resistances (in Ohms) specifying the minimum
+#   and maximum resistance range for the button. If analog_range is
+#   provided then the pin must be an analog capable pin. The default
+#   is to use digital gpio for the button.
 #analog_pullup_resistor:
-#    La résistance d'excursion (en Ohms) lorsque la gamme analogique est spécifiée.
-#    La valeur par défaut est 4700 ohms.
+#   The pullup resistance (in Ohms) when analog_range is specified.
+#   The default is 4700 ohms.
 #press_gcode:
-#    Une liste de commandes G-Code à exécuter lorsque le bouton est pressé.
-#    Les modèles G-Code sont pris en charge. Ce paramètre doit être fourni.
+#   A list of G-Code commands to execute when the button is pressed.
+#   G-Code templates are supported. This parameter must be provided.
 #release_gcode:
-#    Une liste de commandes G-code à exécuter lorsque le bouton est relâché.
-#    Les modèles G-Code sont supportés. La valeur par défaut est de ne pas exécuter
-#    de commandes lors du relâchement d'un bouton.
+#   A list of G-Code commands to execute when the button is released.
+#   G-Code templates are supported. The default is to not run any
+#   commands on a button release.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   button gcode. If the button is pressed and released during this
+#   delay, the entire button press is ignored. Default is 0.
 
    
 
 
    [output_pin]
    
@@ -6685,8 +6736,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -6735,6 +6787,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 4
 #driver_PWM_AMPL: 128
+#driver_FREEWHEEL: 0
 #driver_SGT: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6792,8 +6845,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #driver_MULTISTEP_FILT: True
 #driver_IHOLDDELAY: 8
 #driver_TPOWERDOWN: 20
@@ -6808,6 +6862,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #   Set the given register during the configuration of the TMC2208
 #   chip. This may be used to set custom motor parameters. The
 #   defaults for each parameter are next to the parameter name in the
@@ -6851,6 +6906,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #driver_SGTHRS: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6975,8 +7031,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7103,8 +7160,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7695,29 +7753,37 @@ text:
 
    Voir la référence des commandes pour plus d'informations.
    
 
    [filament_switch_sensor my_sensor]
 #pause_on_runout: True
-#    Lorsque défini sur True, une PAUSE sera exécutée immédiatement après qu'un runout
-#    soit détecté. Notez que si pause_on_runout est False et que le runout_gcode est omis,
-#    la détection du runout est désactivée. Par défaut, est True.
+#   When set to True, a PAUSE will execute immediately after a runout
+#   is detected. Note that if pause_on_runout is False and the
+#   runout_gcode is omitted then runout detection is disabled. Default
+#   is True.
 #runout_gcode:
-#    Une liste de commandes G-Code à exécuter après la détection d'une fin de filament.
-#    Voir docs/Command_Templates.md pour le format G-Code. Si pause_on_runout est
-#    réglé sur True, ce G-code sera exécuté après la fin de la PAUSE. Par défaut, aucune
-#    commande G-Code n'est exécutée.
+#   A list of G-Code commands to execute after a filament runout is
+#   detected. See docs/Command_Templates.md for G-Code format. If
+#   pause_on_runout is set to True this G-Code will run after the
+#   PAUSE is complete. The default is not to run any G-Code commands.
 #insert_gcode:
-#    Une liste de commandes G-Code à exécuter après qu'une insertion de filament soit détectée.
-#    Voir docs/Command_Templates.md pour le format G-Code. La valeur par défaut est de
-#    n'exécuter aucune commande G-Code, ce qui désactive la détection de l'insertion.
-#event_delay  3.0
-#    La durée minimale en secondes à attendre entre les événements.
-#    Des événements déclenchés durant cette période seront silencieusement ignorés.
-#    La valeur par défaut est de 3 secondes.
+#   A list of G-Code commands to execute after a filament insert is
+#   detected. See docs/Command_Templates.md for G-Code format. The
+#   default is not to run any G-Code commands, which disables insert
+#   detection.
+#event_delay: 3.0
+#   The minimum amount of time in seconds to delay between events.
+#   Events triggered during this time period will be silently
+#   ignored. The default is 3 seconds.
 #pause_delay: 0.5
-#    Le délai, en secondes, entre l'envoi de la commande de pause et l'exécution du runout_gcode.
-#    Il peut être utile d'augmenter ce délai si OctoPrint présente un comportement étrange lors de
-#    la pause. La valeur par défaut est 0.5 secondes.
+#   The amount of time to delay, in seconds, between the pause command
+#   dispatch and execution of the runout_gcode. It may be useful to
+#   increase this delay if OctoPrint exhibits strange pause behavior.
+#   Default is 0.5 seconds.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   switch gcode. The switch must he held in a single state for at least
+#   this long to activate. If the switch is toggled on/off during this delay,
+#   the event is ignored. Default is 0.
 #switch_pin:
-#    La broche sur laquelle l'interrupteur est connecté.
-#    Ce paramètre doit être fourni.
+#   The pin on which the switch is connected. This parameter must be
+#   provided.
 
    
 
 
    [filament_motion_sensor]
    
@@ -7810,6 +7876,16 @@ adc2:
 
    [load_cell]
 sensor_type:
 #   This must be one of the supported sensor types, see below.
+#counts_per_gram:
+#   The floating point number of sensor counts that indicates 1 gram of force.
+#   This value is calculated by the LOAD_CELL_CALIBRATE command.
+#reference_tare_counts:
+#   The integer tare value, in raw sensor counts, taken when LOAD_CELL_CALIBRATE
+#   is run. This is the default tare value when klipper starts up.
+#sensor_orientation:
+#   Change the sensor's orientation. Can be either 'normal' or 'inverted'.
+#   The default is 'normal'. Use 'inverted' if the sensor reports a
+#   decreasing force value when placed under load.
 
    
 
 
    HX711
    
@@ -7957,6 +8033,38 @@ vssa_pin :
 #    La valeur par défaut est de 2 secondes.
    +

    [ads1x1x]

    +

    ADS1013, ADS1014, ADS1015, ADS1113, ADS1114 and ADS1115 are I2C based Analog to Digital Converters that can be used for temperature sensors. They provide 4 analog input pins either as single line or as differential input.

    +

    Note: Use caution if using this sensor to control heaters. The heater min_temp and max_temp are only verified in the host and only if the host is running and operating normally. (ADC inputs directly connected to the micro-controller verify min_temp and max_temp within the micro-controller and do not require a working connection to the host.)

    +
    [ads1x1x my_ads1x1x]
+chip: ADS1115
+#pga: 4.096V
+#   Default value is 4.096V. The maximum voltage range used for the input. This
+#   scales all values read from the ADC. Options are: 6.144V, 4.096V, 2.048V,
+#   1.024V, 0.512V, 0.256V
+#adc_voltage: 3.3
+#   The suppy voltage for the device. This allows additional software scaling
+#   for all values read from the ADC.
+i2c_mcu: host
+i2c_bus: i2c.1
+#address_pin: GND
+#   Default value is GND.  There can be up to four addressed devices depending
+#   upon wiring of the device. Check the datasheet for details. The i2c_address
+#   can be specified directly instead of using the address_pin.
+
    + +

    The chip provides pins that can be used on other sensors.

    +
    sensor_type: ...
+#   Can be any thermistor or adc_temperature.
+sensor_pin: my_ads1x1x:AIN0
+#   A combination of the name of the ads1x1x chip and the pin. Possible
+#   pin values are AIN0, AIN1, AIN2 and AIN3 for single ended lines and
+#   DIFF01, DIFF03, DIFF13 and DIFF23 for differential between their
+#   correspoding lines. For example
+#   DIFF03 measures the differential between line 0 and 3. Only specific
+#   combinations for the differentials are allowed.
+
    +

    [replicape]

    Support de Replicape - voir le guide beaglebone et le fichier generic-replicape.cfg pour un exemple.

    #    La section de configuration "replicape" ajoute "replicape:stepper_x_enable" pour
@@ -8022,7 +8130,7 @@ host_mcu :
 
    Prise en charge des multimatériaux de la Palette 2 - assure une intégration plus étroite de la prise en charge des périphériques de la Palette 2 en mode connecté.
    
 
    Ce module nécessite également [virtual_sdcard] et [pause_resume] pour une fonctionnalité complète.
    
 
    Si vous utilisez ce module, n'utilisez pas le plugin Palette 2 pour Octoprint car ils entreront en conflit, et le module ne pourra pas s'initialiser correctement, ce qui fera échouer votre impression.
    
-
    Si vous utilisez Octoprint et que vous diffusez du gcode sur le port série au lieu d'imprimer à partir de virtual_sd, alors supprimez M1 et M0 de Commandes de pause dans Paramètres > Connexion série > Firmware & protocole évitera d'avoir à lancer l'impression sur la Palette 2 et de devoir lever la pause dans Octoprint pour que l'impression commence.
    
+
    If you use Octoprint and stream gcode over the serial port instead of printing from virtual_sd, then remove M1 and M0 from Pausing commands in Settings > Serial Connection > Firmware & protocol will prevent the need to start print on the Palette 2 and unpausing in Octoprint for your print to begin.
    
 
    [palette2]
 serial:
 # Le port série à connecter à la Palette 2.
diff --git a/fr/Config_checks.html b/fr/Config_checks.html
index 251f89af4..fd8c36e3e 100644
--- a/fr/Config_checks.html
+++ b/fr/Config_checks.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Contact.html b/fr/Contact.html
index 689b467c0..d4435155a 100644
--- a/fr/Contact.html
+++ b/fr/Contact.html
@@ -451,8 +451,8 @@
 
       
         
  • 
-  
-    GitHub Klipper
+  
+    Professional Services
   
   
 
    • 
@@ -1376,8 +1376,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
       
         
  • 
-  
-    GitHub Klipper
+  
+    Professional Services
   
   
 
    • 
@@ -1558,9 +1558,10 @@
 
    J’apporte des modifications que j’aimerais inclure dans Klipper
    
 
    Klipper est un logiciel libre et nous apprécions les nouvelles contributions.
    
 
    Les nouvelles contributions (que ce soit pour le code ou pour la documentation) sont soumises au moyen de Pull Requests Github. Référez-vous au document CONTRIBUTIONS pour connaître les informations importantes à ce sujet.
    
-
    Il existe plusieurs documents pour les développeurs. Si vous avez des questions sur le code, vous pouvez également les poser sur le Forum de la communauté Klipper ou sur le Discord de la communauté Klipper.
    
-
    GitHub Klipper
    
-
    Le GitHub de Klipper peut être utilisé par les contributeurs pour partager l'état de leur travail pour améliorer Klipper. On s'attend à ce que la personne qui ouvre un ticket github travaille activement sur la tâche donnée et soit celle qui effectue tout le travail nécessaire pour l'accomplir. Le GitHub de Klipper n'est pas utilisé pour les demandes, ni pour signaler des bogues, ni pour poser des questions. Utilisez plutôt le Forum communautaire Klipper ou le Discord communautaire Klipper.
    
+
    There are several documents for developers. If you have questions on the code then you can also ask in the Klipper Discourse Forum or on the Klipper Discord Chat.
    
+
    Professional Services
    
+
    
+
    Custom software development, software support, and solutions: https://ko-fi.com/koconnor
    
 
               
             
diff --git a/fr/Debugging.html b/fr/Debugging.html
index 04b8acb41..3b646b00c 100644
--- a/fr/Debugging.html
+++ b/fr/Debugging.html
@@ -1384,8 +1384,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Delta_Calibrate.html b/fr/Delta_Calibrate.html
index 23eb691d2..0b6868097 100644
--- a/fr/Delta_Calibrate.html
+++ b/fr/Delta_Calibrate.html
@@ -1365,8 +1365,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Eddy_Probe.html b/fr/Eddy_Probe.html
index 80c83ac76..3eff8bc9f 100644
--- a/fr/Eddy_Probe.html
+++ b/fr/Eddy_Probe.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1487,13 +1487,13 @@
       
       
         
-        
  • 
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Example_Configs.html b/fr/Example_Configs.html
index 772c156bd..4943bd4da 100644
--- a/fr/Example_Configs.html
+++ b/fr/Example_Configs.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Exclude_Object.html b/fr/Exclude_Object.html
index 6dac2080e..0f54dac5d 100644
--- a/fr/Exclude_Object.html
+++ b/fr/Exclude_Object.html
@@ -1356,8 +1356,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/FAQ.html b/fr/FAQ.html
index bd73ab6a9..eb9223f31 100644
--- a/fr/FAQ.html
+++ b/fr/FAQ.html
@@ -1488,8 +1488,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Features.html b/fr/Features.html
index dacc7f5d2..b57b341ab 100644
--- a/fr/Features.html
+++ b/fr/Features.html
@@ -1334,8 +1334,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1443,18 +1443,18 @@
 
  • Prise en charge du G-Code standard. Les commandes de g-code courantes produites par les "trancheurs" (slicers) typiques (SuperSlicer, Cura, PrusaSlicer, etc.) sont prises en charge.
    • 
 
  • Prise en charge de l'extrusion multiple. Les extrudeurs avec réchauffeurs partagés et les extrudeurs sur chariots indépendants (IDEX) sont également prises en charge.
    • 
 
  • Prise en charge des imprimantes cartésiennes, delta, corexy, corexz, hybrides-corexy, hybrides-corexz, deltesiennes, rotatives delta, polaires et à treuil.
    • 
-
  • Support du nivellement automatique du bed. Klipper peut être configuré pour une détection de base de l'inclinaison du bed ou pour une mise à niveau complète de celui-ci. Si le bed utilise plusieurs steppers Z, Klipper peut également le mettre à niveau en manipulant indépendamment les steppers Z. La plupart des capteurs de hauteur Z sont prises en charge, y compris les sondes BL-Touch et les sondes activées par servomoteur.
    • 
+
  • Automatic bed leveling support. Klipper can be configured for basic bed tilt detection or full mesh bed leveling. The bed mesh can be customized to the print size (adaptive bed mesh). If the bed uses multiple Z steppers then Klipper can also level by independently manipulating the Z steppers. Most Z height probes are supported, including BL-Touch probes and servo activated probes. Probes may be calibrated for axis twist compensation. If using an "eddy current probe" then one can utilize fast bed mesh scanning,
    • 
 
  • Prise en charge du calibrage delta automatique. L'outil d'étalonnage peut effectuer un étalonnage de base de la hauteur ainsi qu'un avancé des dimensions X et Y. L'étalonnage peut être effectué avec un palpeur de l'axe Z ou manuellement.
    • 
 
  • Prise en charge de l'option "exclure un objet" lors de l'impression. Lorsqu'il est configuré, ce module peut faciliter l'annulation d'un seul objet dans une impression en plusieurs parties.
    • 
-
  • Prise en charge des capteurs de température courants (par exemple, les thermistances courantes, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20 et LM75). Des thermistances et des capteurs de température analogiques personnalisés peuvent également être configurés. On peut surveiller le capteur de température interne du microcontrôleur et le capteur de température interne d'un Raspberry Pi.
    • 
+
  • Support for common temperature sensors (eg, common thermistors, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20, AHT10, SHT3x, and LM75). Custom thermistors and custom analog temperature sensors can also be configured. One can monitor the internal micro-controller temperature sensor and the internal temperature sensor of a Raspberry Pi.
    • 
 
  • Protection thermique basique de l'appareil activée par défaut.
    • 
-
  • Prise en charge des ventilateurs standard, des ventilateurs de buses et des ventilateurs à température contrôlée. Il n'est pas nécessaire de faire tourner les ventilateurs lorsque l'imprimante est inactive. La vitesse du ventilateur peut être contrôlée sur les ventilateurs dotés d'un tachymètre.
    • 
+
  • Support for standard fans, nozzle fans, and temperature controlled fans. No need to keep fans running when the printer is idle. Fan speed can be monitored on fans that have a tachometer. One can assign a "math formula" to a fan for automatic fan speed updating.
    • 
 
  • Prise en charge de la configuration en temps réel des pilotes de moteurs pas à pas TMC2130, TMC2208/TMC2224, TMC2209, TMC2660 et TMC5160. Il existe également un support pour le contrôle du courant des pilotes de moteurs pas à pas traditionnels via AD5206, DAC084S085, MCP4451, MCP4728, MCP4018, et les broches PWM.
    • 
 
  • Prise en charge des écrans LCD courants fixés directement à l'imprimante. Un menu par défaut est également disponible. Le contenu de l'écran et du menu peut être entièrement personnalisé via le fichier de configuration.
    • 
 
  • Accélération constante et prise en charge du "look-ahead". Tous les mouvements de l'imprimante s'accélèrent progressivement de l'arrêt à la vitesse de croisière, puis décélèrent pour revenir à l'arrêt. Le flux entrant de commandes de mouvement en G-Code est mis en file d'attente et analysé - l'accélération entre les mouvements dans une direction similaire sera optimisée pour réduire les blocages d'impression et améliorer le temps d'impression global.
    • 
 
  • Klipper met en œuvre un algorithme de "fin de phase pas à pas" qui peut améliorer la précision des interrupteurs de butée. Lorsqu'il est correctement réglé, il peut améliorer l'adhérence de la première couche d'une impression.
    • 
 
  • Prise en charge des capteurs de présence de filaments, des capteurs de mouvement de filaments et des capteurs de largeur de filaments.
    • 
-
  • Prise en charge de la mesure et l'enregistrement de l'accélération à l'aide d'un accéléromètre adxl345, mpu9250 et mpu6050.
    • 
+
  • Support for measuring and recording acceleration using adxl345, mpu9250, mpu6050, lis2dw12, lis3dh, and icm20948 accelerometers.
    • 
 
  • Prise en charge de la limitation de la vitesse maximale des mouvements courts en "zigzag" pour réduire les vibrations et le bruit de l'imprimante. Voir le document Cinématiques pour plus d'informations.
    • 
 
  • Des exemples de fichiers de configuration sont disponibles pour de nombreuses imprimantes courantes. Consultez le répertoire des configurations pour en obtenir la liste.
    • 
 
@@ -1526,11 +1526,6 @@
 1622K
 
 
-RP2040
-2400K
-1636K
-
-
 SAM4E8E
 2500K
 1674K
@@ -1556,6 +1551,11 @@
 2634K
 
 
+RP2040
+4000K
+2571K
+
+
 RP2350
 4167K
 2663K
@@ -1566,9 +1566,9 @@
 4737K
 
 
-STM32H743
-9091K
-6061K
+STM32H723
+7429K
+8619K
 
 
 
diff --git a/fr/G-Codes.html b/fr/G-Codes.html
index f0a9eff1b..9dc1d517e 100644
--- a/fr/G-Codes.html
+++ b/fr/G-Codes.html
@@ -1620,6 +1620,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -1694,33 +1756,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1789,26 +1824,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1850,6 +1865,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -2281,6 +2316,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -2429,54 +2512,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -3006,8 +3041,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3881,6 +3916,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -3955,33 +4052,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4050,26 +4120,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4111,6 +4161,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -4542,6 +4612,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -4690,54 +4808,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -4831,11 +4901,10 @@
 
    The following commands are available when the axis_twist_compensation config
 section is enabled.
    
 
    AXIS_TWIST_COMPENSATION_CALIBRATE
    
-
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]
    
+
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [SAMPLE_COUNT=<value>]
    
 
    Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.
    
 
      
 
    • AXIS: Define the axis (X or Y) for which the twist compensation will be calibrated. If not specified, the axis defaults to 'X'.
      • 
-
    • AUTO: Enables automatic calibration mode. When AUTO=True, the calibration will run for both the X and Y axes. In this mode, AXIS cannot be specified. If both AXIS and AUTO are provided, an error will be raised.
      • 
 
    
 
    [bed_mesh]
    
 
    Les commandes suivantes sont disponibles lorsque la section configuration de bed_mesh est activée (voir également le guide de bed_mesh).
    
@@ -4965,7 +5034,10 @@ section is enabled.
    
 
    FORCE_MOVE
    
 
    FORCE_MOVE STEPPER=<nom_de_la_configuration> DISTANCE=<valeur> VELOCITE=<valeur> [ACCEL=<valeur>] : 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.
    
 
    SET_KINEMATIC_POSITION
    
-
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]: 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.
    
+
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [SET_HOMED=<[X][Y][Z]>] [CLEAR_HOMED=<[X][Y][Z]>]: Force the low-level kinematic code to believe the toolhead is at the given cartesian position and set/clear homed status. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. Setting an incorrect or invalid position may lead to internal software errors.
    
+
    The X, Y, and Z parameters are used to alter the low-level kinematic position tracking. If any of these parameters are not set then the position is not changed - for example SET_KINEMATIC_POSITION Z=10 would set all axes as homed, set the internal Z position to 10, and leave the X and Y positions unchanged. Changing the internal position tracking is not dependent on the internal homing state - one may alter the position for both homed and not homed axes, and similarly one may set or clear the homing state of an axis without altering its internal position.
    
+
    The SET_HOMED parameter defaults to XYZ which instructs the kinematics to consider all axes as homed. A bare SET_KINEMATIC_POSITION command will result in all axes being considered homed (and not change its current position). If it is not desired to change the state of homed axes then assign SET_HOMED to an empty string - for example: SET_KINEMATIC_POSITION SET_HOMED= X=10. It is also possible to request an individual axis be considered homed (eg, SET_HOMED=X), but note that non-cartesian style kinematics (such as delta kinematics) may not support setting an individual axis as homed.
    
+
    The CLEAR_HOMED parameter instructs the kinematics to consider the given axes as not homed. For example, CLEAR_HOMED=XYZ would request all axes to be considered not homed (and thus require homing prior to movement on those axes). The default is SET_HOMED=XYZ even if CLEAR_HOMED is present, so the command SET_KINEMATIC_POSITION CLEAR_HOMED=Z will set X and Y as homed and clear the homing state for Z. Use SET_KINEMATIC_POSITION SET_HOMED= CLEAR_HOMED=Z if the goal is to clear only the Z homing state. If an axis is specified in neither SET_HOMED nor CLEAR_HOMED then its homing state is not changed and if it is specified in both then CLEAR_HOMED has precedence. It is possible to request clearing of an individual axis, but on non-cartesian style kinematics (such as delta kinematics) doing so may result in clearing the homing state of additional axes. Note the CLEAR parameter is currently an alias for the CLEAR_HOMED parameter, but this alias will be removed in the future.
    
 
    [gcode]
    
 
    Le module gcode est automatiquement chargé.
    
 
    RESTART
    
@@ -5028,6 +5100,28 @@ section is enabled.
    
 
    La commande suivante est activée si une section de configuration input_shaper a été activée (voir également le guide de compensation de résonance).
    
 
    SET_INPUT_SHAPER
    
 
    SET_INPUT_SHAPER [SHAPER_FREQ_X=<shaper_freq_x>] [SHAPER_FREQ_Y=<shaper_freq_y>] [DAMPING_RATIO_X=<damping_ratio_x>] [DAMPING_RATIO_Y=<damping_ratio_y>] [SHAPER_TYPE=<shaper>] [SHAPER_TYPE_X=<shaper_type_x>] [SHAPER_TYPE_Y=<shaper_type_y>] : Modifie les paramètres de mise en forme d'entrée. Notez que le paramètre SHAPER_TYPE réinitialise le shaper d'entrée pour les axes X et Y même si différents types de shaper ont été configurés dans la section [input_shaper]. SHAPER_TYPE ne peut pas être utilisé avec l'un des paramètres SHAPER_TYPE_X et SHAPER_TYPE_Y. Voir config reference pour plus de détails sur chacun de ces paramètres.
    
+
    [led]
    
+
    La commande suivante est disponible lorsque l'une des sections led config est activée.
    
+
    SET_LED
    
+
    SET_LED LED=<nom_de_la_configuration> RED=<valeur> GREEN=<valeur> BLUE=<valeur> WHITE=<valeur> [INDEX=<index>] [TRANSMIT=0] [SYNC=1] : Ceci définit la sortie de la LED. Chaque <valeur> de couleur doit être comprise entre 0.0 et 1.0. L'option WHITE n'est valable que pour les LEDs RGBW. Si la LED supporte plusieurs puces dans une chaîne, on peut spécifier INDEX pour modifier la couleur de la seule puce donnée (1 pour la première puce, 2 pour la seconde, etc.). Si INDEX n'est pas spécifié, alors toutes les LEDs de la chaîne seront réglées sur la couleur fournie. Si TRANSMIT=0 est spécifié, le changement de couleur ne sera effectué que lors de la prochaine commande SET_LED qui ne spécifie pas TRANSMIT=0 ; cela peut être utile en combinaison avec le paramètre INDEX pour effectuer plusieurs mises à jour dans une chaîne. Par défaut, la commande SET_LED synchronisera ses changements avec les autres commandes gcode en cours. Cela peut conduire à un comportement indésirable si les LEDs sont réglées alors que l'imprimante n'imprime pas, car cela réinitialisera le délai d'inactivité. Si un timing précis n'est pas nécessaire, le paramètre optionnel SYNC=0 peut être spécifié pour appliquer les changements sans réinitialiser le délai d'inactivité.
    
+
    SET_LED_TEMPLATE
    
+
    SET_LED_TEMPLATE LED=<nom_de_la_led> TEMPLATE=<nom_du_modèle> [<param_x>=<literal>] [INDEX=<index>] : Attribue un modèle d'affichage à une LED donnée. Par exemple, si l'on définit une section de configuration [display_template my_led_template], on peut affecter TEMPLATE=my_led_template ici. Le modèle d'affichage doit produire une chaîne de caractères séparée par des virgules contenant quatre nombres à virgule flottante correspondant aux paramètres de couleur rouge, vert, bleu et blanc. Le modèle sera continuellement évalué et la LED sera automatiquement réglée sur les couleurs résultantes. On peut définir des paramètres display_template à utiliser pendant l'évaluation du modèle (les paramètres seront analysés comme des littéraux Python). Si INDEX n'est pas spécifié, alors toutes les puces dans la chaîne de la LED seront réglées sur le modèle, sinon seule la puce avec l'index donné sera mise à jour. Si TEMPLATE est une chaîne vide, cette commande effacera tout modèle précédent assigné à la LED (on peut alors utiliser les commandes SET_LED pour gérer les paramètres de couleur de la LED).
    
+
    [load_cell]
    
+
    The following commands are enabled if a load_cell config section has been enabled.
    
+
    LOAD_CELL_DIAGNOSTIC
    
+
    LOAD_CELL_DIAGNOSTIC [LOAD_CELL=<config_name>]: This command collects 10 seconds of load cell data and reports statistics that can help you verify proper operation of the load cell. This command can be run on both calibrated and uncalibrated load cells.
    
+
    LOAD_CELL_CALIBRATE
    
+
    LOAD_CELL_CALIBRATE [LOAD_CELL=<config_name>]: Start the guided calibration utility. Calibration is a 3 step process:
    
+
      
+
    1. First you remove all load from the load cell and run the TARE command
      2. 
+
    2. Next you apply a known load to the load cell and run the CALIBRATE GRAMS=nnn command
      3. 
+
    3. Finally use the ACCEPT command to save the results
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    LOAD_CELL_TARE
    
+
    LOAD_CELL_TARE [LOAD_CELL=<config_name>]: This works just like the tare button on digital scale. It sets the current raw reading of the load cell to be the zero point reference value. The response is the percentage of the sensors range that was read and the raw value in counts.
    
+
    LOAD_CELL_READ load_cell="name"
    
+
    LOAD_CELL_READ [LOAD_CELL=<config_name>]: This command takes a reading from the load cell. The response is the percentage of the sensors range that was read and the raw value in counts. If the load cell is calibrated a force in grams is also reported.
    
 
    [manual_probe]
    
 
    Le module manual_probe est automatiquement chargé.
    
 
    MANUAL_PROBE
    
@@ -5049,12 +5143,6 @@ section is enabled.
    
 
    La commande suivante est disponible lorsqu'une section mcp4018 config est activée.
    
 
    SET_DIGIPOT
    
 
    SET_DIGIPOT DIGIPOT=config_name WIPER=<valeur> : Cette commande change la valeur actuelle du digipot. Cette valeur devrait typiquement être comprise entre 0.0 et 1.0, à moins qu'une 'échelle' soit définie dans la configuration. Lorsque 'scale' est défini, alors cette valeur doit être comprise entre 0.0 et 'scale'.
    
-
    [led]
    
-
    La commande suivante est disponible lorsque l'une des sections led config est activée.
    
-
    SET_LED
    
-
    SET_LED LED=<nom_de_la_configuration> RED=<valeur> GREEN=<valeur> BLUE=<valeur> WHITE=<valeur> [INDEX=<index>] [TRANSMIT=0] [SYNC=1] : Ceci définit la sortie de la LED. Chaque <valeur> de couleur doit être comprise entre 0.0 et 1.0. L'option WHITE n'est valable que pour les LEDs RGBW. Si la LED supporte plusieurs puces dans une chaîne, on peut spécifier INDEX pour modifier la couleur de la seule puce donnée (1 pour la première puce, 2 pour la seconde, etc.). Si INDEX n'est pas spécifié, alors toutes les LEDs de la chaîne seront réglées sur la couleur fournie. Si TRANSMIT=0 est spécifié, le changement de couleur ne sera effectué que lors de la prochaine commande SET_LED qui ne spécifie pas TRANSMIT=0 ; cela peut être utile en combinaison avec le paramètre INDEX pour effectuer plusieurs mises à jour dans une chaîne. Par défaut, la commande SET_LED synchronisera ses changements avec les autres commandes gcode en cours. Cela peut conduire à un comportement indésirable si les LEDs sont réglées alors que l'imprimante n'imprime pas, car cela réinitialisera le délai d'inactivité. Si un timing précis n'est pas nécessaire, le paramètre optionnel SYNC=0 peut être spécifié pour appliquer les changements sans réinitialiser le délai d'inactivité.
    
-
    SET_LED_TEMPLATE
    
-
    SET_LED_TEMPLATE LED=<nom_de_la_led> TEMPLATE=<nom_du_modèle> [<param_x>=<literal>] [INDEX=<index>] : Attribue un modèle d'affichage à une LED donnée. Par exemple, si l'on définit une section de configuration [display_template my_led_template], on peut affecter TEMPLATE=my_led_template ici. Le modèle d'affichage doit produire une chaîne de caractères séparée par des virgules contenant quatre nombres à virgule flottante correspondant aux paramètres de couleur rouge, vert, bleu et blanc. Le modèle sera continuellement évalué et la LED sera automatiquement réglée sur les couleurs résultantes. On peut définir des paramètres display_template à utiliser pendant l'évaluation du modèle (les paramètres seront analysés comme des littéraux Python). Si INDEX n'est pas spécifié, alors toutes les puces dans la chaîne de la LED seront réglées sur le modèle, sinon seule la puce avec l'index donné sera mise à jour. Si TEMPLATE est une chaîne vide, cette commande effacera tout modèle précédent assigné à la LED (on peut alors utiliser les commandes SET_LED pour gérer les paramètres de couleur de la LED).
    
 
    [output_pin]
    
 
    La commande suivante est disponible lorsqu'une section output_pin config est activée.
    
 
    SET_PIN
    
@@ -5077,10 +5165,6 @@ section is enabled.
    
 
    PALETTE_CUT : Cette commande demande à Palette 2 de couper le filament actuellement chargé dans le noyau de jonction.
    
 
    PALETTE_SMART_LOAD
    
 
    PALETTE_SMART_LOAD : cette commande initialise la séquence de chargement intelligente sur Palette 2. Le filament est chargé automatiquement en l’extrudant sur la distance calibrée sur l’appareil pour l’imprimante, et l'indique à Palette 2 une fois le chargement terminé. Cette commande revient à appuyer sur Smart Load directement sur l’écran Palette 2 une fois l'insertion du filament faite.
    
-
    [pid_calibrate]
    
-
    Le module pid_calibrate est automatiquement chargé si un chauffage est défini dans le fichier de configuration.
    
-
    PID_CALIBRATE
    
-
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]: Effectuer un test d’étalonnage PID. Le chauffage demandé sera activé jusqu’à ce que la température définie soit atteinte, il s'éteindra et se rallumera durant plusieurs cycles. Si le paramètre WRITE_FILE est activé, le fichier /tmp/heattest.txt sera créé avec un journal de tous les échantillons de température mesurés pendant le test.
    
 
    [pause_resume]
    
 
    Les commandes suivantes sont disponibles lorsque la section pause_resume config est activée :
    
 
    PAUSE
    
@@ -5091,6 +5175,10 @@ section is enabled.
    
 
    CLEAR_PAUSE: Supprime la mise en pause actuelle sans reprendre l'impression. Ceci est utile si l'on décide d'interrompre une impression après une PAUSE. Il est recommandé d'ajouter ceci à votre gcode de démarrage pour s'assurer que l'état de pause est réinitialisé pour chaque impression.
    
 
    CANCEL_PRINT
    
 
    CANCEL_PRINT: Annule l'impression en cours.
    
+
    [pid_calibrate]
    
+
    Le module pid_calibrate est automatiquement chargé si un chauffage est défini dans le fichier de configuration.
    
+
    PID_CALIBRATE
    
+
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]: Effectuer un test d’étalonnage PID. Le chauffage demandé sera activé jusqu’à ce que la température définie soit atteinte, il s'éteindra et se rallumera durant plusieurs cycles. Si le paramètre WRITE_FILE est activé, le fichier /tmp/heattest.txt sera créé avec un journal de tous les échantillons de température mesurés pendant le test.
    
 
 
    Le module print_stats est automatiquement chargé.
    
 
    SET_PRINT_STATS_INFO
    
@@ -5158,7 +5246,7 @@ section is enabled.
    
 
    [save_variables]
    
 
    La commande suivante est activée si une section save_variables config a été activée.
    
 
    SAVE_VARIABLE
    
-
    SAVE_VARIABLE VARIABLE=<nom> VALUE=<valeur> : Enregistre la variable sur le disque afin qu'elle puisse être utilisée lors des redémarrages. Toutes les variables enregistrées sont chargées dans le dict printer.save_variables.variables au démarrage et peuvent être utilisées dans des macros gcode. La VALEUR fournie est analysée comme un littéral Python.
    
+
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>: Saves the variable to disk so that it can be used across restarts. The VARIABLE must be lowercase. All stored variables are loaded into the printer.save_variables.variables dict at startup and can be used in gcode macros. The provided VALUE is parsed as a Python literal.
    
 
    [screws_tilt_adjust]
    
 
    Les commandes suivantes sont disponibles lorsque la section de configuration screws_tilt_adjust est activée (voir également le guide du nivelage manuel).
    
 
    SCREWS_TILT_CALCULATE
    
@@ -5199,6 +5287,18 @@ section is enabled.
    
 
    La commande suivante est disponible lorsqu'une section temperature_fan config est activée.
    
 
    SET_TEMPERATURE_FAN_TARGET
    
 
    SET_TEMPERATURE_FAN_TARGET temperature_fan=<nom_du_ventilateur_température> [target=<température_cible>] [min_speed=<vitesse_min>] [max_speed=<vitesse_max>] : Définit la température cible d'un ventilateur_température. Si une cible n'est pas fournie, elle est fixée à la température spécifiée dans le fichier de configuration. Si les vitesses ne sont pas fournies, aucun changement n'est appliqué.
    
+
    [temperature_probe]
    
+
    The following commands are available when a temperature_probe config section is enabled.
    
+
    TEMPERATURE_PROBE_CALIBRATE
    
+
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
+
    TEMPERATURE_PROBE_NEXT
    
+
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
+
    TEMPERATURE_PROBE_COMPLETE:
    
+
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
+
    ABORT
    
+
    ABORT: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.
    
+
    TEMPERATURE_PROBE_ENABLE
    
+
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
    [tmcXXXX]
    
 
    Les commandes suivantes sont disponibles lorsque l'une des sections tmcXXXX config est activée.
    
 
    DUMP_TMC
    
@@ -5246,18 +5346,6 @@ section is enabled.
    
 
    Les commandes suivantes sont disponibles lorsque la section z_tilt config est activée.
    
 
    Z_TILT_ADJUST
    
 
    Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]: 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 RETRIES, RETRY_TOLERANCE, and HORIZONTAL_MOVE_Z values override those options specified in the config file.
    
-
    [temperature_probe]
    
-
    The following commands are available when a temperature_probe config section is enabled.
    
-
    TEMPERATURE_PROBE_CALIBRATE
    
-
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
-
    TEMPERATURE_PROBE_NEXT
    
-
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
-
    TEMPERATURE_PROBE_COMPLETE:
    
-
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
-
    ABORT
    
-
    ABORT: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.
    
-
    TEMPERATURE_PROBE_ENABLE
    
-
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
               
             
diff --git a/fr/Hall_Filament_Width_Sensor.html b/fr/Hall_Filament_Width_Sensor.html
index efb7025e9..1b0f42922 100644
--- a/fr/Hall_Filament_Width_Sensor.html
+++ b/fr/Hall_Filament_Width_Sensor.html
@@ -1357,8 +1357,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Installation.html b/fr/Installation.html
index 01030079e..1253b7c39 100644
--- a/fr/Installation.html
+++ b/fr/Installation.html
@@ -1366,8 +1366,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
 
 
    Installation
    
-
    These instructions assume the software will run on a linux based host running a Klipper compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian based Linux device be used as the host machine (see the FAQ for other options).
    
-
    For the purposes of these instructions host relates to the Linux device and mcu relates to the printboard. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
+
    These instructions assume the software will run on a Linux-based host running a Klipper-compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian-based Linux device be used as the host machine (see the FAQ for other options).
    
+
    For the purposes of these instructions, host relates to the Linux device and mcu relates to the printer board. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
 
    Obtenir un fichier de configuration de Klipper
    
 
    Most Klipper settings are determined by a "printer configuration file" printer.cfg, that will be stored on the host. An appropriate configuration file can often be found by looking in the Klipper config directory for a file starting with a "printer-" prefix that corresponds to the target printer. The Klipper configuration file contains technical information about the printer that will be needed during the installation.
    
 
    S'il n'y a pas de fichier de configuration d'imprimante approprié dans le répertoire des configurations de Klipper, essayez de rechercher le site Web du fabricant de l'imprimante pour voir s'il y a un fichier de configuration Klipper approprié.
    
@@ -1493,13 +1493,13 @@
 
    Currently the best choices are front ends that retrieve information through the Moonraker web API and there is also the option to use Octoprint to control Klipper.
    
 
    The choice is up to the user on what to use, but the underlying Klipper is the same in all cases. We encourage users to research the options available and make an informed decision.
    
 
    Obtaining an OS image for SBC's
    
-
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manafactures of these SBC boards also provide their own Klipper-centric images.
    
-
    The two main Moonraker based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi varianta.
    
+
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manufacturers of these SBC boards also provide their own Klipper-centric images.
    
+
    The two main Moonraker-based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi variants.
    
 
    Fluidd can be installed via KIAUH(Klipper Install And Update Helper), which is explained below and is a 3rd party installer for all things Klipper.
    
 
    OctoPrint can be installed via the popular OctoPi image or via KIAUH, this process is explained in 
    
 
    Installing via KIAUH
    
-
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of a x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions working and even mask access to some print boards.
    
-
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
+
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of an x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions from working and even mask access to some printer boards.
    
+
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux-based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
 
    Compilation et flashage du micro-contrôleur
    
 
    To compile the micro-controller code, start by running these commands on your host device:
    
 
    cd ~/klipper/
@@ -1510,7 +1510,7 @@ make menuconfig
 
    make
 
    
 
-
    Si les commentaires au haut de printer configuration file décrive des étapes pour le "flashing" de l'image finale sur la carte de contrôle de l'imprimante alors suivez ces étapes puis procédez à configuring OctoPrint.
    
+
    If the comments at the top of the printer configuration file describe custom steps for "flashing" the final image to the printer control board, then follow those steps and then proceed to configuring OctoPrint.
    
 
    Sinon, les étapes suivantes sont souvent utilisées pour le "flash" de la carte de contrôle de l'imprimante. D'abord, il est nécessaire de déterminer le port série connecté au micro-contrôleur. Lancez ceci :
    
 
    ls /dev/serial/by-id/*
 
    
@@ -1520,8 +1520,8 @@ make menuconfig
 
    
 
 
    It's common for each printer to have its own unique serial port name. This unique name will be used when flashing the micro-controller. It's possible there may be multiple lines in the above output - if so, choose the line corresponding to the micro-controller. If many items are listed and the choice is ambiguous, unplug the board and run the command again, the missing item will be your print board(see the FAQ for more information).
    
-
    For common micro-controllers with STM32 or clone chips, LPC chips and others it is usual that these need an initial Klipper flash via SD card.
    
-
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occuring.
    
+
    For common micro-controllers with STM32 or clone chips, LPC chips and others, it is usual that these need an initial Klipper flash via SD card.
    
+
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring.
    
 
    For common micro-controllers using Atmega chips, for example the 2560, the code can be flashed with something similar to:
    
 
    sudo service klipper stop
 make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
@@ -1538,9 +1538,9 @@ sudo service klipper start
 
    It is important to note that RP2040 chips may need to be put into Boot mode before this operation.
    
 
    Configuration de Klipper
    
 
    The next step is to copy the printer configuration file to the host.
    
-
    Arguably the easiest way to set the Klipper configuration file is using the built in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
+
    Arguably the easiest way to set the Klipper configuration file is using the built-in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
 
    Another option is to use a desktop editor that supports editing files over the "scp" and/or "sftp" protocols. There are freely available tools that support this (eg, Notepad++, WinSCP, and Cyberduck). Load the printer config file in the editor and then save it as a file named "printer.cfg" in the home directory of the pi user (ie, /home/pi/printer.cfg).
    
-
    Alternatively, one can also copy and edit the file directly on the host via ssh. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
+
    Alternatively, one can also copy and edit the file directly on the host via SSH. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
 
    cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
 nano ~/printer.cfg
 
    
@@ -1558,9 +1558,9 @@ nano ~/printer.cfg
 serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
 
    
 
-
    After creating and editing the file it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
+
    After creating and editing the file, it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report that the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
 
    Lors de la personnalisation du fichier de configuration de l'imprimante, il n'est pas rare que Klipper signale une erreur de configuration. Si une erreur se produit, apportez les corrections nécessaires au fichier de configuration de l'imprimante et lancez "restart" jusqu'à ce que "status" indique que l'imprimante est prête.
    
-
    Klipper reports error messages via the command console and via pop up in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located in ~/printer_data/logs this is named klippy.log
    
+
    Klipper reports error messages via the command console and pop-ups in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located at ~/printer_data/logs/klippy.log.
    
 
    Une fois que Klipper a signalé que l'imprimante est prête, passez au document de vérification de la configuration pour effectuer les vérifications de base sur les définitions du fichier de configuration. Pour plus d'informations, consultez la référence de documentation  principale pour plus d'informations.
    
 
               
diff --git a/fr/Kinematics.html b/fr/Kinematics.html
index ab545dbd7..9e66dd73d 100644
--- a/fr/Kinematics.html
+++ b/fr/Kinematics.html
@@ -1411,8 +1411,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Load_Cell.html b/fr/Load_Cell.html
new file mode 100644
index 000000000..b1305607a
--- /dev/null
+++ b/fr/Load_Cell.html
@@ -0,0 +1,1635 @@
+
+
+
+  
+    
+      
+      
+      
+      
+      
+      
+      
+    
+    
+      
+        Load Cells - Documentation Klipper
+      
+    
+    
+      
+      
+        
+        
+        
+      
+    
+    
+    
+      
+        
+        
+        
+        
+      
+    
+    
+      
+    
+    
+    
+      
+  
+
+
+  
+  
+
+
+  
+  
+
+
+    
+    
+  
+  
+  
+    
+    
+      
+    
+    
+    
+    
+    
+  
+    
+    
+      
+    
+    
+    
+    
+    
+    
    
+      
+    
    
+    
+    
+      
+
+
    
+  
+  
+
    
+    
+    
    
+      
+      
+        
+          
+        
+      
+      
    
+        
    
+          
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+
+                  
    
+                
    
+              
    
+            
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+                  
    
+                
    
+              
    
+            
+          
+          
    
+            
    
+              
+                
+
+  
+
+
+
+
    Load Cells
    
+
    This document describes Klipper's support for load cells. Basic load cell functionality can be used to read force data and to weigh things like filament. A calibrated force sensor is an important part of a load cell based probe.
    
+
+
+
    Using LOAD_CELL_DIAGNOSTIC
    
+
    When you first connect a load cell its good practice to check for issues by running LOAD_CELL_DIAGNOSTIC. This tool collects 10 seconds of data from the load cell and resport statistics:
    
+
    $ LOAD_CELL_DIAGNOSTIC
+// Collecting load cell data for 10 seconds...
+// Samples Collected: 3211
+// Measured samples per second: 332.0
+// Good samples: 3211, Saturated samples: 0, Unique values: 900
+// Sample range: [4.01% to 4.02%]
+// Sample range / sensor capacity: 0.00524%
+
    
+
+
    Things you can check with this data:
    
+
      
+
    • The configured sample rate of the sensor should be close to the 'Measured samples per second' value. If it is not you may have a configuration or wiring issue.
      • 
+
    • 'Saturated samples' should be 0. If you have saturated samples it means the load sell is seeing more force than it can measure.
      • 
+
    • 'Unique values' should be a large percentage of the 'Samples Collected' value. If 'Unique values' is 1 it is very likely a wiring issue.
      • 
+
    • Tap or push on the sensor while LOAD_CELL_DIAGNOSTIC runs. If things are working correctly ths should increase the 'Sample range'.
      • 
+
    
+
    Calibrating a Load Cell
    
+
    Load cells are calibrated using the LOAD_CELL_CALIBRATE command. This is an interactive calibration utility that walks you though a 3 step process:
    
+
      
+
    1. First use the TARE command to establish the zero force value. This is the reference_tare_counts config value.
      2. 
+
    2. Next you apply a known load or force to the load cell and run the CALIBRATE GRAMS=nnn command. From this the counts_per_gram value is calculated. See the next section for some suggestions on how to do this.
      3. 
+
    3. Finally, use the ACCEPT command to save the results.
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    Applying a Known Force or Load
    
+
    The CALIBRATE GRAMS=nnn step can be accomplished in a number of ways. If your load cell is under a platform like a bed or filament holder it might be easiest to put a known mass on the platform. E.g. you could use a couple of 1KG filament spools.
    
+
    If your load cell is in the printer's toolhead a different approach is easier. Put a digital scale on the printers bed and gently lower the toolhead onto the scale (or raise the bed into the toolhead if your bed moves). You may be able to do this using the FORCE_MOVE command. But more likely you will have to manually moving the z axis with the motors off until the toolhead presses on the scale.
    
+
    A good calibration force would ideally be a large percentage of the load cell's rated capacity. E.g. if you have a 5Kg load cell you would ideally calibrate it with a 5kg mass. This might work well with under-bed sensors that have to support a lot of weight. For toolhead probes this may not be a load that your printer bed or toolhead can tolerate without damage. Do try to use at least 1Kg of force, most printers should tolerate this without issue.
    
+
    When calibrating make careful note of the values reported:
    
+
    $ CALIBRATE GRAMS=555
+// Calibration value: -2.78% (-59803108), Counts/gram: 73039.78739,
+Total capacity: +/- 29.14Kg
+
    
+
+
    The Total capacity should be close to the theoretical rating of the load cell based on the sensor's capacity. If it is much larger you could have used a higher gain setting in the sensor or a more sensitive load cell. This isn't as critical for 32bit and 24bit sensors but is much more critical for low bit width sensors.
    
+
    Reading Force Data
    
+
    Force data can be read with a GCode command:
    
+
    LOAD_CELL_READ
+// 10.6g (1.94%)
+
    
+
+
    Data is also continuously read and can be consumed from the load_cell printer object in a macro:
    
+
    {% set grams = printer.load_cell.force_g %}
+
    
+
+
    This provides an average force over the last 1 second, similar to how temperature sensors work.
    
+
    Taring a Load Cell
    
+
    Taring, sometimes called zeroing, sets the current weight reported by the load_cell to 0. This is useful for measuring relative to a known weight. e.g. when measuring a filament spool, using LOAD_CELL_TARE sets the weight to 0. Then as filament is printed the load_cell will report the weight of the filament used.
    
+
    LOAD_CELL_TARE
+// Load cell tare value: 5.32% (445903)
+
    
+
+
    The current tare value is reported in the printers status and can be read in a macro:
    
+
    {% set tare_counts = printer.load_cell.tare_counts %}
+
    
+
+              
+            
    
+          
    
+        
    
+        
+          
+            
+            Retour en haut de la page
+          
+        
+      
    
+      
+        
+      
+    
    
+    
    
+      
    
+    
    
+    
+    
+    
+      
+      
+    
+  
+
\ No newline at end of file
diff --git a/fr/MCU_Commands.html b/fr/MCU_Commands.html
index 05f6b59c3..150670f45 100644
--- a/fr/MCU_Commands.html
+++ b/fr/MCU_Commands.html
@@ -1383,8 +1383,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Manual_Level.html b/fr/Manual_Level.html
index c832ba1ef..47a0307aa 100644
--- a/fr/Manual_Level.html
+++ b/fr/Manual_Level.html
@@ -1358,8 +1358,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/fr/Measuring_Resonances.html b/fr/Measuring_Resonances.html
index 09931f744..683f855ec 100644
--- a/fr/Measuring_Resonances.html
+++ b/fr/Measuring_Resonances.html
@@ -838,11 +838,11 @@
       
    
 
-
    A tesztet utoljára az f6718291 kötelezően futtattuk a arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 gcc verzióval Raspberry Pi Pico és Pico 2 lapkákon.
    
+
    The test was last run on commit 14c105b8 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.
    
 
@@ -2226,11 +2226,11 @@ finalize_config crc=0
 
-
+
-
+
    
 
 
    
 
    
 1 léptető53
 
    
 
    
 3 léptető2214
 
    
     
 
    
@@ -2252,7 +2252,7 @@ finalize_config crc=0
 
 
 
-
    (*) Megjegyzendő, hogy a bejelentett rp2040 tickek egy 12Mhz-es ütemező időzítőhöz viszonyítva vannak, és nem felelnek meg a 125Mhz-es belső ARM-feldolgozási sebességnek. Várhatóan 5 ütemezési tick megfelel ~47 ARM magciklusnak, 22 ütemezési tick pedig ~224 ARM magciklusnak.
    
+
    (*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 200Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 ARM core cycles.
    
 
    Linux MCU lépésszám referencia
    
 
    A következő konfigurációs sorrendet egy Raspberry Pi esetében használjuk:
    
 
    allocate_oids count=3
diff --git a/hu/Bootloader_Entry.html b/hu/Bootloader_Entry.html
index c2ea5aee6..e1f0da4c3 100644
--- a/hu/Bootloader_Entry.html
+++ b/hu/Bootloader_Entry.html
@@ -1429,8 +1429,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Bootloaders.html b/hu/Bootloaders.html
index e64b28c93..b2524ca03 100644
--- a/hu/Bootloaders.html
+++ b/hu/Bootloaders.html
@@ -1501,8 +1501,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/CANBUS.html b/hu/CANBUS.html
index 0435621c7..d6b9751f7 100644
--- a/hu/CANBUS.html
+++ b/hu/CANBUS.html
@@ -1371,8 +1371,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1549,6 +1549,7 @@ iface can0 can static
 
 
 
      
+
    • It is only valid to use USB to CAN bridge mode if there is a functioning CAN bus with at least one other node available (in addition to the bridge node itself). Use a standard USB configuration if the goal is to communicate only with the single USB device. Using USB to CAN bridge mode without a fully functioning CAN bus (including terminating resistors and an additional node) may result in sporadic errors even when communicating with the bridge node.
      • 
 
    • Az USB-CAN hídlap nem jelenik meg USB soros eszközként, nem jelenik meg az ls /dev/serial/by-id futtatásakor, és nem konfigurálható a Klipper printer.cfg fájljában a serial: paraméterrel. A hídlap "USB CAN adapter"-ként jelenik meg, és a printer.cfg fájlban CAN node-ként van konfigurálva .
      • 
 
    
 
    Tippek a hibaelhárításhoz
    
diff --git a/hu/CANBUS_Troubleshooting.html b/hu/CANBUS_Troubleshooting.html
index db4ecdce1..1c2dc10b8 100644
--- a/hu/CANBUS_Troubleshooting.html
+++ b/hu/CANBUS_Troubleshooting.html
@@ -1284,6 +1284,13 @@
     Használj megfelelő txqueuelen beállítást
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1370,8 +1377,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1444,6 +1451,13 @@
     Használj megfelelő txqueuelen beállítást
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1500,12 +1514,16 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    Ellenőrizd, hogy a CAN-busz kábelezésén lévő összes csatlakozó és vezetékrögzítő jól van rögzítve. A nyomtatófej mozgása megrázhatja a CAN-busz vezetékeit, ami egy rosszul rögzített vagy rögzítetlen csatlakozó miatt időszakos kommunikációs hibákat okozhat.
    
 
    A bytes_invalid számláló növelésének ellenőrzése
    
 
    A Klipper naplófájl másodpercenként egyszer jelent egy Stats sort, amikor a nyomtató aktív. Ezek a "Stats" sorok minden mikrokontroller esetében tartalmaznak egy bytes_invalid számlálót. Ennek a számlálónak nem szabad növekednie a nyomtató normál működése során (normális, hogy a számláló nem nulla az újraindítás után, és nem jelent gondot, ha a számláló havonta egyszer növekszik). Ha ez a számláló egy CAN-buszos mikrovezérlőn normál nyomtatás közben növekszik (néhány óránként vagy gyakrabban), akkor az súlyos problémára utal.
    
-
    A bytes_invalid növekedése egy CAN-busz kapcsolaton a CAN-buszon lévő átrendezett üzenetek tünete. Az újrarendezett üzeneteknek két ismert oka van:
    
-
      
-
    1. Az USB CAN-adapterek népszerű candlight_firmware-jének régi verzióiban volt egy hiba, amely átrendezett üzeneteket okozhatott. Ha ilyen firmware-t futtató USB CAN adaptert használsz, akkor mindenképpen frissítsd a legújabb firmware-re, ha a bytes_invalid növekedését észleled.
      2. 
-
    2. Néhány beágyazott eszközökhöz készült Linux kernelről ismert, hogy átrendezi a CAN-busz üzeneteket. Szükség lehet egy alternatív Linux kernel használatára, vagy olyan alternatív hardverek használatára, amelyek támogatják a mainstream Linux kerneleket, amelyek nem mutatják ezt a problémát.
      3. 
-
    
-
    Az átrendezett üzenetek súlyos problémát jelentenek, amelyet orvosolni kell. Ez instabil viselkedést eredményez, és zavaró hibákhoz vezethet a nyomtatás bármelyik részénél.
    
+
    Incrementing bytes_invalid on a CAN bus connection is a symptom of reordered messages on the CAN bus. If seen, make sure to:
    
+
      
+
    • Use a Linux kernel version 6.6.0 or later.
      • 
+
    • If using a USB-to-CANBUS adapter running candlelight firmware, use v2.0 or later of candleLight_fw.
      • 
+
    • If using Klipper's USB-to-CANBUS bridge mode, make sure the bridge node is flashed with Klipper v0.12.0 or later.
      • 
+
    
+
    Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print. An incrementing bytes_invalid is not caused by wiring or similar hardware issues and can only be fixed by identifying and updating the faulty software.
    
+
    Older versions of the Linux kernel had a bug in the gs_usb canbus driver code that could cause reordered canbus packets. The issue is thought to be fixed in Linux commit 24bc41b4 which was released in v6.6.0. In some cases, older Linux versions may not show the problem (due to how hardware interrupts are configured), however if problems are seen the recommended solution is to upgrade to a newer kernel.
    
+
    Older versions of candlelight firmware could reorder canbus packets, and the issue is thought to be fixed in candlelight_fw commit 8b3a7b45.
    
+
    Older versions of Klipper's USB-to-CANBUS bridge code could incorrectly drop canbus messages. This is not as severe as reordering messages, but it should still be fixed. It is thought to be fixed with Klipper PR #6175.
    
 
    Használj megfelelő txqueuelen beállítást
    
 
    A Klipper kód a Linux kernelt használja a CAN-busz forgalom kezelésére. Alapértelmezés szerint a kernel csak 10 CAN átviteli csomagot állít sorba. Ajánlott a can0 eszköz konfigurálása txqueuelen 128-val, hogy növeld ezt a méretet.
    
 
    Ha a Klipper továbbít egy csomagot, és a Linux betöltötte az összes átviteli várólistát, akkor a Linux eldobja a csomagot, és a Klipper naplójában a következő üzenetek jelennek meg:
    
@@ -1517,6 +1535,10 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    Az aktuális várólista méretét a Linux ip link show can0 parancs futtatásával ellenőrizhetjük. A parancsnak egy csomó szöveget kell kiírnia, köztük a qlen 128 szalagot. Ha valami olyasmit látunk, mint qlen 10, akkor az azt jelzi, hogy a CAN-eszköz nincs megfelelően konfigurálva.
    
 
    Nem ajánlott 128-nál lényegesen nagyobb txqueuelen értéket használni. Egy 1000000-ós frekvencián futó CAN-buszon egy CAN-csomag továbbítása általában körülbelül 120 másodpercig tart. Így egy 128 csomagból álló sor valószínűleg 15-20 ms-ig tart, amíg a sor kiürül. Egy lényegesen nagyobb várólista az üzenetek átfutási idejében túlzott kiugrásokat okozhat, ami helyrehozhatatlan hibákhoz vezethet. Másképp fogalmazva, a Klipper alkalmazás újraküldési rendszere robusztusabb, ha nem kell megvárnia, hogy a Linuxnak ki kelljen ürítenie egy túl nagy, esetleg elavult adatokat tartalmazó várólistát. Ez analóg a bufferbloat problémájával az internetes útválasztókon.
    
 
    Normál körülmények között a Klipper MCU-nként ~25 várólistahelyet használhat - jellemzően csak az újratovábbítások során használ több helyet. (Konkrétan, a Klipper gazdagép legfeljebb 192 bájtot küldhet minden Klipper MCU-nak, mielőtt nyugtát kapna az adott MCU-tól). Ha egy CAN-buszon 5 vagy több Klipper MCU van, akkor szükséges lehet a txqueuelen értéket a 128-as ajánlott érték fölé emelni. A fentiekhez hasonlóan azonban az új érték kiválasztásakor óvatosan kell eljárni, hogy elkerülhető legyen a túlzott körutazási késleltetés.
    
+
    Use canbus_query.py only to identify nodes never previously seen
    
+
    It is only valid to use the canbus_query.py tool to identify micro-controllers that have never been previously identified. Once all nodes on a bus are identified, record the resulting uuids in the printer.cfg, and avoid running the tool unnecessarily.
    
+
    The tool is implemented using a low-level mechanism that can cause nodes to internally observe bus errors. These internal errors may result in communication interruptions and may result is some nodes disconnecting from the bus.
    
+
    It is not valid to use the tool to "ping" if a node is connected. Do not run the tool during an active print.
    
 
    Candump naplók beszerzése
    
 
    A mikrokontrollerhez küldött és onnan érkező CAN-busz üzeneteket a Linux kernel kezeli. Lehetőség van arra, hogy ezeket az üzeneteket a kernelből hibakeresés céljából rögzítsük. Ezen üzenetek naplózása hasznos lehet a diagnosztikában.
    
 
    A Linux can-utils eszköz biztosítja a rögzítő szoftvert. Ezt általában a következő futtatásával telepíthetjük a gépre:
    
diff --git a/hu/CANBUS_protocol.html b/hu/CANBUS_protocol.html
index 012e2c22b..ebccdc68b 100644
--- a/hu/CANBUS_protocol.html
+++ b/hu/CANBUS_protocol.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/CONTRIBUTING.html b/hu/CONTRIBUTING.html
index aa47551b6..5ce47d01d 100644
--- a/hu/CONTRIBUTING.html
+++ b/hu/CONTRIBUTING.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Code_Overview.html b/hu/Code_Overview.html
index 5fde94d6f..dd50046e2 100644
--- a/hu/Code_Overview.html
+++ b/hu/Code_Overview.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Command_Templates.html b/hu/Command_Templates.html
index 3915788c5..14f5bafdf 100644
--- a/hu/Command_Templates.html
+++ b/hu/Command_Templates.html
@@ -1421,8 +1421,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Config_Changes.html b/hu/Config_Changes.html
index 3c39188af..ba8d12c4a 100644
--- a/hu/Config_Changes.html
+++ b/hu/Config_Changes.html
@@ -1327,8 +1327,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1410,6 +1410,12 @@
 
    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.
    
 
    A dokumentumban szereplő valamennyi dátum hozzávetőleges.
    
 
    Változások
    
+
    20250428: The maximum cycle_time for pwm [output_pin], [pwm_cycle_time], [pwm_tool], and similar config sections is now 3 seconds (reduced from 5 seconds). The maximum_mcu_duration in [pwm_tool] is now also 3 seconds.
    
+
    20250418: The manual_stepper STOP_ON_ENDSTOP feature may now take less time to complete. Previously, the command would wait the entire time the move could possibly take even if the endstop triggered earlier. Now, the command finishes shortly after the endstop trigger.
    
+
    20250417: SPI devices using "software SPI" are now rate limited. Previously, the spi_speed in the config was ignored and the transmission speed was only limited by the processing speed of the micro-controller. Now, speeds are limited by the spi_speed config parameter (actual hardware speeds are likely to be lower than the configured value due to software overhead).
    
+
    20250411: Klipper v0.13.0 released.
    
+
    20250308: The AUTO parameter of the AXIS_TWIST_COMPENSATION_CALIBRATE command has been removed.
    
+
    20250131: Option VARIABLE=<name> in SAVE_VARIABLE requires lowercase value. For example, extruder instead of mixedcase Extruder or uppercase EXTRUDER. Using any uppercase letter will raise an error.
    
 
    20241203: A rezonancia tesztet megváltoztattuk, hogy lassú, pásztázó mozdulatokat is tartalmazzon. Ez a változtatás megköveteli, hogy a vizsgálati pontoknak legyen némi távolsága az X/Y síkban (az alapértelmezett beállítások használata esetén +/- 30 mm távolság elegendő a vizsgálati pontoktól). Az új tesztnek általában pontosabb és megbízhatóbb teszteredményeket kell produkálnia. Szükség esetén azonban a korábbi tesztelési viselkedés visszaállítható a sweeping_period: 0 és accel_per_hz: 75 beállításokat a [resonance_tester] konfigurációs szakaszhoz.
    
 
    20241201: Egyes esetekben a Klipper figyelmen kívül hagyhatta a hagyományos G-kód-os parancsban a vezető karaktereket vagy szóközöket. Például a „99M123”-at „M123”-nak, az „M 321”-et pedig „M321”-nek értelmezhette. A Klipper mostantól ezeket az eseteket „Ismeretlen parancs” figyelmeztetéssel jelzi.
    
 
    20241112: A CHIPS=<chip_name> opció a TEST_RESONANCES és a SHAPER_CALIBRATE műveletekben megköveteli a gyorsítóchipek teljes nevének megadását. Például adxl345 rpi a rövid név - rpi helyett.
    
diff --git a/hu/Config_Reference.html b/hu/Config_Reference.html
index d11474d4f..ad3eef5cc 100644
--- a/hu/Config_Reference.html
+++ b/hu/Config_Reference.html
@@ -931,6 +931,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -1741,6 +1748,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -2600,8 +2614,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3053,6 +3067,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -3863,6 +3884,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -5303,6 +5331,22 @@ cs_pin:
 #   eredményeinek minőségét.
 
    • 
 
+
    [icm20948]
    
+
    Support for icm20948 accelerometers.
    
+
    [icm20948]
+#i2c_address:
+#   Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
+#i2c_mcu:
+#i2c_bus:
+#i2c_software_scl_pin:
+#i2c_software_sda_pin:
+#i2c_speed: 400000
+#   See the "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.
+
    
+
 
    [lis2dw]
    
 
    LIS2DW gyorsulásmérők támogatása.
    
 
    [lis2dw]
@@ -5647,26 +5691,25 @@ z_offset:
 
    Örvényáramú induktív szondák támogatása. Meghatározható ez a szakasz (szonda szakasz helyett), hogy engedélyezd ezt a szondát. További információkért lásd a parancshivatkozást.
    
 
    [probe_eddy_current my_eddy_probe]
 sensor_type: ldc1612
-#   Az örvényáram mérések elvégzésére használt érzékelő chip.
-#   Ezt a paramétert meg kell adni, és ldc1612-re kell állítani.
+#   The sensor chip used to perform eddy current measurements. This
+#   parameter must be provided and must be set to ldc1612.
+#frequency:
+#   The external crystal frequency (in Hz) of the LDC1612 chip.
+#   The default is 12000000.
 #intb_pin:
-
-#   MCU gpio tű csatlakoztatva az ldc1612 érzékelő INTB tűjéhez
-#   (ha van). Az alapértelmezett beállítás szerint az INTB tű
-#   nem használható.
-
+#   MCU gpio pin connected to the ldc1612 sensor's INTB pin (if
+#   available). The default is to not use the INTB pin.
 #z_offset:
-#   A fúvóka és az ágy közötti névleges távolság (mm-ben),
-#   amelynél a mérési kísérletnek meg kell állnia.
-#   Ezt a paramétert meg kell adni.
+#   The nominal distance (in mm) between the nozzle and bed that a
+#   probing attempt should stop at. This parameter must be provided.
 #i2c_address:
 #i2c_mcu:
 #i2c_bus:
 #i2c_software_scl_pin:
 #i2c_software_sda_pin:
 #i2c_speed:
-#   Az érzékelő chip I2C beállításai. A fenti paraméterek leírását
-#   lásd a "közös I2C beállítások" szakaszban.
+#   The i2c settings for the sensor chip. See the "common I2C
+#   settings" section for a description of the above parameters.
 #x_offset:
 #y_offset:
 #speed:
@@ -5676,8 +5719,7 @@ sensor_type: ldc1612
 #samples_result:
 #samples_tolerance:
 #samples_tolerance_retries:
-#   A paraméterekkel kapcsolatos információkért lásd a
-#   "szonda" című szakaszt.
+#   See the "probe" section for information on these parameters.
 
    
 
 
    [axis_twist_compensation]
    
@@ -6606,22 +6648,27 @@ pin:
 
    A G-kód végrehajtása, amikor egy gombot megnyomnak vagy elengednek (vagy amikor egy tű állapota megváltozik). A gomb állapotát a QUERY_BUTTON button=my_gcode_button segítségével ellenőrizhetjük.
    
 
    [gcode_button my_gcode_button]
 pin:
-#   Az a tű, amelyre a gomb csatlakozik. Ezt a paramétert meg kell adni.
+#   The pin on which the button is connected. This parameter must be
+#   provided.
 #analog_range:
-#   Két vesszővel elválasztott ellenállás (ohmban), amely meghatározza
-#   a gomb minimális és maximális ellenállási tartományát. Ha meg van
-#   adva az analog_range, akkor a lábnak analóg-képes tűnek kell lennie.
-#   Az alapértelmezett a digitális GPIO használata a gombhoz.
+#   Two comma separated resistances (in Ohms) specifying the minimum
+#   and maximum resistance range for the button. If analog_range is
+#   provided then the pin must be an analog capable pin. The default
+#   is to use digital gpio for the button.
 #analog_pullup_resistor:
-#   A felhúzási ellenállás (ohmban), ha az analog_range meg van adva.
-#   Az alapértelmezett érték 4700 ohm.
+#   The pullup resistance (in Ohms) when analog_range is specified.
+#   The default is 4700 ohms.
 #press_gcode:
-#   A gomb megnyomásakor végrehajtandó G-kód parancsok listája.
-#   A G-kód sablonok támogatottak. Ezt a paramétert meg kell adni.
+#   A list of G-Code commands to execute when the button is pressed.
+#   G-Code templates are supported. This parameter must be provided.
 #release_gcode:
-#   A gomb elengedésekor végrehajtandó G-kód parancsok listája.
-#   A G-kód sablonok támogatottak. Az alapértelmezés szerint nem
-#   futnak le parancsok a gombok felengedésekor.
+#   A list of G-Code commands to execute when the button is released.
+#   G-Code templates are supported. The default is to not run any
+#   commands on a button release.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   button gcode. If the button is pressed and released during this
+#   delay, the entire button press is ignored. Default is 0.
 
    
 
 
    [output_pin]
    
@@ -6716,59 +6763,56 @@ pins:
 
    TMC2130 motorvezérlő konfigurálása SPI-buszon keresztül. A funkció használatához definiáljon egy konfigurációs szekciót "tmc2130" előtaggal, amelyet a megfelelő léptető konfigurációs szekció neve követ (például "[tmc2130 stepper_x]").
    
 
    [tmc2130 stepper_x]
 cs_pin:
-#   A TMC2130 chip select vonalnak megfelelő tű. Ez a tű az
-#   SPI-üzenetek kezdetén alacsony értékre áll, és az üzenet
-#   befejezése után magas értékre emelkedik.
-#   Ezt a paramétert meg kell adni.
+#   The pin corresponding to the TMC2130 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.
 #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 True, engedélyezi a lépésinterpolációt (a meghajtó belsőleg 256
-#   mikrolépéses sebességgel lépked). Ez az interpoláció egy kis
-#   rendszerszintű pozícióeltérést eredményez - a részletekért lásd a
-#   TMC_Drivers.md fájlt. Az alapértelmezett érték True.
+#   If true, enable step interpolation (the driver will internally
+#   step at a rate of 256 micro-steps). This interpolation does
+#   introduce a small systemic positional deviation - see
+#   TMC_Drivers.md for details. 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.
 #sense_resistor: 0.110
-#   A motorérzékelő ellenállás ellenállása (ohmban).
-#   Az alapértelmezett érték 0,110 ohm.
+#   The resistance (in ohms) of the motor sense resistor. The default
+#   is 0.110 ohms.
 #stealthchop_threshold: 0
-#   A sebesség (mm/s-ban), amelyre a „stealthChop” küszöbértéket
-#   állítani kell. Ha be van állítva, a „stealthChop” üzemmód akkor lesz
-#   engedélyezve, ha a léptetőmotor sebessége ez alatt az érték alatt van.
-#   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. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. 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!
-#   Az alapértelmezett beállítá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
@@ -6786,14 +6830,13 @@ run_current:
 #driver_X3: 255
 #driver_START_SIN: 0
 #driver_START_SIN90: 247
-#   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.
+#   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.
 #driver_IHOLDDELAY: 8
 #driver_TPOWERDOWN: 0
 #driver_TBL: 1
@@ -6806,6 +6849,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 4
 #driver_PWM_AMPL: 128
+#driver_FREEWHEEL: 0
 #driver_SGT: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6813,62 +6857,59 @@ run_current:
 #driver_SEDN: 0
 #driver_SEIMIN: 0
 #driver_SFILT: 0
-#   Állítsd be az adott regisztert a TMC2130 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.
+#   Set the given register during the configuration of the TMC2130
+#   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 TMC2130 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 „tmc2130_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őpontot”.
-#   (Győződj meg róla, hogy a driver_SGT-t is megfelelő érzékenységi
-#   értékre állította be.) Az alapértelmezett beállítás nem engedélyezi
-#   az érzékelő nélküli kezdőpont felvételt.
+#   The micro-controller pin attached to one of the DIAG lines of the
+#   TMC2130 chip. Only a single diag pin should be specified. The pin
+#   is "active low" and is thus normally prefaced with "^!". Setting
+#   this creates a "tmc2130_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.
 
    
 
 
    [tmc2208]
    
 
    TMC2208 (vagy TMC2224) motorvezérlő konfigurálása egyvezetékes UART-on keresztül. A funkció használatához definiáljon egy konfigurációs részt "tmc2208" előtaggal, amelyet a megfelelő léptető konfigurációs rész neve követ (például "[tmc2208 stepper_x]").
    
 
    [tmc2208 stepper_x]
 uart_pin:
-#       A TMC2208 PDN_UART vonalhoz csatlakoztatott tű.
-#       Ezt a paramétert meg kell adni.
+#   The pin connected to the TMC2208 PDN_UART line. This parameter
+#   must be provided.
 #tx_pin:
-#       Ha külön vételi és adási vonalat használsz a meghajtóval
-#       való kommunikációhoz, akkor állítsd be az uart_pin paramétert
-#       a vételi lábra, és a tx_pin értéket az átviteli lábra.
-#       Az alapértelmezett az uart_pin használata mind
-#       az olvasáshoz, mind az íráshoz.
+#   If using separate receive and transmit lines to communicate with
+#   the driver then set uart_pin to the receive pin and tx_pin to the
+#   transmit pin. The default is to use uart_pin for both reading and
+#   writing.
 #select_pins:
-#       A tmc2208 UART elérése előtt beállítandó tűk vesszővel
-#       elválasztott listája. Ez hasznos lehet egy analóg mux
-#       konfigurálásához az UART kommunikációhoz.
-#       Az alapértelmezett az, hogy nem adunk meg érintkezőt.
+#   A comma separated list of pins to set prior to accessing the
+#   tmc2208 UART. This may be useful for configuring an analog mux for
+#   UART communication. The default is to not configure any pins.
 #interpolate: True
-#       Ha True, engedélyezett a lépésinterpoláció (az illesztőprogram
-#       belsőleg 256 mikrolépéses sebességgel léptet). Ez az interpoláció
-#       egy kis szisztémás pozícióeltérést vezet be – a részletekért lásd a
-#       TMC_Drivers.md fájlt. Az alapértelmezett érték True.
+#   If true, enable step interpolation (the driver will internally
+#   step at a rate of 256 micro-steps). This interpolation does
+#   introduce a small systemic positional deviation - see
+#   TMC_Drivers.md for details. The default is True.
 run_current:
-#       Az áramerősség (amper RMS-ben) a meghajtónak a léptető
-#       mozgása közbeni konfigurálásához. 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 az áramerősség (amper RMS-ben), amellyel az illesztőprogramot
-#       akkor kell használni, 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 az, hogy nem csökkentjük az áramerősséget.
-#sense_resistor: 0,110
-#       A motor érzékelő ellenállásának ellenállása (ohmban).
-#       Az alapértelmezett érték 0,110 ohm.
+#   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.
+#sense_resistor: 0.110
+#   The resistance (in ohms) of the motor sense resistor. The default
+#   is 0.110 ohms.
 #stealthchop_threshold: 0
-#       A sebesség (mm/s-ban), amelyre a "stealthChop" küszöbértéket
-#       be kell állítani. Ha be van állítva, a "stealthChop" mód engedélyezve
-#       lesz, ha a léptetőmotor sebessége ez az érték alatt van.
-#       Az alapértelmezett érték 0, ami letiltja a "stealthChop" mó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. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #driver_MULTISTEP_FILT: True
 #driver_IHOLDDELAY: 8
 #driver_TPOWERDOWN: 20
@@ -6883,10 +6924,11 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
-#       Állítsd be a megadott regisztert a TMC2208 chip konfigurációja során.
-#       Ez egyéni motorparaméterek beállítására használható.
-#       Az egyes paraméterek alapértelmezett értékei a paraméter
-#       neve mellett találhatók a fenti listában.
+#driver_FREEWHEEL: 0
+#   Set the given register during the configuration of the TMC2208
+#   chip. This may be used to set custom motor parameters. The
+#   defaults for each parameter are next to the parameter name in the
+#   above list.
 
    
 
 
    [tmc2209]
    
@@ -6900,21 +6942,18 @@ run_current:
 #hold_current:
 #sense_resistor: 0.110
 #stealthchop_threshold: 0
-#   A paraméterek definícióját lásd a „tmc2208” szakaszban.
+#   See the "tmc2208" section for the definition of these parameters.
 #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! Az alapértelmezett beállítá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.
 #uart_address:
-#   A TMC2209 chip címe az UART üzenetekhez (0 és 3 közötti egész szám).
-#   Ezt általában akkor használják, ha több TMC2209 chip van
-#   csatlakoztatva ugyanahhoz az UART tűhöz.
-#   Az alapértelmezett érték nulla.
+#   The address of the TMC2209 chip for UART messages (an integer
+#   between 0 and 3). This is typically used when multiple TMC2209
+#   chips are connected to the same UART pin. The default is zero.
 #driver_MULTISTEP_FILT: True
 #driver_IHOLDDELAY: 8
 #driver_TPOWERDOWN: 20
@@ -6929,25 +6968,25 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #driver_SGTHRS: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
 #driver_SEMAX: 0
 #driver_SEDN: 0
 #driver_SEIMIN: 0
-#   Állítsd be az adott regisztert a TMC2209 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.
+#   Set the given register during the configuration of the TMC2209
+#   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.
 #diag_pin:
-#   A TMC2209 chip DIAG vonalához csatlakoztatott mikrokontrollertű.
-#   A tű elé általában „^” kerül, hogy engedélyezze a pullupot.
-#   Ennek beállítása létrehoz egy „tmc2209_stepper_x:virtual_endstop”
-#   virtuális tűt, amely a stepper endstop_pin-jeként használható.
-#   Ez lehetővé teszi a „sensorless homing”-ot. (Ügyelj arra, hogy a
-#   driver_SGTHRS-t is megfelelő érzékenységi értékre állítsd be.)
-#   Az alapértelmezett beállítás nem engedélyezi az
-#   érzékelő nélküli kezdőpontot.
+#   The micro-controller pin attached to the DIAG line of the TMC2209
+#   chip. The pin is normally prefaced with "^" to enable a pullup.
+#   Setting this creates a "tmc2209_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_SGTHRS to
+#   an appropriate sensitivity value.) The default is to not enable
+#   sensorless homing.
 
    
 
 
    [tmc2660]
    
@@ -7057,8 +7096,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7152,54 +7192,54 @@ run_current:
 
    TMC5160 motorvezérlő konfigurálása SPI-buszon keresztül. A funkció használatához definiáljon egy konfigurációs szekciót "tmc5160" előtaggal, amelyet a megfelelő léptető konfigurációs szekció neve követ (például "[tmc5160 stepper_x]").
    
 
    [tmc5160 stepper_x]
 cs_pin:
-#   A TMC5160 chip select vonalának megfelelő tű. Ez a tű az
-#   SPI-üzenetek kezdetén 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 TMC5160 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.
 #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.
 #sense_resistor: 0.075
-#   A motorérzékelő ellenállás ellenállása (ohmban).
-#   Az alapértelmezett érték 0,075 ohm.
+#   The resistance (in ohms) of the motor sense resistor. The default
+#   is 0.075 ohms.
 #stealthchop_threshold: 0
-#   A sebesség (mm/s-ban), amelyre a „stealthChop” küszöbértéket
-#   állítani kell. Ha be van állítva, a „stealthChop” üzemmód akkor lesz
-#   engedélyezve, ha a léptetőmotor sebessége ez alatt az érték alatt van.
-#   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. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. 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 felvétel” használatban van, akkor biztosítani
-#   kell, hogy a kezdőpont sebesség a CoolStep küszöbérték felett legyen!
-#   Az alapértelmezett beállítá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.
-#   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
@@ -7217,15 +7257,13 @@ run_current:
 #driver_X3: 255
 #driver_START_SIN: 0
 #driver_START_SIN90: 247
-#   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.
+#   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.
 #driver_MULTISTEP_FILT: True
 #driver_IHOLDDELAY: 6
 #driver_TPOWERDOWN: 10
@@ -7259,20 +7297,20 @@ run_current:
 #driver_BBMCLKS: 4
 #driver_BBMTIME: 0
 #driver_FILT_ISENSE: 0
-#   Állítsd be az adott regisztert a TMC5160 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.
+#   Set the given register during the configuration of the TMC5160
+#   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 TMC5160 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
-#   „tmc5160_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őpontot.
+#   The micro-controller pin attached to one of the DIAG lines of the
+#   TMC5160 chip. Only a single diag pin should be specified. The pin
+#   is "active low" and is thus normally prefaced with "^!". Setting
+#   this creates a "tmc5160_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.
 
    
 
 
    Futás-idejű léptetőmotor áram konfiguráció
    
@@ -7795,32 +7833,37 @@ text:
 
    További információkért lásd a parancs hivatkozást.
    
 
    [filament_switch_sensor my_sensor]
 #pause_on_runout: True
-#   Ha True értékre van állítva, a PAUSE azonnal végrehajtódik, miután a
-#   rendszer szálkifutást észlel. Ne feledd, hogy ha a pause_on_runout
-#   értéke False, és a runout_gcode kimarad, akkor a kifutás észlelése le
-#   van tiltva. Az alapértelmezett érték True.
+#   When set to True, a PAUSE will execute immediately after a runout
+#   is detected. Note that if pause_on_runout is False and the
+#   runout_gcode is omitted then runout detection is disabled. Default
+#   is True.
 #runout_gcode:
-#   A nyomtatószál kifutását követően végrehajtandó G-kód parancsok listája.
-#   Lásd a docs/Command_Templates.md fájlt a G-kód formátumhoz. Ha a
-#   pause_on_runout értéke True, ez a G-kód a PAUSE befejezése után fog
-#   futni. Az alapértelmezés szerint nem fut semmilyen G-kód parancs.
+#   A list of G-Code commands to execute after a filament runout is
+#   detected. See docs/Command_Templates.md for G-Code format. If
+#   pause_on_runout is set to True this G-Code will run after the
+#   PAUSE is complete. The default is not to run any G-Code commands.
 #insert_gcode:
-#   A nyomtatószál-beillesztés észlelése után végrehajtandó G-kód parancsok
-#   listája. Lásd a docs/Command_Templates.md fájlt a G-kód formátumhoz.
-#   Az alapértelmezés szerint nem fut semmilyen G-kód parancs, ami letiltja
-#   a beszúrás észlelését.
+#   A list of G-Code commands to execute after a filament insert is
+#   detected. See docs/Command_Templates.md for G-Code format. The
+#   default is not to run any G-Code commands, which disables insert
+#   detection.
 #event_delay: 3.0
-#   Az események közötti késleltetés minimális időtartama másodpercben.
-#   Az ebben az időszakban elindított eseményeket a rendszer csendben
-#   figyelmen kívül hagyja. Az alapértelmezett érték 3 másodperc.
+#   The minimum amount of time in seconds to delay between events.
+#   Events triggered during this time period will be silently
+#   ignored. The default is 3 seconds.
 #pause_delay: 0.5
-#   A szüneteltetési parancs kiküldése és a runout_gcode végrehajtása
-#   között eltelt idő másodpercben. Hasznos lehet növelni ezt a késleltetést,
-#   ha az OctoPrint furcsa szüneteltetést mutat.
-#   Az alapértelmezett érték 0,5 másodperc.
+#   The amount of time to delay, in seconds, between the pause command
+#   dispatch and execution of the runout_gcode. It may be useful to
+#   increase this delay if OctoPrint exhibits strange pause behavior.
+#   Default is 0.5 seconds.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   switch gcode. The switch must he held in a single state for at least
+#   this long to activate. If the switch is toggled on/off during this delay,
+#   the event is ignored. Default is 0.
 #switch_pin:
-#   Az a tű, amelyre a kapcsoló csatlakoztatva van.
-#   Ezt a paramétert meg kell adni.
+#   The pin on which the switch is connected. This parameter must be
+#   provided.
 
    
 
 
    [filament_motion_sensor]
    
@@ -7913,8 +7956,17 @@ adc2:
 
    Terhelőcella. Egy erőmérő cellához csatlakoztatott ADC érzékelőt használ digitális mérleg létrehozásához.
    
 
    [load_cell]
 sensor_type:
-#   Ennek a támogatott érzékelőtípusok egyikének kell lennie,
-#   lásd alább.
+#   This must be one of the supported sensor types, see below.
+#counts_per_gram:
+#   The floating point number of sensor counts that indicates 1 gram of force.
+#   This value is calculated by the LOAD_CELL_CALIBRATE command.
+#reference_tare_counts:
+#   The integer tare value, in raw sensor counts, taken when LOAD_CELL_CALIBRATE
+#   is run. This is the default tare value when klipper starts up.
+#sensor_orientation:
+#   Change the sensor's orientation. Can be either 'normal' or 'inverted'.
+#   The default is 'normal'. Use 'inverted' if the sensor reports a
+#   decreasing force value when placed under load.
 
    
 
 
    HX711
    
@@ -8063,6 +8115,38 @@ vssa_pin:
 #   zaj csökkentése érdekében. Az alapértelmezett érték 2 másodperc.
    +

    [ads1x1x]

    +

    ADS1013, ADS1014, ADS1015, ADS1113, ADS1114 and ADS1115 are I2C based Analog to Digital Converters that can be used for temperature sensors. They provide 4 analog input pins either as single line or as differential input.

    +

    Note: Use caution if using this sensor to control heaters. The heater min_temp and max_temp are only verified in the host and only if the host is running and operating normally. (ADC inputs directly connected to the micro-controller verify min_temp and max_temp within the micro-controller and do not require a working connection to the host.)

    +
    [ads1x1x my_ads1x1x]
+chip: ADS1115
+#pga: 4.096V
+#   Default value is 4.096V. The maximum voltage range used for the input. This
+#   scales all values read from the ADC. Options are: 6.144V, 4.096V, 2.048V,
+#   1.024V, 0.512V, 0.256V
+#adc_voltage: 3.3
+#   The suppy voltage for the device. This allows additional software scaling
+#   for all values read from the ADC.
+i2c_mcu: host
+i2c_bus: i2c.1
+#address_pin: GND
+#   Default value is GND.  There can be up to four addressed devices depending
+#   upon wiring of the device. Check the datasheet for details. The i2c_address
+#   can be specified directly instead of using the address_pin.
+
    + +

    The chip provides pins that can be used on other sensors.

    +
    sensor_type: ...
+#   Can be any thermistor or adc_temperature.
+sensor_pin: my_ads1x1x:AIN0
+#   A combination of the name of the ads1x1x chip and the pin. Possible
+#   pin values are AIN0, AIN1, AIN2 and AIN3 for single ended lines and
+#   DIFF01, DIFF03, DIFF13 and DIFF23 for differential between their
+#   correspoding lines. For example
+#   DIFF03 measures the differential between line 0 and 3. Only specific
+#   combinations for the differentials are allowed.
+
    +

    [replicape]

    Replicape támogatás. Lásd a beaglebone útmutatót és a generic-replicape.cfg fájlt egy példáért.

    # A "replicape" konfigurációs rész hozzáadja a
@@ -8132,7 +8216,7 @@ host_mcu:
 
    Palette 2 multimaterial támogatás szorosabb integrációt biztosít, amely támogatja a Palette 2 eszközöket csatlakoztatott módban.
    
 
    Ez a modul a teljes funkcionalitáshoz a [virtual_sdcard] és [pause_resume] modulokat is igényli.
    
 
    Ha ezt a modult használod, ne használd a Palette 2 plugint az Octoprinthez, mivel ezek ütközni fognak, és az egyik nem fog megfelelően inicializálódni, ami valószínűleg megszakítja a nyomtatást.
    
-
    Ha az Octoprintet használod és a G-kódot a soros porton keresztül streameli a virtual_sd-ről való nyomtatás helyett, akkor a M1 és M0 parancsok Pausing parancsok a Settings >. alatt remo; Serial Connection > Firmware & protocol megakadályozzák, hogy a nyomtatás megkezdéséhez a Paletta 2-n el kelljen indítani a nyomtatást, és az Octoprintben fel kelljen oldani a szünetet.
    
+
    If you use Octoprint and stream gcode over the serial port instead of printing from virtual_sd, then remove M1 and M0 from Pausing commands in Settings > Serial Connection > Firmware & protocol will prevent the need to start print on the Palette 2 and unpausing in Octoprint for your print to begin.
    
 
    [paletta2]
 serial:
 # A soros port, amelyhez a Palette 2 csatlakozik.
diff --git a/hu/Config_checks.html b/hu/Config_checks.html
index 34c1ecb91..09bf2d921 100644
--- a/hu/Config_checks.html
+++ b/hu/Config_checks.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Contact.html b/hu/Contact.html
index 28f8a3091..f98e3bbf4 100644
--- a/hu/Contact.html
+++ b/hu/Contact.html
@@ -451,8 +451,8 @@
 
       
         
  • 
-  
-    Klipper github
+  
+    Professional Services
   
   
 
    • 
@@ -1376,8 +1376,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
       
         
  • 
-  
-    Klipper github
+  
+    Professional Services
   
   
 
    • 
@@ -1558,9 +1558,10 @@
 
    Változtatásokat végzek, amelyeket szeretnék a Klipperbe beépíteni
    
 
    A Klipper nyílt forráskódú szoftver, és örömmel fogadjuk az új hozzájárulásokat.
    
 
    Az új hozzájárulásokat (mind a kódot, mind a dokumentációt illetően) a GitHub Pull Requests-en keresztül küldheted be. Lásd a CONTRIBUTING dokumentumot a fontos információkért.
    
-
    Számos dokumentum fejlesztőknek. Ha kérdésed van a kóddal kapcsolatban, akkor a Klipper Közösségi Fórum vagy a Klipper Közösségi Discord oldalon is felteheted.
    
-
    Klipper github
    
-
    A Klipper githubot a közreműködők arra használhatják, hogy megosszák a Klipper fejlesztésére irányuló munkájuk állapotát. Elvárás, hogy a github jegyet nyitó személy aktívan dolgozzon az adott feladaton, és ő végezze el az összes szükséges munkát a feladat elvégzéséhez. A Klipper githubot nem használjuk kérésekre, sem hibák bejelentésére, sem kérdések feltevésére. Használd helyette a Klipper közösségi fórumot vagy a Klipper közösségi discordot.
    
+
    There are several documents for developers. If you have questions on the code then you can also ask in the Klipper Discourse Forum or on the Klipper Discord Chat.
    
+
    Professional Services
    
+
    
+
    Custom software development, software support, and solutions: https://ko-fi.com/koconnor
    
 
               
             
diff --git a/hu/Debugging.html b/hu/Debugging.html
index 8e1099aa0..5c8982b19 100644
--- a/hu/Debugging.html
+++ b/hu/Debugging.html
@@ -1384,8 +1384,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Delta_Calibrate.html b/hu/Delta_Calibrate.html
index d3019fa10..2584a98fc 100644
--- a/hu/Delta_Calibrate.html
+++ b/hu/Delta_Calibrate.html
@@ -1365,8 +1365,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Eddy_Probe.html b/hu/Eddy_Probe.html
index 417024d42..7c546a729 100644
--- a/hu/Eddy_Probe.html
+++ b/hu/Eddy_Probe.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1487,13 +1487,13 @@
       
       
         
-        
  • 
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Example_Configs.html b/hu/Example_Configs.html
index 91e7072a7..57fb26da1 100644
--- a/hu/Example_Configs.html
+++ b/hu/Example_Configs.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Exclude_Object.html b/hu/Exclude_Object.html
index 3a6f40662..33a60ff3e 100644
--- a/hu/Exclude_Object.html
+++ b/hu/Exclude_Object.html
@@ -1356,8 +1356,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/FAQ.html b/hu/FAQ.html
index 42698786f..13b361cd8 100644
--- a/hu/FAQ.html
+++ b/hu/FAQ.html
@@ -1488,8 +1488,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Features.html b/hu/Features.html
index 2521d7d31..8752b38d0 100644
--- a/hu/Features.html
+++ b/hu/Features.html
@@ -1334,8 +1334,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1443,18 +1443,18 @@
 
  • Standard G-kód támogatás. A tipikus "szeletelők" (SuperSlicer, Cura, PrusaSlicer, stb.) által előállított általános G-kód parancsok támogatottak.
    • 
 
  • Több extruder támogatása. A közös fűtőberendezéssel rendelkező extrudereket és a független kocsikon (IDEX) lévő extrudereket is támogatják.
    • 
 
  • Támogatja a cartesian, delta, corexy, corexz, hybrid-corexy, hybrid-corexz, rotary delta, polár és kábelcsörlő stílusú nyomtatókat.
    • 
-
  • Tárgyasztal szintezésének automatikus támogatása. A Klipper konfigurálható alapszintű tárgyasztal dőlés-érzékelésre vagy a tárgyasztal teljes hálós szintezésére. Ha a tárgyasztal több Z steppert használ, akkor a Klipper a Z stepper-ek független manipulálásával is képes szintezni. A legtöbb Z magasságmérő szonda támogatott, beleértve a BL-Touch szondákat és a szervómotoros szondákat is.
    • 
+
  • Automatic bed leveling support. Klipper can be configured for basic bed tilt detection or full mesh bed leveling. The bed mesh can be customized to the print size (adaptive bed mesh). If the bed uses multiple Z steppers then Klipper can also level by independently manipulating the Z steppers. Most Z height probes are supported, including BL-Touch probes and servo activated probes. Probes may be calibrated for axis twist compensation. If using an "eddy current probe" then one can utilize fast bed mesh scanning,
    • 
 
  • Automatikus delta kalibráció támogatása. A kalibráló eszköz alapvető magassági kalibrálást, valamint továbbfejlesztett X és Y dimenzió kalibrálást végezhet. A kalibrálás elvégezhető Z magasságmérővel vagy kézi szintezővel.
    • 
 
  • Futtatási idejű "objektum kizárása" támogatás. Beállítása esetén ez a modul megkönnyítheti egy több részből álló nyomtatás egyetlen objektumának törlését.
    • 
-
  • Az általános hőmérséklet-érzékelők támogatása (pl. általános termisztorok, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20 és LM75). Egyedi termisztorok és egyedi analóg hőmérséklet-érzékelők is konfigurálhatók. Lehet figyelni a mikrokontroller hőmérsékletét és a Raspberry Pi processzor hőmérsékletét.
    • 
+
  • Support for common temperature sensors (eg, common thermistors, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20, AHT10, SHT3x, and LM75). Custom thermistors and custom analog temperature sensors can also be configured. One can monitor the internal micro-controller temperature sensor and the internal temperature sensor of a Raspberry Pi.
    • 
 
  • Alapértelmezés szerint a fűtésvédelem engedélyezett.
    • 
-
  • Standard ventilátorok, fejhűtő ventilátorok és hőmérséklet-szabályozott ventilátorok támogatása. Nincs szükség arra, hogy a ventilátorok folyamatosan működjenek, amikor a nyomtató üresjáratban van. A fordulatszámmérővel ellátott ventilátoroknál a ventilátorok fordulatszáma ellenőrizhető.
    • 
+
  • Support for standard fans, nozzle fans, and temperature controlled fans. No need to keep fans running when the printer is idle. Fan speed can be monitored on fans that have a tachometer. One can assign a "math formula" to a fan for automatic fan speed updating.
    • 
 
  • A TMC2130, TMC2208/TMC2224, TMC2209, TMC2660 és TMC5160 léptetőmotor-meghajtók futásidejű konfigurációjának támogatása. A hagyományos léptetőmotor-meghajtók AD5206, MCP4451, MCP4728, MCP4018 és PWM-tűkön keresztül történő áramszabályozásának támogatása is biztosított.
    • 
 
  • Közvetlenül a nyomtatóhoz csatlakoztatott általános LCD-kijelzők támogatása. Egy alapértelmezett menü is rendelkezésre áll. A kijelző és a menü tartalma a konfigurációs fájlon keresztül teljesen testreszabható.
    • 
 
  • Állandó gyorsulás és "look-ahead" támogatás. Minden mozgás fokozatosan gyorsul fel álló helyzetből utazósebességre, majd lassul vissza álló helyzetbe. A beérkező G-kódos mozgásparancsok sorba kerülnek és elemzi őket - a hasonló irányú mozgások közötti gyorsulás optimalizálva lesz a nyomtatási hibák csökkentése és a teljes nyomtatási idő javítása érdekében.
    • 
 
  • A Klipper egy olyan "léptetőfázis végállás" algoritmust valósít meg, amely javíthatja a tipikus végálláskapcsolók pontosságát. Megfelelő beállítás esetén javíthatja a nyomtatás első réteg tárgyasztalhoz tapadását.
    • 
 
  • Száljelenlét-, szálmozgás- és szálszélesség-érzékelők támogatása.
    • 
-
  • A gyorsulás mérésének és rögzítésének támogatása adxl345, mpu9250 és mpu6050 gyorsulásmérőkkel.
    • 
+
  • Support for measuring and recording acceleration using adxl345, mpu9250, mpu6050, lis2dw12, lis3dh, and icm20948 accelerometers.
    • 
 
  • A nyomtató rezgésének és zajának csökkentése érdekében a rövid "cikcakk" mozgások csúcssebességének korlátozásának támogatása. További információkért lásd a Kinematika dokumentumot.
    • 
 
  • Számos gyakori nyomtatóhoz rendelkezésre állnak minta konfigurációs fájlok. Listát a config könyvtárban találod.
    • 
 
@@ -1526,11 +1526,6 @@
 1622K
 
 
-RP2040
-2400K
-1636K
-
-
 SAM4E8E
 2500K
 1674K
@@ -1556,6 +1551,11 @@
 2634K
 
 
+RP2040
+4000K
+2571K
+
+
 RP2350
 4167K
 2663K
@@ -1566,9 +1566,9 @@
 4737K
 
 
-STM32H743
-9091K
-6061K
+STM32H723
+7429K
+8619K
 
 
 
diff --git a/hu/G-Codes.html b/hu/G-Codes.html
index f8848dd1a..7f96e00a2 100644
--- a/hu/G-Codes.html
+++ b/hu/G-Codes.html
@@ -1620,6 +1620,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -1694,33 +1756,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1789,26 +1824,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1850,6 +1865,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -2281,6 +2316,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -2429,54 +2512,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -3006,8 +3041,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3881,6 +3916,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -3955,33 +4052,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4050,26 +4120,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4111,6 +4161,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -4542,6 +4612,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -4690,54 +4808,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -4831,11 +4901,10 @@
 
    The following commands are available when the axis_twist_compensation config
 section is enabled.
    
 
    AXIS_TWIST_COMPENSATION_CALIBRATE
    
-
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]
    
+
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [SAMPLE_COUNT=<value>]
    
 
    A tengelycsavar kompenzáció kalibrálása a céltengely megadásával vagy az automatikus kalibráció engedélyezésével.
    
 
      
 
    • TENGELY: Határozd meg azt a tengelyt (X vagy Y), amelyre a csavarkompenzáció kalibrálásra kerül. Ha nincs megadva, a tengely alapértelmezett értéke 'X'.
      • 
-
    • AUTO: Automatikus kalibrációs üzemmód engedélyezése. Ha AUTO=True, a kalibrálás mind az X, mind az Y tengelyre lefut. Ebben az üzemmódban az AXIS nem adható meg. Ha az AXIS és az AUTO is meg van adva, hibaüzenet jelenik meg.
      • 
 
    
 
    [bed_mesh]
    
 
    A következő parancsok akkor érhetők el, ha a bed_mesh konfigurációs szakasz engedélyezve van (lásd még a tárgyasztal háló útmutatót).
    
@@ -4965,7 +5034,10 @@ section is enabled.
    
 
    FORCE_MOVE
    
 
    FORCE_MOVE STEPPER=<config_name> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]: 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.
    
 
    SET_KINEMATIC_POSITION
    
-
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]: Kényszeríti az alacsony szintű kinematikai kódot, hogy azt higgye, a nyomtatófej a megadott kartoték pozícióban van. Ez egy diagnosztikai és hibakeresési parancs; a SET_GCODE_OFFSET és/vagy a G92 parancsot használja 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 vezérelték. A helytelen vagy érvénytelen pozíció beállítása belső szoftverhibához vezethet. A CLEAR paraméterrel elfelejtheti a megadott tengelyek kezdőpozíció állapotát. Vedd figyelembe, hogy a CLEAR nem írja felül az előző funkciót; ha egy tengely nincs megadva a CLEAR paraméterhez, akkor a kinematikai pozíciója a fentiek szerint lesz beállítva. Ez a parancs érvénytelenítheti a jövőbeli határellenőrzéseket; a kinematika visszaállításához adjunk ki egy G28 parancsot.
    
+
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [SET_HOMED=<[X][Y][Z]>] [CLEAR_HOMED=<[X][Y][Z]>]: Force the low-level kinematic code to believe the toolhead is at the given cartesian position and set/clear homed status. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. Setting an incorrect or invalid position may lead to internal software errors.
    
+
    The X, Y, and Z parameters are used to alter the low-level kinematic position tracking. If any of these parameters are not set then the position is not changed - for example SET_KINEMATIC_POSITION Z=10 would set all axes as homed, set the internal Z position to 10, and leave the X and Y positions unchanged. Changing the internal position tracking is not dependent on the internal homing state - one may alter the position for both homed and not homed axes, and similarly one may set or clear the homing state of an axis without altering its internal position.
    
+
    The SET_HOMED parameter defaults to XYZ which instructs the kinematics to consider all axes as homed. A bare SET_KINEMATIC_POSITION command will result in all axes being considered homed (and not change its current position). If it is not desired to change the state of homed axes then assign SET_HOMED to an empty string - for example: SET_KINEMATIC_POSITION SET_HOMED= X=10. It is also possible to request an individual axis be considered homed (eg, SET_HOMED=X), but note that non-cartesian style kinematics (such as delta kinematics) may not support setting an individual axis as homed.
    
+
    The CLEAR_HOMED parameter instructs the kinematics to consider the given axes as not homed. For example, CLEAR_HOMED=XYZ would request all axes to be considered not homed (and thus require homing prior to movement on those axes). The default is SET_HOMED=XYZ even if CLEAR_HOMED is present, so the command SET_KINEMATIC_POSITION CLEAR_HOMED=Z will set X and Y as homed and clear the homing state for Z. Use SET_KINEMATIC_POSITION SET_HOMED= CLEAR_HOMED=Z if the goal is to clear only the Z homing state. If an axis is specified in neither SET_HOMED nor CLEAR_HOMED then its homing state is not changed and if it is specified in both then CLEAR_HOMED has precedence. It is possible to request clearing of an individual axis, but on non-cartesian style kinematics (such as delta kinematics) doing so may result in clearing the homing state of additional axes. Note the CLEAR parameter is currently an alias for the CLEAR_HOMED parameter, but this alias will be removed in the future.
    
 
    [gcode]
    
 
    A G-kód modul automatikusan betöltődik.
    
 
    RESTART
    
@@ -5028,6 +5100,28 @@ section is enabled.
    
 
    A következő parancs akkor engedélyezett, ha az input_shaper konfigurációs szakasz engedélyezve van (lásd még a rezonancia kompenzációs útmutatót).
    
 
    SET_INPUT_SHAPER
    
 
    SET_INPUT_SHAPER [SHAPER_FREQ_X=<shaper_freq_x>] [SHAPER_FREQ_Y=<shaper_freq_y>] [DAMPING_RATIO_X=<damping_ratio_x>] [DAMPING_RATIO_Y=<damping_ratio_y>] [SHAPER_TYPE=<shaper>] [SHAPER_TYPE_X=<shaper_type_x>] [SHAPER_TYPE_Y=<shaper_type_y>]: A bemeneti formáló paraméterek módosítása. Vedd figyelembe, hogy a SHAPER_TYPE paraméter visszaállítja a bemeneti formálót mind az X, mind az Y tengelyre, még akkor is, ha az [input_shaper] szakaszban különböző formálótípusok lettek beállítva. A SHAPER_TYPE nem használható együtt a SHAPER_TYPE_X és SHAPER_TYPE_Y paraméterekkel. Az egyes paraméterekkel kapcsolatos további részletekért lásd a konfigurációs hivatkozást.
    
+
    [led]
    
+
    A következő parancs akkor érhető el, ha a LED konfigurációs szakaszok bármelyike engedélyezve van.
    
+
    SET_LED
    
+
    SET_LED LED=<config_name> RED=<value> GREEN=<value> BLUE=<value> WHITE=<value> [INDEX=<index>] [TRANSMIT=0] [SYNC=1]: Ez állítja be a LED kimenetet. Minden szín <value> 0,0 és 1,0 között kell lennie. A WHITE opció csak RGBW LED-ek esetén érvényes. Ha a LED több chipet támogat egy daisy-chainben, akkor megadhatjuk az INDEX-et, hogy csak az adott chip színét változtassuk meg (1 az első chiphez, 2 a másodikhoz stb.). Ha az INDEX nincs megadva, akkor a daisy-chain összes LED-je a megadott színre lesz beállítva. Ha TRANSMIT=0 van megadva, akkor a színváltoztatás csak a következő SET_LED parancsnál történik meg, amely nem ad meg TRANSMIT=0-t. Ez hasznos lehet az INDEX paraméterrel kombinálva, ha egy daisy-chainben több frissítést szeretnénk kötegelni. Alapértelmezés szerint a SET_LED parancs szinkronizálja a változtatásokat a többi folyamatban lévő G-kód paranccsal. Ez nemkívánatos viselkedéshez vezethet, ha a LED-ek beállítása akkor történik, amikor a nyomtató nem nyomtat, mivel ez visszaállítja az üresjárati időkorlátot. Ha nincs szükség gondos időzítésre, az opcionális SYNC=0 paraméter megadható, hogy a módosításokat az üresjárati időkorlát visszaállítása nélkül alkalmazd.
    
+
    SET_LED_TEMPLATE
    
+
    SET_LED_TEMPLATE LED=<led_name> TEMPLATE=<template_name> [<param_x>=<literal>] [INDEX=<index>]: Egy display_template hozzárendelése egy adott LED-hez. Például, ha definiáltunk egy [display_template my_led_template] konfigurációs szakaszt, akkor itt hozzárendelhetjük a TEMPLATE=my_led_template. A display_template-nek egy vesszővel elválasztott karakterláncot kell létrehoznia, amely négy lebegőpontos számot tartalmaz, amelyek megfelelnek a piros, zöld, kék és fehér színbeállításoknak. A sablon folyamatosan kiértékelésre kerül, és a LED automatikusan az így kapott színekre lesz beállítva. A sablon kiértékelése során használandó display_template paramétereket lehet beállítani (a paraméterek Python literálokként lesznek elemezve). Ha az INDEX nincs megadva, akkor a LED's daisy-chain összes chipje a sablonra lesz beállítva, ellenkező esetben csak a megadott indexszel rendelkező chip lesz frissítve. Ha a TEMPLATE üres karakterlánc, akkor ez a parancs törli a LED-hez rendelt korábbi sablonokat (ekkor a SET_LED parancsokat használhatjuk a LED színbeállításainak kezelésére).
    
+
    [load_cell]
    
+
    The following commands are enabled if a load_cell config section has been enabled.
    
+
    LOAD_CELL_DIAGNOSTIC
    
+
    LOAD_CELL_DIAGNOSTIC [LOAD_CELL=<config_name>]: This command collects 10 seconds of load cell data and reports statistics that can help you verify proper operation of the load cell. This command can be run on both calibrated and uncalibrated load cells.
    
+
    LOAD_CELL_CALIBRATE
    
+
    LOAD_CELL_CALIBRATE [LOAD_CELL=<config_name>]: Start the guided calibration utility. Calibration is a 3 step process:
    
+
      
+
    1. First you remove all load from the load cell and run the TARE command
      2. 
+
    2. Next you apply a known load to the load cell and run the CALIBRATE GRAMS=nnn command
      3. 
+
    3. Finally use the ACCEPT command to save the results
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    LOAD_CELL_TARE
    
+
    LOAD_CELL_TARE [LOAD_CELL=<config_name>]: This works just like the tare button on digital scale. It sets the current raw reading of the load cell to be the zero point reference value. The response is the percentage of the sensors range that was read and the raw value in counts.
    
+
    LOAD_CELL_READ load_cell="name"
    
+
    LOAD_CELL_READ [LOAD_CELL=<config_name>]: This command takes a reading from the load cell. The response is the percentage of the sensors range that was read and the raw value in counts. If the load cell is calibrated a force in grams is also reported.
    
 
    [manual_probe]
    
 
    A manual_probe modul automatikusan betöltődik.
    
 
    MANUAL_PROBE
    
@@ -5049,12 +5143,6 @@ section is enabled.
    
 
    A következő parancs akkor érhető el, ha az mcp4018 config szekció engedélyezve van.
    
 
    SET_DIGIPOT
    
 
    SET_DIGIPOT DIGIPOT=config_name WIPER=<value>: Ez a parancs megváltoztatja a digipot aktuális értékét. Ennek az értéknek általában 0.0 és 1.0 között kell lennie, hacsak a configban nincs definiálva 'scale'. Ha 'scale' van definiálva, akkor ennek az értéknek 0.0 és a 'scale' érték között kell lennie.
    
-
    [led]
    
-
    A következő parancs akkor érhető el, ha a LED konfigurációs szakaszok bármelyike engedélyezve van.
    
-
    SET_LED
    
-
    SET_LED LED=<config_name> RED=<value> GREEN=<value> BLUE=<value> WHITE=<value> [INDEX=<index>] [TRANSMIT=0] [SYNC=1]: Ez állítja be a LED kimenetet. Minden szín <value> 0,0 és 1,0 között kell lennie. A WHITE opció csak RGBW LED-ek esetén érvényes. Ha a LED több chipet támogat egy daisy-chainben, akkor megadhatjuk az INDEX-et, hogy csak az adott chip színét változtassuk meg (1 az első chiphez, 2 a másodikhoz stb.). Ha az INDEX nincs megadva, akkor a daisy-chain összes LED-je a megadott színre lesz beállítva. Ha TRANSMIT=0 van megadva, akkor a színváltoztatás csak a következő SET_LED parancsnál történik meg, amely nem ad meg TRANSMIT=0-t. Ez hasznos lehet az INDEX paraméterrel kombinálva, ha egy daisy-chainben több frissítést szeretnénk kötegelni. Alapértelmezés szerint a SET_LED parancs szinkronizálja a változtatásokat a többi folyamatban lévő G-kód paranccsal. Ez nemkívánatos viselkedéshez vezethet, ha a LED-ek beállítása akkor történik, amikor a nyomtató nem nyomtat, mivel ez visszaállítja az üresjárati időkorlátot. Ha nincs szükség gondos időzítésre, az opcionális SYNC=0 paraméter megadható, hogy a módosításokat az üresjárati időkorlát visszaállítása nélkül alkalmazd.
    
-
    SET_LED_TEMPLATE
    
-
    SET_LED_TEMPLATE LED=<led_name> TEMPLATE=<template_name> [<param_x>=<literal>] [INDEX=<index>]: Egy display_template hozzárendelése egy adott LED-hez. Például, ha definiáltunk egy [display_template my_led_template] konfigurációs szakaszt, akkor itt hozzárendelhetjük a TEMPLATE=my_led_template. A display_template-nek egy vesszővel elválasztott karakterláncot kell létrehoznia, amely négy lebegőpontos számot tartalmaz, amelyek megfelelnek a piros, zöld, kék és fehér színbeállításoknak. A sablon folyamatosan kiértékelésre kerül, és a LED automatikusan az így kapott színekre lesz beállítva. A sablon kiértékelése során használandó display_template paramétereket lehet beállítani (a paraméterek Python literálokként lesznek elemezve). Ha az INDEX nincs megadva, akkor a LED's daisy-chain összes chipje a sablonra lesz beállítva, ellenkező esetben csak a megadott indexszel rendelkező chip lesz frissítve. Ha a TEMPLATE üres karakterlánc, akkor ez a parancs törli a LED-hez rendelt korábbi sablonokat (ekkor a SET_LED parancsokat használhatjuk a LED színbeállításainak kezelésére).
    
 
    [output_pin]
    
 
    A következő parancs akkor érhető el, ha az output_pin konfigurációs szakasz engedélyezve van.
    
 
    SET_PIN
    
@@ -5077,10 +5165,6 @@ section is enabled.
    
 
    PALETTE_CUT: Ez a parancs utasítja a Palette 2-t, hogy vágja el az illesztési magba töltött szálat.
    
 
    PALETTE_SMART_LOAD
    
 
    PALETTE_SMART_LOAD: Ez a parancs elindítja az intelligens betöltési sorozatot a Paletta 2-n. A nyomtatószál betöltése automatikusan történik a készülékben a nyomtatóhoz kalibrált távolság extrudálásával, és utasítja a Palette 2-t, amint a betöltés befejeződött. Ez a parancs megegyezik a Smart Load megnyomásával közvetlenül a Palette 2 képernyőjén, miután a nyomtatószál betöltése befejeződött.
    
-
    [pid_calibrate]
    
-
    A pid_calibrate modul automatikusan betöltődik, ha a konfigurációs fájlban van egy fűtés definiálva.
    
-
    PID_CALIBRATE
    
-
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]: A PID kalibrációs teszt elvégzése. A megadott fűtőberendezés a megadott célhőmérséklet eléréséig engedélyezve lesz, majd a fűtőberendezés több cikluson keresztül ki- és bekapcsol. Ha a WRITE_FILE paraméter engedélyezve van, akkor létrejön a /tmp/heattest.txt fájl a teszt során vett összes hőmérséklet-mintát tartalmazó naplóval.
    
 
    [pause_resume]
    
 
    A következő parancsok akkor érhetők el, ha a pause_resume konfigurációs szakasz engedélyezve van:
    
 
    PAUSE
    
@@ -5091,6 +5175,10 @@ section is enabled.
    
 
    CLEAR_PAUSE: Törli az aktuális szüneteltetett állapotot a nyomtatás folytatása nélkül. Ez akkor hasznos, ha valaki úgy dönt, hogy PAUSE után megszakítja a nyomtatást. Ajánlatos ezt hozzáadni az indító G-kódhoz, hogy a szüneteltetett állapot minden nyomtatásnál friss legyen.
    
 
    CANCEL_PRINT
    
 
    CANCEL_PRINT: Az aktuális nyomtatás törlése.
    
+
    [pid_calibrate]
    
+
    A pid_calibrate modul automatikusan betöltődik, ha a konfigurációs fájlban van egy fűtés definiálva.
    
+
    PID_CALIBRATE
    
+
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]: A PID kalibrációs teszt elvégzése. A megadott fűtőberendezés a megadott célhőmérséklet eléréséig engedélyezve lesz, majd a fűtőberendezés több cikluson keresztül ki- és bekapcsol. Ha a WRITE_FILE paraméter engedélyezve van, akkor létrejön a /tmp/heattest.txt fájl a teszt során vett összes hőmérséklet-mintát tartalmazó naplóval.
    
 
 
    A print_stats modul automatikusan betöltődik.
    
 
    SET_PRINT_STATS_INFO
    
@@ -5158,7 +5246,7 @@ section is enabled.
    
 
    [save_variables]
    
 
    A következő parancs akkor engedélyezett, ha a save_variables konfigurációs szakasz engedélyezve van.
    
 
    SAVE_VARIABLE
    
-
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>: A változót a lemezre menti, hogy újraindításkor is használható legyen. Minden tárolt változó betöltődik a printer.save_variables.variables dict indításkor, és használható a G-kód makrókban. A megadott VALUE-t Python literálként elemzi.
    
+
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>: Saves the variable to disk so that it can be used across restarts. The VARIABLE must be lowercase. All stored variables are loaded into the printer.save_variables.variables dict at startup and can be used in gcode macros. The provided VALUE is parsed as a Python literal.
    
 
    [screws_tilt_adjust]
    
 
    A következő parancsok akkor érhetők el, ha a screws_tilt_adjust konfigurációs szakasz engedélyezve van (lásd még a kézi szintbeállítási útmutatót).
    
 
    SCREWS_TILT_CALCULATE
    
@@ -5199,6 +5287,18 @@ section is enabled.
    
 
    A következő parancs akkor érhető el, ha a temperature_fan konfigurációs szakasz engedélyezve van.
    
 
    SET_TEMPERATURE_FAN_TARGET
    
 
    SET_TEMPERATURE_FAN_TARGET temperature_fan=<temperature_fan_name> [target=<target_temperature>] [min_speed=<min_speed>] [max_speed=<max_speed>]: A temperature_fan célhőmérsékletének beállítása. Ha nincs megadva célérték, akkor a konfigurációs fájlban megadott hőmérsékletet állítja be. Ha a sebességek nincsenek megadva, akkor nem történik változás.
    
+
    [temperature_probe]
    
+
    A következő parancsok akkor érhetők el, ha a temperature_probe konfigurációs szakasz engedélyezve van.
    
+
    TEMPERATURE_PROBE_CALIBRATE
    
+
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Elindítja a szonda sodródásának kalibrálását örvényáram alapú szondákhoz. A TARGET az utolsó mérés célhőmérséklete. Ha a mérés során rögzített hőmérséklet meghaladja a TARGET kalibrációt, akkor a kalibráció befejeződik. A STEP paraméter beállítja a hőmérséklet-deltát (C-ban) a mérések között. A mérések után ez a delta a TEMPERATURE_PROBE_NEXT hívás ütemezésére szolgál. Az alapértelmezett STEP a 2.
    
+
    TEMPERATURE_PROBE_NEXT
    
+
    TEMPERATURE_PROBE_NEXT: A kalibrálás megkezdése után ez a parancs fut a következő méréshez. A rendszer automatikusan ütemezi a futást, amikor elérte a STEP által meghatározott delta értéket, de lehetséges manuálisan is futtatni ezt a parancsot egy új mérés kényszerítéséhez. Ez a parancs csak kalibrálás közben érhető el.
    
+
    TEMPERATURE_PROBE_COMPLETE:
    
+
    TEMPERATURE_PROBE_COMPLETE: A kalibráció befejezésére és az aktuális eredmény mentésére használható, mielőtt elérné a TARGET hőmérsékletet. Ez a parancs csak kalibrálás közben érhető el.
    
+
    ABORT
    
+
    ABORT: Megszakítja a kalibrálási folyamatot, elveti az aktuális eredményeket. Ez a parancs csak a drift-kalibráció során érhető el.
    
+
    TEMPERATURE_PROBE_ENABLE
    
+
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Be- vagy kikapcsolja a hőmérséklet-eltolás kompenzációját. Ha az ENGEDÉLYEZÉS 0-ra van állítva, az eltolás kompenzáció le lesz tiltva, ha 1-re van állítva, akkor engedélyezve van.
    
 
    [tmcXXXX]
    
 
    A következő parancsok akkor érhetők el, ha a tmcXXXXXX konfigurációs szakaszok bármelyike engedélyezve van.
    
 
    DUMP_TMC
    
@@ -5246,18 +5346,6 @@ section is enabled.
    
 
    A következő parancsok akkor érhetők el, ha a z_tilt konfigurációs szakasz engedélyezve van.
    
 
    Z_TILT_ADJUST
    
 
    Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]: Ez a parancs a konfigurációban megadott pontokat szondázza, majd a dőlés kompenzálása érdekében független beállításokat végez minden egyes Z léptetőn. Az opcionális mérő paraméterekkel kapcsolatos részletekért lásd a PROBE parancsot. Az opcionális RETRIES, RETRY_TOLERANCE és HORIZONTAL_MOVE_Z értékek felülírják a konfigurációs fájlban megadott opciókat.
    
-
    [temperature_probe]
    
-
    A következő parancsok akkor érhetők el, ha a temperature_probe konfigurációs szakasz engedélyezve van.
    
-
    TEMPERATURE_PROBE_CALIBRATE
    
-
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Elindítja a szonda sodródásának kalibrálását örvényáram alapú szondákhoz. A TARGET az utolsó mérés célhőmérséklete. Ha a mérés során rögzített hőmérséklet meghaladja a TARGET kalibrációt, akkor a kalibráció befejeződik. A STEP paraméter beállítja a hőmérséklet-deltát (C-ban) a mérések között. A mérések után ez a delta a TEMPERATURE_PROBE_NEXT hívás ütemezésére szolgál. Az alapértelmezett STEP a 2.
    
-
    TEMPERATURE_PROBE_NEXT
    
-
    TEMPERATURE_PROBE_NEXT: A kalibrálás megkezdése után ez a parancs fut a következő méréshez. A rendszer automatikusan ütemezi a futást, amikor elérte a STEP által meghatározott delta értéket, de lehetséges manuálisan is futtatni ezt a parancsot egy új mérés kényszerítéséhez. Ez a parancs csak kalibrálás közben érhető el.
    
-
    TEMPERATURE_PROBE_COMPLETE:
    
-
    TEMPERATURE_PROBE_COMPLETE: A kalibráció befejezésére és az aktuális eredmény mentésére használható, mielőtt elérné a TARGET hőmérsékletet. Ez a parancs csak kalibrálás közben érhető el.
    
-
    ABORT
    
-
    ABORT: Megszakítja a kalibrálási folyamatot, elveti az aktuális eredményeket. Ez a parancs csak a drift-kalibráció során érhető el.
    
-
    TEMPERATURE_PROBE_ENABLE
    
-
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Be- vagy kikapcsolja a hőmérséklet-eltolás kompenzációját. Ha az ENGEDÉLYEZÉS 0-ra van állítva, az eltolás kompenzáció le lesz tiltva, ha 1-re van állítva, akkor engedélyezve van.
    
 
               
             
diff --git a/hu/Hall_Filament_Width_Sensor.html b/hu/Hall_Filament_Width_Sensor.html
index 36567973f..e21943a49 100644
--- a/hu/Hall_Filament_Width_Sensor.html
+++ b/hu/Hall_Filament_Width_Sensor.html
@@ -1357,8 +1357,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Installation.html b/hu/Installation.html
index e1c11b83b..8d9495383 100644
--- a/hu/Installation.html
+++ b/hu/Installation.html
@@ -1366,8 +1366,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
 
 
    Telepítés
    
-
    Ezek az utasítások feltételezik, hogy a szoftver egy linux alapú gazdagépen fut, ahol egy Klipper-kompatibilis frontend fut. Javasoljuk, hogy egy SBC(Small Board Computer), például egy Raspberry Pi vagy Debian alapú Linux eszköz legyen a gazdagép (lásd a GYIK más lehetőségeket).
    
-
    Ezen utasítások alkalmazásában a gazdagép a Linux eszközre, az MCU pedig a nyomtatólapra vonatkozik. Az SBC a Small Board Computer kifejezésre utal, mint például a Raspberry Pi.
    
+
    These instructions assume the software will run on a Linux-based host running a Klipper-compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian-based Linux device be used as the host machine (see the FAQ for other options).
    
+
    For the purposes of these instructions, host relates to the Linux device and mcu relates to the printer board. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
 
    Klipper konfigurációs fájl beszerzése
    
 
    A Klipper legtöbb beállítását a printer.cfg „nyomtató konfigurációs fájl” határozza meg, amely a gépen lesz tárolva. A megfelelő konfigurációs fájl gyakran úgy található meg, hogy a Klipper config könyvtárában keresünk egy „printer-” előtaggal kezdődő fájlt, amely megfelel a célnyomtatónak. A Klipper konfigurációs fájl tartalmazza a nyomtatóra vonatkozó technikai információkat, amelyekre a telepítés során szükség lesz.
    
 
    Ha nincs megfelelő nyomtató konfigurációs fájl a Klipper config könyvtárban, akkor keresd meg a nyomtató gyártójának weboldalát, hogy van-e megfelelő Klipper konfigurációs fájljuk.
    
@@ -1493,13 +1493,13 @@
 
    Jelenleg a legjobb választás a frontendek, amelyek a Moonraker web API segítségével kérik le az információkat, és lehetőség van az Octoprint használatára is a Klipper vezérléséhez.
    
 
    A felhasználó dönti el, hogy mit használ, de az alapjául szolgáló Klipper minden esetben ugyanaz. Arra bátorítjuk a felhasználókat, hogy kutassák fel a rendelkezésre álló lehetőségeket, és hozzanak megalapozott döntést.
    
 
    OS-kép beszerzése SBC-khez
    
-
    Számos módja van annak, hogy a Klipper SBC használatra szánt operációs rendszer képét megszerezd, a legtöbb attól függ, hogy milyen (front end-et) szeretnél használni. Az SBC lapok egyes gyártói saját Klipper-központú image-eket is biztosítanak.
    
-
    A két fő Moonraker alapú frontend a Fluidd és a Mainsail, az utóbbi rendelkezik egy előre elkészített telepítő image „MainsailOS”, ez tartalmazza a Raspberry Pi és néhány OrangePi variáns opciót.
    
+
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manufacturers of these SBC boards also provide their own Klipper-centric images.
    
+
    The two main Moonraker-based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi variants.
    
 
    A Fluidd telepíthető a KIAUH (Klipper Install And Update Helper) segítségével, amely az alábbiakban ismertetésre kerül, és egy harmadik féltől származó telepítő minden Klipper dologhoz.
    
 
    Az OctoPrint telepíthető a népszerű OctoPi képen keresztül vagy a KIAUH segítségével, ezt a folyamatot a  ismerteti.
    
 
    Telepítés a KIAUH-n keresztül
    
-
    Normális esetben az SBC alapképével kezd, például az RPiOS Lite-tal, vagy x86-os Linux eszköz esetén az Ubuntu Server-el. Kérjük, vedd figyelembe, hogy az asztali változatok nem ajánlottak bizonyos segédprogramok miatt, amelyek megakadályozhatják egyes Klipper funkciók működését, sőt, egyes nyomtatólapokhoz való hozzáférést is elfedhetik.
    
-
    A KIAUH használható a Klipper és a hozzá tartozó programok telepítésére különböző Linux alapú rendszerekre, amelyeken a Debian egy formája fut. További információ a https://github.com/dw-0/kiauh oldalon található.
    
+
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of an x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions from working and even mask access to some printer boards.
    
+
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux-based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
 
    A mikrokontroller felépítése és égetése
    
 
    A mikrokontroller kódjának lefordításához kezdj a következő parancsok futtatásával a gazdakészüléken:
    
 
    cd ~/klipper/
@@ -1510,7 +1510,7 @@ make menuconfig
 
    make
 
    
 
-
    Ha a nyomtató konfigurációs fájl tetején található megjegyzések egyéni lépéseket írnak le a "flash" végső képnek a nyomtató vezérlőpanelére történő égetéséhez, akkor kövesd ezeket a lépéseket, majd folytasd az OctoPrint konfigurálása lépésekkel.
    
+
    If the comments at the top of the printer configuration file describe custom steps for "flashing" the final image to the printer control board, then follow those steps and then proceed to configuring OctoPrint.
    
 
    Ellenkező esetben a következő lépéseket gyakran használják a nyomtató vezérlőlapjának "flash" égetésére. Először meg kell határozni a mikrokontrollerhez csatlakoztatott soros portot. Futtasd a következőket:
    
 
    ls /dev/serial/by-id/*
 
    
@@ -1520,8 +1520,8 @@ make menuconfig
 
    
 
 
    Gyakori, hogy minden nyomtatónak saját egyedi soros port neve van. Ez az egyedi név kerül felhasználásra a mikrokontroller égetésekor. Lehetséges, hogy a fenti kimeneten több sor is szerepel - ha igen, válaszd ki a mikrokontrollernek megfelelő sort. Ha több elem is szerepel a listában, és a választás nem egyértelmű, húzd ki a kártyát, és futtasd le újra a parancsot, a hiányzó elem a nyomtató alaplapod lesz(további információért lásd GYIK).
    
-
    Az STM32 vagy klón chipekkel, LPC chipekkel és más, gyakori mikrovezérlők esetében szokásos, hogy ezeknek SD-kártyán keresztül történő kezdeti Klipper flashelésre van szükségük.
    
-
    Ha ezzel a módszerrel égetsz, fontos, hogy a nyomtatópanel ne legyen USB-n keresztül csatlakoztatva a gazdagéphez, mivel egyes panelek képesek visszatáplálni a feszültséget, és megakadályozni az égetést.
    
+
    For common micro-controllers with STM32 or clone chips, LPC chips and others, it is usual that these need an initial Klipper flash via SD card.
    
+
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring.
    
 
    Az Atmega chipeket használó általános mikrovezérlők, például a 2560-asok esetében a kódot a következő módon lehet égetni:
    
 
    sudo service klipper stop
 make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
@@ -1538,9 +1538,9 @@ sudo service klipper start
 
    Fontos megjegyezni, hogy az RP2040 chipeket e művelet előtt Boot üzemmódba kell helyezni.
    
 
    A Klipper beállítása
    
 
    A következő lépés a nyomtató konfigurációs fájl átmásolása a gazdagépre.
    
-
    Vitathatatlanul a legegyszerűbb módja a Klipper konfigurációs fájl beállításának a Mainsail vagy a Fluidd beépített szerkesztőinek használata. Ezek lehetővé teszik a felhasználó számára, hogy megnyissa a konfigurációs példákat, és elmentse őket a printer.cfg fájlba.
    
+
    Arguably the easiest way to set the Klipper configuration file is using the built-in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
 
    Egy másik lehetőség egy olyan asztali szerkesztő használata, amely támogatja a fájlok szerkesztését az „scp” és/vagy „sftp” protokollokon keresztül. Vannak szabadon elérhető eszközök, amelyek támogatják ezt (pl. Notepad++, WinSCP és Cyberduck). Töltsd be a nyomtató konfigurációs fájlját a szerkesztőbe, majd mentsd el a „printer.cfg” nevű fájlként a PI felhasználó home könyvtárába (pl. /home/pi/printer.cfg).
    
-
    Alternatív megoldásként a fájlt közvetlenül az állomáson is lehet másolni és szerkeszteni SSH-n keresztül. Ez valahogy így nézhet ki (ügyelj arra, hogy a parancsot frissítsd a megfelelő nyomtató konfigurációs fájlnévvel):
    
+
    Alternatively, one can also copy and edit the file directly on the host via SSH. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
 
    cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
 nano ~/printer.cfg
 
    
@@ -1558,9 +1558,9 @@ nano ~/printer.cfg
 serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
 
    
 
-
    A fájl létrehozása és szerkesztése után a konfiguráció betöltéséhez szükséges lesz egy „restart” parancs kiadása a parancskonzolon. A „status” parancs azt jelenti, hogy a nyomtató készen áll, ha a Klipper config fájl sikeresen beolvasásra került, és a mikrokontroller sikeresen meg lett találva és konfigurálva.
    
+
    After creating and editing the file, it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report that the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
 
    A nyomtató konfigurációs fájljának testreszabásakor nem ritka, hogy a Klipper konfigurációs hibát jelez. Ha hiba lép fel, végezd el a szükséges javításokat a nyomtató konfigurációs fájljában, és add ki az "újraindítás" parancsot, amíg az "állapot" nem jelzi, hogy a nyomtató készen áll.
    
-
    A Klipper hibaüzeneteket jelent a parancsikonon és a Fluidd és Mainsail felugró ablakán keresztül. A „status” parancs használható a hibaüzenetek újbóli jelentésére. Egy napló is rendelkezésre áll, és általában a ~/printer_data/logs könyvtárban található, ennek a neve klippy.log.
    
+
    Klipper reports error messages via the command console and pop-ups in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located at ~/printer_data/logs/klippy.log.
    
 
    Miután a Klipper jelenti, hogy a nyomtató készen áll, folytasd a konfigurációs ellenőrzés című dokumentummal, hogy elvégezz néhány alapvető ellenőrzést a config fájlban lévő definíciókon. További információkért lásd a fő dokumentációs hivatkozás című rész.
    
 
               
diff --git a/hu/Kinematics.html b/hu/Kinematics.html
index f68ae5c07..68691031f 100644
--- a/hu/Kinematics.html
+++ b/hu/Kinematics.html
@@ -1411,8 +1411,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Load_Cell.html b/hu/Load_Cell.html
new file mode 100644
index 000000000..eec926813
--- /dev/null
+++ b/hu/Load_Cell.html
@@ -0,0 +1,1635 @@
+
+
+
+  
+    
+      
+      
+      
+      
+      
+      
+      
+    
+    
+      
+        Load Cells - Klipper dokumentáció
+      
+    
+    
+      
+      
+        
+        
+        
+      
+    
+    
+    
+      
+        
+        
+        
+        
+      
+    
+    
+      
+    
+    
+    
+      
+  
+
+
+  
+  
+
+
+  
+  
+
+
+    
+    
+  
+  
+  
+    
+    
+      
+    
+    
+    
+    
+    
+  
+    
+    
+      
+    
+    
+    
+    
+    
    
+      
+        
+        
+          Kihagyás
+        
+      
+    
    
+    
    
+      
+    
    
+    
+    
+      
+
+
    
+  
+  
+
    
+    
+    
    
+      
+      
+        
+          
+        
+      
+      
    
+        
    
+          
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+
+                  
    
+                
    
+              
    
+            
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+                  
    
+                
    
+              
    
+            
+          
+          
    
+            
    
+              
+                
+
+  
+
+
+
+
    Load Cells
    
+
    This document describes Klipper's support for load cells. Basic load cell functionality can be used to read force data and to weigh things like filament. A calibrated force sensor is an important part of a load cell based probe.
    
+
+
+
    Using LOAD_CELL_DIAGNOSTIC
    
+
    When you first connect a load cell its good practice to check for issues by running LOAD_CELL_DIAGNOSTIC. This tool collects 10 seconds of data from the load cell and resport statistics:
    
+
    $ LOAD_CELL_DIAGNOSTIC
+// Collecting load cell data for 10 seconds...
+// Samples Collected: 3211
+// Measured samples per second: 332.0
+// Good samples: 3211, Saturated samples: 0, Unique values: 900
+// Sample range: [4.01% to 4.02%]
+// Sample range / sensor capacity: 0.00524%
+
    
+
+
    Things you can check with this data:
    
+
      
+
    • The configured sample rate of the sensor should be close to the 'Measured samples per second' value. If it is not you may have a configuration or wiring issue.
      • 
+
    • 'Saturated samples' should be 0. If you have saturated samples it means the load sell is seeing more force than it can measure.
      • 
+
    • 'Unique values' should be a large percentage of the 'Samples Collected' value. If 'Unique values' is 1 it is very likely a wiring issue.
      • 
+
    • Tap or push on the sensor while LOAD_CELL_DIAGNOSTIC runs. If things are working correctly ths should increase the 'Sample range'.
      • 
+
    
+
    Calibrating a Load Cell
    
+
    Load cells are calibrated using the LOAD_CELL_CALIBRATE command. This is an interactive calibration utility that walks you though a 3 step process:
    
+
      
+
    1. First use the TARE command to establish the zero force value. This is the reference_tare_counts config value.
      2. 
+
    2. Next you apply a known load or force to the load cell and run the CALIBRATE GRAMS=nnn command. From this the counts_per_gram value is calculated. See the next section for some suggestions on how to do this.
      3. 
+
    3. Finally, use the ACCEPT command to save the results.
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    Applying a Known Force or Load
    
+
    The CALIBRATE GRAMS=nnn step can be accomplished in a number of ways. If your load cell is under a platform like a bed or filament holder it might be easiest to put a known mass on the platform. E.g. you could use a couple of 1KG filament spools.
    
+
    If your load cell is in the printer's toolhead a different approach is easier. Put a digital scale on the printers bed and gently lower the toolhead onto the scale (or raise the bed into the toolhead if your bed moves). You may be able to do this using the FORCE_MOVE command. But more likely you will have to manually moving the z axis with the motors off until the toolhead presses on the scale.
    
+
    A good calibration force would ideally be a large percentage of the load cell's rated capacity. E.g. if you have a 5Kg load cell you would ideally calibrate it with a 5kg mass. This might work well with under-bed sensors that have to support a lot of weight. For toolhead probes this may not be a load that your printer bed or toolhead can tolerate without damage. Do try to use at least 1Kg of force, most printers should tolerate this without issue.
    
+
    When calibrating make careful note of the values reported:
    
+
    $ CALIBRATE GRAMS=555
+// Calibration value: -2.78% (-59803108), Counts/gram: 73039.78739,
+Total capacity: +/- 29.14Kg
+
    
+
+
    The Total capacity should be close to the theoretical rating of the load cell based on the sensor's capacity. If it is much larger you could have used a higher gain setting in the sensor or a more sensitive load cell. This isn't as critical for 32bit and 24bit sensors but is much more critical for low bit width sensors.
    
+
    Reading Force Data
    
+
    Force data can be read with a GCode command:
    
+
    LOAD_CELL_READ
+// 10.6g (1.94%)
+
    
+
+
    Data is also continuously read and can be consumed from the load_cell printer object in a macro:
    
+
    {% set grams = printer.load_cell.force_g %}
+
    
+
+
    This provides an average force over the last 1 second, similar to how temperature sensors work.
    
+
    Taring a Load Cell
    
+
    Taring, sometimes called zeroing, sets the current weight reported by the load_cell to 0. This is useful for measuring relative to a known weight. e.g. when measuring a filament spool, using LOAD_CELL_TARE sets the weight to 0. Then as filament is printed the load_cell will report the weight of the filament used.
    
+
    LOAD_CELL_TARE
+// Load cell tare value: 5.32% (445903)
+
    
+
+
    The current tare value is reported in the printers status and can be read in a macro:
    
+
    {% set tare_counts = printer.load_cell.tare_counts %}
+
    
+
+              
+            
    
+          
    
+        
    
+        
+          
+            
+            Back to top
+          
+        
+      
    
+      
+        
+      
+    
    
+    
    
+      
    
+    
    
+    
+    
+    
+      
+      
+    
+  
+
\ No newline at end of file
diff --git a/hu/MCU_Commands.html b/hu/MCU_Commands.html
index d655324f9..bcf49fc7b 100644
--- a/hu/MCU_Commands.html
+++ b/hu/MCU_Commands.html
@@ -1383,8 +1383,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Manual_Level.html b/hu/Manual_Level.html
index 809873e70..e322edefe 100644
--- a/hu/Manual_Level.html
+++ b/hu/Manual_Level.html
@@ -1358,8 +1358,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/hu/Measuring_Resonances.html b/hu/Measuring_Resonances.html
index 57b2465b6..724ed3f3d 100644
--- a/hu/Measuring_Resonances.html
+++ b/hu/Measuring_Resonances.html
@@ -838,11 +838,11 @@
       
    
 
-
    The test was last run on commit f6718291 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.
    
+
    The test was last run on commit 14c105b8 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.
    
 
@@ -2226,11 +2226,11 @@ finalize_config crc=0
 
-
+
-
+
    
 
 
    
 
    
 1 stepper53
 
    
 
    
 3 stepper2214
 
    
     
 
    
@@ -2252,7 +2252,7 @@ finalize_config crc=0
 
 
 
-
    (*) 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.
    
+
    (*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 200Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 ARM core cycles.
    
 
    Benchmark step rate MCU Linux
    
 
    La seguente sequenza di configurazione viene utilizzata su un Raspberry Pi:
    
 
    allocate_oids count=3
diff --git a/it/Bootloader_Entry.html b/it/Bootloader_Entry.html
index e0817b026..e07724ac5 100644
--- a/it/Bootloader_Entry.html
+++ b/it/Bootloader_Entry.html
@@ -1429,8 +1429,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Bootloaders.html b/it/Bootloaders.html
index a70801d88..93278c8ef 100644
--- a/it/Bootloaders.html
+++ b/it/Bootloaders.html
@@ -1501,8 +1501,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/CANBUS.html b/it/CANBUS.html
index beca2f5e3..9887e2a75 100644
--- a/it/CANBUS.html
+++ b/it/CANBUS.html
@@ -1371,8 +1371,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1549,6 +1549,7 @@ iface can0 can static
 
 
 
      
+
    • It is only valid to use USB to CAN bridge mode if there is a functioning CAN bus with at least one other node available (in addition to the bridge node itself). Use a standard USB configuration if the goal is to communicate only with the single USB device. Using USB to CAN bridge mode without a fully functioning CAN bus (including terminating resistors and an additional node) may result in sporadic errors even when communicating with the bridge node.
      • 
 
    • A USB to CAN bridge board will not appear as a USB serial device, it will not show up when running ls /dev/serial/by-id, and it can not be configured in Klipper's printer.cfg file with a serial: parameter. The bridge board appears as a "USB CAN adapter" and it is configured in the printer.cfg as a CAN node.
      • 
 
    
 
    Tips for troubleshooting
    
diff --git a/it/CANBUS_Troubleshooting.html b/it/CANBUS_Troubleshooting.html
index a344c1b28..81eff345f 100644
--- a/it/CANBUS_Troubleshooting.html
+++ b/it/CANBUS_Troubleshooting.html
@@ -1284,6 +1284,13 @@
     Use an appropriate txqueuelen setting
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1370,8 +1377,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1444,6 +1451,13 @@
     Use an appropriate txqueuelen setting
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1500,12 +1514,16 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    Verify that all plugs and wire crimps on the CAN bus wiring are fully secured. Movement of the printer toolhead may jostle the CAN bus wiring causing a bad wire crimp or unsecured plug to result in intermittent communication errors.
    
 
    Check for incrementing bytes_invalid counter
    
 
    The Klipper log file will report a Stats line once a second when the printer is active. These "Stats" lines will have a bytes_invalid counter for each micro-controller. This counter should not increment during normal printer operation (it is normal for the counter to be non-zero after a RESTART and it is not a concern if the counter increments once a month or so). If this counter increments on a CAN bus micro-controller during normal printing (it increments every few hours or more frequently) then it is an indication of a severe problem.
    
-
    Incrementing bytes_invalid on a CAN bus connection is a symptom of reordered messages on the CAN bus. There are two known causes of reordered messages:
    
-
      
-
    1. Old versions of the popular candlight_firmware for USB CAN adapters had a bug that could cause reordered messages. If using a USB CAN adapter running this firmware then make sure to update to the latest firmware if incrementing bytes_invalid is observed.
      2. 
-
    2. Some Linux kernel builds for embedded devices have been known to reorder CAN bus messages. It may be necessary to use an alternative Linux kernel or to use alternative hardware that supports mainstream Linux kernels that do not exhibit this problem.
      3. 
-
    
-
    Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print.
    
+
    Incrementing bytes_invalid on a CAN bus connection is a symptom of reordered messages on the CAN bus. If seen, make sure to:
    
+
      
+
    • Use a Linux kernel version 6.6.0 or later.
      • 
+
    • If using a USB-to-CANBUS adapter running candlelight firmware, use v2.0 or later of candleLight_fw.
      • 
+
    • If using Klipper's USB-to-CANBUS bridge mode, make sure the bridge node is flashed with Klipper v0.12.0 or later.
      • 
+
    
+
    Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print. An incrementing bytes_invalid is not caused by wiring or similar hardware issues and can only be fixed by identifying and updating the faulty software.
    
+
    Older versions of the Linux kernel had a bug in the gs_usb canbus driver code that could cause reordered canbus packets. The issue is thought to be fixed in Linux commit 24bc41b4 which was released in v6.6.0. In some cases, older Linux versions may not show the problem (due to how hardware interrupts are configured), however if problems are seen the recommended solution is to upgrade to a newer kernel.
    
+
    Older versions of candlelight firmware could reorder canbus packets, and the issue is thought to be fixed in candlelight_fw commit 8b3a7b45.
    
+
    Older versions of Klipper's USB-to-CANBUS bridge code could incorrectly drop canbus messages. This is not as severe as reordering messages, but it should still be fixed. It is thought to be fixed with Klipper PR #6175.
    
 
    Use an appropriate txqueuelen setting
    
 
    The Klipper code uses the Linux kernel to manage CAN bus traffic. By default, the kernel will only queue 10 CAN transmit packets. It is recommended to configure the can0 device with a txqueuelen 128 to increase that size.
    
 
    If Klipper transmits a packet and Linux has filled all of its transmit queue space then Linux will drop that packet and messages like the following will appear in the Klipper log:
    
@@ -1517,6 +1535,10 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    One may check the current queue size by running the Linux command ip link show can0. It should report a bunch of text including the snippet qlen 128. If one sees something like qlen 10 then it indicates the CAN device has not been properly configured.
    
 
    It is not recommended to use a txqueuelen significantly larger than 128. A CAN bus running at a frequency of 1000000 will typically take around 120us to transmit a CAN packet. Thus a queue of 128 packets is likely to take around 15-20ms to drain. A substantially larger queue could cause excessive spikes in message round-trip-time which could lead to unrecoverable errors. Said another way, Klipper's application retransmit system is more robust if it does not have to wait for Linux to drain an excessively large queue of possibly stale data. This is analogous to the problem of bufferbloat on internet routers.
    
 
    Under normal circumstances Klipper may utilize ~25 queue slots per MCU - typically only utilizing more slots during retransmits. (Specifically, the Klipper host may transmit up to 192 bytes to each Klipper MCU before receiving an acknowledgment from that MCU.) If a single CAN bus has 5 or more Klipper MCUs on it, then it might be necessary to increase the txqueuelen above the recommended value of 128. However, as above, care should be taken when selecting a new value to avoid excessive round-trip-time latency.
    
+
    Use canbus_query.py only to identify nodes never previously seen
    
+
    It is only valid to use the canbus_query.py tool to identify micro-controllers that have never been previously identified. Once all nodes on a bus are identified, record the resulting uuids in the printer.cfg, and avoid running the tool unnecessarily.
    
+
    The tool is implemented using a low-level mechanism that can cause nodes to internally observe bus errors. These internal errors may result in communication interruptions and may result is some nodes disconnecting from the bus.
    
+
    It is not valid to use the tool to "ping" if a node is connected. Do not run the tool during an active print.
    
 
    Obtaining candump logs
    
 
    The CAN bus messages sent to and from the micro-controller are handled by the Linux kernel. It is possible to capture these messages from the kernel for debugging purposes. A log of these messages may be of use in diagnostics.
    
 
    The Linux can-utils tool provides the capture software. It is typically installed on a machine by running:
    
diff --git a/it/CANBUS_protocol.html b/it/CANBUS_protocol.html
index 8a282636c..4ba47b8e2 100644
--- a/it/CANBUS_protocol.html
+++ b/it/CANBUS_protocol.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/CONTRIBUTING.html b/it/CONTRIBUTING.html
index f9b1cb7b3..bb6db9893 100644
--- a/it/CONTRIBUTING.html
+++ b/it/CONTRIBUTING.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Code_Overview.html b/it/Code_Overview.html
index 0c212d25c..2cfac63b5 100644
--- a/it/Code_Overview.html
+++ b/it/Code_Overview.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Command_Templates.html b/it/Command_Templates.html
index 741c1575a..a1b348614 100644
--- a/it/Command_Templates.html
+++ b/it/Command_Templates.html
@@ -1421,8 +1421,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Config_Changes.html b/it/Config_Changes.html
index 33eae67ba..82e847c65 100644
--- a/it/Config_Changes.html
+++ b/it/Config_Changes.html
@@ -1327,8 +1327,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1410,6 +1410,12 @@
 
    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.
    
 
    Tutte le date in questo documento sono approssimative.
    
 
    Cambiamenti
    
+
    20250428: The maximum cycle_time for pwm [output_pin], [pwm_cycle_time], [pwm_tool], and similar config sections is now 3 seconds (reduced from 5 seconds). The maximum_mcu_duration in [pwm_tool] is now also 3 seconds.
    
+
    20250418: The manual_stepper STOP_ON_ENDSTOP feature may now take less time to complete. Previously, the command would wait the entire time the move could possibly take even if the endstop triggered earlier. Now, the command finishes shortly after the endstop trigger.
    
+
    20250417: SPI devices using "software SPI" are now rate limited. Previously, the spi_speed in the config was ignored and the transmission speed was only limited by the processing speed of the micro-controller. Now, speeds are limited by the spi_speed config parameter (actual hardware speeds are likely to be lower than the configured value due to software overhead).
    
+
    20250411: Klipper v0.13.0 released.
    
+
    20250308: The AUTO parameter of the AXIS_TWIST_COMPENSATION_CALIBRATE command has been removed.
    
+
    20250131: Option VARIABLE=<name> in SAVE_VARIABLE requires lowercase value. For example, extruder instead of mixedcase Extruder or uppercase EXTRUDER. Using any uppercase letter will raise an error.
    
 
    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 sweeping_period: 0 and accel_per_hz: 75 to the [resonance_tester] config section.
    
 
    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.
    
 
    20241112: Option CHIPS=<chip_name> in TEST_RESONANCES and SHAPER_CALIBRATE requires specifying the full name(s) of the accel chip(s). For example, adxl345 rpi instead of short name - rpi.
    
diff --git a/it/Config_Reference.html b/it/Config_Reference.html
index 029e480a2..cd5fd5176 100644
--- a/it/Config_Reference.html
+++ b/it/Config_Reference.html
@@ -931,6 +931,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -1741,6 +1748,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -2600,8 +2614,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3053,6 +3067,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -3863,6 +3884,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -5331,6 +5359,22 @@ cs_pin:
 #   measurements.
 
    • 
 
+
    [icm20948]
    
+
    Support for icm20948 accelerometers.
    
+
    [icm20948]
+#i2c_address:
+#   Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
+#i2c_mcu:
+#i2c_bus:
+#i2c_software_scl_pin:
+#i2c_software_sda_pin:
+#i2c_speed: 400000
+#   See the "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.
+
    
+
 
    [lis2dw]
    
 
    Support for LIS2DW accelerometers.
    
 
    [lis2dw]
@@ -5664,6 +5708,9 @@ z_offset:
 sensor_type: ldc1612
 #   The sensor chip used to perform eddy current measurements. This
 #   parameter must be provided and must be set to ldc1612.
+#frequency:
+#   The external crystal frequency (in Hz) of the LDC1612 chip.
+#   The default is 12000000.
 #intb_pin:
 #   MCU gpio pin connected to the ldc1612 sensor's INTB pin (if
 #   available). The default is to not use the INTB pin.
@@ -6613,22 +6660,27 @@ pin:
 
    Esegui gcode quando un pulsante viene premuto o rilasciato (o quando un pin cambia stato). Puoi controllare lo stato del pulsante usando QUERY_BUTTON button=my_gcode_button.
    
 
    [gcode_button my_gcode_button]
 pin:
-#   Il pin su cui è collegato il pulsante. Questo parametro deve essere fornito.
+#   The pin on which the button is connected. This parameter must be
+#   provided.
 #analog_range:
-#   Due resistenze separate da virgole (in Ohm) che specificano l'intervallo
-#   di resistenza minimo e massimo per il pulsante. Se viene fornito
-#   analog_range, il pin deve essere un pin con capacità analogica.
-#   L'impostazione predefinita è utilizzare digital gpio per il pulsante.
+#   Two comma separated resistances (in Ohms) specifying the minimum
+#   and maximum resistance range for the button. If analog_range is
+#   provided then the pin must be an analog capable pin. The default
+#   is to use digital gpio for the button.
 #analog_pullup_resistor:
-#   La resistenza di pullup (in Ohm) quando è specificato analog_range.
-#   Il valore predefinito è 4700 ohm.
+#   The pullup resistance (in Ohms) when analog_range is specified.
+#   The default is 4700 ohms.
 #press_gcode:
-#   Un elenco di comandi G-Code da eseguire quando si preme il pulsante.
-#   I modelli G-Code sono supportati. Questo parametro deve essere fornito.
+#   A list of G-Code commands to execute when the button is pressed.
+#   G-Code templates are supported. This parameter must be provided.
 #release_gcode:
-#   Un elenco di comandi G-Code da eseguire quando il pulsante viene
-#   rilasciato. I modelli G-Code sono supportati. L'impostazione predefinita
-#   è di non eseguire alcun comando al rilascio di un pulsante.
+#   A list of G-Code commands to execute when the button is released.
+#   G-Code templates are supported. The default is to not run any
+#   commands on a button release.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   button gcode. If the button is pressed and released during this
+#   delay, the entire button press is ignored. Default is 0.
 
    
 
 
    [output_pin]
    
@@ -6762,8 +6814,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -6812,6 +6865,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 4
 #driver_PWM_AMPL: 128
+#driver_FREEWHEEL: 0
 #driver_SGT: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6869,8 +6923,9 @@ run_current:
 #stealthchop_threshold: 0
 #   The velocity (in mm/s) to set the "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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #driver_MULTISTEP_FILT: True
 #driver_IHOLDDELAY: 8
 #driver_TPOWERDOWN: 20
@@ -6885,6 +6940,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #   Set the given register during the configuration of the TMC2208
 #   chip. This may be used to set custom motor parameters. The
 #   defaults for each parameter are next to the parameter name in the
@@ -6928,6 +6984,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #driver_SGTHRS: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -7055,8 +7112,9 @@ run_current:
 #stealthchop_threshold: 0
 #   The velocity (in mm/s) to set the "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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7183,8 +7241,9 @@ run_current:
 #stealthchop_threshold: 0
 #   The velocity (in mm/s) to set the "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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7785,34 +7844,37 @@ text:
 
    Per ulteriori informazioni, vedere command reference.
    
 
    [filament_switch_sensor my_sensor]
 #pause_on_runout: True
-#   Se impostato su True, verrà eseguita una PAUSA immediatamente
-#   dopo il rilevamento di un'eccentricità. Si noti che se pause_on_runout
-#   è False e runout_gcode viene omesso, il rilevamento dell'eccentricità
-#   è disabilitato. L'impostazione predefinita è Vero.
+#   When set to True, a PAUSE will execute immediately after a runout
+#   is detected. Note that if pause_on_runout is False and the
+#   runout_gcode is omitted then runout detection is disabled. Default
+#   is True.
 #runout_gcode:
-#   Un elenco di comandi G-Code da eseguire dopo il rilevamento di
-#   un'esaurimento del filamento. Vedi docs/Command_Templates.md
-#   per il formato G-Code. Se pause_on_runout è impostato su True,
-#   questo codice G verrà eseguito al termine della PAUSA.
-#   L'impostazione predefinita è di non eseguire alcun comando G-Code.
+#   A list of G-Code commands to execute after a filament runout is
+#   detected. See docs/Command_Templates.md for G-Code format. If
+#   pause_on_runout is set to True this G-Code will run after the
+#   PAUSE is complete. The default is not to run any G-Code commands.
 #insert_gcode:
-#   Un elenco di comandi G-Code da eseguire dopo il rilevamento
-#   dell'inserimento di filamento. Vedi docs/Command_Templates.md
-#   per il formato G-Code. L'impostazione predefinita non prevede
-#   l'esecuzione di alcun comando G-Code, che disabilita il rilevamento
-#   dell'inserimento.
+#   A list of G-Code commands to execute after a filament insert is
+#   detected. See docs/Command_Templates.md for G-Code format. The
+#   default is not to run any G-Code commands, which disables insert
+#   detection.
 #event_delay: 3.0
-#   Il tempo minimo in secondi per ritardare tra gli eventi. Gli eventi
-#   attivati durante questo periodo di tempo verranno ignorati
-#   silenziosamente. L'impostazione predefinita è 3 secondi.
+#   The minimum amount of time in seconds to delay between events.
+#   Events triggered during this time period will be silently
+#   ignored. The default is 3 seconds.
 #pause_delay: 0.5
-#   Il tempo di ritardo, in secondi, tra l'invio del comando pause e
-#   l'esecuzione di runout_gcode. Potrebbe essere utile aumentare
-#   questo ritardo se OctoPrint mostra uno strano comportamento
-#   di pausa. Il valore predefinito è 0,5 secondi.
+#   The amount of time to delay, in seconds, between the pause command
+#   dispatch and execution of the runout_gcode. It may be useful to
+#   increase this delay if OctoPrint exhibits strange pause behavior.
+#   Default is 0.5 seconds.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   switch gcode. The switch must he held in a single state for at least
+#   this long to activate. If the switch is toggled on/off during this delay,
+#   the event is ignored. Default is 0.
 #switch_pin:
-#   Il pin su cui è collegato l'interruttore.
-#   Questo parametro deve essere fornito.
+#   The pin on which the switch is connected. This parameter must be
+#   provided.
 
    
 
 
    [filament_motion_sensor]
    
@@ -7907,6 +7969,16 @@ L'impostazione predefinita è disabilitare.
 
    [load_cell]
 sensor_type:
 #   This must be one of the supported sensor types, see below.
+#counts_per_gram:
+#   The floating point number of sensor counts that indicates 1 gram of force.
+#   This value is calculated by the LOAD_CELL_CALIBRATE command.
+#reference_tare_counts:
+#   The integer tare value, in raw sensor counts, taken when LOAD_CELL_CALIBRATE
+#   is run. This is the default tare value when klipper starts up.
+#sensor_orientation:
+#   Change the sensor's orientation. Can be either 'normal' or 'inverted'.
+#   The default is 'normal'. Use 'inverted' if the sensor reports a
+#   decreasing force value when placed under load.
 
    
 
 
    HX711
    
@@ -8056,6 +8128,38 @@ vssa_pin:
 #   noise. The default is 2 seconds.
 
    
 
+
    [ads1x1x]
    
+
    ADS1013, ADS1014, ADS1015, ADS1113, ADS1114 and ADS1115 are I2C based Analog to Digital Converters that can be used for temperature sensors. They provide 4 analog input pins either as single line or as differential input.
    
+
    Note: Use caution if using this sensor to control heaters. The heater min_temp and max_temp are only verified in the host and only if the host is running and operating normally. (ADC inputs directly connected to the micro-controller verify min_temp and max_temp within the micro-controller and do not require a working connection to the host.)
    
+
    [ads1x1x my_ads1x1x]
+chip: ADS1115
+#pga: 4.096V
+#   Default value is 4.096V. The maximum voltage range used for the input. This
+#   scales all values read from the ADC. Options are: 6.144V, 4.096V, 2.048V,
+#   1.024V, 0.512V, 0.256V
+#adc_voltage: 3.3
+#   The suppy voltage for the device. This allows additional software scaling
+#   for all values read from the ADC.
+i2c_mcu: host
+i2c_bus: i2c.1
+#address_pin: GND
+#   Default value is GND.  There can be up to four addressed devices depending
+#   upon wiring of the device. Check the datasheet for details. The i2c_address
+#   can be specified directly instead of using the address_pin.
+
    
+
+
    The chip provides pins that can be used on other sensors.
    
+
    sensor_type: ...
+#   Can be any thermistor or adc_temperature.
+sensor_pin: my_ads1x1x:AIN0
+#   A combination of the name of the ads1x1x chip and the pin. Possible
+#   pin values are AIN0, AIN1, AIN2 and AIN3 for single ended lines and
+#   DIFF01, DIFF03, DIFF13 and DIFF23 for differential between their
+#   correspoding lines. For example
+#   DIFF03 measures the differential between line 0 and 3. Only specific
+#   combinations for the differentials are allowed.
+
    
+
 
    [replicape]
    
 
    Supporto per Replicape: vedere la guida beaglebone e il file generic-replicape.cfg per un esempio.
    
 
    # La sezione di configurazione "replicape" aggiunge i pin di abilitazione
@@ -8125,7 +8229,7 @@ host_mcu:
 
    Supporto multimateriale Palette 2: fornisce un'integrazione più stretta supportando i dispositivi Palette 2 in modalità connessa.
    
 
    Questo modulo richiede anche [virtual_sdcard] e [pause_resume] per la piena funzionalità.
    
 
    Se si utilizza questo modulo, non utilizzare il plug-in Palette 2 per Octoprint poiché entreranno in conflitto e 1 non si inizializzerà correttamente, probabilmente interrompendo la stampa.
    
-
    Se utilizzi Octoprint e esegui lo streaming di gcode sulla porta seriale invece di stampare da virtual_sd, rimuovere M1 e M0 da Pausa dei comandi in Impostazioni > Connessione seriale > Firmware e protocollo eviterà la necessità per avviare la stampa sulla tavolozza 2 e riattivare la pausa in Octoprint per avviare la stampa.
    
+
    If you use Octoprint and stream gcode over the serial port instead of printing from virtual_sd, then remove M1 and M0 from Pausing commands in Settings > Serial Connection > Firmware & protocol will prevent the need to start print on the Palette 2 and unpausing in Octoprint for your print to begin.
    
 
    [palette2]
 serial:
 #   The serial port to connect to the Palette 2.
diff --git a/it/Config_checks.html b/it/Config_checks.html
index 451f2f339..5eee884fa 100644
--- a/it/Config_checks.html
+++ b/it/Config_checks.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Contact.html b/it/Contact.html
index 35ab91481..9b1282eef 100644
--- a/it/Contact.html
+++ b/it/Contact.html
@@ -451,8 +451,8 @@
 
       
         
  • 
-  
-    Klipper github
+  
+    Professional Services
   
   
 
    • 
@@ -1376,8 +1376,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
       
         
  • 
-  
-    Klipper github
+  
+    Professional Services
   
   
 
    • 
@@ -1558,9 +1558,10 @@
 
    Sto apportando modifiche che vorrei includere in Klipper
    
 
    Klipper è un software open-source e apprezziamo i nuovi contributi.
    
 
    I nuovi contributi (sia per il codice che per la documentazione) vengono inviati tramite Github Pull Requests. Vedere [CONTRIBUTING document per informazioni importanti.
    
-
    Ci sono diversi documenti per sviluppatori. Se hai domande sul codice, puoi anche chiedere nel Klipper Community Forum o nella Klipper Community Discord.
    
-
    Klipper github
    
-
    Klipper github può essere utilizzato dai contributori per condividere lo stato del loro lavoro per migliorare Klipper. Ci si aspetta che la persona che apre un ticket github stia lavorando attivamente all'attività specificata e sarà quella che eseguirà tutto il lavoro necessario per realizzarla. Il github di Klipper non viene utilizzato per richieste, né per segnalare bug, né per porre domande. Usa invece il Klipper Community Forum o la Klipper Community Discord.
    
+
    There are several documents for developers. If you have questions on the code then you can also ask in the Klipper Discourse Forum or on the Klipper Discord Chat.
    
+
    Professional Services
    
+
    
+
    Custom software development, software support, and solutions: https://ko-fi.com/koconnor
    
 
               
             
diff --git a/it/Debugging.html b/it/Debugging.html
index 59c63c469..0f82d1679 100644
--- a/it/Debugging.html
+++ b/it/Debugging.html
@@ -1384,8 +1384,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Delta_Calibrate.html b/it/Delta_Calibrate.html
index 0bf4935f8..1c1b0f5de 100644
--- a/it/Delta_Calibrate.html
+++ b/it/Delta_Calibrate.html
@@ -1365,8 +1365,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Eddy_Probe.html b/it/Eddy_Probe.html
index 6a6306e4e..39979e964 100644
--- a/it/Eddy_Probe.html
+++ b/it/Eddy_Probe.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1487,13 +1487,13 @@
       
       
         
-        
  • 
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Example_Configs.html b/it/Example_Configs.html
index 40418baa9..e066bd122 100644
--- a/it/Example_Configs.html
+++ b/it/Example_Configs.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Exclude_Object.html b/it/Exclude_Object.html
index dc3994a5e..7a3b82075 100644
--- a/it/Exclude_Object.html
+++ b/it/Exclude_Object.html
@@ -1356,8 +1356,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/FAQ.html b/it/FAQ.html
index c80a567f4..34ddc001d 100644
--- a/it/FAQ.html
+++ b/it/FAQ.html
@@ -1488,8 +1488,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Features.html b/it/Features.html
index 44aff0852..320093a74 100644
--- a/it/Features.html
+++ b/it/Features.html
@@ -1334,8 +1334,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1443,18 +1443,18 @@
 
  • Supporto G-code standard. Sono supportati i comandi G-code comuni prodotti dai tipici "slicer" (SuperSlicer, Cura, PrusaSlicer, ecc.).
    • 
 
  • Supporto per più estrusori. Sono supportati anche estrusori con riscaldatori condivisi ed estrusori su carrelli indipendenti (IDEX).
    • 
 
  • Supporto per stampanti cartesiane, delta, corexy, corexz, hybrid-corexy, hybrid-corexz, deltesian, rotary delta, polar e cable winch.
    • 
-
  • Supporto per il livellamento automatico del letto. Klipper può essere configurato per il rilevamento di base dell'inclinazione del piatto o per il livellamento del piatto a mesh completa. Se il piatto utilizza più stepper Z, Klipper può anche livellare manipolando in modo indipendente gli stepper Z. Sono supportate la maggior parte delle sonde di altezza Z, comprese le sonde BL-Touch e le sonde servoattivate.
    • 
+
  • Automatic bed leveling support. Klipper can be configured for basic bed tilt detection or full mesh bed leveling. The bed mesh can be customized to the print size (adaptive bed mesh). If the bed uses multiple Z steppers then Klipper can also level by independently manipulating the Z steppers. Most Z height probes are supported, including BL-Touch probes and servo activated probes. Probes may be calibrated for axis twist compensation. If using an "eddy current probe" then one can utilize fast bed mesh scanning,
    • 
 
  • Supporto per la calibrazione delta automatica. Lo strumento di calibrazione può eseguire la calibrazione dell'altezza di base e una calibrazione avanzata delle dimensioni X e Y. La calibrazione può essere eseguita con una sonda di altezza Z o tramite tastatura manuale.
    • 
 
  • Supporto "escludi oggetto" in fase di esecuzione. Se configurato, questo modulo può facilitare l'annullamento di un solo oggetto in una stampa multiparte.
    • 
-
  • Supporto per sensori di temperatura comuni (ad es. termistori comuni, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20 e LM75). È inoltre possibile configurare termistori personalizzati e sensori di temperatura analogici personalizzati. È possibile monitorare il sensore di temperatura del microcontrollore interno e il sensore di temperatura interna di un Raspberry Pi.
    • 
+
  • Support for common temperature sensors (eg, common thermistors, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20, AHT10, SHT3x, and LM75). Custom thermistors and custom analog temperature sensors can also be configured. One can monitor the internal micro-controller temperature sensor and the internal temperature sensor of a Raspberry Pi.
    • 
 
  • Protezione del riscaldatore termico di base abilitata di default.
    • 
-
  • Supporto per ventole standard, ventole per ugelli e ventole a temperatura controllata. Non è necessario mantenere le ventole in funzione quando la stampante è inattiva. La velocità della ventola può essere monitorata su ventole dotate di contagiri.
    • 
+
  • Support for standard fans, nozzle fans, and temperature controlled fans. No need to keep fans running when the printer is idle. Fan speed can be monitored on fans that have a tachometer. One can assign a "math formula" to a fan for automatic fan speed updating.
    • 
 
  • Supporto per la configurazione in fase di esecuzione dei driver per motori passo-passo TMC2130, TMC2208/TMC2224, TMC2209, TMC2660 e TMC5160. È inoltre disponibile il supporto per il controllo corrente dei tradizionali driver passo-passo tramite i pin AD5206, DAC084S085, MCP4451, MCP4728, MCP4018 e PWM.
    • 
 
  • Supporto per comuni display LCD collegati direttamente alla stampante. È disponibile anche un menu predefinito. Il contenuto del display e del menu può essere completamente personalizzato tramite il file di configurazione.
    • 
 
  • Accelerazione costante e supporto "look-ahead". Tutti i movimenti della stampante accelereranno gradualmente dall'arresto alla velocità di crociera, quindi decelereranno fino all'arresto. Il flusso in entrata dei comandi di movimento del G-code viene messo in coda e analizzato: l'accelerazione tra i movimenti in una direzione simile sarà ottimizzata per ridurre gli arresti di stampa e migliorare il tempo di stampa complessivo.
    • 
 
  • Klipper implementa un algoritmo "stepper phase endstop" che può migliorare la precisione dei tipici interruttori endstop. Se regolato correttamente, può migliorare l'adesione del primo strato di stampa.
    • 
 
  • Supporto per sensori di presenza del filamento, sensori di movimento del filamento e sensori di larghezza del filamento.
    • 
-
  • Supporto per misurare e registrare l'accelerazione utilizzando gli accelerometri adxl345, mpu9250 e mpu6050.
    • 
+
  • Support for measuring and recording acceleration using adxl345, mpu9250, mpu6050, lis2dw12, lis3dh, and icm20948 accelerometers.
    • 
 
  • Supporto per limitare la velocità massima di brevi spostamenti a "zigzag" per ridurre le vibrazioni e il rumore della stampante. Per ulteriori informazioni, vedere il documento cinematica.
    • 
 
  • Sono disponibili file di configurazione di esempio per molte stampanti comuni. Controllare la directory di configurazione per un elenco.
    • 
 
@@ -1526,11 +1526,6 @@
 1622K
 
 
-RP2040
-2400K
-1636K
-
-
 SAM4E8E
 2500K
 1674K
@@ -1556,6 +1551,11 @@
 2634K
 
 
+RP2040
+4000K
+2571K
+
+
 RP2350
 4167K
 2663K
@@ -1566,9 +1566,9 @@
 4737K
 
 
-STM32H743
-9091K
-6061K
+STM32H723
+7429K
+8619K
 
 
 
diff --git a/it/G-Codes.html b/it/G-Codes.html
index a630a7b73..c7c99bacc 100644
--- a/it/G-Codes.html
+++ b/it/G-Codes.html
@@ -1620,6 +1620,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -1694,33 +1756,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1789,26 +1824,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1850,6 +1865,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -2281,6 +2316,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -2429,54 +2512,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -3006,8 +3041,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3881,6 +3916,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -3955,33 +4052,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4050,26 +4120,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4111,6 +4161,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -4542,6 +4612,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -4690,54 +4808,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -4831,11 +4901,10 @@
 
    The following commands are available when the axis_twist_compensation config
 section is enabled.
    
 
    AXIS_TWIST_COMPENSATION_CALIBRATE
    
-
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]
    
+
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [SAMPLE_COUNT=<value>]
    
 
    Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.
    
 
      
 
    • AXIS: Define the axis (X or Y) for which the twist compensation will be calibrated. If not specified, the axis defaults to 'X'.
      • 
-
    • AUTO: Enables automatic calibration mode. When AUTO=True, the calibration will run for both the X and Y axes. In this mode, AXIS cannot be specified. If both AXIS and AUTO are provided, an error will be raised.
      • 
 
    
 
    [bed_mesh]
    
 
    I seguenti comandi sono disponibili quando la sezione di configurazione bed_mesh è abilitata (consultare anche la guida della mesh del letto).
    
@@ -4965,7 +5034,10 @@ section is enabled.
    
 
    FORCE_MOVE
    
 
    FORCE_MOVE STEPPER=<nome_config> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>]: 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.
    
 
    SET_KINEMATIC_POSITION
    
-
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]: 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.
    
+
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [SET_HOMED=<[X][Y][Z]>] [CLEAR_HOMED=<[X][Y][Z]>]: Force the low-level kinematic code to believe the toolhead is at the given cartesian position and set/clear homed status. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. Setting an incorrect or invalid position may lead to internal software errors.
    
+
    The X, Y, and Z parameters are used to alter the low-level kinematic position tracking. If any of these parameters are not set then the position is not changed - for example SET_KINEMATIC_POSITION Z=10 would set all axes as homed, set the internal Z position to 10, and leave the X and Y positions unchanged. Changing the internal position tracking is not dependent on the internal homing state - one may alter the position for both homed and not homed axes, and similarly one may set or clear the homing state of an axis without altering its internal position.
    
+
    The SET_HOMED parameter defaults to XYZ which instructs the kinematics to consider all axes as homed. A bare SET_KINEMATIC_POSITION command will result in all axes being considered homed (and not change its current position). If it is not desired to change the state of homed axes then assign SET_HOMED to an empty string - for example: SET_KINEMATIC_POSITION SET_HOMED= X=10. It is also possible to request an individual axis be considered homed (eg, SET_HOMED=X), but note that non-cartesian style kinematics (such as delta kinematics) may not support setting an individual axis as homed.
    
+
    The CLEAR_HOMED parameter instructs the kinematics to consider the given axes as not homed. For example, CLEAR_HOMED=XYZ would request all axes to be considered not homed (and thus require homing prior to movement on those axes). The default is SET_HOMED=XYZ even if CLEAR_HOMED is present, so the command SET_KINEMATIC_POSITION CLEAR_HOMED=Z will set X and Y as homed and clear the homing state for Z. Use SET_KINEMATIC_POSITION SET_HOMED= CLEAR_HOMED=Z if the goal is to clear only the Z homing state. If an axis is specified in neither SET_HOMED nor CLEAR_HOMED then its homing state is not changed and if it is specified in both then CLEAR_HOMED has precedence. It is possible to request clearing of an individual axis, but on non-cartesian style kinematics (such as delta kinematics) doing so may result in clearing the homing state of additional axes. Note the CLEAR parameter is currently an alias for the CLEAR_HOMED parameter, but this alias will be removed in the future.
    
 
    [gcode]
    
 
    Il modulo gcode viene caricato automaticamente.
    
 
    RESTART
    
@@ -5028,6 +5100,28 @@ section is enabled.
    
 
    Il comando seguente è abilitato se è stata abilitata una sezione di configurazione di input_shaper (consultare anche la guida alla compensazione della risonanza).
    
 
    SET_INPUT_SHAPER
    
 
    SET_INPUT_SHAPER [SHAPER_FREQ_X=<shaper_freq_x>] [SHAPER_FREQ_Y=<shaper_freq_y>] [DAMPING_RATIO_X=<damping_ratio_x>] [DAMPING_RATIO_Y=<damping_ratio_y>] [SHAPER_TYPE=<shaper>] [SHAPER_TYPE_X=<shaper_type_x>] [SHAPER_TYPE=<shaper_TYPE_X=<shaper_type_x>] [SHAPER_TYPE=<shaper_type_y=<shaper_type_x> ]: Modifica i parametri dell'input shaper. Si noti che il parametro SHAPER_TYPE reimposta l'input shaper per entrambi gli assi X e Y anche se sono stati configurati tipi di shaper diversi nella sezione [input_shaper]. SHAPER_TYPE non può essere utilizzato insieme a uno dei parametri SHAPER_TYPE_X e SHAPER_TYPE_Y. Vedere config reference per maggiori dettagli su ciascuno di questi parametri.
    
+
    [led]
    
+
    Il comando seguente è disponibile quando una qualsiasi delle sezioni di configurazione led è abilitata.
    
+
    SET_LED
    
+
    SET_LED LED=<nome_config> ROSSO=<valore> VERDE=<valore> BLU=<valore> BIANCO=<valore> [INDEX=<indice>] [TRANSMIT=0] [SYNC=1]: Imposta il LED in output. Ogni colore <valore> deve essere compreso tra 0,0 e 1,0. L'opzione BIANCO è valida solo su LED RGBW. Se il LED supporta più chip in una catena daisy-chain, è possibile specificare INDEX per modificare il colore del solo chip specificato (1 per il primo chip, 2 per il secondo, ecc.). Se INDEX non viene fornito, tutti i LED nella catena verranno impostati sul colore fornito. Se viene specificato TRANSMIT=0, il cambio colore verrà effettuato solo sul successivo comando SET_LED che non specifica TRANSMIT=0; questo può essere utile in combinazione con il parametro INDEX per raggruppare più aggiornamenti in una catena. Per impostazione predefinita, il comando SET_LED sincronizzerà le modifiche con altri comandi gcode in corso. Ciò può comportare un comportamento indesiderato se i LED vengono impostati mentre la stampante non sta stampando in quanto reimposta il timeout di inattività. Se non è necessaria una tempistica attenta, è possibile specificare il parametro SYNC=0 opzionale per applicare le modifiche senza ripristinare il timeout di inattività.
    
+
    SET_LED_TEMPLATE
    
+
    SET_LED_TEMPLATE LED=<nome_led> TEMPLATE=<nome_modello> [<param_x>=<letterale>] [INDEX=<indice>]: Assegna un modello_visualizzazione a un dato LED. Ad esempio, se si definisce una sezione di configurazione [display_template my_led_template] allora si potrebbe assegnare TEMPLATE=my_led_template qui. Il display_template dovrebbe produrre una stringa separata da virgole contenente quattro numeri in virgola mobile corrispondenti alle impostazioni dei colori rosso, verde, blu e bianco. Il modello verrà continuamente valutato e il LED verrà impostato automaticamente sui colori risultanti. È possibile impostare i parametri display_template da utilizzare durante la valutazione del modello (i parametri verranno analizzati come valori letterali Python). Se INDEX non è specificato, tutti i chip nella catena dei LED verranno impostati sul modello, altrimenti verrà aggiornato solo il chip con l'indice specificato. Se TEMPLATE è una stringa vuota, questo comando cancellerà qualsiasi modello precedente assegnato al LED (è quindi possibile utilizzare i comandi SET_LED per gestire le impostazioni del colore del LED).
    
+
    [load_cell]
    
+
    The following commands are enabled if a load_cell config section has been enabled.
    
+
    LOAD_CELL_DIAGNOSTIC
    
+
    LOAD_CELL_DIAGNOSTIC [LOAD_CELL=<config_name>]: This command collects 10 seconds of load cell data and reports statistics that can help you verify proper operation of the load cell. This command can be run on both calibrated and uncalibrated load cells.
    
+
    LOAD_CELL_CALIBRATE
    
+
    LOAD_CELL_CALIBRATE [LOAD_CELL=<config_name>]: Start the guided calibration utility. Calibration is a 3 step process:
    
+
      
+
    1. First you remove all load from the load cell and run the TARE command
      2. 
+
    2. Next you apply a known load to the load cell and run the CALIBRATE GRAMS=nnn command
      3. 
+
    3. Finally use the ACCEPT command to save the results
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    LOAD_CELL_TARE
    
+
    LOAD_CELL_TARE [LOAD_CELL=<config_name>]: This works just like the tare button on digital scale. It sets the current raw reading of the load cell to be the zero point reference value. The response is the percentage of the sensors range that was read and the raw value in counts.
    
+
    LOAD_CELL_READ load_cell="name"
    
+
    LOAD_CELL_READ [LOAD_CELL=<config_name>]: This command takes a reading from the load cell. The response is the percentage of the sensors range that was read and the raw value in counts. If the load cell is calibrated a force in grams is also reported.
    
 
    [manual_probe]
    
 
    Il modulo manual_probe viene caricato automaticamente.
    
 
    MANUAL_PROBE
    
@@ -5049,12 +5143,6 @@ section is enabled.
    
 
    Il comando seguente è disponibile quando una sezione di configurazione mcp4018 è abilitata.
    
 
    SET_DIGIPOT
    
 
    SET_DIGIPOT DIGIPOT=config_name WIPER=<value>: Questo comando cambierà il valore corrente del digipot. Questo valore dovrebbe essere in genere compreso tra 0.0 e 1.0, a meno che non sia definita una 'scale' nella configurazione. Quando viene definita 'scale', questo valore dovrebbe essere compreso tra 0,0 e 'scale'.
    
-
    [led]
    
-
    Il comando seguente è disponibile quando una qualsiasi delle sezioni di configurazione led è abilitata.
    
-
    SET_LED
    
-
    SET_LED LED=<nome_config> ROSSO=<valore> VERDE=<valore> BLU=<valore> BIANCO=<valore> [INDEX=<indice>] [TRANSMIT=0] [SYNC=1]: Imposta il LED in output. Ogni colore <valore> deve essere compreso tra 0,0 e 1,0. L'opzione BIANCO è valida solo su LED RGBW. Se il LED supporta più chip in una catena daisy-chain, è possibile specificare INDEX per modificare il colore del solo chip specificato (1 per il primo chip, 2 per il secondo, ecc.). Se INDEX non viene fornito, tutti i LED nella catena verranno impostati sul colore fornito. Se viene specificato TRANSMIT=0, il cambio colore verrà effettuato solo sul successivo comando SET_LED che non specifica TRANSMIT=0; questo può essere utile in combinazione con il parametro INDEX per raggruppare più aggiornamenti in una catena. Per impostazione predefinita, il comando SET_LED sincronizzerà le modifiche con altri comandi gcode in corso. Ciò può comportare un comportamento indesiderato se i LED vengono impostati mentre la stampante non sta stampando in quanto reimposta il timeout di inattività. Se non è necessaria una tempistica attenta, è possibile specificare il parametro SYNC=0 opzionale per applicare le modifiche senza ripristinare il timeout di inattività.
    
-
    SET_LED_TEMPLATE
    
-
    SET_LED_TEMPLATE LED=<nome_led> TEMPLATE=<nome_modello> [<param_x>=<letterale>] [INDEX=<indice>]: Assegna un modello_visualizzazione a un dato LED. Ad esempio, se si definisce una sezione di configurazione [display_template my_led_template] allora si potrebbe assegnare TEMPLATE=my_led_template qui. Il display_template dovrebbe produrre una stringa separata da virgole contenente quattro numeri in virgola mobile corrispondenti alle impostazioni dei colori rosso, verde, blu e bianco. Il modello verrà continuamente valutato e il LED verrà impostato automaticamente sui colori risultanti. È possibile impostare i parametri display_template da utilizzare durante la valutazione del modello (i parametri verranno analizzati come valori letterali Python). Se INDEX non è specificato, tutti i chip nella catena dei LED verranno impostati sul modello, altrimenti verrà aggiornato solo il chip con l'indice specificato. Se TEMPLATE è una stringa vuota, questo comando cancellerà qualsiasi modello precedente assegnato al LED (è quindi possibile utilizzare i comandi SET_LED per gestire le impostazioni del colore del LED).
    
 
    [output_pin]
    
 
    Il comando seguente è disponibile quando una sezione di configurazione pin_output è abilitata.
    
 
    SET_PIN
    
@@ -5077,10 +5165,6 @@ section is enabled.
    
 
    PALETTE_CUT: Questo comando indica alla Palette 2 di tagliare il filamento attualmente caricato nello splice core.
    
 
    PALETTE_SMART_LOAD
    
 
    PALETTE_SMART_LOAD: Questo comando avvia la sequenza di caricamento intelligente sulla Palette 2. Il filamento viene caricato automaticamente estrudendolo alla distanza calibrata sul dispositivo per la stampante e istruisce la Palette 2 una volta completato il caricamento. Questo comando equivale a premere Smart Load direttamente sullo schermo della Palette 2 dopo che il caricamento del filamento è stato completato.
    
-
    [pid_calibrate]
    
-
    Il modulo pid_calibrate viene caricato automaticamente se nel file di configurazione è definito un riscaldatore.
    
-
    PID_CALIBRATE
    
-
    PID_CALIBRATE HEATER=<nome_config> TARGET=<temperatura> [WRITE_FILE=1]: esegue un test di calibrazione PID. Il riscaldatore specificato verrà abilitato fino al raggiungimento della temperatura target specificata, quindi il riscaldatore verrà spento e acceso per diversi cicli. Se il parametro WRITE_FILE è abilitato, verrà creato il file /tmp/heattest.txt con un log di tutti i campioni di temperatura prelevati durante il test.
    
 
    [pause_resume]
    
 
    I seguenti comandi sono disponibili quando la pause_resume config section è abilitata:
    
 
    PAUSE
    
@@ -5091,6 +5175,10 @@ section is enabled.
    
 
    CLEAR_PAUSE: cancella lo stato di pausa corrente senza riprendere la stampa. Questo è utile se si decide di annullare una stampa dopo un PAUSE. Si consiglia di aggiungerlo al gcode iniziale per assicurarsi che lo stato in pausa sia aggiornato per ogni stampa.
    
 
    CANCEL_PRINT
    
 
    CANCEL_PRINT: Annulla la stampa corrente.
    
+
    [pid_calibrate]
    
+
    Il modulo pid_calibrate viene caricato automaticamente se nel file di configurazione è definito un riscaldatore.
    
+
    PID_CALIBRATE
    
+
    PID_CALIBRATE HEATER=<nome_config> TARGET=<temperatura> [WRITE_FILE=1]: esegue un test di calibrazione PID. Il riscaldatore specificato verrà abilitato fino al raggiungimento della temperatura target specificata, quindi il riscaldatore verrà spento e acceso per diversi cicli. Se il parametro WRITE_FILE è abilitato, verrà creato il file /tmp/heattest.txt con un log di tutti i campioni di temperatura prelevati durante il test.
    
 
 
    Il modulo print_stats viene caricato automaticamente.
    
 
    SET_PRINT_STATS_INFO
    
@@ -5158,7 +5246,7 @@ section is enabled.
    
 
    [save_variables]
    
 
    Il comando seguente è abilitato se è stata abilitata una sezione di configurazione save_variables.
    
 
    SAVE_VARIABLE
    
-
    SAVE_VARIABLE VARIABLE=<nome> VALUE=<valore>: salva la variabile su disco in modo che possa essere utilizzata tra i riavvii. Tutte le variabili memorizzate vengono caricate nel dict printer.save_variables.variables all'avvio e possono essere utilizzate nelle macro gcode. Il VALUE fornito viene analizzato come un valore letterale Python.
    
+
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>: Saves the variable to disk so that it can be used across restarts. The VARIABLE must be lowercase. All stored variables are loaded into the printer.save_variables.variables dict at startup and can be used in gcode macros. The provided VALUE is parsed as a Python literal.
    
 
    [screws_tilt_adjust]
    
 
    I seguenti comandi sono disponibili quando la sezione di configurazione viti_tilt_adjust è abilitata (consultare anche la manual level guide).
    
 
    SCREWS_TILT_CALCULATE
    
@@ -5199,6 +5287,18 @@ section is enabled.
    
 
    Il comando seguente è disponibile quando una sezione di configurazione della ventola_temperatura è abilitata.
    
 
    SET_TEMPERATURE_FAN_TARGET
    
 
    SET_TEMPERATURE_FAN_TARGET temperature_fan=<temperature_fan_name> [target=<target_temperature>] [min_speed=<min_speed>] [max_speed=<max_speed>]: Imposta la temperatura target per una temperature_fan. Se non viene fornito un target, viene impostato sulla temperatura specificata nel file di configurazione. Se le velocità non vengono fornite, non viene applicata alcuna modifica.
    
+
    [temperature_probe]
    
+
    The following commands are available when a temperature_probe config section is enabled.
    
+
    TEMPERATURE_PROBE_CALIBRATE
    
+
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
+
    TEMPERATURE_PROBE_NEXT
    
+
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
+
    TEMPERATURE_PROBE_COMPLETE:
    
+
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
+
    ABORT
    
+
    ABORT: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.
    
+
    TEMPERATURE_PROBE_ENABLE
    
+
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
    [tmcXXXX]
    
 
    I seguenti comandi sono disponibili quando una qualsiasi delle tmcXXXX config section è abilitata.
    
 
    DUMP_TMC
    
@@ -5246,18 +5346,6 @@ section is enabled.
    
 
    I seguenti comandi sono disponibili quando la sezione z_tilt config è abilitata.
    
 
    Z_TILT_ADJUST
    
 
    Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]: 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 RETRIES, RETRY_TOLERANCE, and HORIZONTAL_MOVE_Z values override those options specified in the config file.
    
-
    [temperature_probe]
    
-
    The following commands are available when a temperature_probe config section is enabled.
    
-
    TEMPERATURE_PROBE_CALIBRATE
    
-
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
-
    TEMPERATURE_PROBE_NEXT
    
-
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
-
    TEMPERATURE_PROBE_COMPLETE:
    
-
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
-
    ABORT
    
-
    ABORT: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.
    
-
    TEMPERATURE_PROBE_ENABLE
    
-
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
               
             
diff --git a/it/Hall_Filament_Width_Sensor.html b/it/Hall_Filament_Width_Sensor.html
index 014e07468..17c18a98b 100644
--- a/it/Hall_Filament_Width_Sensor.html
+++ b/it/Hall_Filament_Width_Sensor.html
@@ -1357,8 +1357,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Installation.html b/it/Installation.html
index 7d5f8082c..71d8d2d4f 100644
--- a/it/Installation.html
+++ b/it/Installation.html
@@ -1366,8 +1366,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
 
 
    Installazione
    
-
    These instructions assume the software will run on a linux based host running a Klipper compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian based Linux device be used as the host machine (see the FAQ for other options).
    
-
    For the purposes of these instructions host relates to the Linux device and mcu relates to the printboard. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
+
    These instructions assume the software will run on a Linux-based host running a Klipper-compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian-based Linux device be used as the host machine (see the FAQ for other options).
    
+
    For the purposes of these instructions, host relates to the Linux device and mcu relates to the printer board. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
 
    Ottenere un file di configurazione di Klipper
    
 
    Most Klipper settings are determined by a "printer configuration file" printer.cfg, that will be stored on the host. An appropriate configuration file can often be found by looking in the Klipper config directory for a file starting with a "printer-" prefix that corresponds to the target printer. The Klipper configuration file contains technical information about the printer that will be needed during the installation.
    
 
    Se non c'è un file di configurazione della stampante appropriato nella directory di configurazione di Klipper, prova a cercare nel sito web del produttore della stampante per vedere se hanno un file di configurazione di Klipper appropriato.
    
@@ -1493,13 +1493,13 @@
 
    Currently the best choices are front ends that retrieve information through the Moonraker web API and there is also the option to use Octoprint to control Klipper.
    
 
    The choice is up to the user on what to use, but the underlying Klipper is the same in all cases. We encourage users to research the options available and make an informed decision.
    
 
    Obtaining an OS image for SBC's
    
-
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manafactures of these SBC boards also provide their own Klipper-centric images.
    
-
    The two main Moonraker based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi varianta.
    
+
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manufacturers of these SBC boards also provide their own Klipper-centric images.
    
+
    The two main Moonraker-based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi variants.
    
 
    Fluidd can be installed via KIAUH(Klipper Install And Update Helper), which is explained below and is a 3rd party installer for all things Klipper.
    
 
    OctoPrint can be installed via the popular OctoPi image or via KIAUH, this process is explained in 
    
 
    Installing via KIAUH
    
-
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of a x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions working and even mask access to some print boards.
    
-
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
+
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of an x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions from working and even mask access to some printer boards.
    
+
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux-based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
 
    Compilare il firmware e flashare il microcontrollore
    
 
    To compile the micro-controller code, start by running these commands on your host device:
    
 
    cd ~/klipper/
@@ -1510,7 +1510,7 @@ make menuconfig
 
    make
 
    
 
-
    Se i commenti nella parte superiore del file di configurazione della stampante descrivono i passaggi personalizzati per il "flash" dell'immagine finale sulla scheda di controllo della stampante, segui questi passaggi e poi procedi con configurazione OctoPrint.
    
+
    If the comments at the top of the printer configuration file describe custom steps for "flashing" the final image to the printer control board, then follow those steps and then proceed to configuring OctoPrint.
    
 
    In caso contrario, i seguenti passaggi vengono spesso utilizzati per eseguire il "flash" della scheda di controllo della stampante. Innanzitutto è necessario determinare la porta seriale collegata al microcontrollore. Esegui quanto segue:
    
 
    ls /dev/serial/by-id/*
 
    
@@ -1520,8 +1520,8 @@ make menuconfig
 
    
 
 
    It's common for each printer to have its own unique serial port name. This unique name will be used when flashing the micro-controller. It's possible there may be multiple lines in the above output - if so, choose the line corresponding to the micro-controller. If many items are listed and the choice is ambiguous, unplug the board and run the command again, the missing item will be your print board(see the FAQ for more information).
    
-
    For common micro-controllers with STM32 or clone chips, LPC chips and others it is usual that these need an initial Klipper flash via SD card.
    
-
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occuring.
    
+
    For common micro-controllers with STM32 or clone chips, LPC chips and others, it is usual that these need an initial Klipper flash via SD card.
    
+
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring.
    
 
    For common micro-controllers using Atmega chips, for example the 2560, the code can be flashed with something similar to:
    
 
    sudo service klipper stop
 make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
@@ -1538,9 +1538,9 @@ sudo service klipper start
 
    It is important to note that RP2040 chips may need to be put into Boot mode before this operation.
    
 
    Configurare Klipper
    
 
    The next step is to copy the printer configuration file to the host.
    
-
    Arguably the easiest way to set the Klipper configuration file is using the built in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
+
    Arguably the easiest way to set the Klipper configuration file is using the built-in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
 
    Another option is to use a desktop editor that supports editing files over the "scp" and/or "sftp" protocols. There are freely available tools that support this (eg, Notepad++, WinSCP, and Cyberduck). Load the printer config file in the editor and then save it as a file named "printer.cfg" in the home directory of the pi user (ie, /home/pi/printer.cfg).
    
-
    Alternatively, one can also copy and edit the file directly on the host via ssh. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
+
    Alternatively, one can also copy and edit the file directly on the host via SSH. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
 
    cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
 nano ~/printer.cfg
 
    
@@ -1558,9 +1558,9 @@ nano ~/printer.cfg
 serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
 
    
 
-
    After creating and editing the file it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
+
    After creating and editing the file, it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report that the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
 
    Quando si personalizza il file di configurazione della stampante, non è raro che Klipper segnali un errore di configurazione. Se si verifica un errore, apportare le correzioni necessarie al file di configurazione della stampante ed eseguire il "restart" finché "status" non segnala che la stampante è pronta.
    
-
    Klipper reports error messages via the command console and via pop up in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located in ~/printer_data/logs this is named klippy.log
    
+
    Klipper reports error messages via the command console and pop-ups in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located at ~/printer_data/logs/klippy.log.
    
 
    Dopo che Klipper ha segnalato che la stampante è pronta, vai al config check document per eseguire alcuni controlli di base sulle definizioni nel file di configurazione. Vedere idocumentation reference per altre informazioni.
    
 
               
diff --git a/it/Kinematics.html b/it/Kinematics.html
index 36bfcd1e9..81cd06a0c 100644
--- a/it/Kinematics.html
+++ b/it/Kinematics.html
@@ -1411,8 +1411,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Load_Cell.html b/it/Load_Cell.html
new file mode 100644
index 000000000..6d735164a
--- /dev/null
+++ b/it/Load_Cell.html
@@ -0,0 +1,1635 @@
+
+
+
+  
+    
+      
+      
+      
+      
+      
+      
+      
+    
+    
+      
+        Load Cells - Documentazione Klipper
+      
+    
+    
+      
+      
+        
+        
+        
+      
+    
+    
+    
+      
+        
+        
+        
+        
+      
+    
+    
+      
+    
+    
+    
+      
+  
+
+
+  
+  
+
+
+  
+  
+
+
+    
+    
+  
+  
+  
+    
+    
+      
+    
+    
+    
+    
+    
+  
+    
+    
+      
+    
+    
+    
+    
+    
+    
    
+      
+    
    
+    
+    
+      
+
+
    
+  
+  
+
    
+    
+    
    
+      
+      
+        
+          
+        
+      
+      
    
+        
    
+          
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+
+                  
    
+                
    
+              
    
+            
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+                  
    
+                
    
+              
    
+            
+          
+          
    
+            
    
+              
+                
+
+  
+
+
+
+
    Load Cells
    
+
    This document describes Klipper's support for load cells. Basic load cell functionality can be used to read force data and to weigh things like filament. A calibrated force sensor is an important part of a load cell based probe.
    
+
+
+
    Using LOAD_CELL_DIAGNOSTIC
    
+
    When you first connect a load cell its good practice to check for issues by running LOAD_CELL_DIAGNOSTIC. This tool collects 10 seconds of data from the load cell and resport statistics:
    
+
    $ LOAD_CELL_DIAGNOSTIC
+// Collecting load cell data for 10 seconds...
+// Samples Collected: 3211
+// Measured samples per second: 332.0
+// Good samples: 3211, Saturated samples: 0, Unique values: 900
+// Sample range: [4.01% to 4.02%]
+// Sample range / sensor capacity: 0.00524%
+
    
+
+
    Things you can check with this data:
    
+
      
+
    • The configured sample rate of the sensor should be close to the 'Measured samples per second' value. If it is not you may have a configuration or wiring issue.
      • 
+
    • 'Saturated samples' should be 0. If you have saturated samples it means the load sell is seeing more force than it can measure.
      • 
+
    • 'Unique values' should be a large percentage of the 'Samples Collected' value. If 'Unique values' is 1 it is very likely a wiring issue.
      • 
+
    • Tap or push on the sensor while LOAD_CELL_DIAGNOSTIC runs. If things are working correctly ths should increase the 'Sample range'.
      • 
+
    
+
    Calibrating a Load Cell
    
+
    Load cells are calibrated using the LOAD_CELL_CALIBRATE command. This is an interactive calibration utility that walks you though a 3 step process:
    
+
      
+
    1. First use the TARE command to establish the zero force value. This is the reference_tare_counts config value.
      2. 
+
    2. Next you apply a known load or force to the load cell and run the CALIBRATE GRAMS=nnn command. From this the counts_per_gram value is calculated. See the next section for some suggestions on how to do this.
      3. 
+
    3. Finally, use the ACCEPT command to save the results.
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    Applying a Known Force or Load
    
+
    The CALIBRATE GRAMS=nnn step can be accomplished in a number of ways. If your load cell is under a platform like a bed or filament holder it might be easiest to put a known mass on the platform. E.g. you could use a couple of 1KG filament spools.
    
+
    If your load cell is in the printer's toolhead a different approach is easier. Put a digital scale on the printers bed and gently lower the toolhead onto the scale (or raise the bed into the toolhead if your bed moves). You may be able to do this using the FORCE_MOVE command. But more likely you will have to manually moving the z axis with the motors off until the toolhead presses on the scale.
    
+
    A good calibration force would ideally be a large percentage of the load cell's rated capacity. E.g. if you have a 5Kg load cell you would ideally calibrate it with a 5kg mass. This might work well with under-bed sensors that have to support a lot of weight. For toolhead probes this may not be a load that your printer bed or toolhead can tolerate without damage. Do try to use at least 1Kg of force, most printers should tolerate this without issue.
    
+
    When calibrating make careful note of the values reported:
    
+
    $ CALIBRATE GRAMS=555
+// Calibration value: -2.78% (-59803108), Counts/gram: 73039.78739,
+Total capacity: +/- 29.14Kg
+
    
+
+
    The Total capacity should be close to the theoretical rating of the load cell based on the sensor's capacity. If it is much larger you could have used a higher gain setting in the sensor or a more sensitive load cell. This isn't as critical for 32bit and 24bit sensors but is much more critical for low bit width sensors.
    
+
    Reading Force Data
    
+
    Force data can be read with a GCode command:
    
+
    LOAD_CELL_READ
+// 10.6g (1.94%)
+
    
+
+
    Data is also continuously read and can be consumed from the load_cell printer object in a macro:
    
+
    {% set grams = printer.load_cell.force_g %}
+
    
+
+
    This provides an average force over the last 1 second, similar to how temperature sensors work.
    
+
    Taring a Load Cell
    
+
    Taring, sometimes called zeroing, sets the current weight reported by the load_cell to 0. This is useful for measuring relative to a known weight. e.g. when measuring a filament spool, using LOAD_CELL_TARE sets the weight to 0. Then as filament is printed the load_cell will report the weight of the filament used.
    
+
    LOAD_CELL_TARE
+// Load cell tare value: 5.32% (445903)
+
    
+
+
    The current tare value is reported in the printers status and can be read in a macro:
    
+
    {% set tare_counts = printer.load_cell.tare_counts %}
+
    
+
+              
+            
    
+          
    
+        
    
+        
+          
+            
+            Torna su
+          
+        
+      
    
+      
+        
+      
+    
    
+    
    
+      
    
+    
    
+    
+    
+    
+      
+      
+    
+  
+
\ No newline at end of file
diff --git a/it/MCU_Commands.html b/it/MCU_Commands.html
index 9142bc280..8881e0550 100644
--- a/it/MCU_Commands.html
+++ b/it/MCU_Commands.html
@@ -1383,8 +1383,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Manual_Level.html b/it/Manual_Level.html
index f42064221..2f479d5d3 100644
--- a/it/Manual_Level.html
+++ b/it/Manual_Level.html
@@ -1358,8 +1358,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/it/Measuring_Resonances.html b/it/Measuring_Resonances.html
index ed17fcd0a..27d8d72fc 100644
--- a/it/Measuring_Resonances.html
+++ b/it/Measuring_Resonances.html
@@ -838,11 +838,11 @@
       
    
 
-
    The test was last run on commit f6718291 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.
    
+
    The test was last run on commit 14c105b8 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.
    
 
@@ -2226,11 +2226,11 @@ finalize_config crc=0
 
-
+
-
+
    
 
 
    
 
    
 1個步進電機53
 
    
 
    
 3個步進電機2214
 
    
     
 
    
@@ -2252,7 +2252,7 @@ finalize_config crc=0
 
 
 
-
    (*) 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.
    
+
    (*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 200Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 ARM core cycles.
    
 
    Linux MCU 步速率基準測試
    
 
    樹莓派上使用以下配置序列：
    
 
    allocate_oids count=3
diff --git a/zh-Hant/Bootloader_Entry.html b/zh-Hant/Bootloader_Entry.html
index 6013f1bf5..9b50c7474 100644
--- a/zh-Hant/Bootloader_Entry.html
+++ b/zh-Hant/Bootloader_Entry.html
@@ -1429,8 +1429,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Bootloaders.html b/zh-Hant/Bootloaders.html
index 134f42128..d82de97e7 100644
--- a/zh-Hant/Bootloaders.html
+++ b/zh-Hant/Bootloaders.html
@@ -1501,8 +1501,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/CANBUS.html b/zh-Hant/CANBUS.html
index d9e920ea9..e98c58591 100644
--- a/zh-Hant/CANBUS.html
+++ b/zh-Hant/CANBUS.html
@@ -1371,8 +1371,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1549,6 +1549,7 @@ iface can0 can static
 
 
 
      
+
    • It is only valid to use USB to CAN bridge mode if there is a functioning CAN bus with at least one other node available (in addition to the bridge node itself). Use a standard USB configuration if the goal is to communicate only with the single USB device. Using USB to CAN bridge mode without a fully functioning CAN bus (including terminating resistors and an additional node) may result in sporadic errors even when communicating with the bridge node.
      • 
 
    • A USB to CAN bridge board will not appear as a USB serial device, it will not show up when running ls /dev/serial/by-id, and it can not be configured in Klipper's printer.cfg file with a serial: parameter. The bridge board appears as a "USB CAN adapter" and it is configured in the printer.cfg as a CAN node.
      • 
 
    
 
    Tips for troubleshooting
    
diff --git a/zh-Hant/CANBUS_Troubleshooting.html b/zh-Hant/CANBUS_Troubleshooting.html
index b721a3a7c..a2650dc0a 100644
--- a/zh-Hant/CANBUS_Troubleshooting.html
+++ b/zh-Hant/CANBUS_Troubleshooting.html
@@ -1284,6 +1284,13 @@
     Use an appropriate txqueuelen setting
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1370,8 +1377,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1444,6 +1451,13 @@
     Use an appropriate txqueuelen setting
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1500,12 +1514,16 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    Verify that all plugs and wire crimps on the CAN bus wiring are fully secured. Movement of the printer toolhead may jostle the CAN bus wiring causing a bad wire crimp or unsecured plug to result in intermittent communication errors.
    
 
    Check for incrementing bytes_invalid counter
    
 
    The Klipper log file will report a Stats line once a second when the printer is active. These "Stats" lines will have a bytes_invalid counter for each micro-controller. This counter should not increment during normal printer operation (it is normal for the counter to be non-zero after a RESTART and it is not a concern if the counter increments once a month or so). If this counter increments on a CAN bus micro-controller during normal printing (it increments every few hours or more frequently) then it is an indication of a severe problem.
    
-
    Incrementing bytes_invalid on a CAN bus connection is a symptom of reordered messages on the CAN bus. There are two known causes of reordered messages:
    
-
      
-
    1. Old versions of the popular candlight_firmware for USB CAN adapters had a bug that could cause reordered messages. If using a USB CAN adapter running this firmware then make sure to update to the latest firmware if incrementing bytes_invalid is observed.
      2. 
-
    2. Some Linux kernel builds for embedded devices have been known to reorder CAN bus messages. It may be necessary to use an alternative Linux kernel or to use alternative hardware that supports mainstream Linux kernels that do not exhibit this problem.
      3. 
-
    
-
    Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print.
    
+
    Incrementing bytes_invalid on a CAN bus connection is a symptom of reordered messages on the CAN bus. If seen, make sure to:
    
+
      
+
    • Use a Linux kernel version 6.6.0 or later.
      • 
+
    • If using a USB-to-CANBUS adapter running candlelight firmware, use v2.0 or later of candleLight_fw.
      • 
+
    • If using Klipper's USB-to-CANBUS bridge mode, make sure the bridge node is flashed with Klipper v0.12.0 or later.
      • 
+
    
+
    Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print. An incrementing bytes_invalid is not caused by wiring or similar hardware issues and can only be fixed by identifying and updating the faulty software.
    
+
    Older versions of the Linux kernel had a bug in the gs_usb canbus driver code that could cause reordered canbus packets. The issue is thought to be fixed in Linux commit 24bc41b4 which was released in v6.6.0. In some cases, older Linux versions may not show the problem (due to how hardware interrupts are configured), however if problems are seen the recommended solution is to upgrade to a newer kernel.
    
+
    Older versions of candlelight firmware could reorder canbus packets, and the issue is thought to be fixed in candlelight_fw commit 8b3a7b45.
    
+
    Older versions of Klipper's USB-to-CANBUS bridge code could incorrectly drop canbus messages. This is not as severe as reordering messages, but it should still be fixed. It is thought to be fixed with Klipper PR #6175.
    
 
    Use an appropriate txqueuelen setting
    
 
    The Klipper code uses the Linux kernel to manage CAN bus traffic. By default, the kernel will only queue 10 CAN transmit packets. It is recommended to configure the can0 device with a txqueuelen 128 to increase that size.
    
 
    If Klipper transmits a packet and Linux has filled all of its transmit queue space then Linux will drop that packet and messages like the following will appear in the Klipper log:
    
@@ -1517,6 +1535,10 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    One may check the current queue size by running the Linux command ip link show can0. It should report a bunch of text including the snippet qlen 128. If one sees something like qlen 10 then it indicates the CAN device has not been properly configured.
    
 
    It is not recommended to use a txqueuelen significantly larger than 128. A CAN bus running at a frequency of 1000000 will typically take around 120us to transmit a CAN packet. Thus a queue of 128 packets is likely to take around 15-20ms to drain. A substantially larger queue could cause excessive spikes in message round-trip-time which could lead to unrecoverable errors. Said another way, Klipper's application retransmit system is more robust if it does not have to wait for Linux to drain an excessively large queue of possibly stale data. This is analogous to the problem of bufferbloat on internet routers.
    
 
    Under normal circumstances Klipper may utilize ~25 queue slots per MCU - typically only utilizing more slots during retransmits. (Specifically, the Klipper host may transmit up to 192 bytes to each Klipper MCU before receiving an acknowledgment from that MCU.) If a single CAN bus has 5 or more Klipper MCUs on it, then it might be necessary to increase the txqueuelen above the recommended value of 128. However, as above, care should be taken when selecting a new value to avoid excessive round-trip-time latency.
    
+
    Use canbus_query.py only to identify nodes never previously seen
    
+
    It is only valid to use the canbus_query.py tool to identify micro-controllers that have never been previously identified. Once all nodes on a bus are identified, record the resulting uuids in the printer.cfg, and avoid running the tool unnecessarily.
    
+
    The tool is implemented using a low-level mechanism that can cause nodes to internally observe bus errors. These internal errors may result in communication interruptions and may result is some nodes disconnecting from the bus.
    
+
    It is not valid to use the tool to "ping" if a node is connected. Do not run the tool during an active print.
    
 
    Obtaining candump logs
    
 
    The CAN bus messages sent to and from the micro-controller are handled by the Linux kernel. It is possible to capture these messages from the kernel for debugging purposes. A log of these messages may be of use in diagnostics.
    
 
    The Linux can-utils tool provides the capture software. It is typically installed on a machine by running:
    
diff --git a/zh-Hant/CANBUS_protocol.html b/zh-Hant/CANBUS_protocol.html
index 866a9181d..d5c11dfbc 100644
--- a/zh-Hant/CANBUS_protocol.html
+++ b/zh-Hant/CANBUS_protocol.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/CONTRIBUTING.html b/zh-Hant/CONTRIBUTING.html
index 9b3c4cffe..81e1c7028 100644
--- a/zh-Hant/CONTRIBUTING.html
+++ b/zh-Hant/CONTRIBUTING.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Code_Overview.html b/zh-Hant/Code_Overview.html
index f42e15f67..f33c9b5f3 100644
--- a/zh-Hant/Code_Overview.html
+++ b/zh-Hant/Code_Overview.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Command_Templates.html b/zh-Hant/Command_Templates.html
index aad2cf541..443f85bfe 100644
--- a/zh-Hant/Command_Templates.html
+++ b/zh-Hant/Command_Templates.html
@@ -1421,8 +1421,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Config_Changes.html b/zh-Hant/Config_Changes.html
index 8c013c393..f7d9d9116 100644
--- a/zh-Hant/Config_Changes.html
+++ b/zh-Hant/Config_Changes.html
@@ -1327,8 +1327,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1410,6 +1410,12 @@
 
    本文件涵蓋了軟體更新中對配置檔案不向后相容的部分。在升級 Klipper 時，最好也檢視一下這份文件。
    
 
    本文件中的所有日期都是不精確的。
    
 
    變更
    
+
    20250428: The maximum cycle_time for pwm [output_pin], [pwm_cycle_time], [pwm_tool], and similar config sections is now 3 seconds (reduced from 5 seconds). The maximum_mcu_duration in [pwm_tool] is now also 3 seconds.
    
+
    20250418: The manual_stepper STOP_ON_ENDSTOP feature may now take less time to complete. Previously, the command would wait the entire time the move could possibly take even if the endstop triggered earlier. Now, the command finishes shortly after the endstop trigger.
    
+
    20250417: SPI devices using "software SPI" are now rate limited. Previously, the spi_speed in the config was ignored and the transmission speed was only limited by the processing speed of the micro-controller. Now, speeds are limited by the spi_speed config parameter (actual hardware speeds are likely to be lower than the configured value due to software overhead).
    
+
    20250411: Klipper v0.13.0 released.
    
+
    20250308: The AUTO parameter of the AXIS_TWIST_COMPENSATION_CALIBRATE command has been removed.
    
+
    20250131: Option VARIABLE=<name> in SAVE_VARIABLE requires lowercase value. For example, extruder instead of mixedcase Extruder or uppercase EXTRUDER. Using any uppercase letter will raise an error.
    
 
    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 sweeping_period: 0 and accel_per_hz: 75 to the [resonance_tester] config section.
    
 
    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.
    
 
    20241112: Option CHIPS=<chip_name> in TEST_RESONANCES and SHAPER_CALIBRATE requires specifying the full name(s) of the accel chip(s). For example, adxl345 rpi instead of short name - rpi.
    
diff --git a/zh-Hant/Config_Reference.html b/zh-Hant/Config_Reference.html
index 4d5eb4b0f..81152d4fc 100644
--- a/zh-Hant/Config_Reference.html
+++ b/zh-Hant/Config_Reference.html
@@ -931,6 +931,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -1741,6 +1748,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -2600,8 +2614,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3053,6 +3067,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -3863,6 +3884,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -5292,6 +5320,22 @@ cs_pin:
 #   共振測量的質量。
 
    • 
 
+
    [icm20948]
    
+
    Support for icm20948 accelerometers.
    
+
    [icm20948]
+#i2c_address:
+#   Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
+#i2c_mcu:
+#i2c_bus:
+#i2c_software_scl_pin:
+#i2c_software_sda_pin:
+#i2c_speed: 400000
+#   See the "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.
+
    
+
 
    [lis2dw]
    
 
    Support for LIS2DW accelerometers.
    
 
    [lis2dw]
@@ -5616,6 +5660,9 @@ z_offset:
 sensor_type: ldc1612
 #   The sensor chip used to perform eddy current measurements. This
 #   parameter must be provided and must be set to ldc1612.
+#frequency:
+#   The external crystal frequency (in Hz) of the LDC1612 chip.
+#   The default is 12000000.
 #intb_pin:
 #   MCU gpio pin connected to the ldc1612 sensor's INTB pin (if
 #   available). The default is to not use the INTB pin.
@@ -6552,20 +6599,27 @@ pin:
 
    在一個按鈕被按下或放開（或當一個引腳狀態發生變化時）時執行G程式碼。你可以使用 QUERY_BUTTON button=my_gcode_button 來查詢按鈕的狀態。
    
 
    [gcode_button my_gcode_button]
 pin:
-#   連線到按鈕的引腳。
-#   必須提供此參數。
+#   The pin on which the button is connected. This parameter must be
+#   provided.
 #analog_range:
-#   兩個逗號分隔的阻值(單位：歐姆)，指定了按鈕的最小和最大電阻。
-#   如果提供了 analog_range ，必須使用一個模擬功能的引腳。預設
-#   情況下為按鈕使用數字GPIO。
-#   analog_pullup_resistor:
-#   當定義 analog_range 時的上拉電阻(歐姆)。預設為4700歐姆。
+#   Two comma separated resistances (in Ohms) specifying the minimum
+#   and maximum resistance range for the button. If analog_range is
+#   provided then the pin must be an analog capable pin. The default
+#   is to use digital gpio for the button.
+#analog_pullup_resistor:
+#   The pullup resistance (in Ohms) when analog_range is specified.
+#   The default is 4700 ohms.
 #press_gcode:
-#   當按鈕被按下時要執行的 G-Code 命令序列，支援G-Code模板。
-#   必須提供此參數。
+#   A list of G-Code commands to execute when the button is pressed.
+#   G-Code templates are supported. This parameter must be provided.
 #release_gcode:
-#   當按鈕被釋放時要執行的G-Code命令序列，支援G-Code模板。
-#   預設在按鈕釋放時不執行任何命令。
+#   A list of G-Code commands to execute when the button is released.
+#   G-Code templates are supported. The default is to not run any
+#   commands on a button release.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   button gcode. If the button is pressed and released during this
+#   delay, the entire button press is ignored. Default is 0.
 
    
 
 
    [output_pin]
    
@@ -6698,8 +6752,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -6748,6 +6803,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 4
 #driver_PWM_AMPL: 128
+#driver_FREEWHEEL: 0
 #driver_SGT: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6805,8 +6861,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #driver_MULTISTEP_FILT: True
 #driver_IHOLDDELAY: 8
 #driver_TPOWERDOWN: 20
@@ -6821,6 +6878,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #   Set the given register during the configuration of the TMC2208
 #   chip. This may be used to set custom motor parameters. The
 #   defaults for each parameter are next to the parameter name in the
@@ -6864,6 +6922,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #driver_SGTHRS: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6990,8 +7049,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7118,8 +7178,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7704,35 +7765,39 @@ text:
 
    [filament_switch_sensor]
    
 
    耗材開關感測器。支援使用開關感測器（如限位開關）進行耗材插入和耗盡檢測。
    
 
    有關詳細信息，請參閱 命令參考。
    
-
    [filament_switch_sensor my_sensor]。
+
    [filament_switch_sensor my_sensor]
 #pause_on_runout: True
-#   當設定為 "True "時，會在檢測到耗盡后立即暫停印表機。
-#   請注意, 如果 pause_on_runout 為 False 並且沒有定義。
-#   runout_gcode的話, 耗盡檢測將被禁用。
-#   預設為 True。
+#   When set to True, a PAUSE will execute immediately after a runout
+#   is detected. Note that if pause_on_runout is False and the
+#   runout_gcode is omitted then runout detection is disabled. Default
+#   is True.
 #runout_gcode:
-#   在檢測到耗材耗盡後會執行的G程式碼命令列表。
-#   有關G-Code 格式請見 docs/Command_Templates.md。
-#   如果 pause_on_runout 被設定為 True，這個G-Code將在
-#   暫停后執行。
-#   預設情況是不執行任何 G-Code 命令。
+#   A list of G-Code commands to execute after a filament runout is
+#   detected. See docs/Command_Templates.md for G-Code format. If
+#   pause_on_runout is set to True this G-Code will run after the
+#   PAUSE is complete. The default is not to run any G-Code commands.
 #insert_gcode:
-#   在檢測到耗材插入後會執行的 G-Code 命令列表。
-#   關於G程式碼格式，請參見 docs/Command_Templates.md。
-#   預設不執行任何 G-Code 命令，這將禁用耗材插入檢測。
+#   A list of G-Code commands to execute after a filament insert is
+#   detected. See docs/Command_Templates.md for G-Code format. The
+#   default is not to run any G-Code commands, which disables insert
+#   detection.
 #event_delay: 3.0
-#   事件之間的最小延遲時間（秒）。
-#   在這個時間段內觸發的事件將被默許忽略。
-#   預設為3秒。
+#   The minimum amount of time in seconds to delay between events.
+#   Events triggered during this time period will be silently
+#   ignored. The default is 3 seconds.
 #pause_delay: 0.5
-#   暫停命令和執行 runout_gcode 之間的延遲時間, 單位是秒。
-#   如果在OctoPrint的情況下，增加這個延遲可能改善暫
-#   停的可靠性。如果OctoPrint表現出奇怪的暫停行為，
-#   考慮增加這個延遲。
-#   預設為0.5秒。
+#   The amount of time to delay, in seconds, between the pause command
+#   dispatch and execution of the runout_gcode. It may be useful to
+#   increase this delay if OctoPrint exhibits strange pause behavior.
+#   Default is 0.5 seconds.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   switch gcode. The switch must he held in a single state for at least
+#   this long to activate. If the switch is toggled on/off during this delay,
+#   the event is ignored. Default is 0.
 #switch_pin:
-#   連線到檢測開關的引腳。
-#   必須提供此參數。
+#   The pin on which the switch is connected. This parameter must be
+#   provided.
 
    
 
 
    [filament_motion_sensor]
    
@@ -7822,6 +7887,16 @@ adc2:
 
    [load_cell]
 sensor_type:
 #   This must be one of the supported sensor types, see below.
+#counts_per_gram:
+#   The floating point number of sensor counts that indicates 1 gram of force.
+#   This value is calculated by the LOAD_CELL_CALIBRATE command.
+#reference_tare_counts:
+#   The integer tare value, in raw sensor counts, taken when LOAD_CELL_CALIBRATE
+#   is run. This is the default tare value when klipper starts up.
+#sensor_orientation:
+#   Change the sensor's orientation. Can be either 'normal' or 'inverted'.
+#   The default is 'normal'. Use 'inverted' if the sensor reports a
+#   decreasing force value when placed under load.
 
    
 
 
    HX711
    
@@ -7966,6 +8041,38 @@ vssa_pin:
 #   VSSA 測量來減少測量的干擾。預設為2秒。
 
    
 
+
    [ads1x1x]
    
+
    ADS1013, ADS1014, ADS1015, ADS1113, ADS1114 and ADS1115 are I2C based Analog to Digital Converters that can be used for temperature sensors. They provide 4 analog input pins either as single line or as differential input.
    
+
    Note: Use caution if using this sensor to control heaters. The heater min_temp and max_temp are only verified in the host and only if the host is running and operating normally. (ADC inputs directly connected to the micro-controller verify min_temp and max_temp within the micro-controller and do not require a working connection to the host.)
    
+
    [ads1x1x my_ads1x1x]
+chip: ADS1115
+#pga: 4.096V
+#   Default value is 4.096V. The maximum voltage range used for the input. This
+#   scales all values read from the ADC. Options are: 6.144V, 4.096V, 2.048V,
+#   1.024V, 0.512V, 0.256V
+#adc_voltage: 3.3
+#   The suppy voltage for the device. This allows additional software scaling
+#   for all values read from the ADC.
+i2c_mcu: host
+i2c_bus: i2c.1
+#address_pin: GND
+#   Default value is GND.  There can be up to four addressed devices depending
+#   upon wiring of the device. Check the datasheet for details. The i2c_address
+#   can be specified directly instead of using the address_pin.
+
    
+
+
    The chip provides pins that can be used on other sensors.
    
+
    sensor_type: ...
+#   Can be any thermistor or adc_temperature.
+sensor_pin: my_ads1x1x:AIN0
+#   A combination of the name of the ads1x1x chip and the pin. Possible
+#   pin values are AIN0, AIN1, AIN2 and AIN3 for single ended lines and
+#   DIFF01, DIFF03, DIFF13 and DIFF23 for differential between their
+#   correspoding lines. For example
+#   DIFF03 measures the differential between line 0 and 3. Only specific
+#   combinations for the differentials are allowed.
+
    
+
 
    [replicape]
    
 
    副本支持 - 有關示例，請參見 beaglebone guide 和 generic-replicape.cfg 文件。
    
 
    # The "replicape" config section adds "replicape:stepper_x_enable"
@@ -8032,7 +8139,7 @@ host_mcu:
 
    Palette 2 多材料支援 - 提供更緊密的整合，支援處於連線模式的 Palette 2 裝置。
    
 
    此模塊還需要 [virtual_sdcard] 和 [pause_resume] 才能獲得完整功能。
    
 
    不要和 Octoprint 的 Palette 2外掛一起使用這個模組，因為它們會發生衝突，造成初始化和列印失敗。
    
-
    如果使用 OctoPrint 並通過串列埠流式傳輸 G-Code，而不通過 virtual_sd 列印，將 * 設定>序列連線>韌體和協議 * 中的「暫停命令」 設定為M1 和 M0 可以避免在開始列印時需要在Palette 2 上選擇開始列印並在 OctoPrint 中取消暫停。
    
+
    If you use Octoprint and stream gcode over the serial port instead of printing from virtual_sd, then remove M1 and M0 from Pausing commands in Settings > Serial Connection > Firmware & protocol will prevent the need to start print on the Palette 2 and unpausing in Octoprint for your print to begin.
    
 
    [palette2]
 serial:
 #   The serial port to connect to the Palette 2.
diff --git a/zh-Hant/Config_checks.html b/zh-Hant/Config_checks.html
index b216e142c..e6c4cdf46 100644
--- a/zh-Hant/Config_checks.html
+++ b/zh-Hant/Config_checks.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Contact.html b/zh-Hant/Contact.html
index 8a7eb6387..5d6e5c6e5 100644
--- a/zh-Hant/Contact.html
+++ b/zh-Hant/Contact.html
@@ -451,8 +451,8 @@
 
       
         
  • 
-  
-    Klipper github
+  
+    Professional Services
   
   
 
    • 
@@ -1376,8 +1376,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
       
         
  • 
-  
-    Klipper github
+  
+    Professional Services
   
   
 
    • 
@@ -1558,9 +1558,10 @@
 
    我正在進行一些我想新增到 Klipper 中的改進
    
 
    Klipper 是開源軟體，我們非常感謝新的貢獻。
    
 
    新的貢獻（包括程式碼和文件）需要通過拉取請求(PR)提交。重要資訊請參見貢獻文件。
    
-
    There are several documents for developers. If you have questions on the code then you can also ask in the Klipper Community Forum or on the Klipper Community Discord.
    
-
    Klipper github
    
-
    Klipper github may be used by contributors to share the status of their work to improve Klipper. It is expected that the person opening a github ticket is actively working on the given task and will be the one performing all the work necessary to accomplish it. The Klipper github is not used for requests, nor to report bugs, nor to ask questions. Use the Klipper Community Forum or the Klipper Community Discord instead.
    
+
    There are several documents for developers. If you have questions on the code then you can also ask in the Klipper Discourse Forum or on the Klipper Discord Chat.
    
+
    Professional Services
    
+
    
+
    Custom software development, software support, and solutions: https://ko-fi.com/koconnor
    
 
               
             
diff --git a/zh-Hant/Debugging.html b/zh-Hant/Debugging.html
index ca497b54d..cffe04afb 100644
--- a/zh-Hant/Debugging.html
+++ b/zh-Hant/Debugging.html
@@ -1384,8 +1384,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Delta_Calibrate.html b/zh-Hant/Delta_Calibrate.html
index 30adabe79..677e18e04 100644
--- a/zh-Hant/Delta_Calibrate.html
+++ b/zh-Hant/Delta_Calibrate.html
@@ -1365,8 +1365,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Eddy_Probe.html b/zh-Hant/Eddy_Probe.html
index a8eeae421..3731a25b9 100644
--- a/zh-Hant/Eddy_Probe.html
+++ b/zh-Hant/Eddy_Probe.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1487,13 +1487,13 @@
       
       
         
-        
  • 
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Example_Configs.html b/zh-Hant/Example_Configs.html
index 6604e092d..bf959d045 100644
--- a/zh-Hant/Example_Configs.html
+++ b/zh-Hant/Example_Configs.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Exclude_Object.html b/zh-Hant/Exclude_Object.html
index 153cc48bc..83ead2c74 100644
--- a/zh-Hant/Exclude_Object.html
+++ b/zh-Hant/Exclude_Object.html
@@ -1356,8 +1356,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/FAQ.html b/zh-Hant/FAQ.html
index 48bd38e35..3b4a9f74b 100644
--- a/zh-Hant/FAQ.html
+++ b/zh-Hant/FAQ.html
@@ -1488,8 +1488,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Features.html b/zh-Hant/Features.html
index 39986fe52..dd9a88fd1 100644
--- a/zh-Hant/Features.html
+++ b/zh-Hant/Features.html
@@ -1334,8 +1334,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1443,18 +1443,18 @@
 
  • 標準 G 程式碼支援。支援由常見「切片軟體」（SuperSlicer、Cura、PrusaSlicer 等）產生的通用 G 程式碼命令。
    • 
 
  • 支援多擠出機。包括對共享熱端的擠出機（多進一出）和多頭（IDEX）的支援。
    • 
 
  • 支援多種列印機架構，包括直線式 (Cartesian)、三角洲式 (Delta)、CoreXY、CoreXZ、混合式 CoreXY、混合式 CoreXZ、Deltesian、旋轉三角洲式 (Rotary Delta)、極座標式 (Polar) 以及纜繩式 (Cable Winch) 列印機。
    • 
-
  • 自動床面平整支援。Klipper可以被配置為基本的床身傾斜檢測或網床調平。如果床鋪使用多個Z步進器，那麼Klipper也可以通過獨立操縱Z步進器來調平。支援大多數Z高度探頭，包括BL-Touch探頭和伺服啟用的探頭。
    • 
+
  • Automatic bed leveling support. Klipper can be configured for basic bed tilt detection or full mesh bed leveling. The bed mesh can be customized to the print size (adaptive bed mesh). If the bed uses multiple Z steppers then Klipper can also level by independently manipulating the Z steppers. Most Z height probes are supported, including BL-Touch probes and servo activated probes. Probes may be calibrated for axis twist compensation. If using an "eddy current probe" then one can utilize fast bed mesh scanning,
    • 
 
  • 支援自動delta校準。校準工具可以進行基本的高度校準，以及增強的X和Y尺寸校準。校準可以用Z型高度探頭或通過手動探測來完成。
    • 
 
  • 列印時支援“排除物件”。當啟用此模組時，可在多件列印中僅取消指定的單一物件。
    • 
-
  • 支援常見的溫度感測器（例如，常見的熱敏電阻、AD595、AD597、AD849x、PT100、PT1000、MAX6675、MAX31855、MAX31856、MAX31865、BME280、HTU21D、DS18B20和LM75）。還可以配置自定義熱敏電阻和自定義模擬溫度感測器。還可以監測微控制器和 Raspberry Pi 內部的溫度感測器。
    • 
+
  • Support for common temperature sensors (eg, common thermistors, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20, AHT10, SHT3x, and LM75). Custom thermistors and custom analog temperature sensors can also be configured. One can monitor the internal micro-controller temperature sensor and the internal temperature sensor of a Raspberry Pi.
    • 
 
  • 預設啟用基本加熱器保護。
    • 
-
  • 支援標準風扇、噴嘴風扇和溫控風扇。不需要在印表機閑置時保持風扇運轉。可以在帶有轉速錶的風扇上監測風扇速度。
    • 
+
  • Support for standard fans, nozzle fans, and temperature controlled fans. No need to keep fans running when the printer is idle. Fan speed can be monitored on fans that have a tachometer. One can assign a "math formula" to a fan for automatic fan speed updating.
    • 
 
  • 支援運行時配置 TMC2130、TMC2208/TMC2224、TMC2209、TMC2660 和 TMC5160 步進馬達驅動器。此外，也支援透過 AD5206、DAC084S085、MCP4451、MCP4728、MCP4018 和 PWM 腳位對傳統步進驅動器進行電流控制。
    • 
 
  • 支援直接連線到印表機的普通LCD顯示器。還提供了一個預設的菜單。顯示器和菜單的內容可以通過配置檔案完全定製。
    • 
 
  • 恒定加速和「look-ahead」（前瞻）支援。所有印表機移動將從靜止逐漸加速到巡航速度，然後減速回到靜止。對傳入的 G 程式碼移動命令流進行排隊和分析 - 將優化類似方向上的移動之間的加速度，以減少列印停頓並改善整體列印時間。
    • 
 
  • Klipper 實現了一種「步進相位限位」演算法，可以提高典型限位開關的精度。如果調整得當，它可以提高列印件首層和列印床的附著力。
    • 
 
  • 支援列印絲存在感測器、列印絲運動感測器和列印絲寬度感測器。
    • 
-
  • 支援使用 ADXL345、MPU9250 和 MPU6050 加速度計進行加速度的測量與記錄。
    • 
+
  • Support for measuring and recording acceleration using adxl345, mpu9250, mpu6050, lis2dw12, lis3dh, and icm20948 accelerometers.
    • 
 
  • 支援限制短距離「之」字形移動的最高速度，以減少印表機的振動和噪音。更多資訊見運動學文件。
    • 
 
  • 許多常見的印表機都有樣本配置檔案。檢視配置資料夾中的列表。
    • 
 
@@ -1526,11 +1526,6 @@
 1622K
 
 
-RP2040
-2400K
-1636K
-
-
 SAM4E8E
 2500K
 1674K
@@ -1556,6 +1551,11 @@
 2634K
 
 
+RP2040
+4000K
+2571K
+
+
 RP2350
 4167K
 2663K
@@ -1566,9 +1566,9 @@
 4737K
 
 
-STM32H743
-9091K
-6061K
+STM32H723
+7429K
+8619K
 
 
 
diff --git a/zh-Hant/G-Codes.html b/zh-Hant/G-Codes.html
index 306965e2b..814d6916d 100644
--- a/zh-Hant/G-Codes.html
+++ b/zh-Hant/G-Codes.html
@@ -1620,6 +1620,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -1694,33 +1756,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1789,26 +1824,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1850,6 +1865,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -2281,6 +2316,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -2429,54 +2512,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -3006,8 +3041,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3881,6 +3916,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -3955,33 +4052,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4050,26 +4120,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4111,6 +4161,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -4542,6 +4612,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -4690,54 +4808,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -4831,11 +4901,10 @@
 
    The following commands are available when the axis_twist_compensation config
 section is enabled.
    
 
    AXIS_TWIST_COMPENSATION_CALIBRATE
    
-
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]
    
+
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [SAMPLE_COUNT=<value>]
    
 
    Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.
    
 
      
 
    • AXIS: Define the axis (X or Y) for which the twist compensation will be calibrated. If not specified, the axis defaults to 'X'.
      • 
-
    • AUTO: Enables automatic calibration mode. When AUTO=True, the calibration will run for both the X and Y axes. In this mode, AXIS cannot be specified. If both AXIS and AUTO are provided, an error will be raised.
      • 
 
    
 
    [bed_mesh]
    
 
    當啟用 bed_mesh config section 時，以下命令可用（另請參閱 bed mesh guide）。
    
@@ -4965,7 +5034,10 @@ section is enabled.
    
 
    FORCE_MOVE
    
 
    FORCE_MOVE STEPPER=<config_name> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>] 。該命令將以給定的恒定速度（mm/s）強制移動給定的步進器，移動距離（mm）。如果指定了ACCEL並且大於零，那麼將使用給定的加速度（單位：mm/s^2）；否則不進行加速。不執行邊界檢查；不進行運動學更新；一個軸上的其他平行步進器將不會被移動。請謹慎使用，因為不正確的命令可能會導致損壞使用該命令幾乎肯定會使低階運動學處於不正確的狀態；隨後發出G28命令以重置運動學。該命令用於低階別的診斷和除錯。
    
 
    SET_KINEMATIC_POSITION
    
-
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]: 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.
    
+
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [SET_HOMED=<[X][Y][Z]>] [CLEAR_HOMED=<[X][Y][Z]>]: Force the low-level kinematic code to believe the toolhead is at the given cartesian position and set/clear homed status. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. Setting an incorrect or invalid position may lead to internal software errors.
    
+
    The X, Y, and Z parameters are used to alter the low-level kinematic position tracking. If any of these parameters are not set then the position is not changed - for example SET_KINEMATIC_POSITION Z=10 would set all axes as homed, set the internal Z position to 10, and leave the X and Y positions unchanged. Changing the internal position tracking is not dependent on the internal homing state - one may alter the position for both homed and not homed axes, and similarly one may set or clear the homing state of an axis without altering its internal position.
    
+
    The SET_HOMED parameter defaults to XYZ which instructs the kinematics to consider all axes as homed. A bare SET_KINEMATIC_POSITION command will result in all axes being considered homed (and not change its current position). If it is not desired to change the state of homed axes then assign SET_HOMED to an empty string - for example: SET_KINEMATIC_POSITION SET_HOMED= X=10. It is also possible to request an individual axis be considered homed (eg, SET_HOMED=X), but note that non-cartesian style kinematics (such as delta kinematics) may not support setting an individual axis as homed.
    
+
    The CLEAR_HOMED parameter instructs the kinematics to consider the given axes as not homed. For example, CLEAR_HOMED=XYZ would request all axes to be considered not homed (and thus require homing prior to movement on those axes). The default is SET_HOMED=XYZ even if CLEAR_HOMED is present, so the command SET_KINEMATIC_POSITION CLEAR_HOMED=Z will set X and Y as homed and clear the homing state for Z. Use SET_KINEMATIC_POSITION SET_HOMED= CLEAR_HOMED=Z if the goal is to clear only the Z homing state. If an axis is specified in neither SET_HOMED nor CLEAR_HOMED then its homing state is not changed and if it is specified in both then CLEAR_HOMED has precedence. It is possible to request clearing of an individual axis, but on non-cartesian style kinematics (such as delta kinematics) doing so may result in clearing the homing state of additional axes. Note the CLEAR parameter is currently an alias for the CLEAR_HOMED parameter, but this alias will be removed in the future.
    
 
    [gcode]
    
 
    模組gcode module已自動載入.
    
 
    RESTART
    
@@ -5028,6 +5100,28 @@ section is enabled.
    
 
    如果啟用了 input_shaper config section，則啟用以下命令（另請參閱 resonance compensation guide）。
    
 
    SET_INPUT_SHAPER
    
 
    SET_INPUT_SHAPER [SHAPER_FREQ_X=<shaper_freq_x>] [SHAPER_FREQ_Y=<shaper_freq_y>] [DAMPING_RATIO_X=<damping_ratio_x>] [DAMPING_RATIO_Y=<damping_ratio_y>] [SHAPER_TYPE=<shaper>] [SHAPER_TYPE_X=<shaper_type_x>] [SHAPER_TYPE_Y=<shaper_type_y>]：修改輸入整形參數。注意 SHAPER_TYPE 參數會同時覆寫 X 和 Y 軸的整形器型別，即使它們在 [input_shaper] 配置分段中有不同的整形器型別。SHAPER_TYPE 不能和 SHAPER_TYPE_X 和 SHAPER_TYPE_Y 參數同時使用。這些參數的細節請見配置參考。
    
+
    [led]
    
+
    The following command is available when any of the led config sections are enabled.
    
+
    SET_LED
    
+
    SET_LED LED=<config_name> RED=<value> GREEN=<value> BLUE=<value> WHITE=<value> [INDEX=<index>] [TRANSMIT=0] [SYNC=1]: This sets the LED output. Each color <value> must be between 0.0 and 1.0. The WHITE option is only valid on RGBW LEDs. If the LED supports multiple chips in a daisy-chain then one may specify INDEX to alter the color of just the given chip (1 for the first chip, 2 for the second, etc.). If INDEX is not provided then all LEDs in the daisy-chain will be set to the provided color. If TRANSMIT=0 is specified then the color change will only be made on the next SET_LED command that does not specify TRANSMIT=0; this may be useful in combination with the INDEX parameter to batch multiple updates in a daisy-chain. By default, the SET_LED command will sync it's changes with other ongoing gcode commands. This can lead to undesirable behavior if LEDs are being set while the printer is not printing as it will reset the idle timeout. If careful timing is not needed, the optional SYNC=0 parameter can be specified to apply the changes without resetting the idle timeout.
    
+
    SET_LED_TEMPLATE
    
+
    SET_LED_TEMPLATE LED=<led_name> TEMPLATE=<template_name> [<param_x>=<literal>] [INDEX=<index>]: Assign a display_template to a given LED. For example, if one defined a [display_template my_led_template] config section then one could assign TEMPLATE=my_led_template here. The display_template should produce a comma separated string containing four floating point numbers corresponding to red, green, blue, and white color settings. The template will be continuously evaluated and the LED will be automatically set to the resulting colors. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If INDEX is not specified then all chips in the LED's daisy-chain will be set to the template, otherwise only the chip with the given index will be updated. If TEMPLATE is an empty string then this command will clear any previous template assigned to the LED (one can then use SET_LED commands to manage the LED's color settings).
    
+
    [load_cell]
    
+
    The following commands are enabled if a load_cell config section has been enabled.
    
+
    LOAD_CELL_DIAGNOSTIC
    
+
    LOAD_CELL_DIAGNOSTIC [LOAD_CELL=<config_name>]: This command collects 10 seconds of load cell data and reports statistics that can help you verify proper operation of the load cell. This command can be run on both calibrated and uncalibrated load cells.
    
+
    LOAD_CELL_CALIBRATE
    
+
    LOAD_CELL_CALIBRATE [LOAD_CELL=<config_name>]: Start the guided calibration utility. Calibration is a 3 step process:
    
+
      
+
    1. First you remove all load from the load cell and run the TARE command
      2. 
+
    2. Next you apply a known load to the load cell and run the CALIBRATE GRAMS=nnn command
      3. 
+
    3. Finally use the ACCEPT command to save the results
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    LOAD_CELL_TARE
    
+
    LOAD_CELL_TARE [LOAD_CELL=<config_name>]: This works just like the tare button on digital scale. It sets the current raw reading of the load cell to be the zero point reference value. The response is the percentage of the sensors range that was read and the raw value in counts.
    
+
    LOAD_CELL_READ load_cell="name"
    
+
    LOAD_CELL_READ [LOAD_CELL=<config_name>]: This command takes a reading from the load cell. The response is the percentage of the sensors range that was read and the raw value in counts. If the load cell is calibrated a force in grams is also reported.
    
 
    [manual_probe]
    
 
    模組manual_probe已自動載入.
    
 
    MANUAL_PROBE
    
@@ -5049,12 +5143,6 @@ section is enabled.
    
 
    The following command is available when a mcp4018 config section is enabled.
    
 
    SET_DIGIPOT
    
 
    SET_DIGIPOT DIGIPOT=config_name WIPER=<value>: This command will change the current value of the digipot. This value should typically be between 0.0 and 1.0, unless a 'scale' is defined in the config. When 'scale' is defined, then this value should be between 0.0 and 'scale'.
    
-
    [led]
    
-
    The following command is available when any of the led config sections are enabled.
    
-
    SET_LED
    
-
    SET_LED LED=<config_name> RED=<value> GREEN=<value> BLUE=<value> WHITE=<value> [INDEX=<index>] [TRANSMIT=0] [SYNC=1]: This sets the LED output. Each color <value> must be between 0.0 and 1.0. The WHITE option is only valid on RGBW LEDs. If the LED supports multiple chips in a daisy-chain then one may specify INDEX to alter the color of just the given chip (1 for the first chip, 2 for the second, etc.). If INDEX is not provided then all LEDs in the daisy-chain will be set to the provided color. If TRANSMIT=0 is specified then the color change will only be made on the next SET_LED command that does not specify TRANSMIT=0; this may be useful in combination with the INDEX parameter to batch multiple updates in a daisy-chain. By default, the SET_LED command will sync it's changes with other ongoing gcode commands. This can lead to undesirable behavior if LEDs are being set while the printer is not printing as it will reset the idle timeout. If careful timing is not needed, the optional SYNC=0 parameter can be specified to apply the changes without resetting the idle timeout.
    
-
    SET_LED_TEMPLATE
    
-
    SET_LED_TEMPLATE LED=<led_name> TEMPLATE=<template_name> [<param_x>=<literal>] [INDEX=<index>]: Assign a display_template to a given LED. For example, if one defined a [display_template my_led_template] config section then one could assign TEMPLATE=my_led_template here. The display_template should produce a comma separated string containing four floating point numbers corresponding to red, green, blue, and white color settings. The template will be continuously evaluated and the LED will be automatically set to the resulting colors. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If INDEX is not specified then all chips in the LED's daisy-chain will be set to the template, otherwise only the chip with the given index will be updated. If TEMPLATE is an empty string then this command will clear any previous template assigned to the LED (one can then use SET_LED commands to manage the LED's color settings).
    
 
    [output_pin]
    
 
    當啟用 output_pin config section 時，以下命令可用。
    
 
    SET_PIN
    
@@ -5077,10 +5165,6 @@ section is enabled.
    
 
    PALETTE_CUT:該命令指引Palette 2切割耗材並且裝載分段的耗材。
    
 
    PALETTE_SMART_LOAD
    
 
    PALETTE_SMART_LOAD：該命令在Palette 2上啟動智慧載入序列。通過在裝置上為印表機校準的距離擠壓，自動載入耗材，並在載入完成後指示Palette 2。該命令與耗材載入完成後直接在Palette 2螢幕上按Smart Load相同。
    
-
    [pid_calibrate]
    
-
    如果在配置文件中定義了加熱器，則會自動載入 pid_calibrate 模塊。
    
-
    PID_CALIBRATE
    
-
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]：執行一個PID校準測試。指定的加熱器將被啟用，直到達到指定的目標溫度，然後加熱器將被關閉和開啟幾個週期。如果WRITE_FILE參數被啟用，那麼將建立檔案/tmp/heattest.txt，其中包含測試期間所有溫度樣本的日誌。
    
 
    [pause_resume]
    
 
    當pause_resume 配置分段被啟用時，以下命令可用：
    
 
    PAUSE
    
@@ -5091,6 +5175,10 @@ section is enabled.
    
 
    CLEAR_PAUSE:清除目前的暫停狀態而不恢復列印。如果一個人決定在暫停后取消列印，這很有用。建議將其新增到你的啟動程式碼中，以確保每次列印時的暫停狀態是新的。
    
 
    CANCEL_PRINT
    
 
    CANCEL_PRINT：取消目前的列印。
    
+
    [pid_calibrate]
    
+
    如果在配置文件中定義了加熱器，則會自動載入 pid_calibrate 模塊。
    
+
    PID_CALIBRATE
    
+
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]：執行一個PID校準測試。指定的加熱器將被啟用，直到達到指定的目標溫度，然後加熱器將被關閉和開啟幾個週期。如果WRITE_FILE參數被啟用，那麼將建立檔案/tmp/heattest.txt，其中包含測試期間所有溫度樣本的日誌。
    
 
 
    The print_stats module is automatically loaded.
    
 
    SET_PRINT_STATS_INFO
    
@@ -5158,7 +5246,7 @@ section is enabled.
    
 
    [save_variables]
    
 
    如果啟用了 save_variables config section，則啟用以下命令。
    
 
    SAVE_VARIABLE
    
-
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>：將變數儲存到磁碟，以便在重新啟動時使用。所有儲存的變數都會在啟動時載入到 printer.save_variables.variables 目錄中，並可以在 gcode 宏中使用。所提供的 VALUE 會被解析為一個 Python 字面。
    
+
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>: Saves the variable to disk so that it can be used across restarts. The VARIABLE must be lowercase. All stored variables are loaded into the printer.save_variables.variables dict at startup and can be used in gcode macros. The provided VALUE is parsed as a Python literal.
    
 
    [screws_tilt_adjust]
    
 
    當啟用 screws_tilt_adjust config section 時，以下命令可用（另請參閱 [manual level guide](Manual_Level.md#adjusting-bed-leveling-screws-using-the-bed-probe ））。
    
 
    SCREWS_TILT_CALCULATE
    
@@ -5199,6 +5287,18 @@ section is enabled.
    
 
    當啟用 temperature_fan config section 時，以下命令可用。
    
 
    SET_TEMPERATURE_FAN_TARGET
    
 
    SET_TEMPERATURE_FAN_TARGET temperature_fan=<temperature_fan_名稱> [target=<目標溫度>] [min_speed=<最小速度>] [max_speed=<最大速度>]：設定一個溫度控制風扇的目標溫度。如果沒有提供目標溫度，它將被設為配置檔案中定義的溫度。如果沒有提供速度，則不會進行任何更改。
    
+
    [temperature_probe]
    
+
    The following commands are available when a temperature_probe config section is enabled.
    
+
    TEMPERATURE_PROBE_CALIBRATE
    
+
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
+
    TEMPERATURE_PROBE_NEXT
    
+
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
+
    TEMPERATURE_PROBE_COMPLETE:
    
+
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
+
    ABORT
    
+
    ABORT: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.
    
+
    TEMPERATURE_PROBE_ENABLE
    
+
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
    [tmcXXXX]
    
 
    當啟用任何 tmcXXXX config sections 時，以下命令可用。
    
 
    DUMP_TMC
    
@@ -5246,18 +5346,6 @@ section is enabled.
    
 
    當啟用 z_tilt config section 時，以下命令可用。
    
 
    Z_TILT_ADJUST
    
 
    Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]: 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 RETRIES, RETRY_TOLERANCE, and HORIZONTAL_MOVE_Z values override those options specified in the config file.
    
-
    [temperature_probe]
    
-
    The following commands are available when a temperature_probe config section is enabled.
    
-
    TEMPERATURE_PROBE_CALIBRATE
    
-
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
-
    TEMPERATURE_PROBE_NEXT
    
-
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
-
    TEMPERATURE_PROBE_COMPLETE:
    
-
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
-
    ABORT
    
-
    ABORT: Aborts the calibration process, discarding the current results. This command is only available during drift calibration.
    
-
    TEMPERATURE_PROBE_ENABLE
    
-
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
               
             
diff --git a/zh-Hant/Hall_Filament_Width_Sensor.html b/zh-Hant/Hall_Filament_Width_Sensor.html
index 0a6924834..2ed2de2a4 100644
--- a/zh-Hant/Hall_Filament_Width_Sensor.html
+++ b/zh-Hant/Hall_Filament_Width_Sensor.html
@@ -1357,8 +1357,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Installation.html b/zh-Hant/Installation.html
index 8b43a1341..ff9987b55 100644
--- a/zh-Hant/Installation.html
+++ b/zh-Hant/Installation.html
@@ -1366,8 +1366,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
 
 
    安裝
    
-
    These instructions assume the software will run on a linux based host running a Klipper compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian based Linux device be used as the host machine (see the FAQ for other options).
    
-
    For the purposes of these instructions host relates to the Linux device and mcu relates to the printboard. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
+
    These instructions assume the software will run on a Linux-based host running a Klipper-compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian-based Linux device be used as the host machine (see the FAQ for other options).
    
+
    For the purposes of these instructions, host relates to the Linux device and mcu relates to the printer board. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
 
    獲取 Klipper 配置文件
    
 
    Most Klipper settings are determined by a "printer configuration file" printer.cfg, that will be stored on the host. An appropriate configuration file can often be found by looking in the Klipper config directory for a file starting with a "printer-" prefix that corresponds to the target printer. The Klipper configuration file contains technical information about the printer that will be needed during the installation.
    
 
    如果 Klipper 配置目錄中沒有合適的打印機配置文件，請嘗試搜索打印機製造商的網站，看看他們是否有合適的 Klipper 配置文件。
    
@@ -1493,13 +1493,13 @@
 
    Currently the best choices are front ends that retrieve information through the Moonraker web API and there is also the option to use Octoprint to control Klipper.
    
 
    The choice is up to the user on what to use, but the underlying Klipper is the same in all cases. We encourage users to research the options available and make an informed decision.
    
 
    Obtaining an OS image for SBC's
    
-
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manafactures of these SBC boards also provide their own Klipper-centric images.
    
-
    The two main Moonraker based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi varianta.
    
+
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manufacturers of these SBC boards also provide their own Klipper-centric images.
    
+
    The two main Moonraker-based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi variants.
    
 
    Fluidd can be installed via KIAUH(Klipper Install And Update Helper), which is explained below and is a 3rd party installer for all things Klipper.
    
 
    OctoPrint can be installed via the popular OctoPi image or via KIAUH, this process is explained in 
    
 
    Installing via KIAUH
    
-
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of a x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions working and even mask access to some print boards.
    
-
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
+
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of an x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions from working and even mask access to some printer boards.
    
+
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux-based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
 
    構建和刷寫微控制器
    
 
    To compile the micro-controller code, start by running these commands on your host device:
    
 
    cd ~/klipper/
@@ -1510,7 +1510,7 @@ make menuconfig
 
    make
 
    
 
-
    如果 打印機配置文件 頂部的註釋描述了將最終圖像“閃爍”到打印機控制板的自定義步驟，則按照這些步驟操作，然後繼續 配置OctoPrint。
    
+
    If the comments at the top of the printer configuration file describe custom steps for "flashing" the final image to the printer control board, then follow those steps and then proceed to configuring OctoPrint.
    
 
    否則，通常使用以下步驟來“刷新”打印機控制板。首先，需要確定連接到微控制器的串口。運行以下命令：
    
 
    ls /dev/serial/by-id/*
 
    
@@ -1520,8 +1520,8 @@ make menuconfig
 
    
 
 
    It's common for each printer to have its own unique serial port name. This unique name will be used when flashing the micro-controller. It's possible there may be multiple lines in the above output - if so, choose the line corresponding to the micro-controller. If many items are listed and the choice is ambiguous, unplug the board and run the command again, the missing item will be your print board(see the FAQ for more information).
    
-
    For common micro-controllers with STM32 or clone chips, LPC chips and others it is usual that these need an initial Klipper flash via SD card.
    
-
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occuring.
    
+
    For common micro-controllers with STM32 or clone chips, LPC chips and others, it is usual that these need an initial Klipper flash via SD card.
    
+
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring.
    
 
    For common micro-controllers using Atmega chips, for example the 2560, the code can be flashed with something similar to:
    
 
    sudo service klipper stop
 make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
@@ -1538,9 +1538,9 @@ sudo service klipper start
 
    It is important to note that RP2040 chips may need to be put into Boot mode before this operation.
    
 
    配置 Klipper
    
 
    The next step is to copy the printer configuration file to the host.
    
-
    Arguably the easiest way to set the Klipper configuration file is using the built in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
+
    Arguably the easiest way to set the Klipper configuration file is using the built-in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
 
    Another option is to use a desktop editor that supports editing files over the "scp" and/or "sftp" protocols. There are freely available tools that support this (eg, Notepad++, WinSCP, and Cyberduck). Load the printer config file in the editor and then save it as a file named "printer.cfg" in the home directory of the pi user (ie, /home/pi/printer.cfg).
    
-
    Alternatively, one can also copy and edit the file directly on the host via ssh. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
+
    Alternatively, one can also copy and edit the file directly on the host via SSH. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
 
    cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
 nano ~/printer.cfg
 
    
@@ -1558,9 +1558,9 @@ nano ~/printer.cfg
 serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
 
    
 
-
    After creating and editing the file it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
+
    After creating and editing the file, it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report that the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
 
    在自定義打印機配置文件時，Klipper 報告配置錯誤的情況並不少見。如果發生錯誤，請對打印機配置文件進行任何必要的更正並發出“restart”，直到“status”報告打印機已準備好。
    
-
    Klipper reports error messages via the command console and via pop up in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located in ~/printer_data/logs this is named klippy.log
    
+
    Klipper reports error messages via the command console and pop-ups in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located at ~/printer_data/logs/klippy.log.
    
 
    在 Klipper 報告打印機準備就緒後，進入 配置檢查文檔 對配置文件中的定義進行一些基本檢查。有關其他信息，請參閱主要 文檔參考。
    
 
               
diff --git a/zh-Hant/Kinematics.html b/zh-Hant/Kinematics.html
index d05fc3df1..e6291130a 100644
--- a/zh-Hant/Kinematics.html
+++ b/zh-Hant/Kinematics.html
@@ -1411,8 +1411,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Load_Cell.html b/zh-Hant/Load_Cell.html
new file mode 100644
index 000000000..8b2186a13
--- /dev/null
+++ b/zh-Hant/Load_Cell.html
@@ -0,0 +1,1635 @@
+
+
+
+  
+    
+      
+      
+      
+      
+      
+      
+      
+    
+    
+      
+        Load Cells - Klipper 文檔
+      
+    
+    
+      
+      
+        
+        
+        
+      
+    
+    
+    
+      
+        
+        
+        
+        
+      
+    
+    
+      
+    
+    
+    
+      
+  
+
+
+  
+  
+
+
+  
+  
+
+
+    
+    
+  
+  
+  
+    
+    
+      
+    
+    
+    
+    
+    
+  
+    
+    
+      
+    
+    
+    
+    
+    
    
+      
+        
+        
+          跳轉至
+        
+      
+    
    
+    
    
+      
+    
    
+    
+    
+      
+
+
    
+  
+  
+
    
+    
+    
    
+      
+      
+        
+          
+        
+      
+      
    
+        
    
+          
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+
+                  
    
+                
    
+              
    
+            
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+                  
    
+                
    
+              
    
+            
+          
+          
    
+            
    
+              
+                
+
+  
+
+
+
+
    Load Cells
    
+
    This document describes Klipper's support for load cells. Basic load cell functionality can be used to read force data and to weigh things like filament. A calibrated force sensor is an important part of a load cell based probe.
    
+
+
+
    Using LOAD_CELL_DIAGNOSTIC
    
+
    When you first connect a load cell its good practice to check for issues by running LOAD_CELL_DIAGNOSTIC. This tool collects 10 seconds of data from the load cell and resport statistics:
    
+
    $ LOAD_CELL_DIAGNOSTIC
+// Collecting load cell data for 10 seconds...
+// Samples Collected: 3211
+// Measured samples per second: 332.0
+// Good samples: 3211, Saturated samples: 0, Unique values: 900
+// Sample range: [4.01% to 4.02%]
+// Sample range / sensor capacity: 0.00524%
+
    
+
+
    Things you can check with this data:
    
+
      
+
    • The configured sample rate of the sensor should be close to the 'Measured samples per second' value. If it is not you may have a configuration or wiring issue.
      • 
+
    • 'Saturated samples' should be 0. If you have saturated samples it means the load sell is seeing more force than it can measure.
      • 
+
    • 'Unique values' should be a large percentage of the 'Samples Collected' value. If 'Unique values' is 1 it is very likely a wiring issue.
      • 
+
    • Tap or push on the sensor while LOAD_CELL_DIAGNOSTIC runs. If things are working correctly ths should increase the 'Sample range'.
      • 
+
    
+
    Calibrating a Load Cell
    
+
    Load cells are calibrated using the LOAD_CELL_CALIBRATE command. This is an interactive calibration utility that walks you though a 3 step process:
    
+
      
+
    1. First use the TARE command to establish the zero force value. This is the reference_tare_counts config value.
      2. 
+
    2. Next you apply a known load or force to the load cell and run the CALIBRATE GRAMS=nnn command. From this the counts_per_gram value is calculated. See the next section for some suggestions on how to do this.
      3. 
+
    3. Finally, use the ACCEPT command to save the results.
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    Applying a Known Force or Load
    
+
    The CALIBRATE GRAMS=nnn step can be accomplished in a number of ways. If your load cell is under a platform like a bed or filament holder it might be easiest to put a known mass on the platform. E.g. you could use a couple of 1KG filament spools.
    
+
    If your load cell is in the printer's toolhead a different approach is easier. Put a digital scale on the printers bed and gently lower the toolhead onto the scale (or raise the bed into the toolhead if your bed moves). You may be able to do this using the FORCE_MOVE command. But more likely you will have to manually moving the z axis with the motors off until the toolhead presses on the scale.
    
+
    A good calibration force would ideally be a large percentage of the load cell's rated capacity. E.g. if you have a 5Kg load cell you would ideally calibrate it with a 5kg mass. This might work well with under-bed sensors that have to support a lot of weight. For toolhead probes this may not be a load that your printer bed or toolhead can tolerate without damage. Do try to use at least 1Kg of force, most printers should tolerate this without issue.
    
+
    When calibrating make careful note of the values reported:
    
+
    $ CALIBRATE GRAMS=555
+// Calibration value: -2.78% (-59803108), Counts/gram: 73039.78739,
+Total capacity: +/- 29.14Kg
+
    
+
+
    The Total capacity should be close to the theoretical rating of the load cell based on the sensor's capacity. If it is much larger you could have used a higher gain setting in the sensor or a more sensitive load cell. This isn't as critical for 32bit and 24bit sensors but is much more critical for low bit width sensors.
    
+
    Reading Force Data
    
+
    Force data can be read with a GCode command:
    
+
    LOAD_CELL_READ
+// 10.6g (1.94%)
+
    
+
+
    Data is also continuously read and can be consumed from the load_cell printer object in a macro:
    
+
    {% set grams = printer.load_cell.force_g %}
+
    
+
+
    This provides an average force over the last 1 second, similar to how temperature sensors work.
    
+
    Taring a Load Cell
    
+
    Taring, sometimes called zeroing, sets the current weight reported by the load_cell to 0. This is useful for measuring relative to a known weight. e.g. when measuring a filament spool, using LOAD_CELL_TARE sets the weight to 0. Then as filament is printed the load_cell will report the weight of the filament used.
    
+
    LOAD_CELL_TARE
+// Load cell tare value: 5.32% (445903)
+
    
+
+
    The current tare value is reported in the printers status and can be read in a macro:
    
+
    {% set tare_counts = printer.load_cell.tare_counts %}
+
    
+
+              
+            
    
+          
    
+        
    
+        
+          
+            
+            Back to top
+          
+        
+      
    
+      
+        
+      
+    
    
+    
    
+      
    
+    
    
+    
+    
+    
+      
+      
+    
+  
+
\ No newline at end of file
diff --git a/zh-Hant/MCU_Commands.html b/zh-Hant/MCU_Commands.html
index e17005005..e0176e479 100644
--- a/zh-Hant/MCU_Commands.html
+++ b/zh-Hant/MCU_Commands.html
@@ -1383,8 +1383,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Manual_Level.html b/zh-Hant/Manual_Level.html
index 4d79435f0..17a91ef1a 100644
--- a/zh-Hant/Manual_Level.html
+++ b/zh-Hant/Manual_Level.html
@@ -1358,8 +1358,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh-Hant/Measuring_Resonances.html b/zh-Hant/Measuring_Resonances.html
index 3c98a03af..d30e6ddfb 100644
--- a/zh-Hant/Measuring_Resonances.html
+++ b/zh-Hant/Measuring_Resonances.html
@@ -838,11 +838,11 @@
       
    
 
-
    The test was last run on commit f6718291 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.
    
+
    The test was last run on commit 14c105b8 with gcc version arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0 on Raspberry Pi Pico and Pico 2 boards.
    
 
@@ -2226,11 +2226,11 @@ finalize_config crc=0
 
-
+
-
+
    
 
 
    
 
    
 1个步进电机53
 
    
 
    
 3个步进电机2214
 
    
     
 
    
@@ -2252,7 +2252,7 @@ finalize_config crc=0
 
 
 
-
    (*) 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.
    
+
    (*) Note that the reported rp2040 ticks are relative to a 12Mhz scheduling timer and do not correspond to its 200Mhz internal ARM processing rate. It is expected that 5 scheduling ticks corresponds to ~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 ARM core cycles.
    
 
    Linux MCU 步速率基准测试
    
 
    树莓派上使用以下配置序列：
    
 
    allocate_oids count=3
diff --git a/zh/Bootloader_Entry.html b/zh/Bootloader_Entry.html
index 4ec86296b..43fcca328 100644
--- a/zh/Bootloader_Entry.html
+++ b/zh/Bootloader_Entry.html
@@ -1429,8 +1429,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Bootloaders.html b/zh/Bootloaders.html
index d2bf634ee..11ec0f5c1 100644
--- a/zh/Bootloaders.html
+++ b/zh/Bootloaders.html
@@ -1501,8 +1501,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/CANBUS.html b/zh/CANBUS.html
index 0d06810ae..46d7c26f0 100644
--- a/zh/CANBUS.html
+++ b/zh/CANBUS.html
@@ -1371,8 +1371,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1549,6 +1549,7 @@ iface can0 can static
 
 
 
      
+
    • It is only valid to use USB to CAN bridge mode if there is a functioning CAN bus with at least one other node available (in addition to the bridge node itself). Use a standard USB configuration if the goal is to communicate only with the single USB device. Using USB to CAN bridge mode without a fully functioning CAN bus (including terminating resistors and an additional node) may result in sporadic errors even when communicating with the bridge node.
      • 
 
    • USB转CAN桥板不会显示为USB串口设备，也不会在运行ls/dev/Serial/by-id时出现，也不能在Klipper的printer.cfg文件中使用Serial：参数进行配置。桥接板显示为“USB CAN适配器”，并在printer.cfg中配置为CAN节点。
      • 
 
    
 
    故障排除提示
    
diff --git a/zh/CANBUS_Troubleshooting.html b/zh/CANBUS_Troubleshooting.html
index 6ca988f6e..451b9f216 100644
--- a/zh/CANBUS_Troubleshooting.html
+++ b/zh/CANBUS_Troubleshooting.html
@@ -1284,6 +1284,13 @@
     使用适当的 txqueuelen 设置
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1370,8 +1377,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1444,6 +1451,13 @@
     使用适当的 txqueuelen 设置
   
   
+
+      
+        
  • 
+  
+    Use canbus_query.py only to identify nodes never previously seen
+  
+  
 
    • 
       
         
  • 
@@ -1500,12 +1514,16 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    确认CAN总线接线上的所有插头和线夹都已完全固定。打印机刀头的移动可能会挤压CAN总线布线，导致不良的线缆卷曲或未固定的插头，从而导致间歇性通信错误。
    
 
    检查递增BYTES_INVALID计数器
    
 
    当打印机处于活动状态时，Klipper日志文件将每秒报告一次Stats‘行。对于每个微控制器，这些“Stat”行都将有一个bytes_valid`计数器。在正常的打印机操作期间，此计数器不应递增(重新启动后计数器为非零值是正常的，如果计数器每月递增一次也无关紧要)。如果在正常打印过程中，CAN Bus微控制器上的此计数器增加(每隔几个小时或更频繁地增加一次)，则表示存在严重问题。
    
-
    在CAN总线连接上递增BYTES_INVALID是CAN总线上消息重新排序的症状。消息重新排序有两个已知原因：
    
-
      
-
    1. 用于USB CAN适配器的常用烛光固件的旧版本有一个错误，可能会导致消息重新排序。如果使用运行此固件的USB CAN适配器，则在观察到递增的Bytes_Invalid时，请确保更新到最新固件。
      2. 
-
    2. 已知一些用于嵌入式设备的Linux内核版本会对CAN总线消息进行重新排序。可能需要使用替代的Linux内核，或者使用支持不存在此问题的主流Linux内核的替代硬件。
      3. 
-
    
-
    重新排序的消息是一个必须解决的严重问题。这将导致行为不稳定，并可能导致打印的任何部分出现令人困惑的错误。
    
+
    Incrementing bytes_invalid on a CAN bus connection is a symptom of reordered messages on the CAN bus. If seen, make sure to:
    
+
      
+
    • Use a Linux kernel version 6.6.0 or later.
      • 
+
    • If using a USB-to-CANBUS adapter running candlelight firmware, use v2.0 or later of candleLight_fw.
      • 
+
    • If using Klipper's USB-to-CANBUS bridge mode, make sure the bridge node is flashed with Klipper v0.12.0 or later.
      • 
+
    
+
    Reordered messages is a severe problem that must be fixed. It will result in unstable behavior and can lead to confusing errors at any part of a print. An incrementing bytes_invalid is not caused by wiring or similar hardware issues and can only be fixed by identifying and updating the faulty software.
    
+
    Older versions of the Linux kernel had a bug in the gs_usb canbus driver code that could cause reordered canbus packets. The issue is thought to be fixed in Linux commit 24bc41b4 which was released in v6.6.0. In some cases, older Linux versions may not show the problem (due to how hardware interrupts are configured), however if problems are seen the recommended solution is to upgrade to a newer kernel.
    
+
    Older versions of candlelight firmware could reorder canbus packets, and the issue is thought to be fixed in candlelight_fw commit 8b3a7b45.
    
+
    Older versions of Klipper's USB-to-CANBUS bridge code could incorrectly drop canbus messages. This is not as severe as reordering messages, but it should still be fixed. It is thought to be fixed with Klipper PR #6175.
    
 
    使用适当的 txqueuelen 设置
    
 
    Klipper 代码使用 Linux 内核来管理 CAN 总线流量。默认情况下，内核只会排队 10 个 CAN 传输数据包。建议使用 txqueuelen 128 配置 can0 设备 来增加该大小。
    
 
    如果 Klipper 传输了一个数据包，而 Linux 已经填满了其所有的传输队列空间，那么 Linux 将丢弃该数据包，并且 Klipper 日志中将出现如下消息：
    
@@ -1517,6 +1535,10 @@ resistors on the CAN bus. If the resistors are not properly installed then m
 
    可以通过运行 Linux 命令“ip link show can0”来检查当前队列大小。它应该会报告一堆文本，包括代码片段“qlen 128”。如果看到类似“qlen 10”的内容，则表明 CAN 设备尚未正确配置。
    
 
    不建议使用明显大于 128 的 txqueuelen。以 1000000 频率运行的 CAN 总线通常需要大约 120us 来传输 CAN 数据包。因此，128 个数据包的队列可能需要大约 15-20ms 才能耗尽。大得多的队列可能会导致消息往返时间出现过度峰值，从而导致无法恢复的错误。换句话说，如果 Klipper 的应用程序重传系统不必等待 Linux 耗尽可能过时的过大队列，它会更加强大。这类似于互联网路由器上的 bufferbloat 问题。
    
 
    在正常情况下，Klipper 可能每个 MCU 使用约 25 个队列槽 - 通常仅在重传期间使用更多槽。（具体而言，Klipper 主机可能向每个 Klipper MCU 传输最多 192 个字节，然后才会收到该 MCU 的确认。）如果单个 CAN 总线上有 5 个或更多 Klipper MCU，则可能需要将txqueuelen增加到建议值 128 以上。但是，如上所述，选择新值时应小心谨慎，以避免过长的往返时间延迟。
    
+
    Use canbus_query.py only to identify nodes never previously seen
    
+
    It is only valid to use the canbus_query.py tool to identify micro-controllers that have never been previously identified. Once all nodes on a bus are identified, record the resulting uuids in the printer.cfg, and avoid running the tool unnecessarily.
    
+
    The tool is implemented using a low-level mechanism that can cause nodes to internally observe bus errors. These internal errors may result in communication interruptions and may result is some nodes disconnecting from the bus.
    
+
    It is not valid to use the tool to "ping" if a node is connected. Do not run the tool during an active print.
    
 
    获取candump日志
    
 
    向微控制器发送和从微控制器发送的CAN总线消息由Linux内核处理。出于调试目的，可以从内核捕获这些消息。这些消息的日志可能在诊断中有用。
    
 
    Linuxcan-utils工具提供了捕获软件。通常通过运行以下命令将其安装在计算机上：
    
diff --git a/zh/CANBUS_protocol.html b/zh/CANBUS_protocol.html
index ed2ae37ca..72671a8fd 100644
--- a/zh/CANBUS_protocol.html
+++ b/zh/CANBUS_protocol.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/CONTRIBUTING.html b/zh/CONTRIBUTING.html
index 202da6fba..879b292bc 100644
--- a/zh/CONTRIBUTING.html
+++ b/zh/CONTRIBUTING.html
@@ -1370,8 +1370,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Code_Overview.html b/zh/Code_Overview.html
index 041d0fc55..dd46b129a 100644
--- a/zh/Code_Overview.html
+++ b/zh/Code_Overview.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Command_Templates.html b/zh/Command_Templates.html
index 81340f8e4..599a02b82 100644
--- a/zh/Command_Templates.html
+++ b/zh/Command_Templates.html
@@ -1421,8 +1421,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Config_Changes.html b/zh/Config_Changes.html
index afe47ebeb..fdb5847b2 100644
--- a/zh/Config_Changes.html
+++ b/zh/Config_Changes.html
@@ -1327,8 +1327,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1410,6 +1410,12 @@
 
    本文档涵盖了软件更新中对配置文件不向后兼容的部分。在升级 Klipper 时，最好也查看一下这份文档。
    
 
    文档的所有日期都是大概时间。
    
 
    变更
    
+
    20250428: The maximum cycle_time for pwm [output_pin], [pwm_cycle_time], [pwm_tool], and similar config sections is now 3 seconds (reduced from 5 seconds). The maximum_mcu_duration in [pwm_tool] is now also 3 seconds.
    
+
    20250418: The manual_stepper STOP_ON_ENDSTOP feature may now take less time to complete. Previously, the command would wait the entire time the move could possibly take even if the endstop triggered earlier. Now, the command finishes shortly after the endstop trigger.
    
+
    20250417: SPI devices using "software SPI" are now rate limited. Previously, the spi_speed in the config was ignored and the transmission speed was only limited by the processing speed of the micro-controller. Now, speeds are limited by the spi_speed config parameter (actual hardware speeds are likely to be lower than the configured value due to software overhead).
    
+
    20250411: Klipper v0.13.0 released.
    
+
    20250308: The AUTO parameter of the AXIS_TWIST_COMPENSATION_CALIBRATE command has been removed.
    
+
    20250131: Option VARIABLE=<name> in SAVE_VARIABLE requires lowercase value. For example, extruder instead of mixedcase Extruder or uppercase EXTRUDER. Using any uppercase letter will raise an error.
    
 
    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 sweeping_period: 0 and accel_per_hz: 75 to the [resonance_tester] config section.
    
 
    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.
    
 
    20241112: Option CHIPS=<chip_name> in TEST_RESONANCES and SHAPER_CALIBRATE requires specifying the full name(s) of the accel chip(s). For example, adxl345 rpi instead of short name - rpi.
    
diff --git a/zh/Config_Reference.html b/zh/Config_Reference.html
index 896e7e8ad..9e77b7468 100644
--- a/zh/Config_Reference.html
+++ b/zh/Config_Reference.html
@@ -931,6 +931,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -1741,6 +1748,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -2600,8 +2614,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3053,6 +3067,13 @@
     [adxl345]
   
   
+
+        
+          
  • 
+  
+    [icm20948]
+  
+  
 
    • 
         
           
  • 
@@ -3863,6 +3884,13 @@
     [adc_scaled]
   
   
+
    • 
+        
+          
  • 
+  
+    [ads1x1x]
+  
+  
 
    • 
         
           
  • 
@@ -5212,6 +5240,22 @@ cs_pin:
 #   共振测量的质量。
 
    • 
 
+
    [icm20948]
    
+
    Support for icm20948 accelerometers.
    
+
    [icm20948]
+#i2c_address:
+#   Default is 104 (0x68). If AD0 is high, it would be 0x69 instead.
+#i2c_mcu:
+#i2c_bus:
+#i2c_software_scl_pin:
+#i2c_software_sda_pin:
+#i2c_speed: 400000
+#   See the "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.
+
    
+
 
    [lis2dw]
    
 
    Support for LIS2DW accelerometers.
    
 
    [lis2dw]
@@ -5529,6 +5573,9 @@ z_offset:
 sensor_type: ldc1612
 #   The sensor chip used to perform eddy current measurements. This
 #   parameter must be provided and must be set to ldc1612.
+#frequency:
+#   The external crystal frequency (in Hz) of the LDC1612 chip.
+#   The default is 12000000.
 #intb_pin:
 #   MCU gpio pin connected to the ldc1612 sensor's INTB pin (if
 #   available). The default is to not use the INTB pin.
@@ -6436,20 +6483,27 @@ pin:
 
    在一个按钮被按下或放开（或当一个引脚状态发生变化时）时运行G代码。你可以使用 QUERY_BUTTON button=my_gcode_button 来查询按钮的状态。
    
 
    [gcode_button my_gcode_button]
 pin:
-#   连接到按钮的引脚。
-#   必须提供此参数。
+#   The pin on which the button is connected. This parameter must be
+#   provided.
 #analog_range:
-#   两个逗号分隔的阻值(单位：欧姆)，指定了按钮的最小和最大电阻。
-#   如果提供了 analog_range ，必须使用一个模拟功能的引脚。默认
-#   情况下为按钮使用数字GPIO。
-#   analog_pullup_resistor:
-#   当定义 analog_range 时的上拉电阻(欧姆)。默认为4700欧姆。
+#   Two comma separated resistances (in Ohms) specifying the minimum
+#   and maximum resistance range for the button. If analog_range is
+#   provided then the pin must be an analog capable pin. The default
+#   is to use digital gpio for the button.
+#analog_pullup_resistor:
+#   The pullup resistance (in Ohms) when analog_range is specified.
+#   The default is 4700 ohms.
 #press_gcode:
-#   当按钮被按下时要执行的 G-Code 命令序列，支持G-Code模板。
-#   必须提供此参数。
+#   A list of G-Code commands to execute when the button is pressed.
+#   G-Code templates are supported. This parameter must be provided.
 #release_gcode:
-#   当按钮被释放时要执行的G-Code命令序列，支持G-Code模板。
-#   默认在按钮释放时不运行任何命令。
+#   A list of G-Code commands to execute when the button is released.
+#   G-Code templates are supported. The default is to not run any
+#   commands on a button release.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   button gcode. If the button is pressed and released during this
+#   delay, the entire button press is ignored. Default is 0.
 
    
 
 
    [output_pin]
    
@@ -6582,8 +6636,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -6632,6 +6687,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 4
 #driver_PWM_AMPL: 128
+#driver_FREEWHEEL: 0
 #driver_SGT: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6689,8 +6745,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #driver_MULTISTEP_FILT: True
 #driver_IHOLDDELAY: 8
 #driver_TPOWERDOWN: 20
@@ -6705,6 +6762,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #   Set the given register during the configuration of the TMC2208
 #   chip. This may be used to set custom motor parameters. The
 #   defaults for each parameter are next to the parameter name in the
@@ -6748,6 +6806,7 @@ run_current:
 #driver_PWM_FREQ: 1
 #driver_PWM_GRAD: 14
 #driver_PWM_OFS: 36
+#driver_FREEWHEEL: 0
 #driver_SGTHRS: 0
 #driver_SEMIN: 0
 #driver_SEUP: 0
@@ -6864,8 +6923,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -6992,8 +7052,9 @@ run_current:
 #stealthchop_threshold: 0
 #   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.
+#   velocity is below this value. Note that the "sensorless homing"
+#   code may temporarily override this setting during homing
+#   operations. The default is 0, which disables "stealthChop" mode.
 #coolstep_threshold:
 #   The velocity (in mm/s) to set the TMC driver internal "CoolStep"
 #   threshold to. If set, the coolstep feature will be enabled when
@@ -7575,35 +7636,39 @@ text:
 
    [filament_switch_sensor]
    
 
    耗材开关传感器。支持使用开关传感器（如限位开关）进行耗材插入和耗尽检测。
    
 
    更多信息请参阅命令参考。
    
-
    [filament_switch_sensor my_sensor]。
+
    [filament_switch_sensor my_sensor]
 #pause_on_runout: True
-#   当设置为 "True "时，会在检测到耗尽后立即暂停打印机。
-#   请注意, 如果 pause_on_runout 为 False 并且没有定义。
-#   runout_gcode的话, 耗尽检测将被禁用。
-#   默认为 True。
+#   When set to True, a PAUSE will execute immediately after a runout
+#   is detected. Note that if pause_on_runout is False and the
+#   runout_gcode is omitted then runout detection is disabled. Default
+#   is True.
 #runout_gcode:
-#   在检测到耗材耗尽后会执行的G代码命令列表。
-#   有关G-Code 格式请见 docs/Command_Templates.md。
-#   如果 pause_on_runout 被设置为 True，这个G-Code将在
-#   暂停后执行。
-#   默认情况是不运行任何 G-Code 命令。
+#   A list of G-Code commands to execute after a filament runout is
+#   detected. See docs/Command_Templates.md for G-Code format. If
+#   pause_on_runout is set to True this G-Code will run after the
+#   PAUSE is complete. The default is not to run any G-Code commands.
 #insert_gcode:
-#   在检测到耗材插入后会执行的 G-Code 命令列表。
-#   关于G代码格式，请参见 docs/Command_Templates.md。
-#   默认不运行任何 G-Code 命令，这将禁用耗材插入检测。
+#   A list of G-Code commands to execute after a filament insert is
+#   detected. See docs/Command_Templates.md for G-Code format. The
+#   default is not to run any G-Code commands, which disables insert
+#   detection.
 #event_delay: 3.0
-#   事件之间的最小延迟时间（秒）。
-#   在这个时间段内触发的事件将被默许忽略。
-#   默认为3秒。
+#   The minimum amount of time in seconds to delay between events.
+#   Events triggered during this time period will be silently
+#   ignored. The default is 3 seconds.
 #pause_delay: 0.5
-#   暂停命令和执行 runout_gcode 之间的延迟时间, 单位是秒。
-#   如果在OctoPrint的情况下，增加这个延迟可能改善暂
-#   停的可靠性。如果OctoPrint表现出奇怪的暂停行为，
-#   考虑增加这个延迟。
-#   默认为0.5秒。
+#   The amount of time to delay, in seconds, between the pause command
+#   dispatch and execution of the runout_gcode. It may be useful to
+#   increase this delay if OctoPrint exhibits strange pause behavior.
+#   Default is 0.5 seconds.
+#debounce_delay:
+#   A period of time in seconds to debounce events prior to running the
+#   switch gcode. The switch must he held in a single state for at least
+#   this long to activate. If the switch is toggled on/off during this delay,
+#   the event is ignored. Default is 0.
 #switch_pin:
-#   连接到检测开关的引脚。
-#   必须提供此参数。
+#   The pin on which the switch is connected. This parameter must be
+#   provided.
 
    
 
 
    [filament_motion_sensor]
    
@@ -7693,6 +7758,16 @@ adc2:
 
    [load_cell]
 sensor_type:
 #   This must be one of the supported sensor types, see below.
+#counts_per_gram:
+#   The floating point number of sensor counts that indicates 1 gram of force.
+#   This value is calculated by the LOAD_CELL_CALIBRATE command.
+#reference_tare_counts:
+#   The integer tare value, in raw sensor counts, taken when LOAD_CELL_CALIBRATE
+#   is run. This is the default tare value when klipper starts up.
+#sensor_orientation:
+#   Change the sensor's orientation. Can be either 'normal' or 'inverted'.
+#   The default is 'normal'. Use 'inverted' if the sensor reports a
+#   decreasing force value when placed under load.
 
    
 
 
    HX711
    
@@ -7836,6 +7911,38 @@ vssa_pin:
 #   VSSA 测量来减少测量的干扰。默认为2秒。
 
    
 
+
    [ads1x1x]
    
+
    ADS1013, ADS1014, ADS1015, ADS1113, ADS1114 and ADS1115 are I2C based Analog to Digital Converters that can be used for temperature sensors. They provide 4 analog input pins either as single line or as differential input.
    
+
    Note: Use caution if using this sensor to control heaters. The heater min_temp and max_temp are only verified in the host and only if the host is running and operating normally. (ADC inputs directly connected to the micro-controller verify min_temp and max_temp within the micro-controller and do not require a working connection to the host.)
    
+
    [ads1x1x my_ads1x1x]
+chip: ADS1115
+#pga: 4.096V
+#   Default value is 4.096V. The maximum voltage range used for the input. This
+#   scales all values read from the ADC. Options are: 6.144V, 4.096V, 2.048V,
+#   1.024V, 0.512V, 0.256V
+#adc_voltage: 3.3
+#   The suppy voltage for the device. This allows additional software scaling
+#   for all values read from the ADC.
+i2c_mcu: host
+i2c_bus: i2c.1
+#address_pin: GND
+#   Default value is GND.  There can be up to four addressed devices depending
+#   upon wiring of the device. Check the datasheet for details. The i2c_address
+#   can be specified directly instead of using the address_pin.
+
    
+
+
    The chip provides pins that can be used on other sensors.
    
+
    sensor_type: ...
+#   Can be any thermistor or adc_temperature.
+sensor_pin: my_ads1x1x:AIN0
+#   A combination of the name of the ads1x1x chip and the pin. Possible
+#   pin values are AIN0, AIN1, AIN2 and AIN3 for single ended lines and
+#   DIFF01, DIFF03, DIFF13 and DIFF23 for differential between their
+#   correspoding lines. For example
+#   DIFF03 measures the differential between line 0 and 3. Only specific
+#   combinations for the differentials are allowed.
+
    
+
 
    [replicape]
    
 
    Replicape支持 - 参考beaglebone guide和generic-replicape.cfg
    
 
    #   "replicape"配置分段添加了"replicape:stepper_x_enable"虚拟步进使能
@@ -7898,7 +8005,7 @@ host_mcu:
 
    Palette 2 多材料支持 - 提供更紧密的集成，支持处于连接模式的 Palette 2 设备。
    
 
    该模块的全部功能需要[virtual_sdcard]和[pause_resume]。
    
 
    不要和 Octoprint 的 Palette 2插件一起使用这个模块，因为它们会发生冲突，造成初始化和打印失败。
    
-
    如果使用 OctoPrint 并通过串行端口流式传输 G-Code，而不通过 virtual_sd 打印，将 * 设置>串行连接>固件和协议 * 中的“暂停命令” 设置为M1 和 M0 可以避免在开始打印时需要在Palette 2 上选择开始打印并在 OctoPrint 中取消暂停。
    
+
    If you use Octoprint and stream gcode over the serial port instead of printing from virtual_sd, then remove M1 and M0 from Pausing commands in Settings > Serial Connection > Firmware & protocol will prevent the need to start print on the Palette 2 and unpausing in Octoprint for your print to begin.
    
 
    [palette2]
 serial:
 #   与 Palette 2 连接的串口。
diff --git a/zh/Config_checks.html b/zh/Config_checks.html
index f24c08084..122f5affe 100644
--- a/zh/Config_checks.html
+++ b/zh/Config_checks.html
@@ -1385,8 +1385,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Contact.html b/zh/Contact.html
index e2876165d..6479b59dc 100644
--- a/zh/Contact.html
+++ b/zh/Contact.html
@@ -451,8 +451,8 @@
 
       
         
  • 
-  
-    Klipper GitHub
+  
+    Professional Services
   
   
 
    • 
@@ -1376,8 +1376,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
       
         
  • 
-  
-    Klipper GitHub
+  
+    Professional Services
   
   
 
    • 
@@ -1558,9 +1558,10 @@
 
    我正在进行一些我想添加到 Klipper 中的改进
    
 
    Klipper 是开源软件，我们非常感谢新的贡献。
    
 
    新的贡献（包括代码和文档）需要通过拉取请求(PR)提交。重要信息请参见贡献文档。
    
-
    有几个开发者文档。如果你对代码有疑问，那么你也可以在Klipper社区论坛或Klipper社区Discord上提问。
    
-
    Klipper GitHub
    
-
    Klipper GitHub可以被贡献者用来分享他们改进Klipper的工作状态。我们希望创建GitHub Ticket的人正在积极地处理给定的任务，并将执行所有必要工作以完成该任务。Klipper GitHub不用于功能请求，也不用于报告bug，更不用于提问。请使用Klipper社区论坛或Klipper社区Discord来代替。
    
+
    There are several documents for developers. If you have questions on the code then you can also ask in the Klipper Discourse Forum or on the Klipper Discord Chat.
    
+
    Professional Services
    
+
    
+
    Custom software development, software support, and solutions: https://ko-fi.com/koconnor
    
 
               
             
diff --git a/zh/Debugging.html b/zh/Debugging.html
index 55def2648..3d15096a0 100644
--- a/zh/Debugging.html
+++ b/zh/Debugging.html
@@ -1384,8 +1384,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Delta_Calibrate.html b/zh/Delta_Calibrate.html
index 6c1805137..ac28df1a7 100644
--- a/zh/Delta_Calibrate.html
+++ b/zh/Delta_Calibrate.html
@@ -1365,8 +1365,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Eddy_Probe.html b/zh/Eddy_Probe.html
index d756a6073..f3fe47761 100644
--- a/zh/Eddy_Probe.html
+++ b/zh/Eddy_Probe.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1487,13 +1487,13 @@
       
       
         
-        
  • 
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Example_Configs.html b/zh/Example_Configs.html
index 224add5aa..f34e3d081 100644
--- a/zh/Example_Configs.html
+++ b/zh/Example_Configs.html
@@ -1329,8 +1329,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Exclude_Object.html b/zh/Exclude_Object.html
index 27df27c67..034323cd9 100644
--- a/zh/Exclude_Object.html
+++ b/zh/Exclude_Object.html
@@ -1356,8 +1356,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/FAQ.html b/zh/FAQ.html
index e96d8b470..60821a5fc 100644
--- a/zh/FAQ.html
+++ b/zh/FAQ.html
@@ -1488,8 +1488,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Features.html b/zh/Features.html
index 8d65dd354..7a1ebe7a1 100644
--- a/zh/Features.html
+++ b/zh/Features.html
@@ -1334,8 +1334,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1443,18 +1443,18 @@
 
  • 标准 G 代码支持。支持由常见“切片软件”（SuperSlicer、Cura、PrusaSlicer 等）生成的通用 G 代码命令。
    • 
 
  • 支持多挤出机。包括对共享热端的挤出机（多进一出）和多头（IDEX）的支持。
    • 
 
  • 支持笛卡尔、三角洲、CoreXY、CoreXZ、混合CoreXY、混合CoreXZ、deltesian、旋转三角洲、极坐标和缆绳铰盘式打印机。
    • 
-
  • 自动床面平整支持。Klipper可以被配置为基本的床身倾斜检测或网床调平。如果床铺使用多个Z步进器，那么Klipper也可以通过独立操纵Z步进器来调平。支持大多数Z高度探头，包括BL-Touch探头和伺服激活的探头。
    • 
+
  • Automatic bed leveling support. Klipper can be configured for basic bed tilt detection or full mesh bed leveling. The bed mesh can be customized to the print size (adaptive bed mesh). If the bed uses multiple Z steppers then Klipper can also level by independently manipulating the Z steppers. Most Z height probes are supported, including BL-Touch probes and servo activated probes. Probes may be calibrated for axis twist compensation. If using an "eddy current probe" then one can utilize fast bed mesh scanning,
    • 
 
  • 支持自动delta校准。校准工具可以进行基本的高度校准，以及增强的X和Y尺寸校准。校准可以用Z型高度探头或通过手动探测来完成。
    • 
 
  • 支持打印时“排除对象”。配置后，此模块可以取消多零件打印中的一个对象。
    • 
-
  • 支持常见的温度传感器（例如，常见的热敏电阻、AD595、AD597、AD849x、PT100、PT1000、MAX6675、MAX31855、MAX31856、MAX31865、BME280、HTU21D、DS18B20和LM75）。还可以配置自定义热敏电阻和自定义模拟温度传感器。还可以监测微控制器和 Raspberry Pi 内部的温度传感器。
    • 
+
  • Support for common temperature sensors (eg, common thermistors, AD595, AD597, AD849x, PT100, PT1000, MAX6675, MAX31855, MAX31856, MAX31865, BME280, HTU21D, DS18B20, AHT10, SHT3x, and LM75). Custom thermistors and custom analog temperature sensors can also be configured. One can monitor the internal micro-controller temperature sensor and the internal temperature sensor of a Raspberry Pi.
    • 
 
  • 默认启用基本加热器保护。
    • 
-
  • 支持标准风扇、喷嘴风扇和温控风扇。不需要在打印机闲置时保持风扇运转。可以在带有转速表的风扇上监测风扇速度。
    • 
+
  • Support for standard fans, nozzle fans, and temperature controlled fans. No need to keep fans running when the printer is idle. Fan speed can be monitored on fans that have a tachometer. One can assign a "math formula" to a fan for automatic fan speed updating.
    • 
 
  • 支持TMC2130、TMC2208/TMC2224、TMC2209、TMC2660和TMC5160步进电机驱动器的运行时配置。还支持通过AD5206、DAC084S085、MCP4451、MCP4728、MCP4018和PWM引脚对传统步进驱动器进行电流控制。
    • 
 
  • 支持直接连接到打印机的普通LCD显示器。还提供了一个默认的菜单。显示器和菜单的内容可以通过配置文件完全定制。
    • 
 
  • 恒定加速和“look-ahead”（前瞻）支持。所有打印机移动将从静止逐渐加速到巡航速度，然后减速回到静止。对传入的 G 代码移动命令流进行排队和分析 - 将优化类似方向上的移动之间的加速度，以减少打印停顿并改善整体打印时间。
    • 
 
  • Klipper 实现了一种“步进相位限位”算法，可以提高典型限位开关的精度。如果调整得当，它可以提高打印件首层和打印床的附着力。
    • 
 
  • 支持打印丝存在传感器、打印丝运动传感器和打印丝宽度传感器。
    • 
-
  • 支持使用 adxl345、mpu9250 和 mpu 6050 加速度计测量和记录加速度。
    • 
+
  • Support for measuring and recording acceleration using adxl345, mpu9250, mpu6050, lis2dw12, lis3dh, and icm20948 accelerometers.
    • 
 
  • 支持限制短距离“之”字形移动的最高速度，以减少打印机的振动和噪音。更多信息见运动学文档。
    • 
 
  • 许多常见的打印机都有样本配置文件。查看配置文件夹中的列表。
    • 
 
@@ -1526,11 +1526,6 @@
 1622K
 
 
-RP2040
-2400K
-1636K
-
-
 SAM4E8E
 2500K
 1674K
@@ -1556,6 +1551,11 @@
 2634K
 
 
+RP2040
+4000K
+2571K
+
+
 RP2350
 4167K
 2663K
@@ -1566,9 +1566,9 @@
 4737K
 
 
-STM32H743
-9091K
-6061K
+STM32H723
+7429K
+8619K
 
 
 
diff --git a/zh/G-Codes.html b/zh/G-Codes.html
index 91e4d36a8..98ef52198 100644
--- a/zh/G-Codes.html
+++ b/zh/G-Codes.html
@@ -1620,6 +1620,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -1694,33 +1756,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1789,26 +1824,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -1850,6 +1865,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -2281,6 +2316,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -2429,54 +2512,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -3006,8 +3041,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -3881,6 +3916,68 @@
       
     
   
+
+        
+          
  • 
+  
+    [led]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    [load_cell]
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_DIAGNOSTIC
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_CALIBRATE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_TARE
+  
+  
+
    • 
+        
+          
  • 
+  
+    LOAD_CELL_READ load_cell="name"
+  
+  
 
    • 
         
           
  • 
@@ -3955,33 +4052,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [led]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4050,26 +4120,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [pid_calibrate]
-  
-  
-    
-  
 
    • 
         
           
  • 
@@ -4111,6 +4161,26 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [pid_calibrate]
+  
+  
+    
+  
 
    • 
         
           
  • 
@@ -4542,6 +4612,54 @@
       
     
   
+
    • 
+        
+          
  • 
+  
+    [temperature_probe]
+  
+  
+    
+  
+
    • 
+        
+          
  • 
+  
+    TEMPERATURE_PROBE_ENABLE
+  
+  
 
    • 
         
           
  • 
@@ -4690,54 +4808,6 @@
       
     
   
-
    • 
-        
-          
  • 
-  
-    [temperature_probe]
-  
-  
-    
-  
-
    • 
-        
-          
  • 
-  
-    TEMPERATURE_PROBE_ENABLE
-  
-  
 
    • 
         
       
@@ -4831,11 +4901,10 @@
 
    The following commands are available when the axis_twist_compensation config
 section is enabled.
    
 
    AXIS_TWIST_COMPENSATION_CALIBRATE
    
-
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [AUTO=<True|False>] [SAMPLE_COUNT=<value>]
    
+
    AXIS_TWIST_COMPENSATION_CALIBRATE [AXIS=<X|Y>] [SAMPLE_COUNT=<value>]
    
 
    Calibrates axis twist compensation by specifying the target axis or enabling automatic calibration.
    
 
      
 
    • AXIS: Define the axis (X or Y) for which the twist compensation will be calibrated. If not specified, the axis defaults to 'X'.
      • 
-
    • AUTO: Enables automatic calibration mode. When AUTO=True, the calibration will run for both the X and Y axes. In this mode, AXIS cannot be specified. If both AXIS and AUTO are provided, an error will be raised.
      • 
 
    
 
    [bed_mesh]
    
 
    启用[床网格配置部分]（config_Reference.md#bed_mesh）时，以下命令可用（另请参阅[床网格指南]（bed_mesh.md））。
    
@@ -4965,7 +5034,10 @@ section is enabled.
    
 
    FORCE_MOVE
    
 
    FORCE_MOVE STEPPER=<config_name> DISTANCE=<value> VELOCITY=<value> [ACCEL=<value>] 。该命令将以给定的恒定速度（mm/s）强制移动给定的步进器，移动距离（mm）。如果指定了ACCEL并且大于零，那么将使用给定的加速度（单位：mm/s^2）；否则不进行加速。不执行边界检查；不进行运动学更新；一个轴上的其他平行步进器将不会被移动。请谨慎使用，因为不正确的命令可能会导致损坏使用该命令几乎肯定会使低级运动学处于不正确的状态；随后发出G28命令以重置运动学。该命令用于低级别的诊断和调试。
    
 
    SET_KINEMATIC_POSITION
    
-
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [CLEAR=<[X][Y][Z]>]: 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.
    
+
    SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>] [SET_HOMED=<[X][Y][Z]>] [CLEAR_HOMED=<[X][Y][Z]>]: Force the low-level kinematic code to believe the toolhead is at the given cartesian position and set/clear homed status. This is a diagnostic and debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis transformations. Setting an incorrect or invalid position may lead to internal software errors.
    
+
    The X, Y, and Z parameters are used to alter the low-level kinematic position tracking. If any of these parameters are not set then the position is not changed - for example SET_KINEMATIC_POSITION Z=10 would set all axes as homed, set the internal Z position to 10, and leave the X and Y positions unchanged. Changing the internal position tracking is not dependent on the internal homing state - one may alter the position for both homed and not homed axes, and similarly one may set or clear the homing state of an axis without altering its internal position.
    
+
    The SET_HOMED parameter defaults to XYZ which instructs the kinematics to consider all axes as homed. A bare SET_KINEMATIC_POSITION command will result in all axes being considered homed (and not change its current position). If it is not desired to change the state of homed axes then assign SET_HOMED to an empty string - for example: SET_KINEMATIC_POSITION SET_HOMED= X=10. It is also possible to request an individual axis be considered homed (eg, SET_HOMED=X), but note that non-cartesian style kinematics (such as delta kinematics) may not support setting an individual axis as homed.
    
+
    The CLEAR_HOMED parameter instructs the kinematics to consider the given axes as not homed. For example, CLEAR_HOMED=XYZ would request all axes to be considered not homed (and thus require homing prior to movement on those axes). The default is SET_HOMED=XYZ even if CLEAR_HOMED is present, so the command SET_KINEMATIC_POSITION CLEAR_HOMED=Z will set X and Y as homed and clear the homing state for Z. Use SET_KINEMATIC_POSITION SET_HOMED= CLEAR_HOMED=Z if the goal is to clear only the Z homing state. If an axis is specified in neither SET_HOMED nor CLEAR_HOMED then its homing state is not changed and if it is specified in both then CLEAR_HOMED has precedence. It is possible to request clearing of an individual axis, but on non-cartesian style kinematics (such as delta kinematics) doing so may result in clearing the homing state of additional axes. Note the CLEAR parameter is currently an alias for the CLEAR_HOMED parameter, but this alias will be removed in the future.
    
 
    [gcode]
    
 
    The gcode module is automatically loaded.
    
 
    RESTART
    
@@ -5028,6 +5100,28 @@ section is enabled.
    
 
    The following command is enabled if an input_shaper config section has been enabled (also see the resonance compensation guide).
    
 
    SET_INPUT_SHAPER
    
 
    SET_INPUT_SHAPER [SHAPER_FREQ_X=<shaper_freq_x>] [SHAPER_FREQ_Y=<shaper_freq_y>] [DAMPING_RATIO_X=<damping_ratio_x>] [DAMPING_RATIO_Y=<damping_ratio_y>] [SHAPER_TYPE=<shaper>] [SHAPER_TYPE_X=<shaper_type_x>] [SHAPER_TYPE_Y=<shaper_type_y>]：修改输入整形参数。注意 SHAPER_TYPE 参数会同时覆写 X 和 Y 轴的整形器类型，即使它们在 [input_shaper] 配置分段中有不同的整形器类型。SHAPER_TYPE 不能和 SHAPER_TYPE_X 和 SHAPER_TYPE_Y 参数同时使用。这些参数的细节请见配置参考。
    
+
    [led]
    
+
    The following command is available when any of the led config sections are enabled.
    
+
    SET_LED
    
+
    SET_LED LED=<config_name> RED=<value> GREEN=<value> BLUE=<value> WHITE=<value> [INDEX=<index>] [TRANSMIT=0] [SYNC=1]: This sets the LED output. Each color <value> must be between 0.0 and 1.0. The WHITE option is only valid on RGBW LEDs. If the LED supports multiple chips in a daisy-chain then one may specify INDEX to alter the color of just the given chip (1 for the first chip, 2 for the second, etc.). If INDEX is not provided then all LEDs in the daisy-chain will be set to the provided color. If TRANSMIT=0 is specified then the color change will only be made on the next SET_LED command that does not specify TRANSMIT=0; this may be useful in combination with the INDEX parameter to batch multiple updates in a daisy-chain. By default, the SET_LED command will sync it's changes with other ongoing gcode commands. This can lead to undesirable behavior if LEDs are being set while the printer is not printing as it will reset the idle timeout. If careful timing is not needed, the optional SYNC=0 parameter can be specified to apply the changes without resetting the idle timeout.
    
+
    SET_LED_TEMPLATE
    
+
    SET_LED_TEMPLATE LED=<led_name> TEMPLATE=<template_name> [<param_x>=<literal>] [INDEX=<index>]: Assign a display_template to a given LED. For example, if one defined a [display_template my_led_template] config section then one could assign TEMPLATE=my_led_template here. The display_template should produce a comma separated string containing four floating point numbers corresponding to red, green, blue, and white color settings. The template will be continuously evaluated and the LED will be automatically set to the resulting colors. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If INDEX is not specified then all chips in the LED's daisy-chain will be set to the template, otherwise only the chip with the given index will be updated. If TEMPLATE is an empty string then this command will clear any previous template assigned to the LED (one can then use SET_LED commands to manage the LED's color settings).
    
+
    [load_cell]
    
+
    The following commands are enabled if a load_cell config section has been enabled.
    
+
    LOAD_CELL_DIAGNOSTIC
    
+
    LOAD_CELL_DIAGNOSTIC [LOAD_CELL=<config_name>]: This command collects 10 seconds of load cell data and reports statistics that can help you verify proper operation of the load cell. This command can be run on both calibrated and uncalibrated load cells.
    
+
    LOAD_CELL_CALIBRATE
    
+
    LOAD_CELL_CALIBRATE [LOAD_CELL=<config_name>]: Start the guided calibration utility. Calibration is a 3 step process:
    
+
      
+
    1. First you remove all load from the load cell and run the TARE command
      2. 
+
    2. Next you apply a known load to the load cell and run the CALIBRATE GRAMS=nnn command
      3. 
+
    3. Finally use the ACCEPT command to save the results
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    LOAD_CELL_TARE
    
+
    LOAD_CELL_TARE [LOAD_CELL=<config_name>]: This works just like the tare button on digital scale. It sets the current raw reading of the load cell to be the zero point reference value. The response is the percentage of the sensors range that was read and the raw value in counts.
    
+
    LOAD_CELL_READ load_cell="name"
    
+
    LOAD_CELL_READ [LOAD_CELL=<config_name>]: This command takes a reading from the load cell. The response is the percentage of the sensors range that was read and the raw value in counts. If the load cell is calibrated a force in grams is also reported.
    
 
    [manual_probe]
    
 
    The manual_probe module is automatically loaded.
    
 
    MANUAL_PROBE
    
@@ -5049,12 +5143,6 @@ section is enabled.
    
 
    The following command is available when a mcp4018 config section is enabled.
    
 
    SET_DIGIPOT
    
 
    SET_DIGIPOT DIGIPOT=config_name WIPER=<value>: This command will change the current value of the digipot. This value should typically be between 0.0 and 1.0, unless a 'scale' is defined in the config. When 'scale' is defined, then this value should be between 0.0 and 'scale'.
    
-
    [led]
    
-
    The following command is available when any of the led config sections are enabled.
    
-
    SET_LED
    
-
    SET_LED LED=<config_name> RED=<value> GREEN=<value> BLUE=<value> WHITE=<value> [INDEX=<index>] [TRANSMIT=0] [SYNC=1]: This sets the LED output. Each color <value> must be between 0.0 and 1.0. The WHITE option is only valid on RGBW LEDs. If the LED supports multiple chips in a daisy-chain then one may specify INDEX to alter the color of just the given chip (1 for the first chip, 2 for the second, etc.). If INDEX is not provided then all LEDs in the daisy-chain will be set to the provided color. If TRANSMIT=0 is specified then the color change will only be made on the next SET_LED command that does not specify TRANSMIT=0; this may be useful in combination with the INDEX parameter to batch multiple updates in a daisy-chain. By default, the SET_LED command will sync it's changes with other ongoing gcode commands. This can lead to undesirable behavior if LEDs are being set while the printer is not printing as it will reset the idle timeout. If careful timing is not needed, the optional SYNC=0 parameter can be specified to apply the changes without resetting the idle timeout.
    
-
    SET_LED_TEMPLATE
    
-
    SET_LED_TEMPLATE LED=<led_name> TEMPLATE=<template_name> [<param_x>=<literal>] [INDEX=<index>]: Assign a display_template to a given LED. For example, if one defined a [display_template my_led_template] config section then one could assign TEMPLATE=my_led_template here. The display_template should produce a comma separated string containing four floating point numbers corresponding to red, green, blue, and white color settings. The template will be continuously evaluated and the LED will be automatically set to the resulting colors. One may set display_template parameters to use during template evaluation (parameters will be parsed as Python literals). If INDEX is not specified then all chips in the LED's daisy-chain will be set to the template, otherwise only the chip with the given index will be updated. If TEMPLATE is an empty string then this command will clear any previous template assigned to the LED (one can then use SET_LED commands to manage the LED's color settings).
    
 
    [output_pin]
    
 
    使用output_pin 配置分段时，以下命令可用：
    
 
    SET_PIN
    
@@ -5077,10 +5165,6 @@ section is enabled.
    
 
    PALETTE_CUT:该命令指引Palette 2切割耗材并且装载分段的耗材。
    
 
    PALETTE_SMART_LOAD
    
 
    PALETTE_SMART_LOAD：该命令在Palette 2上启动智能加载序列。通过在设备上为打印机校准的距离挤压，自动加载耗材，并在加载完成后指示Palette 2。该命令与耗材加载完成后直接在Palette 2屏幕上按Smart Load相同。
    
-
    [pid_calibrate]
    
-
    The pid_calibrate module is automatically loaded if a heater is defined in the config file.
    
-
    PID_CALIBRATE
    
-
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]：执行一个PID校准测试。指定的加热器将被启用，直到达到指定的目标温度，然后加热器将被关闭和开启几个周期。如果WRITE_FILE参数被启用，那么将创建文件/tmp/heattest.txt，其中包含测试期间所有温度样本的日志。
    
 
    [pause_resume]
    
 
    当pause_resume 配置分段被启用时，以下命令可用：
    
 
    PAUSE
    
@@ -5091,6 +5175,10 @@ section is enabled.
    
 
    CLEAR_PAUSE:清除当前的暂停状态而不恢复打印。如果一个人决定在暂停后取消打印，这很有用。建议将其添加到你的启动代码中，以确保每次打印时的暂停状态是新的。
    
 
    CANCEL_PRINT
    
 
    CANCEL_PRINT：取消当前的打印。
    
+
    [pid_calibrate]
    
+
    The pid_calibrate module is automatically loaded if a heater is defined in the config file.
    
+
    PID_CALIBRATE
    
+
    PID_CALIBRATE HEATER=<config_name> TARGET=<temperature> [WRITE_FILE=1]：执行一个PID校准测试。指定的加热器将被启用，直到达到指定的目标温度，然后加热器将被关闭和开启几个周期。如果WRITE_FILE参数被启用，那么将创建文件/tmp/heattest.txt，其中包含测试期间所有温度样本的日志。
    
 
 
    The print_stats module is automatically loaded.
    
 
    SET_PRINT_STATS_INFO
    
@@ -5158,7 +5246,7 @@ section is enabled.
    
 
    [save_variables]
    
 
    The following command is enabled if a save_variables config section has been enabled.
    
 
    SAVE_VARIABLE
    
-
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>：将变量保存到磁盘，以便在重新启动时使用。所有存储的变量都会在启动时加载到 printer.save_variables.variables 目录中，并可以在 gcode 宏中使用。所提供的 VALUE 会被解析为一个 Python 字面。
    
+
    SAVE_VARIABLE VARIABLE=<name> VALUE=<value>: Saves the variable to disk so that it can be used across restarts. The VARIABLE must be lowercase. All stored variables are loaded into the printer.save_variables.variables dict at startup and can be used in gcode macros. The provided VALUE is parsed as a Python literal.
    
 
    [screws_tilt_adjust]
    
 
    The following commands are available when the screws_tilt_adjust config section is enabled (also see the manual level guide).
    
 
    SCREWS_TILT_CALCULATE
    
@@ -5199,6 +5287,18 @@ section is enabled.
    
 
    使用temperature_fan配置分段时，以下命令可用：
    
 
    SET_TEMPERATURE_FAN_TARGET
    
 
    SET_TEMPERATURE_FAN_TARGET temperature_fan=<temperature_fan_名称> [target=<目标温度>] [min_speed=<最小速度>] [max_speed=<最大速度>]：设置一个温度控制风扇的目标温度。如果没有提供目标温度，它将被设为配置文件中定义的温度。如果没有提供速度，则不会进行任何更改。
    
+
    [temperature_probe]
    
+
    The following commands are available when a temperature_probe config section is enabled.
    
+
    TEMPERATURE_PROBE_CALIBRATE
    
+
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
+
    TEMPERATURE_PROBE_NEXT
    
+
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
+
    TEMPERATURE_PROBE_COMPLETE:
    
+
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
+
    关于
    
+
    ABORT：中止校准过程，丢弃当前结果。此命令仅在漂移校准期间可用。
    
+
    TEMPERATURE_PROBE_ENABLE
    
+
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
    [tmcXXXX]
    
 
    The following commands are available when any of the tmcXXXX config sections are enabled.
    
 
    DUMP_TMC
    
@@ -5246,18 +5346,6 @@ section is enabled.
    
 
    The following commands are available when the z_tilt config section is enabled.
    
 
    Z_TILT_ADJUST
    
 
    Z_TILT_ADJUST [RETRIES=<value>] [RETRY_TOLERANCE=<value>] [HORIZONTAL_MOVE_Z=<value>] [<probe_parameter>=<value>]: 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 RETRIES, RETRY_TOLERANCE, and HORIZONTAL_MOVE_Z values override those options specified in the config file.
    
-
    [temperature_probe]
    
-
    The following commands are available when a temperature_probe config section is enabled.
    
-
    TEMPERATURE_PROBE_CALIBRATE
    
-
    TEMPERATURE_PROBE_CALIBRATE [PROBE=<probe name>] [TARGET=<value>] [STEP=<value>]: Initiates probe drift calibration for eddy current based probes. The TARGET is a target temperature for the last sample. When the temperature recorded during a sample exceeds the TARGET calibration will complete. The STEP parameter sets temperature delta (in C) between samples. After a sample has been taken, this delta is used to schedule a call to TEMPERATURE_PROBE_NEXT. The default STEP is 2.
    
-
    TEMPERATURE_PROBE_NEXT
    
-
    TEMPERATURE_PROBE_NEXT: After calibration has started this command is run to take the next sample. It is automatically scheduled to run when the delta specified by STEP has been reached, however its also possible to manually run this command to force a new sample. This command is only available during calibration.
    
-
    TEMPERATURE_PROBE_COMPLETE:
    
-
    TEMPERATURE_PROBE_COMPLETE: Can be used to end calibration and save the current result before the TARGET temperature is reached. This command is only available during calibration.
    
-
    关于
    
-
    ABORT：中止校准过程，丢弃当前结果。此命令仅在漂移校准期间可用。
    
-
    TEMPERATURE_PROBE_ENABLE
    
-
    TEMPERATURE_PROBE_ENABLE ENABLE=[0|1]: Sets temperature drift compensation on or off. If ENABLE is set to 0, drift compensation will be disabled, if set to 1 it is enabled.
    
 
               
             
diff --git a/zh/Hall_Filament_Width_Sensor.html b/zh/Hall_Filament_Width_Sensor.html
index 6c0efecac..c60d1b317 100644
--- a/zh/Hall_Filament_Width_Sensor.html
+++ b/zh/Hall_Filament_Width_Sensor.html
@@ -1357,8 +1357,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Installation.html b/zh/Installation.html
index c1c838eba..34e4cbeea 100644
--- a/zh/Installation.html
+++ b/zh/Installation.html
@@ -1366,8 +1366,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
@@ -1481,8 +1481,8 @@
 
 
 
    安装
    
-
    这些说明假设软件将在运行 Klipper 兼容前端的 Linux 主机上运行。建议使用 SBC（小型板计算机），例如 Raspberry Pi 或基于 Debian 的 Linux 设备作为主机（有关其他选项，请参阅 FAQ）。
    
-
    就本说明而言，主机与 Linux 设备相关，而 mcu 与印刷电路板相关。SBC 与术语“小型板计算机”相关，例如 Raspberry Pi。
    
+
    These instructions assume the software will run on a Linux-based host running a Klipper-compatible front end. It is recommended that a SBC(Small Board Computer) such as a Raspberry Pi or Debian-based Linux device be used as the host machine (see the FAQ for other options).
    
+
    For the purposes of these instructions, host relates to the Linux device and mcu relates to the printer board. SBC relates to the term Small Board Computer such as the Raspberry Pi.
    
 
    获取 Klipper 配置文件
    
 
    大多数 Klipper 设置由“打印机配置文件”printer.cfg 决定，该文件将存储在主机上。通常可以通过在 Klipper config 目录 中查找以“printer-”前缀开头且与目标打印机相对应的文件来找到适当的配置文件。Klipper 配置文件包含安装过程中需要的有关打印机的技术信息。
    
 
    如果 Klipper 配置目录中没有合适的打印机配置文件，请尝试搜索打印机制造商的网站，看看他们是否有合适的 Klipper 配置文件。
    
@@ -1493,13 +1493,13 @@
 
    目前最好的选择是通过 Moonraker web API 检索信息的前端，也可以选择使用 Octoprint 来控制 Klipper。
    
 
    用户可自行选择使用哪种工具，但底层的 Klipper 在所有情况下都是相同的。我们鼓励用户研究可用的选项并做出明智的决定。
    
 
    获取 SBC 的操作系统映像
    
-
    有多种方法可以获取用于 SBC 的 Klipper 操作系统映像，大多数方法取决于您希望使用哪种前端。这些 SBC 板的一些制造商还提供自己的以 Klipper 为中心的映像。
    
-
    两个主要的基于 Moonraker 的前端是 Fluidd 和 Mainsail，后者具有预制的安装映像 "MainsailOS"，它有适用于 Raspberry Pi 和一些 OrangePi 变体的选项。
    
+
    There are many ways to obtain an OS image for Klipper for SBC use, most depend on what front end you wish to use. Some manufacturers of these SBC boards also provide their own Klipper-centric images.
    
+
    The two main Moonraker-based front ends are Fluidd and Mainsail, the latter of which has a premade install image "MainsailOS", this has the option for Raspberry Pi and some OrangePi variants.
    
 
    Fluidd 可以通过 KIAUH（Klipper 安装和更新助手）进行安装，如下所述，它是所有 Klipper 的第三方安装程序。
    
 
    OctoPrint 可以通过流行的 OctoPi 镜像或通过 KIAUH 安装，此过程在  中有说明
    
 
    通过 KIAUH 安装
    
-
    通常，您会从 SBC 的基本映像（例如 RPiOS Lite）开始，或者在 x86 Linux 设备的情况下，从 Ubuntu Server 开始。请注意，不建议使用桌面版本，因为某些辅助程序可能会阻止某些 Klipper 功能运行，甚至屏蔽对某些打印板的访问。
    
-
    KIAUH 可用于在运行 Debian 的各种 Linux 系统上安装 Klipper 及其相关程序。更多信息请访问 https://github.com/dw-0/kiauh
    
+
    Normally you would start with a base image for your SBC, RPiOS Lite for example, or in the case of an x86 Linux device, Ubuntu Server. Please note that Desktop variants are not recommended due to certain helper programs that can stop some Klipper functions from working and even mask access to some printer boards.
    
+
    KIAUH can be used to install Klipper and its associated programs on a variety of Linux-based systems that run a form of Debian. More information can be found at https://github.com/dw-0/kiauh
    
 
    构建和刷写微控制器
    
 
    要编译微控制器代码，首先在主机设备上运行以下命令：
    
 
    cd ~/klipper/
@@ -1510,7 +1510,7 @@ make menuconfig
 
    make
 
    
 
-
    如果打印机配置文件顶部的注释描述了"flashing"最终固件镜像到打印机控制板的特殊步骤，那么请遵循这些步骤，然后继续进行配置OctoPrint。
    
+
    If the comments at the top of the printer configuration file describe custom steps for "flashing" the final image to the printer control board, then follow those steps and then proceed to configuring OctoPrint.
    
 
    否则，通常采用以下步骤来"flash"打印机控制板。首先，需要确定连接到微控制器的串行端口。然后，运行以下程序：
    
 
    ls /dev/serial/by-id/*
 
    
@@ -1520,8 +1520,8 @@ make menuconfig
 
    
 
 
    通常，每台打印机都有自己独特的串行端口名称。此唯一名称将在刷新微控制器时使用。上面的输出中可能有多行 - 如果是这样，请选择与微控制器相对应的行。如果列出了许多项目并且选择不明确，请拔下电路板并再次运行命令，缺少的项目将是您的打印板（有关更多信息，请参阅 FAQ）。
    
-
    对于带有 STM32 或克隆芯片、LPC 芯片和其他芯片的常见微控制器，通常需要通过 SD 卡进行初始 Klipper 闪存。
    
-
    使用此方法进行刷写时，务必确保打印板未通过 USB 连接到主机，因为某些电路板能够将电源反馈给电路板并阻止刷写开始。
    
+
    For common micro-controllers with STM32 or clone chips, LPC chips and others, it is usual that these need an initial Klipper flash via SD card.
    
+
    When flashing with this method, it is important to make sure that the print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring.
    
 
    对于使用 Atmega 芯片的常见微控制器，例如 2560，代码可以使用类似以下内容进行烧录：
    
 
    sudo service klipper stop
 make flash FLASH_DEVICE=/dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
@@ -1538,9 +1538,9 @@ sudo service klipper start
 
    It is important to note that RP2040 chips may need to be put into Boot mode before this operation.
    
 
    配置 Klipper
    
 
    The next step is to copy the printer configuration file to the host.
    
-
    Arguably the easiest way to set the Klipper configuration file is using the built in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
+
    Arguably the easiest way to set the Klipper configuration file is using the built-in editors in Mainsail or Fluidd. These will allow the user to open the configuration examples and save them to be printer.cfg.
    
 
    Another option is to use a desktop editor that supports editing files over the "scp" and/or "sftp" protocols. There are freely available tools that support this (eg, Notepad++, WinSCP, and Cyberduck). Load the printer config file in the editor and then save it as a file named "printer.cfg" in the home directory of the pi user (ie, /home/pi/printer.cfg).
    
-
    Alternatively, one can also copy and edit the file directly on the host via ssh. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
+
    Alternatively, one can also copy and edit the file directly on the host via SSH. That may look something like the following (be sure to update the command to use the appropriate printer config filename):
    
 
    cp ~/klipper/config/example-cartesian.cfg ~/printer.cfg
 nano ~/printer.cfg
 
    
@@ -1558,9 +1558,9 @@ nano ~/printer.cfg
 serial: /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
 
    
 
-
    After creating and editing the file it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
+
    After creating and editing the file, it will be necessary to issue a "restart" command in the command console to load the config. A "status" command will report that the printer is ready if the Klipper config file is successfully read and the micro-controller is successfully found and configured.
    
 
    在定制打印机配置文件时，Klipper 报告配置错误是很正常的情况。如果发生错误，请对打印机配置文件进行必要的修正，并发出"restart"，直到"status"报告打印机已准备就绪。
    
-
    Klipper reports error messages via the command console and via pop up in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located in ~/printer_data/logs this is named klippy.log
    
+
    Klipper reports error messages via the command console and pop-ups in Fluidd and Mainsail. The "status" command can be used to re-report error messages. A log is available and usually located at ~/printer_data/logs/klippy.log.
    
 
    在Klipper报告打印机已就绪后，继续进入配置检查文件，对配置文件中的定义进行一些基本检查。其他信息见主文档参考。
    
 
               
diff --git a/zh/Kinematics.html b/zh/Kinematics.html
index 26f150a2d..e78f72b74 100644
--- a/zh/Kinematics.html
+++ b/zh/Kinematics.html
@@ -1411,8 +1411,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Load_Cell.html b/zh/Load_Cell.html
new file mode 100644
index 000000000..43252be79
--- /dev/null
+++ b/zh/Load_Cell.html
@@ -0,0 +1,1635 @@
+
+
+
+  
+    
+      
+      
+      
+      
+      
+      
+      
+    
+    
+      
+        Load Cells - Klipper 文档
+      
+    
+    
+      
+      
+        
+        
+        
+      
+    
+    
+    
+      
+        
+        
+        
+        
+      
+    
+    
+      
+    
+    
+    
+      
+  
+
+
+  
+  
+
+
+  
+  
+
+
+    
+    
+  
+  
+  
+    
+    
+      
+    
+    
+    
+    
+    
+  
+    
+    
+      
+    
+    
+    
+    
+    
    
+      
+        
+        
+          跳转至
+        
+      
+    
    
+    
    
+      
+    
    
+    
+    
+      
+
+
    
+  
+  
+
    
+    
+    
    
+      
+      
+        
+          
+        
+      
+      
    
+        
    
+          
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+
+                  
    
+                
    
+              
    
+            
+            
+              
+              
    
+                
    
+                  
    
+                    
+
+
+                  
    
+                
    
+              
    
+            
+          
+          
    
+            
    
+              
+                
+
+  
+
+
+
+
    Load Cells
    
+
    This document describes Klipper's support for load cells. Basic load cell functionality can be used to read force data and to weigh things like filament. A calibrated force sensor is an important part of a load cell based probe.
    
+
+
+
    Using LOAD_CELL_DIAGNOSTIC
    
+
    When you first connect a load cell its good practice to check for issues by running LOAD_CELL_DIAGNOSTIC. This tool collects 10 seconds of data from the load cell and resport statistics:
    
+
    $ LOAD_CELL_DIAGNOSTIC
+// Collecting load cell data for 10 seconds...
+// Samples Collected: 3211
+// Measured samples per second: 332.0
+// Good samples: 3211, Saturated samples: 0, Unique values: 900
+// Sample range: [4.01% to 4.02%]
+// Sample range / sensor capacity: 0.00524%
+
    
+
+
    Things you can check with this data:
    
+
      
+
    • The configured sample rate of the sensor should be close to the 'Measured samples per second' value. If it is not you may have a configuration or wiring issue.
      • 
+
    • 'Saturated samples' should be 0. If you have saturated samples it means the load sell is seeing more force than it can measure.
      • 
+
    • 'Unique values' should be a large percentage of the 'Samples Collected' value. If 'Unique values' is 1 it is very likely a wiring issue.
      • 
+
    • Tap or push on the sensor while LOAD_CELL_DIAGNOSTIC runs. If things are working correctly ths should increase the 'Sample range'.
      • 
+
    
+
    Calibrating a Load Cell
    
+
    Load cells are calibrated using the LOAD_CELL_CALIBRATE command. This is an interactive calibration utility that walks you though a 3 step process:
    
+
      
+
    1. First use the TARE command to establish the zero force value. This is the reference_tare_counts config value.
      2. 
+
    2. Next you apply a known load or force to the load cell and run the CALIBRATE GRAMS=nnn command. From this the counts_per_gram value is calculated. See the next section for some suggestions on how to do this.
      3. 
+
    3. Finally, use the ACCEPT command to save the results.
      4. 
+
    
+
    You can cancel the calibration process at any time with ABORT.
    
+
    Applying a Known Force or Load
    
+
    The CALIBRATE GRAMS=nnn step can be accomplished in a number of ways. If your load cell is under a platform like a bed or filament holder it might be easiest to put a known mass on the platform. E.g. you could use a couple of 1KG filament spools.
    
+
    If your load cell is in the printer's toolhead a different approach is easier. Put a digital scale on the printers bed and gently lower the toolhead onto the scale (or raise the bed into the toolhead if your bed moves). You may be able to do this using the FORCE_MOVE command. But more likely you will have to manually moving the z axis with the motors off until the toolhead presses on the scale.
    
+
    A good calibration force would ideally be a large percentage of the load cell's rated capacity. E.g. if you have a 5Kg load cell you would ideally calibrate it with a 5kg mass. This might work well with under-bed sensors that have to support a lot of weight. For toolhead probes this may not be a load that your printer bed or toolhead can tolerate without damage. Do try to use at least 1Kg of force, most printers should tolerate this without issue.
    
+
    When calibrating make careful note of the values reported:
    
+
    $ CALIBRATE GRAMS=555
+// Calibration value: -2.78% (-59803108), Counts/gram: 73039.78739,
+Total capacity: +/- 29.14Kg
+
    
+
+
    The Total capacity should be close to the theoretical rating of the load cell based on the sensor's capacity. If it is much larger you could have used a higher gain setting in the sensor or a more sensitive load cell. This isn't as critical for 32bit and 24bit sensors but is much more critical for low bit width sensors.
    
+
    Reading Force Data
    
+
    Force data can be read with a GCode command:
    
+
    LOAD_CELL_READ
+// 10.6g (1.94%)
+
    
+
+
    Data is also continuously read and can be consumed from the load_cell printer object in a macro:
    
+
    {% set grams = printer.load_cell.force_g %}
+
    
+
+
    This provides an average force over the last 1 second, similar to how temperature sensors work.
    
+
    Taring a Load Cell
    
+
    Taring, sometimes called zeroing, sets the current weight reported by the load_cell to 0. This is useful for measuring relative to a known weight. e.g. when measuring a filament spool, using LOAD_CELL_TARE sets the weight to 0. Then as filament is printed the load_cell will report the weight of the filament used.
    
+
    LOAD_CELL_TARE
+// Load cell tare value: 5.32% (445903)
+
    
+
+
    The current tare value is reported in the printers status and can be read in a macro:
    
+
    {% set tare_counts = printer.load_cell.tare_counts %}
+
    
+
+              
+            
    
+          
    
+        
    
+        
+          
+            
+            回到页面顶部
+          
+        
+      
    
+      
+        
+      
+    
    
+    
    
+      
    
+    
    
+    
+    
+    
+      
+      
+    
+  
+
\ No newline at end of file
diff --git a/zh/MCU_Commands.html b/zh/MCU_Commands.html
index 32714389a..a149f5653 100644
--- a/zh/MCU_Commands.html
+++ b/zh/MCU_Commands.html
@@ -1383,8 +1383,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Manual_Level.html b/zh/Manual_Level.html
index 04ca94987..7c94abd03 100644
--- a/zh/Manual_Level.html
+++ b/zh/Manual_Level.html
@@ -1358,8 +1358,8 @@
   
   
     
  • 
-      
-        None
+      
+        Load Cells
       
     
    • 
   
diff --git a/zh/Measuring_Resonances.html b/zh/Measuring_Resonances.html
index 58aa808da..ae4ca6432 100644
--- a/zh/Measuring_Resonances.html
+++ b/zh/Measuring_Resonances.html
@@ -838,11 +838,11 @@