LabVIEW Real-Time Module 2022 Q3 Bug Fixes

Overview

The following items are notable issues fixed between the release of LabVIEW Real-Time Module 2021 and LabVIEW Real-Time Module 2022 Q3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of LabVIEW Real-Time Module.

Bug Number

Legacy ID

Description

Details

1741985

Interactively Deploying a VI to a Real-Time Target Fails If the VI Has a Subpanel

Workaround:

Deploy the VI built into a Real-Time application.

Reported Version:

LabVIEW Real-Time Module 2015 SP1

Resolved Version:

LabVIEW Real-Time Module 2022 Q3

Added:

Jul 26, 2022

1571043

Real-Time Target Can Crash When an Interactively Running VI Calls a VI Deployed without Its Block-Diagram

The crash can occur if the VI being called is deployed in a source distribution.

    Workaround:

    Build the subVI into a PPL and deploy the PPL.

    Reported Version:

    LabVIEW Real-Time Module 2019

    Resolved Version:

    LabVIEW Real-Time Module 2022 Q3

    Added:

    Jul 26, 2022

    1828222

    LabVIEW May Crash When a Subroutine VI Is Skipped

    A conditional local variable written in a skipped subroutine VI may crash under the following scenarios:
    1. Subroutine VI is marked "Skip on Busy" and
    2. Subroutine VI contains an indicator written from inside a Case Structure and by a local variable.

    Workaround:

    There is currently no known workaround for this issue.

    Reported Version:

    LabVIEW Real-Time Module 2018

    Resolved Version:

    LabVIEW Real-Time Module 2022 Q3

    Added:

    Jul 26, 2022

    Additional Patch Information

    Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

    These patches currently do not have any special instructions.

    Glossary of Terms

     

    • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
    • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
    • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
    • Workaround - Possible ways to work around the problem.
    • Reported Version - The earliest version in which the issue was reported.
    • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
    • Date Added - The date the issue was added to the document (not the reported date).