Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

Hello Jan, thanks for the swift and in-depth reply to my problem: On 12/04/2016 07:31 PM, Jan Kandziora wrote: Am 04.12.2016 um 12:07 schrieb Martin Patzak (GMX): I am experiencing delays and also time-outs when reading temperatures of very very close to and equal to 85 degrees Celsius. This

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

The new node works fine too, but unfortunately I get an error, when a sensor is right at 85 deg C: /Traceback (most recent call last):// // File "read_a_temp.py", line 15, in // //sensed = op.read('/28.676A2006/latesttemp')// // File "/home/mnm/pyownet/src/pyownet/protocol.py", line

Re: [Owfs-developers] Testing code

OK more research and I have made a bit of progress. adding server: fake=10.053C8A010800,10.2AFE89010800,10.90F889010800 to owfs.conf creates these devices with random values, different at each read. They can be split over different lines e.g. server: fake=10.053C8A010800 fake=10.2AFE89010800,

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

> On 05 Dec 2016, at 09:35, Martin Patzak (GMX) wrote: > > >> The new node works fine too, but unfortunately I get an error, when a sensor >> is right at 85 deg C: >> >> >> Traceback (most recent call last): >> File "read_a_temp.py", line 15, in >> sensed = op.read('/28.676A2006/l

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

On 12/05/2016 05:42 PM, Stefano Miccoli wrote: On 05 Dec 2016, at 09:35, Martin Patzak (GMX) > wrote: The new node works fine too, but unfortunately I get an error, when a sensor is right at 85 deg C: /Traceback (most recent call last):// // File "read_a_te

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

> On 05 Dec 2016, at 18:11, Martin Patzak (GMX) wrote: > > [Errno 1] Startup - command line parameters invalid: > '28.CF791502/temperature' > > but this is rare, so I thought I better not mention it right now - but hey, > now I did ;-) this error, despite it’s misleading description, occ

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

On 12/05/2016 06:29 PM, Stefano Miccoli wrote: On 05 Dec 2016, at 18:11, Martin Patzak (GMX) > wrote: /[Errno 1] Startup - command line parameters invalid: '28.CF791502/temperature' /but this is rare, so I thought I better not mention it right now - but h

Re: [Owfs-developers] Testing code

Am 05.12.2016 um 16:39 schrieb Mick Sulley: > OK more research and I have made a bit of progress. > > adding > > server: fake=10.053C8A010800,10.2AFE89010800,10.90F889010800 > > to owfs.conf creates these devices with random values, different at each > read. They can be split over different li

Re: [Owfs-developers] Problem reading temperatures of 85 degree Celsius

Am 05.12.2016 um 09:35 schrieb Martin Patzak (GMX): > >> The new node works fine too, but unfortunately I get an error, when a >> sensor is right at 85 deg C: >> >> >> /Traceback (most recent call last):// >> // File "read_a_temp.py", line 15, in // >> //sensed = op.read('/28.676A2006/lat

[Owfs-developers] Consequence of NOT grounding VDD on DS18x20 in parasite mode

After years of using all sorts of 1-wire devices I've just read in the spec sheet that if the DS18B20 is to be parasite powered then the VDD pin should be connected to ground. Does anyone know of the consequence of not doing so? Also, does anyone have an opinion either way on whether the MAX31826

Re: [Owfs-developers] Consequence of NOT grounding VDD on DS18x20 in parasite mode

I have multiple DS18B20 with VDD tied to ground, and one IButtonLink T-sense with VDD not connected. I observe that the T-sense returns 85.0 *much* more often than the others. Arne On 06.12.2016 07.17, Robin Gilks wrote: > After years of using all sorts of 1-wire devices I've just read in the >