Archived: LabVIEW 2014 Instrument Design Libraries for Vector Signal Transceivers 14.0 Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



This document contains the NI LabVIEW 2014 Instrument Design Libraries for Vector Signal Transceivers 14.0 known issues that were discovered before and since the release of NI LabVIEW 2014 Instrument Design Libraries for Vector Signal Tranceivers 14.0. 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 LabVIEW Instrument Design Libraries for Vector Signal Transceivers in which the issue was reported. If you discover the issue appears in an earlier version of NI LabVIEW Instrument Design Libraries for Vector Signal Transceivers 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 by Severity

364860 A deadlock can occur when creating two peer-to-peer streams between two devices in opposite directions concurrently
365340 Running a VST sample project FPGA VI on a development computer with simulated I/O context causes LabVIEW to hang
363009 NI PXIe-5644R, NI PXIe-5645R, or NI PXIe-5646R device may occasionally appear outside the chassis in MAX when the device is installed for the first time
364518 Error –52018. A hardware failure has occurred. The operation could not be completed as specified
453026 When closing a newly created Simple VSA/VSG sample project, selecting Save in the Save Changes (Close Project) dialog box does not work
369338 A dialog box prompts you to save a file when you create a VST sample project in localized LabVIEW
392126 The niVST Calibration.lvlib:Self-Calibrate.vi leaks memory when loading and unloading
414557 Error –2147220623 occurs when a Simple VSA/VSG sample project created in design library 1.0 is run in design library 13.5
364736 Waveform Sequencer does not generate any samples if the Set Priming Depth VI is set to a value of 4 samples or less
452057 The default maximum outstanding requests for data value for VST DRAM memory items is insufficient for maximum DRAM throughput
425439 When NI-RFSA and NI-RFSG both export a signal to the same external trigger line on a VST, LabVIEW does not return an error
411948 Error –373104 occurs when a hyphen character is used in a configuration list name
464021 The 802.11ac 80 MHz bandwidth and 160 MHz bandwidth with channel tracking enabled specifications are marked as warranted in the NI PXIe-5646R Specifications



364860

A deadlock can occur when creating two peer-to-peer streams between two devices in opposite directions concurrently

Workaround: To avoid the deadlock, serialize the calls to the niP2P Create Peer to Peer Stream VIs.

Reported Version: Design Library 1.0    Resolved Version: N/A    Added: 08/28/2012
365340

Running a VST sample project FPGA VI on a development computer with simulated I/O context causes LabVIEW to hang
Running a VST Sample Project FPGA VI on the development computer with simulated I/O context causes LabVIEW to hang because of the way LabVIEW FPGA allocates and uses the DRAM memory primitive when executing in the development computer context.

Workaround: There is no workaround to achieve full functionality, that is, to achieve the same waveform and record memory size available when running on hardware. However, you can use the following instructions to work around the LabVIEW memory issue:
  1. In the FPGA Target in your LabVIEW project, navigate to Memory/FIFOs»Acquisition»acq.data memory 0.
  2. Right-click acq.data memory 0 and select Properties.
  3. Under the General category, change the Requested number of elements to a smaller number, for example, 65,536.
  4. Repeat steps 2 and 3 for Memory/FIFOs»Generation»wfm seq.data memory 0.
  5. Change the memory size (128-bit elements) value in Acquisition.lvclass»Private»Constants.vi.
  6. Change the waveform memory size (num of 128-bit elements) value in Generation.lvclass»Private»Constants.vi.
Note: There is no guarantee that the rest of the sample project will work after you work around the LabVIEW memory issue.

Reported Version: Design Library 1.0    Resolved Version: N/A    Added: 08/28/2012
363009

The NI PXIe-5644R, NI PXIe-5645R, NI PXIe-5646R device may occasionally appear outside the chassis in MAX when the device is installed for the first time
The NI PXIe-5644R, NI PXIe-5645R, or NI PXIe-5646R device may occasionally appear outside the chassis in Measurement & Automation Explorer (MAX) when the hardware/software is installed for the first time. The device should still function properly.

Workaround: Restart the machine to get the device to appear in MAX properly.

Reported Version: Design Library 1.0    Resolved Version: N/A    Added: 08/28/2012
364518

Error –52018. A hardware failure has occurred. The operation could not be completed as specified
This error may occur when an instrument design VI accesses elements of an FPGA VI that are inside a Single Cycle Timed Loop (SCTL) that does not have a running clock. In this case, the problem is not a hardware failure and can be fixed by enabling the clock of the SCTL.

Workaround: Ensure that the SCTL clocks are running before calling the VI that returns the error.

Reported Version: Design Library 1.0    Resolved Version: N/A    Added: 08/28/2012
453026

When closing a newly created Simple VSA/VSG sample project, selecting Save in the Save Changes (Close Project) dialog box does not work
When closing a newly created Simple VSA/VSG sample project, selecting Save in the Save Changes (Close Project) dialog box does not work and the Save Changes (Close Project) dialog box does not close.

Workaround: There are two possible workarounds for this issue:
  • Close a newly created Simple VSA/VSG sample project and select Don't Save in the Save Changes dialog box when prompted. This workaround will close the Save Changes dialog box, but will not save your sample project.
  • Complete the following steps:
    1. Right-click FPGA Interface Type Definitions.lvlib in the sample project tree, and select Properties.
    2. In the General Settings category, select Separate compiled code from source file.
    3. Select OK to close the Properties dialog box.
    4. Close the project and choose Save when prompted.

Reported Version: Design Library 13.5    Resolved Version: N/A    Added: 02/25/2014
369338

A dialog box prompts you to save a file when you create a VST sample project in localized LabVIEW
The first time you create a VST sample project (Simple VSA/VSG or Simple VST Streaming) in localized LabVIEW after installing instrument design libraries 2012.1, a dialog box prompts you to save niLvFpga_Open_PXIe-5644R.vi or similar.

Workaround: Click Save in the dialog box to continue creating the sample project.

Reported Version: Design Library 2012.1    Resolved Version: N/A    Added: 04/05/2013
392126

The niVST Calibration.lvlib:Self-Calibrate.vi leaks memory when loading and unloading
When using Self-Calibrate VI from the NI VST Calibration palette to self-calibrate the NI PXIe-5644R or NI PXIe-5645R, a memory leak may occur when loading and unloading the VI repeatedly.

Workaround: Keep the Self-Calibrate VI in memory. For example, in your top-level VI, create a "dummy" subVI that includes one instance of the Self-Calibrate VI to keep the Self-Calibrate VI loaded in memory. For applications that optimize memory usage where it is not acceptable to keep the Self-Calibrate VI in memory, you can minimize the memory leak by keeping a Timed Loop in memory. A memory leak will still exist, but it will be considerably smaller.

Reported Version: Design Library 2012.1    Resolved Version: N/A    Added: 04/05/2013
414557

Error –2147220623 occurs when a Simple VSA/VSG sample project created in design library 1.0 is run in design library 13.5
Running a Simple VSA/VSG sample project created with NI LabVIEW 2012 Support for NI PXIe-5644R 1.0.0 with current VST support returns error -2147220623.

Workaround: Complete the following steps to workaround this issue:
  1. In the Simple VSA/VSG sample project, navigate to Instrument Driver»Instrument Support - Shared.lvlib»Get RIO Product ID.vi.
  2. Open the Get RIO Product ID VI.
  3. Call the Create Filter VI after the Initialize Session VI, but before the Find VI. The Create Filter VI is located on the Functions palette at Measurement I/O»System Configuration»Utilities.
  4. Wire the session out and error out outputs of the Initialize Session VI to the session in and error in inputs of the Create Filter VI.
  5. If IsDev is not selected on the System Filter property node, click the first entry in the property node and select the Is Device property.
  6. Wire a Boolean constant to the IsDev input, and set it to True.
  7. Wire the System Session and error out outputs of the System Filter property node to the filter in and error in inputs of the Find VI.

Reported Version: Design Library 13.5    Resolved Version: N/A    Added: 02/25/2014
364736

Waveform Sequencer does not generate any samples if the Set Priming Depth VI is set to a value of 4 samples or less
The Retrieve Waveform Sample FPGA VI of the Waveform Sequencer library does not generate any samples if you set the generation priming depth to a value less than or equal to 4 in the Set Priming Depth VI of the Waveform Sequencer host library.

Workaround: Configure the Set Priming Depth VI to a value of at least 5 samples; otherwise do not call the Set Priming Depth VI. If you do not call the Set Priming Depth VI, the application uses the default priming depth.

Reported Version: Design Library 1.0    Resolved Version: N/A    Added: 08/28/2012
452057

The default value for Maximum outstanding requests for data on VST DRAM memory items is insufficient for maximum DRAM throughput
When creating a new DRAM memory item, the default value for Maximum outstanding requests for data is 32. This value must be changed to 64 to achieve maximum DRAM throughput on VST devices.

Workaround: Right-click a DRAM memory item under an FPGA Target in your LabVIEW project, and select Properties. In the General category, change the value for Maximum outstanding requests for data to 64.

Reported Version: Design Library 13.5    Resolved Version: N/A    Added: 02/25/2014
425439

When NI-RFSA and NI-RFSG both export a signal to the same external trigger line on a VST, LabVIEW does not return an error
It is possible to export two different signals to the same external trigger line on a VST, for example, NI-RFSG exports a Marker Event to PFI0, and NI-RFSA exports a Start Trigger to PFI0. However, LabVIEW does not return an error when this occurs, which causes only the last item that is configured within either driver to export its signal.

Workaround: Avoid exporting signals from both drivers to the same external trigger line.

Reported Version: RFSA/RFSG Support 13.0    Resolved Version: N/A    Added: 02/25/2014
411948

Error –373104 occurs when a hyphen character is used in a configuration list name
When creating a configuration list in NI-RFSA or NI-RFSG on a VST target, the use of hyphens in the configuration list name results in error -373104, the specified configuration list name is invalid.

Workaround: Avoid using hyphen characters in configuration list names.

Reported Version: RFSA/RFSG Support 1.1    Resolved Version: N/A    Added: 02/25/2014
464021

The 802.11ac 80 MHz bandwidth and 160 MHz bandwidth with channel tracking enabled specifications are marked as warranted in the NI PXIe-5646R Specifications
The 802.11ac 80 MHz bandwidth and 160 MHz bandwidth with channel tracking enabled specifications are typical specifications. These specifications should be marked as typical specifications instead of warranted in the NI PXIe-5646R Specifications.

Workaround: N/A

Reported Version: 376125A-01, 326125A-01    Resolved Version: N/A    Added: 04/10/2014

Related Topics

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