Skip to content
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

Supported part first layer speed / use bridge settings #20391

Closed
sargonphin opened this issue Mar 14, 2025 · 7 comments
Closed

Supported part first layer speed / use bridge settings #20391

sargonphin opened this issue Mar 14, 2025 · 7 comments
Labels
Type: Question Question about how something works with concrete answers.

Comments

@sargonphin
Copy link

Is your feature request related to a problem?

When printing supported parts, it is preferable to have a small vertical spacing (Z distance) between support roof and supported part to make removal easier. Because of that spacing, it is necessary to print the first layer of a curved supported object very slow to give time for the filament to drop and solidify

Currently, Cura does not provide such a feature and thus, supported walls and skin are not printed correctly. The walls are printed at regular walls speeds, which is too fast and the filament "drags" in a straight line instead of a curve (the pictures below show a wall that was printed at 180 and 240mm/s over a support roof, with supports already removed)

Image
Image

Describe the solution you'd like

2 possibilities, one preferable to the other but the other is already implemented:

  • A new set of settings for the first layer over supports, with the possibility to expand these settings to 3 or more layers instead of just 1 (useful when printing with small layers heights) (preferable solution)
  • Layers directly over supports use the same speeds as Bridge settings

Describe alternatives you've considered

A setting exists to print an unsupported skin layer using Bridge settings (Bridge Skin Support Threshold in Experimental) which allows skin to be printed over supports more easily, but walls do not use these settings/don't have an equivalent setting and thus are printed too fast

Affected users and/or printers

Only users using fast printers that print fast walls will benefit this change

Additional information & file uploads

No response

@sargonphin sargonphin added Status: Triage This ticket requires input from someone of the Cura team Type: New Feature Adding some entirely new functionality. labels Mar 14, 2025
@HellAholic
Copy link
Contributor

HellAholic commented Mar 14, 2025

@sargonphin Feature is part of the 5.10 Beta release, you can download that version and try it out.
Search for Bottom Surface and all the settings related to that should pop up. You can set number of layers, set speed, adjust flow, change pattern, set extruder, .... and much more :)

https://github.com/Ultimaker/Cura/releases/tag/5.10.0-beta.1

Image

@HellAholic HellAholic added Type: Question Question about how something works with concrete answers. and removed Type: New Feature Adding some entirely new functionality. Status: Triage This ticket requires input from someone of the Cura team labels Mar 14, 2025
@sargonphin
Copy link
Author

Thanks for your reply, but this does not resolve the problem I am having here. These settings are for bottom layers only, but in my case the walls that need to be printed slow are not at the bottom. After downloading the new version and setting up the features, the wall speeds did not change

Image

Here are a couple screenshot to show what part I am trying to print

Image
Image

Let me know if there are more settings I did not see that should be changed. Here is the file for the part in question

TubeDuct_Pump.zip (3mf file inside)

@HellAholic
Copy link
Contributor

HellAholic commented Mar 16, 2025

How many "bottom surface skin layers" have you set in the profile if the number is 0 then the settings will not apply.
With 2 layers & setting bottom surface outer/inner wall speed to 25 I get this which includes the walls.

Image

internal reference @Ultimaker/cura :

  • All settings for the bottom surface skin should have enabled if 'Bottom Surface Skin layers' > 0

@pkuiper-ultimaker
Copy link
Contributor

pkuiper-ultimaker commented Mar 16, 2025 via email

@sargonphin
Copy link
Author

sargonphin commented Mar 16, 2025

Thanks for the fast reply! @pkuiper-ultimaker I am not using any default profiles, as this printer is custom-built. The profile is also custom

@HellAholic Thank you for the tip! I had 0 bottom layers in my settings. I am encountering an extra problem though, where the bottom layer is only partially printing slow. This leads to very sharp changes in flow which even with the direct extruder would show on the surface

Image

I will search for a solution in the background, if I find anything I will get back to you. Thanks again for the help, very appreciated :)

EDIT: I had set the bridge skin threshold back to 0 to test the settings. Setting it back to 94% (that's the threshold that works for me) did kind of fix it, but the bridge settings are different than the bottom layer settings. Bridges have multiple layers and different flow settings than skin

EDIT 2: I wanted to test the new settings but the solid-state relay for bed heating broke down the very moment I wanted to test... transistor shorted source and drain, bed heating up permanently 😆

@pkuiper-ultimaker
Copy link
Contributor

pkuiper-ultimaker commented Mar 16, 2025 via email

@sargonphin
Copy link
Author

Alright after fixing the bed SSR and fine-tunning some settings, I can confirm that the results are significantly better than before. Issue solved I suppose, although it might be worth keeping in mind moving these features into "supports" since it's only useful with supports. This should avoid further confusion and passively increase print quality for most people ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Question Question about how something works with concrete answers.
Projects
None yet
Development

No branches or pull requests

3 participants