> 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/pe-add-on-opal-rt/model-in-schematic-editor/design-the-ehs-circuit.md).

# Design the eHS Circuit

Circuits are created by assembling blocks from the library into the work area, connecting them together, and configuring their parameters. This page describes the tools and workflows used to build, modify, and organize eHS circuit models before configuring I/O mappings and integrating the circuit with a real-time simulation environment.

## Add and connect blocks

Blocks are added to the circuit using the **Library Browser**.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FwmFOJXyUShTjuGJS7Rlf%2FaddingComponent.gif?alt=media&amp;token=5dc9fc09-8889-4d16-8f4a-ac9f68a5613a" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

### Browse or search blocks

1. Open the **Library Browser**
2. Navigate through component categories (block families), or
3. Use the **search bar** to quickly find a component by name
   {% endstep %}

{% step %}

### Place blocks in the work area

Drag and drop blocks from the **Library Browser** into the **Work Area.** Once placed, blocks can be:

* Repositioned for clarity
* Rotated, aligned, or flipped
* Grouped within subsystems if needed
* Cut, copied, duplicated, deleted, etc
  {% endstep %}

{% step %}

### Connect blocks

Blocks are connected through their **connection points (nodes)**. Click and drag between nodes to create connections. Ensure all required electrical paths are defined, and verify polarity and direction when applicable.

* **Block to block**: Hover over a port until the cursor changes, then click and drag to connect
* **Signal line to port or signal line**: Hold **Ctrl**, then click and drag from the signal line to create a connection

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FRJwyad8bwKGx3lw7uOQc%2FSIGPOR.gif?alt=media&amp;token=5a677aaf-2fcc-4146-b0ae-29870df84381" alt="" width="225"><figcaption></figcaption></figure>

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FGe69mpfTS2LnAswSATCe%2FTARTAR2.gif?alt=media&amp;token=17cd6d36-e6af-4632-81c7-a5e907ef502f" alt="" width="225"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Define block parameters

Configure block parameters using the **Parameters Sidebar**.

1. Select a block, signal, or port to display its parameters. The sidebar is contextual, so available parameters depend on the selected object.
2. Edit a parameter by entering a value and pressing **Enter**. You can repeat this for any number of parameters. When selecting another element, the sidebar updates automatically. If a value does not meet validation rules, it is reverted to the previous valid value.
3. See the [Library Blocks Reference](https://www.opal-rt.com/docs/pe-add-on-opal-rt/model-in-schematic-editor/library-blocks-reference.md) for details about each block’s parameters.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FZrTlVAZxFqWyYBurxzQa%2FchangingParamOfComponent.gif?alt=media&amp;token=2bf45abf-c927-4df4-a4e2-e1e4c8afbcdd" alt=""><figcaption></figcaption></figure>

For certain parameters, you can display their value on the canvas using **View on Canvas** from the **Deep Panel**. Open the **Deep Panel** by clicking the arrow next to the parameter input.
{% endstep %}

{% step %}

### Save the eHS circuit model

Go to **File** and select **Save**.
{% endstep %}
{% endstepper %}

## Adjust the work area

The **Zoom Slider**, located at the bottom‑right of the work area, lets you adjust the zoom level from **5% to 800%**.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2F5hcIold2HWkThtWLXWZE%2Fimage.png?alt=media&amp;token=08cb1ef5-8600-47ac-a747-d6545d5f6b5d" alt=""><figcaption></figcaption></figure>

Click the **grid icon** to show grid lines and help align blocks. The grid is composed of large 8×8 squares subdivided into smaller cells. Blocks snap subtly to the grid when moved, helping maintain alignment even when the grid is hidden.

Alternatively, use the **View** menu to zoom (**Zoom In**, **Zoom Out**, **Fit to Screen**, **Normal Zoom**), toggle the grid, or change the theme.


---

# 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/pe-add-on-opal-rt/model-in-schematic-editor/design-the-ehs-circuit.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.
