NIMBUS CONOPS Maggie Krause, Ryan Rasmussen, Caleb Fangmeier, Brett Mahnke, and Jiajun Yang

Table of Contents Operational View (OV-1) Constraints Timeline Components Stakeholders Use Case Sequence Diagram Data and Reports Entity Relation Diagram

OV-1 Resources: Websites for building open source drones, open source simulators and software Tools, parts, and technical expertise provided by NIMBUS labs Log of progress made on project over time Comparison table of possible communication methods between drone and mobile device Constraints: -Time -Hardware Test data, real-time testing, case studies, video Inputs Outputs iOS/Android ArduCopter and software Radio control Assembly and programming of an open-source UAV and mobile app The process of drone assembly will be documented and an optimal mode of communication with the mobile device selected. The mobile device will have the ability to issue simple commands to the drone. Results aim to broaden research options for NIMBUS labs and provide expanded utility of UAVs. Communication interface Companion document to assembly instructions noting required skills, pitfalls, successes

Project Constraints Time Missing/broken parts, order time Unforeseen setbacks in assembly, development, or testing Hardware Choice of iOS or Android Choice of wireless communication method impacts real time performance Drone hardware must be lightweight

Timeline CONOPS (Oct 12) Elicitation and Requirements (Oct 12-Nov 2) Assembly (Oct-early Nov) Research Communications (Oct-Dec) Implement communication interface (Jan-Mar) Research and develop software (Oct-Jan) Design, build app (Mar-Apr) Expected items from externals: -Parts for ArduCopter, workspace in lab already provided Expected Outputs by end of 1 st semester: -Have a working drone that can be controlled manually -Have an in depth comparison of app-to-drone communication methods -Generate a report documenting assembly Expected Outputs by end of 2 nd semester: -Have a working app to communicate with drone -Generate a report documenting development process System integration and testing (Feb-Apr)

Components UAV hardware motors, sensors Microcontroller UAV software communicates with hardware Wireless communication interface WiFi, Bluetooth, Radio Mobile App Remote control

Component Architecture Hardware Controller Mid-level Software Wireless communication Mobile AppRemote Control

Stakeholders Dr. Elbaum and Dr. Detweiler, sponsors: Provide guidelines, resources (parts, lab usage) Interested in successes and pitfalls of assembly and software development Interested in documented outcomes, testing results, and are potential users NIMBUS labs, users: Student researchers benefit from documented outcomes and are potential users and potential future developers

Stakeholders (2) Potential external users: Users outside of NIMBUS labs would interact with the system via the app Could contribute back to open-source community with design decisions Development team: Involved in research, assembly, development, testing, and evaluation of system Concerned about quality of system and results

Use Case Sequence Diagram Drone Hardware Controller Drone Software Wireless Interface Mobile app User Remote control Developer, researcher Documentation User from open-source community

Data and Reports Real-time testing Documents Comparison of wireless communication methods Bluetooth, radio, WiFi Analyzed to select optimal method Companion document to assembly instructions Ease or difficulty at various points Skills required Multimedia documentation Photos, videos

Entity Relation Diagram System Drone App has Developers generate Remote control Documentation Instruction document Communication Analysis Test Results Sponsors analyze Provide feedback Progress log