-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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] Cooling fan full speed after 2.0.9.3 update #23459
Comments
Please attach configuration files. |
Marlin.zip |
Configuration.zip |
Duplicate of #23418 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Did you test the latest
bugfix-2.0.x
code?Yes, the issue still exists with the latest 'bugfix-2.0.x' code
Bug Description
After updating to 2.0.9.3, the cooling fan on both my Anet A8s and my Anet A8 Plus run at full speed after power on, even though '0%' is displayed for fan speed. If I move the cooling fan speed setting to 100% and then back to 0%, the fan then turns off but will go back to 100% if the printer is power cycled or experiences a serial reset.
Bug Timeline
First started with updating to 2.0.9.3 - was not an issue in 2.0.9.2 or prior (going back to at least 2.0.7 or earlier)
Expected behavior
Cooling fan should be off at power on and/or when setting is set to 0%
Actual behavior
Print cooling fan runs at 100% even though the setting is set to 0%
Steps to Reproduce
After power on or a serial reset of the printer, the print cooling fan runs at 100%
Version of Marlin Firmware
2.0.9.3
Printer model
Anet A8 and Anet A8 Plus
Electronics
Stock electronics
Add-ons
Anet A8 full graphics display
Bed Leveling
No Bed Leveling, I do this manually
Your Slicer
Cura
Host Software
Cura
Additional information & file uploads
Nightly build and 2.0.9.3 release configs for both the A8 Plus and A8 uploaded
The text was updated successfully, but these errors were encountered: