> 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/enumeration-and-define/op_events.md).

# OP\_EVENTS

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Description</strong></td><td><p>Use these enum to register an event with the OpalSetNotificationCallback function. When one of the following events is detected, a notification is sent to all registered API.</p><p>Use values greater than OP_USER_BASE_EVENTS(1024) to define your own events.</p></td></tr><tr><td><strong>Usage</strong></td><td>see Elements</td></tr><tr><td><strong>Elements</strong></td><td><ul><li><strong>OP_SYSTEM_PRINT (0):</strong> OpalPrint has been called on target.</li><li><strong>OP_SYSTEM_PAUSE (1):</strong> The model is paused.</li><li><strong>OP_SYSTEM_CONTINUE (2):</strong> The model is executed.</li><li><strong>OP_SYSTEM_TRIM (3):</strong> The model is trimming.</li><li><strong>OP_SYSTEM_RESET (4):</strong> The model is reset.</li><li><strong>OP_SYSTEM_STOP (5):</strong> The model stopped by itself normally.</li><li><strong>OP_SYSTEM_DISCONNECT (6):</strong> The model is disconnected (connection with target has been lost)</li><li><strong>OP_SYSTEM_ERROR (7):</strong> The model stopped by itself with errors.</li><li><strong>OP_SYSTEM_MESSAGE (8):</strong> A system message is available.</li><li><strong>OP_SYSTEM_OVERRUN (9):</strong> An overrun occur on target.</li><li><strong>OP_SYSTEM_INTERRUPTS_ON (10):</strong> XHP is disabled.</li><li><strong>OP_SYSTEM_INTERRUPTS_OFF (11):</strong> XHP is enabled.</li><li><strong>OP_SYSTEM_CONTROL_LOST (12):</strong> System control has been lost (it should have been taken before).</li><li><strong>OP_SYSTEM_CONTROL_TAKEN (13):</strong> System control has been taken by another API.</li><li><strong>OP_SYSTEM_CONTROL_AVAIL (14):</strong> System control has been released by another API.</li><li><strong>OP_PARAMETER_UPDATE (15):</strong> Some parameters have been modified on target.</li><li><strong>OP_PARAMETER_CONTROL_LOST (16):</strong> Parameter control has been lost (it should have been taken before).</li><li><strong>OP_PARAMETER_CONTROL_TAKEN (17):</strong> Parameter control has been taken by another API.</li><li><strong>OP_PARAMETER_CONTROL_AVAIL (18):</strong> Parameter control has been released by another API.</li><li><strong>OP_SNAPHOT_TAKE (19):</strong> A snapshot has been taken.</li><li><strong>OP_SNAPSHOT_RESTORE (20):</strong> A snapshot has been restored.</li><li><strong>OP_SNAPSHOT_CONTROL_LOST (21):</strong> Snapshot control has been lost (it should have been taken before).</li><li><strong>OP_SNAPSHOT_CONTROL_TAKEN (22):</strong> Snapshot control has been taken by another API.</li><li><strong>OP_SNAPSHOT_CONTROL_AVAIL (23):</strong> Snapshot control has been released by another API.</li><li><strong>OP_SIGNAL_CHANGE (24):</strong> A control signal has been sent to the target.</li><li><strong>OP_SIGNAL_CONTROL_LOST (25):</strong> Signal control has been lost (it should have been taken before).</li><li><strong>OP_SIGNAL_CONTROL_TAKEN (26):</strong> Signal control has been taken by another API.</li><li><strong>OP_SIGNAL_CONTROL_AVAIL (27):</strong> Signal control has been released by another API.</li><li><strong>OP_ACQGR_CONTROL_LOST (28):</strong> Acquisition control has been lost (it should have been taken before).</li><li><strong>OP_ACQGR_CONTROL_TAKEN (29):</strong> Acquisition control has been taken by another API.</li><li><strong>OP_ACQGR_CONTROL_AVAIL (30):</strong> Acquisition control has been released by another API.</li><li><strong>OP_BLOB_CONTROL_LOST (31):</strong> Blob control has been lost (it should have been taken before).</li><li><strong>OP_BLOB_CONTROL_TAKEN (32):</strong> Blob control has been taken by another API.</li><li><strong>OP_BLOB_CONTROL_AVAIL (33):</strong> Blob control has been released by another API.</li><li><strong>OP_MONITORING_CONTROL_LOST (34):</strong> Monitoring control has been lost (it should have been taken before).</li><li><strong>OP_MONITORING_CONTROL_TAKEN (35):</strong> Monitoring control has been taken by another API.</li><li><strong>OP_MONITORING_CONTROL_AVAIL (36):</strong> Monitoring control has been released by another API.</li><li><strong>OP_CONFIG_CONTROL_LOST (37):</strong> Configuration control has been lost (it should have been taken before).</li><li><strong>OP_CONFIG_CONTROL_TAKEN (38):</strong> Configuration control has been taken by another API.</li><li><strong>OP_CONFIG_CONTROL_AVAIL (39):</strong> Configuration control has been released by another API.</li><li><strong>OP_DYN_ACQ_LIST_UPDATE (42):</strong> List of dynamic acquisition has been updated.</li><li><strong>OP_ALL_EVENTS:</strong> Always the last item, may vary.</li><li><strong>OP_USER_BASE_EVENTS:</strong> 1024, base event number for user notification.</li></ul></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related Items</strong></td><td>OpalSetNotificationCallback, OpalSetNotificationCallbackForModel</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/enumeration-and-define/op_events.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.
