> 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.md).

# ARK 4IN1 ESC

NDAA compliant, made in the USA, 4 in 1 electronic speed controller running open source ARK32 firmware.

{% hint style="danger" %}
**Before first use**, configure **KV**, **Pole Count**, and **Ramp Rate** for each motor channel in the [ARK32 Configurator](https://ark32.arkelectron.com/). The KV/pole defaults will not match your motor. Factory ramp is 2 %/ms — lower it for large props. See [ARK32 Configuration](/products/electronic-speed-controller/ark-4in1-esc/ark32-configuration.md).
{% endhint %}

This ESC runs [**ARK32**](https://github.com/ARK-Electronics/ARK32). Use ARK32 on this board. See [Why ARK32](/products/electronic-speed-controller/ark-4in1-esc/firmware.md#why-ark32).

**Specifications:**

* Voltage
  * 3s – 8s Lithium Polymer Battery Input
  * 6V Minimum
  * 65V Absolute Maximum
* Current Per Motor
  * 50A Continuous
  * 75A Burst Current
* Input Protocols
  * Dshot (300, 600)
    * Bi-directional Dshot
    * KISS Serial Telemetry
  * PWM
* Dimensions
  * 43.00mm x 40.50mm x 7.60mm
  * 30.5mm Mounting Pattern
* Weight
  * 14.5g

**Capacitance:**

The ARK 4IN1 ESC has 450µF of bulk capacitance built in, which is sufficient for most 3S–6S installations with short battery leads.

{% hint style="warning" %}
For 8S and above, add an external bulk capacitor across the battery input to keep switching and inrush transients below the 65V absolute maximum. Long battery leads increase inductance and make transients worse at any voltage.
{% endhint %}

{% content-ref url="/pages/n6YlyGRFz0S4n9wwBw7w" %}
[Pinout](/products/electronic-speed-controller/ark-4in1-esc/pinout.md)
{% endcontent-ref %}

{% content-ref url="/pages/2WEpmwEk9qQBWRoqPqcv" %}
[Firmware](/products/electronic-speed-controller/ark-4in1-esc/firmware.md)
{% endcontent-ref %}

{% content-ref url="/pages/xu15sk9Nia1VuvWWiP2d" %}
[PWM Calibration](/products/electronic-speed-controller/ark-4in1-esc/pwm-calibration.md)
{% endcontent-ref %}

{% content-ref url="/pages/OA41i2YJTdQdxmWQs0Dv" %}
[3D Models](/products/electronic-speed-controller/ark-4in1-esc/3d-models.md)
{% endcontent-ref %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arkelectron.com/products/electronic-speed-controller/ark-4in1-esc.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 `build a script that syncs our docs to a CMS` 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.