- All the ArduPilot 1.0 functions: programmable 3D waypoints; return-to-launch mode, in-flight reset ability, fully programmable actions at waypoint and totally expandable board.
- Now integrates the stabilization and navigation functions, eliminating the need for a FMA Co-Pilot and vastly improving waypoint tracking
- Controls elevator and ailerons/rudder. Throttle control coming in 2.1
- "Fly-by-wire" mode stabilizes the aircraft in RC mode, duplicating the function of the FMA Co-Pilot
- Stores home waypoints and sensor calibration in EEPROM, so they are retained even in the case of a system restart
- Controls altitude with the elevator, vastly improving performance in wind
- Currently optimized for the three-channel EasyStar. Versions have also been tested on Funjet and four-channel Superstar (code coming soon)
- Simple in-field calibration process
- Can use any thermopile XY sensors (default settings are for the FMA sensor, but Paparazzi, AttoPilot and custom sensors can also be used)
- Currently supports the EM406 GPS. Support for Locosys and Ublox GPS modules coming soon
- Uses "chained PID loops" to combine the stabilization and navigation functions seamlessly
- ArduPilot board ($24.95)
- EM406 GPS module ($59.95)
- A FMA XY sensor ($42.95; if you already have a FMA Co-Pilot, you can use its sensor). If you're buying the FMA sensor by itself, you'll also need to purchase a cable.
- A FTDI cable, such as the Sparkfun ($13.95) or Adafruit ($20) ones
- ArduPilot 2.0 code (Free)
- Uses Z sensor for self-calibration in the field
- Uses small desktop app to load ArduPilot settings and waypoints, without having to work with code
- Adds throttle to altitude control, improving accuracy and wind performance
Comments
((target_distance x sen(target_bearing)) x (.000009xcos(home_lat)))+home_lon = referenced lon waypoint.
But is not the most accurate way, but believe me, you will not even note it.
If you want to use referenced coordinates use your calc and do this:
((target_distance x cos(target_bearing)) x .000009)+home_lat = referenced lat waypoint.
((target_distance x sen(target_bearing)) x .000009)+home_lon = referenced lon waypoint.
But carefully with the sign's the formula should calculate the right one... And is not the most accurate way, but is good enough.
Want to add some waypoints but im not too sure if what I want to do is correct. Ive got google earth open & my coords, but, from the looks of the code below the waypoints are setup in relation to your home possition?
So if I want to plot out a flight in google I first need to find where Iam going to turn on the uav & then calculate the distance to each waypoint for ardu?
Cant I just export the coords from google and paste them... somewhere?
Thanks,
Max
//0.000009 degrees is about 1 meter...
Leave the 1st one alone for RTL yes?
wp_alt[0]=50;
//wp_lat[0]=0; Do not change unless you want to override home position...
//wp_lon[0]=0;
Where would I put the coords from google?
wp_alt[1]=50;
wp_lat[1]=wp_lat[0]+0.002000; //Travelling north about 200 meters from launch position....
wp_lon[1]=wp_lon[0];
I am in awe of the work that is going on here. I've never seen an open source project moving along, at this pace, with amazing people participating...from every level and angle, worldwide. A beautiful artlike kinetic. Bravo!
You might want to keep the AVR programmer, however. It's really handy for reloading bootloaders or otherwise rescuing chips when things go wrong. Which they do, more often than we might like.
But just to be clear, the "2.0 board" is the same as the "1.0 board". It's just the software on the main chip, which you flash with Arduino, that's been updated.