> 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/examples/transmission/hvac-735kv-38bus.md).

# HVAC 735kV 38Bus

## Description

The **HVAC 735 kV 38 Bus** example, located in **File > Open an Example File > Transmission**, simulates a 60 Hz transmission network with 38 buses, 9 transformers, and 7 generators at voltage levels of 13.8 kV, 25 kV, and 735 kV.

The main objective is to demonstrate how the system responds when a 250 MW load is switched on and off, with emphasis on generator behavior across the network.

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

## Requirements

The simulation time step is 50 µs.

## Detailed explanation

The model represents a transmission system where the main generation is located in the north and the primary loads are in the south. A breaker is configured to connect a 250 MW load to the system and later disconnect it to observe the transient response.

Event sequence and timing:

* Breaker closes at 0.2 s to connect the 250 MW load
* Breaker opens at 2.2 s to disconnect the load

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

## Simulation and results

Run the simulation and visualize the results using the ScopeView template *HVAC\_735kV\_38Bus.svt.* The results include active power, terminal voltage, and angular speed of four generators, as well as breaker currents.

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

The system starts from the steady state after load flow and initialization. When the breaker closes at 0.2 s, the southern generators Ge7 and Ge6, located near the switched load, exhibit more pronounced dynamics than the northern generators. This highlights the system response to the added load. The load is disconnected at 2.2 s.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-366e3514cb04b60e18a135bdfb4cb7e8c513d075%2Fimage%20(1014).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/examples/transmission/hvac-735kv-38bus.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.
