Atmel Lightweight Mesh wireless stack

[ataradov]

Disclaimer: I'm the author of the stack.

Atmel Lightweight Mesh software stack is an easy to use proprietary low power wireless mesh network protocol. It has been designed to address the needs of a wide range of wireless connectivity applications.

The Lightweight Mesh is designed to work with all Atmel IEEE 802.15.4 transceivers and SoCs.

The current implementation of the Lightweight Mesh protocol has the following features:

• Simplicity of configuration and use
• Up to 65535 nodes in one network (theoretical limit)
• Up to 65535 separate PANs on one channel
• Up to 15 independent application endpoints
• No dedicated node is required to start a network
• No periodic service traffic occupying bandwidth
• Two distinct types of nodes: routing and non-routing
• Once powered on node is ready to send and receive data; no special joining procedure is required
• Route discovery happens automatically if route to the destination is not known
• No child-parent relationship between the nodes
• Routing table is updated automatically based on the data from the received and transmitted frames
• Duplicate frames (broadcast or multipath unicast) are rejected
• Optional AODV route discovery
• Multicast messaging
• Small footprint (less than 8kB of Flash and 4kB of RAM for a typical application)

Stack is open-source, but license limits its use only to Atmel MCUs and radios.

Software can be downloaded here: http://www.atmel.com/tools/lightweight_mesh.aspx

I'm available to answer any questions you might have and provide as much support as I can.

[Len]

Stack is open-source, but license limits its use only to Atmel MCUs and radios.

That's not open-source. http://opensource.org/osd

[ataradov]

Source code is available and open as in "everyone can download and look at it". Simply because some other entity has redefined meaning of "open-source" it does not mean that it can not be used otherwise.

As far as FSF is concerned, "open-source" means just open, so they've invented "free".

PS: Anyway, there is not much I can do about it; I'd prefer it to be completely free.

[Len]

I'm afraid you're the one who's re-defining "open source," according to the FSF as well as the OSI and everyone I've ever heard talk about it.

[free_electron]

Stop jammering about open sauce.
You get all the sourcecode for the stack. No secrets. It will only run on atmel since it is written for their rf chips. Every rf chip from different vendors works differently. Registers are different, initialisarion is different, usage is different.

This happens to be a wad of sourcecode that implements an easy to use mesh network written for a particular set of rf chips.

I say it's great ! A bunch of work done. We can use it without having to pay for it. I call that 'free'.

It's the perpetual whining of the FSF and other open-sores purists that makes people eschew them.

[Rasz]

its open source, but not open source license, two different things that sound almost the same
Its typical "you can use it on our product only, no patches, no sharing, no distributing". Same deal as with Microchip USB stack

[cthree]

Hellooo Alex! Great to see you on the EEVBLOG forum!

He knows his shit as anyone who has spent time on the AVRfreaks wireless forum will attest.

BitCloud is a good ZigBee stack. I'm fine with picking a wireless SoC and using the free software they provide to do the mundane task of moving a bit from here to there. If you want to switch platforms to say Ti, then use their stack instead. It is also free but requires IAR which is obscenely expensive. The last time I used it, the BitCloud stack compiled with AVRGCC.

I haven't used your Atmel lightweight mesh stack, maybe someday.

If anyone out there wants to write a GNU/MIT/APACHE licensed mesh network stack that works with any transceiver/microcontroller pair or SoC, go for it! I will applaud your efforts.