-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Firmware 3.9.0-RC1 print quality degradation compared to 3.8.1 #2543
Comments
Could you post the 3mf file saved by PrusaSlicer using the same settings you used to print it? Also posting the gcode itself would help so we can have a look. |
Sure, here is the 3mf file. |
And the gcode |
Hm... have you tried re-calibrating your linear advance K-value with 3.9.0? I'm not saying the default shouldn't work fine, but I'm curious whether calibrating for the 1.5 K-value makes the issue go away. |
No, I haven't. What is the proper way to run the linear advance calibration ? |
You can find instructions on what Linear advance is and how to calibrate it here: https://marlinfw.org/docs/features/lin_advance.html |
FWIW, I hadn't paid it much mind but since you are also using PETG... I've noticed my PETG prints are also a little sloppier in terms of strings, sags and zits, but nowhere near the picture levels of bad. I initially ascribed it to wet filament but a fresh roll last night didn't show any improvement, so there may be something to this issue. I'll also try running an LA1.5 calibration for PETG next time I load it up. |
@nikkolade thanks for reporting, this is a serious issue and we must solve it before the 3.9 final goes out. |
I don't know what is the problem with this particular calibration, as I only increased the temp to 210C and changed some filenames, but for some reason the included gcode crashes the printer right after the initial bed calibration. Therefore I was unable to print anything with this test. |
I used that code/page recently for flex, so the gcode should be okay. I see you have an MMU. There's a known bug if you try to extrude with IR=1 and FINDA=0, or a runout detected with a "?" on the screen for the filament. (Fix is pending merge) Try doing a load to nozzle first if you haven't already done so - the gcode does not have the MMU single mode Tx/Tc commands that prompt filament selection. |
@nikkolade Just tried the gcode on a MK2.5S without MMU and there was no crash. It is as @vintagepc said. |
The calibration is technically filament specific, so you might want to use the orange PETG for the calibration. |
Also, you're going to want to run a lot narrower range. Your 0.1 line is already showing overextrusion at the start of the fast section, and it just gets worse. Try something like 0 to 0.2 with 0.02 steps instead. (I think the default range of up to 2 is targeted at bowden setups, which require much higher K values) Hope that helps clarify what you're looking at. You might need a few cycles to narrow down the right range of values to test. |
@nikkolade looking at your calibration print I'd say the best K factor is 0.08. S far we've been using 0.12 AFAIK. Save and run a few centimeters of your container print to see if there is any difference. |
.08 looks pretty good to me - Edit your custom filament g-code for the orange PETG and change the K value for the M900 command, e.g. Then try your original print again (be careful you don't revert the K change if you re-open the 3MF file!) You can probably skip doing the whole print and just cut out a chunk of it or stop a few cm in where the issue would have manifested itself |
Ok, I'll let the printer try again with the modified gcode. Let's see if the end result is equal to FW 3.8.1 this time. I'll let you know latest in the morning. |
I would definitely use a smooth PEI sheet to determine the K factor. 😄 |
Interesting, and good to know. I'll spot check my Overture (AKA former Amazon) PETG tonight and see if I get a similar value or if it's closer to 0.12. |
@nikkolade interesting result, please let the print finish if possible for detailed comparison with the one printed with FW 3.8.1 |
Will do. Current print is finishing in about 20 minutes. Will post pictures of the plate. |
Results are in. For me, PLA @ 210C (red) comes in best at 0.04, PETG@235 (black) also at 0.08. I do have a Skelestruder but the gear->nozzle distance isn't as different from stock as it used to be; the 3S revision shortened that a bit; so my values might be a smidgen lower than expected. (FWIW I was running 20 for PLA and 35 for PETG in LA1.0, but those were not calibrated at all and just going off a generic comment that I could drop the Mk3 values by ~10. ) |
The print is now complete and there seems to be still a big difference with the latest 3.9.0-RC1 and the older 3.8.1 versions. The print looks much better from the front after the K-value change. The filament is Prusa PETG, not prusament. All my filaments have been dried every once in a while, so they are not wet. The printer itself is originally of MK3 model and it has been delivered on December 2018. It has not been used heavily though as there has been occasionally months between the prints. I quess 3-4 complete rolls and half a dozen non-empty rolls. |
@nikkolade oh, this is interesting - it looks like some error is being accumulated after those many retractions. |
So I ran your gcode on my MK3S with some prusament petg (the orange one) and I'm comparing to some other ones I have. At least with this material, using the .15/.2 quality and speed profiles (so default params) I see thin strings, but nothing too bad. Using yours it starts similar (similar amount of thin stringing in general), but then I noticed the pillars start to wobble heavily towards the top, and this is when quality degrades very quickly. In my case it detached on one side, so I'm re-running it again. Did you notice this effect as well, or something different? |
Yes, that is one of the observations I had made. |
So I ran through some different trade-offs, and came to this: https://github.com/wavexx/Prusa-Firmware/tree/la15_chained_wipes Before I make a PR, I'd love some feedback. I see an improvement in both your "bad" test, as well as a re-sliced model with .15 layers. Stringing is reduced and the pillars look very consistent, however at least using PETG there are still tiny whisps which very in quantity just by reprinting the same model twice. I'd say this is consistent with what I would expect - but I've been wrong before ;) |
Sure, I'll take it for a spin tomorrow! |
It does look quite good- I don't have any 3.8.1 references, but the surface finish is perfect, and the stringing is about on par with the better results I've gotten for this particular model. It was worse than those for my default K of 0.08 but improved when I tried 0.12 (which makes sense, since this altered the K handling slightly it means a different value might now be optimal). |
@vintagepc I pushed one last change which again covers some even rarer corner cases. I re-checked this model and I get consistent results with the previous version. I was only able to see a minor difference in a synthetic test that starts extrusion mid-flight (something at least prusa-slicer and slic3r never does). But if you have filament to spare, I'd love an extra test :P |
I have a number of items on the to-print list; I'll merge your changes to my local build and use it during the coming week 👍 |
Solved by #2591 |
Been waiting for this to be resolved to try LA1.5. To be clear, do I need to change anything in the slicer to make use of this or will my existing slicer profiles be recognised as legacy and translated by the LA1.5 firmware? |
Old gcodes are converted automatically. You don’t have to change anything. Slicer profiles will be updated after the final release (hopefully 2 weeks from now) |
My 2 cents: I dialed in the K-factor for PETG (with marlin LA 1.5 pattern) and observed a decrease in quality compared to LA 1.0 as well. Most notably, corners were sometimes massively underextruded. To the extent that there were holes in them. |
We can't switch to another letter since the Marlin test pattern only uses K as the K factor :( |
Also, the two ranges don't overlap. Anything over ~15 has to be LA1.0, anything under ~2 (unless you have a bowden system) is 1.5 |
LA1.5 is < 10 |
I stand corrected. I was going from memory and the thresholds I saw in earlier code. (I do know that it was <15 but in reality values over 2 don't make a lot of sense for most cases, especially stock MK3s) |
@nikkolade please contact me via email, we'd like to reward you for helping us fixing this issue. |
https://marlinfw.org/docs/features/lin_advance.html It was linked in the first few posts. |
Hello! |
@mmuellerphoto very helpfull. I saw a preliminary version of this PDF a couple of days ago. This would be a nice addition directly to prusa help. |
Thank you for the kind words - what can I say ... I'm here ... ;o) |
@nikkolade I think we sorted out and fixed this issue. Can we close it and continue on other things in #2693 ? BTW: Thanks again to everyone helping testing and improving the firmware. Awesome community we have here. |
I'm closing this issue as stale, thanks for understanding. |
Printer type - MK3S
Printer firmware version- 3.9.0-RC1
MMU Upgrade - MMU2S
**MMU upgrade firmware version 1.0.6
Describe the bug
Print source: https://www.thingiverse.com/thing:3494496
and explicitly: https://www.thingiverse.com/download:6386081
While printing the above STL sliced with PrusaSlicer 2.20-RC2 and using PETG material works just fine when using the MK3S firmware 3.8.1 (build result on the left), the very same gcode results an awful quality after the printer was upgraded to 3.9.0-RC1 (end result on the right).
Please, see the attached picture.
To Reproduce
Upgrade firmware MK3S firmware to 3.9.0-RC1
and print the above mentioned STL file.
Expected behavior
The print quality should not degrade, compared to previous firmware version.
The text was updated successfully, but these errors were encountered: