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.
| |||||
378277 |
In Spectrum acquisition mode, there is no magnitude only equalization performed when doing in-band retuning. Workaround: N/A
| |||||
343973 |
Specifying a non-zero external gain for the External Gain property or NIRFSA_ATTR_EXTERNAL_GAIN attribute with the Input Isolation Enabled property set to Enabled or the NIRFSA_ATTR_INPUT_ISOLATION attribute set to NIRFSA_VAL_ENABLED causes the driver to return incorrect amplitude parameters. Workaround: To obtain the actual values of the downconverter gain, fetched IQ, and spectrum data, subtract the external gain from the data returned by the driver.
| |||||
343973 |
Specifying a non-zero external gain for the External Gain property or NIRFSA_ATTR_EXTERNAL_GAIN attribute with the Input Isolation Enabled property set to Enabled or the NIRFSA_ATTR_INPUT_ISOLATION attribute set to NIRFSA_VAL_ENABLED causes the driver to return incorrect amplitude parameters. Workaround: To obtain the actual values of the downconverter gain, fetched IQ, and spectrum data, subtract the external gain from the data returned by the driver.
| |||||
325036 |
Reference Clock cannot be exported on the Ref Out terminal on the NI PXIe-5663E. The LO returned the following error: Requested value is not a supported value for this property. Property: NIRFSG_ATTR_EXPORTED_REF_CLOCK_OUTPUT_TERMINAL Workaround: Export the Reference clock to another terminal or downgrade your version of NI-RFSA to NI-RFSA 2.4.2.
| |||||
312899 |
Handle leaks can occur when using Spectral Measurements Toolkit 2.6.1 or Modulation Toolkit 4.3.1 and earlier with the NI-5660 API. Manual Change Option:
Note: You must make this change for each installed location and version of LabVIEW on the disk where the Spectral Measurements Toolkit and/or the Modulation Toolkit are installed. Upgrade option: Install a newer version of the Spectral Measurements Toolkit or of the Modulation Toolkit.
| |||||
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.
| |||||
350338 | In the device documentation, including the Getting Started Guide and Help file, the MAX "Configure" button is inaccurately labeled with its former name, "Properties." Workaround: When the documentation instructs you to select the "Properties" button, you should select the "Configure" button.
| |||||
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.
|
ID | Known Issue | |||||
---|---|---|---|---|---|---|
356088 |
Mismatch between the analyzed range and visual indication on the UI when you set the Delay for an IQ power edge trigger to a non-zero value. Workaround: Set the Measurement Method to Above Threshold Level or set the trigger delay to zero.
| |||||
347833 |
In SEM, the Soft Front Panel sometimes disables the IQ Power Edge softkey when it shouldn't. Workaround: Turn the SEM measurement off by clicking the Meas»All Meas Off softkeys. Set your span to the same value as the span used in SEM. Turn SEM back on to enable the IQ Power Edge softkey.
| |||||
346699 |
In Zero Span with a marker enabled, if you change acquisition time, the keypad cannot change the marker position. Workaround: Use the arrow keys or knob to enter a new zero span marker position. After using the arrow keys or knob to change the marker position, the keypad can be used.
| |||||
346134 |
In CCDF, you cannot set the delta marker to a trace different from the reference marker. Workaround: Set two markers to normal mode and manually calculate the difference using the reported values in the marker table.
| |||||
346518 |
A delay occurs if you use the mouse to move a marker when there are many points on the graph. Workaround: Change the marker position by entering a new marker value using the keypad instead of the mouse or arrow keys.
| |||||
345649 |
When you recall a configuration with RF Coupling set to DC, the SFP does not display a warning when it should.
Workaround: For condition 1, toggle the RF Coupling to AC and then back to DC after loading the file and the warning will appear. For condition 2, toggle the Start frequency to another value and then back after loading the file and the warning will appear.
| |||||
345782 |
In SEM, the SFP does not coerce the Integration BW when you set the Span of the Ref Channel to a value less than the Integration BW. Workaround: Set the Integration BW value to a value less than or equal to the Span value.
| |||||
349655 |
RBW and Step Frequency can be set lower than the minimum limit in SEM measurement. Workaround: N/A
| |||||
379030 |
The offset value displayed by the Select Offset button is incorrect in certain cases. Workaround: Use the value that you specify in the Select Offset button for editing and viewing the configurations. Ignore the value displayed in the Select Offset button.
|
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.