Each issue appears as a row in the table and includes the following fields:
| ID | Known Issue |
|---|
| 480524 | Upgrading Windows 8.0 to Windows 8.1. Upgrading the version of Windows on a system with this driver installed may result in the loss of device names, the loss of device configuration, and/or devices appearing disconnected. For more information about how to resolve this issue, visit ni.com/info and enter the Info Code 'excrxm'. Workaround: N/A
| |||||
| 499650 | Documentation omits DC coupling value for NI 5668R channel coupling. The NI 5668R supports both AC coupling and DC coupling as valid values for channel coupling. The documentation incorrectly lists only DC coupling. Workaround: N/A
| |||||
| 391719 | VST devices are not included in the support devices list when the Supported Instrument Models property or the NIRFSA_ATTR_SUPPORTED_INSTRUMENT_MODELS attribute are called. VST devices are not included in the support devices list when the Supported Instrument Models property or the NIRFSA_ATTR_SUPPORTED_INSTRUMENT_MODELS attribute are called. Workaround: Refer to the NI RF Vector Signal Analyzers Help to find out how to receive a list of supported devices.
| |||||
| 583240 | Calling the niRFSA_ReadPowerSpectrumF32 function returns a function not supported error. Support for single precision spectrum has not been added. Workaround: Use the niRFSA_ReadPowerSpectrum function.
| |||||
| 564383 | Missing documentation on reference level and mechanical attenuation limits when using the NI 5668R with NI 5698. The NI RF Vector Signal Analyzers Help should include the following information:
| |||||
| 411948 | Error –373104 occurs when a hyphen character is used in a configuration list name. When creating a configuration list in NI-RFSA or NI-RFSG on a VST target, using hyphens in the configuration list name results in error -373104: The specified configuration list name is invalid. Workaround: Avoid using hyphens in configuration list names.
| |||||
| 455741 | Multi-Record Fetch in program using "localhost/DeviceName" and SFP Session Access Utility returns a connection error. If you are using the SFP Session Access Utility and initializing a session with "localhost/DeviceName" in a program, if the program is performing a multi-record fetch, the first call to perform Multi-Record Fetch returns with the following error: Error -1074097835 occurred at niRFSA Fetch IQ (1D Complex WDT NRec 1Chan).vi. Possible reason(s): A connection error has occurred. Ensure that the device session is still open with session access enabled. On subsequent runs, the error does not occur. Workaround: Re-run the program that uses "localhost/DeviceName"
| |||||
| 501287 | NI 5668R Calibration VIs are included in the NI 5665 Calibration Control palette. In LabVIEW, the NI 5668R Calibration VIs do not have a separate palette and are included under the NI 5665 Calibration Control palette. Workaround: N/A
| |||||
| 383089 | NI-RFSA may cause deadlocks on Phar Lap ETS 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 ETS system, the NI-RFSA instrument driver can cause the OS to deadlock. The system must 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 wire the error out parameter from the niRFSA Close VI into the error in terminal of the niRFSA Initialize VI.
| |||||
| 376981 | MAX collapses the Vector Signal Analyzer (VSA) device sub-tree after associating the downconverter with other modules. MAX shows 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 to create a working VSA, MAX collapses the device sub-tree. Workaround: Manually expand the device sub-tree to see the modules that make up the VSA.
| |||||
| 474077 | MAX allows RIO and DAQmx-based devices to have the same aliases. In MAX, you can assign the same alias to a RIO-based device and a DAQmx-based device. For devices that are supported using NI-RFSA, the NI-RFSA instrument driver reports a problem but MAX does not. Workaround: Give unique aliases (or leave as default) to all devices that work with NI-RFSA.
| |||||
| 559585 | Trigger routes may not get reset on the NI 5688R. Calling the nirfsa_ExportSignal function or niRFSA Export Signal VI on trigger signals in order to change the terminal to PFI or PXI trigger lines may not take effect. Workaround: Call the niRFSA Export Signal VI or the nirfsa_ExportSignal function on the route to be reset and set the output terminal parameter to Do not export signal or NIRFSA_VAL_DO_NOT_EXPORT_STR.
| |||||
| 498763 | Configuring a small number of samples value with a large number of records value causes an overflow error. An error occurs when trying to configure NI-RFSA for a small number of samples value with a large number of records value. Higher I/Q rates accentuate the issue. Workaround: Increase the numberOfSamples value, lower the I/Q rate, or decrease the numberOfRecords value.
| |||||
| 499332 | Importing and exporting two signals on the same digital trigger line does not cause an error, depending on configuration order. The system sometimes does not display an error when a digital line is configured to export a signal and the same digital line is configured to import a signal on the same device. This action should always result in an error. Workaround: Avoid importing/exporting signals on the same digital trigger line. Use logical routes using arbitrary/implicit digital lines so that routing is done automatically on separate digital lines.
| |||||
| 562221 | Small memory leak when using the NI 5668R with the NI 5698. Calling the niRFSA_Init function followed by the niRFSA_close function leaks about 150 bytes per iteration. Workaround: Close the process to recapture the memory.
| |||||
| 494142 | Configuration related warnings do not persist. Using the Same configuration, NI-RFSA may not return a configuration warning after the first instance of calling the niRFSA_Commit or niRFSA_Initiate function on subsequent calls. Workaround: Ensure all API calls are properly status chained in C and the error wire is properly propagated in LabVIEW.
| |||||
| 391305 | When the Number of Records is Finite propertry or the NIRFSA_ATTR_NUMBER_OF_RECORDS_IS_FINITE attribute is set to false and the Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute is set to enabled, querying a property, an attribute or calling a commit takes a long time. When the Number of Records is Finite property or the NIRFSA_ATTR_NUMBER_OF_RECORDS_IS_FINITE attribute is set to FALSE and the Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute is set to enabled then calling niRFSAGetAttribute methods, reading an NI-RFSA property in LabVIEW, calling the niRFSA Commit VI or the niRFSA_commit function takes a long time before returning an error. The same behavior above is observed when the Allow More Records Than Memory property or the NIRFSA_ATTR_ALLOW_MORE_RECORDS_THAN_MEMORY attribute is set to TRUE instead of setting the Number of Records is Finite propertry or the NIRFSA_ATTR_NUMBER_OF_RECORDS_IS_FINITE attribute to FALSE. Workaround: N/A
| |||||
| 499290 | The NI 5668R may require an NI-RFSA device reset if an application using the NI 5624R synchronization library terminates unexpectedly. If an application terminates while NI 5624R synchronization is in progress, any successive sessions opened to NI-RFSA may fail to properly measure its ADC pipeline delay. This could result in delayed measurement timeout when calling the niRFSA Commit VI or niRFSA_Commit function, as well as incorrect trigger alignment, both for internal and exported events. Workaround: Call the niRFSA Reset Device VI or niRFSA_ResetDevice function if continuing to use the same FPGA extensions bitfile. If using the default bitfile, no action is needed.
| |||||
| 346251 | Unsupported property or attribute error for the Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute in NI-RFSA Soft Front Panel or missing extended error information. When using the NI PXI-5661 through the NI-RFSA Soft Panel, invalid configurations may produce an error message that reports that the Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute is not supported. After the error condition is reported, the NI-RFSA Soft Front Panel acquisition stops. At this point, reset the value change that caused the error to another invalid setting and back to the original to receive the correct error message. Correcting the invalid setting allows the acquisition to continue. Workaround: When using the NI-RFSA Soft Front Panel, revert the changes that caused the error and re-apply those same changes to get the correct error message. For LabVIEW and C clients of NI-RFSA, place the niRFSA Commit VI or the niRFSA_Commit function after configuration changes that come before a fetch. This causes the correct error report to be produced. For C NI-RFSA clients, calls to niRFSA_GetError after a fetch call may still report an unsupported attribute error when the return code from fetch is VI_SUCCESS.
| |||||
| 344383 | 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 >0 dBm and does not set the Mixer Level property or the NIRFSA_ATTR_MIXER_LEVEL attribute, NI-RFSA reports an error. Workaround: Set the Mixer Level property or the NIRFSA_ATTR_MIXER_LEVEL attribute to its default -20 dBm value.
| |||||
| 497298 | Two NI 5606 devices appear in MAX when only one is present. Two NI 5606 devices appear in MAX. One of the devices contains only VISA information, and the other is a module in the NI 5668R composite device. Both devices display the following error message: "The device name is not unique within the system". Workaround: Perform either of the following options as a workaround.
| |||||
| 469772 | Documentation incorrectly lists IF Filter Bandwidth as supported on NI 5601 and NI 5663 devices. IF Filter Bandwidth is not supported on NI 5601 or NI 5663 devices, but the documentation states that it is. Setting this attribute or querying it for NI 5601 or NI 5663 devices results in an attribute not supported error. Workaround: N/A
| |||||
| 365669 | 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.
| |||||
| 499100 | The digitizer FPGA for the NI PXIe-5668R goes into an unrecoverable state if the clock sent to the digitizer (NI PXIe-5624R) is lost. If the clock signal connected to CLK IN on the NI PXIe-5624R, as part of the NI PXIe-5668R system, is lost after the session is initialized, the system reports an error. Workaround: Call the niRFSA Reset VI or niRFSA_reset function, the niRFSA Reset Device VI or niRFSA_ResetDevice function, or the niRFSA Close VI or niRFSA_close function. Then call the niRFSA Initialize VI or niRFSA_init function to re-open the session.
| |||||
| 389317 | The niRFSA Self Calibrate Range VI execution time is greater than expected. In some instances, calling the niRFSA Self Calibrate Range VI or the niRFSA_SelfCalibrateRange function takes much longer than expected because of device settling, which can occur each time the device is reconfigured. When the VI or function executes, the RF IN and RF OUT connectors are configured twice. The connectors are configured once before and after execution where RF IN and RF OUT are reconfigured to their original states. Extended execution time is most noticeable when you repeatedly call the Self Calibrate Range VI or function for a single point, varying the frequency slightly for each call. Workaround: Perform either of the following options as a workaround.
| |||||
| 363009 | NI PXIe-5644R or NI PXIe-5645R device may occasionally appear outside the chassis in MAX when the device is installed for the first time. An NI PXIe-5644R or NI PXIe-5645R device may occasionally appear outside the chassis in MAX when the hardware/software is installed for the first time. The device should still function properly. Workaround: Restart the machine to get the device to appear in MAX properly.
| |||||
| 400235 | The Test Panels for NI-RFSG devices fail to load from MAX under certain installation scenarios. Installing the NI-RFSA 2.7 Runtime or later after installing NI-RFSA 2.6 or earlier causes the Test Panels for NI-RFSG devices to stop loading from MAX. Workaround: Perform a full install of NI-RFSA 2.7 or later when upgrading from NI-RFSA 2.6 or earlier.
| |||||
| 251423 | 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, the acquired data may 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, empirically determine the expected misalignment and correct the acquired data manually.
| |||||
| 370013 | 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 you call niRFSA Read IQ (Complex WDT 1Rec 1Chan) VI from LabVIEW, the waveform data displayed in NI I/O Trace is not correct. Workaround: N/A
| |||||
| 294969 | 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
| |||||
| 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: Change the location of the source and destination devices for the hardware route such that both of them lie in the same trigger bus. Since this error is intermittent, first retry the same route because it may succeed. In LabVIEW, you can retry by conditionally detecting error -26981, clearing the error, and attempting to reserve the same route again.
| |||||
| 258630 | 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.
| |||||
| 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. Refer to the corresponding article for more details. 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 signal from the power spectrum data through one of the following methods:
| |||||
| 502878 | Incorrect trigger delay occurs after an IF overload when using niRFSA Reset VI with NI 5668R devices. Calling niRFSA Reset VI after a digitizer overload (input power protection error) can cause an incorrect trigger delay after the next initialization. Triggers can be as early as 500 to 600 nanoseconds, causing data to appear to be delayed by the same amount of time. Workaround: After a digitizer overload, do one of the following three things: Avoid calling niRFSA Reset VI, reset the NI 5606 downconverter in MAX, or call niRFSA Reset Device VI.
| |||||
| 389207 | Committing a configuration list with the Number of Records Is Finite property or the NIRFSA_ATTR_NUMBER_OF_RECORDS_IS_FINITE attribute set to false and the Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute set to enabled will freeze NI-RFSA. Committing a configuration list with the Number of Records Is Finite property or the NIRFSA_ATTR_NUMBER_OF_RECORDS_IS_FINITE attribute set to FALSE and the Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute set to enabled freezes NI-RFSA when calling niRFSAGetAttribute methods, reading an NI-RFSA property in LabVIEW, or calling the niRFSA Commit VI or the niRFSA_commit function. During the freeze, NI-RFSA is unresponsive and may return an internal error after an indeterminate amount of time. Workaround: Set the Number of Records Is Finite property or the NIRFSA_ATTR_NUMBER_OF_RECORDS_IS_FINITE attribute to TRUE. The Contiguous Multirecord property or the NIRFSA_ATTR_CONTIGUOUS_MULTIRECORD attribute is not supported with the Number of Records Is Finite property or the NIRFSA_ATTR_NUMBER_OF_RECORDS_IS_FINITE attribute set to FALSE.
| |||||
| 456682 | Starting an acquisition without clearing the previous acquisition causes a data overflow error. The niRFSA Close VI does not automatically clear data. Acquiring data, then starting a second acquisition without explicitly clearing the data from the first acquisition, causes a data overflow error at the beginning of the second acquisition. Workaround: Add code to your test to clear any data left at the end of an acquisition.
| |||||
| 569554 | When using the NI 5668R, dither signal may interfere with I/Q power edge trigering. Dither signal may leak into I/Q data and cause the I/Q power edge to not trigger as expected. Workaround: Reduce the I/Q rate and change the IF filter. Refer to the Dither Signal Conditions table in the NI PXIe-5668R Device Specifications for more information.
| |||||
| 491993 | System returns error -1074118655 or the application hangs when calling the niRFSA Initialize VI or the niRFSA_init function. The system can return error -1074118655 or the application can hang (including NI-RFSA Soft Front Panel) when calling the niRFSA Initialize VI or the niRFSA_init function to initialize a session to the NI-RFSA device. This behavior occurs if you configure the system as follows:
| |||||
| 456000 | Installer built with LabVIEW Application Builder and NI-RFSA 2.7.5 fails. An installer build with LabVIEW Application Builder fails when NI-RFSA 2.7.5 Full is included. The system returns an error about "Missing NI-RFSA_SFP" dependency. Workaround: Include the NI-RFSA Full and Runtime as well as an NI-RFSA example in the installer.
| |||||
| 395826 | Scaling coefficients returned can differ by up to 1e-10. For a single record I/Q acquisition, scaling coefficients obtained from the niRFSA Get Scaling Coefficients VI or the niRFSA_GetScalingCoefficientstt> 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 multirecord I/Q 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 small, this difference does not affect amplitude accuracy for any NI-RFSA devices.
| |||||
| 412860 | When using synchronization examples on NI 5663/5663E devices, the examples display a PLL Lock error. When configuring the master and slave NI 5663 devices for the first time, the synchronization examples do not export the clocks correctly, resulting in a PLL lock error. Workaround: Run NI-RFSA Getting Started Spectrum or NI-RFSA Getting Started IQ example on the master device prior to using the synchronization examples. This workaround is required after a system restart or a reset device is called on the master NI 5663/5663E.
| |||||
| 456047 | The niRFSA Abort VI and the niRFSA Close VI can return DSP overflow warnings if a record acquisition is in progress and RF list mode is aborted on VST devices. Workaround: There are two workarounds for this issue:
| |||||
| 467770 | When using a vector signal transceiver device, changing the Reference Clock source from PXI_CLK to OnBoardClk requires a ten second delay for stability. When using a vector signal transceiver device (NI 5644R/5645R/5646R), changing the Reference Clock source from PXI_CLK to OnBoardClk requires the hardware to disable and then re-enable the onboard Reference Clock. Disabling and re-enabling the onboard Reference Clock is necessary to provide the PXIClk route enough isolation from the onboard clock. After being re-enabled, the clock requires ten seconds to reach stability. Workaround: N/A
|
| 457149 | The niRFSA Abort VI and the niRFSA Close VI can corrupt recorded acquisition data if a record acquisition is in progress and RF list mode is aborted on VST devices. Workaround: There are two workarounds for this issue:
| |||||
| 375859 | 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 produces an error reporting that the quiet time is invalid. This error persists 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.
|
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.