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

# Release Notes 2019

## Version: 2019.3.2

### New features

* **Pickering**: Added support for 50-297-041 and 40-298-050 resistive cards.

### Improvements

* **RT-LAB**: Stopped changing the default Python version on Red Hat 32-bit Linux targets. Python 2.4 remains the system version, while Python 2.7 is used for scripting.

## Version: 2019.3.1

### New features

* **DIANE**: Added an I/O interface for the DIANE Ethernet communication protocol.

### Bug fixes

* **ARINC 429**: Fixed transmission issues when embedded recording was enabled.

## Version: 2019.3

### New features

* **RT-LAB**: Added support for Windows 64-bit.
* **RT-LAB API**: Added `getConnectionPointsForIO` and `getIOInterfaces`.
* **RT-LAB API**: Added linked-model support to `CreatePackage`.
* **Recorder**: Added internal timing, DataLoggerTool priority control, and SignalGroup selection in DataViewer.
* **ePHASORSIM**: Added native machine, exciter, stabilizer, and governor models, including GENSAL, GENSAE, ESAC1A, ESAC5A, ESAC6A, ESDC1A, ESDC2A, ESST1A, ESST4B, EXAC1, EXAC2, EXDC2, EXPIC1, IEEET1, IEEEX1, IVOEX, SCRX, URST5T, IEE2ST, IEEEST, PSS2A, PSS2B, GAST, HYGOV, IEESGO, and CRANIT.
* **TCP/UDP**: Added an I/O interface for TCP/UDP communication.
* **OPAL-RT Board**: Added support for distributing connections across multiple subsystems.
* **OPAL-RT Board**: Added support for OP4510 chassis equipped with a TE0741 410T FPGA.
* **CAN**: Added ARXML database support and channel enable/disable control.

### Improvements

* **RT-LAB**: Improved connection creation and project opening and closing.
* **RT-LAB**: Improved LabVIEW panel loading and model reset performance.
* **RT-LAB**: Improved ScopeView post-trigger processing.
* **RT-LAB**: Optimized Orchestra compilation.
* **RT-LAB API**: Allowed connection imports to continue when an individual connection cannot be created.
* **Recorder**: Added DataViewer JSON configuration documentation.
* **ePHASORSIM**: Improved runtime performance by up to 30%.
* **ePHASORSIM**: Added diagnostic warnings for invalid dynamic-model parameters.
* **ePHASORSIM**: Added a CRANIT example based on Kundur’s two-area system.

### Bug fixes

* **RT-LAB**: Fixed alias creation and refresh, Disconnect All, 64-bit target uninstallation, working sets, variable tables, drag-and-drop signal assignment, and `OpWriteFile` busy errors.
* **RT-LAB API**: Fixed connection export and imports containing approximately 3,000 connections.
* **LabVIEW**: Fixed panel connection loading, reopening, saving, and closing.
* **Recorder**: Fixed a memory leak, recorder deletion, status icons, trigger values, and holdoff settings.
* **ScopeView**: Fixed time conversion, acquisition durations greater than four seconds, time units, and the splash screen.
* **CAN**: Fixed Motorola-endian signal imports.
* **C37.118**: Fixed fractional-second rounding.
* **Modbus**: Ensured that the driver binds to the configured network interface.
* **VC707 S-Function driver**: Fixed the voltage range for group 3B of the OP5607 chassis.
* **OPAL-RT Board**: Improved bitstream discovery and fixed remote encoder support, synchronization cable configuration, and MuSE synchronization on 64-bit OPAL-RTLinux systems.
* **ARINC 429**: Fixed detection of JSON configuration file changes.

### Breaking changes

* **RT-LAB Python**: Removed support for Python 2.2 through 2.5.
* **RT-LAB Licensing**: Changed license validity to use `END_OF_SUPPORT_DATE`.


---

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