> 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/radio/ark-microhard-ddl-carrier/setup.md).

# Setup

This page covers the carrier and getting started with the radio. For everything else about the radio, see the operating manual for your module on the [Microhard support portal](https://support.microhardcorp.com/portal/en/home).

## Power

| Input   | Range                          |
| ------- | ------------------------------ |
| Battery | 5.5–55 V, 2-pin Molex Nano-Fit |
| USB-C   | 5–20 V, USB Power Delivery     |

On a vehicle, power the carrier from the battery input. You can connect battery and USB-C at the same time, and the carrier runs from whichever is the higher voltage.

The radio takes about a minute to boot.

## Radio Access

Connect the carrier's USB-C port to a computer. The radio shows up as a network adapter and gives the computer an address, so you can open the radio's web UI at `192.168.168.1` in a browser. The factory login is `admin` / `admin`, and the radio asks you to change the password the first time you log in.

Every radio ships at `192.168.168.1`, so give each one its own address before linking them.

**RESET** reboots the radio. Holding **CONFIG** after the radio has booted resets it to factory settings. The hold time depends on the module, so check its manual.

## Linking Radios

In the web UI, open **Wireless > RF**. Set one radio as the master and the others as remotes. All radios in the network need the same network ID, frequency, channel bandwidth and compatibility mode.

## Flight Controller

Connect the carrier's serial connector to a TELEM port on the flight controller with a 6-pin JST-GH cable. The radio sends the flight controller's serial data over the network as UDP. Give the ground computer a static address on the radio's subnet, such as `192.168.168.69` with netmask `255.255.255.0`. Then in the air radio's web UI, set its serial port to the flight controller's baud rate and send to that address on port 14550, which QGroundControl and Mission Planner listen on.

PX4 and ArduPilot both run MAVLink on TELEM1 at 57600 baud by default. The radio's serial port goes up to 230400 baud. To use another port or rate:

* PX4: [MAVLink Peripherals](https://docs.px4.io/main/en/peripherals/mavlink_peripherals.html)
* ArduPilot: [Serial Port Configuration](https://ardupilot.org/copter/docs/common-serial-options.html)

## Companion Computer

Connect a companion computer to the LAN or WAN port. The [ARK Jetson PAB Carrier integration guide](https://docs.arkelectron.com/tutorials/radio-integration/ark-microhard-ddl-carrier-integration-for-ark-jetson-pab-carrier.md) sets up a two-radio network with static addresses.


---

# 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/radio/ark-microhard-ddl-carrier/setup.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.
