> 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/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **ARINC429** driver is included by default with RT-LAB and does not require any additional installation.

## Hardware requirements

ARINC429 communication is supported through [**OP3511**](https://www.opal-rt.com/docs/pcie-cards-and-connector-kits/pcie-cards/op3511-abaco-rar-pcie-arinc-429.md) **ABACO RAR‑PCIE ARINC 429 cards**.

To verify whether the PCIe card is already included in your system, refer to your **System Description Document**. If the card is not included, consult the **Hardware Modularity** section of your hardware platform documentation to identify the compatible ABACO RAR‑PCIE ARINC 429 available for your platform.

## License requirements

### Simulator license

[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 to run simulations using the ARINC429 protocol:

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

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the ARINC429 protocol.

## Supported features

* Multiple board configuration is supported.
* The number of active channels is configurable.
* The baud rate of each channel is configurable independently.
* Internal and IRIG-B synchronization sources are supported.
* Message transmission can be enabled/disabled dynamically (cyclical transmitted messages are also supported).
* Raw-data or field definition (Label, SSM, SDI, Parity) available on transmission and reception.
* Field-specific (Label, SSM, SDI) filtering on reception messages.
* Two error injection modes per channel.
* BNR, BCD, Discrete data types supported.
* Different signal types can be packaged on a single message.
* Signals are configurable with 1-bit granularity precision.
* A gain and an offset can be applied to each signal within a message both in transmission and reception.
* Status information for each channel can be monitored independently.
* Reception intervals can be monitored on reception messages and set timeout triggering is available.
* The timestamp of each received message can be monitored.
* Python scripted configuration file creation is available.
* Configuration creation, modification and importing fully supported in GUI.

## Limitations

* No special limitation.


---

# 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/requirements-features-and-limitations.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.
