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

Internal brim overlapping same layer #3185

Closed
panik988 opened this issue Sep 6, 2022 · 10 comments
Closed

Internal brim overlapping same layer #3185

panik988 opened this issue Sep 6, 2022 · 10 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@panik988
Copy link

panik988 commented Sep 6, 2022

What happened?

The internal brim is printed 2 times overlapping the same layer

Project file & How to reproduce

error_interior_brim.zip

Version

2.5.59

Operating system

window 11

Printer model

vzbot 330

@supermerill supermerill added bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build labels Sep 7, 2022
supermerill added a commit that referenced this issue Sep 9, 2022
supermerill added a commit that referenced this issue Sep 12, 2022
supermerill added a commit that referenced this issue Sep 16, 2022
@EllaFoxo
Copy link

EllaFoxo commented Dec 3, 2022

Not sure if this is the same issue, but I've also noticed a double brim on some parts. Running version 2.4.58.5 under Windows 11. Custom configuration for an Ender 5 Plus running Klipper.

Project files & Slicer config: bmg_bug.zip

Double Brim

@lusanagi
Copy link

I'm using version 2.5.59.2 and still get this issue :/
Gcode looks good, but when printing it has the described behavior, which causes the brim to be lifted from the heat plate (only happens with brim, brim ears work correctly).
I do see that even though I have my first layer height set at 0.44 (0.6 nozzle) in the gcode it is set as 0.4375, not sure if that is relevant
image

Running TwoTrees SP5 with klipper (pretty much a Voron Trident); For now I'm running Orca with brimmed prints or if I need tree supports, but besides not having fine tuning like susl, I just realized that estimation is way off than real print time (some times by 2x), and they already stated they won't fix

@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Dec 29, 2023
@supermerill
Copy link
Owner

still can't reproduce in latest 2.5.59.5 release
If you can reproduce it, please put here the problematic project.

@lusanagi
Copy link

All projects give me this issue (I even have a 0.2 layer profile with a first layer of 0.24 and have the same issue); I found that as a workaround I can put the first layer as 0.4 (and 0.2) and the gcode will have the correct height

I just saved a project with my 0.4 profile and attached here
Shape-Box.zip

@supermerill
Copy link
Owner

@lusanagi can't reproduce from my dev build, what is your version? (help -> about)

@lusanagi
Copy link

@supermerill when I mentioned the issue I was on 2.5.59.2, but the project I uploaded yesterday was saved in 2.5.59.6

@supermerill
Copy link
Owner

@lusanagi
can't reproduce with fresh 2.5.59.2, nor 2.5.59.6 on win10.
image

I miss something. Maybe I don't look at the right thing? I checked it via the gcode viewer, and the brim is printed only one time.
Maybe there is something else that mess it. Can you test from an empty configuration directory?

@lusanagi
Copy link

@supermerill I'll try that when I get to my computer, but I can tell you that yeah, on gcode viewer it looks good, but if you check the gcode with a text editor you can see that Z height is reduced by 0.025 (0.4375)
I'm guessing this is the reason the brim is lifted while printing (which is the issue I first mentioned), but I can't say for sure

@supermerill
Copy link
Owner

your z_step is 0.00625
your first layer height is 0.44
0.44/0.00625 = 70.4
rounded to 70 : 70*0.00625 = 0.4375
so the first layer height is set to 0.4375
then after that, the slicing and all the stuff is done.

@lusanagi
Copy link

Well, that's something I didn't know about and don't know how I got that value 🤦
I just set the z_step to 0.005 and get the correct first layer

Thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

4 participants