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

  • Developer
    BTW Danilo,

    The max speed of XCS is 9600 bps.
  • Developer
    Danilo,

    You need X-CTU to program your Xbee's:
    http://www.digi.com/support/kbase/kbaseresultdetl.jsp?kb=125

    The software is a GUI easy to use. Don't forget to check the "Always Update Firmware" to permanently save your stuff.
  • Hi Jordi!!!

    I have 2 xbee 900 XCS and I don't know how to configure it to use with my ground station.The problem is the baud rate that is in instructions manual the program refuse it, only function with 9600, but for this the ground station is not working.I have a ardupilot AT328 and I did all how is in manual instruction.
    What's may be my problem?!!!

    Regards.
  • Developer
    Paul BTW, i just read again my post and i look like a mad or something but I'm not, i was hurry actually (Sorry!). In other words you are not giving (in my opinion) enough data, but even if you give me all your information i don't have plenty of time to analyze it, sorry about that.
  • Developer
    Thanks Bryan!I I will suggest Chris to add that into the manual.

    In the mean time i will add another debug option that will read the IR sensors and pulse the servos directly, so you can verify if your hardware setup is correct easily.
    http://manual.In/
    See related links to what you are looking for.
  • >Paul,
    Make sure that with your settings, you have the navigation roll and stabilization roll (IR sensor output to the aierons/rudder) going in the correct direction. In other words, try switching back the servo direction so it flies in the right direction and then check the rudder/aileron direction when you roll the plane and make sure the sensor output acts to stabilize her. If the stabilization is reversed, you'll definitely get the "death spiral".
  • Developer
    Paul,

    How i suppose to know that with the information your are giving me? Seriously, i need to see your code, your header, your hardware setup and orientation, the direction of your servos when you pulse them positively, etc. Maybe like that i can help you, but to be honest i don't have time to check all the setups of everybody individually (That would be and endless job!). You have enough tools in the system and telemetry to debug and figure out that by yourself. If you have minor questions of what happens if i do this or that i can help you. =)

    Jordi
  • One quesyion for you. Doing a test on the ground it appears to work. when flying as soon as I switch to atuo it spirals down. Ok so I alterd the servo direction in the .H file which stops the spiral but it flys in the wrong direction. I am not sure if I change the roll direction, will it spiral down again.
    Paul
  • Developer
    Maybe i will make some more tests to improve the tuning in uBlox GPS.
  • Developer
    Peter,
    No i didn't say that. Why?
    I'm sorry to hear your unsuccessful fly. Anything else i can do for you? In the mean time i will polish the comments and i will prepare the official release of Ardupilot 2.3, that has been successfully test in my aircraft.
This reply was deleted.