> 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/flight-controller/jetson-pabs/ark-jetson-pab-carrier-v3/using-ark-os/autopilot-connections.md).

# Autopilot Connections

There are three communication channels between the Jetson and the flight controller: USB, serial, and Ethernet. USB and serial are direct board-to-board connections tested up to 3 Mbps; Ethernet runs through the onboard 100 Mbps switch.

| Type     | Jetson device path | Flight Controller |
| -------- | ------------------ | ----------------- |
| USB      | /dev/ttyACM0       | USB               |
| Serial   | /dev/ttyTHS1       | Telem2            |
| Ethernet | enP8p1s0           | eth0              |

{% hint style="info" %}
We recommend running MAVLink on USB and XRCE-DDS on serial. ARK-OS's defaults do exactly this — see [Services](/software/ark-os/services.md).
{% endhint %}

## USB

For the flight controller's USB to enumerate, its VBUS\_SENSE pin must be driven high by the Jetson. This is set in the Jetson pinmux at boot, so it works out of the box.

## Serial

The serial connection is Jetson UART1 (`/dev/ttyTHS1`) to **Telem2** on the flight controller, tested to 3 Mbps. When running MAVLink on Telem2, set flow control to off: [MAV\_x\_FLOW\_CTRL](https://docs.px4.io/main/en/advanced_config/parameter_reference.html#MAV_1_FLOW_CTRL) = 0.

## Ethernet

The flight controller and Jetson are connected through a 100 Mbps switch on the board, along with two external connections: the 4-pin JST-GH Ethernet connector and the Pixhawk Payload Bus FFC.

To set up the flight controller side, follow the [PX4 Ethernet guide](https://docs.px4.io/main/en/advanced_config/ethernet_setup) or the [ArduPilot network guide](https://ardupilot.org/copter/docs/common-network.html). If one of the external connections leads to a router running DHCP, both the Jetson and flight controller get addresses from it; otherwise configure static IPs on both ends.

## Flight Controller Reset

The Jetson can hard-reset the flight controller via a GPIO reset line. The reset is gated by the nARMED signal — the Jetson cannot reset the flight controller while it is armed.

ARK-OS ships two reset helpers on `PATH`:

```bash
reset_fmu_fast.py       # reset and boot straight into the application
reset_fmu_wait_bl.py    # reset and wait in the bootloader (for firmware flashing)
```


---

# 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/flight-controller/jetson-pabs/ark-jetson-pab-carrier-v3/using-ark-os/autopilot-connections.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.