[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] Anyone used Atmel's 802.15.4 stack (or OpenMac) ?

From: Joerg Wunsch
Subject: Re: [avr-gcc-list] Anyone used Atmel's 802.15.4 stack (or OpenMac) ?
Date: Sat, 28 Jul 2007 23:43:08 +0200 (MET DST)

"Robert Rozman" <address@hidden> wrote:

> - do you perhaps have published some more info about your work ?

What we published is what you can find as the current Atmel MAC. ;-)

> - did you find any bugs ?

Sure... all important ones have been fixed in the release.  But you
know, there's always one more bug.  Remember there's an official Atmel
helpline (avr at atmel com).

> - any other general experiences about stack, used HW etc...

These stacks tend to be quite resource intensive, but you've got an
ATmega1281 controller, that's plenty.

With Atmel being a chip manufacturer and Meshnetics being a software
vendor (who even does have a working ZigBee stack, which sits on top
of 802.15.4), the Meshnetics stack might be the better one.

> - are there any extensions being published and made to more complete
> wireless nodes (ADCs, switches, sensors, etc..) ?

Not that I know of.  But seriously, connecting a switch or an ADC to
an AVR is a few lines of code only, you should be able to find plenty
of examples for that.

> - also curious how to minimize energy consumption of nodes (I'm
> using atmega1281V)....

You should get acquainted with the details of IEEE 802.15.4 networks
in general.  Energy consumption is highly dependant on your usage
profile.  If you're using the Atmel MAC, make sure you get the most
recent version (I think it's 1.6) because previous versions didn't
power-down the transceiver while idle.  That has now been implemented.
(IMHO the Meshnetics stack can do it, but I never looked at their
opensource offering.)

cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]