> For the complete documentation index, see [llms.txt](https://docs.gremsy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gremsy.com/payloads/vio/case-study/gremsy-vio-x-wispr-systems.md).

# Gremsy VIO x WISPR Systems

{% embed url="<https://www.youtube.com/watch?embeds_referring_euri=https://wisprsystems.atlassian.net/&source_ve_path=MjE0Mjgz&v=B-ngfthmN4M>" %}

## Initial Configuration WISPR Ground Control (WGC) <a href="#initial-configuration-wispr-ground-control-wgc" id="initial-configuration-wispr-ground-control-wgc"></a>

### Access Settings <a href="#access-settings" id="access-settings"></a>

* Open WGC on smart controller with drone powered.
* Click the “W” in the upper left corner of the WGC home screen.

<figure><img src="/files/hdJhpUZLJ0dGPmBaHJhQ" alt=""><figcaption></figcaption></figure>

* On the popup, choose “Settings.”

<figure><img src="/files/ZzNJRKpF71PS1hvXCKAj" alt=""><figcaption></figcaption></figure>

### Selecting Payload <a href="#selecting-payload" id="selecting-payload"></a>

* In Settings, click the “Payload” tab on the left side of the screen.

<figure><img src="/files/LgfxekoqjXEMg22jSf8a" alt=""><figcaption></figcaption></figure>

* From the Payload drop-down menu, choose “Gremsy Vio.”

<figure><img src="/files/q3k9Z14fmzHAR1NrxC24" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Notes:**

Both F1 and G1 models are called the Gremsy Vio. The F1 contains a FLIR Boson sensor and the G1 contains a generic Chinese thermal core. The F1 has a 14mm focal length, records video at 60 Hz, and the G1 has a 19mm focal length and records video at 30 Hz. Otherwise, they are the same camera.

The Gremsy Vio Thermal is for thermal mapping. This selection is to be used only when thermal mapping or orthomosaic creation is required. WGC will use only the thermal sensor for taking photos in a mapping scenario.
{% endhint %}

### Selecting Options <a href="#selecting-options" id="selecting-options"></a>

* To display crosshairs on screen, click the checkbox labeled “Display crosshairs on video stream.”
* To display the panoramic auto-capture button, click the checkbox labeled “Display panoramic auto-capture button.” When the drone is in Loiter at a safe altitude, click the button in the upper-right corner of the screen, swipe to confirm, and the drone will capture 31 images for a panoramic photo stitch at the selected height.

<figure><img src="/files/WxJuZwLHL2lcZf9xdiOf" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** SkyBoss controller will display the TRSP URL as shown above.
{% endhint %}

## Flying Payload <a href="#flying-payload" id="flying-payload"></a>

### Onscreen Display and Buttons — SkyBoss Controller Users <a href="#onscreen-display-and-buttons-skyboss-controller-users" id="onscreen-display-and-buttons-skyboss-controller-users"></a>

On the right-hand side of WGC for SkyBoss users:

<figure><img src="/files/pK8LnHFx015bOhCe844V" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/CD5NRbXCOortIxFC1ioV" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/DMjKIU0CEDaYRqWHcMwP" alt=""><figcaption></figcaption></figure>

### Onscreen Display and Buttons — HereLink Controller Users <a href="#onscreen-display-and-buttons-herelink-controller-users" id="onscreen-display-and-buttons-herelink-controller-users"></a>

On the right-hand side of WGC for HereLink users:

<figure><img src="/files/RJK2Ox2PHnuqcLJ2hNtd" alt=""><figcaption></figcaption></figure>

#### Left-hand WGC controls <a href="#left-hand-wgc-controls" id="left-hand-wgc-controls"></a>

On the left-hand side of WGC:

<figure><img src="/files/ilP7st88hej1Neto0wY8" alt=""><figcaption></figcaption></figure>

## Geotagged Images and Video <a href="#geotagged-images-and-video" id="geotagged-images-and-video"></a>

### Image Geotagging Information <a href="#image-geotagging-information" id="image-geotagging-information"></a>

Images are georeferenced. Below is a snip of the EXIF data written into an image captured

<figure><img src="/files/gpyAefLcghaGvxFFyPOq" alt=""><figcaption></figcaption></figure>

## Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

### &#x20;No Video Feed <a href="#no-video-feed" id="no-video-feed"></a>

Make sure “Downloading Parameters” has completed across the top bar, make sure the correct camera is selected and if not, select it and reboot. Next step would be to remove the payload and reseat on gimble. Next step would be to check the video stream as there are two options, Stream 1 and Stream 2, only one has the video feed. The final and last step is to connect the controller to the internet and reboot the drone especially if this is the first time the Vio has been on this drone. The Downloading Parameter’s bar may take a few minutes as it downloads a new library.

<figure><img src="/files/15k9eB8znzxKKJedqduM" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/6Nri55rhzo0tnVBKNrLU" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gremsy.com/payloads/vio/case-study/gremsy-vio-x-wispr-systems.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
