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

  • Hi Jordi,
    For the throttle adjustments in the header, what is the
    (//3-23
    #define throttle_dead_zone 20 //In porcent %) and the

    (//3-24
    #define throttle_absolute 3 //Absolute)

    adjustments for?

    Thanks,
    Brent
  • Developer
    You are welcome!
  • hi, all !

    i'm back from the sea and what i hear is very good!!

    thank's to you all guys "bug hunters"!!

    as soon as i'm ready to fly with a new rebuild plane i'll check this beta release

    @Jordi
    thank you for not giving up after all.

    regards
    fefenin
  • Success at last. after weeks of testing all the codes I flew sunday (I am in the UK) first flight with Beta code. flew all the waypoints, all working thanks Jordi. It ws a calm day no wind, on the second flight a did pretty good but could not find some of the WP's so it flew around hunting them out. I altered the heading gain to .9 and it was way to much it was all over the place, so reduced it to .65 this was to low so the default .7 must be pretty close. The amount of roll I feel is to much so next time I try it iout I am going to try and reduce the amount of roll. But Now I have a working base to play with
  • Developer
    Well i bought one (the last one red) and didn't work at all with ardupilot so i switched back to adafruit.
  • Quick question: I recall the sparkfun Xbee adapter boards not being recommended. What was the reason behind this?
    Cheers,
    Nick
  • I have been on travel Jordi, so haven't had a chance to check the site that often this week. I will try the new code tomorrow...and let you know the results...thanks again for the hard work to resolve this...
  • > Jordi, Your_da_man!
    Looked at the new beta code. Coulnt see a diff in the 'Save_Launch_Parameters_Flagged();'
    Don't know what you did,but now I don't need to know. It's working. I loaded the new code and saw on the screen a few meters for dist and not 121 for brg. I changed the print code for testing,and thats all, and it printed what i would expect. YEA!!!
    Now I feel confident to put it in my plane.
    Thank you
  • Developer
    The big deal code is here.
    I made a lot of good changes including the new navigation algorithms and much more. Please read the text file inside for more details. I also test it very well, i added 4 waypoints around my block and i drove with my car to be 100% sure the navigation was working and everything (i used the ArduStation).

    To download click ArduPilot23_Beta2.ziphere.

    BTW the PI gains must be re calibrated, because the servos where bad configured. Read the text file. This is just a beta, after everything works fines i will make the official release. Maybe tomorrow i will go and fly to tune the PI's again.

    Any other errors like HOME (0,0) means is something wrong in your setup.

    Enjoy!
  • >Brent,
    Sorry about the harsh comments earlier. I think people like you are just what this project needs. People willing to put in the time to get out there and test the hardware and software. Chris and Jordi can only do so much so I figure we are the "free labor" beta testers they can use to get some objective feedback on their product. I should say free and willing labor. It's fun to work on a project that is still growing and needs some polishing. As they say, "The joy is in the journey".
    >Jordi,
    Thanks for the latest code revision. Can't wait to try it out.
This reply was deleted.