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

  • Not knowing Labview too well, can we add reading the ground station XBee with +++ (OK) ATDB (xx) and displaying the RSSI on the ground station somewhere ? The (OK) is the XBee saying ready and (xx) is the RSSI from the XBee ATDB command.
    I know doing a +++ to get the XBee's attention disrupts the flow of data to the ground station, but how about once every 10 seconds or so ?
    Earl
  • Is there many out there doing the telemetry and ground station ? I don't see too many reports. Mine is invaluable for testing !
    Earl
  • Thanks Chris,
    Well I’m not quite sure how to enable the telemetry, I mean I don’t have my Xbees yet or ground station setup.
    The way that it turns away from WP1, it sure looks like it found its mark and going to the next. I got the role and heading dialed in now that it steers a pretty steady course. Other than that I’m not sure what other gains to play with.
    I thought next that I would increase the radius limit (config tool) from the default 20 and see what happens.??
  • 3D Robotics
    Brent,

    Enable telemetry and watch what's going on the laptop or ArduStation. It's probably that it didn't actually hit the waypoint and is going back to get it again, which means you need to tweak gains etc, but you can't know for sure if you're not getting telemetry.
  • Awesome Jordi, thats a great idea to add it to the nav and then reset after each waypoint. Will help compensate for the winds quite well if you do that.....

    @Fefenin, haven't forgot my friend. Zipping it up now and pm'ing you...
  • Missing Waypoints
    Had a good weekend to do some test flying with the paraglider.
    The first couple flights were very drunk driver like, and I was able to tame that down with adjustments in the header.
    But I’m scratching my head with this one. Over the weekend, I tried two different courses, one having five waypoints and the other having six waypoints.
    Neither of the courses was I able to complete! For example, this mornings flight started looking great, she leveled off and flew towards waypoint one, then turned and headed for WP2, but instead of going to WP3, it turned and headed for WP1 again then back to two, then seemed to come home and linger over head.

    With the config tool, I’m able to write and read my WP’s ok, but don’t know why it won’t go to WP3, 4 and 5 to complete the course.

    @Jordi, I’m curious about your last post about adding integrator to the navigation system to solve missing waypoints. Could this be where I’m having a problem?
    I’m also using the walk around mode, that shouldn’t be the reason, right?
    Thanks,
    Brent
  • @Jordi,
    could you explain a bit further the integrator thing?

    i'm really interrested on that (just to know)

    @Peter
    didn't receive any private mail, is it normal? (i'm not in a hurry, but just asking)


    @everyone
    i guess i'll fly with all the gear tomorrow cause my plane is finished tonight:

    sides are on...
    canopy is cutted
    main gear is stronger and lower

    need to put the sensors and ardupilot and i'm on for a fly
  • Developer
    Peter,

    Nice video, i thing i should add integrator to the navigation system, that will solve the problem of missing waypoints a little bit, also will compensate the high winds. Then after touching the waypoint i should reset the integrator and star again for the new waypoint.
  • Developer
    Mike,

    You should at least see noise coming from the sensors.

    Regards.
  • Chris,

    I dont recall it doing so but I'm going to re-flash everything with fresh code and test it all out again this afternoon. I'll report back! Thanks for the support you guys are the best.
This reply was deleted.