-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
[5.5.0-b1] Initial layer speed not honored #17010
Comments
Just a note, the produced gcode also has these speeds. I noticed the issue because my printer was going mad on the first layer, and nothing was sticking. |
That's weird. The attached project file uses a smaller model, but shows the same issue for me |
Thanks for taking the time to look! For what it's worth, I've just narrowed down the trigger for me: changing the 'Slicing Tolerance' setting back to 'Middle' fixes the problem, but both 'Inclusive' and 'Exclusive' modes cause the fast initial layer problem. |
Hi @stestagg, Welcome to the UltiMaker Cura Github 🚀 This was quite a puzzling issue, but I believe I've figured it out. This is the repaired model: CE3S1_wall-mini.zip To me, it doesn't seem like a bug in Ultimaker Cura, since the error is caused by your model. |
Good one @MariMakes . I owe you a beer. |
Hi, Thanks @MariMakes and @GregValiant, and sorry, I've trained myself to ignore the watertight error message, as it's so common now! but it was telling me there was a problem. I've checked and it's working for me once the mesh is fixed. |
I can also confirm on my own end that this is only occurring in 5.5.0 and later releases, I've been pulling my hair out trying to solve it and going back to 5.4.0 seems to have fixed the problem. These two pictures were taken using the same profile and same printer settings, the only difference is the cura version. 5.5.0: 5.4.0: I've tried tweaking every setting to fix this but at the time of writing the only solution seems to be to revert to 5.4.0. |
I got the same problem cura 5.5.0 with my voron2 custom, but with the same model, slice on Flsun Super Racer won't see that problem. |
@MariMakes I would like to re-open this as it is an ongoing problem. It isn't just an "Initial Layer Speed" problem so maybe changing the report title would be in order. This is the model submitted by @stestagg on 10-17. I ran this model through MS 3D Builder and it has no errors. You can see that the speed of the mid-wall extrusion is 259mm/sec. If I change the Flow Equalization to zero% the problem goes away. This behavior appears to involved the wall thickness and the Line Width that will fit between the outer walls. This is the same setup in 5.4.0. You can see that the Flow Equalization at 100% results in a reasonable speed increase to 84mm/sec. This is in 5.2.2. The speed has been adjusted down to 57.93 rather than up to 259. A 200mm/sec speed difference would seem to indicate that sumthin' ain't right. |
@GregValiant For example, voron2, find the file : So that I can be sure Initial Layer Speed will work. |
That fixed it for me, thanks! |
Does the change on file |
It's only for Voron based profiles. Have a look at the corresponding Ender file. Sorry I don't know how it is called and can't look it up for you right now. |
I switched back to Cura 5.4. in Cura 5.6 this also seems to an issue. So before fixing the files I simply reverted back. Anyways, thanks for your reply |
@ole1986 it does not. The "creality_base.def.json) file says: |
I took a quick look into my related file using the FLsun Q5/QQ and could not quickly figure it out.. so that is why I switched back |
5.2.2 would be my choice. |
Getting the same on Sovol SV06, so it not only about Vorons. Flow equalisation and print thin walls options doesn't help. |
Cura Version
5.5.0-b1
Operating System
Mac Sonoma 14.1
Printer
Creality Ender-3 S1 (pro, using klipper v0.11.0-299-gb1f597c5)
Reproduction steps
Actual results
I.e. not 15mm/s but 150mm/s
Extract from the gcode
Expected results
Expected gcode
Add your .zip and screenshots here ⬇️
Stl can be provided if useful
The text was updated successfully, but these errors were encountered: