NI CompactRIO Device Drivers and NI R Series Multifunction RIO June 2019 (19.1) Bug Fixes


The following items are a subset of issues fixed in NI CompactRIO Device Drivers and NI R Series Multifunction RIO Device Drivers June 2019 (19.1). These items have been resolved since NI CompactRIO Device Drivers and NI R Series Multifunction RIO Device Drivers May 2019 (19.0) were released. If you have an issue ID, you can search this list to validate that the issue has been fixed in NI CompactRIO Device Drivers and NI R Series Multifunction RIO Device Drivers June 2019.
IDFixed Issue


FPGA compilation is more likely to fail due to timing violations on cRIO-905x targets than other cRIO targets.


The NI 9231 module in a cRIO-904x or cRIO-905x chassis can enter an error state if FPGA code that accesses it is started, stopped, and restarted in quick succession. The module must be removed from the chassis and replaced to correct this error state. This commonly happens when the the FPGA reference is opened with the Run VI option checked, then reset, and restarted.


Timing constraints on cRIO-905x targets are applied incorrectly for some modules, which can result in FPGA compilation failure. This appears as a "Timing violation on non-diagram component" and can occur in a VI that compiles successfully on another cRIO target.


FPGA compilations containing NI-922x module I/O nodes on cRIO-905x targets may fail timing due to non-diagram components.


A driver accessed during cRIO-905x boot may cause a kernel crash, which causes the target to reboot. This is a rare, random occurrence that has no effect besides causing the target to reboot. After rebooting and completing boot operations, the target will function normally.


CompactRIO 19.0 LabVIEW 2019 Runtime support is missing components which enable the use of the RSI module property node. When the RSI module property node is present in a built executable that uses CompactRIO 19.0 LabVIEW 2019 Runtime support, the executable will fail with an indication that a .dll file is missing, or with an error that says a refnum entry point cannot be found. The required components missing from the LabVIEW 2019 Runtime support are present in LabVIEW 2019 development support, so the RSI module property node will work in the development environment.


LabVIEW projects saved in LabVIEW 2016 or earlier with certain EOL cRIO products can generate a "Project or Library file is corrupt" error in LabVIEW 2019. This only occurs when the original project contains a C Series module as a Real-Time Scan Resource for a cRIO-910x chassis or cRIO-901x controller.


When continously sampling at the maximum rate (4 MS/s) on the NI 9775 in a cRIO, the module will intermittently return invalid data.


The Voltage Range values are swapped between analog input channel 6 and 7 on PXI Express NI-7861 and NI-7862 cards. As a result, analog input channels 6 and 7 will read values scaled with improper gain only when set to different Voltage Ranges.


Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).