> 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/flash-ark32.md). # Flash ARK32 This page details flashing ARK32 firmware using the ARK32 Configurator. You can flash firmware to the ESCs using a Betaflight or Ardupilot flight controller. The ESCs must be powered and connected to the flight controller via the signal wire. The configurator serves ARK32 releases itself — under **Flash Firmware**, the **Release** tab lists every published version and picks the matching asset (`ARK32_ARK_4IN1_F051_.hex`) from the board's own identifier. You only choose the version. The **Local** tab flashes a `.hex` from disk, for builds the configurator does not serve. It accepts `.hex` only — not the `.bin`, `.eeprom.bin`, or `.factory.bin` that also appear on an [ARK32 release](https://github.com/ARK-Electronics/ARK32/releases). *** Navigate to the [ARK32 Configurator](https://ark32.arkelectron.com/) and connect your flight controller to your PC via USB. If you're using Ardupilot you must first configure Ardupilot for ESC Passthrough.\ \ Connect to your device\ ![](https://1515919775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOwmEn1N45AR4WjMQhHlu%2Fuploads%2FLoDHYOHngDFgQGN1UBS1%2Fimage.png?alt=media\&token=b7ddd5b2-e6a6-47b3-849d-8c15e9ddb2fe) Once connected, select Read\ ![](https://1515919775-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOwmEn1N45AR4WjMQhHlu%2Fuploads%2FIVV1RT5t2LLrsyKWy7E7%2Fimage.png?alt=media\&token=036c0e7c-5beb-4997-8dc4-a17e2bba7d37) If successful you should see all of the settings for each motor
*** {% hint style="danger" %} **Flashing alone is not enough.** You must now set **KV** and **Pole Count** for each motor channel — see [ARK32 Configuration](/products/electronic-speed-controller/ark-4in1-esc/firmware/ark32-configuration.md). {% endhint %} --- # 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/flash-ark32.md?ask=&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.