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

# ExportConnections

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Utilities</td></tr><tr><td><strong>Description</strong></td><td><p>Export connections (excluding datalogger connections) into CSV format The generated file is not supposed to be modified manually to make it work with the <strong>ImportConnections</strong> API. The file includes the following columns:</p><ul><li><em><strong>Connection Type</strong>:</em>enum [model ↔︎ IO; model ↔︎ panel]</li><li><em><strong>Datapoint 1:</strong></em> Primary ID</li><li><em><strong>Datapoint 1:</strong></em> Secondary ID</li><li><em><strong>Datapoint 1:</strong></em> Type</li><li><em><strong>Datapoint 2:</strong></em> Primary ID</li><li><em><strong>Datapoint 2:</strong></em> Secondary ID</li><li><em><strong>Datapoint 2:</strong></em> Type</li></ul><p>For model datapoints, the Primary ID typically corresponds to their alias. However, in projects that use the new I/O interfaces (mandatory starting with version 2025.1), this alias is no longer populated and remains empty.</p><p>The Secondary ID refers to their paths. For IO datapoints, primary ID corresponds to their UI paths where secondary ID may contain GUID in paths.</p></td></tr><tr><td><strong>Required Control</strong></td><td>None</td></tr><tr><td><strong>Usage</strong></td><td><strong>RtlabApi.ExportConnections</strong>(filename, overwrite)</td></tr><tr><td><strong>Input</strong></td><td><p><strong>filename</strong>: Optional argument. Save into 'C:/OPAL-RT/RT-LAB/vX/connections.csv' file per default.</p><p><strong>overwrite</strong>: Optional argument. False per default. Allow to overwrite the csv file if existing.</p></td></tr><tr><td><strong>Output</strong></td><td>None</td></tr><tr><td><strong>Exception</strong></td><td><p><strong>ENOMEM</strong>: Memory allocation error.</p><p><strong>EIO:</strong> Error sending the request or receiving the reply.</p><p><strong>EBADF:</strong> Project not specified by previous OpenProject</p></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related Items</strong></td><td>ImportConnections</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/exportconnections_144216375.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.
