> 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-ssn-nodal-interface.md).

# ARTEMiS SSN Nodal Interface

## Description

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

The **ARTEMiS-SSN Nodal Interface Blocks (NIB)**, located in the **ARTEMiS/SSN/Nodal Interface Blocks library**, define nodes and group boundaries for the ARTEMiS-SSN solver. The SSN (State-Space Nodal) solver uses a nodal method to couple, without delays, groups represented by discretized SPS state-space equations or any model that has a discrete resistive companion model compatible with the EMTP nodal method.

In a Simscape Electrical Specialized Power Systems (SPS) schematic, each block instance defines a node by itself and the NIB defines the perimeter of the SSN groups.

Use these options to connect different types of SSN groups:

* Inductive-type SSN groups require a V-type interface.
* Capacitive-type SSN groups require an I-type interface.
* External SSN models, such as the FD-line model, require an X-type interface.

{% 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-9ae22b2177f7948bd6ee12390b15f4df31041eb8%2FArtemis_SSN_nodal_interface_mask.png?alt=media" alt="" width="318"><figcaption></figcaption></figure>

<table><thead><tr><th width="220.4000244140625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Number of phases</strong></td><td>Sets the number of phases for the NIB.</td></tr><tr><td><strong>Number of Ports</strong></td><td>Sets the number of ports on the block. All phases of a single port connect to one SSN group.</td></tr><tr><td><strong>Port </strong><em><strong>x</strong></em><strong> type</strong></td><td><p>The <strong>Number of Ports</strong> parameter sets the number of <strong>Port x type</strong> entries available (x = 1 to 16). Each <strong>Port x type</strong> can be configured with one of the following options:</p><ul><li><strong>V-type (Left):</strong> Voltage-type interface to the state-space groups, with ports on the left side.</li><li><strong>V-type (Right):</strong> Voltage-type interface to the state-space groups, with ports on the right side.</li><li><strong>I-type (Left):</strong> Current-type interface to the state-space groups, with ports on the left side.</li><li><strong>I-type (Right):</strong> Current-type interface to the state-space groups, with ports on the right side.</li><li><strong>X-type (Left):</strong> External SSN group interface, with ports on the left side.</li><li><strong>X-type (Right):</strong> External SSN group interface, with ports on the right side.</li></ul></td></tr></tbody></table>

## Conserving ports

| Port               | Description         |
| ------------------ | ------------------- |
| PM-type connectors | PM-type connectors. |

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.

## Characteristics and limitations

| Characteristic       | Value |
| -------------------- | ----- |
| Direct Feedthrough   | N/A   |
| Discrete Sample Time | Yes   |
| RT-LAB 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-ssn-nodal-interface.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.
