Home Support Documentation Bugs

Archived: NI-VNA 14.0 Known Issues

Updated Mar 10, 2020

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-VNA 14.0 known issues that were discovered before and since the release of NI-VNA 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-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 by Severity

506610—NI-VNA measurements are incorrect after loading multiple CHX files using the niVNA Load Calibration And Configuration Data From File VI or the niVNA_LoadCalibrationAndConfigurationDataFromFile function.
319170—NI-VNA does not recall setup/calibration files from previous NI-VNA versions in Windows XP.
433386—Performing a 2 port adapter removal calibration with the AutoCal module in the NI-VNA Soft Front Panel (SFP) results in unexpected 90 degree phase discontinuities.
496962—NI-VNA occasionally fails to export End of Step and End of Sweep events to the PXI_TRIG lines.
385294—The NI PXIe-8133 Controller hangs when using BIOS (basic input/output system) 1.2.0f6 with the NI PXIe-5630.
200090—The NI-VNA Soft Front Panel cannot load when using Remote Desktop on Windows XP.
494957—NI-VNA cannot export the Ready for Start event.
460163—NI-VNA Soft Front Panel does not reserve PXI_TRIG lines.
453927—The NI PXIe-5632 sends a spurious pulse on any active PXI_TRIG line when you configure it for a Rising Edge or Active High Level output event in the NI-VNA Soft Front Panel.
492581—NI-VNA does not support IVI interchangeability checking or coercion recording.
250239—Users can receive a misleading error message when loading an AutoCal characterization file.
451229—The NI PXIe-5632 continues to drive PXI_TRIG lines after you close the NI-VNA Soft Front Panel.
245461—The NI-VNA Soft Front Panel consumes all the video memory.
451230—The NI PXIe-5632 sends spurious pulses on previously used PXI_TRIG lines when the NI-VNA Soft Front Panel is closed.
408875—Launching the NI-VNA Soft Front Panel fails when using the NI RMC-8354.
246949—NI-VNA returns "Device in Use" error when device is unavailable.
456886—NI-VNA does not calibrate with the AutoCal over a remote desktop connection when you share serial ports over the remote desktop connection.
IDKnown Issue
506610

NI-VNA measurements are incorrect after loading multiple CHX files using the niVNA Load Calibration And Configuration Data From File VI or the niVNA_LoadCalibrationAndConfigurationDataFromFile function.
After loading multiple CHX files using the niVNA Load Calibration and Configuration Data From File VI or the niVNA_LoadCalibrationAndConfigurationDataFromFile function, the returned measurement data is incorrect. Reversing the order that you load the CHX files in gives the correct data.

Workaround: To avoid incorrect measurement data when you load multiple CHX files, complete one of the following tasks:

  • Reset the device using either the niVNA Reset VI or the niVNA_reset function before loading the CHX files
  • Load the CHX file twice before taking a measurement.
Reported Version: 14.0  Resolved Version: 15.0  Added: 12/02/2014
319170

NI-VNA does not recall setup/calibration files from previous NI-VNA versions in Windows XP.
The NI-VNA Soft Front Panel reports, "Error in Recalling file. Exception has been thrown by the target of an invocation." when recalling the .chx file. The API shows the error "Unknown Exception" when performing the load calibration.

Workaround: Perform the following steps as a workaround.

  1. View the KB960442 known issue from Microsoft: http://support.microsoft.com/kb/960442.
  2. Install the latest service pack updates for .NET Framework 2.0 and 3.5 from Microsoft.
  3. Install the Microsoft Hotfix KB981574 (referenced by KB960442).

Reported Version: 1.1  Resolved Version: 1.1  Added: 10/24/2011
433386Performing a 2 port adapter removal calibration with the AutoCal module in the NI-VNA Soft Front Panel (SFP) results in unexpected 90 degree phase discontinuities.
Performing a 2 port adapter removal calibration with the AutoCal module in the NI-VNA SFP results in unexpected 90 degree phase discontinuities in subsequent measurements.

Workaround: Complete the following steps to workaround this issue:

  1. Perform an AutoCal in the NI-VNA SFP with the port adapter connected to Port1 on the device.
  2. Save a .chx file with the correction data from step 1.
  3. Flip the AutoCal module and perform another AutoCal in the NI-VNA SFP with the port adapter connected to Port2 on the device.
  4. Save a .chx file with the correction data from step 3.
  5. In the NI-VNA SFP navigate to Calibration>>Cal Options>>Perform Manual Adapter Removal.
  6. Load the two .chx files that you saved in steps 2 and 4 and follow the instructions in the dialog box. Set the estimated adapter length in ps.
  7. Click Perform Adapter Removal.

Reported Version: 2.0.1  Resolved Version: N/A  Added: 9/15/2014
496962NI-VNA occasionally fails to export End of Step and End of Sweep events to the PXI_TRIG lines.
NI-VNA occasionally fails to export End of Step and End of Sweep events to the PXI_TRIG lines despite these events being configured to export. This is a rare occurrence, but when it does happen, all exported edges fail to be sent.

Workaround: Repeat the sweep. If the End of Step or End of Sweep events are configured to export, they will likely be correctly exported the next sweep.

Reported Version: 14.0  Resolved Version: N/A  Added: 10/07/2014
385294The NI PXIe-8133 Controller hangs when using BIOS (basic input/output system) 1.2.0f6 with the NI PXIe-5630.
The NI PXIe-8133 Controller may hang causing the keyboard, mouse, and monitor display to become unresponsive when you configure the BIOS 1.2.0f6 with the PCI Express payload size set to AUTO in the BIOS setup and install the NI PXIe-5630 in the chassis.

Workaround: Visit ni.com/kb and search for 667FGM0S for more information about working around this issue.

Reported Version: 2.0.1  Resolved Version: N/A  Added: 1/15/2013
200090The NI-VNA Soft Front Panel cannot load when using Remote Desktop on Windows XP.
The NI-VNA Soft Front Panel does not load in a remote desktop environment on Windows XP. The splash screen shows "Application Initialization Failed!" This error only occurs when the NI-VNA Soft Front Panel is running on Windows XP. Remote Desktop works successfully on Windows Vista and Windows 7. You can use any supported OS on the client; you will only see this problem if you use Windows XP as the server (the system with the hardware) operating system.

Workaround: Install Windows Vista or Windows 7 on the NI-VNA system.

Reported Version: 1.0  Resolved Version: N/A  Added: 10/25/2010
494957NI-VNA cannot export the Ready for Start event.
NI-VNA cannot export the Ready for Start event. If you try to export the Ready for Start event, NI-VNA will return an error.

Workaround: There is no workaround for this issue.

Reported Version: 14.0  Resolved Version: N/A  Added: 10/07/2014
460163NI-VNA Soft Front Panel does not reserve PXI_TRIG lines.
The NI-VNA Soft Front Panel does not programmatically reserve PXI_TRIG lines. You can export events to PXI_TRIG lines for synchronization; however, it is possible to double-drive a PXI_TRIG line if care is not taken.

Workaround: Manually reserve and unreserve the PXI_TRIG lines using NI MAX.

Reported Version: 2.0.3  Resolved Version: N/A  Added: 9/23/2014
453927The NI PXIe-5632 sends a spurious pulse on any active PXI_TRIG line when you configure it for a Rising Edge or Active High Level output event in the NI-VNA Soft Front Panel.
When you configure the PXIe-5632 to use a Rising Edge or Active High Level output event for single sweep and hold measurements using the NI-VNA Soft Front Panel (SFP), the device sends a single spurious pulse on the configured PXI_TRIG line at the beginning of each sweep.

Workaround: To avoid all spurious pulses on the PXI_TRIG lines, configure any output events to be Falling Edge or Active Low Level.

Reported Version: 2.0.3  Resolved Version: N/A  Added: 9/15/2014
492581NI-VNA does not support IVI interchangeability checking or coercion recording.
NI-VNA does not implement interchangeability checking or coercion recording. These features are optional features of IVI drivers. If you set the NIVNA_ATTR_INTERCHANGE_CHECK attribute or the NIVNA_ATTR_RECORD_COERCIONS attribute to VI_TRUE, NI-VNA should return an error, but does not.

Workaround: There is no workaround for this issue.

Reported Version: 14.0  Resolved Version: N/A  Added: 9/15/2014
250239Users can receive a misleading error message when loading an AutoCal characterization file.
The NI-VNA instrument driver and Soft Front Panel return a misleading error message if you attempt to load the AutoCal characterization file either without having the AutoCal module connected or if the file is read-only on your system. If you call the niVNA Load AutoCal Characterization Data From File VI or function with no AutoCal module connected or if the file has been set to read-only, the VI or function fails with a "File not found" error. In the Soft Front Panel, the error returned is "Failed to read. You might have a corrupted file." The error should instead indicate that no AutoCal box was found, or the file is read-only.

Workaround: Connect AutoCal box before calling this VI or function. Change the AutoCal characterization file to not be read-only.

Reported Version: 1.0  Resolved Version: N/A  Added: 10/25/2010
451229The NI PXIe-5632 continues to drive PXI_TRIG lines after you close the NI-VNA Soft Front Panel.
The NI PXIe-5632 fails to release PXI_TRIG lines after you close the NI-VNA Soft Front Panel (SFP). If you configured PXI_TRIG lines in the NI-VNA SFP, they will remain driven in the state in which they were last used. As a result, if another device attempts to use the PXI_TRIG lines afterward, the lines may be double driven and damage may occur.

Workaround: To avoid double driving the PXI_TRIG lines after using them in the NI-VNA SFP, complete one of the following tasks:
  • If you are using output events, set the output events to Do Not Export and perform at least one sweep before closing the NI-VNA SFP.
  • If you are using triggers, set the trigger source to Internal and perform at least one sweep before closing the NI-VNA SFP.

Reported Version: 2.0.3  Resolved Version: N/A  Added: 9/15/2014
245461The NI-VNA Soft Front Panel consumes all the video memory.
The NI-VNA Soft Front Panel can use up the available video memory, resulting in it either loading with all traces blank or closing with an error. This situation typically happens with multiple VNAs in the system and happens intermittently.

Workaround: Close NI-VNA Soft Front Panel and reopen it.

Reported Version: 1.0  Resolved Version: N/A  Added: 10/25/2010
451230The NI PXIe-5632 sends spurious pulses on previously used PXI_TRIG lines when the NI-VNA Soft Front Panel is closed.
The NI PXIe-5632 fails to release PXI_TRIG lines after you close the NI-VNA Soft Front Panel (SFP). If you configured PXI_TRIG lines in the NI-VNA SFP, there may be some spurious signals on these lines when you close the NI-VNA SFP.

Workaround: To avoid spurious signals on the PXI_TRIG lines after using them in the NI-VNA SFP, complete one of the following tasks:
  • If you are using output events, set the output events to Do Not Export and perform at least one sweep before closing the NI-VNA SFP.
  • If you are using triggers, set the trigger source to Internal and perform at least one sweep before closing the NI-VNA SFP.

Reported Version: 2.0.3  Resolved Version: N/A  Added: 9/15/2014
408875Launching the NI-VNA Soft Front Panel fails when using the NI RMC-8354.
When launching the NI-VNA Soft Front Panel (SFP) on the NI RMC-8354 rack-mount controller, the NI-VNA SFP fails to launch.

Workaround: Use NI-VNA examples through the LabVIEW application programming interface.

Reported Version: 1.0  Resolved Version: N/A  Added: 5/20/2013
246949NI-VNA returns "Device in Use" error when device is unavailable.
If you use NI-VNA to open a session to a device that has recently been powered off or disconnected, the Initialize VI or function returns a "Device in Use" error instead of a "Invalid Device" error.

Workaround: Open a session to a valid device.

Reported Version: 1.0  Resolved Version: N/A  Added: 10/25/2010
456886NI-VNA does not calibrate with the AutoCal over a remote desktop connection when you share serial ports over the remote desktop connection.
Executing the AutoCal calibration over a remote desktop connection results in an error caused by sharing serial ports over the remote desktop connection.

Workaround: You can disable sharing serial ports by selecting Show Options in the Remote Desktop Connection window, and then navigate to the Local Resources tab and select More... under the Local Devices and resources section. Clear the Ports checkbox in the window that appears.

Reported Version: 2.0.3  Resolved Version: N/A  Added: 9/15/2014

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.

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