Each issue appears as a row in the table and includes the following fields:
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
|
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.