NI CompactRIO Device Drivers May 2019 and R Series Multifunction RIO May 2019 (19.0) Known Issues

Panoramica

This document contains the known issues with NI CompactRIO Device Drivers May 2019 that were discovered after the release of NI CompactRIO Device Drivers January 2019. New issues appear at the top of this document. This list includes only severe or the most common issues, and does not include every issue known to NI.

The workarounds described in this document are not always tested by NI and are not guaranteed to resolve the issue. The brief description given does not necessarily describe the problem in full detail. If you would like more information on an issue, visit ni.com/contact and reference the issue ID. If you identify a workaround for an issue that is not listed in this document, please contact NI so that the workaround may be published.

ID Known Issue Affected LV Versions
724110 Project & System Comparison Dialog changes all channels and modules to upload LabVIEW 2019
735928 RIO Scan Interface (RSI) bitfile fails to install on cRIO-9055 and cRIO-9058 targets if software is installed via SystemLink LabVIEW 2019
737917 "Project or Library file is corrupt" error opening LabVIEW project with certain EOL cRIO products LabVIEW 2019
732407 LabVIEW FPGA compilation fails occasionally with NI 9205 in slot 5 of cRIO-905x targets LabVIEW 2018 and LabVIEW 2019
737501 Use of RSI Module Property Node in LabVIEW-built executable using CompactRIO 19.0 LabVIEW 2019 Runtime support will cause executable to fail LabVIEW 2019
727001 Calls from System Configuration API fail with error -2147467259 on first call after boot for VxWorks targets LabVIEW 2019
722866 Open Thermocouple Detection on NI 9213 Module used in NI 9149 chassis may incorrectly return error -1950678943 or -1950679035 when open thermocouple is detected and sample at rate of timeout period LabVIEW 2019
734618 In rare occurrences, cRIO-905x targets may restart during boot up LabVIEW 2019
733762 Using NI-922x modules on cRIO-905x targets may cause FPGA compilation to fail timing LabVIEW 2019
729217 Accessing properties of unconfigured modules in RSI mode may return error 65704 LabVIEW 2019
730745 FPGA code which accesses the NI 9231 module in a cRIO-904x or cRIO-905x chassis can put the module in an error state if the FPGA code is started, stopped, and restarted in quick succession LabVIEW 2018
727706 USB R Series DIO Write takes three cycles outside of Single-Cycle Timed Loop LabVIEW 2019

 

Known Issues with NI CompactRIO Device Drivers May 2019

ID Known Issues
724110

Project & System Comparison Dialog changes all channels and modules to upload

In certain cases, using the Project & System Comparison tool and changing a CompactRIO channel action to "Upload" will change all module and channel actions to "Upload".

Workaround:

Ensure the CompactRIO module settings are correct in the LabVIEW Project and select "Deploy All" from the target settings in the project.

Back to top

735928

RIO Scan Interface (RSI) bitfile fails to install on cRIO-9055 and cRIO-9058 targets if software is installed via SystemLink

An essential component for RSI is not installed on these targets when software is installed via SystemLink. Installation will complete without issue, but when a module is deployed to the target in Scan Mode, an error will occur indicating the RIO Scan Interface bitfile is missing or corrupt.

Workaround:

  • Install software via the Real-Time Software Wizard on a target that is not running the SystemLink Client software.

 

Back to top

737917

"Project or Library file is corrupt" error opening LabVIEW project with certain EOL cRIO products

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.

Workaround: 

  • Open in a version prior to LabVIEW 2019 and move the code to a non-EOL'd cRIO. Save and open in LabVIEW 2019
  • Update to NI CompactRIO Device Drivers June 2019 (19.1)

 

Back to top

732407

LabVIEW FPGA compilation fail occasionally with NI 9205 in slot 5 of cRIO-905x targets

LabVIEW FPGA compilations will fail occasionally when an NI 9205 is in slot 5 of cRIO-905x targets. The failure typically occurs when the top-level FPGA clock is set to 80 MHz.

Workaround:

  • Retry compilation of the LabVIEW FPGA VI
  • Move the NI 9205 to another cRIO slot

 

Back to top

737501

Use of RSI Module Property Node in LabVIEW-built executable using CompactRIO 19.0 LabVIEW 2019 Runtime support will cause executable to fail.

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.

Workaround:

To resolve this issue on a computer with CompactRIO 19.0 LabVIEW 2019 development support installed:

  1. Find the two required files at the following file locations:
    C:\Program Files (x86)\National Instruments\LabVIEW\2019\resource\nNIBlueBus_nCrioFixed_nRefnum.dll
    C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\Framework\Providers\nNIBlueBus_nCrioFixed.dll
  2. Copy these files to the following directory:
    C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2019

To resolve this issue on computers targeted for executable installation:

  1. On a computer with CompactRIO 19.0 LabVIEW 2019 development support installed, find the two required files at the following file locations:
    C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\nNIBlueBus_nCrioFixed_nRefnum.dll
    C:\Program Files (x86)\National Instruments\LabVIEW 2019\resource\Framework\Providers\nNIBlueBus_nCrioFixed.dll
  2. Add these files to the LabVIEW project where the LabVIEW installer for the executable program is being built
  3. In Installer Properties, in the Source Files category, add the two .dll files to the LabVIEW 2019 Run-Time folder

This will cause the files to be installed to the LabVIEW Runtime folder by the installer.

Back to top

727001

Calls from System Configuration API fail with error -2147467259 fail on first call after boot for VxWorks targets

For CompactRIO targets running the VxWorks operating system, the first call to the System Configuration API after the target boots will fail with error -2147467259. Subsequent calls to System Configuration API will succeed.

Workaround:

Retry System Configuration API call until it succeeds.

Back to top

722866

Open Thermocouple Detection on NI 9213 Module used in NI 9149 chassis may incorrectly return error -1950678943 or -1950679035 when open thermocouple is detected and sample at rate of timeout period

When the NI 9213 module is used in an NI 9149 Ethernet chassis, reading the variable with Read Variable with Timeout may return error -1950678943 or -1950679035 instead of error -65582 when an open thermocouple is detected. When this occurs, the module will also sample at the rate of the timeout.

Workaround:

  • Move 9213 modules to a chassis other than the NI 9149 if one is available
  • Turn off Open Thermocouple Detection and detect open thermocouple condition manually by detecting the open circuit value produced by the module

 

Back to top

734618

cRIO-905x targets may rarely restart during boot up

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.

Workaround:

No workaround required; issue fixes itself. Target runs without issue after successful reboot

Back to top

733762

Using NI-922x modules on cRIO-905x targets may cause FPGA compilation to fail timing

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

Workaround:

  • Retry the compilation repeatedly.
  • Reduce the rate at which the NI-922x module samples

 

Back to top

729217

Accessing properties of unconfigured modules in RSI mode may return error 65704

Attempting to access properties of modules that have not been deployed in RSI mode may result in error 65704: "CompactRIO:  Could not resolve RSI module URL".

Workaround:

Deploy the modules before attempting to access module properties

Back to top

730745

FPGA code which accesses the NI 9231 module in a cRIO-904x or cRIO-905x chassis can put the module in an error state if the FPGA code is started, stopped, and restarted in quick succession

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.

Workaround:

Disable the Run VI option if the Open FPGA Reference VI settings, or leave the option enabled and do not reset and run the FPGA after opening the reference

Back to top

727706

USB R Series DIO Write takes three cycles outside of Single-Cycle Timed Loop

Executing a USB R Series DIO Write takes three clock cycles instead of one when executed outside of a Single-Cycle Timed Loop.

Workaround:

Execute DIO Write inside Single-Cycle Timed Loop

Back to top

Glossary of Terms

 

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