NI-RFSA 15.0 and 15.0.2 Known Issues

Panoramica

This document contains the NI-RFSA 15.0 and 15.0.2 known issues that were discovered before and since the release of NI-RFSA 15.0.2. 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

480524 Upgrading Windows 8.0 to Windows 8.1
456000 Installer built with LabVIEW Application Builder and NI-RFSA 2.7.5 fails.
456682 Starting an acquisition without clearning the previous acquisition causes a data overflow error.
455741 Multi-Record Fetch in program using "localhost/DeviceName" and SFP Session Access Utility returns a connection error.
445202 Setting the clock setting to Clk In using the SFP causes an error.
549715 NI-RFSA does not account for mechanical attenuator settling time when using the NI 5668R.
224755 Low-power signals may appear at fixed intervals in power spectrum data.
258630 Using NI-RFSA with NI-TClk to synchronize multiple devices acquiring at different I/Q rates results in misaligned data.
395826 Scaling coefficients returned can differ by up to 1e-10
375859 Setting an IQ Power Edge Trigger with an invalid minimum quiet time on the NI PXI-5661 produces a persistent error.
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
258323 Routing signals across segment boundaries on the NI PXIe-1075 chassis can intermittently fail
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.
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.
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.
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.
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.
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.
376981 MAX collapses the Vector Signal Analyzer (VSA) device sub-tree after associating the downconverter with other modules.
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 take a long time.
294969 NI-TClk synchronization on a distributed chassis setup may show higher jitter than a single chassis setup.
400235 The Test Panels for NI-RFSG devices fail to load from MAX under certain installation scenarios.
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.
389317 The niRFSA Self Calibrate Range VI execution time is greater than expected.
364860 A deadlock can occur when creating two peer-to-peer streams between two devices in opposite directions concurrently.
411948 Error –373104 occurs when a hyphen character is used in a configuration list name.
491993 System returns error -1074118655 or the application hangs when calling the niRFSA Initialize VI or the niRFSA_init function.
498763 Configuring a small number of samples with a large number of records causes an overflow error.
499100 The digitizer FPGA for the NI PXIe-5668R goes into an unrecoverable state if the clock sent to the digitizer (PXIe-5624R) is lost.
499332 Importing and exporting two signals on the same digital trigger line does not cause an error, depending on configuration order.
499650 Documentation omits DC coupling value for NI 5668R channel coupling.
502878 Incorrect trigger delay occurs after an IF overload when using niRFSA Reset VI with NI 5668R devices.
365669 MAX does not refresh the Composite Device information after the configuration for the downconverter is changed
489122 NI 5652 appears outside of the composite device in MAX.
482160 When using synchronization examples on NI 5663/5663E devices, the examples display a PLL Lock error.
469772 Documentation incorrectly lists IF Filter Bandwidth as supported on NI 5601 and NI 5663 devices.
457149 NI 5668R Maximum Instantaneous Bandwidth exceeded error reports first limit violated.
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.
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.
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

Reported Version: 14.0    Resolved Version: N/A    Added: 07/08/2014
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.

Reported Version: 2.7    Resolved Version: 17.1    Added: 03/24/2014
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.

Reported Version: 2.9    Resolved Version: N/A    Added: 03/24/2014
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"

Reported Version: 2.9    Resolved Version: N/A    Added: 03/24/2014
445202
Setting the clock setting to Clk In using the SFP causes an error.
Opening the NI-RFSA SFP for a device and changing the clock setting to Clk In causes an LO error and PLL phase lock failure.

Workaround: N/A

Reported Version: 2.9    Resolved Version: N/A    Added: 03/24/2014
549715
NI-RFSA does not properly account for mechanical attenuator settling time when using the NI 5668R.
When the mechanical attenuator on the NI 5668R is changed or whenever the reference level is changed by greater than or equal to 5 dB, NI-RFSA does not wait long enough to account for the settling time. This may result in incorrect power measurements or poor EVM measurements.

Workaround: For the NI 5668R, when changing the mechanical attenuator or changing the reference level to >5 dB, instead of calling the niRFSA Initiate VI or niRFSA_Initiate function, call the niRFSA Commit VI or niRFSA_Commit function, wait for 30 ms, and then call the niRFSA Initiate VI or niRFSA_Initiate function.

Alternatively, lock the mechanical attenuator by setting the Mechanical Attenuation property or NIRFSA_ATTR_MECHANICAL_ATTENUATION attribute to the desired value.

Reported Version: 14.1    Resolved Version: N/A    Added: 10/14/2015
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:
  • Using a narrower resolution bandwidth.
  • Disabling the dither signal.
  • Choosing a different FFT window type. This solution may be less effective than the previous solutions, depending on the resolution bandwidth.

Reported Version: 2.3    Resolved Version: N/A    Added: 01/17/2011
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.

Reported Version: 2.3    Resolved Version: N/A    Added: 01/17/2011
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_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 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.

Reported Version: 2.4    Resolved Version: N/A    Added: 03/13/2013
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.

Reported Version: 2.3    Resolved Version: N/A    Added: 11/15/2012
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.

Reported Version: 2.5.5    Resolved Version: N/A    Added: 11/15/2012
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:
  • Trigger Bus 1: PXI Slots 1, 2, 3, 4, 5, and 6
  • Trigger Bus 2: PXI Slots 7, 8, 9, 10, 11, and 12
  • Trigger Bus 3: PXI Slots 13, 14, 15, 16, 17, and 18
Backplane signal route requests may sometimes fail if the source and destination devices lie in different segments of the chassis. In that scenario, error -26981 ("A protocol violation was detected.") is returned. This error is intermittent, and its frequency depends on the embedded controller or MXI interface device used in the chassis.

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.

Reported Version: 2.4    Resolved Version: N/A    Added: 01/17/2011
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.

Reported Version: 2.4    Resolved Version: N/A    Added: 12/05/2012
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.

Reported Version: 2.7    Resolved Version: N/A    Added: 03/28/2013
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

Reported Version: 2.6    Resolved Version: N/A    Added: 11/15/2012
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.

Reported Version: 2.4    Resolved Version: N/A    Added: 11/19/2012
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 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.

Reported Version: 2.6    Resolved Version: N/A    Added: 12/13/2012
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 set 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.

Reported Version: 2.6    Resolved Version: N/A    Added: 03/28/2013
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.

Reported Version: 2.6    Resolved Version: N/A    Added: 11/15/2012
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 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 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

Reported Version: 2.7    Resolved Version: N/A    Added: 03/28/2013
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

Reported Version: 2.5    Resolved Version: N/A    Added: 12/18/2012
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.

Reported Version: 2.7    Resolved Version: N/A    Added: 03/28/2013
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.

Reported Version: 2.7    Resolved Version: N/A    Added: 08/28/2012
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.
  • Call the niRFSA Self Calibrate Range VI or the niRFSA_SelfCalibrateRange function only once for the entire frequency range so that device settling is minimized.
  • Configure and commit the NI-RFSA session to the desired frequency prior to calling the niRFSA Self Calibrate Range VI or the niRFSA_SelfCalibrateRange function to minimize the call time.
Reported Version: 2.7    Resolved Version: N/A    Added: 02/18/2013
364860
A deadlock can occur when creating two peer-to-peer streams between two devices in opposite directions concurrently.

Workaround: To avoid the deadlock, serialize the calls to the niP2P Create Peer to Peer Stream VIs.

Reported Version: 2.7    Resolved Version: N/A    Added: 08/28/2012
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.

Reported Version: RFSA/G Support 1.1    Resolved Version: N/A    Added: 02/25/2014
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:
  1. NI-RFSA 14.1 or NI-SCOPE 14.1 are installed.
  2. Only the NI digitizer (NI PXI-5142 or NI PXIe-5622) is configured with Debug Session enabled and the "Using breakpoints in C/C++/.NET application" option is selected.
Workaround: When using Debug Session for NI-RFSA device, NI recommends disabling Debug Session for the associated NI-SCOPE device. Complete the following steps to disable Debug Session:
  1. Launch the NI-SCOPE Soft Front Panel.
  2. Select Utility>>Configure Debugging.
  3. Select the associated NI-Scope Device from the list, and set Debug Session to disabled.
  4. Click OK to save changes.
Note: You can still debug an NI-RFSA device using breakpoints in C/C++/.NET without the associated NI-SCOPE device Debug Session enabled. Refer to the NI-RFSA documentation for more information about configuring debugging for an NI-RFSA device.

Reported Version: 14.1    Resolved Version: N/A    Added: 11/03/2014
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.

Reported Version: 14.1    Resolved Version: N/A    Added: 11/03/2014
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 function or VI, the reset device function or VI, or the close function or VI. Then call the initialize function or VI to re-open the session.

Reported Version: 14.1    Resolved Version: N/A    Added: 11/03/2014
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.

Reported Version: 14.1    Resolved Version: N/A    Added: 11/03/2014
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

Reported Version: 14.1    Resolved Version: N/A    Added: 11/03/2014
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.

Reported Version: 14.1    Resolved Version: N/A    Added: 11/03/2014
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.

Reported Version: 14.1    Resolved Version: 17.1    Added: 11/03/2014
489122

NI 5652 appears outside of the composite device in MAX.
After configuring the associated devices for a composite device in MAX, you may see the NI 5652 represented outside of the composite device in the MAX configuration tree. This behavior has no functional implications. The composite device and the NI 5652 continue to function as usual.

Workaround: N/A

Reported Version: 14.1    Resolved Version: N/A    Added: 11/03/2014
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 RFSA Getting Started Spectrum or 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.

Reported Version: 14.1    Resolved Version: N/A    Added: 11/13/2014
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

Reported Version: 14.1    Resolved Version: N/A    Added: 11/13/2014
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:
  • Do not call the niRFSA Abort VI while a record acquisition is in progress. This workaround does not help for an infinite records case.
  • Complete the following steps:
    1. Call the Records Done property before the the niRFSA Check Acquisition Status VI.
    2. Wire the reference out output of the niRFSA Property Node to the instrument handle input of the niRFSA Check Acquisition Status VI.
    3. If the done? output of the niRFSA Check Acquisition Status VI is TRUE, you can safely use the number of records that are returned upon fetching.

Reported Version: 2.9    Resolved Version: N/A    Added: 03/06/2014
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:
  • Do not call the niRFSA Abort VI while a record acquisition is in progress. This workaround does not help for an infinite records case.
  • Complete the following steps:
    1. Call the Records Done property before the the niRFSA Check Acquisition Status VI.
    2. Wire the reference out output of the niRFSA Property Node to the instrument handle input of the niRFSA Check Acquisition Status VI.
    3. If the done? output of the niRFSA Check Acquisition Status VI is TRUE, you can safely use the number of records that are returned upon fetching.

Reported Version: 2.9    Resolved Version: N/A    Added: 03/06/2014
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.

Reported Version: 2.7    Resolved Version: N/A    Added: 05/12/2014

Related Topics

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).