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.
This document contains the NI-VNA 1.2 known issues that were discovered before and since the release of NI-VNA 1.2. 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-VNA in which the issue was reported. If you discover the issue appears in an earlier version of NI-VNA 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).
NI-VNA does not support device rename in MAX.
You cannot rename the NI-VNA device in MAX using the standard method of right-clicking and selecting rename.
Workaround: You can create an IVI Logical name in MAX to use with the NI-VNA driver. To create an IVI logical name in MAX, follow the instructions in MAX under IVI drivers to create an NI-VNA logical driver session. You can rename the IVI logical name to whatever you want.
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.
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.
NI-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.
Users 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.
NI-VNA returns a nondescriptive error during some AutoCal operations.
If you perform an AutoCal without loading the AutoCal characterization file, the NI-VNA Soft Front Panel and NI-VNA instrument driver return an error message of "Other Error."
Workaround: Load the Autocal characterization data before performing AutoCal.
Saving a screen capture in NI-VNA Soft Front Panel results in an incorrect picture.
When saving a screen capture of the NI-VNA Soft Front Panel using File >> Save Data >> .bmp, the resulting picture is incorrect.
Workaround: Press <Alt - PrtScn> in the NI-VNA Soft Front Panel to place a screen shot on the Windows clipboard. Paste the clipboard image to your desired image editor, such as Microsoft Paint, and save the resulting file.
NI-VNA does not recall setup/calibration files from previous NI-VNA versions.
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.
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.
You probably noticed we have a new look, but our focus remains on you. We've expanded our offerings to better serve you so that you can take on the complex challenges facing humanity today, tomorrow, and for the next 100 years. It's time. Let's Engineer Ambitiously.