> 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/c-rt-lab-api-reference/functions-reference/opalsetcontrolsignals.md).

# OpalSetControlSignals

<table data-header-hidden><thead><tr><th width="200.66668701171875"></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><p>Sets the current values of the control signals (see <strong>Glossary</strong>) sent to the computation node subsystem. These signals can be return by a call to <strong>OpalSetControlSignals.</strong> The values are sent to the appropriate position at the output of the <strong>OpComm</strong> block, found in the subsystem with the specified <strong>logicalId</strong>, which receives its inputs from the model's console subsystem.<br>All the values must be provided to this function. In order to set only one signal, see</p><p><strong>OpalSetSignalsByName.</strong></p></td></tr><tr><td><strong>Required Control</strong></td><td>Signal Control</td></tr><tr><td><strong>Usage</strong></td><td>int <strong>OpalSetControlSignals</strong> (unsigned short numSignals,unsigned short logicalId, double values[]);</td></tr><tr><td><strong>Input</strong></td><td><ul><li><strong>numSignals:</strong> Number of values to set.</li><li><strong>logicalId:</strong> See <strong>Glossary</strong>.</li><li><strong>values:</strong> Value of each signal.</li></ul></td></tr><tr><td><strong>Output</strong></td><td>None</td></tr><tr><td><strong>Return value</strong></td><td><ul><li><strong>EOK:</strong> Success.</li><li><strong>ENOMEM:</strong> Memory allocation error.</li><li><strong>EINVAL:</strong> Invalid <strong>logicalId</strong>.</li><li><strong>EPERM:</strong> Signal control had not been granted to this client.</li><li><strong>EBADF:</strong> Model not specified by previous OpalConnect or OpalSet CurrentModel.</li><li><strong>EIO:</strong> Error sending the request or receiving the reply.</li><li><strong>EACCES:</strong> No console found in the model. Unable to send signals to sub- systems.</li><li><strong>ESRCH:</strong> Model has not been compiled yet.</li></ul></td></tr><tr><td><strong>Examples</strong></td><td>See example <strong>control_signal</strong>.</td></tr><tr><td><strong>Related items</strong></td><td>OpalGetSignalControl, OpalGetControlSignals</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/c-rt-lab-api-reference/functions-reference/opalsetcontrolsignals.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.
