Hi Johan,
You can program the PXI-5660 to acquire continuous, gap-free data, as
illustrated by the NI-RFSA 1.5 shipping example "ni5660 Fetch IQ
Data.VI". This example acquires continuous IQ data. I have modified
this example to add FSK demodulation to it to accomplish continuous FSK
demodulation.
Hello Johan,
The difference between a 5660 and 5600 is the 5600 is the RF
downconverter module, and the 5660 is the pair of modules containing
both the downconverter (5600) as well as the IF digitizer (the
PXI-5620).
So, the 5600 is essentially a signal conditioner that (a) does
frequency downconversion and (b) applies attenuation and gain and the
digitizer module does all the data acquisition and transfer. It is not
possible for me to send you an FSK example using just the 5600 since
the 5600 does no data acquisition.
Thank you for your message. Indeed, my message was incomplete. We have a 5600 plus PXI-5620 (digitizer). I interpreted a question of my PhD student to hastely. If the combination is identical to the PXI-5660 (the bundle), than the example should work fine for us, and we need to study your example better. My student mentioned that the example was for the PXI-5660 and not for the PXI-5600, just before he left on holiday, and that's what triggered my question. Next time we take a closer look to the web-site first! When he's back we dive into the example.
Hello Johan,
I apologize for the confusion. The PXI-5660 RF Vector Signal Analyzer
refers to the kit available from NI that contains (1) the PXI-5600
module, (2) the PXI-5620 digitizer, (3) cables for interconnecting the
two modules and (4) the Spectral Measurements Toolkit software +
drivers. You should be able to use the example - just look in
Measurement and Automation Explorer for the device numbers (of the 5600
and 5620) and enter these into the front panel in the appropriate place!
We looked into the example further and in the beginning we were missing a number of VI's (ni5660 initialize, ni5669 fetch IQ, etc). We solved that by upgrading our RFSA (and scope) driver to 1.5 (and 2.8), respectively. What is keeping us from running your example is one missing VI, called MT generate systems parameters (might be FSK in there, you will know). We traced it back to modulation tool kit 3.0. We are using modulation tool kit 2.0. Is there a different source for this, or any way to use your example with modulation tool kit 2.0?
Hi Johan,
In Modulation Tooklit 2.0, there were separate VIs used for generating
system parameters for each of the supported modulation types (Generate
FSK System Parameters.vi, Generate QAM System Parameters.vi, etc...).
In MT 3.0, this was changed to a single polymorphic LabVIEW VI, so you
drop down one instance of Generate System Parameters and then select
which type on the block diagram.
So, all you have to do to make this work in MT 2.0 is replace the
missing subVI with MT Generate FSK System Parameters.vi from the
Modulation Toolkit pallette.
I went ahead and installed 2.0 and did this in the attached (modified) example.
