> 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/native-library-components/probes.md).

# Probes

## Introduction

ePHASORSIM includes probes that can be added to a network via the Excel configuration file to calculate electrical characteristics between selected locations in the network and expose the results through block I/O pins.

Currently, the only supported probe type is the **Multiport Thevenin Equivalent Impedance** probe (`ZTH_MP`), which computes the Thevenin resistance and reactance between:

* A bus and ground.
* Two buses in the network.

The calculated impedance is reported in the same units as the network model:

* **Positive-sequence transmission systems** typically produce results in **per unit (pu)**.
* **Multiphase distribution systems** typically produce results in **ohms (Ω)**.

## Multiport Thevenin Equivalent Impedance

To calculate Thevenin impedance, add a row of type `ZTH_MP` in the **Probes** worksheet.

| Parameter | Description                                                   |
| --------- | ------------------------------------------------------------- |
| **Type**  | Probe type. Use `ZTH_MP` for Thevenin impedance calculations. |
| **ID**    | Unique probe identifier.                                      |
| **Bus**   | List of bus identifiers involved in the calculation.          |

The probe calculates impedance between any pair of buses listed in the Bus column.


---

# 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/native-library-components/probes.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.
