FREE Texas Instruments and Farnell Webinar - Introduction to ZigBee

Hi MC,

This webinar wasnt recorded, but you can find the slides from the presentation here: http://www.element14.com/community/docs/DOC-34540/l/webinar-supporting-slides-texas-instruments-and-farnell-webinar--introduction-to-zigbee

thanks

James

Hello.

I used certified modules IEEE 802.15.4 (according to FCC/CE radio compliance) and certified ZigBee software protocol stack (according to ZigBee protocol documentation) (http://www.atmel.com/zigbit).

BUT this solution did not solve ZigBee Alliance $$$ problem. I should pay for commercial deployment (even without certification) because license agreement on ZigBee documentation and to be compliant (even without certification) to unique "Application profile identifier"/"Device Identifier".

Try to imagine: I did not download or read any ZigBee documentation (due to documentation license agreement), I used module with certified stack for free to use, I used "Sony's random generator + 0x0100" to determine "Application profile identifier" to 0x0104 (and other random values), I created large sensor network (few kmsq). Do you thing that your smart-home will work without problems within this area ?

I thing that ZigBee software stack is only for ZigBee alliance defined patterns and for large enterprise developers and not for other use. The ZigBee alliance developed "standardized" but "closed to public" protocol like other (EIB, KNX ...).

I was not able to attend seminar (wrong time). Was the seminar recorded ?

Thanks, M.C>

Hello.

I evaluated ZigBee protocol stack (and modules) but I had to cancel project on ZigBee.
There is "hidden" cost in ZigBee protocol (sw stack over IEEE 802.15.4) ! You MUST pay zigbee.org alliance membership (>=$3500) to use the protocol (commercially and even non-commercially (due to "Application profile identifier" request)) and for each certified device ($500-$1000).

ZigBee protocol is not compatible with GPL (http://en.wikipedia.org/wiki/ZigBee#Licensing). You should use proprietary licenses, BSD ... and other compatible licenses to "extra payment".

ZigBee protocol has special "feature". If you create application descriptor you MUST use UNIQUE "Application profile identifier" and "Device Identifier Field" that are both only 16-bit !!! in length (obtained ZigBee Alliance AFTER membership fee). I did not found any "free for local use" identifiers and/or prefixes in specs. This is worse than internet number assignment (16bit - "port assignment" by IANA in TCP/UDP, 32bit - "program ID" SUNRPC/ONC, 64bit/EUI64 - "program ID" in DCE ...).

My questions:

How can I develop "economically" small commercial application (~20 zigbee units but not zigbee standard "profile") with zigbee stack ?

Now I am evaluating other sw stack over IEEE 802.15.4 (tinyos and contiki). Is this right solution ?

Thanks for answers, mcerveny

Want to know more about Wireless and Zigbee from TI  ? 

register to the webinar