-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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
Bed thermistor malfunction behavior #2024
Comments
@clefranc That sounds like a bug! I will try playing with that later too, and see if there's a simple fix. I assume you are testing thermal runaway protection and have that option enabled (?) but it sounds like this condition should throw an alarm regardless of whether there's thermal protection or not. |
Updated the OP! |
I see that if the thermistor isn't connected at all from the start, you probably don't get any alarm either. |
@thinkyhead Is there a reason why there is not WATCH_TEMP_PERIOD for the bed? There is thermal runaway protection for both the hotend(s) and bed, but the WATCH_TEMP_PERIOD is not applied to bed. |
@thinkyhead Here is some bed tests. Will do hotends later. Using #2055 TEST #1 - Bed heating pad disconnected before startupThe bed heating pad shows 0°C current temperature at startup. Host:
LCD:
Conclusion: THERMAL RUNAWAY RISK: noneTEST #2 - Bed heating pad disconnected after heating beginsThe bed heating pad shows 25°C current temperature at startup. Host:
LCD:
Conclusion: THERMAL RUNAWAY RISK: noneTEST #3 - Bed heating pad disconnected before startup when thermistor table begins at 25°CThe bed heating pad shows 25°C current temperature at startup (ADC read 1023). Host:
LCD:
Conclusion: THERMAL RUNAWAY RISK: HIGHTEST #4 - Bed heating pad disconnected after heating begins when thermistor table begins at 25°CThe bed heating pad shows 25°C current temperature at startup. Host:
LCD:
Conclusion: THERMAL RUNAWAY RISK: HIGH |
@clefranc No bed watch period has been implemented yet, but it should be easy enough to clone the hotend code and apply it to the bed heater. I will do that soon. Another thing that needs to be added is sudden temperature change handling, a change of more than 5 degrees in a single sample period (up or down). But that won't catch a thermistor that falls out just shortly after heating begins. The watch temp period should catch that situation, however it currently only does a single test, so it will not catch a thermistor that falls out after that (currently 16 seconds after heating begins). So a sudden temp change handler is needed, and the heating sanity check (watch temp period) needs to re-enable itself after each test. |
Please continue discussion here: #2066 |
Closing this. See #2066 |
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. |
Doing some temperature protection test today!
I started with the bed:
The problem is that the target bed temperature is still at 100°C (LCD) and there is no message of a temperature malfunction, not on the LCD nor the host (Repetier), but the bed has nonetheless disappeared from the host.
I'm using the latest dev version.
EDIT: I'm using all thermal protection:
define THERMAL_RUNAWAY_PROTECTION_PERIOD 40 //in seconds
define THERMAL_RUNAWAY_PROTECTION_HYSTERESIS 4 // in degree Celsius
define THERMAL_RUNAWAY_PROTECTION_BED_PERIOD 120 //in seconds
define THERMAL_RUNAWAY_PROTECTION_BED_HYSTERESIS 4 // in degree Celsius
define WATCH_TEMP_PERIOD 40000 //40 seconds
define WATCH_TEMP_INCREASE 10 //Heat up at least 10 degree in 20 seconds
The text was updated successfully, but these errors were encountered: