UAS

From HeatSync Labs Wiki
Revision as of 16:52, 16 August 2011 by en>ScottyB (→‎Design)
Jump to navigation Jump to search

What

Arduino based auto-flight, auto-land drone.

Why

Because it interests us.

Who

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.

Architecture

Maybe the following subsystems exist:?

Navigation (NAV)

This subsystem calculates location, orientation, and--maybe--HAGL.

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.

Maintenance (MAINT)

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?)

Bill of Materials (BOM)

Auto Pilot

Plane

  • 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...
  • Servos X 3 (two control surfaces plus throttle)

Assumptions