> 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/arinc429-example.md).

# ARINC429 Example

## Description <a href="#description" id="description"></a>

The **ARINC429** example can be created by starting a new RT‑LAB project. From the menu bar, select **File > New > RT‑LAB Project**. Enter a name and location for your project, then click **Next**. From the available templates list, navigate to **IO > Abaco** and select **ARINC429**, then click **Finish**. This example demonstrates how to use the **ARINC429 interface** in RT‑LAB to transmit and receive ARINC‑429 messages using **internal loopback**. The example uses a **RAR PCIe 44** board, which provides **four transmission channels** and **four reception channels**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-ff8630e4043d29cb92dd19310c518c8278567a1d%2FDR-rtlab-arinc-ex.png?alt=media" alt="" width="383"><figcaption></figcaption></figure>

All transmission channels are internally looped back to their corresponding reception channels using the board’s **Enable internal loopback** option. As a result, **no external cabling or physical connections are required** to execute this example.

## Requirements

The simulator must be equipped with an **ABACO RAR‑PCIE ARINC 429 card** **(**[**OP3511**](https://www.opal-rt.com/docs/pcie-cards-and-connector-kits/pcie-cards/op3511-abaco-rar-pcie-arinc-429.md)**)** providing **four ARINC TX/RX channels**.

[Verify that an active RT-LAB license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md) with the following features is installed on the simulator:

| Feature Name          | Required Status     | Description                                           |
| --------------------- | ------------------- | ----------------------------------------------------- |
| ARINC429              | enabled             | Enables communication protocol ARINC429               |
| ARINC429\_CHANNEL\_NB | 2 enabled (or more) | Number of channels for communication protocol ARINC29 |

## Detailed explanation

In this example, all four ARINC‑429 transmission channels are configured with different baud rates to illustrate **high‑speed**, **low‑speed**, and **custom‑speed** operation:

* **Channel 1** and **Channel 2** operate at **100 kbps (high speed)**
* **Channel 3** operates at **12.5 kbps (low speed)**
* **Channel 4** operates at a **custom baud rate of 55.5 kbps** (for demonstration purposes)

All transmission channels have **External transmission enabled**, meaning transmitted data is available both on the physical board ports and through the internal loopback mechanism used by this example.

To simplify the demonstration:

* **Parity management** is disabled
* **Error injection** is disabled on all transmission and reception channels

Each transmission channel is paired with its corresponding reception channel through internal loopback, and messages are assigned to channels as shown below.

### Transmission channels

| Channel                 | Assigned Message             | Message Group |
| ----------------------- | ---------------------------- | ------------- |
| Ch1 – High Speed (Tx)   | TX1‑Raw Data                 | Group 1       |
| Ch2 – High Speed (Tx)   | TX2‑FCC‑Mixed Types          | Group 2       |
| Ch3 – Low Speed (Tx)    | TX3‑FMC‑Cross Track Distance | Group 3       |
| Ch4 – Custom Speed (Tx) | TX4‑Valve Position Message   | Group 4       |

### Reception channels

| Channel                 | Assigned Message             | Message Group |
| ----------------------- | ---------------------------- | ------------- |
| Ch1 – High Speed (Rx)   | RX1‑Raw Data                 | Group 1       |
| Ch2 – High Speed (Rx)   | RX2‑FCC‑Mixed Types          | Group 2       |
| Ch3 – Low Speed (Rx)    | RX3‑FMC‑Cross Track Distance | Group 3       |
| Ch4 – Custom Speed (Rx) | RX4‑Valve Position Message   | Group 4       |

All messages are configured for **cyclic transmission**, with the exception of **Group 2**, which is transmitted **at every model time step**.

* **Group 1** uses a **raw data message**. Because it is configured as raw data, reception does not filter on label and accepts all received words.
* **Groups 2 to 4** each contain one transmission message and one reception message. These groups differ only in their parameter values and signal content and apply label‑based filtering at reception.

### Model preparation and configuration

To prepare and run the example:

1. Review and adjust the ARINC429 interface parameters as desired.
2. Build the ARINC429\_Example\_Model model.
3. Load the model and verify that all interface connections have been properly created.
4. Execute the model.
5. Use the **Dashboard panels** to interact with the simulation.

## Simulation and results

During execution, each transmission channel sends ARINC‑429 words that are internally looped back to the corresponding reception channel. The received data is decoded and made available to the model.

Dedicated **Dashboard panels** are provided for each message group. These panels allow you to:

* Modify transmitted data values
* Observe received ARINC‑429 data
* Monitor message behavior in real time

Changes made to transmitted values are immediately reflected on the corresponding reception channels through the internal loopback.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-20dee2b16eb2cd43cf9e11a7114cba1d6b4d25f7%2FDR-rtlab-arinc-ex2.png?alt=media" alt=""><figcaption></figcaption></figure>

Successful execution confirms correct ARINC‑429 transmission, reception, decoding, and internal loopback operation.


---

# 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/arinc429-example.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.
