> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/connect-the-hardware.md).

# Connect the Hardware

## Connect devices using ARINC 429 cabling

ARINC 429 communication uses dedicated, point‑to‑point avionics wiring. To establish communication between transmitting and receiving avionics units, or between a simulator and devices under test, connect the systems using **ARINC 429‑compliant twisted, shielded pair cabling**. Transmission and reception use **separate physical ports**, and communication is strictly **unidirectional**.

For reliable ARINC 429 operation, the following wiring and configuration rules must be observed:

* Each ARINC 429 channel supports **a single transmitter** to prevent bus contention.
* Up to **20 receivers** may be connected to a single transmitter line.
* Transmitters and receivers must be connected using **twisted, shielded differential pairs**.
* The transmitter and all receivers on a channel must operate at the **same data rate**.
* Each physical ARINC 429 channel is **independent** and must be wired separately when multiple avionics systems are connected.

### Example of valid ARINC 429 channel configuration

* Channel 1 TX: Flight Management System
* Channel 1 RX: Autopilot Computer, Navigation Display
* Data rate: 100 kb/s
* Channel 2 TX: Air Data Computer
* Channel 2 RX: Primary Flight Display
* Data rate: 12.5 kb/s


---

# 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://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/connect-the-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.
