> 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-the-cmde-add-on-to-the-system-definition.md).

# Configure the CMDE Add-On to the System Definition

## CMDE Add-On page configurations <a href="#configure-the-power-electronics-add-on" id="configure-the-power-electronics-add-on"></a>

In the **System Explorer** window configuration tree, expand **Targets >> Controller >> Custom Devices** and select **CMDE Add-On** to display this page.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2F6KO3SI7RZqyLjjBxEHux%2Fimage.png?alt=media&amp;token=9d8748e6-6228-40b2-bdeb-6691f82a5550" alt=""><figcaption></figcaption></figure>

### **CMDE Add-On Main Page** <a href="#power-electronics-add-on-main-page" id="power-electronics-add-on-main-page"></a>

<table><thead><tr><th width="220.22222900390625">Parameter / Button</th><th>Description</th></tr></thead><tbody><tr><td><strong>Version</strong></td><td>Specifies the version of the CMDE Add-On.</td></tr><tr><td><strong>Configuration</strong></td><td>Selected <a href="https://www.opal-rt.com/docs/cmde-add-on/hardware-configurations-reference/default-hardware-configurations.md"><strong>Hardware Configuration</strong></a> for the project.  The configuration defines the types of FPGA cards to be targeted and the features available in their firmware.</td></tr><tr><td><strong>Configuration Description</strong></td><td>Description of the features included in the selected hardware configuration.  For more detailed information about a configuration, navigate in the <a href="https://www.opal-rt.com/docs/cmde-add-on/hardware-configurations-reference/default-hardware-configurations.md"><strong>Hardware Configurations Reference</strong></a>.</td></tr><tr><td><strong>Target</strong></td><td>Name of the FPGA target onto which the corresponding bitfile will be deployed.  This must match the name of the FPGA target as displayed in the NI Measurement and Automation Explorer.</td></tr><tr><td><strong>Bitfile</strong></td><td>File name of the bitfile to be deployed to the FPGA target.</td></tr></tbody></table>

### Target Credentials

<table><thead><tr><th width="220.22222900390625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Username</strong></td><td>Specify the username for the NI Real Time Target.  The default target username is <strong>admin</strong>. Target credentials can be modified in the NI Measurement and Automation Explorer.</td></tr><tr><td><strong>Password</strong></td><td>Specify the password for the NI Real Time Target.  The default target password is an empty string. Target credentials can be modified in the NI Measurement and Automation Explorer.</td></tr></tbody></table>

### Advanced Performance

<table><thead><tr><th width="220.22222900390625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Loop Rate (us)</strong></td><td>The loop rate of the CMDE Engine as it executes on the Real Time CPU of the deployment target.</td></tr><tr><td><strong>Processor Assignment Mode</strong></td><td><p>Select one of the following modes: </p><ul><li><strong>Automatic</strong> - Processor assignment is configured automatically, and the <strong>Processor</strong> control is disabled. This is the default state.</li><li><strong>Manual</strong> - Processor assignment is configured manually by the user.</li></ul></td></tr><tr><td><strong>Processor</strong></td><td>The index of the Real Time CPU processor on which the CMDE executes.</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/cmde-add-on/model-and-simulation/configure-the-cmde-add-on-to-the-system-definition.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.
