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

  • @Jordi, it looks like you may have finally cracked the Nav issue. I'm looking forward to getting off the bench and actively testing again.
    As usual, thanks for putting so much effort into this.

    Matt
  • For those of you that read and saw my test-bed and thought about doing the same for ground testing alone, forget about it! I’m thinking of removing it from the forum. Or at least understand that its only purpose was convenience.

    After Bryan’s comment, I got to thinking that he’s right! I was forgetting a very important part, the sensors! I was carrying this thing around like a Geiger counter and wanting it to lead me to the right direction. Don’t do that!!
    My biggest mistake was that while I was walking towards my waypoint, I was not rolling my test-bed like the airplane would in flight.

    Give me time, I’ll catch up.

    Brent

    BTW Bryan thanks. Constructive criticism goes along way, or at least to waypoint one.
  • Developer
    "R" means real calculation and "F" fake calculation (the actual one). the L1, L1 and L2,L2 are the generated waypoints.
  • Developer
    Please before asking, when i print the values only shows two numbers after the decimal point 0.00 is normal and is not the same number used for the calculations-> 0.000000. OK???

  • Developer
    OK i found something interesting. THE NAVIGATION IS NOT WORKING PROPERLY AROUND THE WORLD, just some places like my HOME .
    I wrote this small app GPS_Formulas.ziphere, to generate random float coordinates (lat from -90 to 90 and lon +-180), works pretty well i was able to generate 50 calculations for seconds (even more). I found out that at low latitudes and long distances the error is pretty, pretty big, just for not say completely wrong, so i switch back to the 100% real formulas. I will release the fixed beta code during this day.
    https://storage.ning.com/topology/rest/1.0/file/get/3691955138?profile=original
  • Developer
    Peter, this code i posted days ago, so you never saw it? Weird.
  • I will try the new code today Jordi, thanks for all the work. Package going out monday to you my friend....

    Fingers crossed on this version :)

    -Peter
  • Developer
    I just need be sure not bug are inside to make the official release. I'm setting up the small simulator to check the navigation around the world (but without getting out of home).
  • Admin
    @Earl,
    You get what you pay for in the way of brushless motors though some users may argue contrary to that statement. The cheaper motors usually do not have quality bearings and the armatures are not as well balanced. Also you cannot push the cheaper motors as much as you can the better built and usually more expensive motors.
    @David Low,
    I have mounted the FMA XY sensor just aft of the cockpit cover. I do not find that the ESC thermal energy affecting the XY sensor as the air stream over the ESC keeps it pretty cool.

    Regards,
    TCIII
This reply was deleted.