> 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/edit-a-model-schematic/device-and-signals-naming-options.md).

# Device & Signals Naming Options

## **Device naming** <a href="#device-naming-options" id="device-naming-options"></a>

On the **Options** ribbon, click **Design Naming Options** to open the **Design Naming Options** dialog box.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7aea878c7f87ea23fc55414106a8bc47e835b573%2Fdevice-auto-assign-window.png?alt=media" alt="" width="388"><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Make auto-assigned names visible</strong></td><td>If this box is checked, the auto-assigned name is displayed on the schematic next to the symbol. If this box is not checked, the name is stored with the device, but not displayed on the schematic.</td></tr><tr><td><strong>Default name prefix</strong></td><td>The text in this box is the default prefix used to generate a device name if no prefix is provided in the device attributes.</td></tr></tbody></table>

An auto-generated device name consists of two parts, the fixed prefix, and the numeric suffix.

**The prefix portion is derived from one of two sources:**

* The device's Name.Prefix attribute field, or if that is empty,
* The value set using the **Device Naming Options** menu command shown above.

The numeric suffix is assigned sequentially for each different prefix found in the design. The names R1, R2, R3, etc. are assigned to devices with the value R in their prefix field, and the names Tr1, Tr2, Tr3, etc. for devices having prefix Tr.

The default device prefix field is Name.Prefix. This can be changed by entering the name of any other field in the design's PrefixField field (Design attributes, use the right-click menu on the design). As an advanced option, you can change the PrefixField field and use a different device prefix field when changing the design type.

### **Reassign names** <a href="#reassign-names" id="reassign-names"></a>

The **Reassign Names** command is available on the **Options** ribbon.

The **Reassign Device Names** command assigns a new name to all devices in the current circuit that are unnamed or have a default name. It is intended as a quick means of tidying up automatically-assigned names when a circuit is created or edited.

* Only the **current circuit level** is affected. Circuits located higher or lower in the hierarchy remain unchanged.
* Only the **Name** field is modified, regardless of the selected hierarchy mode.
* Names are assigned according to the order of objects in the reference grid, proceeding **top to bottom within each column**, then **left to right across the page**, and continuing through any subsequent pages.
* Names are generated using the device's configured **prefix** field.

### **Set the name prefix for a device** <a href="#setting-the-name-prefix-for-a-device" id="setting-the-name-prefix-for-a-device"></a>

The **name prefix** is defined in the device's [**Name.Prefix attribute**](https://github.com/Opal-RT-Technologies/product-docs-hypersim/tree/release-2026.4/model-and-simulation/edit-a-model-schematic/manage-attributes/README.md). This attribute can be configured either after the device has been placed in the design or directly in the device symbol stored in the library.

* If **Name.Prefix** is modified after the device has been placed in the design, the device name is automatically updated to reflect the new prefix.
* If **Name.Prefix** is defined in the library symbol, the device is assigned the desired prefix automatically when it is dragged into the design.

Defining the prefix in the library is recommended when a consistent naming convention is required across multiple instances of the same device type.

### Device token values

Each device created in an HYPERSIM circuit is assigned a unique integer identifier called a **token** (see **Properties > Token Number** from the device's shortcut menu). The token remains associated with the device for its entire lifetime and is never reused, allowing the device to be uniquely identified even if its name changes or duplicates exist.

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

#### **Token usage**

* Displayed in the **Device\_Info** box.
* Can be included in **netlists** when a unique identifier is required.

#### **Token characteristics**

* Tokens are unique only within a given circuit level and are assigned independently in hierarchical designs.
* Each schematic symbol, including pseudo-devices, has its own token.
* Multiple schematic symbols may be combined into a single package in the netlist, so there is not always a one-to-one correspondence between tokens and physical packages.

## **Signal naming** <a href="#signal-auto-naming-options" id="signal-auto-naming-options"></a>

HYPERSIM includes an **automatic signal naming** feature that helps ensure each signal object in a design is assigned a distinct name. Auto-naming is enabled by default when a new design is created, unless it has been explicitly disabled in the selected project template.

In addition, whenever an editing operation splits an existing signal into multiple segments, or copies part of a signal without a visible name label, HYPERSIM automatically assigns a new name to the resulting signal. This behavior helps maintain clear signal identification throughout the design.

### **Signal auto-naming options** <a href="#signal-auto-naming-options" id="signal-auto-naming-options"></a>

On the **Options** ribbon, click **Signal Naming Options** to open the **Signal Auto-Naming Options** dialog box.

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

<table><thead><tr><th width="199.77783203125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Make auto-assigned names visible</strong></td><td>If selected, the default name is displayed on the signal.</td></tr><tr><td><strong>Default signal name prefix</strong></td><td>Allows users to specify the characters to be used as a basis for auto-generated names. Changing this value does not affect existing names.</td></tr></tbody></table>

The **auto-generated signal name** consists of two parts: a fixed **prefix** and a **numeric suffix**.

The prefix is derived from the **Signal Name Prefix** setting. The numeric suffix is generated from the signal's **token value**, which is unique within a given circuit level. As a result, auto-generated names are generally distinct within that level.

Because token values are assigned incrementally and unused values are not reused, signal numbers may not be sequential in designs that have been modified over time.

{% hint style="info" %}
HYPERSIM generates auto-assigned names using a predefined prefix combined with the signal's token number. While this naming convention typically produces unique names, the software does not explicitly verify name uniqueness. Therefore, if a user manually assigns a name that matches the auto-generated format, a naming conflict may occur.
{% endhint %}


---

# 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/edit-a-model-schematic/device-and-signals-naming-options.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.
