NI 5620 acquisition

Hello,
I have NI 5660 RF Signal Analyzer, and I want to configure the digitizer to start acquiring data when a certain RF signal is detected (for examples from a remote control, I press the buton and the device starts acquiring data, I release the buton it stops). Maybe here could be more than one solution thats why I am asking
Best Regards,
Stefan

Hey Stefan,
You can configure your 5660 to start the acquisition by using a start trigger. One option would be to configure the trigger off of a digital edge on one of the PFI lines on the digitizer. Whenever a digital high is received on this line the acquisition would begin. Another option would be to send a software trigger. For example, if you pressed on a button on your VI you could configure it to send the software trigger and begin the acquisition.
As far as releasing the button and the acquisition stopping, this will be more difficult to implement. You could of course just a wire a stop button to your while loop to end the acquisition. If you need an actual hardware signal you could use a reference trigger. This will stop the acquisition after the reference trigger is received.
The driver ships with some example programs that should help you get started with this. If you look in the NI Example Finder in LabVIEW at Help » Find Examples » Hardware Input and Output » Modular Instruments » NI-RFSA (or NI-5660) » IQ Acquisition you should see an example called ni5660 Trigger IQ.vi. This will show you how this is implemented.
Good luck with your application and let me know if you have additional questions.
Regards,
Chris Delvizis
National Instruments

Similar Messages

PXI 5620 Initialize Error

Hi
I am running into a problem. It has been a week but couldn't figure it out. I have PXI 5620 Digitizer and Labview 2010 SP1. The error only occurs when I run EXE, not in debug.
Here is the error:
LabVIEW: Open VI Reference no longer matches VIs in memory by filename. A filename is no longer sufficient because the full name of a VI now includes any owning libraries.
VI Path: C:\SWA-1302-003 2.4GZ FT\2.4GZ Final Test Application\2.4GZ Final Test.exe\1abvi3w\vi.lib\addons\Modulation\niScope\mod_Set Receiver(RFSA).vi
Attachments:
VI call error.png ‏33 KB
VI Error.png ‏86 KB
vi.png ‏33 KB

Have you taken a look at this KB?
I can't see your whole VI (or potential sub VI's), so it might be helpful to post that. It seems like you are passing a VI reference name at somepoint, and when this is compiled into an executable, it is no longer looking in the correct location.
Are you building an installer or an executable?
Jon S
Applications Engineer
National Instruments

Fetch realtime data in 5620

hi
I have a problem in using the 5620 digitizer to fetch real time data
We have a project to demodulate GPS signal wich center frequency at 1.57542GHz and bandwidth 2MHz.
In first step, I used " ni5660 fetch IQ data.vi" by modify the
bandwidth to be 2MHz and fetched about 0.2 second data. I succesfully
demodulated the GPS signal.
But I found with this vi, I can not get longer time, for example,
60seconds data. So I used the "nituner getting started.vi" to
mannually downconverte the signal to IF and "use niScope EX Stream to
Disk.vi" to fetch the data to disk. Now the niTunner: frequency
shift 1.561GHz.
So, the IF frequency is 1.57542GHz-1.561GHz=14.42MHz. Then I set the
digitizer frequency to 6.4M/s which means that the the signal is
aliased to 14.42MHz-6.4MHz*2=1.62MHz. With the signal bandwidth
2MHz. Now the aliased signal is from 1.62MHz-1MHz to
1.62MHz+1MHz. But now, I can not demodulate this signal !!!
Could anybody help me about this?
Thanks

Refer to this previous thread.
Tica T
Applications Engineer

PXI-5620 "No Device Found"

I am unable to get my PXI-5620 to do anything besides appear in NI MAX and pass a self test.
I have tried running several NI-SCOPE example VIs, and the NI-SCOPE Signal Express VI on the target "TransOsc" but both fail to find the 5620 module (It does not appear on the I/O pull down menu even after selecting "refresh").
Attached below is a screen shot with the following items displayed;
NI MAX (to prove that the 5620 module is indeed recognized by MAX, and the proper software is installed on the target)
The project heirarchy ( the VI I am writing to talk to the module through the chassis labeled "TransOsc" is labeled "untitled 3")
The NI-SCOPE Express VI configuration page (showing "No Device Found")
Attachments:
try1.png ‏1897 KB

After consulting the readme for NI-SCOPE 4.1 I found that
"The run-time installer does not support the NI 5102, NI 5112, NI 5620, or NI 5621"
I am running RT 13.0 on the target. Is this why I cant interface with the module?

Windows 7 not recognizing device - Dell Wireless 5620 EVDO HSPA Mobile Broadband Mini Card

Windows 7 is not recognizing my Dell Wireless 5620 EVDO HSPA Mobile Broadband Mini Card (Qualcomm Gobi 2000). I can't even uninstall the driver, it says that I don't have "sufficient permission" to stop device or something to that effect
(though I'm an administrator). I also can't re-install the same or different driver. I might have installed the wrong driver, though this is supposed to be the correct one according to Dell after typing in my service tag. I went to the FTP
to get one specifically for "Verizon Wireless", but I can't uninstall the prior driver.
How can I fix these issues? Thanks.

Hi,
Any update?
Have you tried safe mode mentioned in the first reply? What is the status of the driver in device manager? For "Verizon Wireless", have you installed any verizon software or related verizon device? Uninstall this kind software, then uninstll driver again
as a test.
Contact this support, maybe they can give some different ideas.
Verizon Wireless Support
http://www.verizonwireless.com/support/
NOTE
This
response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you.
Microsoft
does not control these sites and has not tested any software or information found on these sites.
Yolanda Zhu
TechNet Community Support

PXI 5620 not linking

I have Labview 2011 and I am using PXI 5600 downconverter with PXI 5620 as the digitizer..First I had the problem that PXI 5620 was not compatible with DAQmx so the device did not have a self test in MAX 5.0.. Also due to PXI 5600 failed the test.. Then to check the basic functionality by RFSA from Start>>All Programs>>National Instruments>>NI-RFSA.. 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..... Also can someone tell me how to link PXI 5620 with PXI 5600.. Thanks
Attachments:
error1.JPG ‏126 KB

all the other hardware on the PXI chasis is working fine...more specifically I have 5600 and 5620 as RFSA and 5610 and 5421 are RFSG..RFSG is working perfectly fine .It passes the self tests and also runs examples..Problem is with RFSA.5600 does not pass the self test.5620 digitizer passes the self test in traditional NI-DAQ devices. pic # 1
I havent tried 5660 with any other software or any other slot..
As for examples.I tried to initialize the 5660 with Labview VIs.I got the error "the down converter is busy its internal state machine may be locked up" pic # 2
And when I ran the example I got the error" the attribute is not supported when using NI RFSA with an external digitizer module"pic # 3
and while running NI RFSA soft panel it gives the error that "RF downconverter was detected but it has a missing digitzer or LO "...
Can there be any problem with the connecting cables?
Attachments:
5620 DAQ working.JPG ‏129 KB
RFSA initialize error.JPG ‏97 KB
rfsa example error.JPG ‏115 KB

PXI-5660 / 5620. What is lowest reasonable voltage when using Analog Edge Trig?

Presently, I am using Analog Edge Ref Triggering on the PXI-5660. The lowest voltage that I can set the trigger level to is 0.200 volts without noise causing the trigger to occur. Is this level reasonable? Is there a way to reduce the noise so that the trigger level can be set lower?
I graphed the waveform coming out of the niScope MultiRead Cluster.vi in the ni5660 Read Average Power Spectrum.vi. The noise on the graph was as high as 0.190 volts. I thought that I saw the noise down to 0.010 volts at one time.
Thanks.

Thank you for your response.
The reference level I am using is 0 dBm.
I ran the ‘niScope SMT Power in Band.vi’ example with dithering enabled and disabled. I could see the noise when dithering was enabled and the reduced noise or no noise when dithering was disabled. See attached .jpg’s. I added ‘Waveform Graph 2’ to display the output of ‘niScope Multi Read Cluster.vi’.
In my application, I disabled dithering and put the trigger level lower. It now works.
Disabling dithering needs to be set after ‘ni5660 Configure for spectrum.vi’. Inside the ‘ni5660 Configure for Spectrum.vi’, a vi called ‘SMT Configure RFSA for Spectrum.vi’ enables dithering. ‘SMT Config niScope for Spectrum.vi’ is another vi that enables dithering.
Thank you for your help.
Attachments:
SMT Power in Band with 50 ohm termination on input of 5620 Dither Disable.jpg ‏100 KB
SMT Power in Band with 50 ohm termination on input of 5620 Dither Enable.jpg ‏106 KB

Niscope_init does not recognise 5620

I am using NI-5620 digitizer and ran into a problem:
MAX recognises the board, but when I use niscope_init to get the session it returns
error 0xbfff0011 (Insufficient local information or the device or resource not present...
I am using the same instrument ID string I used before on another system. I also tried
the DAQ::1 and create/use alias. Still the same error.
HELP, please – [email protected]

I added a couple of zip files and seq file.
Mark
Attachments:
TestDll.zip ‏790 KB
TestDllTest.zip ‏5 KB
TestDLL.seq ‏15 KB

Problem initializing 5620 digitizer

Trying to run example provided - Getting Started. When niScope_init is executed I get an error - BFFF0011 telling me the "Insufficient location information or ... device not found".
MAX does see the device and for the name I enter the information from MAX - PXI12::15::INSTR. I also tried to set up an alias using rename - same result, same error. At the same time MAX says the device is there, it is fine and I can run the NI-SCOPE soft panel just fine.
HELP!!!
Mark
What can cause that?

It looks like you're using the VISA name for the device. NI-Scope
is expecting an IVI session, IVI logical name, or a DAQ name for the
device instead. In MAX, under Devices and Interfaces, look for
the 5620 under Traditional NI-DAQ Devices. It will have a certain
DAQ number. Use this number in the resource name like the
following example: "DAQ::1"
Hope that works.
Patrick

USB 6009 Data Acquisition noise

When I acquire the voltage from USB 6009, It gives some fluctuation/Noise (Please check the image, green color).
What is the reason for that?. How to overcome this noise? One way is averaging, is there any other ways to do or overcome this problem
Could you please suggest me?
Thank you,
Best Regards,
Rathan
Attachments:
Noise.GIF ‏16 KB

Dear Rathan
The correct Terminal configuration depends on if your power supply is floating or grounded. Please have a look at tabel below.
As to the filter, which type of filter to use depends on the frequency of your signal. If your frequency (or frequencies) is low a lowpass with a cutoff frequency a bit over your frequency would be best. Conversly if your frequency is high a highpass with a lower cutoff frequency would do the job. If you are interested in only a single or small spann of frequencies a bandpass could be used.
You can filter your signal either via a hardware filter before you acquire it via your DAQ, but that would require that you have or can build a hardware filter that fits your needs. Else you can filter the signal in software after you've aquired it. The filters in LabVIEW can be found in the functions palette under Signal Processing -> Filters. I think a butterworth filter would do nicely. You can find an example through the LV Help.
Best Regards
David
Message Edited by DavidEk on 07-29-2009 05:03 AM
Attachments:
Connection Configs.PNG ‏66 KB

How to take a single data point for each trigger pulse ( synchronous acquisition).

hi
          im using the pci-mio-16E1 card, with the IDE VC++, so im looking for an example to explicate me how to make an synchronous acquisition data using an external timing, so the idea is to acquire (take) a single data point for each trigger pulse from one input channel ,and saving the data in a file .
now im making a code using the AI_setup and DAQ_op functions, im getting a speed acquisition (it is the start of acquisition data), and it is a synchronous acquisition just for one trigger pulse, and me i looking for an acquisition for each trigger pulse.
so to  understand my problem you can see my code :
iStatus = Timeout_Config(iDevice, lTimeout);
         iRetVal = NIDAQErrorHandler(iStatus, "Timeout_Config", iIgnoreWarning);
   // configuration and selection of signal trigger
         iStatus = Configure_HW_Analog_Trigger(iDevice, ND_ON, iLowValue,iHighValue, ND_ABOVE_HIGH_LEVEL, ND_THE_AI_CHANNEL);
        iRetVal = NIDAQErrorHandler(iStatus, "Configure_HW_Analog_Trigger", iIgnoreWarning);
iStatus = Select_Signal(iDevice, ND_IN_CONVERT, ND_PFI_2,ND_HIGH_TO_LOW);
         iRetVal = NIDAQErrorHandler(iStatus, "Select_Signal", iIgnoreWarning);
    iStatus = AI_Setup(iDevice, iChannel, iGain);
   iRetVal = NIDAQErrorHandler(iStatus, "AI_Setup", iIgnoreWarning);
   while ((iReadingAvail != 1) && (iStatus == 0)) {
/* Wait until reading is available. */
         iStatus = AI_Check(iDevice, &iReadingAvail, &iReading);
        iRetVal = NIDAQYield(iYieldON);
       // Acquire data from a single channel
    iStatus = DAQ_Op (iDevice, iChannel, iGain, piBuffer, ulCount, dSampRate);
   while ((iDAQstopped != 1) && (iStatus == 0)) {
        iStatus = DAQ_Check(iDevice, &iDAQstopped, &ulRetrieved);
        iRetVal = NIDAQYield(iYieldON);
       iStatus = DAQ_VScale(iDevice, iChannel, iGain, dGainAdjust, dOffset,ulCount, piBuffer, pdVoltBuffer);
      iRetVal = NIDAQErrorHandler(iStatus, "DAQ_VScale",iIgnoreWarning);
   /* Set analog trigger mode back to initial state. */
       iStatus = Configure_HW_Analog_Trigger(iDevice, ND_OFF, iLowValue,iHighValue, ND_ABOVE_HIGH_LEVEL, ND_THE_AI_CHANNEL);
/* Set PFI line back to initial state. */
       iStatus = Select_Signal(iDevice, ND_IN_START_TRIGGER,ND_AUTOMATIC, ND_DONT_CARE);
          iStatus = DAQ_Clear(iDevice);
/* Plot acquired data */
      iRetVal = NIDAQPlotWaveform(pdVoltBuffer,ulCount, WFM_DATA_F64);
so this is the data acquired -0.900879,-0.900879,-0.900879,-0.900879,-0.900879,-0.900879,-0.900879,-0.900879 and i think that is a noise because all time i get this data.
tank you very mutch fo your help

Hello,
Please see the responses to this thread at the following post.
http://forums.ni.com/ni/board/message?board.id=250&message.id=13686
Also, please only post one thread per issue.
Regards,
Sean C.

Counter issues with 2D raster scan and count acquisition

I am building a confocal laser scanning microscope and am currently attempting to develop labview controls for it. I have a fast steering mirror (FSM) which takes analog voltage inputs to control it's x and y angle and I have an avalanche photo diode (APD) which sends a TTL pulse for each photon detection event. For now, I am trying to create a program which will send out two analog signals to create a 2d raster scan with the FSM and count the number of pulses from the APD per pixel. I have been trying to make the program from https://decibel.ni.com/content/docs/DOC-5779 work, but I keep running into counter issues. I am using a generated pulse train from the other counter on my device (NI 6011E) as the period.term input, but I get a "Two consecutive input signals occurred without a counter timebase edge" error if I increase the frequency of the pulse train too high. Unfortunately, the number of pixels I can acquire seems to be limited to twice the frequency of the counter, so I cannot just use a lower frequency train. I believe that the error is occurring because the count rate from the APD is very low and that there are simply no photons hitting the detector in the time period between pulses.This is not a problem, but I would like to know how to simply record a 0 and continue with the scan, rather than have the entire program exit with an error.
Alternatively, if this does not seem like the correct way to accomplish what I am trying to do, I am open to new directions.

So simply ignoring the error did not work, because the DAQmx subroutine stops collection when the error is detected. I think I may need to come up with a different approach to synchronize the counting of TTL pulses with an analog output. Attached below is the code I have been working with.
Attachments:
Raster_2DOutput_wCounter_82.vi ‏45 KB

Use of Audio In on laptop for Data Acquisition

I'd like to use the Audio In on a laptop to acquire 500 point per second data in a biomed experiment. Where to I get a driver or whatever code I can use to access the audio in on my laptop (a HP). I'm using Labview for windows.

I've used the "audio in" to determine a fan's RPM, using a microphone. The problem I see with your application idea is the slow sample rate required. I believe choices are 11K, 22K or 44.1K samples per second for the audio input drivers - at least the version I've used. An example of an ocilloscope using the audio sound card drivers can be found at:
http://www.yelmtel.com/~joej/vis/scsco.zip
Perhaps you can modify this to suit.
Joe Jasniewski

Need help incorporating the second counter into a current data acquisition routine (continuous retriggerable AI).

My current application acquires data when it sees a TTL trigger line. Then it wait until the next TTL pulse and continues taking data until the user stop the data acquisition process. I use "counter 0" as counter source. The program works well. However I need to read digital data everytime I take AI data. I plan to use "counter 1" to read the digital data. The trick is that I need to synchronize both AI and counter 1 readings. Therefore the counter 2 will acquire data when AI acquires data.
Here is the code I implemented and would like to know if it is correct. The new code (implementation of second counter) is in the bottom part of the code. I will really appreciate your help.
Yajai
Attachments:
code.txt ‏6 KB

Hi DrObb,
What is sounds like you want to do is to specify an external sample clock for your analog acquisition and a digital acquisition. Is there a reason in particular that you're using a counter? What hardware are you using? If you simply want to sample a digital and analog channel on the same clock edge, this won't be very difficult (provided your hardware supports hardware-timed digital IO). You can find an example of this being done in C by going to:
Start » All Programs » National Instruments » NI-DAQ » Text-Based Code Support » ANSI C Examples and then navigating to Synchronization\Multi-Function\ContAI-Read Dig Chan
Regards,
Sean
Sean Ferguson
Application Engineering Specialist | RF and Reconfigurable Test

Image acquisition slower than expected on Win 7 64bit

Hi all,
I wanted to know if anyone had issue after upgrading OS from Windows XP to Windows 7 64bit.
I had a fairly big project the runs fine on Windows XP, hardware is computer + PCIe 1433 + Basler A504 + external trig source. The frame size 1000*128 pixel so I can acquire at 4kHz. This works fine. NI Software is LV 2011 SP1 + lastest VDM and VAS.
I've tried to switch to Windows 7 64bit with LV 2011 SP1 + VDM + VAS all in 64bit versions and the acquisition doesn't work as I expect.
I've put together a test VI that configures the acquisirion in a similar way that my app does (triggered ring acquisition) with my external trig source set at 4kHz, when I run it, instead of having a 4kHz frame rate I get ~250Hz frame rate.
I also tried triggered acquisition in MAX because I know MAX gives me 2 information : display frame rate and acquisition frame rate, both appear to be ~250Hz.
I contacted NI about this issue, an application engineer has been able to reproduce the issue with similar hardware and we're trying to identify the reason.
Anyone has a clue?
ps : here's the code used to test the acquisition on Win 7 64bit.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"
Attachments:
TestAcqu_64bit.zip ‏99 KB

Hi TiTou,
Please make sure that you are not triggering the camera and the frame grabber board.Sending a trigger signal to the camera in order to trigger acquisition of every frame. In this case, there is no need to trigger the frame grabber board as well because the camera is being triggered directly. What was causing the acquisition to run at half the triggered frame rate was the way the signals lined up. The camera begins acquiring on the rising edge of the trigger pulse. Once a rising edge is received, FVAL goes high and remains high as long as the camera is exposing. It then goes low until another trigger pulse is received.
At the same time, if you are triggering each buffer on the frame grabber, the frame grabber waits to begin reading data from the camera until a rising edge is received, and then begins read out once FVAL goes low. The result is that the frame grabber begins reading out the current frame, which takes about as long as the camera takes to acquire a frame. So while the frame grabber is reading out the data, the camera receives the next trigger pulse and begins acquiring the next frame. However, the frame grabber is still reading out the previous frame and thus ignores the trigger pulse until it finishes, resulting in an acquired frame rate that is exactly half of the triggered rate. At lower rates, there is enough time for the camera and the frame grabber to acquire the frame off the same trigger pulse and "re-arm" before the next pulse arrives.
Elmar
PS: Please also make sure the exposure time is lower as 161us.

NI 5620 acquisitio​n

Similar Messages

Maybe you are looking for

NI 5620 acquisition