FlexRIO Support 15.1 Known Issues

Overview

This document contains the FlexRIO Support 15.1 known issues that were discovered before and since the release of FlexRIO Support 15.1. Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that can be encountered.

Each issue appears as a row in the table and includes the following fields:

  • Issue ID - The number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.  "N/A" indicates that there is no ID assigned to the issue.
  • Issue Title (in italics) - Describes the issue in one sentence or less.
  • Problem Description - A few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you may want more information on an issue. If you would like more information on an issue, contact NI and reference the ID number given in the document.
  • Workaround - Possible ways to work around the problem. 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, visit www.ni.com/kb/ and enter the KnowledgeBase number in the search field to locate the specific document.
  • Reported Version - The earliest version of FlexRIO in which the issue was reported. If you discover the issue appears in an earlier version of FlexRIO than is reported in this field, report the discrepancy to NI to have the field updated.
  • 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).

Known Issues

545598 The NI-793xR USB Device Port becomes inactive in Windows 8.1 after 2 minutes of inactivity.
544097 The High Throughput Streaming example incorrectly calculates throughput.
526736 Wait For Stream.vi can return the incorrect "Samples Transferred" value in simulation mode.
545599 Controller for FlexRIO (NI-793xR) devices do not support debugging FPGA VIs using a third-party simulator.
489614 Synchronous CLIP signals incorrectly allowed for use in synchronous clock domains.



ID Known Issue
545598

Return
The NI-793xR USB Device Port becomes inactive in Windows 8.1 after 2 minutes of inactivity.

Public Details:Windows 8.1 power management features shut down USB ports that remain inactive for several minutes. This causes an NI-793xR connected through a device port to become inactive, requiring a restart to restore connection.

Public Workaround: Complete the following steps to disable the connected standby feature.
  1. Change the registry key "HKLM\System\CurrentControlSet\Control\Power\CsEnab​led" from "1" to "0".
  2. Reboot the system.
You can also run the batch file (make sure to run it as Administrator) in the attachment.

Reported Version: 15.1    Target Version for Fix: 15.5    Added: 11/30/2015/
544097

Return
The High Throughput Streaming example incorrectly calculates throughput.

Public Details: The example does not accurately demonstrate how to stream at the full bandwidth on NI PXIe-797xR devices.

Reported Version: 14.5    Target Version for Fix: 15.5    Added: 11/30/2015/
526736

Return
Wait For Stream.vi can return the incorrect "Samples Transferred" value in simulation mode.

Public Workaround: Do not use the Samples Transferred output from the Wait For Stream.vi as the value for the Requested Elements input on a DMA FIFO when completing a finite transfer.

Public Details: Due to a race condition present only in simulation mode, the Wait For Stream.vi can return the penultimate Samples Transferred value rather than the expected terminal value of a finite transfer.

Reported Version: 14.0    Target Version for Fix: 15.0    Added: 11/30/2015/
545599

Return
Controller for FlexRIO (NI-793xR) devices do not support debugging FPGA VIs using a third-party simulator.

Public Details: NI-7931R, NI-7932R, and NI-7935R products do not support the use of a third-party simulator to simulate and debug a LabVIEW FPGA VI.

Reported Version: 15.1    Target Version for Fix: 15.5    Added: 11/30/2015/
489614

Return
Synchronous CLIP signals incorrectly allowed for use in synchronous clock domains.

Public Workaround: Recompile the FPGA VI with the IO node in the correct clock domain if using NI 5751, NI 5752, or NI 5781.

Public Details: Certain FlexRIO adapter modules have CLIP signals that must be used in a clock domain provided by the CLIP. Accessing the IO node outside of that clock domain can cause a compilation error. Some adapter modules do not throw a compilation error when the IO node is used in the wrong clock domain, resulting in glitched data.

Reported Version: 14.0    Target Version for Fix: Unspecified    Added: 11/30/2015/

Contacting NI

Contact NI regarding this document or issues in the document. If you contact NI in regards to a specific issue, reference the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also contact us if you find a workaround for an issue that is not listed in the document.

 

Related Resources

 

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