> 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-a-circuit-model-to-the-system-definition/waveforms-section.md).

# Waveforms Section

## Overview

Waveforms allow users to view selected simulation signals at higher speeds and with better resolution than that offered by custom device channels. Custom device channels perform single-point acquisition, a non-buffered operation that occurs at the rate at which the Real-Time CPU runs. Waveforms, on the other hand, read and stream FPGA-generated data at rates faster than the Real-Time CPU.

### Waveform Data Transfer and Streaming Rate

As the simulation executes, data generated on the FPGA is sampled by the waveform engine at the user-specified **Sample Rate**, then streamed to one or more of the 32 Waveform channels on the real time CPU. Each individual channel is sampled at the full **Sample Rate**. Because the FPGA executes much faster than the acquisition rate of the waveform engine, the data is first decimated on the FPGA and subsequently stored in an FPGA FIFO. The values stored in the FIFO are transferred over the PXI backplane to a real time buffer on the CPU, then to the VeriStand Waveform channels. All data transfer occurring after the FPGA decimation is lossless.

The maximum achievable Waveform **Sample Rate** is dependent upon the characteristics of the system, although rates of up to **290,000 Samples/second** have been achieved in all supported versions of VeriStand. The number of configured Waveform mappings does not affect the maximum achievable **Sample Rate**; all 32 Waveform channels are transferred at all times, even if they have not been mapped to a **Source**.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2Fjkhj7XQuve7ZE3NAUW3t%2F9ffa5d0a-65f4-4a6b-b3b0-a2a64aee407a.png?alt=media&amp;token=9007296f-c106-471c-9771-788574e3944b" alt=""><figcaption></figcaption></figure>

## Waveforms Configuration Page

In the **System Explorer** window configuration tree, expand the **Power Electronics Add-On** custom device and select **Circuit Model >> Waveforms** to display this page. The page is populated with a list of the Waveforms available in the selected [**Hardware Configuration**](https://www.opal-rt.com/docs/pe-add-on-simulink/hardware-configurations-reference/default-hardware-configurations.md). Simulated signals can be mapped to each Waveform to allow them to be viewed at a higher resolution during the simulation.

### **Waveform Settings**

For each Waveform, the following mapping options are available at edit time:

<table><thead><tr><th width="140.22222900390625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Source</strong></td><td>Filters the list of available elements to be mapped to the waveform channel. The available options are defined by the selected <strong>Hardware Configuration</strong>, however it is typical to see the following options by default:<br><strong>Not Connected:</strong> No signal is mapped to the Waveform.<br><strong>Measurements:</strong> eHS <strong>Measurements</strong> made in the circuit model. In the Element dropdown, select the name of the measurement to map.<br><strong>Machine:</strong> Output channels of the <strong>Machine Model</strong>. In the Element dropdown, select the name of the channel to map.<br><strong>Analog Inputs: Analog Input</strong> channels of the PXI card. In the Element dropdown, select the index of the AI channel to map.</td></tr><tr><td><strong>Element</strong></td><td>The name or index of the channel to be mapped to the Waveform. The options available in this dropdown depend on the selected Source.</td></tr><tr><td><strong>Sample Rate (S/s)</strong></td><td>Sample rate of the data acquisition performed on the FPGA signals by the waveform engine. This <strong>Sample Rate</strong> is per channel, and applies to all the Waveform channels defined.<br>See <strong>Waveform Data Transfer and Streaming Rate</strong> for more information.</td></tr></tbody></table>

## Waveforms Section Channels

The Waveforms section of the Configuration Tree is populated with a list of Waveform channels corresponding to each of the 32 Waveforms available in the Hardware Configuration. Use these tree items to display the mapped signals in Waveform Graphs in the VeriStand Workspace, or in Charts in the VeriStand Editor. More information about this process can be found in [**Display Simulated Signals using Waveforms**](https://www.opal-rt.com/docs/pe-add-on-simulink/simulation-control-monitoring-and-logging/display-simulated-signals-using-waveforms.md).


---

# 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-a-circuit-model-to-the-system-definition/waveforms-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.
