> 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.md).

# ARINC429

## Introduction to ARINC 429

ARINC 429 (Aeronautical Radio, Incorporated 429) is a widely used, standardized communication protocol in commercial and military aviation. It was designed for reliable, deterministic, and unidirectional data exchange between avionics systems over dedicated point-to-point wiring.

## Protocol characteristics

* **Transmitter/Receiver Architecture**\
  ARINC 429 uses a unidirectional, point-to-point architecture where a single transmitter sends data to one or more receivers.
* **Deterministic Communication**\
  Data is transmitted at fixed rates (12.5 kbps or 100 kbps), ensuring predictable timing and low latency.
* **Supports Multiple Data Types**\
  Labels can represent parameters such as airspeed, altitude, navigation data, system status, and control information.
* **Self-Describing Data Format**\
  Each 32-bit word includes a label, source/destination identifier, data field, and parity for error detection.
* **Built-in Error Detection**\
  Parity checking allows receivers to detect corrupted data without retransmission mechanisms.

## How the protocol works

The transmitting avionics unit continuously sends 32-bit data words on the ARINC 429 bus.\
Receiving units listen for specific labels and extract relevant data for processing or display.\
Communication occurs over twisted-pair wiring using bipolar return-to-zero (BPRZ) signaling.

## Example applications

* **Flight management systems**\
  ARINC 429 is used to transmit navigation, performance, and flight plan data between FMS, GPS, and inertial reference systems.
* **Cockpit displays**\
  Primary flight displays and multifunction displays receive air data, attitude, and navigation information via ARINC 429.
* **Aircraft sensors and systems**\
  Air data computers, engine monitoring systems, and environmental control systems exchange measurements using ARINC 429.
* **Autopilot and flight control systems**\
  Autopilot computers receive sensor data and mode information over ARINC 429 to maintain stable and controlled flight.


---

# 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.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.
