3D Robotics

ArduPilot (Legacy) main page

 

3689315381?profile=original

 

[This original ArduPilot board, now called the "Legacy ArduPilot" is no longer produced or officially supported by the DIY Drones dev team, and this page is maintained just for historic reasons. However, there are still many users of it out there and it still works fine. The user group for Legacy ArduPilot users, for both thermopile and IMU use, is here.]

 

ArduPilot is a full-featured autopilot based on the Arduino open-source hardware platform. It uses infrared (thermopile) sensors or an IMU for stabilization and GPS for navigation. It is the autopilot used to win the 2009 Sparkfun Autonomous Vehicle Competition.

The hardware is available from Sparkfun for $24.95. An expansion board ("Shield") kits that includes an airspeed sensor, a 3.3v power regulator for 3.3v GPS modules and other sensors and cables and connectors for easy attachment of the XY and Z sensors, is available from our own store for $57.20.

 

User f

ArduPilot features include:

  • Can be used for an autonomous aircraft, car or boat.
  • Built-in hardware failsafe that uses a separate circuit (multiplexer chip and ATTiny processor) to transfer control from the RC system to the autopilot and back again. Includes ability to reboot the main processor in mid-flight.
  • Multiple 3D waypoints (limited only by memory)
  • Altitude controlled with the elevator and throttle
  • Comes with a 6-pin GPS connector for the 4Hz uBlox5 or 1hz EM406 GPS modules.
  • Has six spare analog inputs (with ADC on each) and six spare digital input/outputs to add additional sensors
  • Supports addition of wireless modules for real-time telemetry
  • Based on a 16MhZ Atmega328 processor. Total onboard processing power aprox 24 MIPS.
  • Very small: 30mm x 47mm
  • Can be powered by either the RC receiver or a separate battery
  • Four RC-in channels (plus the autopilot on/off channel) can be processed by the autopilot. Autopilot can also control four channels out.
  • LEDs for power, failsafe (on/off), status and GPS (satellite lock).


Resources:

ArduPilot requires the free Arduino IDE to edit and upload the code to the ArduPilot board.



The code is currently optimized for the Mutiplex EasyStar three-channel powered glider and FMA sensors, but can be modified for other aircraft and sensors. It uses the rudder/ailerons and elevator to maintain level flight and navigate to GPS waypoints. It supports a desktop setup utility and ground station software. It also includes a "fly-by-wire" mode that simply stabilizes RC flight. The main code is ArduPilot2.x.zip in the download section of our Google Code repository, where x is the latest version.

What you need to make a fully-functional autopilot:


Open source extras:

  • If you want to build your own board from scratch, the necessary files and component lists are here.
  • [Note: you shouldn't need this, since this code is loaded on the ArduPilot board at the factory] Latest multiplexer code (for the board's second processor, an Attiny, which runs the failsafe system) is here.
    Instructions for loading this code are here.



Recommended UAV setup:

3689303688?profile=original


Airframe option one: Hobbico SuperStar (49" wingspan, $95, shown above). This is an inexpensive, good flying high-wing trainer with ailerons. It can be hand launched in a park or take off from a runway, and replacement parts are readily available in case of a crash. If you want much better performance with this aircraft, you can upgrade it to a brushless motor, speed controller and a LiPo battery. [If you don't already have one, you'll also need a balancing charger and power supply.] Note: any stable aircraft with both ailerons (for stabilization) and rudder (for navigation) can work, so feel free to experiment with what you've got.

3689313666?profile=original


Airframe option two (recommended for ArduPilot 2.x): EasyStar (shown above). Performance can be improved with the modifications described in this post.

You'll also need:

  • A six or seven channel RC transmitter and receiver, with at least one toggle switch (ideally three-position but two-position will work, too, although you will have to mix channels to have access to both autopilot modes in the air), such as the Futaba 7C.
  • Some servos (at least three for ArduPilot 1.0; at least two for ArduPilot 2.x) and at least three female-to-female servo cables to connect the RC receiver to ArduPilot.


Cool optional extras for your UAV:

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • @Chris Anderson
    could you upload your FunJet headers?
  • Roll:
    What should I look for when I have too much Roll Integrator? I am at .8 P and .1 I. (ailerons)

    Heading:
    I have been using the method of increasing P, with I set to 0. Waiting for the drunk driver effect, then pulling back the P and increasing I. I feel pretty good with what I have it set at, I will continue to tighten up nav after I finish roll and pitch. I am currently flying pich manually.


    Had a great night tracking waypoints! thanks guys! cant wait for my Ardustarion and Xbees to come.
  • 3D Robotics
    Doug, that's a new one for me. Sounds like an electrical problem, maybe with a bad solder? Check your connections and solder joints. (In manual mode the signal is passed right through the MUX, so there's no code involved).
  • Developer
    Need help again!

    I took my setup off my test board and just finished the integration into my airframe. Now I have a very weird problem with manual mode. When I switch into manual mode the aileron servo moves full right and stays there for several seconds. During this period transmitter stick movement has no effect. After several seconds the aileron servo moves towards center and begins to respond to stick movements. However the servo jitters and responds to stick movements in a delayed and jerky manner. When I switch to RTL or WP mode the aileron servo quits jittering and holds a position. I haven't had a chance to walk around with it yet and see if it appears to move correctly (its dark now).

    The elevator acts normal. I rebooted several times and the only change between trials was that some times the amount of time the aileron servo went to full right was a bit longer, sometimes a bit shorter. Generally between 2 and 5 seconds.

    Any ideas?
  • hi Brent!!

    sorry late answer but people here answered!!

    for the lock i'm not sure for Ublox and Sirf but in NMEA it doesn't means that you have a sat 3 sats in view
    i did a little mod to be sure lock occurs only when 4 sats viewed

    if you interrested i could post it but since it is NMEA i just prefere not to post it cause it is not supported anymore , exept if you needs it.

    by the way HappyKilmore update is awesome i did try it few times (emulator too) and it works great!!
  • Thanks Peter, That looks like another fun project especially the emulator.

    To anyone, when we get a GPS lock, does that mean that we do indeed have a lock on at least three satellites?
    Over the weekend my first flight for the day was perfect. Landed, got fueled up, and the next flight didn’t do anything right. I just wonder how this 110 degree weather and humidity is affecting my electronics.
    Can’t wait for Winter.
  • @ Brent:

    Here is the link:

    Config tool Update by Happyk
  • Brent,

    HappyKilmore did a config tool update, it allows to click in waypoints, save mission, it does terrain following data analysis. It should be off the forum for 2.3 release. Check there for his link, you can use that one which makes waypoint add and mission saving possible. Also updated gui with better google maps integration etc....well worth using...
  • @ Fefenin,
    What is?
    “i'll try first the config tool mod by Happykillmore that allows to save and load missions”
    You posted on page 54. It gets old having to reenter all my waypoints each time I change flying fields. Is there another config tool I’ve been missing out on?
    Thanks
  • i went for a fly today and sadly, just before the first take off with all the new settings ,i burnt the ESC
    i guess it was because of the 5cells and all the servos + ardupilot and GPS (more than 2 AMPS) + the steerable landing gear servo stuck

    so because i now doesn't have more time to try it before my few month trip to Taiwan 'ill just stop the project for now and waiting for teh UBLOX to arrive

    i hope i'll find all the gear there to fly an easystar with ardupilot

    regads
    fefenin
This reply was deleted.