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

  • Peter. Thanks for all of your testing. It is fantastic to hear you have started to get good results.
  • Unless you’re up for some hacking, 5 channels is a minimum.
    You need channles for throttle, elevator, rudder (or ailerons ) but also a toggle switch for controlling the ardupilot...
  • Hi,
    I am new to microcontrollers but not RC airplanes. Was wondering why you need to purchase a 6 channel radio for an airplane requiring 3 channels. Would a 3 or 4 channel radio do? I have some old 4 channel radios I'd like to use. I am thinking of going with the EasyStar with ArduPilot 2.x
    Thanks for any advice,
    Ron
  • Have you cleaned the IR sensors ? Could be one of the six IR sensors is dirty or has something on it.
  • Peter,
    I wish I could fly tomorrow but I've got to make some fuselage repairs first. I agree that Jordi's latest code revision will allow us to make some real progress in flying and tuning our planes. As Jordi noted, I goofed with my walk around setting but I'll make sure all the header file values are correct next time.
    Asymmetrical/steep right rolling? - Is there any asymmetrical twist in your wings? Lateral CG off? Since you have full control of your throttle, what does your rudder do if you walk the plane while in RTL or WP mode? Does it deflect right more than left? How about when you roll the plane right and left? Do the thermopiles cause the rudder to move the same amount?
  • 3D Robotics
    Peter,

    So it works on the ground in walk-around mode for you, but not in the air? Weird!
  • Developer
    Matt, i also tested the servo in reverse mode. Do the same but in the opposite way, simple math.

    James B. West Thank you for the testing. You were the one who suggest this right? Well somebody did. Rhanks anyway to everybody. =)
  • Developer
    Walk Around must be "0" to test the GPS and heading against the servo and "1" for normal operation. Is just multiplying in the code the roll data coming from the attitude sensors by zero. So it cancel it and the autopilot "believes" is perfectly balanced (roll = 0). So you can clearly see the tail or servo moving left and right. Also this option can me used as ArduPilot V1.
  • @Jordi: I have a question and an idea. Is your roll & pitch set to 1 & 1 or do you have a -1 in there somewhere? I assume since you have created this code that you probably run with 1 & 1...

    Can you somehow mod your set-up or flip some servos so you too require the -1 & -1 for roll & pitch.

    Then your mod set-up can be tested in a manner that's similar to everyone else. Maybe you can just flip (roll) your IR sensor upside down. (I note that when FMA sent me my X/Y IR, they had put the sticker on the wrong sode, so the sensor was inverted compared to your original installation photos, maybe this is part of the problem... also related issue may be cable in front or behind code interfering with the reverse pitch issue...)

    I'm a noob to this so it's just my idea and an assumption of what your own roll/pitch settings are.

    HTH

    Matt
  • Jordi's great little demo video got me off my rear to try again. I downloaded the 223demo code and made minimal changes to the new .h file. I set the walk_around option to 1 to test it on the ground but when I switched on the AP, the motor turned on. This surprised me because I thought the goal of adding the walk_around option was to be able to walk around with the motor engaging. So I set the walk_around back to 0 and did a trick I learned from Peter M. I bypassed the AP and plugged the ESC directly into the Rx. Now I could have direct control of the throttle and do a safe walk around.
    In RTL the ailerons now direct me away from home and in WP mode the ailerons direct me in the opposite direction from WP1. Now we're making progress!!! I switched the reverse_roll and now the roll navigation is correct!!! Got her up in the air but she went into the death spiral when switching to RTL or WP. Got her back down and realized that the stabilization(thermopile) roll was reversed. I also realized later that I had not corrected the reverse_x_sensor for my setup. Once I get the navigation and stabilization outputs coordinated, I'll be good to go. The flight test log can be found here.
    http://around.In/
This reply was deleted.