Suddenly "no pit probe"


 
P

PTirmal

New member
I've had my heatermeter for a month now and have used it in a bunch of smokes. I recently had an issue where during startup it cut off my damper/fan and displayed "no pit probe" after maybe 5 minutes of starting up fine. I thought it might have been a thermocouple that went bad but I just received the replacement and it's not reading that one either. I picked up a presoldered kit so I'm not sure what I should be looking at to diagnose the issue. I reset my config to my backup I created when I initially set it up just in case since I had to mess with disabling probe 0 so I could still use it to smoke but that didn't do anything.

Any help?
 
Did you verify that the probe configuration was set to Thermocouple and 5mV/C with 0 offset?
thermocouple-config.png

Once set like that you should be able to just short the thermocouple connector with a piece of wire or a paperclip (touch it to both metal bits on the connector) and have it read ambient temperature. If it doesn't then it sounds like something has gone wrong in the circuitry and I can replace it once we're allowed to leave our homes again.
 
I did set it to thermocouple, yes. I will double check the rest, I think mV/C and offset were 0. I will check when I get home. I appreciate your help Bryan!
 
So I changed the mV/C back to 5 and it reads my new thermocouple and the old one. :unsure:

I did update the AVR to the snapshot version from this month. Could that have had something to do with it? Like I said it was running during startup no issues, I didn't touch it when the thermocouple stopped reading. I don't think the mV/C could have changed itself to 0 so something else funky must have happened? I guess I'll keep an eye on it.

Thanks again for your help!
 
Yeah it is certainly strange. There are some settings that also edit that value so I am wondering if there is a weird corner case where one isn't passed so the value is converted to 0. I've not seen this happen, but that's the only possibility I can muster, apart from me messing up the EEPROM (storage) write code which is also a possibility.

Glad it was just a configuration loss and not a hardware issue though!
 
You must log in or register to reply here.

 

Back
Top