Hi Daniel!
Is this not a requirement of the routing?
Did you have a look at the IEEE 802.15.4 specification? It's assumed to have
a so called PAN coordinator that forces the network to a star topology. It's
extendable to a tree of stars, but still you need a PAN coordinator in every
region.
On May 11, 2015 3:12 PM, Daniel Krebs m...@daniel-krebs.net wrote:
Hi Joakim,
+1 We use mostly Contiki-based applications presently and it would be
a big improvement if it was possible to get ContikiMAC duty cycling
working in RIOT as well.
Who is we if I may ask? Just curious.
Sorry
Hi Daniel!
As it seems that there are only 2 MAC implementations for now [1,2], both
not what I'm searching for and also not merged, I decided to try this on my
own.
There's a third inside the OpenWSN stack using the TSCH (Time Slotted Channel
Hopping) as specified in the IEEE 802.15.4e
On May 12, 2015, at 11:00 AM 5/12/15, Martine Lenders
authmille...@gmail.com wrote:
Hi,
Am 12.05.2015 08:08 schrieb Oleg Hahm oliver.h...@inria.fr:
Hi Daniel!
Is this not a requirement of the routing?
Did you have a look at the IEEE 802.15.4 specification? It's assumed to
Hi Emmanuel,
One question: do you expect that network membership is rather dynamic,
or rather static? (i.e. do nodes come and go due to mobility for
example, or due to really long sleeping periods).
Depending on the answer to this question, some mechanisms may be more
applicable than
Hi Oleg,
PAN coordinators are only required for the beacon enabled mode in IEEE
802.15.4. 6LoWPAN, for instance, does not require this mode (I'm not even sure
if it is supported by the spec) and thus, there is no need for a PAN
coordinator or star topology.
That's unfortunately not the case.
Hi Daniel!
PAN coordinators are only required for the beacon enabled mode in IEEE
802.15.4. 6LoWPAN, for instance, does not require this mode (I'm not even
sure
if it is supported by the spec) and thus, there is no need for a PAN
coordinator or star topology.
That's unfortunately not the
Hi Oleg again,
There's a third inside the OpenWSN stack using the TSCH (Time Slotted
Channel Hopping) as specified in the IEEE 802.15.4e amendment. I'm
currently spending some time to see how it could be used separately
from the remaining OpenWSN stack, but don't expect any results before
On Mon, May 11, 2015 at 11:37 AM, Daniel Krebs m...@daniel-krebs.net wrote:
Hello RIOTers,
I want to use RIOT for a low-power 802.15.4 network project. Having a bit
familiarized with RIOT and my samr21-xpro boards now I want to tackle my
next milestone, i.e. I need a MAC protocol that fits my
Hi Joakim,
+1 We use mostly Contiki-based applications presently and it would be
a big improvement if it was possible to get ContikiMAC duty cycling
working in RIOT as well.
Who is we if I may ask? Just curious.
# Requirements
* Mesh topology = no single-point-of-failure
Is this not a
Hi Daniel,
I want to use RIOT for a low-power 802.15.4 network project. Having a
bit familiarized with RIOT and my samr21-xpro boards now I want to
tackle my next milestone, i.e. I need a MAC protocol that fits my
requirements (see below).
As it seems that there are only 2 MAC
Hi Jonas,
Better don´t look at [2] for now ;). Currently that PR is based on a
deprecated proposal that does not poperly use the netdev interface. I
hope I will have time for an update of this PR this week. Even if that
is not what you are searching for, maybe it could be used to make this
a
12 matches
Mail list logo
