Arachne causes stuttering extruder on curves, rough surface with klipper. #8534
Comments
|
Would you please test with alpha3?
From the changelog:
Release PrusaSlicer 2.5.0-alpha3 · prusa3d/PrusaSlicer (github.com)
<https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.5.0-alpha3>
- When using the Classic perimeter generator, consecutive segments of
gap fill are now merged when they have the same direction and don't differ
in width (or only differ slightly). This reduces size of the G-Code and
makes printer stuttering less likely.
st 20. 7. 2022 v 20:01 odesílatel napter ***@***.***> napsal:
… Description of the bug
When printing with klipper firmware the surface of the print was rough,
exactly how it looks when the gcode is too large and printing stutters.
Similarly, the issue only happened on curves. However, the same file was
printing ok on other printers.
Reducing the STL nodes didn't help. Increasing the gcode resolution didn't
help. Changing speed didn't help. The artifacts would repeat in the same
spots. When watching the printer it would vibrate when printing on the
curves (I believe it was the the extruder stuttering but it was difficult
to tell if it was the extruder or a motion axis). After determining it was
not a resolution issue, finally, I thought perhaps it is Arachne. I printed
the exact same thing, switching perimeter generator to classic and the
issue disappeared.
Arachne print:
[image: image]
<https://user-images.githubusercontent.com/6260841/180049752-9e531f16-46b8-4623-8416-3dfeb7e47d56.png>
Classic print:
[image: image]
<https://user-images.githubusercontent.com/6260841/180050075-4fdf53ae-7704-4bd8-a699-a50fbe6be3ca.png>
Side by side:
[image: image]
<https://user-images.githubusercontent.com/6260841/180050195-7cb8e817-58e1-47e7-a7e2-c2c20872b220.png>
Notice the bumps on the curves. They print consistently on every print
with arachne but not with classic. I've only experienced this issue with
klipper.
Project file & How to reproduce
arachne issue.zip
<https://github.com/prusa3d/PrusaSlicer/files/9152609/arachne.issue.zip>
Checklist of files included above
- Project file
- Screenshot
Version of PrusaSlicer
2.5 alpha 2
Operating system
Windows 10
Printer model
Ender 5 Plus running Klipper
—
Reply to this email directly, view it on GitHub
<#8534>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSIZBDNOPRTUY64ZFWHLVVA5HTANCNFSM54ETF7ZA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
But @napter has this problem with Arachne, not with classic… |
|
@dartrax
@napter So I think that this issue is also resolved in 2.5.0-alpha3. So please try 2.5.0-alpha3 and report back whether your issue is still present or not. |
|
Ok will do
…On Fri, Jul 22, 2022 at 11:58 AM Lukáš Hejl ***@***.***> wrote:
@dartrax <https://github.com/dartrax>
It was just a wrong quote from the changelog (actually, gap fill and
Arachne share some parts of the code, so fixing one will fix a similar
problem for the other).
Instead of that, it should be a citation of this that is definitely
related to this issue:
Arachne perimeter generator sometimes produced extremely short segments
even when there was no need. These extrusions could have been incorrectly
shown as deretractions and also could have caused extremely short and
counter-productive wipe moves #8455
<#8455>
@napter <https://github.com/napter>
I tried to compare G-code for your attached 3MF from 2.5.0-alpha2 and
2.5.0-alpha3. G-code from 2.5.0-alpha2 contains a lot more short extrusions
than G-code from 2.5.0-alpha3. Even a comparison of G-code sizes shows that
2.5.0-alpha3 produce G-code that is about 25% smaller than G-code from
2.5.0-alpha2.
So I think those short extrusions caused your issue, but the issue with
short extrusions was resolved in 2.5.0-alpha3. A similar situation was also
in issue #8511 <#8511>, and
that issue was resolved with 2.5.0-alpha3.
So I think that this issue is also resolved in 2.5.0-alpha3. So please try
2.5.0-alpha3
<https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.5.0-alpha3>
and report back whether your issue is still present or not.
—
Reply to this email directly, view it on GitHub
<#8534 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPYQ2PKDMGELSWLPMI2PZTVVLALNANCNFSM54ETF7ZA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Please @napter can you retest the issue. In case please check with new PS 2.6.0-alpha4. Hope this issue has been resolved to your pleasue :D ... |
|
No response, should be fixed. Closing. |
Description of the bug
When printing with klipper firmware the surface of the print was rough, exactly how it looks when the gcode is too large and printing stutters. Similarly, the issue only happened on curves. However, the same file was printing ok on other printers.
Reducing the STL nodes didn't help. Increasing the gcode resolution didn't help. Changing speed didn't help. The artifacts would repeat in the same spots. When watching the printer it would vibrate when printing on the curves (I believe it was the the extruder stuttering but it was difficult to tell if it was the extruder or a motion axis). After determining it was not a resolution issue, finally, I thought perhaps it is Arachne. I printed the exact same thing, switching perimeter generator to classic and the issue disappeared.
Arachne print:
Classic print:
Side by side:
Notice the bumps on the curves. They print consistently on every print with arachne but not with classic. I've only experienced this issue with klipper.
Project file & How to reproduce
arachne issue.zip
Checklist of files included above
Version of PrusaSlicer
2.5 alpha 2
Operating system
Windows 10
Printer model
Ender 5 Plus running Klipper
The text was updated successfully, but these errors were encountered: