Hi Joakim! > What is the current state of radio duty cycling in RIOT? > I know that radio drivers implement on and off functions for the chip, but > how do we make the best use of them? > In order to reduce power consumption it will be necessary to duty cycle > the radio
I would agree with Martine: usually, duty cycling should be rather part of the
MAC
layer than of the driver. However, embedded transceiver devices usually are
designed for one particular MAC layer and splitting this up in a sensible way
is not always easy/feasible.
Do you have any concrete ideas of functionality for a generic radio
transceiver the driver (netdev) API should provide?
> For comparison, in
> Contiki there are multiple RDC drivers that can be switched between at
> compile time, the most well-known is ContikiMAC [1]. Something similar
> would be very useful in battery powered scenarios for RIOT.
There's definitely a need for generic MAC layer solutions in RIOT, besides the
specific solutions like CSMA in the cc110x driver or TiSCH for 802.15.4e as
part of the OpenWSN stack. As far as I know, at least two people are currently
working on MAC layer implementations for RIOT. I will also take a look into
this topic with the goal to use only the MAC layer part of the OpenWSN stack
as a standalone module in RIOt.
Cheers,
Oleg
--
panic("do_trap: can't hit this");
linux-2.6.6/arch/i386/mm/extable.c
pgppiqJ16f3Gu.pgp
Description: PGP signature
_______________________________________________ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
