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

  • Thanks Chris,
    I will consider your proposition if I can't get get it to work :)
    Jan
  • I think I havé changed since last year, I was using a Jeti 41mHz and am now using an Assan 2.4 GHz.
    What troubles me is that all other Channels work just fine...
    I'm now on holidays in Normandy and will try to reflash the ATTiny, could someone send me a link to the correct flash please?
    Thanks,
    Jan
  • 3D Robotics
    Jan,

    I've never heard of a Attiny losing its programming, but I suppose it's possible. Have you changed radios since you last tried it? If so, it's possible that your new radio is a low voltage one. In that case, you might want to try a servo amplifier.

    If you'd like me to test your board, however, I'd be happy to. Just PM me and I'll give you an address to send it to. I'll send it back no charge ;-)
  • Developer
    @Diego - That is correct. You can either use an earlier version of the code that has walkaround mode, or you could modify 2.5 or later. You would need to change the control structure so that servo_roll = nav_roll, bypassing the lower level PID loop. There could be a unit conversion required as well.

    @Jan - it is possible that the ATTiny needs reflashed. I don't know why it would loose its programming just sitting in a box.....
  • I've doen some testing with "control switch tester", and what I can say is that mode stays on "manual" whatever the switch position is. I have tested with two other checked and working channels on the RX, but same results, mode doesn't change in serial monitor and mux light doesn't turn on.
    Could it be that the ATTiny45 needs reflashing? I remember I flashed it with the failsafe program last year, and last time I tested the Ardupilot it was working, I really don't understand what's happened...

    Bob
  • Hello all :)

    after almost a year in the box, I decided to put my Ardupilot together.
    I have an Ardupilot 1-12-09 with a ArduPilot Shield v15 and I'm facing some problems with the mode button that doesn't seem to work, mux light doesn't turn on in either 3 positions of switch (1000-1500-2000ms).
    Mode channel doesn't show in radio test, I only see 3 channels 1-2-3 working perfectly, but no channel 4 is this normal?
    What could be the problem, I have checked my soldering and all is fine signal is arriving to the ATTiny45 PB2 Pin7.

    Thanks for your help,
    Jan aka Bob
  • So, I can't use Ardupilot 2.5 code for this:

    "ArduPilot's vehicle (car or boat) mode can also be used for ground testing aircraft navigation or as a simple navigation-only autopilot for aircraft with a separate stabilization system to provide a full autopilot solution. It is enabled by setting "Walkaround mode" in the configuration settings."

    ¿True?

    Thanks.
  • Developer
    Walk-around mode has been removed. I don't think we really have the functionality to support FMA Copilot in 2.5 anymore. You may nee to work with an earlier version.
  • HI,

    I want to use Ardupilot without shield board and without IR sensors (I'm using FMA Copilot for stabilization). I'd like to use 2.5 version of de code, but, where is the WALK_AROUND mode in this versión?

    Thanks.
  • So the ardupilot does not catch the control signals coming from the radio controller (except for the control pin #5), and are wired directly to the output. Oh ok I see now looking from the diagram. I will recheck everything and fix any solder point that is needed. The uBlox GPS is working great. Installed it, got a lock with in seconds, reloaded the ardupilot code and did a few other random test and got a lock every single time. Even got a lock inside our metal building!
This reply was deleted.