> 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/library-blocks-reference/network-sources/controlled-i-source-3-ph.md).

# Controlled I Source, 3-ph

## Description

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

The **Controlled I Source, 3-ph** block, located in the **Network Sources** library, represents a three-phase AC current source with a configurable RLC impedance. It reproduces the signal received on its control input and injects that current into the network. The source injects current between two buses and is not referenced to ground. The impedance is connected in parallel and can be implemented using R, L, and C elements arranged in series or in parallel.

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

## Mask parameters

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

| Parameter               | Description                                            |
| ----------------------- | ------------------------------------------------------ |
| **RLC connection type** | Series (series R, L, C) or parallel (parallel R, L, C) |
| **R**                   | Resistance value (ohms)                                |
| **L**                   | Inductance value (H)                                   |
| **C**                   | Capacitance value (F)                                  |

## Conserving ports

| Port               | Description                                                                                    |
| ------------------ | ---------------------------------------------------------------------------------------------- |
| **Net\_1, Net\_2** | The current source injects a current from one bus (port) to another (port), without grounding. |

## Inputs

| Input       | Description                          |
| ----------- | ------------------------------------ |
| **I input** | The current source amplitude signal. |

## Outputs

This block has no outputs.

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.

Additional signals are also available and are listed below with their descriptions.

| Signal              | Description                |
| ------------------- | -------------------------- |
| **I(a,b,c)\_label** | Current source signal (A). |


---

# 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/library-blocks-reference/network-sources/controlled-i-source-3-ph.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.
