Hi,
Am Dienstag, den 10.08.2010, 18:58 +0200 schrieb Petr Jakeš:
I don't think pyowfs is intended to be used that way. Sounds
like you
need something different.
Hmmm... thanks for the hint.
maybe I can just mount the OWFS and go through
Hi Paul,
thanks for your words ...
Am Mittwoch, den 11.08.2010, 07:15 -0400 schrieb Paul Alfille:
I suspect that pyowfs does an initial scan when you first connect,
nope, it doesnt ...
when you call find () it internally calls iter_sensors () which in turn
calls libcapi's OW_get with the
Hi Petr,
To solve the problem, I have owfs mounted and I am reading the devices
from its file structure right now. It looks it is a bit faster with
the passive RS232 adapter. Because of that I can not provide feedback
right now.
But what you propose looks exactly what I wanted, when I
But what you propose looks exactly what I wanted, when I was trying to
write the code using the pyowfs.
For devices, that are not connected to the bus permanently (like
iButton for example), there is a need to reinit() the bus repeatedly,
otherwise new devices are not discovered.
yes,
Hi again,
sorry, maybe it got already fixed and I missed it but
tracked this down a little further, with 2.7.p39 and 2.8p0 an
owget /alarm
causes
[129730.009333] owserver[31844]: segfault at 0 ip (null) sp b5d66f4c error 4 in
owserver[8048000+6000]
tail of owserver -uall -uscan --foreground
Yep, your file...Our python guys aren't as good as you :)
--Jim
On Tue, Aug 10, 2010 at 2:24 PM, Joshua J. Kugler jos...@azariah.com wrote:
On Tuesday 10 August 2010, Joshua J. Kugler elucidated thus:
On Tuesday 10 August 2010, Jim Kusznir elucidated thus:
The attached patch file did the
On Wednesday 11 August 2010, Jim Kusznir elucidated thus:
Yep, your file...
Caught that...and felt silly when I did.
Our python guys aren't as good as you :)
Thanks for the compliment, but quite frankly I don't consider myself a
Python guru. This time around the ability to fix it so easily
