> 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/ssn-distributed-parameter-line-with-fault.md).

# ARTEMiS 3ph DPL With Variable Internal Fault Distance

## Description

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

The **SSN Distributed Parameters Line with Fault** block, located in the **ARTEMiS/SSN/Lines** library, implements a Bergeron travelling-wave line with losses (CP-line in EMTP-RV) with a fault placed at a user-defined distance from the ABC terminal. The model uses two distributed-parameter line (DPL) sections in series with an internal midline fault. The fault type and distance can be changed during on-line simulation without recompiling the model.

The model uses SSN UCB to dynamically modify the surge impedance according to the fault distance, ensuring an exact distribution of losses on both sides of the fault. Unlike the previous ARTEMiS Distributed Parameters Line with Variable Internal Fault Distance (ADPLF), which fixed losses 50/50 irrespective of fault location, this block reattributes losses dynamically without approximation.

{% 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-24bcede609d9d6cc3154ec3c77befdea77634c2a%2Fimage.png?alt=media" alt="" width="468"><figcaption></figcaption></figure>

<table><thead><tr><th width="251.60003662109375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Number of phases N</strong></td><td>Currently, only 3-phase lines are supported.</td></tr><tr><td><strong>Frequency used for RLC specifications</strong></td><td>Specifies the frequency used to compute the resistance R, inductance L, and capacitance C matrices of the line model.</td></tr><tr><td><strong>Resistance per unit length</strong></td><td>The resistance R per unit length, as an N-by-N matrix in ohms/km. For a symmetrical line, you can either specify the N-by-N matrix or the sequence parameters. For a two-phase or three-phase continuously transposed line, you can enter the positive and zero-sequence resistances [R1 R0]. For a symmetrical six-phase line you can set the sequence parameters plus the zero-sequence mutual resistance [R1 R0 R0m]. For asymmetrical lines, you must specify the complete N-by-N resistance matrix.</td></tr><tr><td><strong>Inductance per unit length</strong></td><td>The inductance L per unit length, as an N-by-N matrix in henries/km (H/km). For a symmetrical line, you can either specify the N-by-N matrix or the sequence parameters. For a two-phase or three-phase continuously transposed line, you can enter the positive and zero-sequence inductances [L1 L0]. For a symmetrical six-phase line, you can enter the sequence parameters plus the zero-sequence mutual inductance [L1 L0 L0m]. For asymmetrical lines, you must specify the complete N-by-N inductance matrix.</td></tr><tr><td><strong>Capacitance per unit length</strong></td><td>The capacitance C per unit length, as an N-by-N matrix in farads/km (F/km). For a symmetrical line, you can either specify the N-by-N matrix or the sequence parameters. For a two-phase or three-phase continuously transposed line, you can enter the positive and zero-sequence capacitances [C1 C0]. For a symmetrical six-phase line you can enter the sequence parameters plus the zero-sequence mutual capacitance [C1 C0 C0m]. For asymmetrical lines, you must specify the complete N-by-N capacitance matrix.</td></tr><tr><td><strong>Line length</strong></td><td>The line length, in km. This length is the total length of the line, not the individual length of the 2 line sections used by the model.</td></tr></tbody></table>

## Conserving ports

<table><thead><tr><th width="251.60003662109375">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>A B C</strong></td><td>Electric ports<br>Each side of the line is electrically connected with ABC and abc ports on each side.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="251.60003662109375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Fault distance ratio</strong></td><td>The distance of the fault from the ABC terminal in PU.</td></tr><tr><td><strong>Fault</strong></td><td>The fault is activated when this input equals 1.</td></tr><tr><td><strong>Fault params</strong></td><td>Fault type selection (ABCG, AB, etc.).<br>Normally connected to an <em>OpElectricFaultSelector</em> block for easy configuration.</td></tr></tbody></table>

## Outputs

This block has no outputs.


---

# 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/ssn-distributed-parameter-line-with-fault.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.
