-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
[Setting] MINTEMP error immediately after print start #1042
Comments
Further investigating: Recv:`` T:28.91 /0.00 B:60.25 /60.00 @:0 B@:7 W:0 |
Solved, Need changes in Configuration_adv.h |
#define PREHEAT_TIME_HOTEND_MS 30000 Maybe it is not a good idea, check the recommendation in the configuration file. |
I leave these disabled. |
I played with the values. The lowest value was: 19000. If i go with lower values, the FW kills the machine with MINTEMP error, even while the temperature reading rising. Solved the issue for myself, the printer works with that timeout offset. Perhaps because my Ender 3 V2, board 4.2.2 with STM32F103RE was the first implementation. I don’t know, but thanks for the reply. |
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. |
Did you test with a precompiled firmware?
No, but I will test it now!
Bug Description
On Ender 3 V2 with 4.2.2 board, can't heat up hotend and bed at the same time on lots of FW (sometimes works, sometimes not). Need to change the start G-code script:
M190 S{material_bed_temperature} ; heat to bed setting in Cura and WAIT
M109 S{material_print_temperature} ; heat hotend to setting in Cura and WAIT
Bug Timeline
No response
Expected behavior
Heat both hotend and bed
Actual behavior
MINTEMP error
Steps to Reproduce
No response
Version of Professional Firmware
Custom built from your repo
Printer model
Creality Ender 3 V2
Electronics
Board 4.2.2
Add-ons
No response
Bed Leveling
ABL Bilinear mesh
Your Slicer
Cura
Host Software
OctoPrint
Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: