> 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/scopeview/get-started/select-signals-to-acquire.md).

# Select Signals to Acquire

<figure><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2FKNHxXkLlqYeMj5fuUT5f%2Fimage.png?alt=media&amp;token=9a8f619e-9d2f-457d-969b-66b88793863f" alt=""><figcaption></figcaption></figure>

## Select the signals to acquire

{% stepper %}
{% step %}

### Choose the Signal Type

1. Under **Data Source**, select the **Signal Type** from the pull-down menu.
   * This list reflects the sensors available in your simulation or database.
2. Signals of the selected type will appear in the **Available Signals** area.
3. Only **one signal group** can be selected per Data Source Chooser dialog.
   {% endstep %}

{% step %}

### Choose the Signal Selection Mode

In the **Signal Processing** area, choose how you want to select signals:

* **Single:** Clicking a signal immediately moves it to the **Selected Signals** list.
* **Multiple:** Select several signals using **CTRL + Click**, then click **Add Signals**. The **Add Signals** button appears only when **Multiple** mode is active.
  {% endstep %}

{% step %}

### Select and manage signals

Once chosen, signals appear in the **Selected Signals** area along with their properties:

* **Signal:** Confirms the selected signal name.
  * Click a cell to edit; press **Enter** to apply changes or **Esc** to cancel.
* **Description:** Displays the signal description (often identical to the signal name).
* **Show:** When checked, the signal will be acquired and displayed in ScopeView.
* **Page:** Indicates on which page the signal’s graph will appear.

The numbered column on the far left provides access to the context menu.

* **Right-click** a row to open editing options.
  {% endstep %}

{% step %}

### Configure how signals are graphed

In the **Signal Processing** area, configure graphing options:

#### Graph Creation

* **Normal:** Displays one signal per graph.
* **Superimposed:** Displays multiple signals on the same graph.

#### **X Axis and Y Axis options**

* **Grid:** Shows or hides the grid.
* **Log:** Switches the axis between linear and logarithmic scale.
* You may check **Grid**, **Log**, **both**, or **neither**.

#### Data

* **Auto Load:** Automatically loads selected signals from pre-recorded files. Supported for all formats except `.oprec`.

#### Page

* Select the **page number** where the signal’s graph should appear.

#### Function

You can apply mathematical functions to transform or enhance the signal before it is displayed.

**To apply a** [**basic function**](https://www.opal-rt.com/docs/scopeview/use-functions/basic-functions.md)**:**

1. Select the function from the pull-down list.
2. Click the signal to be added.

**To apply an advanced function:**

1. Click the **ellipsis (...)**. All advanced functions are described in the [**Use Functions**](https://www.opal-rt.com/docs/scopeview/use-functions/basic-functions.md) section.
2. Click the signal you want to modify.
3. Choose a **function Category** (or select **All** to view every function).
4. Pick a function from the **Function Name** list.
5. Click **Add Function** to apply it.

<figure><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2FBh7No2VDuGQRApofaFp7%2Fimage.png?alt=media&amp;token=10f32e63-a992-4d0b-9f9f-460bd04405df" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Review the selected signals

The **Selected Signals** list displays all signals currently chosen for evaluation. Each line represents a signal (and, if applicable, an associated function) and specifies key characteristics: **Description**, **Show**, and **Page**.

* **Description:** Identifies the result of the formula in the graph. ScopeView generates a default description when a new formula is inserted, consisting of an abbreviation for the applied operation and the name(s) of the selected signal(s). You can also enter a custom description.
* **Show:** When checked, ScopeView will display the formula result in a graph. This box is automatically selected when a signal or function is added from the **Signals** list. For manually created formulas, checking **Show** sets the **Page** field to 1 by default, which can be adjusted as needed.
* **Page:** Specifies the graphic page where the formula result will appear.

By default, formulas are displayed in the order they appear in the list. After the first acquisition, you can change the display order by moving the graphs interactively. The **Selected Signal** field identifies the formula to evaluate, which can be generated automatically or created manually.

## Start the acquisition

To begin acquiring data, click the **Play** button in the **Signals** form:

<figure><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2FNFETO5OLZs79p2SN6DTI%2Fimage.png?alt=media&amp;token=ddf1229c-e09d-4433-bedd-ecbaec6243c7" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **Main** window also provides its own **Play** button to start the acquisition.
{% endhint %}


---

# 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/scopeview/get-started/select-signals-to-acquire.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.
