This document contains the NI-RIO 14.0.1 known issues that were discovered before and since the release of NI-RIO 13.0.0. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered. Each issue appears as a row in the table and includes an issue title, a brief description of the problem, and any workarounds that might help resolve the issue. To help determine if issues have been added since the date of publish, these newly added issues will be in their own section at the top (if applicable).
The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI and referencing the ID number given in the document. You can contact us through any of the normal support channels including phone, email, or the discussion forums. See www.ni.com/contact to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
Installing NI-RIO 14.0 for Linux over older version of NI-RIO causes corrupt installation.
Known Issues with NI-RIO 14.0.1 and LabVIEW
NI 9802 Mount and Unmount Methods cannot be called remotely from Windows
Normally, these commands would be run from the RT controller host (or remotely on the RT host through VI Server). For the EthernetRIO targets, NI 9146/9148 this is not an option. This means that the NI 9802 RT API cannot be used with these targets.
Operating System Crash When Scanning Internal Memory of NI-RIO processes
Using a program (such as a debugger) that scans process memory of an application that interfaces with a FlexRIO, MXI-Express RIO, or R Series device can cause an operating system crash. For more information, refer to Knowledgebase 6CBD88VQ: Scanning Memory Within a Process that uses FlexRIO, MXI-Express RIO, or R Series Devices Can Cause a Crash.
Do not access internal memory within a process that is using NI-RIO devices.
When connecting to a USB R-series card, if you insert or remove other USB devices, some USB controllers can cause persistent error -52023 when communicating with the USB R-series. For more information refer to Knowledgebase 6CCALAVQ: Why Do I Receive Error -52023 Using a USB R Series Device When Inserting or Removing an Additional Device?.
One of the following should work: Unplug the device and replug Suspend Power and Resume Disable and Enable Driver in Windows Device Manager Restart the computer See the above linked Knowledgebase for more details.
RIO Device Setup throws incorrect error when bitfile fails to load
RIO Device Setup will throw Error -2147220597 when it fails to deploy a bitfile. The correct error should be Error -63107. Typically users may see this error if they have just upgraded to NI-RIO Devices Drivers August 2014 f1.