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

  • 3D Robotics
    Yes, once we release 2.3 with the "1.0 simulation mode" we will retire 1.0. People with the old green 168 boards can still use the old 1.0 code, but we won't be developing it anymore. Our aim is to have one code base with multiple configurations.
  • I tested Ardupilot with an RC car yesterday. At first it wandered aimlessly then I discovered that my EM406 GPS had defaulted to 9600 (using v10). Thank goodness the failsafe was working! Changed this in the code and I'm getting GPS lock and better operation.

    It's raining today in Calgary so all I could do was a walkaround test. Curously, the Rudder command shown in my output flips between +25 and -35. Is this normal?

    Are you guys really retiring v10 and suggesting we use 2.2.3 RC1 for cars/boats?
    operation.it
    This domain may be for sale!
  • Jordi, Can you post the servo/sensor test for everyone so they get a 'feel' for what the interaction is between them ?
    Earl
  • 3D Robotics
    Brent, Jordi tells me that it connects the sensors directly to the servos, so they should move in concert with sensor readings.
  • Chris,
    I see it now.
    //5-8
    #define TEST_SENSORS 1 // Set 1 for enable, overwrite the servos with the raw IR sensors data, to test orientation. This will overwrite everything.

    This test is done after you walk away from the computer. With or without the GPS connected, put the switch in autopilot mode, then you wave your hands around the sensors and move the controls.

    No readout while still connected to the computer like with the sensortest.pde test
    Jordi can correct me if I’m wrong.
    Brent
    Hosted By One.com | Webhosting made simple
  • Developer
    Earl it has independent 3.3V regulator. Anyway i was using ublox with the shield power regulator and radio modem with no problems at all. So both ways are ok.
  • Jordi,
    I got my order completed for the uBlox board. I think this will make it better.
    Earl
  • 3D Robotics
    Brent,

    You mean the sensor test option in the RC1 code? I haven't tried that am not quite sure what Jordi has in mind there. I'll ask him.
  • Xbee on external 3.3v and uBlox on shield 3.3 = everything working.
    So.... it is PS related. I dont think it is current but noise on the 3.3 shield line when both are on the shield.
    Earl
  • Chris
    When I load the sensortest.pde software, and then press the serial monitor button in Arduino, I get the readout from each of the sensors and can see them change by covering them individually.
    But to test the sensors with the new code, I don’t get any reading that there working.
    It’s unclear how the test is supposed to run.
    I’m taking notes to help with the manual instructions, but having problems with this one.
    Brent
This reply was deleted.