Home Support Documentation Bugs

NI-DAQmx 2022 Q3 Known Issues

Created Jun 22, 2023

Overview

This document contains the NI-DAQmx known issues that were discovered before and since the release of NI-DAQmx 2022 Q3. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.

Bug Number

Legacy ID

Description

Details
2052778

Using the DAQAssistant with DAQmx 2022 Q3 on LabVIEW 2022 Q3 Fails to Generate Code

Using the DAQAssistant on LabVIEW 2022 Q3 with DAQmx 2022 Q3 installed fails to configure the DAQAssistant node and gives the following code generation error:
"LabVIEW Code Generation failed to execute. This may occur if the code gen engine is not properly installed, or if you are using a LabVIEW version under development" . 

Other workflows that use the DAQ Assistant to generate DAQmx tasks also fail.

Workaround:

Install LabVIEW 2021 SP1

  • LabVIEW 2021 SP1 does not need to be activated, it is sufficient to install LabVIEW 2021 on your system and not activate it
  • Installing just the LabVIEW 2021 SP1 run-time engine will not be sufficient, the LabVIEW ADE needs to be installed 

Reported Version:

NI-DAQmx 2022 Q3

Resolved Version:

N/A

Added:

Aug 26, 2022
2067413

Loading a Project Containing RT CompactDAQ Target on LabVIEW 2022 Q3 when LabVIEW RT is Not Installed Crashes LabVIEW

Consider a case where LV 2022 Q3 and DAQmx 22.8 are installed, but not LabVIEW Real-time. When trying to create a new project and adding an RT CompactDAQ Target to the project, clicking on the newly added target causes LabVIEW to churn away for a bit and then crash.

    Workaround:

    Install LabVIEW Real-Time on the system and re-open the project

    Reported Version:

    NI-DAQmx 2022 Q3

    Resolved Version:

    N/A

    Added:

    Aug 26, 2022
    2067416

    Creating New "DAQmx task" from DAQmx Task Control Does Nothing

    A new DAQmx task should be created when you do the following:
    1. Drop a DAQmx task control.
    2. Right-click on the control and select "New NI-DAQmx task > MAX".
    However, clicking the button currently does nothing.

    Workaround:

    Create the task either from the Project Explorer, or from NI-MAX directly.

    Reported Version:

    LabVIEW 2022 Q3 | NI-DAQmx 2022 Q3

    Resolved Version:

    N/A

    Added:

    Aug 26, 2022
    2067423

    Power Cycling a Network Chassis with an Active DAQmx Output Task Results in Unexpected Behavior

    Power cycling a network chassis (like a 9189 or 9185) with a running task on an output channel  (9263) can cause LabVIEW and MAX to lock up in a way that's only recoverable by rebooting. Ending the task in task manager or using command line and calling taskkill /F also does not end the tasks when LabVIEW or MAX freeze in this state.

    Steps to reproduce
    1. Open LabVIEW and load the example Voltage - On Demand Output.vi.
    2. Run the example using a channel on the 9263.
    3. Unplug the power from the chassis, wait for a few seconds and plug it back in.
    4. If the task errors, and the VI stops, immediately try and start the VI again.
    5. Open MAX and refresh the device after power cycling.
    6. You may have to repeat steps 4-6 a few times, but eventually MAX and LV will hang in an un-killable state.

    Workaround:

    Reboot the machine

    Reported Version:

    FlexLogger 2022 Q2 | NI-DAQmx 2022 Q3 | NI-DAQmx 21.8

    Resolved Version:

    N/A

    Added:

    Aug 26, 2022
    1795745, 2281142

    LabVIEW applications that allocate memory using nipalk.sys may occasionally have bugcheck (Blue Screen) errors

    A customer has reported that one of their LabVIEW-based applications causes occasional bugcheck (Blue Screen of Death--BSoD) errors. The crash dump stacks vary, the involved process varies (nipalsm.exe, 'Customer Application'.exe), and the reported types vary (SYSTEM_SERVICE_EXCEPTION, ATTEMPTED_WRITE_TO_READONLY_MEMORY). However, all the observed errors involve nipalk.sys and they all seem to involve memory allocation. The error is observed only when the application initializes access to NI-DAQmx for the first time during an OS session. If the application is able to initialize successfully, the error is not observed while the application executes. The root cause of this error is currently unknown.

    Workaround:

    There is currently no known workaround for this issue.

    Reported Version:

    NI-DAQmx 19.1 | NI-PAL 19.0

    Resolved Version:

    N/A

    Added:

    Feb 13, 2023

    Final Time Issue Listed

    Issues found in this section will not be listed in future known issues documents for this product.

    There are currently no issues to list.

    Additional Resources

    Explore Support Content and Product Documentation 

     

     

    Ask the NI Community

     

     

    Request Support from an Engineer

     

    A valid service agreement may be required, and support options vary by country

     

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