> 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/cmde-add-on/model-and-simulation/configure-devices-within-a-ring/manage-hexadecimal-and-binary-data-in-veristand-channels.md).

# Manage Hexadecimal and Binary Data in VeriStand Channels

When working with devices in the CMDE Add-On, properly managing the different notations of channel data is essential to ensure accurate emulation results and effective user interaction. Channel data for custom devices may be represented in **decimal**, **hexadecimal**, or **binary formats**, and each format requires careful handling. This guide provides a comprehensive overview of how to work with data across these representations.

VeriStand’s flexible user interfaces, known as *Screens*, allow channel data to be displayed or entered in various formats without modifying the underlying values. However, it is important to note that default channel values can only be defined using decimal notation.

Refer to the **device specific documentation** to confirm the format of each VeriStand channel associated with your model.

## Decimal data <a href="#decimal-data" id="decimal-data"></a>

Channels containing decimal data can be mapped to standard numeric controls and numeric indicators in a VeriStand screen.&#x20;

No custom configuration is necessary. Default values of input channels can also be entered as normal.

## Hexadecimal data <a href="#hexadecimal-data" id="hexadecimal-data"></a>

For channels that contain hexadecimal data, configure the display format of numeric controls and indicators within the **VeriStand Screen** to enable users to view and enter values directly in hexadecimal format. This ensures consistency and reduces the risk of input errors during interaction.

When setting the default value of an input channel in the **system definition**, the value must first be converted to its decimal equivalent, as default values only support decimal notation.

### **Configure hexadecimal controls and indicators**

1. In the VeriStand Screen, map the channel to a numeric control or numeric indicator.
2. Right-click the control or indicator and select **Properties**.
3. Expand the **Display Format** section and select **Hexadecimal** from the drop-down menu.
4. Enable the **Show Radix** option.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FtqyaPYKhmiuDscSpCEwX%2Fimage.png?alt=media&amp;token=e45adfd7-0484-40aa-a55b-01248b04ee15" alt=""><figcaption></figcaption></figure>

### **Setting the default value of a hexadecimal channel**

1. In the system definition file, expand the configuration tree and navigate to the channel.
2. Manually convert the desired default value from hexadecimal to decimal.
3. Enter the **decimal value** into the **Default Value** field.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FKsiLi4Wnn1ErY7sTGvuH%2Fimage.png?alt=media&amp;token=41ef8cd6-0d7c-4f9c-b50c-662756cf00df" alt=""><figcaption></figcaption></figure>

## 1-bit binary data <a href="#id-1-bit-binary-data" id="id-1-bit-binary-data"></a>

In the VeriStand screen, **single-bit binary data** channels can be mapped to Boolean controls and indicators, such as checkboxes, switches, or LEDs. It is also possible to use numeric controls and indicators, if desired. &#x20;

Default input channel values in the **System Definition** can simply be entered as 0 or 1.

### **Configure 1-bit binary controls and indicators**

In the VeriStand Screen, map the channel to an appropriate control or indicator.

* For **input channels**, use a switch, button, checkbox, or numeric control.
* For **output channels**, use an LED or numeric indicator.

In case of a numeric control or indicator:

* Right-click the control or indicator and select **Properties**.
* Expand the **Display Format** section and select **Binary** from the drop-down menu.
* Enable the **Show Radix** option.

### **Set the default value of a 1-bit binary channel**

1. In the system definition file, expand the configuration tree and navigate to the channel.
2. Enter 0 or 1 into the **Default Value** field.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2F2huiYarYQRvWG1IWB8Hb%2Fimage.png?alt=media&amp;token=93a15967-93df-478d-9a0b-f6f2aa2f5223" alt="" width="385"><figcaption></figcaption></figure>

## 4-bit binary data <a href="#id-4-bit-binary-data" id="id-4-bit-binary-data"></a>

For channels containing **4-bit binary data**, modify the display format of numeric controls and indicators in the **VeriStand Screen** to allow the user to view and input binary data directly.&#x20;

When configuring the default value of an input channel in the **system definition**, convert the value to decimal first.

### **Configuring 4-bit Binary Controls and Indicators**

1. In the VeriStand Screen, map the channel to a numeric control or numeric indicator.
2. Right-click the control or indicator and select **Properties**.
3. Expand the **Display Format** section and select **Binary** from the drop-down menu.
4. Enable the **Show Radix** option.
5. Set the **Minimum Field Width** to 4.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FHl6hsk4iGjrxmC0w2kI5%2Fimage.png?alt=media&amp;token=57be30c1-810f-4ea1-b9c4-027dca941b8f" alt=""><figcaption></figcaption></figure>

### **Setting the Default Value of a 4-bit Binary Channel**

1. In the system definition file, expand the configuration tree and navigate to the channel.
2. Manually convert the desired default value from binary to decimal.
3. Enter the decimal value into the **Default Value** field.


---

# 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/cmde-add-on/model-and-simulation/configure-devices-within-a-ring/manage-hexadecimal-and-binary-data-in-veristand-channels.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.
