> For the complete documentation index, see [llms.txt](https://docs.arkelectron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkelectron.com/products/electronic-speed-controller/ark-4in1-esc/firmware/ardupilot-esc-passthrough.md).

# Ardupilot ESC Passthrough

This page details how to configure Ardupilot for use with the ARK32 Configurator to flash firmware.

Connect the ESC to a Flight Controller flashed with Ardupilot (eg ARK FPV). Power on your ESC and Flight controller and connect to your Host PC via USB. Modify the Ardupilot parameters using [QGroundControl](https://qgroundcontrol.com/):

**Setup Ardupilot parameters to use DShot**

```
## Motor mapping
SERVO1_FUNCTION 34  	# Motor 2 -- this should match your motor layout
SERVO2_FUNCTION 35  	# Motor 3
SERVO3_FUNCTION 36  	# Motor 4
SERVO4_FUNCTION 33  	# Motor 1

## Dshot ESC setup
MOT_PWM_TYPE 6 		# DShot600
SERVO_DSHOT_ESC 1 	# BLHeli32/Kiss

## Bidirectional Dshot ESC setup
SERVO_BLH_BDMASK 15 	# Channels 1 - 4
```

**Setup Ardupilot parameters for ESC Passthrough**

```
## ESC Passthrough
SERVO_BLH_AUTO to 1
SERVO_BLH_MASK to 15 (if using output channels 1 - 4)
```

Follow the instructions on the [Flash ARK32](https://docs.arkelectron.com/products/electronic-speed-controller/ark-4in1-esc/firmware/flash-ark32.md) page to flash firmware.


---

# 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.arkelectron.com/products/electronic-speed-controller/ark-4in1-esc/firmware/ardupilot-esc-passthrough.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.
