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

  • SiRF Have you had succesful flights?
  • @Bryan
    I always do calibration on the ground, so far no problem
    @Paul
    which gps unit u used? in NMEA or binary (SiRF) mode?
  • I have four Ardupilots and have used all the 2. codes up to 2.3.3 Demo 2 .none of them have worked for me
    However, I watched Jordi's video of the walkaround and something caught my attention.
    The readout updates at about once per second mine update randome 10 to 20 seconds which by then it's missed the WP
    So I hardwired the ardupliot to the laptop with a the programming cable and cut one of the wires so as not to conflict with serial port, Simulating an Xbee.
    Started hyperterminal and set it to capture. then drove around about a 1 mile radius and watched the data coming through.
    The data is scrolling up the screen nice and fast. But when I looked at the data after the trip there was large chucks of Lat/Long all the same ie. not updateing, which I believe might be causeing the problem.
    I would really like to get some feedback as I do not seem to get much response from this forum.
    Paul
  • Thanks for that last post Jordi. The "calibrate servos" option is going to be a big help. You've also helped explain why my plane has shown different flight characteristics from flight to flight (IR sensor calibration). I thought she was possessed!
    Regarding calibration, I've been using the bind plug and calibrating with the plane on the ground. Will this mess up the IR sensor calibration? Should the plane be held off the ground when binding?
  • Is the 233 demo2 code for testing on the ground or can it be used for actual flying. What radius values are a good starting point?
    Paul
  • 3D Robotics
    Earl,

    We don't have a second serial port. Rx on the one serial port is used by the GPS.
  • please keep the autopilot trigger on the rc transmitter while implementing live PID tuning and waypoint upload during flight :D
  • I think most of us are using XBee for telemetry. Which is 2way. Why not let the G/S XBee handle switching from manual/AP/RTL and other stuff like max radius on turns on the fly, upload more waypoints on thr fly, etc ?? Them you only need a 3 or 4 channel R/C radio for throttle and control surfaces.
    Earl
  • Developer
    Brent West,

    Yes there's a way. Just des-serialize the eeprom data into a file and then load it when you need it. C# is very powerful, of course a lot better than C++.
  • 3D Robotics
    By "fix", you mean "add new functionality". It's a good idea, and we can put it on our (very long) list of to-dos.
This reply was deleted.