Your status should read “submitted” when you submit the FTR to our Flight Test Coordinator.
Once the coordinator approves, and a date/location/drone has been assigned, the status will change to “waiting for sub team review”. Once all sub-teams have reviewed and signed off, the status will change to “approved”
(To be checked once reviewed by sub-team representative)
Mechanical
Electrical
EFS
Autonomy
Operations
Date of Request
Goal Summary
Houston AutoTune / Pilot Training w/ Houston
Status?
APPROVED
Desired Airframe
Houston / Pegasus / Tubie
Desired Date(s)
Approx Date range for help out with FTC Scheduling
🥅 Testplan - to be filled out by requesting team
Create ONE table per test-item. Eg: “Landing pad images over asphalt”, “landing pad images over grass”, “landing pad images over grass, high” should all be unique tables.
Use each expand to capture one series of tests, eg “Landing pad detection” or “Auto-tuning”.
Card 1: Houston Discovery Flight
Card 1, Test #1: Houston un-tuned parameter check
Prerequisite
Objective
Knock off Criteria
Initial Frame paramaters set on Houston
using Alt-A utility tool
Familiarize pilots with system response of untuned drone.
Airframe unstable
Battery < 10.1v overall, < 3.3v/cell
Flight Time > 10 minutes
Procedure
Outcome
Switch into Attitude/Stabilize mode using FM1 button
Drone beep,
Mission planner shows “STAB” or “Stabilize”
Takeoff in Attitude mode, control check in each direction.
Full stick deflection on each axis
Full stick deflection “rocking” on each axis
Watch for drone response, how “long” it takes to get to the setpoint.
Switch to Loiter mode, using FM3 button
Drone beep
Mission planner shows “LOIT” or “Loiter”
Drone holds position
Full stick deflection, same as (2)
Watch for drone response
Watch for drone stability
Land
Don't crash
Card 2: Houston Autotune
Card 2, Test #1: Houston Autotune, Pitch
Prerequisite
Objective
Knock off Criteria
Autotune research done.
Rpi, Camera removed.
Aircraft solid, screws tightened, etc.
ATUN_Axis set to pitch
get pilots/GSO familiar with the procedure of how to autotune
Autotune houston in pitch axis
autotune complete
Airframe unstable
Battery < 10.1v overall, < 3.3v/cell
Flight Time > 15 minutes
Nearby obstacles distance < 30m
Procedure
Outcome
Switch into Loiter using FM3 button on tx16.
Drone beep,
Mission planner shows “LOIT” or “Loiter”
Takeoff in Loiter, fly to a safe distance and around 8 -12 m altitude
Watch for drone stability, ensure systems OK.
Switch into Autotune by using FM5 button on TX16.
Drone beep
Mission planner shows “ATUN” or “Autotune” in HUD
Wait for Autotune to complete
Pilot: Watch for drone stability and clear of objects. Do not touch sticks unless necessary
(still have control ability when nearby object become close)
GSO: Watch for autotune messages, make sure no failures. Enusre order of messages correct.
Autotune complete message received
Crosscheck atune complete
GSO:
Pilot: observe drone not significant movement
Switch into Loiter, fly back to a closer distance
This will revert to old tune.
Ensure system OK, sensors OK
Switch into autotune, land, disarm, power and power cycle + battery check
This will apply new tunes and then save them.
We will do a 3-axis controls check once all autotune is complete.
Card 2, Test #2: Houston Autotune, YAW
Prerequisite
Objective
Knock off Criteria
Autotune research done.
Rpi, Camera removed.
Aircraft solid, screws tightened, etc.
ATUN_Axis set to YAW
get pilots/GSO familiar with the procedure of how to autotune
Autotune houston in pitch axis
autotune complete
Airframe unstable
Battery < 10.1v overall, < 3.3v/cell
Flight Time > 10 minutes
Nearby obstacles distance < 30m
Procedure
Outcome
Switch into Loiter using FM3 button on tx16.
Drone beep,
Mission planner shows “LOIT” or “Loiter”
Takeoff in Loiter, fly to a safe distance and around 8-12 m altitude
Watch for drone stability, ensure systems OK.
Switch into Autotune by using FM5 button on TX16.
Drone beep
Mission planner shows “ATUN” or “Autotune” In HUD
Wait for Autotune to complete
Pilot: Watch for drone stability and clear of objects. Do not touch sticks unless necessary
GSO: Watch for autotune messages, make sure no failures. Enusre order of messages correct.
Autotune complete message received
Crosscheck atune complete
GSO:
Pilot: observe drone not significant movement
Switch into Loiter, fly back to a closer distance
This will revert to old tune.
Ensure system OK, sensors OK
Switch into autotune, land, disarm.
This will apply new tunes and then save them.
We will do a 3-axis controls check once all autotune is complete.
Card 2, Test #3: Houston Autotune, Roll
Prerequisite
Objective
Knock off Criteria
Autotune research done.
Rpi, Camera removed.
Aircraft solid, screws tightened, etc.
ATUN_Axis set to roll
get pilots/GSO familiar with the procedure of how to autotune
Autotune houston in pitch axis
autotune complete
Airframe unstable
Battery < 10.1v overall, < 3.3v/cell
Flight Time > 10 minutes
Procedure
Outcome
Switch into Loiter using FM3 button on tx16.
Drone beep,
Mission planner shows “LOIT” or “Loiter”
Takeoff in Loiter, fly to a safe distance and around 8-12 m altitude
Watch for drone stability, ensure systems OK.
Switch into Autotune by using FM5 button on TX16.
Drone beep
Mission planner shows “ATUN” or “Autotune” in HUD
Wait for Autotune to complete
Pilot: Watch for drone stability and clear of objects. Do not touch sticks unless necessary
GSO: Watch for autotune messages, make sure no failures. Enusre order of messages correct.
Autotune complete message received
Crosscheck atune complete
GSO:
Pilot: observe drone not significant movement
Switch into Loiter, fly back to a closer distance
This will revert to old tune.
Ensure system OK, sensors OK
Switch into autotune, land, disarm.
This will apply new tunes and then save them.
We will do a 3-axis controls check once all autotune is complete.
Card 3: Houston tuned parameters check
Card 3, Test #1: Houston tuned parameter check
Prerequisite
Objective
Knock off Criteria
Autotune card 2 Test 1-3 complete.
Characterize tuned system response
Compare against un-tuned system response.
Airframe unstable
Battery < 10.1v overall, < 3.3v/cell
Flight Time > 10 minutes
Procedure
Outcome
Switch into Attitude/Stabilize mode using FM1 button
Drone beep,
Mission planner shows “STAB” or “Stabilize”
Takeoff in Attitude mode, control check in each direction.
Full stick deflection on each axis
Full stick deflection “rocking” on each axis
Watch for drone response, how “long” it takes to get to the setpoint.
Explain what capacity you need, what needs to be mounted, etc.
Necessary items:
N/A
Flight characteristics needed:
Require long flight endurance (needs more batteries)
Comms / Support needed:
TBD
🫂 Mandatory Attendees
This is a section for all attendees from your subteam which will be present for this flight test. (because they are testing their products, or otherwise)
Raspberry Pi can collect images with the $200 CV Camera
Test the imaging repository with the Raspberry Pi and confirm images are taken and stored on the SD card
Edit the rc.local and ensure that image collection code runs on Raspberry Pi startup
Raspberry Pi can be powered onboard the drone. Need help from the Electrical team.
Raspberry Pi and $200 CV Camera are mounted onto Houston. The $200 CV Camera needs to be pointing in the downards direction.. Need help from the Mechanical team.
Flight test location booked
Drone Registration -
Houston
Tubie
Pegasus → flying on vanny registration
Ensure we have good props for Pegasus after last tests crash
Telemetry Verified Functional - Nathan Green to verify with new LTE connectors
Nolan Haines Schematic for and delegating manufacturing of anti-spark connector configuration
Daniel Puratich to update template with all the new things he added to this template this time
Fire extinguisher - we dont have one, theyre out of our budget gg
Spare foam - not needed
hot glue gun w/ hot glue stick - not bringing that
harnesses
ratchet set
battery removed for velcro (thin 3d printed thing) for pegasus
Wrestrc
Airfame assembled
ESCs/flight controller wired
Radio equipment tested
Channel mappings
Flight modes
Motors tested
Check DSHOT configuration (DS300, bidir?)
Motors plugged into correct pins on pixhawk
Verify motors 1,2,3,4 in motor test go in the correct order
Verify motors in a,b,c,d configuration is correct order
verify rotational response of motors is correct (with more than just audio), move the drone around and check each motors response individually
Wiring secured (Harnessing)
End-to-end test (neglecting props)
Props require a little gold ring which we did not use during the strap down test, may have caused extra vibrations.
Check the center of gravity - CG is off quite a bit but because only running two batteries and much less hardware then anticipated it will be reasonable for this test
All components not on the airframe that are required should be in the flight box (e.g. props & prop nuts)
Airframe payload - Raspberry Pi + $200 Camera
Mount to airframe pointing downwards (exact angle doesn’t really matter)
Spare parts
Props
Houston props
Peggy props
Airframe components (landing struts, arms, etc)
wings nuts - n/a
prop nuts
any detached components such as angle mount - none needed
Hardware to assemble these components
Spare Electronics - we dont have much
ESCs
Motors
Flight controllers
Receiver
Ground station Software updated
Pre-Departure Checklist
Take the WREST RC entrance card - must do!!
Only attach props directly before flight (keep off at all other times)
Read the flight plan to the team (that was made a week ago)
Purpose of flight
Plan of action
Success criteria
Delegate and brief on flight line roles
Safety Briefing
Key flight characteristics to observe
Key system characteristics to observe
Measurements to be made
“Knock off” criteria (anyone can call)
Specify Pegasus Flight area planned, hard land and disarm boundaries set. Ensure visual observers are aware of this and can visually verify boundaries. - Hardy Yu
Houston Trainning Pre-Flight Check
Air Frame
Check all antennas, ensuring they are secure and in good condition
Check the battery emplacement and secure attachment and ensure there are no cracks
Check that all lights are operating normally
Check that all sensors are secured and clear of any obstructions
Check that the GPS is receiving satellites and providing a navigation solution
Inspect top and bottom of air frame arms for cracks, loose parts, or signs of damage
Landing Gear
Check landing gear is secure
Inspect skids or wheels, especially attachment points
Motors
ensure all motors free-spin correctly
Ensure wires secured and not at risk of shorting
Ensure motor mounts secure.
Propellers / Rotors
Ensure propeller is secured
Check for nicks, chips or cracks
Ensure prop direction is correct
Ensure prop mounting is secure
Batteries
Inspect to ensure there is no signs of swelling, external leaking or other defects
Battery wiring and connectors from the battery are connected securely
Batteries (and spares) are adequately charged
Wires are not pinched
Control Station / Receivers / Transmitter
The battery and spare batteries if required are adequately charged
Control Station device and cables are properly connected and functioning
