> 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/rt-lab/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/rt-xsg-scope-series-control.md).

# RT-XSG Scope Series Control

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-55aeaec207a22773aaf57f2ef8c555d1e09eb86f%2Fsps-ehs-rtxg-scopepanel.png?alt=media" alt="" width="274"><figcaption></figcaption></figure>

The **RT-XSG Scope Series Control** block, located in the **eFPGAsim/External circuit editor workflow/Monitoring** library, performs the communication with the FPGA in order to send the configuration of the RT-XSG Scope Series.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-a36fbea7e60684c2ed2629871f21af42a0a409c3%2Fsps-ehs-rtxg-scopepanel-mask.jpg?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Scope controls" %}

<table data-search="false"><thead><tr><th>Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Signal Ch1-Ch8</strong></td><td>This list allows to choose which signals going to be monitored. Note that the drop down list correspond to the lists given in the tab Scope signals. Also, the number of channels can be changed dynamically in the Scope properties tab, but cannot exceed the number of channels used to compile the bitstream</td></tr><tr><td><strong>Sampling rate</strong></td><td>This indicates the sampling rate used for the different channels. The value must be between 5 ns and 20 µs.</td></tr><tr><td><strong>Trig Type</strong></td><td>This list allows to choose under which condition should the XSG Scope Series start its sampling.</td></tr><tr><td><strong>Signal Trig</strong></td><td>This list allows to choose which signal is used for triggering the sampling.</td></tr><tr><td><strong>Trigger Threshold</strong></td><td>This allows to add an offset at the trigger condition.</td></tr><tr><td><strong>Trigger Position of the acquisition window relative to the trigger</strong></td><td>This value can be a positive or negative number of samples. It allows to start the acquisition before or after the trigger is achieved.</td></tr><tr><td><strong>Debouncer type</strong></td><td>To avoid triggering due to noise, a trigger can occurs once the trigger condition is met for a certain number of samples.</td></tr></tbody></table>
{% endtab %}

{% tab title="Scope signals" %}

| Parameter                  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Signal Name list 1 - 4** | <p>This field allows to populate the drop down list from which the different signals to observe are selected. Note that the number of Signal Name lists can be changed dynamically in the Scope properties tab, but cannot exceed the number of serial inputs used to compile the bitstream.</p><p>The list should take the following form {'signal 1' 'signal 2' ... 'last signal'}. Note that there is no connection between the name given to the signal and the signal coming from the FPGA. Also, if the list is incomplete, not all signals would be accessible.</p> |
| {% endtab %}               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |

{% tab title="Scope properties" %}

| Parameter                   | Description                                                                                                                                                                                       |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Number of serial inputs** | This list should be set to the value reflecting the number of serial inputs used during the bitstream generation.                                                                                 |
| **Number of channels**      | This list should be set to the value reflecting the number of channels used during the bitstream generation.                                                                                      |
| **Number of samples**       | This list should be set to the value reflecting the number of samples used during the bitstream generation. Note that a good practice would be to set the same value in the RT-Lab Probe control. |
| {% endtab %}                |                                                                                                                                                                                                   |
| {% endtabs %}               |                                                                                                                                                                                                   |

## Inputs

This block has no inputs.

## Outputs

| Output       | Description                                                                                  |
| ------------ | -------------------------------------------------------------------------------------------- |
| **to scope** | This output should be connected to the XSG Scope Series CPU block found in the RT-Lab model. |

## Characteristics and limitations

| Direct Feedthrough   | N/A |
| -------------------- | --- |
| Discrete sample time | YES |
| XHP support          | YES |
| Work offline         | NO  |


---

# 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/rt-lab/simulink-blocks-reference/efpgasim-library/simulink-sps-workflow/rt-xsg-scope-series-control.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.
