NI CompactRIO Device Drivers May 2019 (19.0) Bug Fixes


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


IDFixed Issue


The RIO Resource (FPGA) serial number can be seen in NI-MAX as a property of the FPGA, and can also be queried in LabVIEW using the System Configuration API. The FPGA serial number on some cRIO-905x can eumerate as 0xFFFFFFFF. This does not affect the controller's serial number, which returns the correct value (and matches what is printed on the label).


If the arrangement of Host Memory Buffers in your LabVIEW Project Explorer are not in alphabetical order, the references used by Real-Time and FPGA will not match. This can result in Real-Time and FPGA VIs accessing different regions of memory, despite using the same Memory Name.
You must have two or more Host Memory Buffers in your project to experience this issue. 


cRIO-9037 and cRIO-9032 controllers cannot connect to WiFi networks with hidden SSID, and will lose connection to WiFi networks if the SSID is hidden while the cRIO is connected.


When using a Host Memory Buffer and a Host to Target DMA FIFO simultaneously, the Host Memory Buffer's Retrieve method on FPGA can incorrectly return data sent by the FIFO. This does not affect the FIFO's data in any way.


If you already have CompactRIO 18.0 or 18.1 installed prior to performing the Windows 10 1703 update ("Creators Update"), the USBLAN driver may stop functioning. The USBLAN driver is what CompactRIO uses to emulate an Ethernet port when you plug a RIO controller in via USB. With this issue, the USBLAN driver does not work and therefore Windows will not associate the RIO controller you plug in. The device might show as "Generic Usb-EEM Network Adapter" in Windows Device Manager. If you did not have CompactRIO installed prior to the Windows update and install it afterward, you will not experience this issue.


When performing network device discovery from a Linux RT operating system, the lvrt process can occasionally crash. Examples of discovery include a call to the Initialize Session VI, or the discovery of a network cDAQ. This will only happen in situations where a large number of devices that are discoverable by NI are present on the network.


The _Chassis_ and _Slot_ fields appear for both cRIO-903x and cRIO-904x. However, these fields should not be present in this window. The value of "Unknown" in the fields does not indicate that anything is wrong with the FPGA target or communication to the FPGA target.


R-Series PXIe Module 100MHz Timebase is not phase locked to PXI_CLK10


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