> 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/telemetry-channels-section.md).

# Telemetry Channels Section

When **Enable Telemetry Channels** is enabled, the **Telemetry Channels** **section** is added to the configuration tree.

The channels are grouped according to the process to which they belong. **FPGA Communication Processes 1**, **2**, and the **Low Latency FPGA Communication Processes** are responsible for CPU-FPGA communication (read/write), while the **Waveform Acquisition Process** is responsible for the acquisition of stream data from waveforms.

{% columns %}
{% column valign="middle" %}

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FIKjyC07IkbbmZvu5dbzT%2Fimage.png?alt=media&amp;token=b4b54673-98c9-4a2f-9f90-ed1af6162f4c" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FQuq0zdeCdaxUfE9H5Uqv%2Fimage.png?alt=media&amp;token=df017ddf-daa2-4b8d-8fa3-d8fa2fa72cc0" alt=""><figcaption><p>Data can be visualized in the screen panel.</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

## **FPGA Communication Process 1**

<table><thead><tr><th width="146.11102294921875">Channel Name</th><th width="99.5555419921875">Type</th><th width="82.7777099609375">Units</th><th>Description</th></tr></thead><tbody><tr><td><strong>Actual Loop Rate</strong></td><td>Output</td><td>Hz</td><td>The execution rate of the FPGA Communication Process.</td></tr><tr><td><strong>Iteration</strong></td><td>Output</td><td></td><td>The iteration count of the FPGA Communication Process.</td></tr><tr><td><strong>Write Time</strong></td><td>Output</td><td>us</td><td>Time taken by the FPGA Communication Process to write the values of the input VeriStand channels to the FPGA model inputs.</td></tr><tr><td><strong>Read Time</strong></td><td>Output</td><td>us</td><td>Time taken by the FPGA Communication Process to read the outputs of the FPGA models and publish them to the output VeriStand Channels.</td></tr><tr><td><strong>Iteration Duration</strong></td><td>Output</td><td>us</td><td>Time taken to execute the last entire iteration of the process.</td></tr><tr><td><strong>Finished Late Count</strong></td><td>Output</td><td></td><td>Number of iterations that have exceeded the specified Loop Rate for this process.</td></tr></tbody></table>

## **FPGA Communication Process 2**

<table><thead><tr><th width="145.22222900390625">Channel Name</th><th width="100.44439697265625">Type</th><th width="83">Units</th><th>Description</th></tr></thead><tbody><tr><td><strong>Actual Loop Rate</strong></td><td>Output</td><td>Hz</td><td>The execution rate of the FPGA Communication Process.</td></tr><tr><td><strong>Iteration</strong></td><td>Output</td><td></td><td>The iteration count of the FPGA Communication Process.</td></tr><tr><td><strong>Read Time</strong></td><td>Output</td><td>us</td><td>Time taken by the FPGA Communication Process to read the outputs of the FPGA models and publish them to the output VeriStand Channels.</td></tr><tr><td><strong>Write Time</strong></td><td>Output</td><td>us</td><td>Time taken by the FPGA Communication Process to write the values of the input VeriStand channels to the FPGA model inputs.</td></tr><tr><td><strong>Iteration Duration</strong></td><td>Output</td><td>us</td><td>Time taken to execute the last entire iteration of the process.</td></tr><tr><td><strong>Finished Late Count</strong></td><td>Output</td><td></td><td>Number of iterations that have exceeded the specified Loop Rate for this process.</td></tr></tbody></table>

## **Low Latency FPGA Communication Process (One per FPGA Target with Low Latency Support)**

<table><thead><tr><th width="145.22222900390625">Channel Name</th><th width="99.55560302734375">Type</th><th width="82.99993896484375">Unit</th><th>Description</th></tr></thead><tbody><tr><td><strong>Actual Loop Rate</strong></td><td>Output</td><td>Hz</td><td>The execution rate of the Low Latency FPGA Communication Process.</td></tr><tr><td><strong>Iteration</strong></td><td>Output</td><td></td><td>The iteration count of the Low Latency FPGA Communication Process.</td></tr><tr><td><strong>Write Time</strong></td><td>Output</td><td>us</td><td>Time taken by the Low Latency FPGA Communication Process to write the values of the input VeriStand channels to the FPGA model inputs.</td></tr><tr><td><strong>Read Time</strong></td><td>Output</td><td>us</td><td>Time taken by the Low Latency FPGA Communication Process to read the outputs of the FPGA models and publish them to the output VeriStand Channels.</td></tr><tr><td><strong>Iteration Duration</strong></td><td>Output</td><td>us</td><td>Time taken to execute the last entire iteration of the process.</td></tr><tr><td><strong>Finished Late Count</strong></td><td>Output</td><td></td><td>This data is not available for Low Latency FPGA Processes. The channel value is always -1.</td></tr><tr><td><strong>Late Samples</strong></td><td>Output</td><td></td><td>Number of samples that have been sent late from the Low Latency Process to the Low Latency Engine on the FPGA. This indicates that the CPU has fallen behind.</td></tr><tr><td><strong>FPGA System Loop Time</strong></td><td>Output</td><td>Ticks</td><td>Measured execution rate of the Low Latency Engine on the FPGA.</td></tr><tr><td><strong>CPU Load Time Value</strong></td><td>Output</td><td>Ticks</td><td>Time measured from the start of the FPGA-to-CPU write data transfer to the completion of the CPU-to-FPGA read data transfer.</td></tr><tr><td><strong>CPU Load Time Maximum</strong></td><td>Output</td><td>Ticks</td><td>Maximum <strong>CPU Load Time Value</strong>.</td></tr><tr><td><strong>Transfer Sequence Number</strong></td><td>Output</td><td></td><td>FPGA-to-CPU Transfer Sequence Number. This value is incremented by the FPGA engine after the FPGA-to-CPU data is transferred to the CPU.</td></tr><tr><td><strong>FPGA Communication State</strong></td><td>Output</td><td></td><td>Last reported state of the Low Latency Engine on the FPGA.</td></tr></tbody></table>

## **Waveform Acquisition Process**

<table><thead><tr><th width="145.22216796875">Channel Name</th><th width="100.44439697265625">Type</th><th width="83">Units</th><th>Description</th></tr></thead><tbody><tr><td><strong>Actual Loop Rate</strong></td><td>Output</td><td>Hz</td><td>The execution rate of the Waveform Acquisition Process.</td></tr><tr><td><strong>Iteration Duration</strong></td><td>Output</td><td>us</td><td>Time taken to execute the last entire iteration of the process.</td></tr><tr><td><strong>Finished Late Count</strong></td><td>Output</td><td></td><td>Number of iterations that have exceeded the specified Loop Rate for this process.</td></tr><tr><td><strong>Iteration</strong></td><td>Output</td><td></td><td>The iteration count of the Waveform Acquisition Process.</td></tr><tr><td><strong>Acquiring</strong></td><td>Output</td><td></td><td>Asserted when the waveform acquisition engine in the FPGA is transferring data to the CPU.</td></tr><tr><td><strong>Synchronized</strong></td><td>Output</td><td></td><td>Asserted when the waveform acquisition engine in the FPGA is synchronized with the CPU.</td></tr><tr><td><strong>Sample Rate per Channel</strong></td><td>Output</td><td>S/s</td><td>Number of samples per channel being acquired and transferred from the FPGA to the CPU every second.</td></tr><tr><td><strong>Block Size per Channel</strong></td><td>Output</td><td></td><td>Size of the memory buffer for each channel on the CPU where the waveform data is stored until it can be processed.</td></tr><tr><td><strong>Overflow</strong></td><td>Output</td><td></td><td>Asserted when the FPGA DMA transfer attempted to write data to the CPU but there was no space available. This type of overflow usually indicates that a PXI backplane bandwidth limit has been reached.</td></tr><tr><td><strong>Overflow Counter</strong></td><td>Output</td><td></td><td>Counts the number of times an overflow occurred since the application was deployed.</td></tr><tr><td><strong>Element in FIFO</strong></td><td>Output</td><td></td><td>Number of elements in the CPU FIFO ready to be read and processed.</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/pe-add-on-simulink/model-and-simulation/add-and-configure-the-pe-add-on-to-the-system-definition/telemetry-channels-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.
