Am 21.08.2016 um 09:25 schrieb Henrik Östman:
> :-)
> Thanks now it's working again!
> Can we expect this fix in the next release?
>
Yes. But next release is still a while to go, having had the latest
release last week.
Or maybe not?
> And one more thing, since this is the first time for me with an sensor
> that has multiple temperature resolutions.
>
> Calling upon /lasttemp looks like its defaults to /temperature9?
> So to switch between resolutions I could do this:
>
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/temperature12
> // Switching to 12 bit resolution
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/lasttemp
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/lasttemp
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/lasttemp
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/lasttemp
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/temperature10
> // Switching to 10 bit resolution
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/lasttemp
> owread -s 192.168.10.110:4304 /uncached/28.3F28AE060000/lasttemp
>
> Correct?
>
This should work with the debugpatch3.diff.
.../latesttemp first reads data from the scratchpad, then looks into
data[4] to decide which resolution the data in data[0] and data[1] have.
Please check if it works that way. Otherwise we have to debug a bit more.
Kind regards
Jan
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
