Skip to content
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

[1.1.x] Update Thermal Protection Documentation #8282

Merged
merged 4 commits into from Nov 7, 2017

Conversation

RowanMeara
Copy link
Contributor

Even before the recent M303 thermal protection changes, the documentation of
the thermal protection feature in the config files did not match the
implementation. I fixed the documentation and reconciled the M303
implementation with the documentation.

The documentation stated that thermal protection needed to be enabled to have min and max temp protection. However, the thermal protection feature does not affect min/max temperature protection so I corrected the documentation.

The Configuration_adv.h has two pairs of thermal timeout variables for different scenarios. I updated the M303 thermal protection in temperature.cpp to use the correct variable pair.

Even before the recent thermal protection changes, the documentation of
the thermal protection feature in the config files did not match the
implementation.  I fixed the documentation and reconciled the M303
implementation with the documentation.
@RowanMeara RowanMeara changed the title Update Thermal Protection Documentation [1.1.x] Update Thermal Protection Documentation Nov 6, 2017
*
* If you get too many "Heating failed" errors, increase WATCH_BED_TEMP_PERIOD and/or decrease
* WATCH_BED_TEMP_INCREASE. (WATCH_BED_TEMP_INCREASE should not be below 2.)
* As described above, except for the bed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps this should continue to include the references to M140/M190, as these bed and hotend temperature G-codes are easy to get mixed up.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, that makes sense. I put the gcodes back in without the repeated explanation.

#else
TEMP_HYSTERESIS
WATCH_TEMP_INCREASE
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hysteresis is the range of temperature considered close enough to call the temperature a match. If the hysteresis variable is being used in some other way, then it shouldn't be called hysteresis.

Copy link
Contributor Author

@RowanMeara RowanMeara Nov 7, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I noticed that last night. I'll make that change.

@thinkyhead thinkyhead merged commit 094bebc into MarlinFirmware:bugfix-1.1.x Nov 7, 2017
mtm88001 pushed a commit to mtm88001/Marlin that referenced this pull request Dec 9, 2017
* Fix thermal protection documentation.

Even before the recent thermal protection changes, the documentation of
the thermal protection feature in the config files did not match the
implementation.  I fixed the documentation and reconciled the M303
implementation with the documentation.

* Applied documentation changes to sample config files

* Renamed hysteresis to watch_temp_increase

* Added gcodes back into documentation.
damicreabox pushed a commit to damicreabox/Marlin that referenced this pull request Sep 14, 2018
* Fix thermal protection documentation.

Even before the recent thermal protection changes, the documentation of
the thermal protection feature in the config files did not match the
implementation.  I fixed the documentation and reconciled the M303
implementation with the documentation.

* Applied documentation changes to sample config files

* Renamed hysteresis to watch_temp_increase

* Added gcodes back into documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants