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

# Page Connectors

## Description

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

The **Page connector** blocks, located in the **Signal Routing** library, mark and manage name-based connections for signals that span multiple schematic pages. HYPERSIM automatically connects signals that share the same name across pages. Page connectors provide a visual indicator of these logical connections and display the location of connected signals relative to the background grid. This location display works even when the grid is hidden; you can toggle grid visibility using the Border Wizard in the Options ribbon.

**Available page connector 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-7f8a5fcbc0bca8a01f1231c53e4ae72e31a873e9%2Fpage_connector_1.png?alt=media" alt="" data-size="line"></td><td><strong>Page connector bundle</strong>: use on any bundle, whatsoever its content</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-05d058f36754191fffc640b08d87a7e814e5797f%2Fpage_connector_12.png?alt=media" alt="" data-size="line"></td><td><strong>Page connector power signal</strong>: use on any 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-e064106087ce86938a82bf40f7763ce20dfe8fe0%2Fpage_connector_3.png?alt=media" alt="" data-size="line"></td><td><strong>Page connector control input</strong>: although not a constraint to the software, this is preferably used on any control signal to indicate that the value is <strong>entering</strong> the wire</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-fcbb5be97d997a816f2b94aa6c703e5bb8cd19c2%2Fpage_connector_4.png?alt=media" alt="" data-size="line"></td><td><strong>Page connector control output</strong>: although not a constraint to the software, this is preferably used on any control signal to indicate that the value is <strong>leaving</strong> the wire</td></tr></tbody></table>

When attached to a signal line, a page connector propagates the signal name across all pages. Any signal with the same name on another page that also has a page connector becomes logically connected. You can place a page connector anywhere along a signal line, although placing it near the page edge is often convenient.

The page connector itself can be named, but its name must always match the attached signal. Renaming the page connector updates the attached signal name, and renaming the signal updates any attached page connectors.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1eee99922edfeb6ff7fe2c471d7f62c2ddf562cd%2Fimage%20(487).png?alt=media" alt=""><figcaption><p>Pages have signals named P1 with power page connectors attached</p></figcaption></figure>

Note that both page connectors are notated with the page number and grid reference.

You can place one or more page connectors on the same page. Two page connectors with the same name can also be placed on the same page to provide additional visual referencing for virtually connected signals.

## 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/page-connectors.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.
