> 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/hypersim/library-blocks-reference/signal-routing/subcircuit-ports.md).

# Subcircuit Ports

## Description

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-79a995db039eacc7886e516de1812101b4b1797b%2Fimage%20(494).png?alt=media" alt=""><figcaption></figcaption></figure>

The **Subcircuit port** blocks, located in the **Signal Routing** library, provide interfaces within a subsystem to connect internal signals to the pins of the block that represents the subsystem on another page.

{% hint style="info" %}
Subcircuits can be created in many ways, although it is recommended to use the Wizard in the Options ribbon
{% endhint %}

Place subcircuit ports inside the subsystem to map internal signals to the pins of the block representing the subsystem on other pages.

**Available subcircuit port types:**

<table><thead><tr><th width="180.33331298828125" align="center">Port representation</th><th>Description</th></tr></thead><tbody><tr><td align="center"><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-81a0a479158cd30e7971c681eade27dedcae835a%2Fimage%20(330).png?alt=media" alt="" data-size="line"></td><td>Subcircuit port, bundle: use to connect a bundle signal</td></tr><tr><td align="center"><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b7cbd0f55fe44e4ab887d5b9ea67e5fc9659bff6%2Fimage%20(827).png?alt=media" alt="" data-size="line"></td><td>Subcircuit port, power signal: use to connect a network signal</td></tr><tr><td align="center"><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-bd9bd2f2b9d70a60890b56ae0a94605f6fbc5e87%2Fimage%20(1196).png?alt=media" alt="" data-size="line"></td><td>Subcircuit port, control input: use to connect a control signal <strong>entering</strong> the subsystem</td></tr><tr><td align="center"><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-75b0d2577e172c8caaa408588be87fdeaa154069%2Fimage%20(1197).png?alt=media" alt="" data-size="line"></td><td>Subcircuit port, control output: use to connect a control signal <strong>leaving</strong> the subsystem</td></tr></tbody></table>

## Mask parameters

This block has no parameters.

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.


---

# 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/hypersim/library-blocks-reference/signal-routing/subcircuit-ports.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.
