> 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-marti-type-fd-line.md).

# SSN Marti-type FD-line

## Description

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

The **SSN Marti-type FD-line** blocks, located in the **ARTEMiS/SSN/Lines** library, implement a Marti-type frequency-dependent transmission line model. This v2.0 implementation removes the need for X-type NIB at the terminals and requires the SSN solver.

The model accurately represents balanced and slightly unbalanced overhead lines using a modal transformation to compute frequency-dependent parameters.

{% hint style="info" %}
For cables, where the modal transformation matrix is strongly frequency dependent, this model can be inaccurate; the SSN-WideBand model is more suitable in that case.
{% endhint %}

The blocks are provided as two half-line models that exchange traveling wave data through Simulink signals. They can be used to decouple electric systems similarly to standard DPL models, but users must manually route the two half-models in the SS\_ subsystems when using RT-LAB.

{% 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-3d0fe246bf0ac9a23abe1e877dfc042677be904f%2FArtemis_SSN_marti_FDLine_mask.png?alt=media" alt="" width="344"><figcaption></figcaption></figure>

<table><thead><tr><th width="279.60003662109375">Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>EMTP-RV Marti-type FD-line fitting file (.pun)</strong></td><td>The FD-line fitting data file produced by EMTP-RV fitter. The file uses the .pun extension.</td></tr><tr><td><strong>Type of .pun file</strong></td><td>{Line or Cable}. EMTP-RV generates slightly different formats of .pun files for lines and cables. Using the Marti-type FD-line model for cables is not recommended.</td></tr><tr><td><strong>Time step (s)</strong></td><td>The model sample time in seconds.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="279.60003662109375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Traveling wave signal (Simulink input)</strong></td><td>Single Simulink signal that must be connected to the complementary half-line block. It can be routed across SS_ subsystems for RT-LAB model decoupling.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="280.4000244140625">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Traveling wave signal (Simulink output)</strong></td><td>Single Simulink signal that must be connected to the complementary half-line block. It can be routed across SS_ subsystems for RT-LAB model decoupling.</td></tr></tbody></table>

{% hint style="info" %}
The blocks also provide **Physical Modeling (PM) electric ports** corresponding to the electric phase connections in SPS.
{% endhint %}

## Characteristics and limitations

<table><thead><tr><th width="279.60003662109375">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td>Solver requirement</td><td>Requires the SSN solver.</td></tr><tr><td>Terminal interface</td><td>Does not require X-type NIB at the terminals.</td></tr><tr><td>Model structure</td><td>Implemented as two half-line blocks that exchange traveling wave data via Simulink signals.</td></tr><tr><td>Decoupling</td><td>Supports RT-LAB model decoupling when the two half-models are manually routed in separate SS_ subsystems.</td></tr><tr><td>Minimum delay for multi-core decoupling</td><td>The fastest mode transport delay must be at least 2*Ts, where Ts is the model sampling time.</td></tr><tr><td>Accuracy with overhead lines</td><td>Accurate for balanced and slightly unbalanced overhead lines.</td></tr><tr><td>Use with cables</td><td>Can be inaccurate for cables due to strong frequency dependence of the modal transformation matrix. The SSN-WideBand model is more accurate for cables.</td></tr><tr><td>Model symmetry</td><td>The two half-line models are identical and interchangeable.</td></tr></tbody></table>


---

# 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-marti-type-fd-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.
