NI-5640R 1.7 Known Issues

Panoramica

This document contains the NI-5640R known issues that were discovered before and since the release of NI-5640R 1.7. 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 NI-RFSG in which the issue was reported. If you discover the issue appears in an earlier version of NI-RFSG 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

ID Known Issue
256976

NI-5640R 1.3 and later includes a new FPGA I/O Node called DAC_Simultaneous_Reset that needs to be added to the target tree in older LabVIEW project files.

NI-5640R 1.3 and later includes a new FPGA I/O Node called DAC_Simultaneous_Reset.  The node must be added to the target tree in older LabVIEW project files. This node adds a new feature to the configuration loop that makes it easier to reset and synchronize the DACs.

Workaround: Complete the following steps to add the node to an earlier LabVIEW project file:
  1. Open LabVIEW project.
  2. Right-click the NI PCI-5640R target and select New»FPGA I/O.
  3. Under Available Resources, select Configuration»DAC_Simultaneous_Reset.
  4. Click Add.
  5. Click OK.
Reported Version: 1.3    Resolved Version: N/A    Added: 11/04/2010
257253

Cannot locate FPGA Examples.

LabVIEW FPGA examples cannot be located using the NI Example Finder.

Workaround: To locate these examples, refer to the table in the Installed Files section of the NI-5640 1.7 Readme or navigate to Start»All Programs»National Instruments»NI-5640R»Examples»<LabVIEW> and then open the FPGA folder.
Reported Version: 1.4    Resolved Version: N/A    Added: 11/04/2010
257263

Global variables stored in different locations.

Register and Circular Buffer data exchange policies use global variables created by the generated code behind the NI-5640R Asynchronous Programming nodes. If your LabVIEW project has not yet been saved, the global variables are stored on disk in a folder at <LabVIEW>\instr.lib\ni5640R\FPGA\AsyncWires\Globals. After your project is saved, the global variables are stored in a folder named Globals in the same folder where your project is stored. The globals are also placed in a LabVIEW project folder named Generated Globals. Deleting a global from the disk folder breaks the primitives that use it, but does not affect the bitfile produced by a previous compile. Causing that primitive to reconfigure itself also causes it to regenerate the globals.

Workaround: N/A
Reported Version: 1.4    Resolved Version: N/A    Added: 11/04/2010
257592

Host VIs do not open.

Host VIs developed in previous versions of LabVIEW do not run when initially opened in later versions of LabVIEW. For example, if you created a host VI in LabVIEW 8.2.1, the VI does not run when initially opened in any later version of LabVIEW. Similarly, if you created a host VI in LabVIEW 8.6, the VI does not run when initially opened in any later version of LabVIEW.

Workaround: For instructions about how to upgrade to LabVIEW 2010 or later, refer to the Upgrading the NI-5640R Driver topic of the NI-5640R Help File to run the VI.  
Reported Version: 1.4    Resolved Version: N/A    Added: 11/04/2010
239701

ni5640R Configure RTSI.vi does not correctly configure.

ni5640R Configure RTSI.vi does not correctly configure RTSI 6 or RTSI 7 on the NI PXIe-5641R.

Workaround: N/A
Reported Version: 1.5    Resolved Version: N/A    Added: 07/29/2011
309010

Temperature sensor reads may intermittently return incorrect data under high CPU load.

There is a timeout in sending commands to the temperature sensor, thereby causing the incorrect information to be read back.

Workaround: Run NI-5640R in LabVIEW 2011 or later. This workaround does not apply to versions of LabVIEW 2010 and earlier.
Reported Version: 1.6    Resolved Version: N/A    Added: 07/29/2011
144748

NI 5640R/5641R streaming examples miscalculate rate when using two channels.

The NI PCI-5640R and NI PXIe-5651R Stream to Disk example miscalculates the streaming rate when two channels are enabled. The streaming rate is calculated by multiplying the block size with the number of bytes per sample and factoring that value in with the time it takes to fetch data. When two channels are enabled, the block size is doubled for the raw data polymorphic VI to account for two interleaved channels. This compensation is not accounted for in the preceding calculation.  Thus, half the rate is reported for streaming statistics.

Workaround: N/A
Reported Version: 1.3    Resolved Version: N/A    Added: 08/01/2011
191505

Errors when running many of the NI-5640R template VIs and examples in Execute VI on Development with Simulated I/O mode.

NI-5640R template VIs (and thereby the FPGA examples) utilize Session to Refnum VI.  When run in Execute VI on Development Computer with Simulated I/O mode, NI-RIO read and write VIs may not function properly when using the Session to Refnum VI.

Workaround: On your block diagram, place a Diagram Disable Structure around all of the configuration VIs. This allows you to emulate your code.
Reported Version: 1.4    Resolved Version: N/A    Added: 08/01/2011

 

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.

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