Suddenly my extruder retract a large amount

General Discussion
1

Basic Information:

Printer Model: voron v2.4
MCU / Printerboard: octopus v1.1 with ebb36 can
Host / SBC rpi4
klippy.log
klippy(14).log (1.8 MB)

I am tuning Ellis’ EM at the moment and suddenly after the second layer, when it should be doing two layers of infil, it retracts what looks like 30 or more mm very rapidly and then prints nothing because it does not deretract the same amount prior to printing the third layer.

I remember it did this also before the complete rebuild and at that time I had just done a klipper update and I thought it was because of that. But this time I did not update anything.

Yesterday I tuned PA and nothing was wrong. All I set was PA at 0.0002 and I set my accels in the cfg equal to the ones in the slicer (so the estimates become more accurate I thought).
Other then that I just followed Ellis’ instructions for prusa slicer and try to print this EM cube.
I tried printing the PA pattern again with the old gcode from yesterday and that does not do this retract.
What have I done to cause this?

2

Sounds strange.
Maybe there’s a mix-up of not resetting the extruder and G90 / M82?

3

I do not recall changing that, where do I find this section?
also, if it is klipper, why can I reprint the file from Ellis’ PA tuning pattern again without problems?

just resliced it with totally different slicer settings (prusa) and I set back some minor things I had changed before but it does it again.

I will try an old gcode from last week or something.
EDIT. The old file from 2 weeks ago still works so it is with the slicer at this moment.
I wanted to try SS for a while anyway and see what is the hype all about. So I will remove Prusa and all its mess and try that with the profiles from Ellis.

4

I don’t think so. Rather a slicer setting.

Supports the theory that it is slicer-related. Likely the starting G-code.

Either global or filament-dependent start G-code, or start G-code macro.

5

I agree. I have had trouble with prusa with updates too. My linux ubuntu did not update correctly from a prusa update notification and neither from the built in app center for some reason. I now have a few non working prusa instances which interfere I think. Its time to clean up and maybe try Prusa latest version. I heard SuperSlicer is also not developing anymore and runs behind.
Thanks as always.

6

One question. Which slicer do you use?

7

it was prusa, an old version because linux ubuntu app center did not work very well and I ended up with not properly installed versions.
I now manually cleaned everything, including profiles, and manually installed the latest prusa.
All my troubles have gone like snow for the sun!

Thank you @Sineos for confirming it was not klipper.
You all are ace at what you do here.

1 Like
8

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