Well, this is interesting:
while further investigating the problem it looks like this:
the value of sensed.BYTE toggles between *55* (00110111) and *183*
(10110111) for quite a while - so its only flipping one bit.
When I increase the toggling speed, I can provoke my *553* error from
*sensed.BYTE* from once a day to several times a minute.
It looks like reading the owfs-file *sensed.BYTE* in python 2.7 is not
an atomic function!?!
Any thoughts?
Cheers,
Martin
On 10/30/2015 08:23 AM, Martin Patzak (GMX) wrote:
Hello All,
I am experiencing 'strange' readings from a DS2408.
Every once in a while (that is about once a day, with reading
the*sensed.BYTE* folders once a second - so its rather rare) the value
read from one of the *DS2408* is *553 *where it should be *between 0
and 255.
*Is this some 'special' value indicating an error or something the
like? Anybody else saw this phenomena before?
I throw this value away and*re-read* again and *everything is fine*!
I am running solely owfs 2.9p8 on a BananaPi running Debian 8 'jessie'
(no owserver or owhttp is running).
There are 25 temperature sensors and 2 DS2408 on a powered bus with an
USB-Link as bus-master.
While there is some perl-code writing to the PIO.<bit> of the DS2408,
it is Python-code reading the sensed.BYTE of the 2408 to display the
state in an HMI on a webpage.
Cheers
Martin
------------------------------------------------------------------------------
_______________________________________________
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
