PXI 5620 not working

[sabe]

I tried to test the functionality of my RFSA from Start>>All Programs>>National Instruments>>NI-RFSA... After I found out that PXI 5620 is not compatible with NI DAQmx.. But when I ran the test I got the error "The down converter is busy.Internal state machine may be locked up" .I cant figure out where the problem is.

[Jake_G]

Hey sabe,

There are a couple reasons this may be occurring. 

Typically this would occur because the PXI-5600 RF Downconverter is overheating.

Check out this knowledgebase article for more information:

Why am I Receiving Error -27004 at the NI TUNER Initialize.vi when using the NI 5600?

You mentioned the PXI-5620 only, but I believe that is only part of the PXI-5660 Vector Signal Analyzer.  If this is the case, make sure the connections are set up as seen in the specifications manual:

NI PXI-5660 Specifications

[sabe]

I have Labview 2011,MAX5.0, Daqmx 9.3.5 and RFSA and NI scope latest drivers installed. The problem is that first 5620 is not compatible with Daqmx 9.3.5 so I can run the self test of 5600...Then to check the basic functionality I went to NI 5660 demo test panel where I got this error "The downconverter status may be locked"...I want to know that is my problem with software(drivers) or with hardware and if it is with hardware then is it with 5600 or 5620 or both of them and whats the solution ...Is my device damaged?? My connections are correct Also how to let device cool of? I use that device two or three hours a day so whats the point in it getting heated

[Jake_G]

Hey sabe,

It does look like you have it physically set up correctly.  Which chassis and which slots do you have the devices in?  Did you follow the getting started instructions precisely when you installed the hardware?

The NI-RFSA driver should install everything you need to run the device (especially in the 5660 Demo Test Panel).  NI-DAQmx isn't necessary to install separately.  If it was a dependency, it would have been installed with NI-RFSA.  If you installed everything in the correct order, you may check the cables that connect the devices by changing them out (if possible).  If none of these is the answer and you let everything cool down and it still gives this error, it is most likely a hardware issue, most likely to do with the 5600 being locked up somehow.