Académique Documents
Professionnel Documents
Culture Documents
AIAA 2010-1021
The authors performed the detailed design phase of a ducted fan MAV. In house
techniques were used to size the propellers, servos, linkages, stators and vanes. With the
detailed design phase completed, the authors moved forward with the construction of the
MAV. It was during this stage that the authors found improved ways of fabricating the
vehicle. These methods allowed for the retention in strength of the materials while shedding
the GTOW of the vehicle, allowing for the possibility of the inclusion of payloads. Tests
conducted on the constructed vehicle include thrust testing, landing gear drop tests,
electronic benchmarking and the beginning of tethered tests on the duct fan MAV.
Nomenclature
aimpact
A
B
C
d1
d2
d3
d4
dA
dE
dR
Fimpact
g
m
Vimpact
Z
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
I. Introduction
A design, build, and fly project was tasked to an intern research team at AVID LLC. The project description was
to design a low cost, low weight, ducted fan micro aerial vehicle (MAV) that a human could remotely pilot. The
design had many requirements that limited the size of the vehicle, cost of materials, method of propulsion and
endurance. A brief list of the specific requirements is given below. Stiltner et. al.1 discusses the preliminary and
conceptual design phases for this vehicle.
Geometric and Size Constraints
o The vehicle must be roughly the size of a football (8 dia., 12 tall)
o Must be lighter than 4 lbs GTOW, with a target weight less than 2 lbs
1
Aircraft Design Engineer, AVID LLC, and M.S. Aerospace Engineering, Virginia Tech, Blacksburg VA, AIAA
Student Member.
2
Aircraft Design Engineer, AVID LLC, Blacksburg VA, AIAA Student Member.
3
Aircraft Design Engineer, AVID LLC, Blacksburg VA, AIAA Student Member
4
Intern, AVID LLC, and M.S. Aerospace Engineering, Virginia Tech, Blacksburg VA, AIAA Student Member.
5
Intern, AVID LLC, and M.S. Aerospace Engineering, Virginia Tech, Blacksburg VA, AIAA Student Member.
1
American Institute of Aeronautics and Astronautics
092407
Copyright 2010 by AVID LLC. Published by the American Institute of Aeronautics and Astronautics, Inc., with permission.
Figure 1: An image of the iMAV superimposed on the image of a football (left); image of the
iMAV (right).
At the CDR, the vehicle design was locked in at a GTOW of 20 ounces. During construction, however, the
designers found that manufacturing qualities were severely underestimated and the result was a 32% decrease in
total vehicle weight. Furthermore, the vehicle was not designed to carry a payload, however, one could be added
without penalty up to a GTOW of 20 ounces. Additional payload may be added beyond the GTOW of 20 ounces
accepting a penalty on performance.
The remainder of this paper provides an in-depth look at the detailed design and construction of the iMAV. A
section on vehicle testing is given, which describes the tests conducted to characterize the performance of the
2
American Institute of Aeronautics and Astronautics
092407
vehicle and gives the results obtained from these tests. The vehicle testing section provides results obtained from
landing gear testing, control and avionics bench testing and thrust testing.
B. Propeller
Most of the iMAVs budget was allocated to the propulsion and avionics components. As such, a self designed
fan, though desirable, proved to be too expensive for the budget. Several off-the-shelf propellers were researched
and a study was made between three different sizes: 8x6, 9x7, and 10x7 Master Airscrew 3-blade propellers. Here,
the first digit is the propeller diameter in inches, and the second digit designates the advance ratio of the propeller.
If the propeller were rotated in a solid (assuming no slip), the propeller would travel this distance forward in the
solid. Thus, if the 8x6 propeller made one complete revolution in a solid, it would travel 6 forward. For the fan to
fit inside the duct, the previously mentioned propellers were trimmed to a 6 diameter.
To analyze the propellers, the geometry of each propeller was needed to create the necessary XROTOR files.
The chord length and blade span was measured using calipers. The chord was measured at eighth inch increments
from the hub out to the tip. The propeller was then projected onto a chalkboard using an overhead projector. The
researchers then measured the propellers projected chord length. Knowing both the actual and the projected chord
lengths allowed the researchers to determine the blade pitch angle at each station, depicted in Figure 3.
XROTOR
Mark
Drela,
http://acdl.mit.edu/research.html
Associate
Professor
of
Aeronautics
3
American Institute of Aeronautics and Astronautics
092407
and
Astronautics,
MIT.
Figure 4: Twist at each normalized radii station for the Master Airscrew 8x6.
4
American Institute of Aeronautics and Astronautics
092407
Figure 5: Normalized chord at each normalized radii station for the Master Airscrew 8x6.
Using XROTOR, velocity sweeps were performed for a constant thrust of 1.5 pounds. These velocity sweeps
were converted to .avr files. These files were merged to form three separate thrust maps; one for each Master
Airscrew propeller. Once the individual thrust maps had been uploaded to AVID OAV, the results were used to
choose the best Master Airscrew for use on the iMAV. While little difference in performance was noticed, the
weight of the 8x6 Master Airscrew was considerably lighter than the others. Figure 6 shows the performance
comparisons between the three propellers.
C. Control Vanes
Control surfaces are a key component in the design of ducted fan MAVs (Unmanned/Uninhabited Aerial
Vehicles) if controlled flight is to be achieved. In short, the control surfaces must be large enough to provide
adequate control authority, yet light enough not to result in a severe impact on CG location. This, in itself, is a
complete contradiction that the designer must be aware of and a design trade is necessary to obtain an adequate vane
size. During the conceptual and preliminary design phases, AVID OAV was used to compute trade studies, which
analyzed trimmed vane deflections vs. forward flight speed, vehicle CG location, vane chord length, and number of
vanes. These initial trade studies showed a vane chord length of 1.25 and two vanes per set (8 total vanes) were
optimal. The trade studies also revealed an optimal CG location of 0.5 above the duct lip, or duct highlight. Stiltner
et. al.1 discusses these trade studies in further detail.
AVID OAV models the aerodynamics of the vanes using two dimensional (airfoil) theory, and so further
analysis was devoted to analyzing the vanes performances in a 3D sense. While a 2D analysis gives the researchers a
5
American Institute of Aeronautics and Astronautics
092407
good starting point for the vane size, it doesnt accurately model the vanes behavior in a real world sense due to tip
loses and other inherent wing behavior. To that end, it was known that the actual vanes must increase in planform
area compared to those modeled in OAV, to obtain the desired performance. XFOIL7, a program for the design of
subsonic airfoils, was used to generate a 2D polar of a NACA 0012 airfoil operating at 100k Re #. The 2D polar was
then used as an input to the aerodynamic software RAPT, to generate 3D polar of the control vanes. This allowed
the researchers to correct the vane area based on more realistic aerodynamic data. The outcome was a control vane
size of 1.5" chord length and 2.5" span, which was approved at the CDR (Critical Design Review).
D. CAM (Computationally-created Aerodynamic Model)
A computationally generated aerodynamic model (CAM) was created to provide data on the forces and moments
acting on the iMAV during flight. This CAM, essentially a virtual wind tunnel aerodynamic model, accepts
prescribed data concerning a desired flight condition as its input, and returns the forces and moments acting on the
vehicle based on those inputs. The CAM is primarily used for the flight controls development. Here, the designers
can use the CAM to develop the six-degree of freedom equations of motion (6DOF EOMs). The control system
development will be discussed later in section II.E.
The iMAV CAM was created using the AVID OAV software. Force and moment data were generated by OAV
at various flight conditions, i.e. flight speed, angle of attack, throttle/fan rpm, and control vane deflections. The
generation of the CAM can be thought of in parallel to a wind tunnel generated look-up model. In a wind tunnel
experiment, data would be collected at various wind tunnel speeds, angles of attack, throttle, control surface
deflections, etc. The data would then be compiled into arrays so that the forces and moments could be obtained or
looked up based on user input wind speed, throttle setting, control surface deflections, and so on. The difference
here is that, rather than performing a wind tunnel experiment to collect the data, the OAV software was used to
simulate a wind tunnel and compute the force and moment data. Furthermore, it is understood that the CAM is
based on aerodynamic theory and assumptions, and may not capture some of the realistic aerodynamic phenomena
of the iMAV.
After obtaining the data from OAV, it was organized into arrays as a response surface using MATLAB. Thus, at
this point the CAM is a large grid of data points. However, as is the case with wind tunnel testing, data cannot be
collected at every conceivable point in the vehicles flight envelope. The same mindset holds for the CAM because
computing data at every possible flight condition would consume too much time. For instance, data may be
collected at flight speeds from 0-50 fps in increments of 5 fps. To fill in the holes of the grid, the data is interpolated
so that every point in the flight envelope contains data.
Once completed, the results of the CAM were used to compare with AVID OAV data. Figure 7 depicts the fan
RPM vs. the forward flight speed, and Figure 8 depicts the power required for flight speed. The CAM data predicts a
lower fan speed and power requirements than that of AVID OAV. These differences amount to just 3% lower in fan
speed and only 0.2% lower in power requirements. The forces and moments for a hover flight condition of iMAV
were used to create a linear model and develop control gains, which is discussed in Section E.
Figure 7: AVID OAV and CAM Comparison of RPM data vs. velocity.
Figure 8: AVID OAV and CAM Comparison of Power Required vs. Velocity.
E. Control Law
Typically, ducted fan vehicles of this nature are unstable and thus some form of stability augmentation is
necessary for human piloted flight. This instability is because the vehicles optimal CG location is above the duct
highlight (most windward point of the duct). So, in hover the vehicles dynamics mimic that of an inverted
pendulum. In Stiltner et. al.1, the authors discuss the reasons why the CG is located above the duct highlight and
describe how the optimal CG location is found. For iMAV, the optimal CG location is roughly 0.5 above the duct
highlight. In the following paragraphs, the iMAV control system is discussed. First, a brief overview of the pilotvehicle interaction is necessary. This is followed by a discussion of the control system architecture, which is a
Command Augmentation System (CAS).
7
American Institute of Aeronautics and Astronautics
092407
1. Pilot-Controller-Vehicle Interactions
The human pilot will use a two-stick transmitter, similar to those used in radio controlled (R/C) aircraft
applications, to control the vehicle (Figure 9). Typically, R/C fixed wing aircraft have four control channels made up
of throttle, aileron, elevator, and rudder. On the transmitter, the sticks are directly linked to each of these channels:
the left hand stick is used for throttle (up/down) and yaw rate (left/right), and the right hand stick for pitch rate
(up/down) and roll rate (left/right).
8
American Institute of Aeronautics and Astronautics
092407
The commanded yaw rate was limited to a maximum of 30 degrees per second so the pilot can avoid getting the
vehicle in a non-recoverable state.
x = Ax + Bu
(1)
y = Cx
The first equation is the classic state space representation of the linearized equations of motion. Here, x is the
state vector, u is the vector of control inputs, and the A and B matrices are the Jacobians termed the state matrix and
the input matrix, respectively. The second equation is the output equation, which gives the measureable states, or
output, y. Typically, y is a subset of the state vector and the matrix C, termed the output matrix, is a mapping from
the state to the output. Here, the state vector was made up of the velocity (vehicle body frame), the attitude, and the
vehicle angular velocity. Similarly, the control vector is made up of throttle, aileron, elevator, and rudder.
Inputs of aileron, elevator, and rudder are hard to visualize for these vehicles. For instance, an aileron deflection
is typically a combination of control surface deflections. Because of this inconvenience, aileron, elevator and rudder
commands are transformed into individual control vane commands. This is done based on the following equation.
9
American Institute of Aeronautics and Astronautics
092407
d1 = dA dR
d2 = dA + dR
d3 = dE + dR
d4 = dE dR
(2)
In the above equation d1-d4 are the individual vane deflections. Similarly, dA, dE and dR are the aileron,
elevator, and rudder deflections respectively. Figure 11 gives an OAV parametric geometry model of the iMAV and
lists which vanes correspond to d1-d4.
Figure 11: Parametric geometry model of iMAV listing the individual vanes.
Lastly, the output vector y, is made up of the attitude and angular rate terms, but excludes the body velocity
terms. This was due to available sensors on the vehicle. The iMAV had an onboard IMU (inertial measurement
unit), which can measure angular rates and accelerations. Using a Kalman filter, the angular rate measurements and
the accelerations are used to estimate the roll and pitch attitude of the vehicle. The accelerations can be integrated to
determine the vehicle velocity, but a second form of sensing is needed to correct integration error. Future versions
of the vehicle will employ a GPS chip to sense the vehicles velocity.
3. Control System Architecture
As mentioned above, the control architecture used for iMAV is a CAS. The specific system is an LQT/LQR
based control law. Simply speaking, an error is computed to compare the desired state with the measured vehicle
state. The control gains then actuate the control surfaces such that the computed error is driven to zero. A basic
block diagram can be seen in Figure 12. In the figure, the plant contains the linearized vehicle dynamics, which were
linearized about the hover equilibrium.
In the block diagram, the plant is the linearized vehicle dynamics discussed in the preceding subsection. The
input to this block is the error, which is the reference command minus the measured output. Here, the reference
commands are made up of the attitude angles roll and pitch, and the angular velocity terms roll rate, pitch rate, and
yaw rate. The yaw attitude is decoupled from the system, because the vehicles dynamics arent affected by how it is
pointed relative to the ground.. The reference commands for roll rate and pitch rate are always zero. This defines
the LQR portion of the control system in that these states are always driven to zero. This is in place to damp out
high frequency oscillations in the vehicle, making it appear to fly steadily rather than jittery. The remaining
values are the commanded inputs, which were discussed in the pilot vehicle interaction subsection.
F. Structures
The two battery pods are located on opposite sides of the duct. The pods provide support for the battery and two
of the four control servos. The battery placement in the pods is high due to the desired vehicle CG location. The
servomotors are mounted beneath the batteries to minimize the control rod length and so that they dont have a
negative impact on vehicle CG location. Two similar pods are mounted at 90-degree stations around the duct from
each battery pod. These pods are only used as servo treys, and therefore do not include the upper structure to house a
battery. For a detailed explanation of component placement, refer to Stiltner et. al.1 The four pods structures
additionally serve as axial stiffeners for the duct. See Figure 13.
Figure 13: Battery pods (left and right), and stator pods (located
front and center), allow for axial stiffeners of the duct wall.
As can be seen in Figure 13, the center-body of the aircraft is located above the lip of the duct in order to achieve
the desired center of gravity. The motor is mounted below the center-body plate such that the propeller is oriented
directly below the lip of the duct. The printed circuit board, IMU, wireless transmitter/receiver, and speed controller
boards are secured to the top of the center-body plate. These electronics and avionics equipment are actively cooled
by the flow entering the duct. The center-body is supported by two perpendicular struts, which are inserted and
glued into the duct lip via epoxy. The struts also serve as a logical path to route the wires from the batteries and
servos to the upper center-body.
The total weight of the iMAV is 13.4 ounces. To this approximate one pound, a factor of safety of 20% is added
to the vehicle weight, resulting in a weight of 1.2 pounds, and a mass of 0.0371 slugs. The landing gear must sustain
an engine out fall from 3-feet AGL. In order to determine the approximate load each landing gear will receive from
the fall, equations of energy and kinematics are employed. First, the velocity upon impact is found using
conservation of energy:
11
American Institute of Aeronautics and Astronautics
092407
m g z =
1
1
m V 2 (0.0371 Slugs)(32.2 ft/s2 )(3 ft) = (.0371 slugs)Vimpact 2
2
2
(3)
(4)
m corresponds to the mass of the iMAV, g is the gravity term, z is the height above the ground and V is the
velocity. Assuming an impact time of 0.005 seconds, the acceleration at impact is calculated, where Vo is zero for
the initial velocity.
a impact =
(5)
This results in 86.3 gs experienced by the iMAV. The force experienced on impact is found using Newton's 2nd
Law:
(6)
Fimpact is the force experienced by the iMAV upon impact with the ground. Therefore, each landing gear
(dividing Fimpact by four) will experience 25.9 lbs of force. The modulus of elasticity needed to sustain this force on
impact was calculated to be 7.91 x 105 psi.
Spring steel (ASTM A228) is chosen to be the material of the landing gears as it was cheap, available and met
the modulus of elasticity requirement. ASTM A228 has the following properties:
12
American Institute of Aeronautics and Astronautics
092407
III. Construction
As mentioned previously, the iMAV was constructed in house at AVID LLC in Blacksburg VA. Low cost
building materials, custom tooling, and COTS components have been purchased to ensure that iMAV stays within
budget. The following chapters describe the construction of the iMAV based on its individual components.
1.
Construction Materials
Fiber Glass
Carbon Fiber: tow, rod, mat
Hobby Epoxy (15 and 30 minute cure)
Various sizes of balsa wood and hobby ply wood
Insulation foam
Spring Steel (music wire) of various O.D.s
CA (cyanoacrylate) and wood glue
MDF and rough lumber
13
American Institute of Aeronautics and Astronautics
092407
14
American Institute of Aeronautics and Astronautics
092407
15
American Institute of Aeronautics and Astronautics
092407
The stators where constructed with 2-plies of 3 oz. fiberglass. One layer with 45/45 degree fiber orientation
relative to the span direction, and the second at 0/90 degree orientation relative to the span direction. A 6 O.D.
cylindrical mold (PVC pipe) was used to create stators with constant twist and circular camber. The fiberglass was
laid on the mold at an angle to the cylinders axis, forming a gentle helix shape. The researchers found that the
linear twist distribution is roughly equal to the offset angle between the span axis of the stators and the height axis of
the cylinder for small offset angles. Again, the stators are depicted in Figure 2.
C. Vanes and Related Hardware Fabrication
Many concepts were brainstormed to construct the control vanes in attempt to make them light weight. Initially,
the designers had intended to cut the vanes from foam using a hot-wire foam cutter. After trade studies revealed the
size of the vanes (~ 1.25 chord), the designers threw out this idea for fear of a poor quality foam cut. Another
consideration was hollow fiberglass or carbon fiber vanes. Unfortunately, the limitation here was that the designers
were required to fabricate the mold of the vanes. Without proper tools and using only hand techniques, this would
also be a tedious job and so it was thrown out for fear of poor manufacturing qualities. Fabricating the vanes from a
sheet of balsa wood proved to be the best solution. Here, the vanes would be hand sanded from a 1/16thick balsa
sheet. A paper template of a NACA 0012 airfoil was used to obtain the proper cross section and chord length.
Due to the relatively low strength of balsa wood, vane coatings were considered for hardening and strengthening
the vanes. Four test articles were built using CA glue (Cyanoacrylate), hobby brand 15 minute epoxy, Elmer's Wood
Glue, and a no coating (control) article. The hobby epoxy coating yielded the most durable part, but was also the
heaviest. The CA glue was the lightest of the coatings, but most brittle, and wood glue came in at 2nd behind the
epoxy. In the end, the coatings were thrown out for weight savings as strength was deemed a secondary penalty
compared to weight. As the project neared completion, a small CNC (Computer Numeric Control) mill had been
purchased, which was used to precision cut the flight article vanes. The use of the CNC mill allowed for accurate
fabrication of the vane dimensions, specifically regarding the NACA 0012 profile. 45 degree cutouts were made to
the inside corners of the vanes to prevent pitch vanes from colliding with the set of roll vanes.
Even at their maximum thickness, the vanes are very thin due to their chord length. So, rather than running a
single axel through the span, separate axels were fixed to the root and tip of the vane. The tip axels were formed out
of wooden dowel rods and the root axels of 1/16 diameter carbon rods. A jig was made to ensure that the axels
remained perpendicular to the vane at the root and tip. The axels are located at the vane quarter-chord location so
that low control (hinge) moments are required.
The vanes were designed such that 1 vane in the set of 2 would drive the set. For example, the servo linkage
would attach to the axel of the driver vane. A passive linkage would then be connected from the driver vane to the
passive vane, such that when the driver vane is actuated the passive vane is also actuated by the same amount. The
passive linkage was fabricated using 0.015 music wire (spring steel), and 0.015 ID aluminum tube for the hinges.
Figure 19 depicts the servo linkage and driver vane and passive vane linkage.
16
American Institute of Aeronautics and Astronautics
092407
Figure 19: Servos are linked to the driver vane via carbon fiber rods.
The passive vane is linked to the driver vane via .015 inch wire.
The vane endplates were constructed from balsa and measured one inch wide for the narrow section, 1.5 wide
for the wider section and are 1.75 tall. Each endplate was fitted between the four sets of ribs and attached to the
outer duct wall via epoxy (Figure 19). Nylon bushings were used to act as bearings where the vane axels and
endplates meet. This helped the vane axels rotate smoothly. Regarding the inner vane support, a rapid prototype
cylinder was used as the lower centerbody. The rapid prototype element contained hollowed out tubes for which the
vane axels could be positioned. Using rapid prototype material allowed for stiffening of the lower portions of the
duct wall.
The servos used for iMAV were four HXT500s. These servos weigh 0.18 oz and provide 11 in*oz of torque.
The servos and control horn of the vanes were connected via carbon fiber rod. This carbon linkage connected to a
1/64 diameter spring steel wire on both ends. The portion of wire connected to the servo was set 3/16 from the
servos center. In order to ensure that a servo movement of 3 degrees corresponded to a 1 degree deflection of the
vanes, it was calculated that the control arm should be offset 0.125 from the axels center. All attachment points
between the carbon rod and spring steel was accomplished via epoxy.
through the center of the foam. This hole was used to house a wooden dowel which protruded from the bottom of
the foam duct by 1.75. This simulated the vanes that protruding from the duct in the actual vehicle. Lead weights
were added to the top of the foam to simulate the weight of the designed vehicle (20 oz). Fiberglass and epoxy were
used to attach the landing gear to the test duct. The landing gear legs were constructed out of the previously
mentioned 1/8 O.D. music wire.
The crude drop test model can be seen in Figure 20. The model was dropped from specified heights to test the
landing gear in an engine out failure. The model was then inspected for yielding of the landing gear or failure at the
attachment location. The dowel position was also inspected to determine whether it had impacted the ground and
receded up into the foam, indicating the potential occurrence of damage to the control vanes. The drop tests showed
that the landing gear were capable of sustaining a fall from 30 inches AGL without excessive deformation to the
landing gear or the attachment method. At a 30 fall, the attachment point failed, and the landing gear were slightly
bent. The researchers observed that the fiberglass was tearing at the bottom of the attachment point and believe that
this is due to splaying of the legs. Also, based on the dowel position, a fall from this height may cause significant
damage to the control vanes.
18
American Institute of Aeronautics and Astronautics
092407
Figure 21: Fishing line attached around the perimeter of the landing gear.
B. Thrust testing
A thrust stand was constructed to measure actual thrust capabilities of fan, duct, and motor combination. The
thrust stand is a simple balance arm with the vehicle on one side and a scale on the other. When the vehicle
produces thrust, the opposing end of the balance compresses an electronic scale, and thrust force is obtained. In this
configuration the duct exhaust can be placed over the edge of a table to minimize ground effect. During thrust tests,
the throttle is commanded by a microcontroller, which also records battery voltage and current draw. To detect fan
RPM, a laser beam was aimed through the fan plane onto a phototransistor. A multimeter was used to detect the
frequency at which the phototransistor was shaded from the laser beam by the fan. Multiplying this frequency by
the number of fan blades (3) and dividing by 60 seconds yields fan RPM.
The thrust tests demonstrated that the system was capable of producing thrust greater than 1.5x the gross weight
of the completed vehicle. Thrust tests also demonstrated that as the battery voltage dropped, fan RPM decreased for
a given throttle command. Currently the pilot has full command of the throttle, but if the throttle command were
given in part or whole to the onboard system, this discrepancy would have to be characterized and accounted for.
Figure 22 shows the XROTOR predictions and results of thrust tests plotted as Thrust versus RPM and Figure 23
depicts the thrust stand.
19
American Institute of Aeronautics and Astronautics
092407
Figure 22: Comparison of actual thrust for a given RPM with the theoretical
prediction.
Figure 23: Balance arm and scale used for thrust testing.
The microcontroller forms the backbone of the avionics system gathering information from the IMU and
wireless connection while simultaneously controlling the servos and sending information back over the wireless.
Once the wireless link was tested, it was used to monitor the other processes such as ADC readings of the IMU and
individual servo commands. Once the IMU and servo commands were working, the onboard control algorithm was
tested.
The basic function of the control algorithm is to translate the IMU signals into servo commands. The first step in
the process is to estimate the angular orientation of the vehicle by Kalman filtering accelerometer and gyroscope
readings. Then the LQR control code is calculated to give elevator, aileron and rudder deflections. Finally the
deflections are mixed into the four servos and translated into PWM commands out to the servos.
A Kalman filter was used to mix accelerometer and gyroscope readings to obtain the best estimate of the actual
vehicle state. Using two perpendicular accelerometers the angle of the vehicle with respect to gravity can be
calculated as an arctangent. A second method is to integrate the gyroscope readings. One method of testing was to
hang the vehicle by a string and let it move as a pendulum. The filter was tested by comparing the observed angles
to those calculated by the Kalman filter. Another test was to subject the vehicle to large translation accelerations,
which would produce inaccurate angles from the acceleration arctangent calculations while, the gyroscope influence
on the Kalman filter kept the angle estimates accurate. During the course of testing it was found that the fan RPM
produced a large amount of noise in the accelerometers. A fast Fourier transform (FFT) analysis of accelerometer
outputs at various fan RPMs demonstrated this clearly as in Figure 24. The current solution is low pass filter with
cutoff frequency as low as 2Hz. A small range FFT onboard the vehicle is being looked into as a method of
determining the cutoff frequency on the fly. Rubber vibration dampeners are also being implemented on the IMU
board and motor bolts to reduce the magnitude of these vibrations in the acceleration data.
21
American Institute of Aeronautics and Astronautics
092407
V. Conclusions
The final preliminary design of the iMAV detailed a vehicle weight of 1.25 lbs. The vehicles overall dimensions
called for a height of 10.25 and an overall width of 9. During detailed design, the authors compared various COTS
propellers using in house analysis to choose the appropriate propeller. AVID OAV and XROTOR were used to
accomplish this. These same tools were used in combination with XFOIL to design the MAVs stators in order to
provide torque cancellation. Using AVID OAV, a computationally-created aerodynamic model was created which
provide analysis on forces and moments the iMAV would encounter during various flight conditions. These results
aided in the formulation of the vehicles control law.
During the fabrication phase, the authors learned of improved techniques and lighter materials, which aided in
the vehicles construction. These techniques included methods of stator layups by using fiberglass draped over a
cylinder to acquire the desired camber and twist distribution, the use of a CNC to construct the vanes with a NACA
0012 profile among others. These methods combined with data received during initial drop tests of the landing gear
allowed for the reduction of the GTOW by 32% and yet retaining the propulsion power of 22 hp. This has yielded
the possibility of the addition of a payload up to 7 oz without the incursion of performance penalty.
As it stands, the iMAV has entered the testing phase. The first rounds of tether tests have begun. The authors are
pleased to report that the iMAV first achieved hover status on December 29, 2009 during its first run of tether tests.
Future tests and free flight are planned to occur within 2010.
References
1. Stiltner, B., Olien, C., and Faber, J., Conceptual and Preliminary Design of a Remotely Piloted Ducted Fan MAV,
AIAA Aerospace Sciences Meeting, Orlando, Florida, Jan. 4 - 7, 2010.
2. Aircraft Control and Simulation, 2nd Edition, Stevens, B., and Lewis, F., John Wiley & Sons, Hoboken, New Jersey,
2003.
22
American Institute of Aeronautics and Astronautics
092407