> 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/simulation-control-monitoring-and-logging/monitor-veristand-channel-values-at-execution-time.md).

# Monitor VeriStand Channel Values at Execution Time

## Procedure

VeriStand provides the [**Channel Data Viewer**](https://www.ni.com/docs/en-US/bundle/veristand/page/channel-data-viewer.html) tab to allow users to monitor multiple channel values at runtime, without the need to display them on a user interface.

{% stepper %}
{% step %}

### Display the Channel Data Viewer

In the VeriStand Editor, navigate to **View** > **Channel Data Viewer** to display a list of all channels in the VeriStand project.
{% endstep %}

{% step %}

### Filter channels

* Type into the **Filter** text box to filter channels by name or path.
* Use the **Channel Filter** pull-down menu to select the type of channels to display.
  {% endstep %}

{% step %}

### Update writeable channel values

If desired, update the value of a writeable channel by entering the new value into the **Pending Value** cell, then click **Apply Pending Changes**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
VeriStand channel values can also be monitored and updated by mapping them to controls, indicators, and graphs on a VeriStand Screen.
{% endhint %}

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2F0VTu2bQpAC6hrtkxaYDG%2F0f6effc3-4cf7-401f-9c3d-3c66c3878caf.png?alt=media&amp;token=4eed8a95-a5a3-4392-a07c-1bb6c6181cb7" 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-simulink/simulation-control-monitoring-and-logging/monitor-veristand-channel-values-at-execution-time.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.
