From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Line of Nodes
Date: Wed, 12 Mar 2014 11:36:16 +0100 [thread overview]
Message-ID: <201403121136.16430.sw@simonwunderlich.de> (raw)
In-Reply-To: <20140310212525.GU24339@pengutronix.de>
Hey Robert,
> Hi,
>
> I have a little bit strange usecase for a wireless mesh network, and I'm
> wondering if B.A.T.M.A.N could be a good choice: my network stations,
> which are part of an industrial application, are located in a line:
>
> Gateway - A1 - A2 - A3 - A4 - A5 - ... - A120
>
> Any station generates data and wants to transmit it to the gateway, with
> the smallest possible latency. The distance of the stations is pretty
> small: about 3...4 m.
>
> It might happen that someone re-arranges the stations:
>
> Gateway - A9 - A17 - A1 - A47 - A9 - ... - A6
>
> but the topology stays the same (a line).
>
> It is allowed that one station sends its data to the farest reachable
> hop, so i.e. for my first example, if A5 wants to send data and is able
> to reach A2, it could directly do so.
>
> - What do you think, could B.A.T.M.A.N be a solution?
Yes, BATMAN could help in this situation - its better than doing it statically
at least, since batman can decide how many intermediate hops to skip.
> - Could the short distance be a problem?
well you have interference between the nodes and the typical throughput
limitations because of the half-duplex nature of WiFi. But if you take that
into consideration and don't expect the same throughput as on a single link,
3-4 meter should be fine.
It also depends on what kind of data you will send (many industrial
applications use broadcast, for example).
> - Is it possible to regulate the transmission power in order to avoid
> disturbance?
There are WiFi driver which allow that, yes. However I'd recommend to keep it
as it is and change the broadcast rate to something higher (e.g. 18M or more)
to force to only use good links, even if they are a little shorter.
Cheers,
Simon
next prev parent reply other threads:[~2014-03-12 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 21:25 [B.A.T.M.A.N.] Line of Nodes Robert Schwebel
2014-03-12 10:36 ` Simon Wunderlich [this message]
2014-03-12 12:53 ` Robert Schwebel
2014-03-12 13:51 ` Simon Wunderlich
2014-03-12 14:25 ` Robert Schwebel
2014-03-12 14:54 ` Andrew Lunn
2014-03-12 18:20 ` Robert Schwebel
2014-03-31 11:06 ` Bruno Antunes
2014-03-31 18:14 ` Robert Schwebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201403121136.16430.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox