> 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/manage-schematic-editor-files.md).

# Manage Schematic Editor Files

## Overview

The **Schematic Editor** is used to create, open, and modify eHS circuit models that will be executed on the FPGA using the eHS solver.

The `.ehs3` file is the main project file used by Schematic Editor. It serves as the single source of truth for an eHS model and stores all information required to recreate and configure the project.

A `.ehs3` file contains:

* The electrical circuit model
* Simulator setup and configuration information
* Firmware descriptions
* Hardware descriptions
* Model connections and mappings
* Other Schematic Editor project settings

Because all project information is centralized in a single file, the `.ehs3` file can be easily shared, version-controlled (for example with Git), and synchronized across users and environments. The `.ehs3` file must be accessible from the MATLAB path to enable synchronization with Simulink blocks.

## Typical Schematic Editor workflow

Creating an eHS circuit model typically involves the following steps:

1. **Configure the Firmware and Simulator Setup**\
   Select the target hardware, firmware, and simulator configuration.
2. **Define the Solver Settings**\
   Configure how the eHS solver will process and execute the circuit on the FPGA.
3. **Design the eHS circuit**\
   Build the electrical circuit by placing components, configuring parameters, and creating connections.
4. **Configure the eHS circuit interfaces**\
   Define how signals, parameters, and measurements interact with the real-time simulation environment and physical I/O resources.
5. **Save and load the circuit**\
   Save the circuit in Schematic Editor and load it from <code class="expression">space.vars.cpu\_model\_veristand</code>, review the generated **Build Report**, and run the simulation on the main software platform.

After the initial circuit model is created, the workflow becomes iterative: modify the circuit, save the changes, reload the circuit in <code class="expression">space.vars.cpu\_model\_veristand</code>, and validate the results.

## Create or open a circuit model

The Schematic Editor is typically launched from <code class="expression">space.vars.cpu\_model\_veristand</code>. At this stage, users can either create a new circuit model or open an existing one.

Once the Schematic Editor is open, circuit models can also be managed independently. Navigate to **File** in the Schematic Editor menu bar and select **New** to create a new circuit model or **Open...** to open an existing one.

## Save a circuit model

Navigate to **File** and select **Save** to save the current circuit model to its existing `.ehs3` file location, or **Save As** to save the current circuit model as a new `.ehs3` file, creating a copy that can be modified independently of the original model.

## Open the archived models folder

Navigate to **File** and select **Open Archived Models Folder** to open the folder containing archived circuit models. This folder can be used to store backups, previous revisions, or reference circuit models that are no longer actively used.

## View or edit model information

Navigate to **File** and select **Open Model Information Folder** to view or modify information associated with the current circuit model, including:

* **Name** — Display name of the circuit model.
* **Version** — User-defined version identifier for the model.
* **Notes** — Additional information, documentation, or revision notes.
* **File Path** — Location of the `.ehs3` file on disk.

Click **Apply** to save the changes.


---

# 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/manage-schematic-editor-files.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.
