Archived: NI-RFSA 2.4 and 2.4.2 Known Issues

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.

Calling niRFSA Self Cal VI or the niRFSA_SelfCalibrate function for the NI PXIe-5663E does not self-calibrate the associated digitizer.
If you call the niRFSA Self Cal VI and set the steps to omit parameter to an empty array, or if you call the niRFSA_SelfCalibrate function and set the stepsToOmit parameter to 0, the Digitizer Self Cal option is not executed as expected.

Workaround: 

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

In Spectrum acquisition mode, there is no magnitude only equalization performed when doing in-band retuning.
The 5 MHz and 300 kHz filters do not have any magnitude equalization performed in spectrum acquisition mode on the NI PXIe-5665.

Workaround: 

N/A

Calling niRFSA Self Cal VI or the niRFSA_SelfCalibrate function for the NI PXIe-5663E does not self-calibrate the associated digitizer.
If you call the niRFSA Self Cal VI and set the steps to omit parameter to an empty array, or if you call the niRFSA_SelfCalibrate function and set the stepsToOmit parameter to 0, the Digitizer Self Cal option is not executed as expected.

Workaround: 

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

EVM and MER measurements are degraded when using RF list mode.
When using NI-RFSA 2.3, 2.4, 2.4.2, or 2.5, EVM and MER measurements are degraded when NI-RFSA executes all RF list mode steps after the first step. NI-RFSA applies calibration corrections incorrectly for RF list mode steps beyond the first step, which leads to greater measurement errors. This issue may be more noticeable if your application uses high symbol rates and/or high-order digital modulation.

Workaround: 

To avoid this issue, you can choose from one of the following options:

• Avoid using RF list mode in your application.
• Wait to use list mode until this issue is fixed in the next version of NI-RFSA.

1. Reset the device in Windows.
2. Restart the controller in the LabVIEW Real-Time module.

1. Update the nihsd.ini file in C:\Program Files\National Instruments\RT Images\NI-SCOPE\

   1. Update the children from @tIniManager@Children = "NI PXIe-5142,NI PXIe-5122,NI PXIe-5152,NI PXIe-5105,NI PXIe-5622,NI PXIe-5184,NI PXIe-5185,NI PXIe-5186"
      to
      @tIniManager@Children = "NI PXIe-5142,NI PXIe-5122,NI PXIe-5152,NI PXIe-5105,NI PXIe-5622,NI PXIe-5622 (25MHz DDC),NI PXIe-5184,NI PXIe-5185,NI PXIe-5186"
   2. Add the following entry at the end of the file:
      "[@tIniManager@Root:Peripheral Modules:National Instruments:NI PXIe-5622 (25MHz DDC)] Library = c:\ni-rt\system\pxi\drivers\NIPXIePM.dll Version = 65536"
2. Reinstall the NI-SCOPE driver on the RT target.

• 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

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

• Using a narrower resolution bandwidth.
• Disabling the dither.
• Choosing a different FFT window type. This solution may be less effective than the previous solutions, depending on the resolution bandwidth.