On 05.09.2018 11:00, Jan Kandziora wrote:
> Yes, exactly. But that's what a clever designed library can assist the
> application programmer. By requiring him to think about the logical
> abstraction of a whole device first, not just a Onewire slave.
Well, I can't help with "requiring".
But once
Am 05.09.2018 um 10:08 schrieb Matthias Urlichs via Owfs-developers:
>
>> The DS2409 is already transparently supported by owlib.
> Is it?
>
> Last time I checked, slaves behind a DS2409 or two do not show up
> in "owdir /" or "owdir /bus.0" or "owdir /alarm", they do not
> notice when I set
On 05.09.2018 07:45, Jan Kandziora wrote:
> So my advice from pratice is basing all the automatical mechanisms on
> a logical abstraction of a whole peripheral, with the Onewire stuff
> being only a part of a bigger picture.
My main goal with this library is that the instance representing a slave
Am 05.09.2018 um 05:20 schrieb Matthias Urlichs via Owfs-developers:
> Hi,
>
> I'm writing a new high-level asynchronous Python library to talk
> to owserver.
>
> It features multiple persistent server connections, transparent
> support for DS2409 couplers, automatic retries when he server is
>
Hi,
I'm writing a new high-level asynchronous Python library to talk to
owserver.
It features multiple persistent server connections, transparent support
for DS2409 couplers, automatic retries when he server is busy or the
connection breaks, object-oriented design, auto-generating accessor
