Zigbee Wireless Networking Deciding on Zig Bee Speaker

Zigbee Wireless Networking - Deciding on Zig. Bee Speaker: Li-Wen Chen Advisor: Quincy Wu 2009/11/17 1

Outline l Introduction l 2. 1 Deciding on the Right Technology ¡ 2. 1. 1 Wired Versus Wireless ¡ 2. 1. 2 Other Wireless Technologies ¡ 2. 1. 3 Other Software Protocols on 802. 15. 4 Radios l 2. 2 Deciding on a Zig. Bee Solution l 2. 3 Zig. Bee Modules l 2. 4 A Zig. Bee Checklist 2

Introduction l Zonal Intercommunication Globalstandard, where Battery life was long, which was Economical to deploy, and which exhibited Efficient use of resources. l Reliable l Secure 3

2. 1. 1 Wired Versus Wireless l Wires need connectors. l Wireless has the interference problems. ¡ Zig. Bee turns what is essentially unreliable into a very reliable network. mesh networking l per-hop l end-to-end retries l acknowledgments l l Wired solutions can be more expensive per foot. 4

2. 1. 2 Other Wireless Technologies l MAC and PHY ← 802. 15. 4 ← Zig. Bee ¡ Zig. Bee is well-targeted at the wireless sensor and control network space. ¡ 802. 15. 4 is not the only radio which targets this space. ¡ Zig. Bee is not the only networking protocol which runs on the 802. 15 MAC and PHY. 5

Non-Zig. Bee 802. 15. 4 radios l 2. 4 GHz (ISM band), 250 kbps ¡ The data rate is sufficient for the Zig. Bee protocol. ¡ Products can interoperate worldwide in this RF space. l 900 MHz, 40 kbps l 868 MHz, 20 kbps 6

Wireless USB generally focuses on the PC peripherals, but could be adapted to the sensor and control space l For example, Cypress CYWUSB 6934 l Advantage l ¡ ¡ l Disadvantage ¡ ¡ l inexpensive great on batteries is not meant to function on a scale as large as Zig. Bee can doesn’t have the security based on Ultra Wideband (UWB) ¡ ¡ 480 Mbps data rate, two meters (about 6. 6 feet) lowered to 110 Mbps, up to 10 meters (or about 30 feet) 7

Wi. Fi™ also starting to see more use in sensor and control networks l a bit more expensive than Zig. Bee l ¡ l can mesh like Zig. Bee ¡ l typically requiring a larger CPU to run the full protocol but there are no interoperable standards for meshing Wi. Fi is not as good with batteries ¡ using up batteries in hours, rather than the months to years of Zig. Bee, but not all control networks require batteries. 8

Bluetooth™ used in headsets and cell phones everywhere l very secure l is relatively inexpensive l does not have the battery life of a Zig. Bee device l ¡ l Think of Bluetooth battery life as days, not the months to years like Zig. Bee. doesn’t scale well ¡ is typically limited to networks of seven devices or less, whereas Zig. Bee networks can contain thousands of devices 9

Wibree l falls under the Bluetooth Special Interest Group l aimed at watches and body sensors l very, very low power l limited in the number of nodes in a network l At the time of this writing, Wibree was not in production, but still in the specification stage. 10

Z-Wave aimed specifically at the home automation space l not a standard l ¡ ¡ Zensys is the only manufacturer of Z-Wave. used by some of the large home automation manufacturers, including l l Danfoss Leviton Universal Electronics Zensys has formed a group called the Z-Wave Alliance, and regularly releases white papers promoting Z-Wave over Zig. Bee. 11

Proprietary radios l is still the norm today l used to be the case in operating systems, too l are the primary competitor of Zig. Bee today l The biggest issue with the proprietary radios is the lack of a protocol. 12

2. 1. 3 Other Software Protocols on 802. 15. 4 Radios l Zig. Bee is the primary networking protocol based on 802. 15. 4 radios, but many other protocols are also commercially available. 13

802. 15. 4 MAC only point-to-point or a star network l doesn’t have l ¡ ¡ ¡ l The MAC uses ¡ ¡ ¡ l device service discovery interoperable applications like Zig. Bee the same per-hop retry mechanism that Zig. Bee uses the same network associate commands the same sleepy end-device polling commands What the MAC-only solution is missing is ¡ ¡ ¡ the application-level compatibility the higher reliability multi-hop nature of mesh networking. 14

Simplici. TI™ l Texas Instruments protocol l point-to-point l extremely small (4 K flash) l extremely simple l only 6 API calls 15

Synkro l originally by Freescale Semiconductor l point-to-point, not meshing l offers a form of frequency agility to avoid potential interference problems 16

Mi. Wi l by Micro. Chip l peer-to-peer l mesh l specifically targeted at the Microchip MRF 24 J 40 radio l has no cost associated with it if used with the Micro. Chip solutions 17

Pop. Net™ by San Juan Software l a small-footprint full-mesh solution that could be considered “Zig. Bee Lite” l Like Zig. Bee, Pop. Net supports l ¡ ¡ ¡ l broadcasting unicasting mesh route discovery Unlike Zig. Bee, Pop. Net fits into 16 K of flash and does not require Zig. Bee certification. 18

Tiny. OS la mesh networking technology written in a language called Nes. C. ¡ This C-like language allows sensors to be treated as objects. l Tiny. OS was even adopted by one of the Zig. Bee stack vendors, Mesh. Netics, as the foundation for their Zig. Bee solution. 19

6 Lo. WPAN l standardized by IETF. org l an 802. 15. 4 networking protocol that looks similar to IPv 6 l Companies such as Arch. Rock are promoting this emerging standard for interfacing sensors to the World Wide Web. 20

2. 2 Deciding on a Zig. Bee Solution l Carefully consider all aspects of your design when selecting hardware. l See http: //www. zigbee. org for a complete list of Zig. Bee silicon and solution providers. 21

Is the Zig. Bee platform certified? la platform called by the Zig. Bee Alliance ¡a combination of the radio ¡ MCU ¡ Zig. Bee stack software l The platform must be certified ¡ if your product will interact with products from other companies. l. A non-certified stack may not work with other Zig. Bee stacks. 22

Will the product use an integrated MCU/radio or a stand-alone radio? l an integrated MCU and radio ¡ very cost-effective ¡ allowing both the Zig. Bee networking protocol l the application l to reside in a single chip, 8 -bit solution 23

l The single chip solution contains everything required for the application except a power supply and sensors 24

la stand-alone 802. 15. 4 radio with some host CPU ¡ the main question is whether Zig. Bee will need to run on that host processor l Most Zig. Bee implementations run really well on the integrated MCU/radio solutions, but may not be portable enough to run on another MCU. ¡ treat the Zig. Bee integrated chip as a communication “ module ” 25

l the single chip solution ¡ the Zig. Bee stack ¡ a small serial “gateway” application l the host processor ¡ the l main application, talking to Zig. Bee through a UART 26

Does the platform have enough memory for the application? l Zig. Bee is quite large. l When evaluating vendors ¡ do a code-size estimate ¡ build the Home Automation On/Off Light application for a Zig. Bee Router device. ¡ check in the. map file l Feel free to call the vendor’s support line, or to check out their online help. 27

Does the price-point make sense for the product? l Consider the following production costs: ¡ ¡ ¡ What external components are required? Can the board layout be two-layer, or must it be four-layer? What quantity will I ship? This can greatly affect price per unit. Do the cost of the tools make a significant difference? How solid is the software? Will it require significant development or debugging effort? Create a bill-of-materials (BOM), and then price them out with one or more distributors. l Consider the cost of l ¡ ¡ manufacturing the software 28

Is the part low-power enough for the power supply? l When evaluating low power for a particular radio or single-chip solution, consider both the ¡ wake power ¡ sleep power l If a node only wakes for a few milliseconds every few minutes, then power consumption while sleeping is everything. 29

Other questions when evaluating l l l l What voltage range does the part support? Does the part support all the required physical characteristics? Are you familiar with the silicon vendor? How good is the stack? What tools are available to support compiling and debugging? What reference designs are available? What is the availability of the radio? Is an alternate supplier a requirement? 30

2. 3 Zig. Bee Modules A Zig. Bee module is a board that is manufactured “application-ready. ” l be government-certified l ¡ l including CE Marking in Europe, IC in Canada, and FCC in the U. S. have various I/O pins ¡ ¡ binary GPIOs analog-to-digital pins be battery-operated l Modules save you money and time, and until your production reaches the millions of units, there is rarely a good reason to build your own board l 31

32

2. 4 A Zig. Bee Checklist l The list of things to remember when building a Zig. Bee application ¡ Protocol Selection ¡ Hardware Selection ¡ Stack Selection ¡ Application Development ¡ Manufacturing ¡ Deployment 33

Thank you! 34