-
-
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] Thermal runaway detected while using #999 & #998 virtual temp sensors #18525
Comments
If you give any heating gcodes you can still trigger a Thermal runaway. |
No gcodes are sent at all |
Confirmed on a standard ramps current bugfix. Only config changes was to enable a REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER and set TEMP_SENSOR_0 999 |
Seem to have been introduced int this commit. c43bbcc |
See the PR for how to get around this issue. |
Works great. Thank you. Do you want me to close this issue or do we wait for official merge ? |
@Patag I suggest you wait for the PR to merge. |
Ideally you would re-test after the merge to be sure it is fixed. Sometimes PRs change during the PR process and are merged before bugs are found. |
OK |
8a594fc - Not fixed all problem: #define TEMP_SENSOR_0 1047 #define TEMP_BED_PIN P0_23_A0 // A0 (TH1) UPDATE: UPDATE2: #define TEMP_SENSOR_0 1000 #if TEMP_SENSOR_0 == 1000 |
I have just retested with merged changes. They work fine. |
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. |
Bug Description
Thermal runaway is detected at startup and stops Marlin.
My Configurations
BTT SKR Pro v1.1 on test bench
Conf.zip
Steps to Reproduce
Expected behavior: Normal Marlin startup
Actual behavior: Thermal runaway detection "MAX TEMP on E1" or something like that.
Additional Information
This happend after 30/06 commit
The text was updated successfully, but these errors were encountered: