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

# SetAcqTrigger

<table data-header-hidden><thead><tr><th width="199.77783203125"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Configuration, Acquisition</td></tr><tr><td><strong>Description</strong></td><td>Set the acquisition trigger dynamically during the simulation. Data will be acquired only when a specific signal is triggered.<br>The option of starting data acquisition only once a specified threshold is reached allows users to obtain information about a specified time-slice of the simulation.<br>If a block OpTrigger is present in the model when activating the dynamic acquisition, the triggering will be set to the value of parameters provided by SetAcqTrigger.<br>When the parameter “triggerEnabled” in the SetAcqTrigger interface is set to zero, the block OpTrigger will regain the triggering control once again.</td></tr><tr><td><strong>Required Control</strong></td><td>Acquisition Control</td></tr><tr><td><strong>Usage</strong></td><td><strong>RtlabApi.SetAcqTrigger</strong>( acqGroup, signalName, level, trigSignalName, offset, condition, triggerEnabled, trigType)</td></tr><tr><td><strong>Input</strong></td><td><p><strong>acqGroup:</strong> Acquisition group (numbering starts at 0).</p><p><strong>signalName:</strong> Name of the signal to be triggered.</p><p><strong>level:</strong> Specifies the value that must be reached by the trigger signal to trigger acquisition.</p><p><strong>trigSignalName:</strong> Specifies a triggering signal instead of a constant value. If “level” is specified then trigSignalName must be NULL.</p><p><strong>offset:</strong> Used to set the number of steps (cycles) to wait before starting the acquisition system.</p><p><strong>condition:</strong> Condition to be satisfied so that the acquisition system is triggered. See OP_TRIGGER_CONDITION.</p><p><strong>triggerEnabled:</strong> Indicates the status of the trigger: (1/0 = Enable/Disable).</p><p><strong>trigType:</strong> Indicates the trigger type : TRIG_BY_SIGNAL(0) / TRIG_BY_VALUE(1).</p></td></tr><tr><td><strong>Output</strong></td><td>None</td></tr><tr><td><strong>Exception</strong></td><td><p><strong>EOK:</strong> success.</p><p><strong>EACCES:</strong> error saving parameters to .probe file.</p><p><strong>EBADF</strong>: Model not specified by previous Connect or OpenProject.</p><p><strong>EINVAL:</strong> invalid acquisition group.</p><p><strong>EIO:</strong> Error sending the request or receiving the reply.</p><p><strong>ENOMEM:</strong> Memory allocation error.</p><p><strong>EPERM</strong>: System control has not been granted to this client.</p><p><strong>OP_API_EBAD_SIGNAL:</strong> The given signal is invalid.</p></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related Items</strong></td><td>GetAcqTrigger</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/setacqtrigger_144086948.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.
