> 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/overview/cell-monitoring-device-emulation-cmde-add-on-1.2.md).

# Cell Monitoring Device Emulation (CMDE) Add-On 1.2

This documentation applies only to Cell Monitoring Device Emulation (CMDE) Add-On for NI VeriStand 1.2 (build date: dec. 2025).

## Introduction <a href="#introduction" id="introduction"></a>

The **OPAL-RT Cell Monitoring Device Emulation (CMDE) Add-On** for **NI VeriStand** is a powerful FPGA-based simulation tool for Hardware-in-the-Loop (HIL) testing of modern **Battery Management Systems (BMS)** used in power electronics applications.&#x20;

This solution further enhances development efficiency by emulating battery cells and BMS chipset register behavior using **isoSPI™ technology**, while preserving the integrity of SPI daisy-chain communication. As a result, it provides a realistic and robust environment for rapid BMS testing and validation.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FB6BQnypNAS5KQeC0IJgU%2Fimage.png?alt=media&amp;token=fe4a63bf-1a56-4386-b9c5-4dd3d00b2415" alt=""><figcaption></figcaption></figure>

### CMDE Add-On Features and Benefits <a href="#cmde-add-on-features-and-benefits" id="cmde-add-on-features-and-benefits"></a>

* **FPGA-based Emulation:** Enables accurate emulation of commercial cell monitoring devices while providing a realistic digital bus interface to the device under test.
* **Expanded Test Coverage:** Includes fault simulation capabilities such as temperature faults, open wires, broken communication links, and CRC errors, all without compromising security.
* **Cost and Time Efficiency:** Reduces the need for numerous physical cell emulators by virtualizing commercial integrated circuits designed for cell monitoring, while preserving isoSPI™ communication links.
* **User-Friendly Interfaces**: Offers simple and intuitive user interfaces for connecting emulated cell monitoring devices to cell chemistry models built in various modeling environments such as MathWorks Simulink, NI LabVIEW, and more.
* **NI VeriStand Compatibility**: The CMDE Add-On integrates seamlessly into the [**NI VeriStand**](https://www.ni.com/en/shop/data-acquisition-and-control/application-software-for-data-acquisition-and-control-category/what-is-veristand.html) platform, which supports automotive communication protocols (CAN, XNET, FlexRay), data acquisition hardware (DAQ), simulation models, and signal conditioning via SLSC, among other features.

## NI VeriStand <a href="#ni-veristand-overview" id="ni-veristand-overview"></a>

**NI VeriStand** is an application software developed and maintained by NI. It enables the configuration of simulation models, I/O channels, data logging, stimulus generation, and host communication for NI Real-Time hardware.  Although this document does not focus on the features of VeriStand, it is beneficial to understand the typical VeriStand workflow and out-of-the-box features.  For more information, please see [**What is VeriStand?**](https://www.ni.com/en-us/shop/data-acquisition-and-control/application-software-for-data-acquisition-and-control-category/what-is-veristand.html)

The [**VeriStand Environment**](https://www.ni.com/docs/en-US/bundle/veristand/page/environment.html) includes the following major components:

* **VeriStand Editor:** Regroups all components of a VeriStand application. It allows access to project files, including the System Definition and Screen files, and is used to start, deploy, and stop Real-Time applications.
* **System Explorer Window**: Used to modify the System Definition file, which contains pre-execution settings of the Real-Time application. It manages DAQ hardware, XNET hardware, Custom Devices, simulation models, procedures, and more.


---

# 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/overview/cell-monitoring-device-emulation-cmde-add-on-1.2.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.
