1 / 22

ZIGBEE/IEEE 802.15.4 PACKET ANALYZER

ZIGBEE/IEEE 802.15.4 PACKET ANALYZER. EC518 – Team 2 – Executive Presentation. Nathan Blagrove Jing Cheng Matthew Hilt. Introduction.

kiona-baird
Télécharger la présentation

ZIGBEE/IEEE 802.15.4 PACKET ANALYZER

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ZIGBEE/IEEE 802.15.4 PACKET ANALYZER EC518 – Team 2 – Executive Presentation Nathan Blagrove Jing Cheng Matthew Hilt

  2. Introduction • The IEEE 802.15.4 standard is designed to enable low cost, power, and data rates in wireless sensor and control networks while ensuring reliable communication. • Our goal is to develop a packet analyzer for use in development and analysis of ZigBee and other IEEE 802.15.4 based wireless networks. • The primary users of this system will be developers working with the ZigBee/IEEE 802.15.4 protocol.

  3. ZigBee/IEEE 802.15.4 - Applications • The following examples demonstrate the importance of the ZigBee/IEEE 802.15.4 standard: • Automation and control: home, factory, warehouse • Monitoring: safety, health, environment • Situational awareness and precision asset location (PAL): military actions, firefighter operations, autonomous manifesting, and real-time tracking of inventory. • Entertainment: learning games, interactive toys

  4. Project Goals • The primary aim is to provide a network packet analyzer with the following characteristics: • Captures IEEE 802.15.4 and ZigBee network traffic • Formats and Displays packet data on a PC • Low Cost • Small Size • Focus of project planning is the Software components; Hardware is generally complete.

  5. Hardware Overview • Atmel ARM7 Based USB MCU • 256K Flash • 64K RAM • Atmel 802.15.4 SPI Radio • JTAG Debug Port • USB Full-Speed Device (Type-A ‘STICK’) • Chip Antenna

  6. Hardware Block Diagram • Please take a look at the actual prototype hardware as it is passed around.

  7. Software Components • MCU/Radio Embedded Software • Capture IEEE 802.15.4 wireless radio communication • Decrypt and/or format data as needed • Transmit data to PC through USB • PC Host Driver Software • Allow communication with the packet analyzer via USB • Feeds the data received from the packet analyzer to the GUI Plug-in for display. • PC Network Trace GUI Plug-in (Wireshark) • Receives data from the host driver software • Provide end users with visual representation of the data captured by the packet analyzer hardware

  8. Graphical User Interface (GUI) • The packet analyzer will target product designers aiming to leverage the capabilities of low-cost/low-bandwidth networks, including those intended to be organized in a mesh topology. • The packet analyzer will provide users with a simple, reliable tool with which to visualize RF packet data transmitted on a network.

  9. Stakeholders • Management Team • First major company project; will set the tone and expectations for projects to come. • Development Team • Similar to management. Success from the engineering perspective will set a positive tone moving forward. • End Users • Positive acceptance of the product by customers is critical. • Functionality, Quality, and Cost must be well balanced. • Investors • As an early-stage venture, all equity holders are closely involved with the progress of the company and its’ projects.

  10. Project Deliverables • Requirements Specification – (3/27/09) • Specification provided to customer and receives customer approval. • MCU and Radio Firmware– (5/7/09) • Passes unit testing and QA performed to confirm functionality matches requirements specification. • PC Host Driver Software – (5/8/09) • Passes unit testing and QA performed to confirm functionality matches requirements specification. • PC Network Trace GUI Plug-in Software– (5/12/09) • Passes unit testing and QA performed to confirm functionality matches requirements specification. • Documentation for Users – (5/18/09) • Covers each of the primary subsystems, overall system operation and usage, and any relevant errata. • Market-Ready Analyzer System with Documentation– (5/18/09) • All firmware and software components are integrated, tested, and verified against requirements specification. Fully functional system delivered to customer with documentation.

  11. Schedule – Work Breakdown Structure

  12. Schedule – Gantt Chart

  13. Schedule – Completion Time • Project Completion Time Calculated to be 75 days • Estimate a contingency time of 34 days over calculated schedule • Based on a staff of 7 full-time and part-time workers

  14. External Milestones • Deliver Requirements Specification – (3/27/09) • Specification provided to customer and receives customer approval. • Demonstrate Radio Packet Reception – (4/13/09) • All packets can be received and decoded (if applicable) by radio on USB-stick and transmitted to the PC over USB for display of the packet data. • Demonstrate USB Functionality – (4/21/09) • Data is successfully transmitted between the USB-stick and the PC. • Demonstrate Display of Packet Data through GUI – (4/30/09) • Packet data can be displayed, saved, loaded, decoded, and filtered through GUI. • Demonstrate Complete System – (5/4/09) • End-to-end functionality of packet analyzer will be provided. Packets will be received and decoded (if applicable) on USB-stick, then transmitted over USB to PC host driver software which will provide received packets to GUI plug-in for display, saving, decoding, or filtering. • Completion of System Testing – (5/5/09) • All integration tests executed satisfactory by test group. • Deliver System to Quality Assurance – (5/5/09) • Fully functional tested system is provided to quality assurance. • Completion of Quality Assurance– (5/14/09) • Quality Assurance verifies all system functionality against requirements specification. • Deliver Market-Ready Analyzer System with Documentation – (5/18/09) • Tested and verified fully functional system delivered to customer with documentation.

  15. Staffing Plan

  16. Staffing Plan • Project Manager (PT) • Liaison between technical staff, investors, and other project stakeholders. • Manages project progress • Software Development Lead (FT) • Oversees all system software development • Directs major architectural decisions • Senior Software Developer (FT) • Primary development role • Responsible for key module development • Junior Software Developer (FT) • Assists Senior and Lead developers • Senior Technical Writer (PT) • Responsible for organization of all project documentation • Senior Software Tester (FT) • Leads the QA testing efforts • Junior Software Tester (PT) • Supports the Senior Tester as required

  17. Staffing Plan Total Man Hours Utilized: 1035 Total Labor Cost: $44,991.62

  18. Resource Usage Statistics

  19. Resource Usage Statistics

  20. Risk Evaluation and Management • Scheduling and/or staffing shortfalls • Team building, provide friendly working environment. • Agreements/contracts at a personnel level. • Cross training between team members. • Packet Analyzer hardware delivery delays • Reach delivery contract with the hardware supplier. • Possible to develop certain firmware components without hardware. • Packet Analyzer hardware design flaws • Hold hardware design reviews. • Simulations. • Test basic communication blocks of the hardware during early firmware development stage.

  21. Risk Evaluation and Management • External dependency on Wireshark • Establish communication channels with Wireshark support at an earlier stage. • Research the Wireshark forum for known issues to anticipate scheduling impacts. • Real-time performance deficiencies • Hardware components review during the design phase. Communicate firmware requirements with the hardware design team. • Firmware instrumentation/fine tuning.

  22. Relative Risk Exposure Analysis Relative Risk (1-10) – Relative Loss (1-10)

More Related