NI CompactRIO and NI R Series MultifunctionRIO August 2015 Known Issues

Overview

This document contains the known issues with NI CompactRIO Device Drivers August 2015 and NI R Series Multifunction RIO Device Drivers August 2015 that were discovered before and after the release of NI-RIO Device Drivers February 2015. New issues appear at the top of this document. Not every issue known to NI will appear on this list. The list is intended to show only the severe or most 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.

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.

IDKnown IssueAffected LV Versions
437384Xilinx Compile Tools report "Unexpected EOF" when compiling a Hybrid Interface mode bitfile.2014 SP1, 2014, 2013 SP1
529910The Minimum Time Between Conversion for the NI 9201 is not properly coerced.2014 SP1
531415The RT LED.vi behavior is incorrect for the cRIO-9063, cRIO-9064, cRIO-9065, cRIO-9066, cRIO-9067, and sbRIO-9651.2014 SP1, 2014
520648A socketed CLIP created from LabVIEW 2014 for the sbRIO-9651 System on Module that includes the secondary Ethernet port will not compile with LabVIEW 2015.2015
538646Updating the firmware of a ZYNQ based Compact RIO, Single-Board RIO, or Ethernet RIO targets with the incorrect firmware can cause the target to appear non-functional.2015, 2014 SP1

Known Issues with NI-RIO 14.0.1 and LabVIEW

IDKnown Issues
437384

Xilinx Compilation Tools may report "Unexpected EOF" when compiling a Hybrid Interface mode bitfile.

A compilation with Xilinx Compilation Tools will report an "Unexpected EOF" failure. Once the failure message appears, it may appear with every compilation that includes the Scan Interface or Hybrid Interface mode.

Please contact support@ni.com if you experience this issue.

Workaround:

Back to top

529910

The Minimum Time Between Conversion for the NI 9201 is not properly coerced.

In FPGA Interface mode, the NI 9201 does not coerce the Minimum Time Between Conversion value to a minimum of 2 us. This sets the maximum sampling rate of the module  to 500 kS/s.

Workaround:

To acquire at the maximum supported sample rate please use a value of 2 us for the Minimum Time Between Conversion..

Back to top

531415

The RT LED.vi behavior is incorrect for the cRIO-9063, cRIO-9064, cRIO-9065, cRIO-9066, cRIO-9067, and sbRIO-9651.

The documented behavior of the RT LED for these chassis are not consistent with published documentation. The RT LEDs.vi used to interface with the user RT LED on the controller front panel and will report the status of the LED. If the secondary led (2) is set the VI will report a value of TRUE. The chassis above do not contain a secondary user LED. In addition, the blink (3) value does not enable the blinking behavior of the LED.

Workaround:

Back to top

520648

A socketed CLIP created in LabVIEW 2014 for the sbRIO-9651 System on Module that includes the secondary Ethernet port will fail to compile due to timing violations in LabVIEW 2015.

Due to changes in the LabVIEW 2015 FPGA Module, you must regenerate a socketed CLIP if you require the secondary Ethernet port enabled.

Workaround:

To update your socketed CLIP for LabVIEW 2015, run the sbRIO CLIP Generator from the Start Menu. You can select you Socketed CLIP configuration from the drop down box and use the LabVIEW Version dropdown to select 2.0 (LabVIEW 2015). Once you’ve finished updating your configuration your bitfile should successfully compile.

Back to top

538646

Updating the firmware of a ZYNQ based Compact RIO, Single-Board RIO, or Ethernet RIO target with the incorrect firmware can cause the target to appear non-functional.

It was discovered that uploading the incorrect firmware to a device can cause certain device functionality like Ethernet communication to be non-functional.

Workaround:

Upload the specific firmware for each target using the targets model number. See KnowledgeBase 702FS6JQ for more information. 

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