-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
GCode spam on perimeter overhangs caused by M106 enable fan commands #11856
Comments
related: #11981 |
Can confirm in 2.8.0; this problem makes my fan literally uncontrollable |
Yeah, unfortunately it still isn't fixed. I've been tracking other posts of the same issue but different circumstance and there doesn't seem to be much happening on fixing it. |
Yes |
Fixed in 2.8.1-rc1. Closing. |
Description of the bug
When slicing any model that has curving overhang perimeters(from what I noticed, may apply to others), the slicer outputs multiples of M106 enable fan commands before and after each of the G1 commands. Using both 'Bridges fan speed' and 'Dynamic overhang fan' makes the issue twice as bad, but it is still there regardless of which of the either two is enabled/disabled.
Here is an example with a simple squished benchy(simply to force the overhang perimeter generation) that clearly shows the problem:
If I disable 'Bridges fan speed' by setting it to 0, it gets slightly less insane, however still very bloated:
The side effect of this was some stuttering of the printer when it reaches the overhangs, which was inexplicable to me at first. Another problem is that Arc Fitting does not recognize the overhang perimeters because of the M106 spam instead of neat G1 blocks of gcode.
I've tried the same thing in PS 2.6.1 and everything seems to work correctly, with G1 commands staying in blocks, with M106 only before and after the whole block, as expected. Here's the 2.6.1 example with the same benchy:
Project file & How to reproduce
M106 spam benchy.zip
Slice the squished benchy and go to a layer where the bow has overhang perimeters.
Move the horizontal gcode slider so the toolhead is in the middle of the overhang perimeter
The issue should be apparent on the left side of the gcode line preview.
Checklist of files included above
Version of PrusaSlicer
2.7.0+win64
Operating system
Windows 10 22H2
Printer model
Ender 3 V2 Neo (with mods)
The text was updated successfully, but these errors were encountered: