> On 22 Jul 2017, at 12:24, Dr. Trigon <dr.tri...@surfeu.ch> wrote:
>
> I don't want to run another instance of owfs on those devices as they should
> act as master and not owfs servers.
What you need is an IP protocol that allows you to access a remote 1-wire
network: owserver (the protocol) was designed exactly to address this problem,
see http://owfs.org/index.php?page=owserver-protocol
Documentation and terminology are … a little hard to understand, so let my try
to explain it here.
First one should understand that “owserver” has many meanings:
- owserver-protocol: the TCP messaging protocol used by OWFS components to
communicate over IP
- owserver-server: an agent that plays the server role in an owserver-protocol
message exchange
- owserver-client: an agent that plays the client side in the owserver-protocol
- owserver-daemon: the program, which is the main OWFS owserver-server, but
that can act also as an owserver-client.
The OWFS way to solve your problem is that on each remote 1-wire network you
should have an owserver-daemon running (Please note: only the owserver-daemon,
not the full stack of owhttp, owftp, owfs, etc.) Each owserver-daemon controls
one or more 1-wire masters, and acts as an owserver-server, over a common IP
network, say a WiFi LAN. Owserver-clients can query over IP the various
owserver-daemons (acting as owserver-servers) about the remote 1-wire networks
they are controlling.
To make things a little bit more complicated, you should know that an
owserver-daemon can be configured to be an owserver-client of a remote
owserver-server: this means that the owserver-daemon is now able to present the
remote 1-wire devices as local ones… Please see
http://owfs.org/index.php?page=loop-suppression for different owserver-server
network topologies examples and the built-in loop suppression mechanism.
This is what OWFS has to offer: if you keep it simple (owserver-daemons acting
only as owserver-servers) it is quite simple to configure and manage. Of course
owserver-clients should know which owserver-server query. However if you
prefer, you can merge all remote 1-wire networks into a single “virtual” 1-wire
network, by using the owserver-daemon client capabilities, so that your to your
clients all 1-wire devices are presented as if they were on a single 1-wire
network.
Of course you can invent your own 1-wire-over-IP protocol and implement it in
the micro-controller of your choice, or even emulate the LINK protocol. But it
is much, much more complicated that having multiple owserver-daemons running on
your network.
Hope my explanation was at least understandable.
Bye
Stefano
---
BTW the Yún is a 65€ device in which you have two parallel environments talking
to each other: Arduino and Linux (Linino OS, based on OpenWRT). Linux specs are
really minimal: 64MB DDR2 RAM, 400MHz clock speed.
On the contrary the Pi Zero W is a 10€ device, which runs a full-fledged Linux
(or windows 10, if you prefer) with 1GB Ram, running at 1GHz.
Spending 55€ just for having an Arduino bit-banging the 1-wire protocol makes
no sense to me.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
