As long as 85 is never a valid temperature. Not sure why they put the error temp in a functional range.
> On Feb 19, 2019, at 05:35, Mick Sulley <m...@sulley.info> wrote: > > The failure happened for about 10-20 minutes, reading about every 10 seconds > or so, then it recovered and is reading fine again. > > All devices are powered. > > I could change my code so that it reads fasttemp and if that is 85 it reads > through the others to try to find a good read. Is that a sensible thing to > do? > > Thanks > > Mick > >> On 19/02/2019 12:49, Jan Kandziora wrote: >>> Am 19.02.19 um 10:39 schrieb Mick Sulley: >>> My control system has detected a no read (85) on a DS18B20 temp sensor, >>> however if I look at it via owhttpd I can see temperature, temperature11 >>> and temperature12, but 85 for fasttemp, temperature9 and temperature10. >>> >>> How can that happen? The sensor had been working OK. I am running >>> 3.2p3 on a Raspberry Pi >>> >> Each reading of the uncached temperature nodes (but latesttemp) triggers >> a new conversion. The browser orders owhttpd to do exactly that. What >> you see isn't one conversion but a series of conversions of which some >> failed because of a Power-On-Reset during conversion (that's the 85°C >> reading) and some failed not. >> >> Check your cabling. Also check if powering the chip helps. >> >> Kind regards >> >> Jan >> >> >> _______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
