NI CompactRIO Device Drivers June 2018 (18.1) Known Issues

Aperçu

This document contains the known issues with NI CompactRIO Device Drivers June 2018 that were discovered after the release of NI CompactRIO Device Drivers May 2018. 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. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field. 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
731435 Compilation failure due to "Timing violation on non-diagram component" on cRIO-905x targets LabVIEW 2018 through LabVIEW 2019
698313 FPGA compilation fails occasionally due to timing violations in cRIO-905x targets LabVIEW 2018 through LabVIEW 2019
660557 Host Memory Buffer Read on FPGA can return FIFO data. LabVIEW 2017 through LabVIEW 2018
706379 Deploying an EtherCAT Master Changes the Programming Modes on cRIO-904x to Real-Time Scan. LabVIEW 2017 and newer
701809 Installing software to a CompactRIO controller through SystemLink can appear to hang. N/A
699295 NI 9881 (CANopen) and NI 9882 (DeviceNet) modules aren't correctly shown in MAX. N/A
698239 Blank Test Panel will display for NI 9469 used in CompactRIO with DAQmx controllers. N/A
666943 Firmware updates occasionally fail with error code -2147219486. LabVIEW 2018

 

Known Issues with NI CompactRIO Device Drivers June 2018

ID Known Issues
731435

Compilation failure due to "Timing violation on non-diagram component" on cRIO-905x targets

Timing constraints on cRIO-905x targets are applied incorrectly for some modules, which can result in FPGA compilation failure. This appears as a "Timing violation on non-diagram component" and can occur in a VI that compiles successfully on another cRIO target.

Workaround: 

698313

FPGA compilation fails occasionally due to timing violations in cRIO-905x targets

FPGA compilation is more likely to fail due to timing violations on cRIO-905x targets than other cRIO targets.

Workaround: 

660557

Host Memory Buffer Read on FPGA can return FIFO data.

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.

Workaround: Manually implement arbitration between Host-to-Target-FIFOs and the Host Memory Buffer's Request / Retrieve methods.  

Back to top

706379

Deploying an EtherCAT Master Changes the Programming Modes on cRIO-904x to Real-Time Scan

Deploying an EtherCAT master with a NI 9144 or NI 9145 slave containing C Series modules in Scan Mode will also change the corresponding C Series modules' program mode to Scan Mode on the local cRIO-904x chassis. If you have an existing FPGA application running on the cRIO-904x while deploying the EtherCAT master, the C Series' I/O Nodes will report error 65673 (if error terminals are enabled) and will hold the last reported value. You can confirm this is the issue you are experiencing by looking at the C Series modules in NI MAX and noting their programming mode has changed to "Real-Time Scan (I/O Variables)".

Workaround: After deploying the chassis, you can use System Configuration functions to programmatically change the module's Programming Mode before starting the FPGA application. The general way to change programming modes programmatically is documented in this KnowledgeBase article, and a specific example (workaround_706379.zip) is attached to this document.  

Back to top

701809

Installing software to a CompactRIO controller through SystemLink can appear to hang.

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

Workaround: 

Reboot the CompactRIO controller as prompted after uninstalling software. 

Back to top

699295

NI 9881 (CANopen) and NI 9882 (DeviceNet) modules aren't correctly shown in MAX.

NI 9882 and NI 9881 modules show 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". This does not affect the functionality of the modules and is related to another Known Issue (#699848), where the NI 9882 lists "LabVIEW FPGA" as a Programming Mode, although it does not support it. This could happen on the cRIO-904x and cRIO-905x controllers. 

Workaround:

N/A; the modules are functional. 

Back to top

698239

Blank Test Panel will display for NI 9469 used in CompactRIO with DAQmx controllers.

If you click the Self Test button in NI MAX for the NI 9469, a Test Panel will open with nothing displayed. The Self Test button in NI MAX is incorrectly enabled for this module. The blank Test Panel does not imply anything negative about the NI 9469's functionality. 

Workaround:

N/A 

Back to top

666943

Firmware updates occasionally fail with error code -2147219486.

If you repeatedly upgrade the firmware on a certain RIO controllers and chassis, you might encounter error -2147219486. This error will be repeated on subsequent attempts after the initial failure. This could happen on the following models:
cRIO-9065, cRIO-9066, cRIO-9067, cRIO-9068, sbRIO-9607, sbRIO-9627, sbRIO-9637, sbRIO-9651, NI 9147, NI 9149, myRIO, roboRIO. 

Workaround: 

Format the controller, then attempt the firmware update again. In rare cases, this might not work. If this happens to you, please contact NI Support for potential recovery and/or RMA. 

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