> 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-opal-rt/simulation-control-monitoring-and-logging/display-simulated-signals-using-waveforms.md).

# Display Simulated Signals using Waveforms

NI VeriStand supports the display of **lossless Waveform data** using charts in the VeriStand Editor.

{% stepper %}
{% step %}

## Connect measurements of the circuit to waveform channels

In the schematic editor, add the destination type Waveform Output and select the channel

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FczLE8w492tbg6ARdta82%2Fimage.png?alt=media&amp;token=3d7840c0-3444-4b8a-a4d9-c552408949e0" alt="" width="332"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Create charts in the Screen Panel

Create a new Screen by selecting **File >> New >> Screen** from the menu at the top. Drop a Chart onto the Screen by selecting the ribbon item **Charts >> Chart.**

A Channel Finder widget will pop up automatically. Select the Waveform channels you wish to view.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FKFDim4ABJhiN5DCytGRN%2Fimage.png?alt=media&amp;token=84dc1914-3411-4f87-80fc-6a914c9569b8" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

By default, Waveform data will be streamed and displayed on the chart at **a rate of 100Hz**. To better visualize high frequency signals, select the chart and navigate to its **Item** Properties page on the right-hand side to modify the **Streaming Rate** parameter. If a high **Streaming Rate** is required, consider reducing the **History Length** and **Visible Length** parameters to avoid lagging and hanging in the user interface.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2F9AwxlW0g9WS6wm4RAfOU%2Fimage.png?alt=media&amp;token=666f12c7-6b24-43a2-9fe2-f72e1acfa51c" alt=""><figcaption></figcaption></figure>


---

# 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-opal-rt/simulation-control-monitoring-and-logging/display-simulated-signals-using-waveforms.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.
