> 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/opalgetacqgroupsignals.md).

# OpalGetAcqGroupSignals

<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, Signal Acquisition</td></tr><tr><td><strong>Description</strong></td><td>Returns the acquisition signals sent to the console subsystem while the model is running. The acquisition signals are the signals sent from the computation nodes to console subsystem in the same order that it was specified at the input of the <strong>OpComm</strong> block for the specified acquisition group.<br>Observes the blocking / non-blocking properties set for the workstation: if blocking is set, will block until data is available; if non-blocking is set, will return EAGAIN when no data is available. In this case, returned values will be equal to zero or last received values depending on the settings specified by the OpalSetAcqBlockLastVal API function.<br>For additional information, please see <strong>Acquiring and Viewing Data</strong> in the <em>RT-LAB User’s Guide</em>.</td></tr><tr><td><strong>Required Control</strong></td><td>None</td></tr><tr><td><strong>Usage</strong></td><td>int <strong>OpalGetAcqGroupSignals</strong>(unsigned short acqGroup,unsigned short allocatedSignals, unsigned int *numSignals, double values[],unsigned short *lastValues, double *timestep);</td></tr><tr><td><strong>Input</strong></td><td><ul><li><strong>acqGroup:</strong> Acquisition group number, starts from 0.</li><li><strong>allocatedSignals:</strong> Number of expected signals.</li></ul></td></tr><tr><td><strong>Output</strong></td><td><ul><li><strong>numSignals:</strong> number of signals in <em>values</em> signals array</li><li><strong>values:</strong> Simulation signals array into which the API will store the acquired signals. May be NULL if allocatedSignals equals 0.</li><li><strong>lastValues:</strong> Pointer to where API stores true when signals are the last in the acquisition buffer (next values will be in a new frame). May be NULL if not of interest.</li><li><strong>timestep:</strong> Simulation timestep of the acquired data. May be NULL if not of interest.</li></ul></td></tr><tr><td><strong>Return value</strong></td><td><ul><li><strong>EOK:</strong> Success.</li><li><strong>E2BIG:</strong> Number of allocated signals is less than the number of group signals.</li><li><strong>EAGAIN:</strong> No data available and the timeout has expired.</li><li><strong>EINVAL:</strong> Specified acquisition group is invalid or not active (does not exist on target).</li><li><strong>EBADF:</strong> Model not specified by previous OpalConnect or OpalSetCurrentModel.</li><li><strong>EIO:</strong> Error sending the request or receiving the reply.</li><li><strong>EACCES:</strong> Not connected a loaded model.</li><li><strong>ENOMEM:</strong> Memory allocation error.</li><li><strong>OP_API_EBAD_SIGNAL:</strong> Doing acquisition of one or more dynamic signals that does no longer exist.</li><li><strong>OP_API_ENO_PRODUCT:</strong> No license for RT-LAB and RT-LABx.</li><li><strong>OP_API_EACQ_MODEL_PAUSED:</strong> no data available because the model is paused.</li></ul></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related items</strong></td><td>None</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/opalgetacqgroupsignals.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.
