# Troubleshooting/FAQ

## Log Files

Log files for particular missions can be downloaded from the Gobi WebUI, but are also downloaded automatically when offloading a mission with GRYFN Processing Tool.

Full Gobi logs can be found in `/data/gryfn.log.YYYY.MM.DD`

Logs from the Headwall NanoHP can be found in `/var/log/mvx/`



<details>

<summary>Altitude estimate does not seem correct.</summary>

Elevations are reported in WGS84. Listed elevation should converge to nominal elevation after 2-5 minutes of static "warm-up" period for the SBG. If estimate does not seem correct after this time:

1. Ensure the GNSS antennae are installed correctly
2. Ensure GNSS antenna cables are connected to the right ports
3. Ensure the GNSS antennae are not covered
4. Ensure GNSS antennae have a clear, open view of the sky

If the above fail:

1. Try moving the aircraft to a new position, and adjusting the orientation
2. Try power cycling the aircraft to see if SBG is able to estimate elevation more accurately

</details>

<details>

<summary>Hyperspectral data did not capture.</summary>

1. Ensure the correct HSI capture polygon was uploaded to the sensor.
2. Ensure the HSI capture polygon and flight plan areas match.
3. Ensure the altitude estimate at takeoff was nominal.
4. Ensure the altitude trigger threshold was set at least 10m below the flight altitude.
5. Ensure the internal storage drive has enough free space to record data.

</details>

<details>

<summary>Can I hotswap batteries with GRYFN Gobi?</summary>

We do not recommend hotswapping batteries with any high-end GNSS solution. Static data can cause drift with the IMU and lead to a decrease in quality of the post-processed trajectory.

</details>

<details>

<summary>GNSS data is not in my mission folder.</summary>

GNSS data is still being captured, but there is a known firmware bug with getting GNSS data to the Gobi mission folder in some circumstances.

* SBG GNSS-INS data is logged to SBG's internal dataLogger.
* When user Stops Mission after a flight, GNSS-INS data is copied from the dataLogger to Gobi mission folder.
* If user removes power from Gobi too quickly after Stop Mission is pressed, two issues can occur:
  * Data partially transfers to Gobi mission folder as power is removed. Data file may not be complete at this time and cause issues in processing.
  * Data does not initiate transfer before user has removed power.

In this case, GNSS data is still stored in the SBG data logger, but must be retrieved from the SBG over FTP. Please see the Quick Start Guide Appendix for WinSCP SBG Profile to FTP into the SBG data logger. Simply download the GNSS data folder from the corresponding flight and either bundle this data into your GRAW bundle, or if you have already bundled data, replace the existing .00# and JSON file with the files downloaded from the data logger.

{% hint style="info" %}
In an upcoming firmware update, when user presses Stop Mission, a checksum will be performed for the file transfer. User will be prompted to not power off Gobi until data is fully transfered and checksum is confirmed.
{% endhint %}

</details>

## Processing Troubleshooting

For any issues with processing, please reach our [support@gryfn.io](mailto:support@gryfn.io) email. Additionally, the following items can be helpful for us to begin troubleshooting and diagnosing any errors:

* Relevant descriptions of the events
* \GPRO\processing\_logs
* \GPRO\pipelines
* Screenshot of console in GRYFN Processing Tool can be helpful (sometimes crashes cause the logs to not be dumped to file entirely

