> 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-bundle.md).

# Radiolink bundle

## Description

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

The **Radiolink emitter, bundle** and **Radiolink receiver, bundle** blocks, located in the **Signal Routing** library, are a pair of blocks that provide bundle-based signal routing across subsystem boundaries. They work similarly to [Page Connectors](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/signal-routing/page-connectors.md) bundles, but radiolink signals can travel in and out of subsystems. Radiolinks connect via a *link name* rather than by pin name. For each link name, only one emitter is allowed; an emitter can broadcast to multiple receivers sharing the same link name.

Radiolink bundle blocks initially contain a single, empty bundle port. Pins within the bundle are created and synchronized automatically based on the resolved link name.

{% hint style="info" %}
The emitter exposes a bundle, not individual output pins. To access the *In* bundle of a block such as [AC1A](https://opal-rt.atlassian.net/wiki/spaces/Documentat/pages/1666482409/AC1A), connect the block’s *In* bundle to a radiolink bundle emitter and feed the signals through a radiolink bundle receiver.

For robust configuration, manually click Analyze before connecting pins inside radiolink bundles.
{% endhint %}

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

In this example, the emitter RLEB\_1 broadcasts via the link name *myBundleLink*. The receiver RLRB\_1 listens to *myBundleLink*. When setting the receiver link name, the emitter is found and pins are updated. The absolute path to the emitter is shown next to the receiver link name for tracability. Finally, The 3 pins of the I Measurement, 3-ph are then directly connected to the 3 pins of the summation component. Therefore, the radiolinks components are not present in the topology and do not affect simulation performances.

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

In this example, the emitter RLEB\_1 broadcasts via the link name *ac1a\_link*. The receiver RLRB\_1 listens to *ac1a\_link*. When setting the receiver link name, the emitter is found and pins are updated. The absolute path to the emitter is shown next to the receiver link name for tracability. We then feed the AC1A via the radiolink bundle receiver.

<details>

<summary>Example with API</summary>

These blocks' workflow is optimized for manual usage. HYPERSIM<sup>®</sup> will try to keep all related pins up to date during your model edition. Therefore, to allow full control of the configuration via the API, there is a parameter '*managedByAPI'* for the emitter, which disables HYPERSIM automated treatments. Please find below a simple example of how to use the radiolink bundles via the API.

{% code overflow="wrap" lineNumbers="true" %}

```
# import the Api as HyWorksApi
 
HyWorksApi.connectToHyWorks()
# Some APIs require a call to HyWorksApi.openModel(), but in this example, we assume an empty design is already open.
 
# Emission
source = HyWorksApi.addDevice('Network Sources.clf', 'AC V source', -1400, 0)
measurement = HyWorksApi.addDevice('Network Measurements.clf', 'I measurement, 3-ph', 0, 0)
resistance = HyWorksApi.addDevice('Network RLC.clf', 'R grounded', 2100, 350)
pow = HyWorksApi.addDevice('Network Tools.clf', 'Point-on-wave', 2800, 350)
emitter = HyWorksApi.addDevice('Signal Routing.clf', 'Radiolink emitter, bundle', 1400, 140)
 
# Reception
receiver = HyWorksApi.addDevice('Signal Routing.clf', 'Radiolink receiver, bundle', -1400, 1400)
max = HyWorksApi.addDevice('Control Math Operations.clf', 'Max, 3-input', 0, 1400)
 
# Connect power section
HyWorksApi.connectDevices(source, 'net_1', measurement, 'net_1', False)
HyWorksApi.connectDevices(measurement, 'net_2', resistance, 'net_1', False)
HyWorksApi.connectDevices(measurement, 'net_2', pow, 'net_1', False)
 
# Since we have to set component parameters, we need an analyze to let the engine know about the topology
HyWorksApi.analyze()
 
# Managed by API, this deactivates HYPERSIM auto connections on this radiolink. So we are in full control in the API
HyWorksApi.setComponentParameter(emitter, 'managedByAPI', 'true')
# Add the pins inside the bundle of the radiolink
HyWorksApi.addPinsToDevice(emitter, "W", "I", ['Bundle[rlb_currentA]', 'Bundle[rlb_currentB]', 'Bundle[rlb_currentC]'], False)
# Connect the radiolink to the measurement
HyWorksApi.connectBundleToBundle(measurement, ['a', 'b', 'c'], emitter, ['rlb_currentA', 'rlb_currentB', 'rlb_currentC'])
 
# Link both radiolinks via the linkname
HyWorksApi.setComponentParameter(emitter, 'linkName', 'myRadiolinkBundle')
HyWorksApi.setComponentParameter(receiver, 'linkName', 'myRadiolinkBundle')
# Note that we do not need to manage the receiver by api, because the pin list should be the same as the emitter
# with opposite directions. So we control the emitter, configure it, and let the receiver match the configuration
 
# Connect the receiver
HyWorksApi.connectPinToBundle(max, "u1", receiver, 'rlb_currentA')
HyWorksApi.connectPinToBundle(max, "u2", receiver, 'rlb_currentB')
HyWorksApi.connectPinToBundle(max, "u3", receiver, 'rlb_currentC')
 
HyWorksApi.analyze()
 
HyWorksApi.selectAllSensors(measurement)
HyWorksApi.selectAllSensors(max)
```

{% endcode %}

</details>

## Mask parameters

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

<table><thead><tr><th width="240.4000244140625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Link name</td><td>Identifier that connects one emitter to one or more receivers. Only one emitter is permitted per link name. In the Python API, this parameter is named linkName.</td></tr></tbody></table>

{% hint style="info" %}
When you set the receiver link name, the corresponding emitter is located and the bundle pins are updated automatically. The absolute path to the emitter is displayed next to the receiver link name for traceability.
{% endhint %}

## Inputs

<table><thead><tr><th width="240.39996337890625">Input</th><th>Description</th></tr></thead><tbody><tr><td>Bundle</td><td>Single bundle port. It is initially empty and is populated with pins when a valid link name is resolved. The direction of each pin is determined by the connected blocks.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="237.20001220703125">Output</th><th>Description</th></tr></thead><tbody><tr><td>Bundle</td><td>Single bundle port. It is initially empty and is populated with pins when a valid link name is resolved. The direction of each pin is determined by the connected blocks.</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-bundle.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.
