Thread: Discussion The AttoPilot project
View Single Post
Old May 25, 2009, 03:30 PM
Irv is offline
Irv
Find More Posts by Irv
Irv
AKA the"Old Flyer" KI6SPO
Irv's Avatar
Carlsbad, CA
Joined Aug 2004
104 Posts
The "flying Breadboard" is to be used to evaluate all of the components of the UAV system before transferring to the next airframe. We kept a record of each flight and the changes made between flights. I made up a check list and mission log form.


UAV MISSION CHECK LIST

FLIGHT _____


DATE: ______ AIRCRAFT: _______________ LOCATION: _____________

TEMP:______ WIND SPEED/DIRECTION _____/_____ CLOUD COVER_______


AIRCRAFT PRE FLIGHT:

[ ] Control Frequency/ clear (pin) _____________

[ ] Check and record flight battery voltage. _____________

[ ] Check and record other batteries: _____________

[ ] Range Check

[ ] Verify proper CG

[ ] AttoPilot SD Card # installed _____________

[ ] RC Transmitter set to proper aircraft

[ ] AttoPilot mode selection verified: RC, ARC, LARC, AUTO

[ ] Verify number of GPS satellites ____________

[ ] Verify pitot and static tubes are clear

[ ] AttoPilot mode set to RC

[ ] Check aircraft control surfaces move are in correct direction,
deflection

[ ] AttoPilot mode to AUTO, Check control surface movement is correct
for Roll and Pitch

[ ] AttoPilot mode back to RC

[ ] Take off and start timer

[ ] Post flight. Record flight battery voltage. _____________






MISSION LOG

Aircraft Configuration: ___________________________
______________________________________________

Aircraft changes since last flight:
______________________________________________
______________________________________________
______________________________________________

Software (SET) changes since last flight:
______________________________________________
______________________________________________
______________________________________________
______________________________________________

Payload: _______________________________________
_______________________________________________
_______________________________________________

Mission Objectives: ______________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________

WP File configuration:
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________
_______________________________________________

Flight Data: _____________________________________
_______________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________

Additional Notes: _________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________
________________________________________________

SET File logged as: _____________________________________

WP File logged as ______________________________________

LOG file logged as: _____________________________________

form updated 05/17/09

You don't need to have a laptop at the field but it makes the tuning process go much faster.

Make sure there is no LOG file on the MicroCard for the first flight of the day. After each flight you should rename the LOG file. If you don't the second flight will have its data appended to the same LOG file as the first flight. That is OK but that can make the Google Earth plot very busy.

I download the SET, WP, and Log files to the main computer after each session and save them as SET.date, LOG.date and WP.date
(ex. SET.05-24-09) That way I can recreate any session if questions come up later.

All of the first phase goals have been met.
1) Demonstrate the ability of an RC airframe under autopilot control to perform tasks such as fly a specified path at a set altitude and airspeed, and release a streamer at a designated point along the flight path.
2) Learn as much as possible about the "care and feeding" and the potential uses of the AUV system.
3) Do all of this at as low an initial cost as possible.

It has taken us 30 flight to get there.

AttoPilot has done everything we have asked of it!

Next - add the 9XTend TX/RX modems to the system for real time flight display and control
Add the video system and test for compatibility.
Irv is offline Find More Posts by Irv
Reply With Quote