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

# Release Notes 2022

## Version: 2022.1.1

### New features

* **PROFINET IO-Device**: Added a new I/O interface for OPAL-RTLinux platforms.
* **EtherCAT Slave**: Added support for OPAL-RTLinux.
* **Profibus**: Added Master and Slave support for OPAL-RTLinux.
* **Pickering**: Added support for the 50-295A-121-6/24 card and custom card configurations.
* **CAN**: Added support for DBC files containing multiple transmitters for the same message.
* **ARINC 429**: Added the option to invert gain and offset calculations.
* **FPGA S-Functions**: Increased LoadIN and LoadOUT support to 64 ports for VC707 and TE0741 boards.
* **EXata**: Added support for the new IEC 61850 solution.
* **TCP/UDP**: Added automatic correction of overlapping data frames.

### Improvements

* **Communication protocols**: Added port validation for C37.118 Slave, DNP3 Slave, IEC 60870-5-104 Slave, IEC 61850 MMS, Modbus TCP Slave, and OPC UA Server.
* **OPAL-RT Board**: Improved FPGA Scope configuration file management.

### Bug fixes

* **RT-LAB**: Fixed blocked resets when splitting a subsystem across multiple cores.
* **FPGA S-Functions**: Fixed inverted PWM duty cycles and issues when using eHS with polymorphic bitstreams.
* **FPGA**: Fixed FPGA enumeration issues.
* **C37.118 Slave**: Removed the 1,000-slave limitation and fixed communication when consecutive PMU IDs are not in ascending order.
* **IEC 61850**: Fixed MMS network configuration validation.
* **CAN**: Fixed CAN FD data frames containing more than 64 bits.
* **ARINC 429**: Corrected the order of gain/offset calculations and minimum/maximum value validation on reception.
* **Licensing**: Fixed target information retrieval on OPAL-RTLinux for license generation.

## Version: 2022.1

### New features

* **MATLAB/Simulink**: Added support for R2021a and R2021b.
* **OPAL-RT Simulink blocks**: Added OPAL-RT blocks to the MATLAB Quick Insert list.
* **Data Logger**: Added Boolean data type support.
* **Synchronization**: Added jitter detection during idle time for hardware and software synchronization.
* **OPAL-RT Board**: Added OP5367-1, OP5367-3, OP5367-5, and OP5360-3 card support.
* **OP5367**: Added threshold configuration for OP5367-3 and OP5367-5 cards.
* **IEC 61850**: Added a new I/O interface with MMS support and a conversion wizard for legacy configurations.
* **IEC 61850**: Added an S-Function helper block for generating GOOSE timestamps.
* **AsyncSerial**: Added RS-485 half-duplex support.
* **AFDX**: Added support for OPAL-RTLinux.
* **Modbus Master**: Added triggered read/write functionality.
* **ARINC 429**: Added dynamic SDI support.
* **OPAL-RT Board**: Extended OP4510 chassis support to the OP4510, OP4512, and OP4610 platforms.

### Improvements

* **RT-LAB**: Improved startup and shutdown stability and performance.
* **Recorder**: Added protection against exceeding the 2 GB maximum file size on 32-bit targets.
* **Orchestra**: Added support for relative paths to XML configuration files.
* **Diagnostic tools**: Added RAM and motherboard information to target diagnostics.
* **AFDX**: Added protection against using incompatible firmware.
* **I/O interfaces**: Improved performance with large configurations and simplified configuration editing.

### Bug fixes

* **RT-LAB**: Fixed watchdog-related simulation startup failures and erroneous “Clock change detected” errors.
* **RT-LAB**: Fixed target status management, multiple OpalD processes, model-loading race conditions, and Software Display issues.
* **Variable Table**: Fixed the display of MATLAB variable values.
* **Data Logger API**: Fixed compatibility with Python 3.7 and 3.8.
* **LabVIEW**: Fixed panel caching when the IP address or port changes.
* **Orchestra**: Restored missing API functions in Orchestra DLLs.
* **Simscape**: Fixed model compilation on OPAL-RTLinux using GCC.
* **CAN**: Fixed reset errors when communication occurs in only one direction.
* **OPAL-RT Board**: Fixed TSDIN performance, PWM Synchronized Analog In on OPAL-RTLinux, and overruns when remote systems have no output connections.
* **OPAL-RT Board**: Fixed compatibility between Fast Scope FPGA and Default Output Values, and board ID validation for threshold and multi-rate configurations.
* **FPGA S-Function**: Fixed configurations using multiple FPGAs of the same type across different subsystems.
* **SCPI**: Fixed measurement-reading delays with Sorensen Asterion devices.
* **Modbus Master**: Fixed byte ordering when reading floating-point values.
* **IEC 61850**: Fixed the microsecond value in GOOSE packets when using automatic clock detection.
* **AsyncSerial**: Fixed crashes on OPAL-RTLinux XG platforms.

### Breaking changes

* **MATLAB/Simulink R2021b**: `.mdl` files are supported only in beta mode; `.slx` is the recommended model format.


---

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