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

# Configure ARINC429

When working with communication protocols, it is recommended to first configure the driver using the **I/O Interfaces** section in RT-LAB.

## Configure the ARINC I/O interface

{% stepper %}
{% step %}

### Add a new I/O interface

In RT-LAB Project Explorer, right-click **I/O Interfaces**, select **New I/O Interface**, and choose **ARINC429**. Double-click the newly created interface to begin configuration.
{% endstep %}

{% step %}

### Import an ARINC429 configuration (optional)

The **ARINC429 Importer** wizard simplifies the creation of ARINC429 configurations by importing **boards, channels, messages, and signal definitions** from JSON format ARINC-429 configuration file:

* [Import ARINC429 Configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429/import-arinc429-configuration.md)
  {% endstep %}

{% step %}

### Configure the general settings

In the **Folders** list, click **General** and configure the general settings.

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

<table><thead><tr><th width="165">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Verbose</strong></td><td><strong>Checked:</strong> Displays the complete interface configuration during model loading.<br><strong>Unchecked:</strong> The configuration is loaded silently without detailed output.</td></tr><tr><td><strong>Recorder Log Level</strong></td><td><p>Selects the <strong>verbosity level of the recorder logs</strong>. The selected level applies to <strong>all recorded channels</strong> and controls how much information is written to the recorder logs during execution:</p><p><strong>Minimal:</strong> Records only essential information required for basic operation, with minimal logging overhead.</p><p><strong>Moderate:</strong> Records standard operational information useful for routine monitoring and validation.</p><p><strong>Detailed:</strong> Records extended information about recorder activity, suitable for in‑depth analysis and debugging.</p><p><strong>Exhaustive:</strong> Records the most detailed level of information, including low‑level recorder activity. This level is intended for <strong>advanced debugging</strong>.</p></td></tr><tr><td><strong>Reverse gain/offset computation</strong></td><td><p>Controls the order in which <strong>gain</strong> and <strong>offset</strong> are applied when converting values between the RT‑LAB model and CAN messages.</p><p><strong>Checked:</strong><br>When transmitting (model → ARINC429), the driver applies the <strong>gain first</strong>, then the <strong>offset</strong>. <code>ARINC_value = (model_value × gain) + offset</code><br>When receiving (ARINC429 → model), the driver applies the <strong>offset first</strong>, then the <strong>gain</strong>. <code>model_value = (ARINC_value − offset)/gain</code></p><p><strong>Unchecked:</strong><br>When transmitting (model → ARINC429), the driver applies the <strong>offset first</strong>, then the <strong>gain</strong>. <code>ARINC_value = (model_value − offset)/gain</code><br>When receiving (ARINC429 → model), the driver applies the <strong>gain first</strong>, then the <strong>offset</strong>. <code>model_value = (ARINC_value × gain) + offset</code></p></td></tr><tr><td><strong>Enable virtual mode</strong></td><td><strong>Checked:</strong> Allows the model to run even if the I/O interface is not compatible with the hardware configuration. Connections are initialized, but the interface performs no actions.<br><strong>Unchecked:</strong> Troubleshoot without hardware or prepare a model for a future hardware platform.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage boards: add, remove, rename, or reorder

In the **Folders** list, click **Boards** and use:

* **+** icon to add boards
* **–** icon to remove boards
* **Arrow** icons to reorder boards

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-aef7521e46b3a889e241838c5787c55b7f3a2519%2FDR-rtlab-arinc2.png?alt=media" alt="" width="451"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the board(s) settings

In the **Folders** list, click a board under the **Boards** folder to configure its settings. Repeat this step for each additional board that needs to be configured.

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

<table><thead><tr><th width="145">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Card type</strong></td><td>Determines the ARINC429 interface card model and available channel count.</td></tr><tr><td><strong>Device ID</strong></td><td>Specifies the device ID on the simulator PCIe bus. Use <code>0</code> when only one card is installed. If multiple cards are installed, use <code>1</code> for the second card installed in a higher‑numbered PCIe slot.</td></tr><tr><td><strong>Clock type</strong></td><td>Selects the synchronization source (Internal or IRIG‑B).</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage channels: add, remove, rename, or reorder

In the **Folders** list, click **Tx Channels** or **Rx Channels** and use:

* **+** icon to add channels (although multiple channels can be added in the interface, the number of usable channels is limited by the **hardware capacity of the card**)
* **–** icon to remove channels
* **Arrow** icons to reorder channels

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-94defe79e3763d98a06e49a5f93546df4536f5ca%2FDR-rtlab-arinc4.png?alt=media" alt="" width="488"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the channels

In the **Folders** list, expand **Tx Channels** and **Rx Channels** to display all available channels, then select a channel to configure its parameters.

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

{% tabs %}
{% tab title="Tx Channels" %}

<table><thead><tr><th width="160">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Channel number</strong></td><td><p>Identifies the <strong>physical ARINC‑429 channel</strong> on the interface board to be configured. Channel numbers are <strong>zero‑based in the interface configuration</strong>, while hardware channels are <strong>one‑based</strong>. For example:</p><ul><li><strong>Channel number 0</strong> configures <strong>hardware Channel 1</strong></li><li><strong>Channel number 1</strong> configures <strong>hardware Channel 2</strong>, and so on.</li></ul><p>When a new channel is added, this value defaults to <strong>0</strong> and must be updated to the desired channel number for the application.</p></td></tr><tr><td><strong>Baudrate</strong></td><td>Selects the channel baud rate. <strong>Low</strong> is <strong>12.5 kbps</strong>, <strong>High</strong> is <strong>100 kbps</strong> and selecting <strong>Custom</strong> allows specifying a baud rate between <strong>12.5 kbps and 100 kbps</strong>.</td></tr><tr><td><strong>Record channel data</strong></td><td><p><strong>Checked:</strong> Enables recording of all data exchanged on the channel. Recorded data is saved in <strong>CSV files</strong> located in the project’s <strong>data</strong> directory on the workstation after each simulation run.</p><ul><li><p><strong>Mode:</strong></p><ul><li>Automatic: Recording starts automatically based on the trigger configuration</li><li>Manual: Recording starts manually or via an API call</li></ul></li><li><strong>Export format:</strong> OPREC (native format), CSV, or MAT.</li><li><strong>Output file auto naming:</strong> Auto or custom. The output file name must begin with an ASCII letter or digit and may include only ASCII letters, digits, hyphens (<code>-</code>), underscores (<code>_</code>), or periods (<code>.</code>).</li><li><strong>Decimation factor:</strong> Defines the logging frequency. For example, a value of 2 means data is recorded every second simulation step.</li><li><strong>Frame length, frame length unit &#x26; number of frames to record:</strong> These settings define how data is chunked during logging. Longer frames reduce data loss but create larger files; shorter frames make smaller chunks but risk gaps between frames. Choose the unit and number of frames based on how much data you need versus available storage. For critical signals, use longer frames; for large models or slower disks, use shorter frames.</li><li><strong>Trigger settings:</strong> These settings control when data logging begins, allowing you to capture specific events with precision. You can choose <strong>Edge</strong> triggers to start recording when a signal crosses a threshold or <strong>Level</strong> triggers to monitor sustained states above or below a set value. Combine these with <strong>trigger polarity</strong> and <strong>trigger level</strong> to define exact conditions, while adjusting <strong>pre-trigger percentage</strong> (relative to frame length) to include data before the event and <strong>holdoff</strong> (number of steps ignored after a record completes before re-arming trigger detection) to avoid immediate retriggering. The appropriate trigger signal will be selected later in the next step. <strong>If no trigger signal is selected, the recording will start immediately</strong>.</li></ul><p><strong>Unchecked:</strong> Channel data is not recorded.</p></td></tr><tr><td><strong>Parity</strong></td><td><p>Configures parity handling for ARINC‑429 words (bit 32).</p><ul><li><strong>Odd parity:</strong> The transmitter sets the parity bit so that the total number of ‘1’ bits in the 32‑bit word is <strong>odd</strong>.</li><li><strong>Even parity:</strong> The transmitter sets the parity bit so that the total number of ‘1’ bits in the 32‑bit word is <strong>even</strong>.</li><li><strong>None:</strong> The transmitter does <strong>not manage parity</strong>.</li></ul></td></tr><tr><td><strong>Enable gap error injection</strong></td><td><strong>Checked:</strong> Reduces the inter‑message gap to <strong>3 bit times</strong>, enabling gap error injection for testing purposes.<br><strong>Unchecked:</strong> Normal inter‑message gap is used.</td></tr><tr><td><strong>Inject bit error</strong></td><td><p>Bit‑length error injection during transmission:</p><ul><li><strong>Disabled:</strong> Standard 32‑bit transmission</li><li><strong>Low bit error:</strong> 31‑bit transmission</li><li><strong>High bit error:</strong> 33‑bit transmission</li></ul></td></tr><tr><td><strong>Enable external transmission</strong></td><td><strong>Checked:</strong> Enables external transmission on the physical channel.<br><strong>Unchecked:</strong> The transmitter output is <strong>tri‑stated</strong>.</td></tr></tbody></table>
{% endtab %}

{% tab title="Rx Channels" %}

<table><thead><tr><th width="160">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Channel number</strong></td><td><p>Identifies the <strong>physical ARINC‑429 channel</strong> on the interface board to be configured. Channel numbers are <strong>zero‑based in the interface configuration</strong>, while hardware channels are <strong>one‑based</strong>. For example:</p><ul><li><strong>Channel number 0</strong> configures <strong>hardware Channel 1</strong></li><li><strong>Channel number 1</strong> configures <strong>hardware Channel 2</strong>, and so on.</li></ul><p>When a new channel is added, this value defaults to <strong>0</strong> and must be updated to the desired channel number for the application.</p></td></tr><tr><td><strong>Baudrate</strong></td><td>Selects the channel baud rate. <strong>Low</strong> is <strong>12.5 kbps</strong>, <strong>High</strong> is <strong>100 kbps</strong> and selecting <strong>Custom</strong> allows specifying a baud rate between <strong>12.5 kbps and 100 kbps</strong>.</td></tr><tr><td><strong>Record channel data</strong></td><td><p><strong>Checked:</strong> Enables recording of all data exchanged on the channel. Recorded data is saved in <strong>CSV files</strong> located in the project’s <strong>data</strong> directory on the workstation after each simulation run.</p><ul><li><p><strong>Mode:</strong></p><ul><li>Automatic: Recording starts automatically based on the trigger configuration</li><li>Manual: Recording starts manually or via an API call</li></ul></li><li><strong>Export format:</strong> OPREC (native format), CSV, or MAT.</li><li><strong>Output file auto naming:</strong> Auto or custom. The output file name must begin with an ASCII letter or digit and may include only ASCII letters, digits, hyphens (<code>-</code>), underscores (<code>_</code>), or periods (<code>.</code>).</li><li><strong>Decimation factor:</strong> Defines the logging frequency. For example, a value of 2 means data is recorded every second simulation step.</li><li><strong>Frame length, frame length unit &#x26; number of frames to record:</strong> These settings define how data is chunked during logging. Longer frames reduce data loss but create larger files; shorter frames make smaller chunks but risk gaps between frames. Choose the unit and number of frames based on how much data you need versus available storage. For critical signals, use longer frames; for large models or slower disks, use shorter frames.</li><li><strong>Trigger settings:</strong> These settings control when data logging begins, allowing you to capture specific events with precision. You can choose <strong>Edge</strong> triggers to start recording when a signal crosses a threshold or <strong>Level</strong> triggers to monitor sustained states above or below a set value. Combine these with <strong>trigger polarity</strong> and <strong>trigger level</strong> to define exact conditions, while adjusting <strong>pre-trigger percentage</strong> (relative to frame length) to include data before the event and <strong>holdoff</strong> (number of steps ignored after a record completes before re-arming trigger detection) to avoid immediate retriggering. The appropriate trigger signal will be selected later in the next step. <strong>If no trigger signal is selected, the recording will start immediately</strong>.</li></ul><p><strong>Unchecked:</strong> Channel data is not recorded.</p></td></tr><tr><td><strong>Parity</strong></td><td><p>Configures parity handling for ARINC‑429 words (bit 32).</p><ul><li><strong>On:</strong> The receiver <strong>checks the parity bit</strong> for each received word. If parity is <strong>valid</strong>, the word is accepted as good data. If parity is <strong>invalid</strong>, the word is flagged as erroneous.</li><li><strong>Off:</strong> Parity is <strong>not checked</strong>. Words are accepted regardless of parity correctness.</li></ul></td></tr><tr><td><strong>Enable internal loopback</strong></td><td><strong>Checked:</strong> Creates an internal loopback connection that links each reception channel to its matching transmission channel (e.g. <strong>Tx1 → Rx1</strong>, <strong>Tx2 → Rx2</strong>, and so on).<br><strong>Unchecked:</strong> No internal loopback is applied.</td></tr><tr><td><strong>Enable merged buffer storage</strong></td><td><strong>Checked:</strong> Stores received messages in a <strong>shared merged buffer</strong> (up to <strong>16 384 messages</strong>) that may be shared across channels.<br><strong>Unchecked:</strong> Stores messages in a <strong>dedicated per‑channel buffer</strong> (up to <strong>2 048 messages</strong>).</td></tr></tbody></table>
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

### Manage messages: add, remove, rename, or reorder

In the **Folders** list, click **Messages** and use:

* **+** icon to add messages
* **–** icon to remove messages
* **Arrow** icons to reorder messages

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-eccd5eeb1efca820afdbc407899358d47edb2fab%2FDR-rtlab-arinc6.png?alt=media" alt="" width="506"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure messages

1. In the **Folders** list, expand **Messages** to display all available messages, then select a message to configure its parameters.

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

{% tabs %}
{% tab title="Direction = Transmission" %}

<table><thead><tr><th width="140">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Board</strong></td><td>Assigns the message to one of the <strong>available ARINC‑429 interface boards</strong>.</td></tr><tr><td><strong>Direction</strong></td><td><strong>Transmission:</strong> Message is sent on the ARINC‑429 bus.</td></tr><tr><td><strong>Channel</strong></td><td>Assigns the message to an <strong>available channel</strong> on the selected board.</td></tr><tr><td><strong>Label</strong></td><td>Sets the <strong>ARINC‑429 label value</strong>, expressed in <strong>octal</strong>, for the message transmitted on the bus.</td></tr><tr><td><strong>SDI</strong></td><td>Specifies the <strong>Source/Destination Identifier (SDI)</strong> value, expressed in <strong>binary</strong>. For transmission, a fixed SDI value may be configured; if set to <strong>Unused</strong>, the SDI bits are controlled directly from the message payload, allowing these bits to be used for application‑specific purposes.</td></tr><tr><td><strong>SSM</strong></td><td>Specifies the <strong>Sign/Status Matrix (SSM)</strong> value, expressed in <strong>binary</strong>. For transmission, a fixed SSM value may be configured; if set to <strong>Unused</strong>, the SSM bits are controlled directly from the message payload, allowing application‑specific usage.</td></tr><tr><td><strong>Enable raw data</strong></td><td><strong>Checked:</strong> Exposes the <strong>Raw ARINC Word</strong> connectable point. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>Raw ARINC Word</strong> is available. This channel can be mapped to an <strong>OpOutput</strong> block allowing direct control of the ARINC word contents from the model during execution. The word length is <strong>32 bits</strong>, or <strong>31 bits</strong> if parity is disabled on the channel:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-50ead77667c2ed99c9cac541bc24c4d5e623a9da%2Fimage%20(352).png?alt=media" alt=""><br><strong>Unchecked:</strong> The ARINC word is constructed by the driver based on message configuration.</td></tr><tr><td><strong>Enable dynamic SSM</strong></td><td><strong>Checked:</strong> Exposes the <strong>SSM</strong> connectable point. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>SSM</strong> is available. This channel can be mapped to an <strong>OpOutput</strong> block allowing dynamic control of the <strong>SSM</strong> value from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-b1122cf8faaf8bbdea4f80b095dcdc941679afc5%2Fimage.png?alt=media" alt=""><br><strong>Unchecked:</strong> The SSM value is fixed by the configuration.</td></tr><tr><td><strong>Enable dynamic SDI</strong></td><td><strong>Checked:</strong> Exposes the <strong>SDI</strong> connectable point. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>SDI</strong> is available. This channel can be mapped to an <strong>OpOutput</strong> block allowing dynamic control of the <strong>SDI</strong> value from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-2c3d96acdb7ee511cde48ea07c507da97a03b371%2Fimage%20(343).png?alt=media" alt=""><br><strong>Unchecked:</strong> The SDI value is fixed by the configuration.</td></tr><tr><td><strong>Enable cyclic transmission</strong></td><td><p><strong>Checked:</strong> Enables periodic transmission of the message at a fixed interval:</p><ul><li><strong>Transmit rate (ms):</strong> Specifies the <strong>period</strong> between consecutive transmissions.</li><li><strong>Offset(ms)</strong>: Specifies the <strong>delay</strong> between the start of message processing and the actual transmission of the message on the bus.</li></ul><p><strong>Unchecked:</strong> The message uses the default transmission rate.</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Direction = Reception" %}

<table><thead><tr><th width="140">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Board</strong></td><td>Assigns the message to one of the <strong>available ARINC‑429 interface boards</strong>.</td></tr><tr><td><strong>Direction</strong></td><td><strong>Reception:</strong> Message is received from the ARINC‑429 bus.</td></tr><tr><td><strong>Channel</strong></td><td>Assigns the message to an <strong>available channel</strong> on the selected board.</td></tr><tr><td><strong>Enable label filtering</strong></td><td><p>Filters received messages based on the following:</p><ul><li><strong>Label:</strong> ARINC 429 label value, expressed in <strong>octal</strong>, used to filter messages.</li></ul></td></tr><tr><td><strong>SDI</strong></td><td><strong>Source/Destination Identifier (SDI)</strong> value expressed in binary. For reception, a fixed SDI value is used to filter received messages. When set to <strong>Unused</strong>, no SDI filtering is applied.</td></tr><tr><td><strong>SSM</strong></td><td><strong>Sign/Status Matrix (SSM)</strong> value expressed in <strong>binary</strong>. For reception, a fixed SSM value is used to filter received messages. When set to <strong>Unused</strong>, no SSM filtering is applied.</td></tr><tr><td><strong>Enable raw data</strong></td><td><strong>Checked:</strong> Exposes the <strong>Raw ARINC Word</strong> connectable point. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>Raw ARINC Word</strong> is available. This channel can be mapped to an <strong>OpInput</strong> block allowing to monitor the <strong>Raw ARINC Word</strong> directly from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-93a1ee7b14d96700fa6ea85a32e18f711fe4399f%2Fimage%20(350).png?alt=media" alt=""><br><strong>Unchecked:</strong> The <strong>Raw ARINC Word</strong> connectable point is not exposed.</td></tr><tr><td><strong>Enable timeout monitoring</strong></td><td><p><strong>Checked:</strong> Exposes the <strong>Message Timeout</strong> connectable point. In <strong>Dashboards</strong>, a new <strong>Simulator Channel</strong> named <strong>Message Timeout</strong> is available. This channel can be mapped to an <strong>OpInput</strong> block allowing to monitor the <strong>Message Timeout</strong> directly from the model during execution:<br><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-b9411af6d387c0943bd76f4531c1624606cba37f%2Fimage%20(353).png?alt=media" alt=""></p><ul><li><strong>Transmit rate (ms):</strong> Specifies the maximum expected latency rate.</li></ul><p><strong>Unchecked:</strong> The <strong>Message Timeout</strong> connectable point is not exposed.</p></td></tr><tr><td><strong>Buffer count</strong></td><td>Specifies the number of received messages of this type that can be processed per time step.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

2. Use the signal definition table (bottom section) to describe how individual data elements are encoded within the ARINC message payload. Use:

* **+** icon to add signals
* **–** icon to remove signals
* **Arrow** icons to reorder signals

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

{% hint style="info" %}
The **Frame Viewer** (middle section) provides a visual, bit‑level representation of an **ARINC 429 word**, which consists of **32 bits**. The viewer is displayed when a message item is selected and appears as a **single row with 32 columns**, where each column represents a bit position within the ARINC 429 word.

Colored blocks indicate how individual signals are packed into the word, allowing users to visually verify **bit alignment**, **signal size**, and **signal placement** within the message. Hovering over a bit displays the name of the signal associated with that position.

The Frame Viewer also detects and highlights **overlapping signals**, where multiple signals share part or all of the same bit range. In the example below, *Signal 1* and *Signal 2* overlap between bits 18 and 14, indicating an invalid configuration. After correcting the signal size or position, the Frame Viewer updates to reflect a valid, non‑overlapping layout. Running a simulation with a configuration that contains overlapping signals may result in incorrect data encoding or decoding and should be avoided.
{% endhint %}

<table data-header-hidden><thead><tr><th width="150"></th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Unique signal identifier used to create a connectable in RT‑LAB.</td></tr><tr><td><strong>Encoding</strong></td><td>Signal encoding format: <strong>BNR</strong> (See <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429/bnr-considerations.md">BNR Considerations</a>), <strong>BCD</strong> (See <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429/bcd-considerations.md">BCD Considerations</a>), or <strong>DIS</strong> (Discrete, no special considerations).</td></tr><tr><td><strong>Start bit</strong></td><td>Signal start position in the ARINC‑429 word (BNR excludes the sign bit).</td></tr><tr><td><strong>Size</strong></td><td>Signal length in bits (1–23).</td></tr><tr><td><strong>Initial value</strong></td><td>Initial signal value at model start.</td></tr><tr><td><strong>Min / Max</strong></td><td>Minimum and maximum representable signal values.</td></tr><tr><td><strong>Gain</strong></td><td>Scaling factor applied to the signal value.</td></tr><tr><td><strong>Value offset</strong></td><td>Offset applied to the signal value.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Save the configuration

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-44bd03ce3c41f8ba5c990b61c29b38c9b80ae5f2%2FDR-rtlab-save.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

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