Archived: NI-RFSG 1.7 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.

Überblick



This document contains the NI-RFSG 1.7 known issues that were discovered before and since the release of NI-RFSG 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 by Severity

 

ID Known Issue
314690

Error returns when calibrating an NI PXI-5650/5651/5652

When performing an external calibration at high power levels, calling the niRFSG 5652 Adjust ALC Calibration VI can return the following error:

Please check the amplitude accuracy of your measurement instrument. Polynomial curve fit rejected LSB off by: x

Even when calibration is accurate, the VI can return this error during external calibration of a NI PXI-5650/5651/5652.

Workaround: N/A
Reported Version: Unknown    Resolved Version: N/A    Added: 11/1/2011
314690

Error returns when using some modular instruments on a real-time system with LabVIEW RT 8.6.1

An error occurs when using some modular instruments on a real-time system with LabVIEW RT 8.6.1. A self-test, self-calibration, or device reset from Measurement & Automation Explorer (MAX) results in the following error:

Error –50251:The specified component is not available. The component was not loaded.
The following additional related errors may occur:
Deploying a VI using my device results in the following error:
LabVIEW: Failed to load shared library niFgen_*.*.
Connecting a monitor to the real time controller results in the following error:
Error loading ivi_support_c.dll.


Workaround: Visit ni.com/kb and search for 5PJF6E77 for information about how to work around this error.
Reported Version: Unknown    Resolved Version: 1.8    Added: 10/24/2011
240669 Dynamic wires do not work with peer-to-peer VIs in NI LabVIEW FPGA 2010

Using dynamic FPGA interfaces (also known as dynamic mode) in the LabVIEW FPGA Module is not supported when using peer-to-peer streaming. Dynamic mode is enabled by default in the LabVIEW FPGA Module 2010.

Workaround: To disable Dynamic mode, complete the following steps: 
  1. Place the Open FPGA VI Reference Function on the LabVIEW block diagram.
  2. Right-click the VI and select Configure Open FPGA VI Reference.
  3. Remove the checkmark from the Dynamic mode listbox.
Reported Version: 1.7    Resolved Version: N/A    Added: 08/03/2010
242645 Incorrect error reporting behavior

LabVIEW FPGA 2010 corrupts error reporting for NI-RFSG, and you may receive the following error message:
Error information resources required by the driver could not be found on your system.  Reinstall the driver or contact National Instruments Technical support.

Workaround: Visit ni.com/kb and search for 5C1CGPJD for more information about how to correct error reporting behavior.

Reported Version: 1.7    Resolved Version: N/A    Added: 08/03/2010
258290
A protocol violation error occurs when using an NI PXIe-1075 chassis

When routing triggers across segments on the NI PXIe-1075 chassis, a protocol violation error may return. The NI PXIe-1075 has three bus segments: slots 1 through 6, slots 7 through 12, and slots 13 through 18. If the devices are located in different segments, you may run into this issue.  Some features, such as RF list mode or NI-TClk when used for synchronization or MIMO applications, internally route triggers. 

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

Reported Version: 1.6    Resolved Version: N/A    Added: 11/24/2010
275819
Running a 64-bit application incorrectly errors out

Due to a bug in third-party dependencies, 64-bit applications can incorrectly return an error, usually during the first run of the application.

Workaround: Perform either of the following options as a workaround.
  • Call the niRFSG Commit VI or niRFSG_Commit function immediately after calling the niRFSG Initialize VI or niRFSG_Initialize function.
  • Call the niRFSG Commit VI or niRFSG_Commit function or niRFSG Initiate VI or niRFSG_Initiate function again after ignoring the incorrect error from the first niRFSG Commit VI or niRFSG_Commit function or niRFSG Initiate VI or niRFSG_Initiate function.
Reported Version: 1.7    Resolved Version: 1.8    Added: 11/24/2010
214278 VIInt64 attributes not working on LabWindows/CVI

VIInt64 attributes do not work on LabWindows/CVI 8.0 or earlier if versions of LabWindows/CVI 8.1 or later are installed prior to installing NI-RFSG.

Workaround: Navigate to C:\Program Files\National Instruments\CVI80\include and replace visatype.h with visatype.h from C:\Program Files\National Instruments\CVI81\include or C:\Program Files\National Instruments\Shared\CVI\Include.

Reported Version: 1.7    Resolved Version: N/A    Added: 08/03/2010
215385 Error when running NI-RFSG examples in LabWindows/CVI

If you run NI-RFSG examples in LabWindows/CVI 8.0.x or 8.1.x and you have newer versions of LabWindows/CVI installed, you receive an error message that the niModInstCustCtrl.fp cannot be found.

Workaround: Visit ni.com/kb and search for 4U1BQJ5F for more information about how to locate the missing files.

Reported Version: 1.7    Resolved Version: N/A    Added: 08/03/2010
248901

File corruption if installing on a system with NI-DAQmx 7.0 or 7.1

Installing NI-RFSG on a system with NI-DAQmx 7.0 or 7.1 previously installed corrupts some files during installation.

Workaround: 

  1. Install NI-RFSG.
  2. When prompted, restart your computer.
  3. Launch the Control Panel by selecting Start»Control Panel.
  4. Double-click Add or Remove Programs.
  5. Select National Instruments Software.
  6. Click Change/Remove.
  7. Select your version of NI-FGEN from the dialog box that appears.
  8. Click Repair.
Reported Version: 1.7    Resolved Version: N/A    Added: 08/03/2010
232478 Devices that do not support self-calibration show the option to self-calibrate in Measurement & Automation Explorer (MAX)

The NI PXIe-5611 and NI PXI/PXIe-5650/5651/5652 devices do not support self-calibration, but the option to self-calibrate the devices appears in MAX.

Workaround: N/A

Reported Version: 1.7    Resolved Version: 1.8    Added: 08/03/2010
192893 Table of contents not locating

When linking to a topic in the NI RF Signal Generators Help from the LabVIEW context help or opening the help file from a VI within LabVIEW, the NI RF Signal Generators Help launches and the relevant topic displays, but the location of the topic might not be highlighted in the table of contents.

Workaround: N/A

Reported Version: 1.6    Resolved Version: N/A    Added: 08/03/2010
238196 Warning about active content

Microsoft Windows security feature that asks users whether or not to allow active content on their computer when launching certain pages from the driver media.

Workaround: Select Yes when the active content warning appears.

Reported Version: 1.7    Resolved Version: N/A    Added: 08/26/2011
109764 Measurement & Automation Explorer test panel does not work when running the NI PXIe-5673/5673E

Ruunning the test panel in Measurement & Automation Explorer (MAX) on the NI 5673/5673E when it is on an real-time system results in the following error: DAQmx Error -200170 occurred: Measurements: Physical channel specified does not exist on this device.

Workaround: N/A

Reported Version: 1.4    Resolved Version: N/A    Added: 09/01/2011
150413

Signal generates at the NI PXIe-5450 CLK OUT connector when Reference clock export is disabled

First setting the Reference Clock Export Output property to Clkout or NIRFSG_ATTR_REF_CLOCK_EXPORT_OUTPUT attribute to NIRFSG_VAL_REF_OUT_STR and then changing the Reference Clock Export Output property to Do Not Export Signal or NIRFSG_ATTR_REF_CLOCK_EXPORT_OUTPUT attribute to NIRFSG_ATTR_DO_NOT_EXPORT_STR still causes a signal to generate on the CLK OUT front panel connector.

Workaround: N/A

Reported Version: 1.4    Resolved Version: N/A    Added: 09/01/2011
248779

NI PXIe-5650/5651/5652 takes 10 ms to hit target power level when switching to the divide by 16 path

When switching to the divide by 16 path (any frequency between 100 MHz to 200 MHz) on the NI PXIe-5650/5651/5652, the output power behaves oddly. If you target 0 dBm on the device, the power starts off at approximately -25 dBm, but then overshoots to 10 dBm until it finally settles at approximately 0 dBm.

Workaround: N/A

Reported Version: 1.7    Resolved Version: N/A    Added: 09/01/2011
314607

A simulated NI PXI-5610 fails self-testing in Measurement & Automation Explorer

Running self-test on a simulated NI PXI-5610 in the Measurement & Automation Explorer (MAX) causes the following error:

Error -200437 occurred at Self-Test. Possible Reason(s): External calibration constants are invalid.

Workaround: N/A

Reported Version: 1.8    Resolved Version: N/A    Added: 09/01/2011
316551

Building LabVIEW with NI-RFSG fails

When building an installer using LabVIEW with NI-RFSG included as part of the installation, the installer build fails and returns the following error:

The system cannot find the path specified.  

When Microsoft Driver Framework (MDF) attempts to access NI-RFSG from the second volume of the stand-alone distribution, there is no setup.ini file located.  MDF then searches the registry for the relative path between the root of the distribution and the Microsoft Installer Package (MSI). The problem is that the MDF does not verify that the source of the relative path is from the same distribution as the source of the root path (only that they are the same product version). It uses the first distribution it locates (alphanumerically) to get the relative path.

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

Reported Version: 1.4    Resolved Version: N/A    Added: 09/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).