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

# Load

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Execution</td></tr><tr><td><strong>Description</strong></td><td>Load the model's executables in memory. Upon successful return, all subsystems are loaded and waiting for the Execute command. The subsystems are loaded on the nodes associated to them in the last call to <strong>SetNodeMapping</strong>.</td></tr><tr><td><strong>Required Control</strong></td><td>System control</td></tr><tr><td><strong>Usage</strong></td><td>instanceId = <strong>RtlabApi.Load</strong>( realTimeMode, timeFactor)</td></tr><tr><td><strong>Input</strong></td><td><p><strong>realTimeMode:</strong> See <strong>OP_REALTIME_MODE.</strong></p><p><strong>timeFactor:</strong> See <strong>Glossary.</strong></p></td></tr><tr><td><strong>Output</strong></td><td><strong>instanceId:See Glossary.</strong></td></tr><tr><td><strong>Exception</strong></td><td><p><strong>EOK:</strong> Success.</p><p><strong>ENOENT:</strong> No such file or directory.</p><p><strong>EPERM:</strong> System control requested, but already given to another client.</p><p><strong>EBUSY:</strong> Node busy (another subsystem already loaded on it).</p><p><strong>EBADF:</strong> Model not specified by previous Connect or OpenProject.</p><p><strong>E2BIG:</strong> More than 1 acquisition group found for simulation without data.</p><p><strong>EINVAL:</strong> Invalid Time Factor value or invalid model path.</p><p><strong>EACCES:</strong> Trying to load a Dinamo model with more than one subsystem (currently not supported).</p><p><strong>EIO:</strong> Error sending the request or receiving the reply.</p><p><strong>ENOMEM:</strong> Memory allocation error.</p><p><strong>ESRCH:</strong> Model instance id not found.</p><p><strong>OP_API_EBAD_PHYS_NODE:</strong> A subsystem is not assigned to a physical node or is assigned to an invalid physical node.</p><p><strong>OP_API_EBAD_CONFIG:</strong> Error reading configuration file or invalid setting found in the configuration file.</p><p><strong>OP_API_EBAD_DEV_ENV:</strong> Could not get the target development node.</p><p><strong>OP_API_MODEL_IO_TIMEOUT:</strong> Timed out waiting for a reply from the model.</p><p><strong>OP_API_MODEL_IO_ERROR:</strong> Model is missing some or all processes or subsystems.</p><p><strong>OP_API_ENO_NODE_LICENSE</strong>: Not enough licenses (number of model's subsys is greater than the number of available node licenses).</p><p><strong>OP_API_ENO_TARGET_LICENSE:</strong> No license for selected target.</p><p><strong>OP_API_ENO_RTCOMM_LICENSE:</strong> No license for selected real time communication.</p><p><strong>OP_API_ENO_TARGET_MULT_LICENSE:</strong> No license for multiprocessing.</p><p><strong>OP_API_ENO_DINAMO_LICENSE:</strong> No license for dinamo.</p><p><strong>OP_API_ENO_POLLING_LICENSE:</strong> No license for XHP mode.</p><p><strong>OP_API_ERR_LOAD_EMBEDDED:</strong> Model's instance Id is reserved for embedded mode.</p><p><strong>OP_API_ERR_LOAD_CALC_STEP</strong>: Calculation step is invalid (usually &#x3C;= 0).</p><p><strong>OP_API_EBAD_SIGNAL:</strong> At least one signal (id or element) is not found.</p><p><strong>OP_API_ENO_DYN_SIGNAL:</strong> Trying to set dynamic signals for an acquisition group that is not set to accept some.</p></td></tr><tr><td><strong>Examples</strong></td><td>See example <strong>basic_example2</strong>.</td></tr><tr><td><strong>Related Items</strong></td><td>Reset, GetModelState, GetSystemControl.</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/load_143693923.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.
