> 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/model-and-simulation/prepare-the-simulation/set-simulation-parameters/target-manager.md).

# Target Manager

All target configuration is managed through the **Target Manager** configuration pane. From this interface, users can configure the target's HYPERSIM version, manage licenses, adjust advanced compilation and simulation settings, and modify a variety of other target-specific parameters.

The **Target Manager** can be accessed from the **HYPERSIM** ribbon.

There are two nodes available by default through the Target Manager interface:

* Targets
* Default Code Generation

## Target

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8b6ec50ae87cf3b5524252ab899ad54f97bd2f2a%2Ftarget-managet-overview.png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-search="false"><thead><tr><th width="200">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name / IP</strong></td><td>The IP address of the target</td></tr><tr><td><strong>Description</strong></td><td>The description of the target is written by the user when adding a new target in HYPERSIM Target Manager.</td></tr><tr><td><strong>Active</strong></td><td><p><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6e2b8a7c0681b7ae153eca2088efbad38399e1a1%2Ftarget-manager-active-green.png?alt=media" alt="" data-size="original"> HyCore and HyServer are running, the target can be used.</p><p>It detects the user and the mode. The following information can be seen in the tooltip:</p><ul><li>user=UserName;</li><li>mode=APPLICATION or SERVICE</li></ul><p><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5fcb5c8a42a421994e282639b168ebe05f0cbf90%2Ftarget-manager-active-orange.png?alt=media" alt="" data-size="line"> HyCore is running but HyServer is not reachable.<br><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-487b174ec21b2cf756bfcdd121460cd272bf804c%2Ftarget-manager-active-red.png?alt=media" alt="" data-size="line"> HyCore is not running. The target is unreachable.</p></td></tr><tr><td><strong>Running Version</strong></td><td><strong>Architecture:</strong> The target Operating System.<br><strong>Build:</strong> The current HYPERSIM version used by the target.<br><strong>Protocol:</strong> gRPC and System D. More informations</td></tr><tr><td><strong>License (days)</strong></td><td>It indicates how many days remain in the target license before it expires.</td></tr></tbody></table>

Each target listed has a hierarchical tree view menu that reveals all the items listed below:

{% columns %}
{% column width="33.33333333333333%" %}

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

{% column width="66.66666666666667%" %}

* **Versions** show both a current and historical log of versions installed on this machine
* **Simulation** shows both a current and historical log of versions installed on this machine
* **Advanced** features **Compilation** and **Task Mapping** settings
* **Network** shows network configuration settings that are used by ScopeView for local simulations
* **Diagnostic** provides a detailed report of the target's current state and is often requested by the support team to help diagnose issues
* **License** shows a current and historical log of licensing for this machine
  {% endcolumn %}
  {% endcolumns %}

### Target home page <a href="#target-home-page" id="target-home-page"></a>

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

To update the target description, click **General** and, if applicable, **FPGA** in this menu.

{% hint style="info" %}
FPGA information should not be requested when a simulation is currently running on target.
{% endhint %}

### Versions <a href="#versions" id="versions"></a>

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

<table><thead><tr><th width="200">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Local running version</strong></td><td>Host HYPERSIM version.</td></tr><tr><td><strong>Last Refresh</strong></td><td><p>Date of the last time the status of the target and its information was refreshed.</p><p><strong>Note:</strong> a warning appears if the target is not running the same version as the host as required.</p></td></tr><tr><td><strong>Install version</strong></td><td><p>Installs the <strong>current HYPERSIM host version</strong> onto the target, selects it, and restarts the target's services.</p><p>If this version is already installed on the target, the current installation is removed and reinstalled.</p></td></tr><tr><td><strong>Restart services</strong></td><td>Restart HYPERSIM services on the target (hycore and hyserver).</td></tr><tr><td><strong>Refresh list of installed versions</strong></td><td>Reloads all target HYPERSIM versions and updates the table.</td></tr><tr><td><strong>Status</strong></td><td>Provides detailed information on the target for debugging purposes.</td></tr></tbody></table>

Right-click a table entry to open a context menu with options to uninstall the selected version from the target or set it as the active server version on the target.

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

Starting with **HYPERSIM 2023.1**, communication with the target uses **gRPC** exclusively. As a result, HYPERSIM **2022.2 and earlier** running on the host PC cannot communicate with targets running **HyCore 2023.1 or later**, since the legacy **RMI** technology was removed for security and stability reasons. HYPERSIM **2022.1** and **2022.2** support both RMI and gRPC, making them suitable transition versions during upgrades.

To upgrade from **2021.x** to **2023.x**, first install **2022.x** on both the host and the target, then upgrade to **2023.x** or later. Similarly, to upgrade to **2024.x** or a newer release, first ensure that **2023.x** is installed on both systems.

To roll back a target from version **X** to an earlier release, use the same version **X** in the host's **Target Manager**. If a further rollback is required, use a **2022.x** host installation as an intermediate step.

For operations such as **restarting services** or **exporting a license to a target**, the host PC must be running the same HYPERSIM version as the target.

<details>

<summary><strong>Protocol versions and backward compatibility</strong></summary>

| Version | Protocol | Samba | RMI | gRPC | SystemD | Main change                                                                                                                                         |
| ------- | -------- | :---: | :-: | :--: | :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| 2021.2  | 1.0.0    |   ✅   |  ✅  |   ❌  |    ❌    | Initial introduction                                                                                                                                |
| 2021.3  | 1.0.0    |   ✅   |  ✅  |   ❌  |    ❌    |                                                                                                                                                     |
| 2022.1  | 2.0.6    |   ❌   |  ✅  |   ✅  |    ❌    | <p>HyServer: Start simulation with decimation parameters.<br>Samba is not used anymore for file transfers to target</p>                             |
| 2022.2  | 3.0.0    |   ❌   |  ✅  |   ✅  |    ❌    | Replaced all usage of the target from RMI to gRPC, except target manager                                                                            |
| 2023.1  | 4.0.0    |   ❌   |  ❌  |   ✅  |    ❌    | RMI removal                                                                                                                                         |
| 2023.2  | 5.0.0    |   ❌   |  ❌  |   ✅  |    ❌    | Internal changes during simulation setup on target                                                                                                  |
| 2023.3  | 5.1.0    |   ❌   |  ❌  |   ✅  |    ❌    | An additional method for switching target versions on certain target configurations                                                                 |
| 2024.1  | 6.0.0    |   ❌   |  ❌  |   ✅  |    ✅    | HyCore and HyServer services are now launched by systemd on OPAL-RTLinux                                                                            |
| 2024.3  | 6.0.1    |   ❌   |  ❌  |   ✅  |    ✅    | HyCore is now able to return the target Serial number to the target manager.                                                                        |
| 2025.1  | 6.1.1    |   ❌   |  ❌  |   ✅  |    ✅    | When setting up a driver during simulation startup on target, use the “Enable simulation Logging” option to determine the log level of each command |
| 2025.3  | 6.2.2    |   ❌   |  ❌  |   ✅  |    ✅    | Removed the need for admin permission for localhost target diagnostic                                                                               |
| 2025.4  | 6.2.3    |   ❌   |  ❌  |   ✅  |    ✅    | Fixed a remote FPGA detection error for the target manager target home page                                                                         |

</details>

### Advanced <a href="#advanced" id="advanced"></a>

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

The values configured here serve as defaults for new models but can be overridden in the model's **Simulation Settings**. Available default settings vary depending on the target operating system.

<table><thead><tr><th width="200">Task Mapping Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Communication overhead</strong></td><td>The portion of the simulation time step granted to communication between processors.</td></tr><tr><td><strong>I/O overhead</strong></td><td>The portion of the simulation time step granted to communication with I/O interfaces.</td></tr><tr><td><strong>Processor performance</strong></td><td><p>Value used by the task mapping algorithm to estimate the tasks based on the hardware specifications.</p><p>The higher the number, the lower the estimate for each task.</p></td></tr></tbody></table>

### Tools <a href="#tools" id="tools"></a>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d6cd5684ff6a867ed431a3cc10d5e6360ed3abe9%2Ftask-manager-tools.png?alt=media" alt=""><figcaption></figcaption></figure>

The **BlackBox Interface Tools** tab lets you manage the tools required to use the **Real-Time Container**.

<table><thead><tr><th width="200">Control</th><th width="60">Button</th><th>Description</th></tr></thead><tbody><tr><td><strong>Installed version</strong></td><td></td><td>Indicates whether the BlackBox Interface Tools are installed and displays their version when available.</td></tr><tr><td><strong>Uninstall</strong></td><td><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4ee99153a093d1215d0b918d6decbdba1950eb66%2Ftarget-manager-tools-uninstall.png?alt=media" alt="Uninstall" data-size="original"></td><td>The button beside the installed version removes the BlackBox Interface Tools from the target.</td></tr><tr><td><strong>Refresh</strong></td><td><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4eb98c60ca710dd4060532fe010e532f2cb5b4e1%2Ftarget-manager-tools-refresh.png?alt=media" alt="Refresh" data-size="original"></td><td>Updates the displayed installation status of the BlackBox Interface Tools.</td></tr><tr><td><strong>RPM file path</strong></td><td><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b22aba1476cc9a1aca82343eee67f829e42ffb5c%2Ftarget-manager-tools-rpm-file.png?alt=media" alt="Browse for RPM file" data-size="original"></td><td>Use the browse button to select the RPM package to install. The selected file's path appears in the text field.</td></tr><tr><td><strong>Install</strong></td><td><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1e09134942dee1b656f469408a1df4fa2d8c1797%2Ftarget-manager-tools-install.png?alt=media" alt="Install" data-size="original"></td><td>Installs the selected RPM package's BlackBox Interface Tools on the target.</td></tr></tbody></table>

### Network <a href="#network" id="network"></a>

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

This tab is used to configure the **communication interface** between **ScopeView** and the **target**.

When ScopeView is configured for continuous data acquisition (**Cont** enabled, as shown below), you may need to specify the correct network interface, particularly on systems with multiple network adapters. This ensures reliable communication between the host and the target.

{% hint style="info" %}
Note that target services will be restarted after applying changes.
{% endhint %}

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5c771c2e91b47cd047f240327f8ed78c81c873a1%2Ftarget-manager-scopeview.png?alt=media" alt=""><figcaption></figcaption></figure>

Identifying the IP where data packets are to be transferred is done through this pane.

<table><thead><tr><th width="200">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Automatic</strong></td><td><p>Uses the default network interface to determine the IP address.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>In this mode, <strong>Datalogger Live Acquisition</strong> and <strong>FPGAScope</strong> won't work.</p></div></td></tr><tr><td><strong>Fixed</strong></td><td>Selects the input IP address.</td></tr><tr><td><strong>Search in range</strong></td><td>Selects the first IP address which can communicate with ScopeView. Once communication is lost, IP is recalculated using that range.</td></tr><tr><td><strong>Network interface</strong></td><td>Use the selected network interface to automatically determine the IP.</td></tr></tbody></table>

### Diagnostic <a href="#diagnostic-inlineextension" id="diagnostic-inlineextension"></a>

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

When issues occur during HYPERSIM installation on a target or when starting a simulation, the cause may not be immediately apparent. In such cases, the **Support team** may request a diagnostic report to help identify the problem.

After running the diagnostic, save the generated report and send it to Support. The report concludes with a **pass/fail summary** that highlights potential issues and provides troubleshooting guidance. For additional details, refer to the corresponding sections earlier in the report, which describe the detected issue and suggest possible solutions.

This function performs the same operation as the **Diagnostic** command on the HYPERSIM ribbon.

{% hint style="danger" %}
The diagnostic **should not be executed** on a target where a simulation is running as it may impact the simulation state, performance or results.
{% endhint %}

### License <a href="#license" id="license"></a>

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

This pane is used to manage the target's licenses. For information on license installation and configuration, refer to the [Licensing Reference documentation](https://www.opal-rt.com/docs/hypersim/licensing-reference/workstation-license/install-a-license.md).

All communications and operations involving the target are recorded in the **Log** tab, providing a detailed history that can be used for monitoring and troubleshooting.

| Parameter                                       | Description                                                                                          |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Machine ID area**                             | Required when requesting a new license.                                                              |
| **Get target information and license file (1)** | Contacts target and auto-completes area 5.                                                           |
| **Save as ... (2)**                             | Exports machine ID to a `.txt` file.                                                                 |
| **Request a new license**                       | Opens the form to send a license request to our support team. *Requires an internet connection.*     |
| **License information**                         | Expiration date, license number, target number (serial number), license path                         |
| **License properties**                          | Lists all features of the license file.                                                              |
| **Select license file**                         | Browse for a new license file.                                                                       |
| **Install selected license**                    | Compares the selected license to the already installed license, if any, and allows for installation. |

## Default Code Generation

**Default Code Generation** holds settings related to code generation storage paths.

The unique code directory is enabled by default. The local target code directory (for localhost) is automatically set to the path below:

**Local code directory:** %{USER\_HOME}\HYPERSIM\code

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


---

# 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/model-and-simulation/prepare-the-simulation/set-simulation-parameters/target-manager.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.
