Home Support Documentation Bugs

NI CompactRIO 2022 Q3 Known Issues

Created Jun 22, 2023

Overview

This document contains the NI CompactRIO known issues that were discovered before and since the release of NI CompactRIO 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
196384 674580

Setting CPU Pool and Running a High Priority Task Causes Normal Priority Tasks to Hang cRIO-904x targets

A normal priority task will hang until the high priority task is stopped. This occurs when the CPU pool has been set using the RT Set CPU Pool VI during boot or before running tasks.

Workaround:

Set the CPU pool after running high priority tasks. Or, if the CPU pool is set on boot, run normal priority tasks first and then run high priority tasks.

Reported Version:

NI-DAQmx 17.6

Resolved Version:

N/A

Added:

Dec 28, 2017
196839 732407

FPGA Compilation Fails Occasionally with NI 9205 in Slot 5 of cRIO-905x Targets

LabVIEW FPGA compilations will fail occasionally when an NI 9205 is in slot 5 of cRIO-905x targets. The failure occurs more frequently when the top-level FPGA clock is set to 80 MHz.

Workaround:

  • Retry compilation of the LabVIEW FPGA VI
  • Move the NI 9205 to a different slot in the CompactRIO

Reported Version:

NI CompactRIO 19.0

Resolved Version:

N/A

Added:

N/A
196787 727001

System Configuration API Fails First Time with Error -2147467259 on VxWorks Targets

For CompactRIO targets running the VxWorks operating system, the first call to the System Configuration API after the target boots will fail with error -2147467259. Subsequent calls to System Configuration API will succeed.

Workaround:

Retry the System Configuration API call until it succeeds.

Reported Version:

NI CompactRIO 19.0

Resolved Version:

N/A

Added:

N/A
196431 711964

MAX Technical Report doesn't include nirio.ini for Linux-RT-based controllers

When generating a technical report in MAX, nirio.ini is no longer included in the zip. This file contains details about the RIO Server remote machine access list. This issue only affects Linux RT targets and does not affect VxWorks or Phar Lap.

Workaround:

Browse to the report on the target at /var/lib/nirio/ini/nirio.ini, if it exists. The nirio.ini file only exists if you've modified the remote access list from the default values.

Reported Version:

NI CompactRIO 18.5

Resolved Version:

N/A

Added:

N/A
196963 711807

CompactRIO with DAQmx target data becomes corrupted after uninstalling and reinstalling software to target

Uninstalling and reinstalling the recommended software stack on CompactRIO with DAQmx targets leaves module aliases and chassis aliases corrupted. This causes warnings to appear in Measurement and Automation Explorer when those items are viewed.

Workaround:

Avoid uninstalling software on the target. If a software change is required, reformat the target and reinstall software.

Reported Version:

NI CompactRIO 18.5

Resolved Version:

N/A

Added:

N/A
196881 724110

Project & System Comparison Dialog Changes All Channels and Modules to Upload

In certain cases, using the Project & System Comparison tool and changing a CompactRIO channel action to Upload will change all module and channel actions to Upload.

Workaround:

Ensure the CompactRIO module settings are correct in the LabVIEW Project and select Deploy All from the target settings in the project.

Reported Version:

LabVIEW Real-Time Module 2019 | NI CompactRIO 19.0

Resolved Version:

N/A

Added:

Jul 23, 2021
196884 671854

VI Copied from One Controller to Another May Attempt to Run on the Original Controller

When copying a VI from one target to another and attempting to run that VI on the new target, the VI tries to run on the original target. This attempt may or may not be successful, based on the particulars of the VI being run and the hardware setup.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI CompactRIO 16.0

Resolved Version:

N/A

Added:

Dec 28, 2017
196966 722866

NI 9213 Module Open Thermocouple Detection in NI 9149 Chassis May Incorrectly Sample and Return Error -1950678943 or -1950679035

When the NI 9213 module is used in an NI 9149 Ethernet chassis, reading the variable with Read Variable with Timeout may return error -1950678943 or -1950679035 instead of error -65582 when an open thermocouple is detected. When this occurs, the module will also sample at the rate of the timeout.

Workaround:

  • Move 9213 modules to a chassis other than the NI 9149 if one is available
  • Turn off Open Thermocouple Detection and manually detect the open thermocouple condition by detecting the open circuit value produced by the module.

Reported Version:

NI CompactRIO 18.0

Resolved Version:

N/A

Added:

N/A
196437 661591

FPGA Single Cycle Timed Loops Driven by Imported Clocks Can Vary in Frequency

When using the sbRIO-9651 (System On Module/SOM), sbRIO-9607, or sbRIO-9627, the sbRIO CLIP Generator does not place constraints into the .XDC constraints file for imported clocks. If your FPGA application uses one of these clocks to drive a Single Cycle Timed Loop, the period of that loop may become erratic.

Workaround:

Follow the guidance of the Constraints and Hierarchy section of the Creating or Acquiring IP  LabVIEW FPGA Help to add the necessary constraint(s) to the CLIP file.

Reported Version:

NI-RIO 16.0.0

Resolved Version:

N/A

Added:

Dec 28, 2017
201483 707391

Mode switching a module from Scan Mode to FPGA/DAQmx while the module is in use can cause data corruption

If a module is in use and mode-switched from Scan Mode to FPGA/DAQmx mode, it will output corrupted data during one scan before error -65536 occurs

Workaround:

Ignore data from one scan before error -65536 is generated

Reported Version:

NI CompactRIO 18.1

Resolved Version:

N/A

Added:

N/A
201486 729217

Property Access of Unconfigured Module in Scan Mode May Return Error 65704

Attempting to access properties of modules that have not been deployed in RSI mode (Real-Time Scan mode) may result in error 65704: "CompactRIO: Could not resolve RSI module URL".

Workaround:

Deploy the modules before attempting to access module properties

Reported Version:

NI CompactRIO 18.0

Resolved Version:

N/A

Added:

N/A
255807 732821

Compilation failure when compiling on cRIO-904x targets with greater than 5 modules

With a cRIO-904x target with greater than five NI-9202 modules, LabVIEW FPGA compilation fails with the message "ERROR [Synth 8-3202] design needs 2 RAMB exceeds device capacity of 0".

Workaround:

Update to LabVIEW 2018 and CompactRIO Device Drivers 18.0 or higher.

Reported Version:

NI CompactRIO 18.5

Resolved Version:

N/A

Added:

N/A
890696 667698

NI 987x Serial Port Items Do Not Show Under the Module in NI MAX for cRIO-904x

The serial ports of the NI 987x may show up in MAX under the FPGA target instead of under the module item. Serial port functionality is not impacted.

Workaround:

Reboot the target.

Reported Version:

NI-RIO 17.6

Resolved Version:

N/A

Added:

Dec 28, 2017
1516233

Adding a CLIP on an sbRIO on a Windows machine with some locales might fail

Adding a CLIP on an sbRIO on a Windows machine with any locale that uses a ',' as the decimal character fails with the following error:

"Declaration is not valid.
Warning Info: This CLIP may have been generated for a different version of LabVIEW than you are currently running. Therefore, this CLIP might fail to compile or might not function correctly. To fix this issue, regenerate the CLIP in the latest version of LabVIEW."

Workaround:

Either of the following can be used as a workaround:
  • Change the decimal symbol in the Windows locale from ',' to '.'.
  • Set useLocaleDecimalPoint=False in LabVIEW.ini.

Reported Version:

NI CompactRIO 20.0 | NI CompactRIO 20.5 | NI CompactRIO 21.0

Resolved Version:

N/A

Added:

Jul 23, 2021
1596481

Installing R-Series before CompactRIO Could Lead To CompactRIO FPGA Targets Creation Failure

MXIe-RIO targets cannot be created in a LabVIEW project if CompactRIO is installed before R-Series.

Workaround:

Install CompactRIO before installing R-Series

Reported Version:

NI CompactRIO 21.0 | NI-RIO 21.0

Resolved Version:

N/A

Added:

Jul 29, 2022
1722320

Upgrading to Runmode 22.5 Will Cause sbRIO Devices to Be Unresponsive over USB

Single-Board RIO devices will become unresponsive over USB when runmode is upgraded to 22.5.

Workaround:

Hold the reset button to boot into the safemode (version 21.0.0) and downgrade to the LabVIEW 2021 stack.

Reported Version:

NI CompactRIO 2022 Q3

Resolved Version:

N/A

Added:

N/A
2062084

CompactRIO Single Board Controllers with NI-DAQmx Support and Real-Time Scan Resources Will Fail to Compile Bitfiles on LabVIEW 2022 Q3

Compilation failures with timing violations are likely to occur for users with C Series modules under Real-Time Scan Resources.The targets affected are sbRIO-9603, sbRIO-9608, sbRIO-9609, sbRIO-9626, sbRIO-9629, sbRIO-9638.

Workaround:

Use LabVIEW 2021 or earlier for these targets

Reported Version:

NI CompactRIO 2022 Q3

Resolved Version:

N/A

Added:

Aug 2, 2022

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