> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/controller/pilot-pro/operating-handbook/input-output-mapping.md).

# Input Output Mapping

Default input and output mapping values

## Visual for Default Functions

<figure><img src="https://2546427254-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXREyAKYAeQJ4gfg2SPg%2Fuploads%2Fgit-blob-9aeb31a191454d4c2802c42b542dceb9741f2f9c%2FScreenshot%202024-08-02%20at%201.38.05%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>

## Configuring the Pilot Pro Buttons

The Pilot Pro has a few buttons that are not mapped to any input by default and can be assigned in the GCS software to provide additional functions

{% tabs %}
{% tab title="First Tab" %}
The following elements are not specific to drone functionality and can be remapped in AMC:

| Buttons Unmapped by Default | AMC Button Number           | Default Mapping in AMC |
| --------------------------- | --------------------------- | ---------------------- |
| L1                          | 14                          | No Action              |
| L2                          | 3                           | No Action              |
| R1                          | 13                          | Trigger Camera / Video |
| R2                          | 5                           | No Action              |
| S2                          | <p>Up - 10<br>Down - 11</p> | No Action              |

{% hint style="warning" %}
Any button that is being handled by the GCS will not send if the tablet is unpowered or GCS is not running
{% endhint %}

When using AMC, these inputs are available under Controller > Joystick, and can be assigned through each button's dropdown menu. To see what number a button is associated with, just press the button or flip the switch and look for which number turns blue

<figure><img src="https://2546427254-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXREyAKYAeQJ4gfg2SPg%2Fuploads%2Fgit-blob-28f66ab735ef83e8a7d1dab53811fea137906b4e%2FAMC%20Button%20Mapping.gif?alt=media" alt=""><figcaption><p>How to map a button using AMC on the Pilot Pro</p></figcaption></figure>
{% endtab %}

{% tab title="QGC" %}
QGC doesn't handle HID inputs and should be configured through Advanced Input Mapping to adjust the SBUS channel values if you need to use any of the buttons not already configured to SBUS channels

{% hint style="danger" %}
Adjusting channels is not recommended since this can change the drone's control commands when configured improperly
{% endhint %}

The Alta does not have slow mode or velocity clamps on firmware v1.4.1 or below for the standard Alta, or v1.3.114 for the Blue/DIU Alta, and the following channels are unused

| Input         | Default SBUS Channel |
| ------------- | -------------------- |
| D2            | 11                   |
| D3            | 12                   |
| D4            | 13                   |
| A1            | 14                   |
| S1            | 15                   |
| S2            | 16                   |
| {% endtab %}  |                      |
| {% endtabs %} |                      |

{% hint style="info" %}
Input mapping on the Pilot Pro can happen at multiple levels. The base level would edit the actual radio commands being sent and what they're mapped to. To read more about this, please see our [Advanced Input Mapping](https://docs.freeflysystems.com/ecosystem/controller/pilot-pro/operating-handbook/input-output-mapping/advanced-input-mapping.md) page.
{% endhint %}

## Input Mapping On Various Output Types

*This is the latest with Astro v1.6 and Pilot Pro v1.3*

<figure><img src="https://2546427254-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXREyAKYAeQJ4gfg2SPg%2Fuploads%2Fgit-blob-ea2954c7a621ee0ac38c38a5c8bdd7687b8de6f9%2FScreenshot%202024-08-06%20at%2012.22.29%E2%80%AFPM.png?alt=media" alt=""><figcaption></figcaption></figure>

## SBUS Mapping (Detailed)

<figure><img src="https://2546427254-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXREyAKYAeQJ4gfg2SPg%2Fuploads%2Fgit-blob-170a81c81038dc439f947d5415c6fd9e249f04fe%2FScreenshot%202024-08-06%20at%2012.21.02%E2%80%AFPM.png?alt=media" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.freeflysystems.com/ecosystem/controller/pilot-pro/operating-handbook/input-output-mapping.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
