NI CompactRIO Device Drivers January 2019 (18.5) Known Issues

Overview

This document contains the known issues with NI CompactRIO Device Drivers January 2019 that were discovered after the release of NI CompactRIO Device Drivers June 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. 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
738710 Intermittent invalid data on NI 9775 when sampling continuously at 4 MS/s LabVIEW 2016 through LabVIEW 2019
732821 Compilation failure when compiling on cRIO-904x targets with greater than 5 modules LabVIEW 2017
714320 WiFi-capable CompactRIO-903x models cannot connect to hidden SSID N/A
707391 Mode switching a module from Scan Mode to FPGA/DAQmx while the module is in use can cause data corruption LabVIEW 2018
711964 MAX Technical Report doesn't include nirio.ini for Linux-RT-based controllers LabVIEW 2018
710783 Host Memory Buffers Return Crossed Data LabVIEW 2017 through LabVIEW 2018
710205 FPGA Serial Number Enumerates As 0xFFFFFFFF For Some cRIO-905x LabVIEW 2018
711807 Warning glyphs appear for cRIO 904x and 905x devices after uninstalling and reinstalling RSS LabVIEW 2018

 

Known Issues with NI CompactRIO Device Drivers January 2019

ID Known Issues
738710

Intermittent invalid data on NI 9775 when sampling continuously at 4 MS/s

When continuously sampling at the maximum rate (4 MS/s) on the NI 9775 in a cRIO, the module will intermittently return invalid data.

Workaround: 

Update to CompactRIO Device Drivers June 2019 (19.1). 

Back to top

732821

Compilation failure when compiling on cRIO-904x targets with greater than 5 modules

With a cRIO-904x target with greater than five NI-9202 modules,  LabVIEW FPGA compilation fails with the message "ERROR [Synth 8-3202] design needs 2 RAMB exceeds device capacity of 0".

Workaround: 

Update to LabVIEW 2018 and CompactRIO Device Drivers 18.0 or higher.

714320

WiFi-capable CompactRIO-903x models cannot connect to hidden SSID

WiFi networks with hidden SSID's will not appear as available networks to WiFi-capable CompactRIO-903x targets, and cannot be found by name. If a WiFi-capable CompactRIO-903x target is connected to a network whose SSID is hidden, the CompactRIO will disconnect from the network and cannot reconnect.

Workaround:

Use a non-hidden SSID.

Back to top

707391

Mode switching a module from Scan Mode to FPGA/DAQmx while the module is in use can cause data corruption

If a module is in use and mode-switched from Scan Mode to FPGA/DAQmx mode, it will output corrupted data during one scan before error -65536 occurs.

Workaround: 

Ignore data from one scan before error -65536 is produced.

Back to top

711964

MAX Technical Report doesn't include nirio.ini for Linux-RT-based controllers

When generating a technical report in MAX, nirio.ini is no longer included in the zipped report folder. This file contains details about the RIO Server remote machine access list. This issue only affects Linux RT targets and does not affect VxWorks or Phar Lap.

Workaround: 

Browse to the report on the target at /var/lib/nirio/ini/nirio.ini, if it exists. The nirio.ini file only exists if you've modified the remote access list from the default values.

Back to top

710783

Host Memory Buffers Return Crossed Data

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.

Workaround: 

Alphabetize the Host Memory Buffers in your LabVIEW Project Explorer.

Back to top

710205

FPGA Serial Number Enumerates As 0xFFFFFFFF For Some cRIO-905x

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 cRIO-905x enumerates as 0xFFFFFFFF occasionally. This does not affect the controller's serial number, which returns the correct value (and matches what is printed on the label).

Workaround: 

If using the FPGA serial number for device identification, we recommend instead querying the controller's serial number. Both can be accessed using the System Configuration API.

Back to top

711807

Warning glyphs appear for cRIO 904x and 905x devices after uninstalling and reinstalling RSS

Uninstalling and reinstalling the recommended software stack (RSS) on CompactRIO-904x and 905x targets will cause warning glyphs to appear on the controller and modules in NI MAX, which indicate "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." 

Workaround:

Reformat the target and reinstall the recommended software stack to resolve the warnings.

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