> 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/conventional-generation/synchronous-machine-xd-td.md).

# Synchronous Machine Xd Td

## Description

The **Synchronous Machine Xd Td** example, located in **File > Open an Example File > Conventional Generation.**

The objective is to estimate the synchronous machine parameters Xd, Xd', Xd'', Td', Td'', Tdo' and Tdo'' by applying and clearing a three-phase-to-ground fault at the machine terminals and analyzing the resulting transients.

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

## Requirements

This example model does not require any additional hardware or licenses.

## Detailed explanation

The Synchronous Machine Xd Td model is developed in HYPERSIM. The basic network is designed to extract key synchronous machine characteristics.

Test procedure:

* Apply a sudden three-phase-to-ground fault at the machine terminals, then remove the fault.
* Analyze the current transient during the fault to evaluate Xd, Xd', Xd'', Td', and Td''.
* Analyze the voltage transient during recovery to evaluate Tdo' and Tdo''.

System bus base quantities:

* Phase = 100 MVA
* Vbase = 100 kV
* Ibase = Phase/Vbase/sqrt(3) = 577.3 A

In steady faulty condition: 685 Apeak --> 484 Arms --> 0.84 pu --> Xd = 1.2\
Peak fault current: 7500/2 Apeak

## Simulation and results

### Fault currents and bus voltages

The simulation captures three-phase fault currents and bus voltages during the fault application and clearing.

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

### Machine currents, terminal voltage, and speed

The simulation records machine phase currents, terminal voltage, and rotor speed for parameter estimation as described above.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f29a156da2c48d704e5c8bb1b046f367558dd216%2Fimage%20(601).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/conventional-generation/synchronous-machine-xd-td.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.
