Putting the temperature read in a loop, or having multiple reads scattered through the main program do no good. My problem is the only way to fix this seems to be to reboot the gpy. I feel this difference is indicative of what the root cause of the problem is, but I don't understand the library well enough to figure it out. While the newer version returns None (indicating a busy DS18B20). If I'm running the older library, read_temp_async gives an Indeċrror(most likely indicating it can't find the DS18B20). However if I try them in a program that deepsleeps they often fail to give a temperature. Both routines, the one at the bottom of the page at, and a more resent version at will chug away happily in a loop printing temperatures at 2s intervals forever. I've tried a couple of different flavours of the OneWire library with a single DS18B20 temperature sender.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |