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

# Hardware Reference

## Specifications

| Specification     | Value                                                                                                             |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| MCU               | 4 × STM32F051, one per motor channel                                                                              |
| Gate driver       | [TI DRV8328](https://www.ti.com/product/DRV8328)                                                                  |
| Input voltage     | 3S–8S LiPo, 6 V minimum, 65 V absolute maximum                                                                    |
| Current per motor | 50 A continuous, 75 A burst. CONS: MR30 connector limit 30 A continuous, 40 A burst                               |
| Bulk capacitance  | 450 µF, see [Capacitance](#capacitance)                                                                           |
| Current sensor    | Onboard, one shunt shared by all four channels                                                                    |
| Input protocols   | DShot (300, 600) with bidirectional DShot and KISS serial telemetry; PWM                                          |
| Connectors        | 8-pin JST-SH flight controller, 10-pin JST-SH debug. CONS: MR30 motor connectors, M2.5 threaded battery standoffs |
| Dimensions        | 43.00 × 40.50 × 7.60 mm. CONS: 77.00 × 42.00 × 9.43 mm                                                            |
| Mounting pattern  | 30.5 mm                                                                                                           |
| Weight            | 14.5 g. CONS: 24.0 g                                                                                              |

## Pinout

### Flight Controller — 8-pin JST-SH

<figure><img src="https://1515919775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOwmEn1N45AR4WjMQhHlu%2Fuploads%2FpfyW0zigvIslsFrTpjkJ%2FAcrobat_4UyaCNYGVF.png?alt=media&amp;token=5156c827-f5ff-4a9f-80ee-d3ebac0d5147" alt=""><figcaption><p>Flight Controller Connector</p></figcaption></figure>

| Pin | Signal  | Voltage |
| --- | ------- | ------- |
| 1   | VBAT    | VBAT    |
| 2   | CURR    | +3.3V   |
| 3   | TELEM   | +3.3V   |
| 4   | MOTOR 1 | +3.3V   |
| 5   | MOTOR 2 | +3.3V   |
| 6   | MOTOR 3 | +3.3V   |
| 7   | MOTOR 4 | +3.3V   |
| 8   | GND     | GND     |

### Debug — 10-pin JST-SH

<figure><img src="https://1515919775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOwmEn1N45AR4WjMQhHlu%2Fuploads%2FU2YUBK7BawRtZz57KWfF%2FAcrobat_uIiYGbeDWe.png?alt=media&amp;token=2baf9d05-1512-4f2c-b25c-22ada932b561" alt=""><figcaption><p>Debug Connector</p></figcaption></figure>

| Pin | Signal   | Voltage |
| --- | -------- | ------- |
| 1   | 3.3V     | +3.3V   |
| 2   | SWDIO 1  | +3.3V   |
| 3   | SWDCLK 1 | +3.3V   |
| 4   | SWDIO 2  | +3.3V   |
| 5   | SWDCLK 2 | +3.3V   |
| 6   | SWDIO 3  | +3.3V   |
| 7   | SWDCLK 3 | +3.3V   |
| 8   | SWDIO 4  | +3.3V   |
| 9   | SWDCLK 4 | +3.3V   |
| 10  | GND      | GND     |

Each SWDIO/SWDCLK pair reaches one channel's MCU. See [Flash Bootloader](/products/electronic-speed-controller/ark-4in1-esc/firmware/flash-bootloader.md) for ST-LINK wiring.

## 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 %}

## Datasheets

* [ARK 4IN1 ESC](https://github.com/ARK-Electronics/ark-hardware/blob/main/ARK_4IN1_ESC/datasheet/ARK_4IN1_ESC_Datasheet.pdf)
* [ARK 4IN1 ESC CONS](https://github.com/ARK-Electronics/ark-hardware/blob/main/ARK_4IN1_ESC/datasheet/ARK_4IN1_ESC_CONS_Datasheet.pdf)

## 3D Model and Case

| File                                                                                                                                                                                                          | Contents                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| [ARK\_4\_IN\_1\_ESC\_Rev\_3.1.step](https://github.com/ARK-Electronics/ark-hardware/raw/main/ARK_4IN1_ESC/model/ARK_4_IN_1_ESC_Rev_3.1.step)                                                                  | ARK 4IN1 ESC board, rev 3.1                             |
| [ARK\_4\_IN\_1\_ESC\_Rev\_3.1\_With\_Solder\_Pads.step](https://github.com/ARK-Electronics/ark-hardware/raw/main/ARK_4IN1_ESC/model/ARK_4_IN_1_ESC_Rev_3.1_With_Solder_Pads.step)                             | ARK 4IN1 ESC board with solder pads, rev 3.1            |
| [ARK\_4\_IN\_1\_ESC\_Rev\_3.1\_PDF3D.pdf](https://github.com/ARK-Electronics/ark-hardware/raw/main/ARK_4IN1_ESC/model/ARK_4_IN_1_ESC_Rev_3.1_PDF3D.pdf)                                                       | ARK 4IN1 ESC board, rev 3.1, 3D PDF                     |
| [ARK\_4\_IN\_1\_ESC\_CON\_Rev\_4.1.step](https://github.com/ARK-Electronics/ark-hardware/raw/main/ARK_4IN1_ESC/model/ARK_4_IN_1_ESC_CON_Rev_4.1.step)                                                         | CONS board, rev 4.1                                     |
| [ARK\_4\_IN\_1\_ESC\_CON\_Rev\_4.1\_With\_Solder\_Pads.step](https://github.com/ARK-Electronics/ark-hardware/raw/main/ARK_4IN1_ESC/model/ARK_4_IN_1_ESC_CON_Rev_4.1_With_Solder_Pads.step)                    | CONS board with solder pads, rev 4.1                    |
| [ARK\_4\_IN\_1\_ESC\_CON\_Straight\_Rev\_4.1\_With\_Solder\_Pads.step](https://github.com/ARK-Electronics/ark-hardware/raw/main/ARK_4IN1_ESC/model/ARK_4_IN_1_ESC_CON_Straight_Rev_4.1_With_Solder_Pads.step) | CONS board, straight variant, with solder pads, rev 4.1 |
| [ARK\_4\_IN\_1\_ESC\_CON\_Rev\_4.1\_PDF3D.pdf](https://github.com/ARK-Electronics/ark-hardware/raw/main/ARK_4IN1_ESC/model/ARK_4_IN_1_ESC_CON_Rev_4.1_PDF3D.pdf)                                              | CONS board, rev 4.1, 3D PDF                             |

All files: [ARK\_4IN1\_ESC in ark-hardware](https://github.com/ARK-Electronics/ark-hardware/tree/main/ARK_4IN1_ESC)


---

# 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/hardware.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.
