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

# GetAcqGroupSyncSignals

<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><p>Return 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 OpComm block for the specified acquisition group. The outputs contains two arrays: acquisition signals + monitoring signals.</p><p>The user can activate the synchronization algorithm to synchronize the acquisition time with the simulation time by inserting data during missed data intervals. The interpolation can be used in this case to get a better result during missed data intervals. Threshold time between acquisition time and simulation time exceeds the threshold, the acquisition (console) will be updated to overtake the difference. The acqtimestep offers the user a way to change his console step size as in Simulink.</p><p>For additional information, please see the section <a href="https://www.opal-rt.com/docs/rt-lab/simulation-control-monitoring-and-logging/interact-using-dashboards.md">Simulation Control, Monitoring &#x26; Logging</a></p><p><strong>Monitoring signals tuple contains 4 values:</strong></p><ul><li><strong>missed data:</strong> number of values between two acquisition frame. If value is 0, there are no missing data between the two frames. Missing data may appears if network communication and display are too slow to refresh value generated by the model.</li><li><strong>offset:</strong> simulation time when the acquisition started.</li><li><strong>target simulation time:</strong> simulation time of the model when the acquisition has been done.</li><li><strong>Sample/sec:</strong> number of sample/sec received from target. Calculation is made for one sample. Ex: If model is running at 0.001s, sample/sec value should not exceed 1000 sample/sec.</li></ul></td></tr><tr><td><strong>Required Control</strong></td><td>None</td></tr><tr><td><strong>Usage</strong></td><td>results = <strong>RtlabApi.GetAcqGroupSyncSignals</strong>(acquisitionGroup, synchronization, interpolation, threshold, acqTimeStep) (values, monitoringInfo, simulationTimeStep, endFrame) = results (value1, value2, value3, ...) = values (missedData, offset, simulationTime, sampleSec) = monitoringInfo</td></tr><tr><td><strong>Input</strong></td><td><p><strong>acquisitionGroup</strong>: Acquisition group number, starts from 0.</p><p><strong>synchronization</strong>: Synchronization 1/0 = Enable/Disable</p><p><strong>interpolation</strong>: Interpolation 1/0 = Enable/Disable</p><p><strong>threshold:</strong> Threshold difference time between the simulation and the acquisition (console) time in seconds.</p><p><strong>acqTimeStep</strong>: Sample interval: acquisition (console) timestep must be equal or greater than the model time step.</p></td></tr><tr><td><strong>Output</strong></td><td><p><strong>values</strong>: Acquired signals from acquisition. It contains a tuple of values with one value for each signal in the acquisition group.</p><p><strong>monitoringInfo</strong>: Monitoring information tuple. It contains the following values: Missed data, offset, simulationTime and sampleSec. See below for more details.</p><p><strong>missedData</strong>: Number of values between two acquisition frame. If value is 0, there are no missing data between the two frames. Missing data may appears if network communication and display are too slow to refresh value generated by the model.</p><p><strong>offset:</strong> Simulation time when the acquisition started.</p><p><strong>simulationTime:</strong> Simulation time of the model when the acquisition has been done.</p><p><strong>sampleSec</strong>: Number of sample/sec received from target. Calculation is made for one sample. Ex: If model is running at 0.001s, sample/sec value should not exceed 1000 sample/sec.</p><p><strong>simTimeStep</strong>: Simulation timestep of the acquired data.</p><p><strong>endFrame</strong>: True when signals are the last in the acquisition buffer (next values will be in a next frame).</p></td></tr><tr><td><strong>Exception</strong></td><td><p><strong>EOK:</strong> Success</p><p>E2BIG:**Number of allocated signals is less than the number of group signals.</p><p><strong>EAGAIN:</strong> No data available and timeout has expired.</p><p><strong>EINVAL:</strong> Specified acquisition group is invalid or not active (does not exist on target).</p><p><strong>EBADF:</strong> Model not specified by previous Connect or OpenProject.</p><p><strong>EIO</strong>: Error sending the request or receiving the reply.</p><p><strong>EACCES:</strong> Not connected to a loaded model.</p><p><strong>ENOMEM:</strong> Memory allocation error.</p><p><strong>OP_API_EBAD_SIGNAL</strong>: Doing acquisition of one or more dynamic signals that does no longer exist.</p><p><strong>OP_API_ENO_PRODUCT:</strong> No license for RT-LAB.</p></td></tr><tr><td><strong>Examples</strong></td><td>See example <strong>acquisition1.</strong></td></tr><tr><td><strong>Related Items</strong></td><td>None</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/getacqgroupsyncsignals_144087045.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.
