> 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/bnr-considerations.md).

# BNR Considerations

**BNR (Binary Number Representation)** signals use fractional binary encoding and may be configured as **signed** or **unsigned**. This section describes the constraints and rules that must be considered when defining BNR signal parameters within an ARINC 429 message.

## General rules

* The **Start bit** parameter does **not** include the BNR sign bit.
* The **Size (bits)** parameter does **not** include the sign bit, for both single and mixed BNR signal types.
* Per ARINC convention, when a message contains a **single BNR signal** (not mixed with others), the *Digits* value excludes the sign bit.

## Signed and unsigned BNR ranges

* **Signed BNR**\
  Specifies a range of:\
  `[ −Limit , +Limit [`
* **Unsigned BNR**\
  Specifies a range of:\
  `[ 0.0 , +Limit [`

### Signed BNR example

This example shows how to determine the **signal** **definition parameters** required for a signed BNR signal in an ARINC 429 message.

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

**Given requirements**

The signal must represent values:

* From **−512.0** up to **+511.9375**
* With a **resolution of 0.0625**

**Signal** **definition parameters calculation**

Step 1: Determine the **Size (bits)**

* `Size = log₂(Scale / Resolution)`
* From the desired signal range, `Scale = 512.0`.
* From the desired signal resolution, `Resolution = 0.0625`.
* Therefore ` Size = log₂(512 / 0.0625) = log₂(8192) =`` `` `**`13`**

Step 2: Determine the **Start bit**

The **Start bit** specifies where the BNR data field begins in the ARINC 429 word. Since the signal uses **13 data bits** (with the sign bit excluded), the Start bit must be chosen so that the signal fits within the ARINC 429 word without overlapping other fields. Because this is the **first signal in the message**, it can be placed at the **first available most‑significant bit (MSB)** position: ` Start bit =`` `` `**`28`**

### Unsigned BNR example

**Given requirements**

The signal must represent values:

* From **0.0** up to **+512**
* With a **resolution of 0.25**

**Signal** **definition parameters calculation**

Step 1: Determine the **Size (bits)**

* `Size = log₂(Scale / Resolution)`
* From the desired signal range, `Scale = 512.0`.
* From the desired signal resolution, `Resolution = 0.25`.
* Therefore ` Size = log₂(512 / 0.25) = log₂(8192) =`` `` `**`11`**

Step 2: Determine the **Start bit**

The **Start bit** specifies where the BNR data field begins in the ARINC 429 word. Since the signal uses **13 data bits** (with the sign bit excluded), the Start bit must be chosen so that the signal fits within the ARINC 429 word without overlapping other fields. Because this is the **first signal in the message**, it can be placed at the **first available most‑significant bit (MSB)** position: ` Start bit =`` `` `**`28`**


---

# 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/bnr-considerations.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.
