Pre-Flight, Way Point Planning - Headwall Nano-Hyperspec Operation Manual

(6) The two circled lines show the GPIO and Trigger check box, which are the controlling features for remote
triggering.
(7) Select the corresponding GPIO value for the connected wire, refer to the Nano manual for GPIO options.
(8) Check the "Trigger is used..." box to set the trigger to behave as a switch, i.e. power in and the device captures,
when power stops the capture ends.
(9) Uncheck the box if the trigger is to operate as a toggle, i.e. a pulse starts the capture and a second pulse ends the
capture.
(10) After configuring the Nano for remote trigger, test the operation with the following steps:
(a) With the Nano powered ON engage the trigger. Verify the blue LED lights on the Nano for the duration of
the trigger event. When the trigger event ends, verify the LED is green.

3. 12 PRE-FLIGHT, WAY POINT PLANNING

To obtain useful data cubes during airborne operations the UAS flight path needs to be outside of the defined capture
polygon. The minimal distance, from Headwall's experience, should be 15 meters, preferably 25 meters. The reason is
that the sensor needs to be triggered OFF during the UAS maneuvers to change direction. Due to speed and commercial
GPS resolution accuracy, the 15-25 meter was empirically developed. Also an altitude of approximately 75 to 150 meters
for a UAS supporting a Nano is suggested. The UAS should use a brushless gimbal for a steady scan view, without chatter
or interference.
Preparing for autonomous flight with a UAS requires defining the waypoints in the UAS system software. Each system
has its own software for defining the flight path and profile. For the example in this manual, generic plans will be
identified.
Figure 3-1. Settings, Sensor Tab.
GPS/IMU
51