Introduction to Ti wireless solution: ZigBee


Published on

Represent Texas Instrument to design the syllabus and conduct a 3 hours workshop for Republic Polytechnic on ZigBee and MSP430 in Singapore.

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • There is an alliance that was formed way back in 2003, 2004. It’s around 200-250 companies came together and they decided that they want a standard for wireless communication. Specifically they don’t want to focus on bluetooth, which is point to point with higher data rate. They want to focus focus on markets where data gets send across buildings and large area, potentially traversing multiple hops. AND everything needs to be really low power. So zigbee actually defines a mesh network protocol between devices out in the field. It’s a lot more than that, it’s not just a mesh network protocol. But the idea being that it’s not just a point to point protocol market whereas one device sending data to another device. Or streaming audios or videos. It’s is more suitable for sensor, monitoring, control type applications AND low power. Battery operated devices.
  • It is important to cover the alternatives to ZigBee because in that sense, it gives you a better idea of what kind of application suits ZigBee and what not. There are some miscommunication going on in the field where, people heard zigbee and zigbee is the end-all-be-all solution. But in a lot of places mention from previous slide such as, streaming audios/video, point to point application. You don’t need the full comprehensive zigbee mesh network protocol. In those scenario, for example you just have one device reporting in, through 5 feet. Maybe those are more suitable to use 802.15MAC Layer, it’s not full zigbee. It’s just the physical and the mac component of it. So it can gets you point to point or point to multi-point communication. One of the key major buzz word for zigbee is the interoperability. That’s to say, I want my device to work with some other vendors device without us collaborating on the side. Because ZigBee is a global standard protocol, our devices can work together. And the second big buzz word is the Mesh Network. So being able to get a large network devices with redundancy in the data path from the sensor to a sink, Or point where we’re sending out data, which is usually a pc or a handheld.
  • I will mention some highlight of the cc2530…
  • 101dBm link budget: to maximize communication range, best in class selectivity to minimize the effect of interference sources. Flexible low-power modes: to maximize longevity of battery operated device.Powerful 5-channel DMA engine: IR generation circuitry: for remote control application Up to 256k of flash for those applications that requires a little more code space.
  • Introduction to Ti wireless solution: ZigBee

    1. 1. 1<br />ZigBee <br />Introduction to TI wireless solution<br />CC2530 ZigBee Network Processor Mini Kit<br />
    2. 2. 2<br />Agenda <br />Brief introduction on ZigBee and current wireless technologies <br />MSP430<br />CC2530 ZigBee Network Processor <br />IAR Embedded Workbench<br />Understanding CC2530ZNP Mini Kit demo code<br /><ul><li>Hardware Interface Example
    3. 3. Communication Example
    4. 4. Simple Project Example</li></li></ul><li>What is ZigBee?<br />3<br />
    5. 5. ZigBee Alliance<br />“The ZigBee Alliance is an association of companies working together to enable reliable, cost-effective, low-power, wirelessly networked monitoring and control products based on an open global standard”<br />Source: ZigBee Alliance homepage<br />Promoters of the ZigBee alliance are:<br />
    6. 6. What are the alternatives to ZigBee?<br />5<br />
    7. 7. Global Frequencies<br />
    8. 8. Technologies Summary<br />
    9. 9. Why Bluetooth®?<br />Wireless data, audio or voice <br />Replacement of serial cables<br />10-100m range personal ‘bubble’ (Personal Area Network)<br />Instant, secure, automatic connections<br />Low power consumption <br /> (AAA battery power source)<br />Good data rates (~2Mbps throughput) <br />Install base of 3 billion units<br />Why TI Bluetooth?<br />Best in-class RF performance (Transmit and Receive)<br />Dual-mode options with ANT & Bluetooth<br />Available with Wi-Fi<br />Highly integrated, fully certified module available to reduce cost and time to market<br />
    10. 10. Why ANT?<br />Ultra low power (ULP) enables coin cell operation for wireless sensors<br />Devices can operate for more than a year without recharging<br />Ideal for sports and fitness sensors, medical and healthcare devices<br />Established ANT+ interoperable ecosystem utilizing 2.4GHz for global deployment<br />Install base of over 13 million devices (Dec’10)<br />Why TI ANT?<br />TI offers single-mode and dual-mode solutions<br />Dual-mode is the first single-chip solution<br />Fully tested ANT ecosystem solution – for both sensor and mobile handheld devices<br />Best in class RF performance<br />Excellent coexistence with other 2.4GHz devices <br />Highly integrated, optimized hardware chipsets or fully certified modules to reduce cost, size and time to market<br />
    11. 11. Why Bluetooth Low Energy (BLE)?<br />Ultra-low power communication<br />Fraction of the power of Bluetooth<br />Enables sensor applications to operate on a coin cell for >1 year<br />Consumer medical, sports and wellness applications, mobile accessories<br />Why TI BLE?<br />TI provides both single mode and dual mode Bluetooth low energy solutions<br />Both sides of the link to create a fully tested Bluetooth low energy ecosystem - from smart sensors to smart phones<br />Leading RF performance up to +97dB output power<br />Excellent coexistence with other 2.4GHz devices <br />System on a chip integrated solution and modules available<br />
    12. 12. Why Wi-Fi?<br />Connect electronic devices to each other, to the Internet, and to wired networks – quickly and securely<br />Most prominent wireless connectivity technology for computers and internet <br />Real-world performance similar to wired networks<br />High data rates (>20Mbps throughput)<br />Over 2.5B Wi-Fi units deployed in the market today; ~1 billion units/year projected starting in 2011<br />Why TI Wi-Fi?<br />Wi-Fi + Bluetooth in a single-chip with best-in-class coexistence<br />Bring multi-radios to battery powered applications<br />Highly integrated, fully certified modules available to reduce cost and time to market<br />Platforms offered that integrate system hardware and software<br />
    13. 13. Why ZigBee?<br />Self healing (Mesh networks)<br />Operate on battery (many years on AA batteries) <br />Low node cost <br />Easy to deploy (low installation cost) <br />Support Large networks (hundreds of nodes)<br />Intended for monitoring & control applications<br />Standardized protocol (interoperability)<br />Why TI ZigBee?<br />With power amplifying support (cc2591) to boost the signal above 100m<br />One of the major promoter in the ZigBee alliance.<br />One of the early adopters with years of accumulated experience. <br />Wide variety of products compatible with ZigBee.<br />
    14. 14. Wireless Technologies Comparison<br />Range<br />Throughput<br />20 Mbps<br />Zigbee<br />WiFi<br /><2 Mbps<br />ANT<br />BLE/ANT<br />RF4CE<br />Zigbee<br />Sub-1GHz<br />2.4GHz<br />Bluetooth<br /><250 kbps<br />RF4CE<br />Technology<br />BLE<br />Sub-1GHz<br />Technology<br />Li-Ion<br />Typical Power Source Required<br />WiFi<br />AAA<br />Bluetooth<br />WiFi<br />2.4GHzProprietary<br />Bluetooth<br />Zigbee<br />RF4CE<br />Coin Cell<br />BLE/ANT<br />Sub-1GHz<br />2.4GHzProprietary<br />10,000<br />100<br />10<br />Range (m)<br />RFID<br />Technology<br />
    15. 15. Typical Decision Parameters<br />Highest Data Rate<br />WLAN (Video)<br />Bluetooth (Audio)<br />Zigbee/802.15.4<br />Highest Battery Life<br />Zigbee/802.15.4 (Alkaline/Li-Ion)<br />Bluetooth (Alkaline/Li-Ion)<br />WLAN/UWB (Line powered/Li-Ion)<br />Longest Range (Radio Only, not boosted)<br />WLAN<br />Zigbee802.15.4<br />Bluetooth <br />
    16. 16. Commercially deployed ZigBee<br />
    17. 17.<br />16<br />
    18. 18. 17<br />
    19. 19. 18<br />
    20. 20. 19<br />
    21. 21. MSP430 <br />20<br />
    22. 22. Ultra-Low-Power+ High Performance<br />Integration<br />• 14 to 113 pin devices<br />• 1-256kB Flash/ROM<br />• 10-/12-/16-bit ADC<br />• 12-bit D/A, LCD Drivers, RTC, DMA<br />• Comparators and Op Amps<br />• Supply Voltage Supervisor & BOR<br />• 16-bit and 8-bit timers; WDT<br />• I2C, SPI, UART/LIN, IrDA<br />• USB & RF<br />Performance<br /><ul><li>16-bit RISC CPU up to 25MHz
    23. 23. Industry leading code density
    24. 24. Flexible clock system
    25. 25. Single-cycle register operations
    26. 26. 16 GP 16-bit Registers
    27. 27. No accumulator bottleneck</li></ul>Low Power<br /><ul><li>Industry’s Lowest Power
    28. 28. Standby <1 μ A
    29. 29. Includes RTC and BOR
    30. 30. Active 160 μA/MIPS
    31. 31. Fast wake-up <1 μs
    32. 32. Internal voltage regulator
    33. 33. 4 Programmable voltage levels
    34. 34. <50 nA pin leakage</li></ul>Ease of Use<br /><ul><li>C friendly IDE and compiler
    35. 35. One programmer for all devices
    36. 36. Embedded emulation
    37. 37. Trace, single-stepping, in-system debug
    38. 38. Intelligent peripherals reduce overhead
    39. 39. DTC, DMA, Autoscanning A/D
    40. 40. Free & Low cost dev tools</li></li></ul><li>MSP430 Key Application Spaces<br />Medical and Industrial Metering<br />Sensoring<br />• Glucose and cholesterol meters, thermometer, EKG, heart rate monitor, pulsoximeters<br />• Voltage, current, temperature,pressure, pH meters<br />• Alarm system, smoke detector<br />• Home control and automation<br />• Wireless asset tracking<br />• Wireless sensors<br />• System supervisor<br />Utility Metering<br />Portable Consumer<br />• Cell phone, digital camera, MP3<br />• Fitness monitors and sensors<br />• Toothbrush, shaver<br />• Remote control<br />• Wireless keyboard and mouse<br />• Battery charging<br />• Energy<br />• Water<br />• Gas<br />• Automated Meter Reading (AMR)<br />• Advanced Metering Infrastructure<br />• Heat Cost Allocation<br />
    41. 41. Ultra-Low Power Is In Our DNA<br /><ul><li>Multiple operating modes</li></ul>0.1 µA power down<br />0.3 µA standby<br />160 µA / MIPS<br /><ul><li>Instant-on stable high-speed clock
    42. 42. 1.8 - 3.6V single-supply operation
    43. 43. Zero-power BOR
    44. 44. <50nA pin leakage
    45. 45. CPU that minimizes cycles per task
    46. 46. Low-power intelligent peripherals</li></ul>ADC that automatically transfers data<br />Timers that consume negligible power<br />100 nA analog comparators<br /><ul><li>Performance over required operating conditions</li></ul>MSP430 designed for ULP from ground up<br />Peripherals optimized to reduce power and minimize CPU usage<br />Intelligent, low power peripherals can operate independently of CPU and let the system stay in a lower power mode<br />
    47. 47. 16-bit Orthogonal RISC CPU<br />Efficient, ultra-low power CPU<br />C-compiler friendly<br />RISC architecture<br />27 core instructions<br />24 emulated instructions<br />7 addressing modes<br />Constant generator<br />Single-cycle register operations<br />Memory-to-memoryatomic addressing<br />Bit, byte and word processing<br />20-bit addressing on MSP430X for Flash >64KB<br />
    48. 48. Ultra-Low PowerActivity Profile<br />Extended Ultra-Low Power standby mode<br />Minimum active duty cycle<br />Interrupt driven performance on-demand<br />
    49. 49. MSP430 Low Power Modes<br />Off<br />All <br />Clocks Off<br />0.1µA<br />Active<br />DCO on<br />ACLK on<br />160µA<br />CPU Off<br />DCO on<br />ACLK on<br />45µA<br /><6µs<br />LPM0<br />LPM4<br /><ul><li>RAM/SFR retained</li></ul><1-6µs<br />LPM3<br /><ul><li>RTC function
    50. 50. LCD driver
    51. 51. RAM/SFR retained</li></ul>Stand-by<br />DCO off<br />ACLK on<br />1.0µA<br />Specific values vary by device<br />
    52. 52. 10-bit & 12-bit ADCs<br />200ksps+<br />Autoscan<br />SingleSequenceRepeat-singleRepeat-sequence <br />Int/ext ref<br />TA SOC triggers <br />Data Transfer Controller(DTC)<br />DMA Enabled<br />Fast Flexible 10- and 12-bit ADCs<br />DirectTransferController<br />DataTransferController<br />
    53. 53. 12-bit monotonic<br />8/12-bit voltage output<br />Programmable settlingtime versus power <br />Int/ext reference<br />Binary or 2’s compliment<br />Self-calibration<br />Group sync load<br />DMA enabled<br />DAC12<br />
    54. 54. ~100nA operation (Comp_B)<br />Hysteresis generator (B)<br />Input multiplexer<br />Reference generator<br />Low-pass filter<br />Battery detect<br />Interrupt source<br />Timer_A capture <br />Multiplexer short for sample-and-hold<br />Analog Comparators<br />
    55. 55. USCI: Serial Communication I/F<br />USCI_A<br />UART with IrDA/LIN support or SPI<br />Baud-rate generator with auto-baud rate detect<br />Double buffered TX/RX<br />USCI_B<br /><ul><li>I2C master/slave up to 400kHz or SPI
    56. 56. Bit clock generator
    57. 57. Double buffered TX/RXs</li></li></ul><li>Q&A<br />31<br />regarding to MSP430…<br />
    58. 58. 32<br />CC2530 ZigBee Network Processor<br />
    59. 59. Two approaches to use CC2530ZNP <br /><ul><li>Basic ZigBee networking examples
    60. 60. Educational tool
    61. 61. No ZigBee Profile support
    62. 62. Not for ZigBee certfied products
    63. 63. Easy portable to other TI platforms
    64. 64. Porting guide to Stellaris on Wiki page
    65. 65. ZigBee Profile Examples
    66. 66. Home Automation
    67. 67. Smart Energy
    68. 68. ZigBee Certification Ready
    69. 69. Includes Operating System Abstraction Layer
    70. 70. Easy to add real-time tasks</li></li></ul><li>34<br />CC2530 ZNP Mini Development Kit<br />The PCB included a CC2530 chip on the front and MSP430F2274 on the back.<br />The MSP430 is designed to handle the main task and CC2530 act as a slave to handle ZigBee network communication.<br />Peripherals<br />Accelerometer<br />Light Sensor<br />Voltage<br />3 ZigBee nodes<br />1 USB dongle and 2 battery nodes<br />
    71. 71. 35<br />Wireless Utility Meter<br />32, 64, 128 or 256KB<br />32KB<br />1KB<br />Low cost, Low power, SoC2.4GHz RF Transceiver<br />Low cost, Low powerMixed Signal Microcontroller<br />
    72. 72. 36<br />
    73. 73. Three paths to ZigBee<br />
    74. 74. 38<br />
    75. 75. 39<br />Flexible low-power modes<br />Powerful 5-channel DMA engine<br />Up to 256k of flash<br />IR generation circuitry <br />102 dBm link budget<br />
    76. 76. 40<br />ZigBee™ – Mesh Network Devices<br />
    77. 77. Coordinator <br />41<br />Starts a non-beaconed PAN<br />Allows other devices to join it<br />Buffers messages for sleeping End Devices<br />Provides binding and address-table services<br />Routes messages <br />Dynamically repair routing <br />Can have I/O capability <br />Manages security <br />Radio always on<br />
    78. 78. Router <br />Does not own or start PAN (Scans to find a network to join)<br />Allows other devices to join it after PAN has been started<br />Routes messages<br />Dynamically repairs routing <br />Buffers messages for sleeping End Devices <br />Support secure messaging <br />Can have I/O capability <br />Radio always on<br />42<br />
    79. 79. End Device <br />Does not:<br />Route messages<br />Own or start network<br />Allow other devices to join it<br />Scans to find a PAN to join<br />Polls parent to get messages (can be disabled) <br />Can be mobile <br />Radio/CPU can sleep <br />43<br />
    80. 80. ZigBee Mesh Routing <br />Mesh network routing employs AODV (Ad Hoc On Demand Distance Vector Routing)<br />Ad Hoc (Network is unknown at start-up)<br />On Demand (Determines the route to the destination only when needed)<br />Distance Vector (Only the final destination and the next hop are stored at each node. Relies on a distributed protocol to handle routing)<br />Self healing upon route failure <br />Reliable and robust. Failed router will reinitiate discovery and find an alternative path<br />44<br />
    81. 81. Automatic Rerouting<br />45<br />
    82. 82. ZigBee Device Software Architecture<br />46<br />
    83. 83. IEEE 802.15.4 and TI-MAC<br />47<br />Specifies the physical and MAC for low data-rate, wireless personal area networks<br />Intended to allow ultra low power consumption nodes<br />Physical limit of 250kb/s, but much lower in practice <br />Predefined modulation types and frequencies <br />TI 802.15.4 devices operate on 2.4GHz<br />ZigBee is built on top of this standard<br />
    84. 84. TI-MAC<br />48<br />Available platforms <br />CC2420/CC2 520 (2.4GHz) + MSP430<br />CC2430/1, CC2530 (2.4Ghz) SoC<br />Low power, low data rate (~100kb/s)<br />Peer to Peer or Star<br />Acknowledgements provided <br />No license, No fees<br />Requires unique IEEE address<br />
    85. 85. 49<br />Z-Stack<br />Low power, Low data rate (~100kb/s)<br />Self forming and repairing mesh networking<br />MAC and APP level acknowledgment<br />Interoperability possible <br /> membership required<br />Compliance testing required<br />Unique IEEE address required<br />
    86. 86. Software Stack Considerations<br />ZigBee<br />SimpliciTI<br />Proprietary<br />IEEE 802.15.4<br />RF4CE<br />Layer<br />Design Freedom<br />Design Freedom<br />Application<br />Design Freedom<br />Design Freedom<br />Design Freedom<br />Higher Layer Protocol<br />Z-Stack +<br />Simple API<br />Design Freedom<br />Remo TI<br />Design Freedom<br />Design Freedom<br />TI MAC<br />Lower Layer Protocol<br />SimpliciTI<br />Design Freedom<br />TI MAC<br />TI MAC<br />CC253x<br />CC243x<br />CC2480<br />Physical Layer<br />CC111x, CC251x,<br />CC243x, CC253x,<br />CC430,<br />MSP430+CC1101,<br />CC2500 or CC2520<br />all LPRF devices<br />CC253x<br />CC243x<br />MSP430+CC2520<br />CC253x<br />CC243x<br />2.4 GHz<br />RF Frequency<br />2.4 GHz<br />Sub 1 GHz<br />2.4 GHz<br />Sub 1 GHz<br />2.4 GHz<br />2.4 GHz<br />Solution<br />
    87. 87. ZigBee vs. SimpliciTi<br />51<br />
    88. 88. ZigBee Snapshot – Sept 2008<br />IEEE 802.15.4 – 2003 defines PHY/MAC<br />ZigBee 2006<br />Products shipping today<br />ZigBee 2007<br />Two stack profiles: ZigBee and ZigBee PRO<br />52<br />
    89. 89. ZigBee 2006<br />Extremely well tested by a variety of companies <br />Base of products and networks on market and in use today<br />Many certified stacks and silicon providers available <br />Simpler: Less code and overheard than 2007 or PRO<br />53<br />
    90. 90. ZigBee 2007 and ZigBee PRO<br />ZigBee 2007<br />Based on proven 2006 feature set plus frequency agility and optional fragmentation <br />Basic features require less memory & resources than PRO<br />ZigBee PRO<br />Enhanced features optimize performance and RAM utilization under select scenarios<br />Feature enhancements based on identified limitations of ZigBee 2006 for specific network deployment<br />Interoperability <br />PRO devices will operate as End Device on a ZigBee 06 or 07 network, and vice cersa<br />ZigBee 06 and 07 network seamlessly<br />54<br />
    91. 91. ZigBee 2007 Summary <br />ZigBee is useful …<br />In most topologies; including peer to peer or sensor reporting <br />ZigBee drawback include: <br />Limited address assignment capabilities in a mobile environment <br />Route establishment takes time and expends energy during route establishment in many source to coordinator scenario <br />55<br />
    92. 92. ZigBee PRO Summary <br />ZigBee PRO is useful in networks with:<br />Large deployments with high ratio of mobile devices <br />Many sensor nodes reporting to Coordinator<br />High Security requirements<br />ZigBee Pro drawbacks include: <br />Additional features increase the code size and complexity <br />Network will suffer reduced throughput due to communication overhead<br />Heavy burden on the Coordinator <br />Required Network Management becomes a point of Failure<br />56<br />
    93. 93. 57<br />Q&A<br />regarding to CC2530 (ZigBee)…<br />
    94. 94. 58<br />IAR Embedded Workbench for MSP430<br />Subhead text here<br />
    95. 95. 59<br />Debug using IAR<br />Launch IAR Embedded Workbench<br />Open ‘Hardware Interface Example.eww’ <br />C:Texas InstrumentsCC2530ZNP Mini KitZNP ExamplesIARHardware Interface Examples.eww<br />Set Button Blink – Debug to Active<br />Project > Download and Debug<br />Once enter debug mod, <br />Click F5 or Debug > Go<br />
    96. 96. Useful Information about IAR<br />60<br />In IAR, right click on the function and choose ‘Go to definition of xxx’ can find out the origin of the function.<br />
    97. 97. Useful Information about IAR<br />61<br />If devices got disconnected while still in use, make sure you choose ‘clean’ before debug to avoid unnecessary problem.<br />
    98. 98. 62<br />Understanding CC2530 ZNP Mini Kit demo code<br />Subhead text here<br />
    99. 99. 63<br />Introduction <br />The examples provided are designed to be small, easy to use building blocks of code which can be easily incorporated into your application. <br />The examples in this document are written for ease of use first, performance second. There is most likely a faster way to do everything, but we want to ensure that the examples are easy to understand.<br />The examples are grouped into three categories, organized for simple to complex:<br />Hardware Interface Example: exercising the basic hardware on the board; light sensor, accelerometer, UART, etc.<br />Communication Examples: sending/receiving packets between two CC2530ZNPs <br />Simple Applications Examples: simple examples of how to use the CC2530ZNP in an application<br />
    100. 100. 64<br />Button Blink <br />This is a simple example that just toggles the state of the LED when the button is pressed, and is a good first program to compile and load to ensure that you have configured the development environment correctly. <br />
    101. 101. 65<br />
    102. 102. 66<br />Hello World <br />The MSP430 hardware creates a virtual COM port to attach to the target board. This is useful for outputting debug information to see what is happening. <br />On the CC2530ZNP target board, the hardware UART is used as a debug console. For this example you’ll need a HyperTerminal.<br />The first step is to determine which COM port the target board is using. On windows XP, Click Start and then Run. Type in, ‘devmgmt.msc’.<br />
    103. 103. 67<br />View under Ports (COM & LPT) to see which COM port is used for the msp430. It will be labeled something similar to “MSP430 Application UART (COM9)”. <br />Now open the HyperTerminal. <br />Select COM port from above (COM9) and configure the serial port as: <br />Port: COM9 <br />Bits per second: 9600 <br />Data bits: 8 <br />Parity: None<br />Stop bits: 1<br />Flow Control: none<br />Once the Hello World example is debugged and downloaded, it should output to this console. You should now see the LED blink and the text ‘Hello World’ output to the console.<br />
    104. 104. 68<br />Communication Examples<br />In this example, it demonstrates how to establish communication between two devices. <br />There must be one coordinator in the network.<br />The basic coordinator startup process<br />Reset ZNP<br />Set Startup Option = CLEAR_STATE and CLEAR_CONFIG – this will restore the ZNP to “factory” configuration.<br />Reset ZNP<br />Set ZigBee Device type to COORDINATOR <br />Reset ZNP <br />Note: if you want to set a custom PANID or channel list, do that here and then reset ZNP<br />Register Application (Configure the ZNP for our application)<br />Start App<br />Wait for Start Confirm<br />
    105. 105. Change Channel<br />69<br />As mention previously, each network can only have one coordinator. Therefore, each group must use different channel to avoid conflict. <br />
    106. 106. 70<br />
    107. 107. 71<br />Basic Communication Flowchart<br />Coordinator<br />Init. network & display info<br />Listen for incoming data or join request<br />Join request<br />Date received<br />Full<br />Display incoming<br />messages<br />Check if network full<br />Denial Connection<br />Not Full<br />Accept Connection<br />
    108. 108. 72<br />Basic Communication Flowchart<br />End-Device<br />Init. network & display info<br />Search for Coordinator or Router<br />Timer Interrupt Triggers<br />Send message to coordinator<br />
    109. 109. 73<br />Simple Application Example<br />
    110. 110. 74<br />CC2530 ZNP Sample Code Flowchart<br />Coordinator<br />Init. network & display info<br />Format and <br />Broadcast<br />Listen for hardware<br />interrupt<br />Button Pressed<br />Listen for incoming data or join request<br />Join request<br />Date received<br />Parse and Display<br />Messages<br />Full<br />Check if network full<br />Denial Connection<br />Not Full<br />Accept Connection<br />Unknown Message<br />Status Report<br />
    111. 111. 75<br />CC2530 ZNP Sample Code Flowchart<br />End-Deivce<br />Timer Triggered<br />Init. network & display info<br />Format and <br />Broadcast<br />Listen for hardware<br />interrupt<br />Button Pressed<br />Listen for incoming data<br />Accelerometer Triggered<br />Date received<br />Display<br />Messages<br />