<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.2" -->
<rss version="2.0">
	<channel>
		<title>802.15.4 Chip Comparison Sheet Update</title>
		<description>Comments for 802.15.4 Chip Comparison Sheet Update at http://freaklabs.org , comment 1 to 8 out of 8 comments</description>
		<link>http://freaklabs.org</link>
		<lastBuildDate>Wed, 08 Sep 2010 12:51:26 +0100</lastBuildDate>
		<generator>FeedCreator 1.7.2</generator>
		<item>
			<title>...</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-858</link>
			<description>I'm not sure how meshing works with Zigbit but as a rule, meshing is pretty complex. It depends on how their software is written. The difficult thing is knowing the node address of the node you're targeting. If you have access to the address of the node, then theoretically, you should just be able to generate a frame to that node and the network layer should take care of the transport. In reality, I'm not sure you can do it simply with AT commands. I believe XBee requires using their API mode to implement a mesh network rather than the transparent (aka serial) mode. I suspect the same is true of Zigbit. But when in doubt, RTFM... - Akiba</description>
			<pubDate>Wed, 17 Mar 2010 01:13:24 +0100</pubDate>
		</item>
		<item>
			<title>ZigBit AMP MeshNetics....</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-857</link>
			<description>Hey Akiba,

Thanks for all the tutorials. i am actually working on the ZigBit AMP by meshnetics. I have to realise a Mesh Network using these modules of ZigBee. is it possible to do that just with the AT-Commands of SerialNet ?? Second Can you plz provides with some indications or hte differents phases to create a Mesh network with ZigBee??

Thanks, - Ramy</description>
			<pubDate>Wed, 17 Mar 2010 00:38:31 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-844</link>
			<description>Thanks for the suggestion. Actually wiki may be a better format since the list seems to be growing. The unfortunate side effect is that wikis are often gamed by manufacturers, but I do like the idea of having a list thats maintained by the community. Especially if you start including non-802.15.4 chips, of which there seem to be quite a few. One of the issues I run into is how to limit the number of fields to compare so the chart is still readable. Wish I had better DB skills.  - Akiba</description>
			<pubDate>Fri, 05 Mar 2010 09:37:25 +0100</pubDate>
		</item>
		<item>
			<title>Chip comparison as a wiki?</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-843</link>
			<description>Hi Akiba,

I see you mention you would like to add more RF chips to the comparison charts, i.e. also non-802.15.4 chips. I agree that it would be interesting.

How about setting it all up in wiki, where you would also get help from your readers?

I believe there is a somewhat comparison list on Wikipedia, but last time I checked it was not kept up to date: http://en.wikipedia.org/wiki/Comparison_of_802.15.4_radio_modules
Whether it's best to consolidate into Wikipedia or put it somewhere else I don't know. As most of your readers are motivated engineers we probably would want to add a bunch of specs up there, probably more than what Wikipedia admins will accept in their articles (I've seen them sometimes complain on articles becoming too technical).

Anyway, 'twas just an idea :-) - aevin</description>
			<pubDate>Fri, 05 Mar 2010 09:24:32 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-840</link>
			<description>It really depends on the application. If you are creating a device that will be a Zigbee or 6LoWPAN router than I'd recommend a larger device for development. The Ember EM35x is nice because its based on ARM Cortex M3 which has good open source tool support. I also think the ATMega128RFA1 is quite interesting because I'm personally a fan of AVRs. On the flip side, if you're going to do something like an end device and need it small, you can look into one of the TI chips like the CC253x w/32k RAM. Personally I prefer to use a standalone 802.15.4 transceiver and just swap around the MCUs controlling it to fit the application. In large vols, 802.15.4 radios are either close to or below $1. - Akiba</description>
			<pubDate>Thu, 04 Mar 2010 08:49:04 +0100</pubDate>
		</item>
		<item>
			<title>Chip choice</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-839</link>
			<description>Hi,

Nice work you've done here. I like the Jennic way of doing things, where the stack can be either 6LowPAN or Zigbee since everything is in ROM.
What are your advices on the best(s) chip(s) to base a development of a sensor product using 802.15.4/Zigbee on 2.4GHz ?

Thanks,

N.

 - noblomov</description>
			<pubDate>Thu, 04 Mar 2010 08:31:28 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-838</link>
			<description>Truthfully, they're probably all the same chip (within each family). It's just some marketing guys idea to give them each different numbers to make it look like there's more products than they're really are. It's quite common. - Akiba</description>
			<pubDate>Thu, 04 Mar 2010 00:10:46 +0100</pubDate>
		</item>
		<item>
			<title>MC13xx1/2/3 differencies</title>
			<link>http://freaklabs.org/index.php/Blog/Zigbee/802.15.4-Chip-Comparison-Sheet-Updated.html#comment-837</link>
			<description>BTW: Do you understand _real_ differencies between MC13201/2/3 chips (and MC13191/2/3)? I couldn't find any info over 'SMAC only/802.15.4-ready/ZigBee-ready'. - Dmitry Eremin-Solenikov</description>
			<pubDate>Wed, 03 Mar 2010 23:58:11 +0100</pubDate>
		</item>
	</channel>
</rss>
