H520 Checklist and Field Outing 1
Introduction
In this lab we planned to gather data with an H520 (Figure 1) UAV equipped with the E90 Yuneec Sensor. The GCPs we used were Aeropoint Markers and were positioned around the field. The class was split into two different groups, in the interest of saving time. One group would observe the preflight portion where Professor Hupy readied the UAV while the other group would go with Evan to position and activate the GCPs. I, in the preflight group, observed the compass calibration, and the accelerometer calibration by Hans and Hupy while Hupy explained what he was doing and what to look for. Once the GCP group got back, we were just about finished with the preflight and ready to fly. Professor Hupy asked if anyone wanted to fly and Lucas agreed to do it. The UAV started up without a hitch, ascended to about 30m, began to move along it’s preprogrammed path, and proceeded to drop to the ground. The payload/ camera with gimbal somehow remained intact but the rest of the UAV was not as lucky, with the landing gear snapped at the base and the folding arms suffering a similar fate (Figure 2).
Obviously, this was not ideal, but in the interest of not having the excursion be a complete waste of time, we have been instructed to create a suitable preflight checklist for the H520. Along with that, we are to include a checklist for during flight and post-flight.
The actual lab, collecting data at oblique angles, will be continued at a later date.
Compass Calibration, account for underground cables
Altitude Assessment, 80m
Checked that we’re not in D airspace
Sensor: E90 Sensor Yuneec
GCP: Aeropoint markers
Datum: Nat 83 2011
Split into groups, in the setup group not doing GCPs
Mission planning done by Hans and Hupy
Set bounds of the mission in the
Nadir, angles of lines, martell
Link the controller with the drone, link management > having trouble with connecting
Calibrate compass and accelerometer
For compass Initiate, rotate, roll. Lights indicate the axis to rotate for calibration.
Accelerometer. Hold on different sides and wait for beep.
Gimble calibration.
Drone crashed
GCP retrieval. Use maps and and descriptions to find them and retrieve them in the reverse order they were placed. Push button to turn them off. (Here I took pictures to help with retrieval)
Post crash:
It was determined that that likely cause of the crash was a failure to fully install the batteries until the latching mechanism was triggered (clicked). If this was the case then the batteries would have slipped out of position causing a complete loss of power for the system.
In this lab we planned to gather data with an H520 (Figure 1) UAV equipped with the E90 Yuneec Sensor. The GCPs we used were Aeropoint Markers and were positioned around the field. The class was split into two different groups, in the interest of saving time. One group would observe the preflight portion where Professor Hupy readied the UAV while the other group would go with Evan to position and activate the GCPs. I, in the preflight group, observed the compass calibration, and the accelerometer calibration by Hans and Hupy while Hupy explained what he was doing and what to look for. Once the GCP group got back, we were just about finished with the preflight and ready to fly. Professor Hupy asked if anyone wanted to fly and Lucas agreed to do it. The UAV started up without a hitch, ascended to about 30m, began to move along it’s preprogrammed path, and proceeded to drop to the ground. The payload/ camera with gimbal somehow remained intact but the rest of the UAV was not as lucky, with the landing gear snapped at the base and the folding arms suffering a similar fate (Figure 2).
Obviously, this was not ideal, but in the interest of not having the excursion be a complete waste of time, we have been instructed to create a suitable preflight checklist for the H520. Along with that, we are to include a checklist for during flight and post-flight.
The actual lab, collecting data at oblique angles, will be continued at a later date.
 |
| Figure 1: H520 in all its glory |
 |
| Figure 2: Alas, poor Yuneec |
Preflight: Location
- Check to make sure that the area that you will be flying in is either in uncontrolled airspace or you have received permission from the FAA.
- If within five miles of an airport, inform them that you will be conducting operations.
- Review the flight path to ensure that you will not be flying over moving vehicles, groups of uncovered people, or around other aircraft.
- Also make sure that the flight path has is clear of obstructions such as trees or buildings that may pose a collision hazard.
- Check for NOTAMs that pertain to your flight and submit your own if you’re close to an airport.
- Check the weather for any reason that the operation might have to be canceled such as clouds too low, winds to high, extreme temperatures, or low visibility.
Preflight: Physical Inspection
- Check that the battery is sufficiently charged for the planned mission keeping in mind that the battery should be stored at 30% - 50% charge, should never be fully discharged, and never be stored at full charge.
- Inspect the battery for any damage that might prevent it from operating correctly.
- Inspect the rest of the drone for any damage or obstructions to the arms, props, landing gear, or body that would impede proper operation.
- Make sure that the props are seated correctly and secure.
Preflight: Software
- Calibrate the compass and accelerometer
- Make sure that you are using the most recent version of DataPilot.
- Gimbal has full range of motion and does not get stuck on anything
- The drone/ sensor are connected to the data station via wifi
- A minimum of 10 GPS satellites are recommended for accuracy
- Failsafes should be configured to suit the location and situation
During Flight:
- Take off ensuring that everyone in the vicinity is aware of this
- Monitor battery life for any abnormal shifts in battery level
- Constantly monitor the surrounding airspace for any aircraft
- Be aware of any obstacles that may be close to the flight path and be prepared to take manual control in the case of unexpected circumstances
- Always maintain visual line of sight of the aircraft
- During landing be prepared to take manual control in the case that the auto land goes wrong.
Post-Flight:
- Turn the power on the drone off before approaching it for inspection. Make sure to power down the aircraft before powering down the control station.
- Inspect the body, props, and landing gear for any damage that may have occurred during flight
- Remove the props
- Repack the drone and all of its’ components
Field Notes:
Preflight
Compass Calibration, account for underground cables
Altitude Assessment, 80m
Checked that we’re not in D airspace
Sensor: E90 Sensor Yuneec
GCP: Aeropoint markers
Datum: Nat 83 2011
Split into groups, in the setup group not doing GCPs
Mission planning done by Hans and Hupy
Set bounds of the mission in the
Nadir, angles of lines, martell
Link the controller with the drone, link management > having trouble with connecting
Calibrate compass and accelerometer
For compass Initiate, rotate, roll. Lights indicate the axis to rotate for calibration.
Accelerometer. Hold on different sides and wait for beep.
Gimble calibration.
Drone crashed
GCP retrieval. Use maps and and descriptions to find them and retrieve them in the reverse order they were placed. Push button to turn them off. (Here I took pictures to help with retrieval)
Post crash:
It was determined that that likely cause of the crash was a failure to fully install the batteries until the latching mechanism was triggered (clicked). If this was the case then the batteries would have slipped out of position causing a complete loss of power for the system.
