> 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.md).

# What's New in RT-LAB 2026.3!

## **Version: 2026.3**

**Release date:** 2025/08/02

### New features

* Support for MATLAB/Simulink R2025a and R2025b.
* **MIL-STD-1553**: Added support for RPCIE-1553-G2-2MW and RPCIE-1553-G2-4MW cards
* **Dashboards**: Undo/redo functionality is now available across all tables and boards.
* **ARTEMiS**: Added support of OPAL-RT SPS Software 25.2 for MATLAB R2025b.
* **ePHASORSIM**: Added support for Dynamic Load, Controllable current source, and Voltage source at PV buses in Excel Template
* **ePHASORSIM**: Added time constants support for Dynamic load
* **ePHASORSIM**: Added a validation at the PiLine initialization to prevent zero series impedance causing the admittance matrix to be singular

### Improvements

* **OPAL-RT Board**: Prevented OP4300 and Versal systems from being reprogrammed while a simulation is running
* **Pickering**: Updated the low-level driver to fix an issue affecting some resistive cards
* **Dashboards**: Graph widget performance has been significantly enhanced, reducing latency for smoother simulation control.
  * More graph widgets can be instantiated per panel.
  * Graphs now continue to render while being moved.
  * The graph status is more precise when not rendering.
  * Note that it is no longer possible to hide a curve by clicking on the legend.
* **Dashboards**: Panel stability has been improved for a more reliable experience.
  * Auto-recovery has been added.
  * Panels have better responsiveness during edition while acquiring on graph widgets.
* **Dashboards**: The Numeric Control widget can now receive Binary and Hexadecimal formats as input.
* **Dashboards Python API**: The installation script install\_opalone\_api.py now supports all Python versions >= 3.9.13.
* **Dashboards Python API**: Panel import/export examples now support vector datapoints.
* **ARTEMiS**: Improved Matlab path usage and configuration.

### Bug fixes

* **CAN**: Fixed a card initialization issue on Hypersim
* **DNP3 master & slave**: Fixed an initialization issue on Windows
* **MIL-STD-1553**: Fixed a compilation issue in the RPCIe 1MW example model
* **S-Function IOs**: Fixed missing parameter issue in OP7160 analog output block (DRV-5269)
* **Dashboards**: Fixed an issue that removed the background image when exporting and importing a panel.
* **Dashboards**: Fixed a 404 error in the Image Loop Control and Display after deleting an attached file.
* **Dashboards**: Fixed an issue with datapoint removal while rendering.

### Breaking changes

* Removed support for MATLAB/Simulink R2022a and R2022b for RT-LAB and all the toolboxes.
* **MMC**: Legacy demo models are removed.

### Known issues

N/A

***

## Version: 2026.4.2

**Release date:** 2025/12/02

### Bug fixes

* **S-Function IOs**: Fixed memory corruption when the PWM Output block’s "Output complementary" option was enabled.


---

# 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.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.
