|Project Summary||Project Information|
An Unmanned Aerial Vehicle (UAV) is an aircraft capable of operating autonomously through an autopilot or remotely by an operator on the ground. UAVs significantly reduce operational costs and pilot risk, and when properly configured can be successfully operated by less experienced users compared to full size aircraft. A UAV can fulfill a variety of mission profiles, including aerial imaging. Previously completed projects have produced an airborne imaging system, an aircraft large enough to carry the imaging system as payload, and an autopilot. However, the airborne imaging system is potentially antiquated, the aircraft requires further testing, and the autopilot has only seen implementation on a smaller test aircraft.
A UAV will be constructed combining the work of previous projects which will carry a payload of imaging hardware and software to accomplish Imaging science research and applications.
Final Project Status
- Working aerial vehicle that can hold a substantial paylod
- ArduPilot and camera integration completed - Can send a signal to trigger the camera from the ArduPilot
- Aircraft has the capability to navigate, autonomously, to set waypoints
- Camera captures occur at the waypoints
- At this iteration not every waypoint will save telemetry data due to an unknown bug
- After a flight the logs and images can be synchronized using a custom Java program
Possible Causes for Log Defect
- The IO operations on the ArduPilot could be synchronous, meaning that they block the CPU. The CPU would have to wait until the IO operation completes to continue its processing. If this is the case it could be interrupting the telemetry data writing in order to complete more important autopilot operations.
- The way the camera is triggered is by sending three electric pulses to the camera. In order to create these pulses the CPU is slept in between signal changes. By sleeping the CPU this could be adversely affecting the other operations, including data logging
|Arick Reed Abraham||ME||Team Lead - Aero Designfirstname.lastname@example.org|
|Tim Fratangelo||CE||Code Masteremail@example.com|
|Spencer Hanson||ME||Aero Designfirstname.lastname@example.org|
|Alex Klymkow||EE||Electronics/Power Designemail@example.com|
|Aaron Wilbee||EE||Camera Integrationfirstname.lastname@example.org|
Table of Contents
|MSD I||MSD II|