> 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/simulink-blocks-reference/artemis-library/artemis-distributed-parameters-line.md).

# Distributed Parameters Line

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-3dea2ec3f5d415908e8930563744771522ba61a5%2FArtemis_distributed_param_line_block.png?alt=media" alt=""><figcaption></figcaption></figure>

The **ARTEMiS Distributed Parameters Line** block, located in the **ARTEMiS** library, implements an N-phase distributed-parameter transmission line with lumped losses optimized for discrete real-time simulation. The model is based on Bergeron’s travelling-wave method used in EMTP (Dommel, 1969). This block is similar to the SimPowerSystems (SPS) Distributed Parameter Line but is optimized for real-time execution, supports network decoupling, and enables distribution across multiple CPUs in RT-LAB. Refer to the SPS Distributed Parameter Line block documentation for additional details on the mathematical model.

**This block decouples the electrical network into smaller subnetwork**s, reducing state-space matrix size and the number of cached topologies for real-time simulation.

* Place the ARTEMiS Distributed Parameters Line at the top level of the RT-LAB compatible Simulink model.
* Do not connect ARTEMiS lines directly to each other at the top level. Route each connection into the corresponding subsystems first, then connect the line ports inside the subsystems.
* Connect each line port only to SimPowerSystems components located inside top-level RT-LAB subsystems (names starting with “SS” or “SM”).

RT-LAB’s distributed architecture allows complex models to run across a cluster of PCs using low-latency communication protocols—such as shared memory, FireWire, SignalWire, or InfiniBand—suitable for real-time performance.

Electrical circuits, however, cannot be split across multiple PCs without affecting their dynamic behavior, as inter-node communication delays degrade the simulation.

**ARTEMiS Distributed Parameter Lines** and **Stublines** address this limitation by using their intrinsic propagation delay to partition circuits without altering system dynamics. SPS and ARTEMiS also use physically based lines and connectors to model circuits accurately.

{% hint style="danger" %}
This block requires a valid RT-LAB license on the simulator with the feature ARTEMiS enabled. Refer to [ARTEMiS Requirements](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/power-systems-with-artemis/artemis-requirements.md) for details.
{% endhint %}

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-433250c51322a54e06b77cf0c308998ef1a707f2%2Fartemis-distributed-line-mask.png?alt=media" alt="" width="413"><figcaption></figcaption></figure>

<table data-search="false"><thead><tr><th width="182.79998779296875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Simulation mode</strong></td><td><p>Selects the mathematical model used by ARTEMiS and SPS:</p><ul><li><strong>SimPowerSystems</strong>: Uses the SPS model (not optimized for real-time).</li><li><strong>ARTEMiS model</strong>: Uses the ARTEMiS model optimized for fast real-time simulation and network decoupling.</li></ul></td></tr><tr><td><strong>Number of phases N</strong></td><td>Sets the number of phases, N. The block updates its inputs and outputs when you apply the parameters or close the dialog.</td></tr><tr><td><strong>Frequency used for RLC specifications</strong></td><td>Frequency used to compute the R, L, and C matrices of the line model.</td></tr><tr><td><strong>Resistance per unit length</strong></td><td>R per unit length as an N-by-N matrix in ohms/km. For a symmetrical line, specify either the N-by-N matrix or sequence parameters. For a two- or three-phase continuously transposed line, enter [R1 R0]. For a symmetrical six-phase line, enter [R1 R0 R0m]. For asymmetrical lines, specify the complete N-by-N matrix.</td></tr><tr><td><strong>Inductance per unit length</strong></td><td>L per unit length as an N-by-N matrix in H/km. For a symmetrical line, specify either the N-by-N matrix or sequence parameters. For a two- or three-phase continuously transposed line, enter [L1 L0]. For a symmetrical six-phase line, enter [L1 L0 L0m]. For asymmetrical lines, specify the complete N-by-N matrix.</td></tr><tr><td><strong>Capacitance per unit length</strong></td><td>C per unit length as an N-by-N matrix in F/km. For a symmetrical line, specify either the N-by-N matrix or sequence parameters. For a two- or three-phase continuously transposed line, enter [C1 C0]. For a symmetrical six-phase line, enter [C1 C0 C0m]. For asymmetrical lines, specify the complete N-by-N matrix.</td></tr><tr><td><strong>Line length</strong></td><td>Line length in km.</td></tr><tr><td><strong>Measurements</strong></td><td>Line current and voltage measurements are not available.</td></tr></tbody></table>

## Conserving ports

| Port                                | Description                                                                          |
| ----------------------------------- | ------------------------------------------------------------------------------------ |
| **N-phase voltage-current signals** | Electrical signals representing N-phase voltages and currents at the line terminals. |

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.

## Characteristics and limitations

| Characteristic       | Value                                                                                                                                                                              |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Initialization       | The block does not initialize in steady state; transients may occur at the start of the simulation.                                                                                |
| Measurements option  | Using the ARTEMiS Distributed Parameters Line disables the **Measurements** option of the regular SPS Distributed Parameter Line. Use standard voltage measurement blocks instead. |
| Direct feedthrough   | No                                                                                                                                                                                 |
| Discrete sample time | Yes; defined in the ARTEMiS Guide block.                                                                                                                                           |
| XHP support          | Yes                                                                                                                                                                                |
| Work offline         | Yes                                                                                                                                                                                |


---

# 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/simulink-blocks-reference/artemis-library/artemis-distributed-parameters-line.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.
