# Input Output Mapping

## Visual for Default Functions

<figure><img src="/files/hQpHF2nms7nFWUCjbXoJ" 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

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="/files/lhNU8Xmt5w5Z5Qu5Dssl" alt=""><figcaption><p>How to map a button using AMC on the Pilot Pro</p></figcaption></figure>

{% 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](/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="/files/DOH7t9s2rZGkPgDRWye1" alt=""><figcaption></figcaption></figure>

## SBUS Mapping (Detailed)

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


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.