- 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
--Super-easy field calibration
--Better angular resolution for turns (XY alone is good at spotting level flight but not as good at maintaining a 15 degree angle, say)
This may be a silly question but in your IR conversion to degrees do you assume that the midpoint is 511? Would it not be better to calculate an average IR value in the level position and reference to this instead?
Thanks for your time.
Sirk
This may be a silly question but in your IR conversion to degrees do you assume that the midpoint is 511? Would it not be better to calculate an average IR value in the level position and reference to this instead?
Thanks for your time.
Sirk
better fly ?
I dropped the "-c stk200" from his command line example because I was using the tinyUSB AVR programmer from Lady Ada.