> 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/cmde-add-on/model-and-simulation/configure-devices-within-a-ring/ring-configuration-page.md).

# Ring Configuration Page

## Overview

A ring consists of a group of emulated cell monitoring devices arranged in a daisy-chain configuration. Each device is connected to its neighbor through a bidirectional interface, with the first and last devices mapped to Digital I/O channel groups Port A and Port B, respectively. The ring is emulated on the FPGA board specified in the **Target** indicator.

When a device is disabled, the connection passes directly onto the next enabled one.&#x20;

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FEaR1EzX3JAU9rUpRLwIN%2Fimage.png?alt=media&amp;token=6bfe34f9-e218-4a53-a905-6f834c0455d2" alt=""><figcaption><p>A 6-device ring with all devices enabled (left), and the same ring with Device 2, Device 4, and Device 5 disabled (right).</p></figcaption></figure>

Consider the following recommendations and limitations when selecting which **devices to enable** in the ring:

* The maximum quantity of enabled devices is dependent upon the limitations set by the deployment [**License**](https://www.opal-rt.com/docs/cmde-add-on/overview/hardware-requirements/license.md).
* For each enabled device, additional CPU resources will be required to execute the simulation.

## Parameters

In the **System Explorer** window configuration tree, expand **Targets >> Controller >> Custom Devices >> CMDE Add-On** and select a **Ring** section to display this page.  Use this page to enable or disable individual cell monitoring devices within a ring.

This page includes the following components, configurable at edit-time only:

<table><thead><tr><th width="199.77777099609375">Parameters</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Specifies the name of the ring.</td></tr><tr><td><strong>Description</strong></td><td>Specifies a description for the ring.</td></tr><tr><td><strong>Device Type</strong></td><td>Specifies the type of cell monitoring device making up the ring.</td></tr><tr><td><strong>Target</strong></td><td>Specifies the name of the FPGA target on which the ring will be simulated once the project is deployed. This must match the name of the FPGA target as displayed in NI MAX.</td></tr><tr><td><strong>Enable All</strong></td><td>Enables all cell monitoring devices in the ring.</td></tr><tr><td><strong>Disable All</strong></td><td>Disables all cell monitoring devices in the ring.</td></tr><tr><td><strong>Device</strong></td><td>This table allows each cell monitoring device within the ring to be enabled or disabled. A <strong>Device section</strong> is added to the System Definition tree for each enabled device. </td></tr><tr><td><strong>Include Simulations Models</strong></td><td><p>This checkbox enables simulation models to be automatically added when devices are activated.<br>A corresponding model is created in the <strong>Models</strong> section of the System Definition tree for each enabled device.<br>If you disable devices, you must <strong>manually</strong> remove any associated models from the Models section.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>This functionality may not be available for all hardware configurations.</strong> <br>Please refer to the device-specific pages in this document for information about devices that include models.</p></div></td></tr><tr><td><strong>Connect To Simulation Models</strong></td><td><p>Makes the necessary connections between the Cell Monitoring Device Emulation Add-On and the models available on the System Definition tree.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>This functionality may not be available for all hardware configurations</strong>. <br>Please refer to the device-specific pages in this document for information about devices that include models.</p></div></td></tr></tbody></table>

## Ring Section Channels - SPI Mode <a href="#ring-section-channels" id="ring-section-channels"></a>

{% hint style="info" %}
**This channel may not be available for all device types**.&#x20;

Please refer to the device-specific pages in this document for information about supported SPI Modes.
{% endhint %}

<table><thead><tr><th width="150">Channel Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>SPI Mode</strong><br><strong>Input</strong></td><td><p>Specifies the SPI Mode for all devices in the ring. This channel accepts numeric integers <strong>0</strong> through <strong>3</strong>, inclusive, as defined below:</p><ul><li><strong>0</strong> - SPI Mode 0, where CPOL=0 and CPHA=0</li><li><strong>1</strong> - SPI Mode 1, where CPOL=0 and CPHA=1</li><li><strong>2</strong> - SPI Mode 2, where CPOL=1 and CPHA=0</li><li><strong>3</strong> - SPI Mode 3, where CPOL=1 and CPHA=1</li></ul><p>Please refer to the de facto SPI standard for detailed information about SPI mode numbers.<br>Default value:0</p></td></tr></tbody></table>

The value of an input channel can be modified dynamically at execution time.


---

# 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/cmde-add-on/model-and-simulation/configure-devices-within-a-ring/ring-configuration-page.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.
