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.
Each issue appears as a row in the table and includes the following fields:
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 395826 |
Scaling coefficients returned can differ by up to 1e-10. Workaround: There is no workaround for this issue. However, since the difference in coefficients is rather small, this difference does not affect amplitude accuracy for any of the devices supported by NI-RFSA.
| |||||
| 336698 |
Calling niRFSA Self Cal VI or the niRFSA_SelfCalibrate function for the NI PXIe-5663E does not self-calibrate the associated digitizer. Use the niScope Cal Self Calibrate VI, or the niSCOPE_CalSelfCalibrate function, in the NI-SCOPE API or self-calibrate the NI PXIe-5622 through Measurement & Automation Explorer (MAX).
| |||||
| 378277 |
In Spectrum acquisition mode, there is no magnitude only equalization performed when doing in-band retuning. Workaround: N/A
| |||||
| 336698 |
Calling niRFSA Self Cal VI or the niRFSA_SelfCalibrate function for the NI PXIe-5663E does not self-calibrate the associated digitizer. Use the niScope Cal Self Calibrate VI, or the niSCOPE_CalSelfCalibrate function, in the NI-SCOPE API or self-calibrate the NI PXIe-5622 through Measurement & Automation Explorer (MAX).
| |||||
| 330425 |
EVM and MER measurements are degraded when using RF list mode. To avoid this issue, you can choose from one of the following options:
| |||||
| 305024 | NI-RFSA can falsely report temperature sensor errors for the NI PXIe-5603. There may be instances in which the temperature sensor on the NI PXIe-5603 incorrectly reports the temperature sensor state when using NI-RFSA 2.4. This error is caused by a temperature sensor data conversion time change that occurred after the device was released. Workaround: Upgrade to NI-RFSA 2.4.2 or later.
| |||||
| 305281 | NI PXIe-5603 devices calibrated with a later version of NI-RFSA do not initialize with NI-RFSA 2.4. Devices calibrated with later versions of NI-RFSA are incompatible with NI-RFSA 2.4. Devices calibrated with NI-RFSA 2.4 continue to function as expected. Workaround: Upgrade to NI-RFSA 2.4.2.
| |||||
| 304436 | Calling the NI-RFSA Commit VI or the niRFSA_Commit function before setting the attenuation-related properties results in incorrect gain scaling coefficients on the NI PXIe-5663, NI PXIe-56653E, and NI PXIe-5665. If you call the NI-RFSA Commit VI or the niRFSA_Commit function before setting any properties or attributes that control attenuation, like the Reference Level property or the NIRFSA_ATTR_REFERENCE_LEVEL attribute, the RF Attenuation property or the NIRFSA_ATTR_ATTENUATION attribute, and so on, and then call the niRFSA Get Scaling Coefficients VI or the niRFSA_GetScalingCoefficients function, the resulting coefficients are incorrect. Workaround: Call the NI-RFSA Commit VI or the niRFSA_Commit function after setting all attenuation related properties, then call the NI-RFSA Get Scaling Coefficients VI or the niRFSA_GetScalingCoefficients function to get the appropriate coefficients.
| |||||
| 301761 | Calling the NI-RFSA Reset Device VI or the niRFSA_ResetDevice function on the NI PXIe-5622 can cause a blue screen in some instances. Using NI-RFSA to self-calibrate the NI PXIe-5622 or resetting the RF vector signal analyzer session using the NI-RFSA Reset Device VI or the niRFSA_ResetDevice function on an NI PXIe-5663 or NI PXIe-5665 may result in a blue screen.
| |||||
| 297868 | Users may get an undefined warning with code 88000 while using the NI PXI-5600 and changing clocking configurations. Using NI-RFSA to set the Sample clock source on the NI PXI-5600 to ClkIn or PXI_STAR may cause an undefined warning with the code 88000. Workaround: To avoid this error, complete the following steps:
| |||||
| 296450 | The NI PXIe-5622 digitizer may incorrectly report a warning that the PLL came unlocked or may experience initial accuracy issues. When using the NI PXIe-5622 digitizer in a RF vector signal analyzer session with NI-RFSA, you may receive a warning that the PLL came unlocked or that the first measurements may have accuracy issues. This issue appears after a device reset or a clock configuration change. Workaround: Add a delay of at least 700 ms after a device reset or a clocking configuration change.
| |||||
| 288143 | The NI PXIe-5622 (25 MHz) digitizer in an RT setup does not appear under the chassis in MAX. The PXI Express device registration is missing for the chassis. This registration is required for the device to be assigned a slot number in MAX. The registration enables routing signals through the chassis backplane. The affected applications are NI-TClk, NI-RFSA List Mode, and any routing application using the chassis backplane. Workaround:
| |||||
| 287752 | Execution times with multiple NI-RFSA sessions is slower than expected. Test execution times with NI-RFSA device applications deteriorates significantly with every additional NI-RFSA session used. Performance degradation of up to 2x has been observed with an additional session. Workaround: Install IVI 4.4.0 or later.
| |||||
| 285185 | NI-RFSA, with NI-SCOPE, writes incorrect calibration values to the NI PXIe-5622 during external calibration. Performing an external calibration on an NI 5622 device with NI-SCOPE 3.7 software results in incorrect calibration values written to the device. The calibration procedure completes without any errors but the validation fails. Workaround: Perform external calibration on the NI 5622 using any other NI-SCOPE driver version other than NI-SCOPE 3.7.
| |||||
| 279084 | Calling the NI-DAQmx Reset VI after calling the NI-RFSA Commit VI may cause the NI PXI-5600 firmware to return an error. When using the niRFSA Commit VI, if you call the DAQmx Reset VI or reset the device in MAX, the NI PXI-5600 firmware may return an error. Workaround: Perform a reset device through MAX to return the device to the default state.
| |||||
| 275798 | The NI PXI-5600 may hang at cold temperatures at driver initialization or reset. When loading or resetting the NI PXI-5600 at cold temperatures, the FPGA may hang, causing the device to be unusable. Workaround: Contact National Instruments to get an updated firmware image with the fix.
| |||||
| 258323 | Routing signals across segment boundaries on the NI PXIe-1075 chassis can intermittently fail. The NI PXIe-1075 chassis backplane has the following three trigger buses (segments) that you can use to route digital signals:
Workaround: There are two possible workarounds for this issue:
| |||||
| 224755 | Low-power signals may appear at fixed intervals in power spectrum data. Low-power signals may appear at fixed intervals when performing a power spectrum acquisition. When performing an acquisition narrower than the hardware instantaneous bandwidth, the signals can appear in the lower frequency bins and upper frequency bins of the acquisition. When performing a multispan acquisition, the signals can appear at the boundary of each single span spectral acquisition that makes up the total acquisition. Workaround: The low-power signals represent the dither signal on the digitizer. Although the dither signal is at a frequency that is outside the bandwidth of the equalized response, the power of the dither signal can leak into the equalized response, depending on the resolution bandwidth and the FFT window type. You can remove the dither from the power spectrum data using one of the following methods:
| |||||
| 258630 | Using NI-RFSA with NI-TClk to synchronize multiple devices acquiring at different I/Q rates results in misaligned data. When using NI-TClk synchronization where two or more NI RF vector signal analyzers acquire at different I/Q rates, the acquired data might be misaligned. The misalignment manifests itself as a skew where the data from one device appears to be leading/lagging the data from the other device. The time delay between the data acquired by the master and a slave is constant for the combination of the hardware settings configured on the two devices. This skew is repeatable and does not vary with time. Workaround: Since the skew does not vary with time, you can empirically determine the expected misalignment and correct the acquired data manually.
| |||||
| 380936 | NI-RFSA computes an incorrect temperature corrected gain when the IF gain on the NI PXIe-5603 or the NI PXIe-5605 is nominal. It is possible for NI-RFSA to report an incorrect value for the Downconverter Gain property or the NIRFSA_ATTR_DOWNCONVERTER_GAIN attribute, the IF Output Power Level property or the NIRFSA_ATTR_IF_OUTPUT_POWER_LEVEL attribute, or return error -1074118655 when the IF gain on the NI PXIe-5603 or the NI PXIe-5605 is nominal. A nominal IF gain is chosen by NI-RFSA if there is no calibration data present in the device EEPROM for the attenuation configuration that is requested. The computed temperature corrected gain is incorrect only when the configuration requires NI-RFSA to choose a nominal IF gain. Workaround: Calibrate the requested gain configuration using the NI-RFSA external calibration API.
|
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.