> 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/pe-add-on-simulink/appendix/known-issues-1.16.0.md).

# Known Issues 1.16.0

## **PEATT-1122**

The **PWM Measurements** and **Analog Outputs Advanced Channels** are regenerated each time the System Definition is opened. This behavior leads to the channels being unmapped from their pre-existing connections, and requiring manual re-mapping.

## **EFSNITT-788**

When the **Reset Models** Channel is asserted, the models are reset and placed into a paused state, but some outputs of the models retain their last valid value (instead of going back to 0).

## **PEA-133**

For frequencies below 1kHz, the **PWM Generators** produce signals with a frequency error. The observed error is approximately 0.02% for a 100Hz signal, 0.3% for a 10Hz signal, and 2.3% for a 1Hz signal.

## **PEATT-1081**

In VeriStand 2024 Q3, error 1003 occurs when a circuit model is loaded. This is due to [Known Issue 2798144](https://www.ni.com/en/support/documentation/bugs/24/labview-2024-q3-known-issues.html) in version 2024 Q3 of the LabVIEW Runtime Engine. To resolve this issue, install Patch 1 for the LabVIEW Runtime Engine 2024 Q3:

### Installing LabVIEW Runtime 2024 Q3 Patch 1

1. Close all NI software, including NI VeriStand.
2. Open the NI Package Manager.
3. Under the **INSTALLED** tab, locate the LabVIEW Runtime (64-bit) and confirm its version. If the version shown is ‘*2024 Q3*' or ‘*24.3.0.49385-0+f233*,’ then the patch is not installed.
4. Navigate to the **UPDATES** tab and select LabVIEW Runtime (64-bit) version ‘*2024 Q3 Patch 1*’ or ‘*24.3.1.4915-0+f2*’.
5. Click **Update** and reboot the machine when prompted.


---

# 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/pe-add-on-simulink/appendix/known-issues-1.16.0.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.
