[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
Let's take this to PM. It's not even clear to me that you've loaded the code properly. Please send me a PM telling me exactly what the LEDs are doing when you power up and we'll take it from there. Let's not clutter this thread up any more.
David is right. Start over. Follow the manual, step by step. Once you've done that if you're still having trouble come back here. But please don't make us rewrite the manual, comment by comment, here.
I guess you must have skipped the ardupilot manual, it is a must-read material, pls spend some time going thru the whole manual :)
Refer Here for changing gps protocol
did u change the gps protocol in the header file (easystar.h) ?
EM406 --> use SiRF
That's great that you went the extra mile to rig up a test bed for ground tests and if more people put in this kind of effort there would be a lot less questions asked. But, come on. To claim that the system works because you performed a 2-dimensional ground test with the stability control loop excluded is a little far fetched.
Put your setup in a plane, fly waypoints and I'm all ears.
Yes, It would be nice to add another function to the config tool, to SAVE our different waypoint playgrounds, and if that can be put on the to-do list, that’s OK. The method that Jordi came up with went way over my head. Just too old to understand.I couldn’t stand turning my radio on and off hundreds of times to test this complex system, so I built this test bed. I’ve walked down the street, put it on the hood of the car, and showed it to my friends at the field, all self contained and testing the navigation system without carrying the airplane or radio. Interested??
Jordi and Chris’s (and all), system works! And you can save yourself and his a lot of time by going back and reading the forums, a wealth of info is back there. I wouldn’t put an airplane in the air without testing it over and over again without the ground test first.
Just turning on the power switch and pulling off the bind plug can give you a different scenario if you are not consistent. And making small changes in the header (one that has been proven) can make a lot of difference.
Everyone that takes this project on, has to be prepared for some setbacks, big learning curves, maybe a broken wing, oh wow, and then, this is cool as shit!! That’s why we’re all here.
Let’s take a pole of hands and see who can help and give Jordi a break. He’s done for us something that we could not have done ourselves, and given us a really exciting addition to the hobby of RC flying.
I say, let the man do his schooling and watch “us” work out the problems we’re having.
You guys that have had proven flights, step in, PLEASE.
That's what I'm talking about Greg an Paul!!! yeha
Brent
you might want to double check the home position with the config tool after calibration :)
make sure it is not Lat Long = (0,0)
-
66
-
67
-
68
-
69
-
70
of 84 Next