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 | |||||
|---|---|---|---|---|---|---|
| 423734 Return | Magnitude equalization correction is not applied to the spectrum data correctly when the valid spectrum bandwidth is smaller than the acquired spectrum bandwidth. Workaround: N/A
| |||||
| 224755 Return | 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:
| |||||
| 394079 Return | NI 5601 revision E modules do not behave properly with NI-RFSA 2.6. NI 5601 revision E modules are not programmed properly with NI-RFSA 2.6. A common symptom of this issue is incorrect power levels being reported by the driver or observed when using the NI-RFSA Soft Front Panel. Additionally, the reported power levels may change after a reset is called from MAX or by calling the niRFSA Reset Device VI or the niRFSA_ResetDevice function. To find out the module revision of your NI 5601, query the Module Revision property or the NIRFSA_ATTR_MODULE_REVISION attribute. Workaround: Upgrade to NI-RFSA 2.7 or later or apply the NI-RFSA 2.6f1 patch.
| |||||
| 258630 Return | Using NI-RFSA with NI-TClk to synchronize multiple devices acquiring at different I/Q rates results in misaligned data. When using TClk synchronization where two or more NI RF vector signal anayzers acquire at different I/Q rates, it is possible for the acquired data to 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, users can empirically determine the expected misalignment and correct the acquired data manually.
| |||||
| 395826 Return | Scaling coefficients returned can differ by up to 1e-10. For a single record IQ acquisition scaling coefficients obtained from the niRFSA Get Scaling Coefficients VI or the niRFSA_GetScalingCoefficients function could be different from the scaling coefficients obtained from the niRFSA Fetch IQ (1D I16) VI or the niRFSA_FetchIQSingleRecordComplexI16 function. Similarly, for a multi-record IQ acquisition scaling coefficients obtained from the niRFSA Get Scaling Coefficients VI or the niRFSA_GetScalingCoefficients function could be different from the scaling coefficients obtained from the niRFSA Fetch IQ (2D I16) VI or the niRFSA_FetchIQMultiRecordComplexI16 function. The difference in the scaling coefficients can be 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.
| |||||
| 258323 Return | 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:
| |||||
| 375859 Return | Setting an IQ Power Edge Trigger with an invalid minimum quiet time on the NI PXI-5661 produces a persistent error. Setting an invalid minimum quiet time on the NI PXI-5661 will produce an error reporting that the quiet time is invalid. This error will persist even after setting the minimum quiet time to a valid value. Workaround: Use the niRFSA Reset VI or the niRFSA_reset function to restore all properties or attributes to their default values and re-apply the desired settings.
| |||||
| 346251 Return | Controlling the NI PXI-5661 through the NI-RFSA Soft Front Panel, you can potentially create an invalid configuration that produces an incorrect error message When controlling the NI PXI-5661 through the NI-RFSA Soft Panel, you can potentially create an invalid configuration that to produces an incorrect error message reporting that the Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute is not supported or an error without extended error information. After the error condition is reported, the NI-RFSA Soft Front Panel acquisition stops. Workaround: There are two possible workarounds for this issue:
| |||||
| 251423 Return | Using NI-RFSA with NI-TClk to synchronize the NI PXIe-5663E with the NI PXIe-5665 or the NI PXIe-5667 results in misaligned data. When using TClk synchronization with the NI PXIe-5663E and the NI PXIe-5665 or the NI PXIe-5667, it is possible for the acquired data to 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, users can empirically determine the expected misalignment and correct the acquired data manually.
| |||||
| 375643 Return | Changing from an IQ Power Edge Trigger to None on the NI PXI-5661 results in a persistent error from the digitizer. Applying an IQ Power Edge Trigger configuration on the NI PXI-5661 and then reconfiguring it by applying a configuration that does not use a trigger will produce a digitizer error indicating that the trigger source is invalid. Workaround: Use the niRFSA Reset VI or the niRFSA_reset function to restore all properties or attributes to their default values and re-apply the desired settings.
| |||||
| 370013 Return | NI I/O Trace log shows incorrect data for the waveform buffer when the niRFSA Read IQ (Complex WDT 1Rec 1Chan) VI is called from LabVIEW. When the niRFSA Read IQ (Complex WDT 1Rec 1Chan) VI is called from LabVIEW, the waveform data displayed in NI I/O Trace is not correct. Workaround: N/A
| |||||
| 344383 Return | Setting the Mixer Level Offset property or the NIRFSA_ATTR_MIXER_LEVEL_OFFSET attribute to 0 dBm and not setting the Mixer Level property or the NIRFSA_ATTR_MIXER_LEVEL attribute causes an error. If your application sets the Mixer Level Offset property or the NIRFSA_ATTR_MIXER_LEVEL_OFFSET attribute to a value of 0 dBm and does not set the Mixer Level property or the NIRFSA_ATTR_MIXER_LEVEL attribute the NI-RFSA driver will report an error. Workaround: Set the Mixer Level property or the NIRFSA_ATTR_MIXER_LEVEL attribute to its default -20 dBm value.
| |||||
| 383089 Return | NI-RFSA may cause deadlocks on Phar Lap when a new NI-RFSA session is initialized in parallel while closing a previously opened NI-RFSA session When the niRFSA Initialize VI and the niRFSA Close VI execute in parallel on a Phar Lap system, the NI-RFSA driver can cause the OS to deadlock. The system will have to be physically rebooted to be used again. Workaround: Sequence the niRFSA Initialize VI and the niRFSA Close VI so that they are not executed in parallel. One way to do this is to chain the error out that exits the niRFSA Close VI into the error in terminal of the niRFSA Initialize VI.
| |||||
| 365669 Return | MAX does not refresh the Composite Device information after the configuration for the downconverter is changed. After using the Configuration Panel to associate the downconverter with any other device, such as a digitizer or an LO, MAX should update the dowconverter or VSA device sub-tree. However, the device sub-tree doesn't update occasionally even if the configuration was modified successfully. Workaround: Refresh the device sub-tree manually or close MAX and open it again.
| |||||
| 376981 Return | MAX will collapse the Vector Signal Analyzer (VSA) device sub-tree after associating the downconverter with other modules. MAX will show a sub-tree for each VSA device, which lists the downconverter along with the other modules that make up the VSA (digitizer, LO, RF conditioning (if applicable) and IF conditioning (if applicable)). After associating the downconverter with the other devices in order to have a working VSA, MAX will collapse the device sub-tree. Workaround: Manually expand the device sub-tree in order to see the modules that make up the VSA.
| |||||
| 294969 Return | NI-TClk synchronization on a distributed chassis setup may show higher jitter than a single chassis setup When using NI-TClk synchronization on two or more NI-RFSA devices that are in separate chassis, it is possible for the run to run synchronization jitter to be higher than a single chassis setup Workaround: N/A
|
Refer to the NI-RFSA Soft Front Panel 2.6 Known Issues for known issues specific to NI-RFSA Soft Front Panel 2.6.
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.