I saw your note and marveled. The law of unintended consequences...
You are using family code 42, which is the DS28EA00
Looking at the datasheet (
http://datasheets.maxim-ic.com/en/ds/DS28EA00.pdf) on page 8 you see
that the temp alarm registers are only one byte long,
and have only 1C resolution.
On the oither hand, OWFS caches the value that you write to the register,
and stores it as a stable value for around 15 minutes.
We cache it at full floating point resolution, so it looked like a safe
bet...
You could use temphigh and templow.
Paul Alfille
On Wed, Aug 4, 2010 at 5:04 AM, Alex Shepherd <[email protected]>wrote:
> Hi Guys,
>
> Something that has got me a bit puzzled is I am using the "temphigh"
> storage
> of a sensor to store a thermostat set point. I have a python script that I
> periodically execute each minute from cron that checks the temperature
> against the temphigh and take appropriate action which is to write a 0 or 3
> to the PIO.BYTE to control pumps/valves etc. This works fine if the value
> of
> temphigh is a whole number. However if it is say 21.5 it works for a while
> and then mysteriously the temphigh value gets changed somewhere to 21 and
> stays there. It seems to happen within 10-15 mins of me changing the value.
>
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
