Hi,
I never faced the issue myself but I'm just wondering, can't we just
check the CRC for those failed conversions ? Is the CRC correct in
that case ?
Rgds.
-Romain
On Wed, Sep 19, 2012 at 12:38 PM, Marcus Priesch wrote:
> Well, 80 normally means that you dont have enough power to do the temp
Well, 80 normally means that you dont have enough power to do the temp
conversion ... are you doing parasite powering ? - then you should
consider using another wire to get 5v to the temp sensor ...
i will look what OW_get internally does and check the return code ...
regards,
marcus.
On Mit, 2
It seems that res could be 0, so None could be returned.
I'll see if that happen.
This is because one of my sensors is in my living room, and the 1wire
signal goes though my telephone lines all over my house.
It is not very reliable.
Before I upgraded from an old debian to ubuntu precise, the bad
> Made my wrapper to its capi, and it looks MUCH better.
> Threads seem responsive again.
Hey, glad to hear that ;)
> Are there exceptions thrown when a sensor read goes wrong?
according to libcapi.py's get and put:
def get (self, path) :
buf_p = ctypes.POINTER (ctypes.c_char) ()
Hi
Thanks a lot for your quick response.
I used pip to install pyowfs with no problem (found out I had to
install libow-dev for it to work)
Made my wrapper to its capi, and it looks MUCH better.
Threads seem responsive again.
Are there exceptions thrown when a sensor read goes wrong?
Thanks ag
Hello Sophana,
i dont know if it would help the gil issue, but you could try pyowfs
(easy_install pyowfs) wihich basically is a ctypes wrapper around
libow.
starting a owserver instance and then talking via different pyowfs
Connections (one in each thread) to the owserver should not block the
ot
