> For the complete documentation index, see [llms.txt](https://aedrox.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aedrox.gitbook.io/docs/flight-controller/interactive-blocks/ardupilot/initial-hardware-setup.md).

# Initial Hardware Setup

##

{% stepper %}
{% step %}

### ​Frame Type

```
SETUP > MANDATORY HARDWARE > FRAME TYPE
Select the frame type of your drone.
```

For QuadX : as the connectors are following the BetaFlight standard, you have to specify it by setting the parameter FRAME\_TYPE : 12  (CONFIG > Full Paramater List)

<figure><img src="/files/oDWJsoZA3kpyjzNSRnD3" alt="" width="375"><figcaption></figcaption></figure>

<br>
{% endstep %}

{% step %}

### Accelerometer Calibration

```
SETUP > MANDATORY HARDWARE > Accel Calibration
```

1 - Click on the 'Calibrate Accel' button, then follow the 6 axis calibration steps.\
2- After 6 axis calibration is done, put your drone perfectly level, then click on 'Calibrate Level'
{% endstep %}

{% step %}

### Radio Calibration

```
SETUP > MANDATORY HARDWARE > Radio Calibration
```

1 - Connect the radio receiver to the flight controller and power it on.\
2 - Setup the proper protocol parameter for your receiver \
3 - Calibrate all radio sticks and buttons range by clicking the 'Caliber Radio' Button

The AEDROXH7 receiver port is the SERIAL3.\
To define the receiver protocol described at step 2 go to : \
CONFIG > FULL PARAMETER LIST > SERIAL3 > SERIAL3\_PROTOCOL\
Ensure to click on 'Write Params' button to record the change. A power cycle can be necessary to make the change effective. &#x20;
{% endstep %}

{% step %}

### SERIAL PORTS

```
SETUP > MANDATORY HARDWARE > SERIAL PORTS
```

The serial ports are already setup by default. You can use this page to modify SERIAL\_PROTOCOL if needed.
{% endstep %}

{% step %}

### Flight Modes

```
SETUP > MANDATORY HARDWARE > FLight Modes
```

1 - Ensure your radio is on, calibration is done, and your receiver connected.\
2 - Define a flight mode switch on your radio\
3 - Set the corresponding parameter into the flight controller \
CONFIG > FULL PARAMETER LIST > FLTMODE\_CH. (Channel 5 is set by default)\
4 - Select the flight modes you want to match the different switch positions (move the switch positions to display the corresponding value / green field). Then click on 'Save Mode'
{% endstep %}

{% step %}

### FailSafe

```
SETUP > MANDATORY HARDWARE > FailSafe
```

1 - Battery failsafe : You can define a low battery level based on your setup and define the behaviour the drone should adopt when this critical level is reached. \
2 - Radio failsafe : activated by default, the default parameters ensure the drone to RTL (return to launch) in case of the radio link is lost.\
3 - GCS failsafe :  you can activate if you control your drone with a GCS (computer or tablet) connected with a telemetry module. In case of telemetry lost, the drone will engage RTL.&#x20;
{% endstep %}
{% endstepper %}


---

# 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://aedrox.gitbook.io/docs/flight-controller/interactive-blocks/ardupilot/initial-hardware-setup.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.