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

# GetConnectionsDescription

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Connections</td></tr><tr><td><strong>Description</strong></td><td>Get the connections of a project (excluding datalogger connections)</td></tr><tr><td><strong>Required Control</strong></td><td>None</td></tr><tr><td><strong>Usage</strong></td><td>connectionsInfo = <strong>RtlabApi.GetConnectionsDescription</strong>()<br>(cnxInfo1, cnxInfo2, ...) = connectionsInfo<br>(datapoint1, datapoint2) = cnxInfo1<br>{'optype', ['path'], ['caption'], ['description'], ['label'], ...} = dpoint1</td></tr><tr><td><strong>Input</strong></td><td>None</td></tr><tr><td><strong>Output</strong></td><td><p><strong>connectionsInfo:</strong> A tuple of tuple of information for each connection.</p><p><strong>cnxInfo</strong> : Tuple of 2 dictionnaries (1 per datapoint)</p><p><strong>class</strong>: Datapoint type, could be OP_TYPE_MODEL, OP_TYPE_PANEL or OP_TYPE_IO</p><p><strong>position</strong>: Position in the panel (panel attribute). May be an empty string.</p><p><strong>path</strong>: Datapoint path. May be an empty string.</p><p><strong>type</strong>: Type. May be an empty string.</p><p><strong>label</strong>: Datapoint label. May be an empty string.</p><p><strong>size</strong>: Datapoint size in the panel (panel attribute). May be an empty string.</p><p><strong>direction</strong>: Direction. May be an empty string.</p><p><strong>uiName</strong>: UI name. May be an empty string.</p><p><strong>simulinkId</strong>: Simulink ID. May be an empty string.</p><p><strong>alias</strong>: Alias. May be an empty string.</p></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>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/getconnectionsdescription_143856106.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.
