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

picoreflowd doesn't handle MAX31855 read errors gracefully #2

Closed
chron0 opened this Issue Sep 21, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@chron0
Copy link
Member

chron0 commented Sep 21, 2014

Reported by Kurt via:
https://apollo.open-resource.org/mission:resources:picoreflow#comment_146a0a60fe7cb141ca3eca11a8bb8eac

Have things pretty well set up, but for some reason I get random “MAX31855Error: Thermocouple short to ground” errors, with 2 different MAX31855 breakout boards. As far as I can tell, there's nothing shorting, all good connections, etc.

What I'd like to do is ignore that and continue running, however once that occurs, the program quits recording the temperature until I kill picoReflow and start it again.

Is there a way to tell it to just keep going, or even close just restart the max31855 part of the program when that happens?

Specific error:

Exception in thread Thread-2: Traceback (most recent call last):

File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
  self.run()
File "/home/pi/picoReflow/lib/oven.py", line 185, in run
  self.temperature = self.thermocouple.get()
File "/home/pi/picoReflow/lib/max31855.py", line 41, in get
  self.checkErrors()
File "/home/pi/picoReflow/lib/max31855.py", line 78, in checkErrors
  raise MAX31855Error("Thermocouple short to ground")
MAX31855Error: 'Thermocouple short to ground'

@chron0 chron0 added the bug label Sep 21, 2014

@chron0

This comment has been minimized.

Copy link
Member

chron0 commented Sep 21, 2014

Please pull and checkout the MAX31855-EH branch (https://github.com/apollo-ng/picoReflow/tree/MAX31855-EH) and see if it continues to run. It should log the occurrences as errors but unfortunately I couldn't test it on real HW yet.

@chron0 chron0 closed this Jun 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment