> 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/automation-api-and-scripting/rt-lab-api/python-rtlab-api-reference/introduction-to-functions_143429297/getcontrolsignals_144218043.md).

# GetControlSignals

<table data-header-hidden><thead><tr><th width="199.77783203125"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Interaction, Control Signals</td></tr><tr><td><strong>Description</strong></td><td>Return the current values of the control signals sent to the computation nodes.<br>The control signals are the signals sent from the console to the computation nodes in the same order than specified at the input of the OpComm of the specified computation nodes. These signals can be set by a call to SetControlSignals.</td></tr><tr><td><strong>Required Control</strong></td><td>None</td></tr><tr><td><strong>Usage</strong></td><td>values = <strong>RtlabApi.GetControlSignals</strong>(logicalId)</td></tr><tr><td><strong>Input</strong></td><td><strong>logicalId</strong>: Always 0.</td></tr><tr><td><strong>Output</strong></td><td><strong>values:</strong> Tuple of signal values.</td></tr><tr><td><strong>Exception</strong></td><td><p><strong>EOK:</strong> Success.</p><p><strong>EBADF</strong>: Model not specified by previous Connect or OpenProject.</p><p><strong>EINVAL</strong>:Model is not loaded, or invalid logicalId.</p><p>EIO: Error sending the request or receiving the reply.</p><p>ENOMEM: Memory allocation error.</p><p>E2BIG: Specified storage not big enough to receive values.</p></td></tr><tr><td><strong>Examples</strong></td><td>See example control_signal.</td></tr><tr><td><strong>Related Items</strong></td><td>SetControlSignals</td></tr><tr><td><strong>Modules</strong></td><td><strong>import RtlabApi</strong></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/rt-lab/automation-api-and-scripting/rt-lab-api/python-rtlab-api-reference/introduction-to-functions_143429297/getcontrolsignals_144218043.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.
