PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

PXI 5660 gives spurious signals, niScope Driver Status err

Gerardo,

We have not made any upgrades since we first received the LV 8.21 package (somehow it seems that Academics are the last to receive new releases and licenses).  But, I can guarantee that all three PCs and all three PXIs are configured in an identical manner and the problem only exists with the single 5600.

Chris
0 Kudos
Message 11 of 14
(1,638 Views)
Hello Chris,
 
The drivers are usually free, independent of the LabVIEW version (as long as is current which 8.20 still is), and you do not need to upgrade but it will be helpful to know what RFSA and NI-TUNER driver version you have. You can find this on Measurement and Automation Explorer. Expand the section called "software" and select the proper driver. On the left, you will see the driver version.
 
I am attaching a NI-Tuner Program to make sure your attenuation is being applied.
1. Open this and run it with RF frequency of 12.5 MHz and span of 15 MHz (0 reference level).
2. Open the shipped example: "C:\Program Files\National Instruments\LabVIEW 8.2\examples\Spectral Measurements Toolset\niScope\SMT Configured Spectrum for niScope.vi"
3. Run it and if your unit is bad, you will see the spurs (you can use your external spectrum analyzer as well tuned at 15 MHz).
4. Make a note of the Attenuation.
5. Now change on the Attached program the RF Frequency to 15 MHz and Span of 20 MHz. Run it.
6. You should stop seeing the spurs if everything is working as your screenshots suggested.
7. Make a note of the Attenuation.
 
Thank you,
Gerardo O.
RF SW Engineering R&D
National Instruments
0 Kudos
Message 12 of 14
(1,634 Views)
Gerardo,
 
I followed your instructions and verified the spurs in step 3 and NO SPURS in step 6.  I don't know what you mean about making a note of the attenuation in steps 4 and 7.  Do you mean from the front panel of the ni-tuner set parameters.vi?  It is 0.00 dB in both cases.
 
Chris
0 Kudos
Message 13 of 14
(1,610 Views)
For those reading this forum,

The issue above has been rectified.  The problem was found to be with the hardware and the card was sent in for repair.

Regards,
Paul C.
0 Kudos
Message 14 of 14
(1,591 Views)