> 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/add-and-configure-the-pe-add-on-to-the-system-definition/processor-assignments.md).

# Processor Assignments

## Overview

At runtime, both the Power Electronics Add-On Engine and the VeriStand Engine execute their own sets of processes on the Real Time CPU of the deployment simulator. The processes managed by the Power Electronics Add-On Engine are described in the figure and table below. For more information related to the processes managed by the VeriStand Engine, refer to the [**VeriStand Engine**](https://www.ni.com/docs/en-US/bundle/veristand/page/vs-engine.html) Help documentation on the National Instruments website.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FeTIMy7kKvRGoX977l7jy%2Fimage.png?alt=media&amp;token=74fdff87-43f1-409b-a95f-5aa5b94efa3f" alt="" width="480"><figcaption><p>Processes managed by the Power Electronics Add-On Engine</p></figcaption></figure>

<table><thead><tr><th>Process</th><th width="299.88897705078125">Description</th><th width="139.77783203125">Priority</th><th>Default Execution Rate</th></tr></thead><tbody><tr><td><strong>Power Electronics Add-On Inline Process</strong></td><td>Highest level inline process in charge of initializing, launching asynchronous processes, shutdown and error handling of the custom device.</td><td>High<br>(Defined by the VeriStand Primary Control Loop)</td><td>(Defined by the VeriStand Primary Control Loop)</td></tr><tr><td><strong>FPGA Communication Process 1</strong></td><td>First asynchronous process establishing read and write communication between VeriStand Channels in Real Time, and their corresponding features on the FPGA. In the case of a hardware configuration with multiple FPGAs, this process communicates with all of them.</td><td>High</td><td>500 Hz</td></tr><tr><td><strong>FPGA Communication Process 2</strong></td><td>Second asynchronous process establishing read and write communication between VeriStand Channels in Real Time, and their corresponding features on the FPGA. In the case of a hardware configuration with multiple FPGAs, this process communicates with all of them.</td><td>High</td><td>5 kHz</td></tr><tr><td><strong>Low Latency FPGA Communication Processes</strong></td><td>Set of asynchronous processes for low latency read and write communication between VeriStand Channels and their corresponding features on the FPGA. In the case of a hardware configuration with multiple FPGAs, a process is dedicated to each FPGA.</td><td>High</td><td>10 kHz</td></tr><tr><td><strong>Waveform Acquisition Process</strong></td><td>Asynchronous process in charge of data communication between the FPGA target and VeriStand <a href="https://www.opal-rt.com/docs/pe-add-on-simulink/model-and-simulation/add-and-configure-a-circuit-model-to-the-system-definition/waveforms-section.md"><strong>Waveforms</strong></a> on the Real Time CPU.</td><td>Low</td><td>100 Hz</td></tr></tbody></table>

{% hint style="info" %}
Processor assignment is managed by the Power Electronics Add-On by default. In most cases, manual processor assignment is not required and the **Processor Assignment Mode** must be set to **Automatic**.
{% endhint %}

However, if the project contains one or more of the following, please contact [OPAL-RT Support](https://www.opal-rt.com/contact-technical-support/) for assistance manually assigning CPU processors:

* A custom hardware configuration consisting of two or more FPGAs
* Additional VeriStand custom devices whose performance may conflict with the Power Electronics Add-On
* A specific component (such as a CPU simulation model) that must execute at an increased speed, potentially at the expense of the performance of other processes

## Processor Assignments Dialog Window

The Processor Assignments Dialog Window is used to assign specific CPU processors to the Power Electronics Add-On processes.

In the **System Explorer** window configuration tree, select the **Power Electronics Add-On** custom device, then click the **Processor Assignments** button under **Advanced Performance** section to display this dialog window.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FcgtbaPcQV3xSYPQOYDsH%2Fimage.png?alt=media&amp;token=dd31f0e5-f9f1-4a3a-9390-cb3048a05faa" alt="" width="249"><figcaption></figcaption></figure>

### **General Processor Assignment Settings**

<table><thead><tr><th width="239.77777099609375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Processor Assignment Mode</strong></td><td><p>Select one of the following modes:</p><ul><li><strong>Automatic</strong> - Processors assignments are configured automatically, and all other dialog controls are disabled. This is the default state.</li><li><strong>Manual</strong> - Processor assignments can be configured manually by the user. This mode enables all dialog controls.</li></ul></td></tr></tbody></table>

### **FPGA Communication Process 1**

<table><thead><tr><th width="239.77777099609375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Processor</strong></td><td>The index of the CPU processor on which FPGA Communication Process 1 executes.</td></tr><tr><td><strong>Loop Rate (us)</strong></td><td>The loop rate of FPGA Communication Process 1, in microseconds.</td></tr></tbody></table>

### **FPGA Communication Process 2**

<table><thead><tr><th width="239.77783203125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Processor</strong></td><td>The index of the CPU processor on which FPGA Communication Process 2 executes.</td></tr><tr><td><strong>Loop Rate (us)</strong></td><td>The loop rate of FPGA Communication Process 2, in microseconds.</td></tr></tbody></table>

### **Low Latency FPGA Communication Process**

This table displays the available FPGA targets supporting Low Latency Communication. The following parameters are configurable for each FPGA target.

<table><thead><tr><th width="239.77777099609375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Processor 1</strong></td><td><p>The index of the CPU processor on which the Low Latency FPGA Communication Process of the specified FPGA target executes.</p><p>For hardware configurations with two or more FPGAs, it is recommended to dedicate one CPU core per Low Latency FPGA Communication Process, and to avoid sharing it with any other process from this or another custom device.</p></td></tr><tr><td><strong>Loop Rate (us)</strong></td><td>The loop rate of Low Latency FPGA Communication Process of the specified FPGA target, in microseconds.</td></tr></tbody></table>

### **CPU Pool Assignment**

Use this section to assign individual CPU cores to pools available for automatic load balancing. For additional information, refer to [Specifying the Set of CPUs Available for Automatic Load Balancing](https://www.ni.com/docs/en-US/bundle/labview-real-time-module/page/lvrtconcepts/smp_api.html#d46e94) in the NI LabVIEW Real-Time Module Help documentation.

<table><thead><tr><th width="239.77783203125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Apply CPU Pool Assignments</strong></td><td>Enables the <strong>CPU Pool Assignment</strong> settings to be enforced on the CPU/controller. Disabling the checkbox will cause the engine to ignore the request to configure the <strong>CPU Pool Assignment</strong> entirely.</td></tr><tr><td><strong>CPU Pool Assignment</strong></td><td><p>For each CPU available on the Real Time controller, select from one of the following states:</p><ul><li><strong>System</strong> - the CPU can be used to execute threads that do not correspond to Timed Structures</li><li><strong>Timed Structures</strong> - the CPU can be used to execute Timed Structures configured for automatic processor assignment</li><li><strong>System &#x26; Timed Structures</strong> - the CPU can be used to execute either of the above</li><li><strong>Reserved</strong> - the CPU is dedicated solely to executing Timed Structures manually assigned to that CPU</li></ul><p>This table is enabled only when the <strong>Manual CPU Pool Configuration</strong> checkbox is enabled. By default, the Power Electronics Add-On will assign all CPUs to the <strong>System &#x26; Timed Structures</strong> pools, except CPUs on which the Low Latency FPGA Communication Process executes. These CPUs are assigned to the <strong>Reserved</strong> pool.</p><p>Please refer to the appropriate NI specification documentation to determine the number of available CPUs on your Real Time controller.</p></td></tr><tr><td><strong>Manual CPU Pool Configuration</strong></td><td>Enables the <strong>CPU Pool Assignment</strong> table. Disabling the checkbox will reset the <strong>CPU Pool Assignment</strong> table to default values.</td></tr></tbody></table>

{% hint style="info" %}
**All CPU assignment fields use a zero-indexed convention**, where the first CPU core is represented by the number 0.
{% endhint %}


---

# 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/add-and-configure-the-pe-add-on-to-the-system-definition/processor-assignments.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.
