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
    Fefenin,

    The number of waypoints does not need to be declared as it's derived. We have an issue with waypoints over 21 (Jordi is working on that) but no issues that we know of for less than that. We don't know what you mean by "strange things" but don't confuse not having airframe-specific config settings dialed in right with logic errors.
  • @Chris and Jordi

    i guess the right numbers of waypoint should be declared into the "ArduPilot_EasyStar_V23.pde" file
    otherwise it is doing strange things

    i guess that could be Brent's issue:
    default setting is:
    byte wp_number=3; //Number of waypoints defined.... Go to to Waypoint tab...

    now my question is ... does the config tool changes this variable to the right number when writing to EEprom?

    @Peter thank's !
  • 2nd one:

    Video 2
  • Here are the direct links to the grounstation videos including the googleearth plots...

    Video 1 Groundstation
  • Here is my video list earl: There are 2 groundstation videos up there...
    Video Library
  • Earl, I'm building the ArduStation while waiting for some plane parts. I'm also writing a ground station program in java which will used with the AS board. Not that I don't like Labview but I just wanted something else to use and be able to modify easily. I agree with you - AS will be probably be my main test bed generator. If I get the alternate program working well, I'll share it with everyone.
  • Ahh... I found out why my hand to sensor tests were not working as good as it should. BAD CONNECTOR at the XY sensor. Man I am glad I didn't fly yet with it. I soldered the wires directly. Problem gone!
    Now the hand by the sensor front,back,and sides do what I thought they should! Never trust connectors.
    Peter,
    If you can, post some video of the ground station.I use XBee Pro 900mhz. Great range.
    Earl
  • I agree with chris, its probably missing the waypoint and flying back to it. Brent if you want to lower the sensitivity as to how close it needs to be to a waypoint to get a Check off, then change the radius in the waypoint config tool. If you have it say at 20, then change to 40. If you have it at 50 then change to 70. Add 20 points to it first to try it out, this might help. This allows the radius for success against a waypoint to be wider then say a laser bullets point. :)

    I have mine set to 20, it works really well. But when your first flying the plane you may not have all your settings locked and tuned, so the best thing to do to get a full waypoint flight is to increase the radius, that way you can observe more full flights and see what needs tuning. Try it, im sure it will help you out on this issue.
  • Earl,

    I fly with both the xbee pros and xtends. I have customized my Groundstation with labview.
  • 3D Robotics
    Brent, yes, if you don't have telemetry you're going to have to do a bit of guesswork. I would indeed start with increasing the radius to 30 or 40 and see what happens.
This reply was deleted.