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

# RadioLink

## Description

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

The **RadioLink Emitter** and **RadioLink Receiver** blocks, located in the **Signal Routing** library, are a pair of blocks that exchange signals using a shared link name. They operate similarly to page connectors, but RadioLink signals can cross subsystem boundaries. Blocks connect by a link name rather than by block names. For each link name, exactly one emitter is allowed, and that emitter can broadcast to multiple receivers that use the same link name.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-be745b655c8c59a5223c3eb1aeac707550d18b0b%2Fimage%20(1032).png?alt=media" alt="" width="458"><figcaption><p>Example: emitter RLE_1 and receiver RLR_1</p></figcaption></figure>

In this example, the emitter RLE\_1 broadcasts via the link name *myControlSignal*. The receiver RLR\_1 listens to *myControlSignal*. During the analysis process, the relationship between the 2 RadioLinks is found. The absolute path to the emitter is shown next to the receiver link name for traceability. Finally, Sine1.y is implicitly connected to Gain1.u. Therefore, the RadioLinks components are not present in the topology and do not affect simulation performances.

## Mask parameters

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

<table><thead><tr><th width="220.4000244140625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Link name</td><td>Identifier used to connect a single emitter to one or more receivers that share the same link name. Python API name: linkName.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="219.60003662109375">Input</th><th>Description</th></tr></thead><tbody><tr><td>in</td><td>Input signal (pu). Present only on the emitter.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="219.60003662109375">Output</th><th>Description</th></tr></thead><tbody><tr><td>out</td><td>Output signal (pu). Present only on the receiver.</td></tr></tbody></table>

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.


---

# 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/radiolink.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.
