Latest revision as of 20:30, 30 March 2024

UAS is either Unmanned Aerial Sensor or Unmanned Aircraft System

What

The goal of this project is to create an Automatic Flight System for use, initially, on inexpensive R/C aircraft. We intend to do this using low cost Arduino (or Arduino-like) development boards, an IMU, and GPS. As our confidence in the system grows, we intend to grow the project to control larger drones capable of greater range and payload.

Demonstration Goals

Command surfaces.
Command throttle.
Demonstrate RTS/preflight.
Unpowered straight line flight coupled with "safe" landing.
Powered, short straight line flight coupled with "safe" landing.
Fly an oval retaining a static altitude
Circle up to altitude, then circle back down and land.
Circle up to altitude, then dive down and land.
Perform multiple "Go Around" test landing passes.
Fly a longer flight plan.
Test failure modes.
Bonus: attempt to fly thermals!
Bonus: aerobatics!

Why

Because it interests us.

Of course, this is nothing new. It's all been done before, but not by us.

Practical Uses

This are some interesting, potentially practical uses:

RF data repeater
Search drone (e.g. missing hikers)
Wildfire spotter

Who

Scott B.
Jeremy M.
Mike M.

Design

See UAS/Design

Implementation

Hardware UAS/Initial_BOM
Software UAS/Software

Assumptions

Developers Notes

UAS/Notes

@@ Line 1: / Line 1: @@
 <div style="float: right">__TOC__</div>
+UAS is either '''Unmanned Aerial Sensor''' or '''Unmanned Aircraft System'''
 == What ==
-Arduino based auto-flight, auto-land  drone.
+The goal of this project is to create an Automatic Flight System for use, initially, on inexpensive R/C aircraft.  We intend to do this using low cost Arduino (or Arduino-like) development boards, an [http://en.wikipedia.org/wiki/Inertial_navigation_system IMU], and GPS.  As our confidence in the system grows, we intend to grow the project to control larger drones capable of greater range and payload.
-=== Goals ===
+=== Demonstration Goals ===
 * Command surfaces.
 * Command throttle.
 * Demonstrate RTS/preflight.
-* Short, straight line flight coupled with "safe" landing.
+* Unpowered straight line flight coupled with "safe" landing.
+* Powered, short straight line flight coupled with "safe" landing.
 * Fly an oval retaining a static altitude
 * Circle up to altitude, then circle back down and land.
@@ Line 14: / Line 17: @@
 * Fly a longer flight plan.
 * Test failure modes.
+* Bonus: attempt to fly thermals!
+* Bonus: aerobatics!
 == Why ==
@@ Line 19: / Line 24: @@
 Of course, this is nothing new.  It's all been done before, but not by us.
+=== Practical Uses ===
+This are some interesting, potentially practical uses:
+* RF data repeater
+* Search drone (e.g. missing hikers)
+* Wildfire spotter
 == Who ==
+* Scott B.
+* Jeremy M.
+* Mike M.
 == Design ==
-going to take an arduino, or arduino like system, and have it control a model airplane. This drone will have an on board GPS for position (3D), heading, and speed. Will need the Gyro to know if we are level, or to hold a certain position in a bank or turning maneuver.
+See [[UAS/Design]]
-=== Architecture ===
+== Implementation ==
-Maybe the following subsystems exist:?
+* Hardware [[UAS/Initial_BOM ]]
-==== Navigation (NAV) ====
+*Software [[UAS/Software ]]
-This subsystem calculates location, orientation, and--maybe--HAGL.
+====Assumptions====
-==== Return to Service (RTS) / Preflight ====
-This subsystem should perform RTS (return to service)/preflight testing of the craft.  I suppose it will come with a checklist so the maintenance person knows when to invert it, etc, so it can test it's various sensors.
-RTS should not pass if Maintenance has stored a fault.  Until formally cleared.
+== Developers Notes ==
-==== Maintenance (MAINT) ====
+*[[UAS/Notes]]
-This subsystem should capture and store faults (e.g. failure of a sensor).
-==== Flight Plan (FP) ====
-This subsystem should feed the flight plan to the Pilot.
-This should interface w/ COMS to enable flight plan updating.
-==== Pilot ====
-This is the thing that takes inputs from NAV and FP and commands servos and throttles.  This flys the craft.
-Somehow, COMS should probably be allowed to command the craft.  This might go through FP or may be an override.
-==== Communications (COMS) ====
-This is a 2 part subsystem: USB and RF.  behavior shall be different in USB vs RF mode.  Also will be different if we are on ground.
-==== Random Thoughts ====
-What do our emergency modes look like and where do they go?
-How do we monitor the battery?  (Shut the engine off and glide in for a landing?)
-Where is autoland?  Is this part of the pilot or it's own subsystem?
-== Bill of Materials (BOM) ==
-===Auto Pilot ===
-* [http://leaflabs.com/devices/#Maple-Mini Maple Mini] as the in craft controller?
-*[http://www.sparkfun.com/products/465 GPS Receiver] ~$60.00
-* accelerometer or Gyro (3 axis)
-* Proximity sensors (for autoland)
-===Aircraft===
-* [http://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idProduct=9614 HobbyKing SkyFun] as the craft
-** Note: make sure to get a redundant craft.  I, or my s/w defect, will surely crash and destroy one...
-* [http://www3.towerhobbies.com/cgi-bin/wti0001p?&I=LXHHB0&P=0 Servos] X 3 (two control surfaces plus throttle)
-* [http://www.hobbyking.com/hobbyking/store/__18083__Hobbyking_Bixler_EPO_1400mm_ARF_USA_Warehouse_.html Bixler] Alternate craft?
-* [http://www.hobbyking.com/hobbyking/store/__5455__Predator_UAV_74in_Spy_Plane_ARF.html Predator]
-* [http://www.hobbyking.com/hobbyking/store/__17988__MQ_9_Reaper_Fiberglass_2500mm_FPV_ARF_.html Reaper]  cool.
-=== Misscelaneous ===
-* [http://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idProduct=13987 Camera?]
-====Assumptions====
 = See Also =
+* [http://en.wikipedia.org/wiki/Inertial_navigation_system INS] @ Wikipedia
+* [https://www.modelaircraft.org American Model Aircraft]
+* [http://diydrones.com/profiles/blog/show?id=705844%3ABlogPost%3A28583 DIYDrones Regulator page]

UAS: Difference between revisions