[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:
- ArduPilot board
- Shield expansion kit with airspeed sensor
- GPS module (uBlox5 recommended)
- XY and Z sensors or ArduIMU+
- FTDI cable for programming
- [Optional] Two Xbee modules for wireless telemetry. This one in the air and this one with this antenna on the ground/laptop side. You'll also need two Xbee adapter boards. You can connect the airborne Xbee adapter to Ardupilot Mega with jumper wires.
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:
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.
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:
- A GPS logger to record your mission and play it back in Google Earth
- A tiny video camera to record the flight
- A wireless video setup to see realtime video from the air
Comments
Thank you Peter for all your flight testing, and Jordi of course.
I think I’ve got all my ground testing done because of the excellent inputs this last week, and now I believe I’m ready to strap it to an aircraft.
Seems that you need to adjust your servos. I added a debug option in the header called CALIBRATE_SERVOS. When you enable it you will see your servos moving right, center and left or Left, center and right (how much they move left and right must be equally). You need to be sure is well calibrated. If the center position is a lot to the left or right (looking into your rudder) means you need to either adjust yours servo externally by removing screw of your horn and center it or by software playing with the "SERVO_MAX" and "SERVO_MIN" located in lines 3.1 and 3.2.
THE ONLY reason why sometimes you fly excellent and the second time don't so much is because the IR sensors are bad calibrated. The sensors suppose to calibrate over time, but at the firsts minutes may be very wrong, depends. Also is very important to level the aircraft when you remove the bind plug after calibration, so you can ensure a good calibration at the beginning.
In general, you need a radio with a toggle switch (to turn the autopilot on or off). I don't know of any radios with less than six channels that have toggle switches.
You need channles for throttle, elevator, rudder (or ailerons ) but also a toggle switch for controlling the ardupilot...
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
I decided to put the EM406 GPS back into NMEA mode (just use SIRFDemo) to test for better H resolution. Here are the results. See my earlier post for how to view this in 3D. Updated analysis:
Much better continuity of height data at 9600 BUT there is still some drift (10-15m) in the height measurements. I would like to see the results of the uBlox if anyone can present it. In the meantime, I got a Parallax GPS unit based on the folks at www.polstargps.com
Will post the results when available...
@Bryan
I have not tested walkaround deeply, went to one waypoint and it seems to deflect both ways properly. Whatever causes the tight right turns is in the code, maybe a setting needs to be changed, etc...or I can always try a larger radius tomorrow to see if it softens it up. But I would love to know Jordis thoughts here...
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?