> 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/pe-add-on-simulink/model-and-simulation/configure-the-hardware-fpga/digital-outputs-section.md).

# Digital Outputs Section

This page is populated with a list of the Digital Output channels available for the selected [**Hardware Configuration**](https://www.opal-rt.com/docs/pe-add-on-simulink/hardware-configurations-reference/default-hardware-configurations.md). Map machine sensor outputs and other simulated signals to each Digital Output channel to interact with external hardware.

The following configuration options are available for each channel, configurable at edit-time only:

## Digital Output Settings

### **Source**

Filters the list of available **Elements** to be mapped to the Digital Output channel. The available options are defined by the selected [**Hardware Configuration**](https://www.opal-rt.com/docs/pe-add-on-simulink/hardware-configurations-reference/default-hardware-configurations.md), however it is typical to see the following options by default:

<table data-header-hidden><thead><tr><th width="210.4444580078125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Not Connected</strong></td><td>No signal is mapped to the physical channel.</td></tr><tr><td><strong>CPU (VeriStand)</strong></td><td>VeriStand custom device channels on the CPU. If this Source is selected, the <strong>Element</strong> dropdown is populated with a single option displaying the name of the custom device channel whose value is mapped.</td></tr><tr><td><strong>Encoders</strong></td><td>Output channels of the <strong>Encoder</strong> sensor models. In the <strong>Element</strong> dropdown, select the name of the channel to map.</td></tr><tr><td><strong>PWMs</strong></td><td>PWM outputs of the <strong>PWM Generators Section</strong>. In the <strong>Element</strong> dropdown, select the index of the PWM Generator whose output signal to map.</td></tr><tr><td><strong>Digital Inputs</strong></td><td><strong>Digital Input</strong> channels. In the <strong>Element</strong> dropdown, select the index of the channel to map.</td></tr><tr><td><strong>Element</strong></td><td>The name or index of the signal to be mapped to the digital output channel. The options available in this dropdown depend on the selected <strong>Source</strong>.</td></tr><tr><td><strong>Polarity</strong></td><td>The polarity of the signal. Active High signals output a HIGH voltage when the signal is True and a LOW voltage when the signal is False. Active Low signals output a HIGH voltage when the signal is False and a LOW voltage when the signal is True.</td></tr></tbody></table>

## Digital Outputs Section Channels

This section includes the following custom device channels:

<table><thead><tr><th width="209.6444091796875">Channel Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>ConnX.DIO</strong> <strong>XX (Input)</strong></td><td><p>The Digital Outputs section is populated with one <strong>ConnX.DIO</strong> <strong>XX</strong> custom device channel for each physical Digital Output channel available in the selected <a href="https://www.opal-rt.com/docs/pe-add-on-simulink/hardware-configurations-reference/default-hardware-configurations.md"><strong>Hardware Configuration</strong></a>.</p><p>If the <strong>CPU (VeriStand)</strong> Source option is mapped to a Digital Output channel, the value of its corresponding <strong>ConnX.DIO</strong> <strong>XX</strong> custom device channel drives the output of the physical channel. If the <strong>CPU (VeriStand)</strong> mapping option is unused, the value of the channel does not affect the Digital Outputs or the simulation.</p></td></tr></tbody></table>


---

# 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/pe-add-on-simulink/model-and-simulation/configure-the-hardware-fpga/digital-outputs-section.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.
