Archived: NI-RIO 4.0.0 Bug Fixes

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.


This document has been archived and is no longer updated by National Instruments.

The following items are the IDs and descriptions of a subset of issues fixed between NI-RIO 3.6.1 and NI-RIO 4.0.0. If you have a CAR ID, you can search this list to validate that the issue has been fixed in NI-RIO 4.0.0 with LabVIEW 2011.


Fixed Issue


Programmatically enabling counter-driven output on C Series digital I/O modules that support Specialty Digital Configuration resulted in error 42.


Accessing PXI FlexRIO devices through a laptop across MXI-Express could limit throughput of the FlexRIO.


Reading some unconfigured C Series module properties through the Scan Engine interface crashed the CompactRIO controller and required a controller reset.


Calling the Wait on IRQ function sometimes returned “Error -52010: The requested resource must be initialized before use” after running correctly for several hours.


Using memory-mapped I/O on a RIO device after the Windows host went through a sleep/wake cycle would return invalid data but no error.


In some cases, the watchdog timer on the NI cRIO-9075 and NI cRIO-9076 could assert up to 204.8 us earlier than expected.


Calling the DMA FIFO Read and Download functions on the same R Series FPGA session could cause a crash on the host Windows system.


Calling the DMA FIFO Read and Reset functions simultaneously on an R Series board could cause a crash on the host Windows system.


C Series module properties available through the FPGA Interface were not available through the Scan Engine.


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