> 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/whats-new-in-rt-lab-2026.3/release-notes-2026.md).

# Release Notes 2026

## Version: 2026.1.6

### Bug fixes

* **S-Function I/Os**: Fixed memory corruption when the PWM Output block's `Output complementary` option was enabled.

## Version: 2026.1.2

### New features

* **MATLAB/Simulink**: Added support for R2025a and R2025b.
* **Dashboards**: Added Undo/Redo across all tables and boards.
* **MIL-STD-1553**: Added support for RPCIE-1553-G2-2MW and RPCIE-1553-G2-4MW cards.
* **ARTEMiS**: Added support for OPAL-RT SPS Software 25.2 with MATLAB R2025b.
* **ePHASORSIM**: Added Dynamic Load, Controllable Current Source, and Voltage Source at PV buses to the Excel Template.
* **ePHASORSIM**: Added time constants for Dynamic Load.
* **ePHASORSIM**: Added PiLine initialization validation to prevent zero series impedance from creating a singular admittance matrix.
* **MMC**: Added external DC-current injection and fast-discharge PWM blocks.

### Improvements

* **Dashboards**: Improved Graph widget performance, including reduced latency, support for more graphs per panel, and rendering while graphs are moved.
* **Dashboards**: Improved panel stability and responsiveness, including automatic recovery.
* **Dashboards**: Numeric Control widgets now accept binary and hexadecimal input.
* **Dashboards Python API**: Added support for Python 3.9.13 and later and vector datapoints in panel import/export examples.
* **OPAL-RT Board**: Prevented OP4300 and Versal systems from being reprogrammed while a simulation is running.
* **Pickering**: Updated the low-level driver to address issues affecting some resistive cards.
* **ARTEMiS**: Improved MATLAB path usage and configuration.
* **MMC**: Updated the library, library browser, MMC Pulse block, and MMC HVDC Bipole model.

### Bug fixes

* **Dashboards**: Fixed background image loss during panel export/import, Image Loop 404 errors after deleting attached files, and datapoint removal while rendering.
* **CAN**: Fixed a card initialization issue on HYPERSIM.
* **DNP3 Master/Slave**: Fixed initialization on Windows.
* **MIL-STD-1553**: Fixed compilation of the RPCIe 1MW example model.
* **Modbus Slave**: Fixed the gap read/write feature.
* **OPAL-RT Board**: Fixed an incorrect “Unsupported chassis type” error and an EEPROM issue affecting OP4300 and Versal systems.
* **S-Function I/Os**: Fixed a missing parameter in the OP7160 Analog Output block.

### Breaking changes

* **MATLAB/Simulink**: Removed support for R2022a and R2022b.
* **MMC**: Removed legacy demo models.


---

# 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/whats-new-in-rt-lab-2026.3/release-notes-2026.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.
