1 / 29

Eric Hettler Manuel Paris Ryan Miller Christian Moreno James Reepmeyer

Eric Hettler Manuel Paris Ryan Miller Christian Moreno James Reepmeyer. ME. Project Status Update R10003 - Wireless Open-Source/Open-Architecture Command and Control System (WOCCS). Agenda. Mission Statement Prior Projects Current and Planned Projects Stakeholder needs

wallis
Download Presentation

Eric Hettler Manuel Paris Ryan Miller Christian Moreno James Reepmeyer

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. Eric Hettler Manuel Paris Ryan Miller Christian Moreno James Reepmeyer ME Project Status UpdateR10003 - Wireless Open-Source/Open-Architecture Command and Control System (WOCCS)

  2. Agenda • Mission Statement • Prior Projects • Current and Planned Projects • Stakeholder needs • Objectives and Functions • Needs Summary • Proposed Projects • Revised project proposals • Schedule

  3. Mission Statement • Product Description /Project Overview We will develop a new command and control system that will introduce a reliable, intuitive, modular and secure system to benefit MSD teams and teach valuable skills and technology relevant to the needs of the Harris Corporation. • Primary Goals • Produce project readiness packages for 4 to 6 MSD teams • Define new WOCCS project family • Stakeholders • Harris Corporation • MSD Teams • MSD Customers • RIT Educational Community

  4. Past Senior Design Teams • P08027 – Wireless Assistive Control System • P06501 – Zigbee Technology • P08201 – RP-10 • P09232 – Airframe B • Common Themes • Limitations with feedback • Use of unproven and untested systems • Distance and range scaling • COTS capabilities

  5. Planned Projects • P10231 – Versatile Adaptive Controller • Lead by Joe Pinzone • P10236 – RF Telemetry • Lead by Chris Barrett

  6. Project Family • WOCCS represents a new MSD family • Builds off of prior C&C system • Intended to provide a common C&C software/hardware interface • Wide applicability across MSD program • Will result in 4+ MSD projects spanning 1-2 years • Challenges • Little prior student development – unknown scale and scope • No other related project families to reference

  7. Stakeholder Needs – Affinity Diagram

  8. Stakeholder Interview - Harris • Want students interested in RF Technologies • Will not be the end-user of the WOCCS • Budget not a major concern • Key-points in the project for Harris : • RF Technologies • Vibrations • Materials • Sensors • Energy Efficiency • Programming

  9. Objectives • Wireless Command • Few Channels, High Bandwidth • Many Channels, Low Bandwidth • Wireless Feedback • Sensor Data vs Real-time Video • Reliability • Battery Life • Range • Minimal Data Loss

  10. Applications • Use on variety of vehicles • Long battery-life • Open Source • Sufficient range • Security • In Biomed • Lightweight • Feedback intensive • User friendly interface • Security

  11. Needs Summary

  12. Initial Proposed Projects (1) • Wireless link design • Data link development • Specify interface • Signal processing • Find scalable hardware for both base end and device end • Staffing: IE, EE, and CE • Background focus in signal processing and coding

  13. Initial Proposed Projects (2) • Software (Base end) • Reduce signal processing software • Develop signal routing and encode/decode • Combine signal processing/routing software and unify code • Provide scalable software to work with x number of channels at y bandwidth • Staffing: SE, CE, EE

  14. Initial Proposed Projects (3) • User Interface • Develop human interface to the software • Use aircraft controller as test case • Represents a worst-case scenario of data channels and bandwidth requirements • Develop vehicle controller and feedback/sensor display • Staffing: ISE, ID, SE, and CE

  15. Initial Proposed Projects (4) • On-board hardware optimization • Shrink/reduce/optimize/package radio send/receive hardware from team (1) for use on real-world devices • Reduce size • Reduce power consumption • Provide and/or enhance radio power supply • Staffing: EE (power system), CE (hardware and interface), and ME (structural and thermal)

  16. Initial Proposed Projects (5) • (Robotics) Integration • Integrate work from 4 previous teams • Run a robotics project from start to finish using hardware and software completed to-date • Provide feedback for future optimization • Document all successes and failures • Staffing: ISE, ME (Robotics), EE or CE (hardware integration)

  17. Initial Proposed Projects (6) • (Biomed) Integration • Integrate work from 4 previous teams • Run a biomedical project from start to finish using hardware and software completed to-date • Provide feedback for future optimization • Document all successes and failures • Staffing: ISE (ergonomics), ME (Biomed), EE or CE (hardware integration)

  18. Results of Research • Dr. Kolodziej – Airframe A/B/C • RP family of robots • Harris • wants COTS parts (No IP issues) • Harris’ goal is developing student interest in RF technologies, not any specific final product • Biomed application • P10231 and P10236 are now attached to the Harris document

  19. Suggested Projects: Interface Summary: • Replacement for intended Project 1 • Retains some scope from original project: • Data link development • COTS Hardware survey • However, adds new scope: • Survey previous interfaces used by MSD teams • Identify specific points of failure within interfaces • Specify the wireless interface to be used • Team Structure: • 3 EE • 2 SE • 1 SE (Team lead?)

  20. Suggested Projects: API Development Summary: • Replacement for intended Project 2 • Retains some scope from original project: • Develop signal routing and encode/decode • Provide scalable software • However, adds new scope: • API development to specify: • Data structures • Analog/Digital/both signal input types? • Could result in two closely linked teams • One for base end • One for device end • Team Structure: • 3 SE • 2 CE

  21. Suggested Projects: Hardware Selection Summary: • Replacement for intended Project 3 and Project 4 • Select actual hardware for final product use • Shrink and Optimize hardware and packaging to fit on real-world devices • Reduce size • Reduce power consumption • Provide and/or enhance radio power supply • Optimize software code • Test! • Team structure: • 2 EE • 2 CE • 2 SE

  22. Schedule • Week 6 • Re-Identify End Users • Re-Define project goals • Week 7 • Re-evaluate project plans • Conduct follow-up interviews with all stakeholders

  23. Schedule • Week 8 • Define individual projects • Week 9 • Refine project goals and staffing requirements • Week 10 • Project Readiness package • Marketing Video

  24. Conclusion • We are designing 4 different cards • 2 very different applications • There is more background for this project than we realized • Need to develop more concrete set project goals and deliverables • Clarify customers (end-users)

  25. Thanks • Dr. Kolodzeij - ME • Dr. Hensel - ME • Dr. Slack - EE • Dr. Vallino - SE • Mr. McCusker - Harris

  26. Eric Hettler Manuel Paris Ryan Miller Christian Moreno James Reepmeyer ME Project Status UpdateR10003 - Wireless Open-Source/Open-Architecture Command and Control System (WOCCS)

More Related