We have moved! Please visit us at ANTHROECOLOGY.ORG. This website is for archival purposes only.

Oct 29 2011

GoPro HD Hero

Because the Ecosynth team has been looking at purchasing the GoPro Hero2 as our next platform camera I figured I'd share some of the videos I've taken with the GoPro Hero. These videos were recorded over the past summer in Cockeysville Maryland. The body of water that's visible when flying at higher altitudes is loch raven reservoir. The GoPro hero is one of the lightest and least expensive HD Cameras on the market and I'm very pleased with its performance so far. The videos were uploaded in HD remember to turn HD on.



Apr 02 2011

Battery Configuration Test

In an attempt to increase the EasyStar’s endurance we had decided to place two 2200mAh, 11.1V battery packs in parallel with one another. One of the major concerns in doing this was the possibility of overloading the plane’s frame and altering both its flight characteristics and inherent stability. Earlier today I had decided to test the EasyStar’s ability to handle the additional weight of a second battery pack (approximately 179g) as well as test the parallel battery cable that I had made a few days earlier.

As expected, the additional weight in the plane’s nose had significantly changed the EasyStar’s center of gravity. To account for this the camera mounting position was moved further back and is now located more than 75% of the plane’s length from the nose. During this test flight the camera was replaced with 165 grams of washers. Overall the EasyStar had handled the additional weight with ease and was actually a bit easier to manage in flight. Full throttle along with a solid throw is now required for an adequate hand launch and the elevator must be used gracefully in order to prevent the wings from breaking when pulling out of a dive. Although the stall characteristics were a bit less forgiving with the added weight the plane was still able to maintain a level flight after both tip and power-off stalls at the cost of a significant loss of altitude. The EasyStar’s gliding capability was greatly affected and sustained gliding via thermals are no longer possible. The most significant difference between the new and old setup was the change in landing speed. the EasyStar must now be landed at much greater speeds to prevent damage to the fuselage. This means that extended flights with two batteries will be limited to areas with larger fields nearby for landing. Sites like Herbert Run would be very difficult if not impossible for this configuration but the Knoll could still be flown due to its close proximity to large open fields. Endurance test will be flown within the next few days along with a one square kilometer mission.  

Jan 15 2011

Easystar clones- which is best for Ecosynth?

On DIYDrones there is a "Roundup of all the EasyStar clones":



Can anyone tell me which of these would be the best for Ecosynth work?

Your thoughts?


EDIT by Jonathan 1/17: Originally posted link is broken, here is a working link.


Jan 04 2011

First Flight With the ArduPilot

Prior to the first flight test I wanted to insure that the servos would remain stable throughout the flight so last night I was trying to figure out why I had experienced occasional servo jitter when in manual mode but not in any of the other flight modes. I had eventually found a line in the code which had indicated that the flight mode was designated by the magnitude of the servo rotation value indicated on the transmitter. My problem was a result of the manual mode switch position being too close to the minimum manual mode switch position value indicated in the code. I was able to increase the switch's magnitude to 140%, well above the minimum value of 37% indicated in the code. The servo jitter problem had not occurred since. 

Today I had visited a local flying field to test the EasyStar in both the Manual and Stabilization modes. In order to simulate the weight of the SD4000 digital camera 165 grams of washers were mounted inside the EasyStar’s fuselage where the digital camera will eventually be placed. The first flight was in manual mode to insure that the CG was located in the correct position and make sure that all the trims were correctly positioned. After making a few adjustments I had switched it over to stabilization mode to see how the plane would respond. Everything had seemed to be in working order. When I had tilted the plane sharply on its side and quickly let go of the stick the plane would correct its orientation and continue on a level flight path. The same would result if the pitch was changed abruptly. Due to a low laptop battery I was unable to optimize the PID gain values or test any of the other flight modes. I will continue with the flight tests tomorrow and am going to work on getting the XBees working so I can record the test flights to make sure the GPS is working properly.

In order to help with calibrating the gain values in the field I had organized the information presented on the DIY Drones website into an easy to follow field guide which is attached as a word document.

Setting PID gain values.docx (15.21 kb)

Dec 02 2010

ArduPilot Fixed Once Again

Just prior to Thanksgiving break the ArduPilot board had stopped powering on once again. I had spent this past week troubleshooting the board and had found that another one of the imbedded wires had become disconnected. Unlike the last time this had happened, this wire appeared to have be charred indicating that the board had shorted out while I was working on it. After double checking the polarity of the cables and reviewing the diagrams on DIY drones I was unable to find and connection errors. I was able to fix the board by using yet another jumper cable to complete the circuit. The image below shows the location of the two jumper wires that are currently attached to the board (indicated by white lines). Once again, the ArduPilot powered up and had shown no signs of further damage. It wasn’t until later on in the week that I had noticed that the desk I  had been working on had collected a large amount of solder globs and loose wires. This had led me to believe that while I was working on the ArduPilot I had placed in on top of a loose wires or A solder glob, causing the board to short out. Yet another reason to keep your soldering area clean.    

Nov 05 2010

Finalized ArduPilot Parts List

Last Friday the Ecosynth Team had placed an order at Tower Hobbies for an almost ready to fly(ARF) EasyStar. Although it has not yet arrived this progress had encouraged me to finalize the complete parts list for the EasyStar project. Over the past few weeks the ArduPilot Shield V2 had been listed as being out of stock on the SparkFun Electronics website. Because of this I have been holding off on creating this list until it was confirmed that this component wasn’t in the process of being replaced by an newer version. As of 11/3/2010, all of the required components are in stock, each of which is listed below.

  1.          Component                   Price/unit
  2. ArduPilot                               24.95
  3. ArduIMU+ V2.                        99.90
  4. ArduPilot Shield V2                 57.20
  5. uBlox 5 GPS                           87.90
  6. GPS Adapter                          19.50
  7.   GPS Cable                            1.95
  8.   Break Away Headers               2.50
  9.   Programming Cable                17.95
  10.   Servo Extension Cable(x4)       1.50
  11.   Air Xbee4                              2.95
  12.   Air Xbee Adapter                    10.00
  13.   Air Xbee Jumper Wires            3.95
  14.   Ground Xbee                          44.95
  15.   Ground Xbee antenna              7.95
  16.   Ground Xbee Adapter Board      24.95

The total cost comes to $452.60, not including the EasyStar, radio gear or battery pack. Although the Xbees aren’t required for autonomous flight they make revising and uploading waypoints in the field more convenient as well as relay live updates to a nearby field computer. For the initial test flights I plan on using a 11.1, 2300 mAh lipo battery which will eventually be upgraded to a higher capacity battery in order to achieve a total flight time of 15 minutes.

Once the EasyStar arrives I will begin to modify the frame and install the brushless motor and ESC. An order for the ArduPilot components will hopefully be placed within the next few days. I have already downloaded the Arduino Program Editor and had started to modify the code such that it will be compatible with all of the above components. I have already spent a significant amount of time reviewing the code and trying to understand what the program is doing and the methodology behind its operation. The majority of my focus has been on the IMU sensor and the process by which it records measured data and transforms it into values that define the plane’s attitude with respect to the earth. Bill Premmerlani had posted a tutorial on the mathematical operations involved in this procedure here.

I had previously mentioned the possibility of integrating a self-deploying parachute into the EasyStar’s fuselage which would enable the plane to land autonomously in small fields. I had recently come across RocketChutes.com, a website that sells inexpensive model rocket parachutes ranging in size from 12’’ to 48’’  in diameter. A chart on RocketChutes.com indicates that their largest parachute (48’’) would be ideal for 48-64oz rockets; well above the weight capacity that would be required for a fully loaded EasyStar. Once this platform is able to fly autonomously I will continue to look into alternative features such as this.

Oct 21 2010

EasyStar Modifications

Ever since our first flight with the EasyStar it was clear that a few modifications were necessary  for the plane to become a usable alternative to the SlowStick. Over the past summer Evan had spent a significant amount of time improving the EasyStar by making it easier and more convenient to use as an image acquisition platform. The following serves as an explanation of the most successful modifications that were made to the plane, many of which will be incorporated into the autonomous EasyStar project.

To provide the EasyStar with more power the stock 400 speed brushed motor was replaced with a 400 speed Turnigy brushless motor running a 6x4 APC propeller. A Turnigy 30A brushless ESC was also used along with a 11.1V 2200 mAh battery. This power system gives the EasyStar enough thrust to carry a standard digital camera, external GPS unit and FPV equipment with ease. Because of the EasyStar’s large wings it was extremely unresponsive to rudder inputs, making it difficult to maneuver.  To fix this the rudder was extended by approximately 1.5 cm to give the plane more agility when turning.

The inside of the EasyStar was carved out to make room for the battery pack and camera. Access to the planes internal components was provided by small plastic hinges mounted along the bottom of the fuselage which enabled it to be opened and closed easily. In order to protect the camera lens when landing plastic skids were created and mounted to the underside of the fuselage with hot glue. Magnets were also added to the front cover, allowing for easy access to the electronics near the nose of the plane while also providing a break-away point in a crash.

Initially, Evan and I had trouble with the elevator becoming jammed so it’s important to make sure that it can move freely in either direction before each flight. The EasyStar’s center of gravity was also found to be abnormally far forward for a high wing plane, making it difficult for us to pinpoint. After a series of test flights we had found that the EasyStar performed best when the center of gravity was located approximately 1/5 of the wing past the leading edge.

In my past experience with the EasyStar, landing has been somewhat difficult due to its natural tendency to fly fast and glide for long distances without throttle. The following are some modifications that I believe would enhance the EasyStar’s ability to land in small fields like HR. Remotely activated Air breaks could be mounted on the body to help slow the plane down when landing. This would consist of a piece of foam connected to a micro-servo which would be activated by a toggle switch on the transmitter, extending the foam and inducing drag. Another solution consists of attaching  flaperons to the trailing edges of each wing. This would act as an extended airfoil to help slow the plane down without compromising its lift. Furthermore, the addition of Landing gear would allow for rise-off-ground (rog) takeoffs and landings while also serving as a replacement for the plastic landing skids used previously.

Oct 16 2010

ArduPilot Flight Modes

Over the past two weeks I’ve been trying to determine what the ArduPilot system is actually capable of. In order to insure the success of this autonomous UAV project, it’s critical that we find a Autopilot system which can support all of the features mentioned in the Autonomous EasyStar post. For more information concerning the ArduPilot system visit the ArduPilot online manual. provided by DIY Drones.

Although the ArduPilot will primarily be used for its autonomous flight capabilities, it also supports a  variety of other flight modes which are described below. Only three of the following modes can be programmed to the AdruPilot at a time and a three way toggle switch on the transmitter is used to activate one of these three modes.

Manual Mode: Yup, its exactly what it sounds like. This mode enables the user to operate the plane manually without any help form the ArduPilot. This mode would mostly be used for takeoffs, landings and positioning the plane at its starting location.

Stabilize: Similar to manual mode, only the ArduPilot will process its kinematics to help the user fly the plane. If the user find him/herself in trouble then all that he/she must do is release the control sticks while the plane levels itself into stable flight. For this mode the airspeed must still be controlled manually.

Fly By Wire A: This is a slightly more autonomous version of “Stabilize” mode in which the airspeed, stability and altitude are controlled by the ArduPilot, all the user has to do is point the control sticks in the direction they want the plane to go and it’ll figure out a way to get there. The altitude will remain at the height the plane is when this mode is activated. In order for this mode to work properly the user must designate a value for maximum pitch, yaw and roll angle in the open source code.

Fly By Wire B: This mode is similar to Fly By Wire A, only the airspeed is controlled manually while the altitude and stability are controlled by the ArduPilot. Again, the altitude is held at the height this mode is activated.

Auto: Fully autonomous GPS waypoint navigation. AdruPilot takes complete control but the user can still “nudge” the plane to help it maintain its course if needed. 3D GPS waypoints are uploaded via the waypoint editor prior to the flight. This mode would most likely be used as the primary mode when performing image acquisition flights. 

RTL: The airplane will return to its launch position and circle above until manual control is re-established. Like the Auto mode, the airplane can still be “nudged” manually. The return to home circling radius can be preset in the main code file.

Loiter: The plane will circle around the position at which this flight mode is initiated. You can also “nudge” the airplane in this mode as well. This feature would be used to distract the plane while groundwork is being done, serving as a “second set of hands” when scanning an area by yourself. If this mode is activated near the ground station then new waypoints could be uploaded wirelessly using the optional Xbees. The radius of the holding pattern can be adjusted in the open source code.

When flying with Xbees a laptop can be used to run LabView, a ground station software which displays the plane’s altitude, airspeed, roll angle, bearing, navigation data and battery voltage. In addition, LabView will log the flight information in both a data log file and kml log file. The data log file stores navigation and altitude information while the kml file contains flight path and waypoint information that can later be viewed in Google Earth. The flight path can also be viewed in real time via Google Earth. 

Within the next two weeks the parts list for this project will be finalized and the respective components ordered. The majority of the work for this project will be done over the winter, when image scans are not our teams first priority. Until then, the Ecosynth Team will continue to be preoccupied with maintaining the hexakopters, performing image captures and analyzing the resulting data and point cloud structures.    

Sep 30 2010

Autonomous EasyStar (Oh the Possibilities)

Although the Hexakopter has been performing flawlessly over the past few weeks, knock on wood; the Ecosynth team is still searching for a less expensive alternative for gathering aerial photographs. As of now, the only way to do this consistently and reliably is through the use of autonomous technology. Throughout this semester I have decided to convert the EasyStar platform into an inexpensive yet fully autonomous airplane.

One of the most significant advantages of this platform will be its ability to fly long distances without having any range limitations. This feature will enable us to fly an entire site without having to plan multiple flight patterns or plan around the “home” position of the aircraft. In addition to this, the open source code will enable us to adjust the flight characteristics and create subroutines of our own that will enhance the airplane’s usability and effectiveness. 

The primary objectives for this project are as follows:

  1. -  Create an autonomous airplane for under $400 (US)
  2. -  Capable of carrying a standard digital camera
  3. -  Utilize GPS technology to allow for multiple 3D waypoint navigation
  4. -  Maintain safe and stable autonomous flights in winds up to 10mph
  5. -  Provide continuous flight for approximately 15 minutes
  6. -  Relay the planes geographic position, altitude and airspeed to a field computer
  7. -  Return to home on request and sustain a holding pattern


If I somehow manage to complete all of the primary objectives with time to spare then I will begin to work on the slightly more interesting secondary objectives:

  • -  Ability to take off and land autonomously in large fields 
  • -  Autonomous parachute deployment at a specified position and altitude to assist with landing in small fields
  • -  Use IR sensors to provide obstacle avoidance capabilities
  • Over the past week I’ve been researching the various autopilot systems available online. One of the most promising options is the ArduPilot from DIY Drones. The main advantage of this system is its use of open source code which can be modified to accommodate any airplane with three or more channels. The ArduPilot is also capable of controlling additional channels to support optional tasks, such as parachute deployment. In addition, the ArduPilot is capable of performing 3D waypoint navigation and two-way telemetry data transfer via the optional XBee modules. DIY Drones provides a free point and click style mission planner that enables users to easily create and upload 3D waypoints to the airplane (as illustrated in the figure above). The components required to use the ArduPilot include the following: 
  • ArduPilot Board                                24.95
  • Shield V2 kit w/ Airspeed Sensor       57.20
  • Breakaway header                              2.50
  • U-Blox5 GPS                                   87.90
  • U-Blox Adapter                                19.50
  • U-Blox Cable                                   1.95
  • X, Y and Z Sensors                           99.90
  • Female-to-female RC cables (x4)       1.50 per
  • The parts required for wireless telemetry are as follows:
  • Air XBee                                            42.95
  • Ground XBee                                      44.95
  • XBee Antenna                                  7.95
  • Adafruit adapter board                      10.00
  • XBee Explorer USB                          24.95

The total cost of the ArduPilot system, without wireless telemetry; is around $299.90 (US). The wireless telemetry brings the total cost to $430.70. Throughout the upcoming week I will continue to look for ways of reducing the cost of this system. If we decide to use the ground XBee, XBee Explorer USB and XBee Antenna included with the Hexakopter then the total cost could be reduced to $352.85, which is still a significant investment.

The EasyStar itself is a relatively inexpensive plane; an almost ready to fly (ARF) version can be purchased for around $120. Our prior experience with the EasyStar has led us to believe that the stock motor and ESC should be upgraded to a 400 speed brushless in-runner motor and brushless 25A ESC. In addition to this, the tail rudder should be extended by 1.5 in. to allow for a tighter turning radius. Over the next few weeks I’ll be creating a page which will contain all of the modifications made to our EasyStar as well as their overall effectiveness.

You can download the Arduino software here and the waypoint configuration tool here, both of which are free. The latest version of the autopilot code can be found here. I will be sure to post more blogs about the ArduPilot system as I continue to familiarize myself with its tools and capabilities.