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

Fix for MAX6675 MINTEMP errors #1680

Closed
wants to merge 1 commit into from
Closed

Fix for MAX6675 MINTEMP errors #1680

wants to merge 1 commit into from

Conversation

AnHardt
Copy link
Member

@AnHardt AnHardt commented Mar 24, 2015

SD-Card and MAX6675, both use hardware SPI. They used to conflict.
For that reason the MAX code was puled out of the interrupt(#1402).
Since then for different reasons either the code did not compile or failed wit an MINTEMP error.
So a test was impossible until now.
Here I eliminate the MIN-MAX-Temp-Test for extruder0 in the interrupt when we are using MAX6675.

When tests are successful we can close #1226 and #1227 and https://github.com/MarlinFirmware/Marlin/milestones/Bug%20Fixing%20Round%203

SD-Card and MAX6675, both use hardware SPI. They used to conflict.
For that reason the MAX code was puled out of the interrupt(#1402).
Since then for different reasons either the code did not compile or failed wit an MINTEMP error.
So a test was impossible until now.
Here I eliminate the MIN-MAX-Temp-Test for extruder0 in the interrupt when we are using MAX6675.

This will let us close #1226 and #1227 and we can close https://github.com/MarlinFirmware/Marlin/milestones/Bug%20Fixing%20Round%203
@thinkyhead
Copy link
Member

Ah, I see the temperature is being checked in manage_heater. Is there some reason that code can't be moved into the #else condition of the #ifndef HEATER_0_USES_MAX6675 you just added?

@thinkyhead
Copy link
Member

Compare to #1674. I moved the temperature check next to the others, but left the temperature update routine where it was. This makes it possible for the temperature to be checked before being read, but it would just be "0" for the first iteration of the program loop when the printer first boots up, and should have no effect.

@thinkyhead thinkyhead closed this Mar 24, 2015
@AnHardt AnHardt deleted the MAX6675_mintemp branch March 26, 2015 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants