# Autopilot Connections There are three primary communication channels between the Jetson and the Flight Controller: Serial , USB, and Ethernet. The serial and USB interfaces are direct board to board connections and have been tested up to 3Mbps. Ethernet runs through a 100Mbps hub to the flight controller, Jetson, and external interfaces. | Type | Jetson device path | Flight Controller | | -------- | ------------------ | ----------------- | | USB | /dev/ttyACM0 | USB | | Serial | /dev/ttyTHS1 | Telem2 | | Ethernet | enP8p1s0 | eth0 | For the USB port to be enabled on the ARKV6X flight controller, the VBUS\_SENSE pin must be driven high from the Jetson. It is connected to pin 206 GPIO07. For Jetpack 5, there is a helper python script in ARK-OS to drive the pin high. For Jetpack 6, a script cannot toggle a GPIO and leave it set. As a workaround, the VBUS\_SENSE pin is set high in the Jetson pinmux on boot.\ ## UART The UART connection between Jetson and the autopilot is on Jetson UART1 which appears as **/dev/ttyTHS0** in Jetpack 5 and **/dev/ttyTHS1** in Jetpack 6. This goes to **Telem2** on the Pixhawk Autopilot Bus. This connection has been tested to 3Mbps. Higher baud rates may be possible. Flow control needs to be set to "Force Off" when using Telem2 for MAVLINK. [MAV\_X\_FLOW\_CTRL ](https://docs.px4.io/main/en/advanced_config/parameter_reference.html#MAV_1_FLOW_CTRL)set to "0". ## Ethernet The flight controller and Jetson Ethernet are connected through a 100Mbps switch on the board along with two external connections. One of a 4 pin JST-GH and one on the Pixhawk Payload Bus FFC connector. To setup the connection on the flight controller, follow either the [PX4 guide](https://docs.px4.io/main/en/advanced_config/ethernet_setup) or the [Ardupilot guide](https://ardupilot.org/copter/docs/common-network.html) depending on which firmware you are running. If one of the external connections is to a router running a DHCP server, the router will give the Jetson and flight controller an IP address. To communicate between the Jetson and flight controller without an external router/DHCP server, static IP addresses on both ends need to be configured. ## Flight Controller Reset The flight controller can be hard reset using the reset signal connected to Jetson pin 228 GPIO13. The Jetson cannot reset the flight controller while it is armed. The reset signal is gated by the nARMED signal from the flight controller. There are a couple of helper scripts to reset the flight controller. One to drive the VBUS\_SENSE pin high before the reset to wait in the bootloader for 5 seconds. This is useful when updating the flight controller firmware and a hard reboot is needed. The other fast reset script drives the VBUS\_SENSE pin low before the reset to avoid the wait.\ \ Reset and wait in the bootloader\ \ Reset quickly and skip the bootloader\ [https://github.com/ARK-Electronics/ARK-OS/blob/main/platform/jetson/scripts/reset\_fmu\_fast.py](https://github.com/ARK-Electronics/ARK-OS/blob/main/platform/jetson/scripts/reset_fmu_wait_bl.py) --- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://docs.arkelectron.com/products/flight-controller/jetson-pabs/ark-jetson-pab-carrier-v3/autopilot-connections.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.