# Move Exceeds Maxiumum Extrusion

**URL:** <https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964>\
**Category:** General Discussion\
**Created:** [April 22, 2024, 11:53pm UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964 "2024-04-22T23:53:48Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![CPTW](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@CPTW](https://klipper.discourse.group/u/CPTW)\
**Post date:** [April 22, 2024, 11:53pm UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/1 "2024-04-22T23:53:48Z")

</div>

### Basic Information:

Printer Model: Ender 5 S1  
 MCU / Printerboard: ?  
 Host / SBC ?  
 klippy.log ?

_Fill out above information and_ **_in all cases attach your_ `klippy.log` _file_** (use zip to compress it, if too big). _Pasting your_ `printer.cfg` _is **not** needed_  
_ **Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there** _

### Describe your issue:

…

Hi, Im new here and don’t really know much when it comes to the software side of 3d printing. As the title suggests, after doing an update I’ve been getting this error halfway though the first layer. Idk where to find the klippy.log file but the exact error is (“code”:“key112”,“msg”:  
“Move exceeds maximum extrusion (2.025mm^2 vs  
0.640mm^2) See the 'max\_extrude\_cross\_section  
config option for details”“values”: [2.025, 0.640]). I’ve found some archived posts here and even tried adding max\_extrude\_cross\_section = 2.0 to the printer config file as was suggested but the error persisted. Any help would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [April 23, 2024, 6:31am UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/2 "2024-04-23T06:31:05Z")

</div>

Hello @CPTW !

Please attach the klippy.log to your **next post**.

---

<div class="post-metadata">

**Author:** ![CPTW](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@CPTW](https://klipper.discourse.group/u/CPTW)\
**Post date:** [April 23, 2024, 7:55am UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/3 "2024-04-23T07:55:09Z")

</div>

Where is this file located?

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [April 23, 2024, 10:51am UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/4 "2024-04-23T10:51:50Z")

</div>

Depends on the frontend you use:

Mainsail or Fluidd or OctoPrint?

---

<div class="post-metadata">

**Author:** ![CPTW](https://avatars.discourse-cdn.com/v4/letter/c/bbce88/32.png) [@CPTW](https://klipper.discourse.group/u/CPTW)\
**Post date:** [April 23, 2024, 9:27pm UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/5 "2024-04-23T21:27:40Z")

</div>

Thank you for the help. I was able to find it in the fluidd web UI. Here is the klippy.log file.  
[klippy.log](https://klipper.discourse.group/uploads/short-url/wFYY3m57x3lVcPYTyJtrFFabxxF.log) (49.7 KB)

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [April 24, 2024, 5:18am UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/6 "2024-04-24T05:18:11Z")

</div>

Sadly it appears you are running a Sonic Pad. The klippy.logs from that machine do not help in any way. Sorry.

> [@Creality Sonic Pad and Alternatives](https://klipper.discourse.group/t/creality-sonic-pad-and-alternatives/6324/1):
>
> Creality Sonic Padexclamation Update Since July 11, 2023, Creality seems to have [released a firmware](https://www.creality.com/pages/download-creality-sonic-pad?spm=..page_1934481.products_display_1.1&spm_prev=..product_afecb672-1369-4c48-ba2d-f0cd762126a6.header_1.1) with a newer Klipper version. Again, they have not released the sources for this and the other components as required by the GPL license. Again, they are violating the OSS license and making money off the work of others. Background The Creality Sonic Pad is intended to be a “one-stop” solution for Klipper. A SBC running Klipper along with Moonraker, Fluidd, Mainsail and KlipperScreen A …

---

<div class="post-metadata">

**Author:** ![cbramsey](https://avatars.discourse-cdn.com/v4/letter/c/c6cbf5/32.png) [@cbramsey](https://klipper.discourse.group/u/cbramsey)\
**Post date:** [May 13, 2024, 4:50pm UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/7 "2024-05-13T16:50:37Z")

</div>

I am having this same issue, are you saying that we can’t remedy the issue if using a sonic pad?

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [May 13, 2024, 5:39pm UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/8 "2024-05-13T17:39:14Z")

</div>

> [@cbramsey](#):
>
> are you saying that we can’t remedy the issue if using a sonic pad?

Yepp.

For several reasons as mentioned in the last link.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [July 12, 2024, 5:40pm UTC](https://klipper.discourse.group/t/move-exceeds-maxiumum-extrusion/15964/9 "2024-07-12T17:40:04Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
