170 likes | 402 Views
Drone Software and Hardware. Build a sophisticated drone and control it with custom mission planning software. Hardware Requirements. Use open-source Arduino hardware for most embedded solutions. Arduino MEGA recommended. The more I/O ports and RS-232 ports the better.
E N D
Drone Software and Hardware Build a sophisticated drone and control it with custom mission planning software.
Hardware Requirements • Use open-source Arduino hardware for most embedded solutions. • Arduino MEGA recommended. The more I/O ports and RS-232 ports the better. • Embedded software must be compiled using the Arduino IDE. • Use standard Arduino shields for adding new hardware if possible.
Hardware Requirements • Use XBee modules for all radio communications. • A modular framework is already written for you: XAPI 3.0 • XBee allows for easy connections and meshing. It simplifies otherwise complex radio communications • XBee modules will communicate with Arudino hardware using RS-232 ASCII-Hex packets.
Hardware Requirements • The Drone must be built from Commercial off-the-shelf (COTS) parts. • Plenty of vendors that cater to the drone community. • We have a stockpile of parts that can be used to build and repair the drone. • There is no budget for this project. Any new hardware (such as GPS, cameras, sensors, etc.) must be purchased by the group members without re-embursment.
Software Requirements • The mission planning software must be programmed using C#. • A small class is ready to go for serial communications via .NET framework. • Must allow the user to set up a 3D representation of a flight plan and upload it to the drone. • Must allow the user to control the drone directly and at any point in the execution of the flight plan. In other words, the user can “override” the flight plan.
Software Requirements • All Arduino embedded hardware must run the XAPI framework. • Documentation regarding the XAPI and the TUN packet is given. • There is no “raw” communications in the entire system. Everything is in the form of a TUN packet. • XAPI must be outfitted with “services” to manage the drone hardware and radio.
Software Requirements • The resulting PC-side and embedded software must be well-documented. • Use cases must be written to describe operational behavior of drone. • All new types of TUN packets must be documented. • Any modifications of the XAPI must be documented along with all new services. • No magic allowed.
System Requirements • The complete drone system must satisfy many requirements.The user should be able to: • Develop a flight plan and upload it to the drone. • Execute the flight plan at any point in time. • Override the flight plan at any point in time. • Execute the flight plan with or without radio communications.
System Requirements • The drone itself must have stable and predictable flight. • Everything must be in the metric system to avoid confusion (ask NASA about this one!) • It must be able to hover and maintain a stable position. • It must be able to liftoff and land softly. • It must be able to climb or descend to the correct altitude dictated by the flight plan.
System Requirements • When the drone system is complete and all requirements are met, you are free to experiment. • How would a camera be connected to the system? • How can GPS be used to make the flight plan more accurate? • Can battery power and weight be improved for ultra long flights?
Conclusion • Have fun with this project! Learn something new and interesting! • Don’t be afraid to experiment. • Work as a team to solve the more complicated problems! • Be safe! Only fly with goggles! Don’t fly above 120 meters! Don’t fly into innocent people! • Don’t be afraid to ask for help or guidance: Dr. Rinker, Dr. Hiromoto, Brandon Ortiz, and people involved with the Tower Lights can all help you! You are not alone!