NI CompactRIO Device Drivers January 2019 (18.5) Bug Fixes


The following items are a subset of issues fixed in NI CompactRIO Device Drivers January 2019 since NI CompactRIO Device Drivers June 2018. If you have an issue ID, you can search this list to validate that the issue has been fixed in NI CompactRIO Device Drivers January 2019 with LabVIEW 2018.


ID Fixed Issue


Deploying an EtherCAT master with a NI 9144 or NI 9145 slave containing C Series modules in Scan Mode would also change the corresponding C Series modules' program mode to Scan Mode on the local cRIO-904x chassis. If there was an existing FPGA application running on the cRIO-904x while deploying the EtherCAT master, the C Series' I/O Nodes would report error 65673 (if error terminals are enabled) and would hold the last reported value. 


When calibrating the PXIe-7846R, either programmatically or when using the NI 78xxR Calibration Utility, the calibration would fail with the message "The device type of the chassis or FPGA target in the LabVIEW project does not match the actual type of device".


User Defined Variables (UDVs) written to in a Single Cycle Timed Loop driven by a derived clock would occasionally fail to transmit data to the host. In some circumstances, this was accompanied by the error code -1 on the FPGA UDV writer node.


Using SystemLink, software installation to a cRIO-904x or cRIO-905x would fail to complete. This would only happen if before attempting to install software, you first uninstalled CompactRIO Support 18.1 and declined to reboot the CompactRIO controller.


The analog input channels AI0, AI1, AI2, and AI3 on the NI 9351 (Functional Safety module) would erroneously report a value of 0. This only occurred when using the Direct Access method to access the channels as opposed to the default Scanned Access.


After DAQmx is installed to a cRIO target, it requests a restart of the target. If the target was restarted too quickly following installation, the MXS database would become corrupted. This error would manifest as an inability to use any DAQmx Tasks or Scales or to configure DAQ devices.


When an SD card was inserted into cRIO-903x or cDAQ-913x "SD In Use" LED did not light up. The issue was purely visual and did not affect SD card operation.


NI 9882 and NI 9881 modules showed a warning "System storage for this item has entered an inconsistent state. The device name displayed here may be wrong. To fix the problem, give this device a unique name".


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