Continuous Acquisition of GSM IQ data

http://forums.ni.com/t5/RF-Measurement-Devices/GSM-IQ-data-capture/td-p/3082271

Hi, When i tries to acquire GSM IQ data with filter active i.e else if (RBWFilterType == MODT_GAUSSIAN_FILTER) {; the code hangs at checkWarn (
niRFSA_FetchIQMultiRecordComplexF64 (rfsaSession,"",0, NUMBER_OF_RECORDS,numSamples,-1,waveform,wfmInfo));
while if i comment the filter i get the following error image attached.
What could be the problem?
Attachments:
error.PNG ‏9 KB

Similar Messages

  • How can I perform continuous acquisition of a repetitive waveform?

    I want to synchronously acquire a repetitive waveform where there is little or no dead time between cycles. I plan to use an external trigger and scan clock. I need to store each cycle of the waveform as a separate record so I need to know the start and stop sample for each cycle.
    I considered putting an N sample acquisition inside a Do While loop, but I can't afford to drop cycles.
    I'm considering doing a continuous acquisition and calculating the correct number samples to read from the buffer for each waveform cycle. My concern with this method is that I need to acquire waveforms for a long time (many hours) and I'm concerned about losing synchronization. I've thought that maybe I could acqu
    ire say a 1000 cycles and then restart the process, which would minimize dropping cycles and maintain synchronization.
    Any suggestions? Am I making this harder than it really is? I probably should say that I'm using a 6052E DAQ sampling at 100ksps.

    Hi
    I am trying to solve a similar problem at the moment (I have a discussion going in the 'Dynamic Signal Acquisition and Analysis' section) but have not found a completely satisfactory solution so far.
    I am acquiring an analogue signal from a rotating machine from which I also have a TTL signal which gives me a once per revolution (OPR) marker. I want to continuously acquire the analogue signal and use the OPR pulsing signal to 'chop up' my continuous analogue signal into a set of data for each rev.
    I have used a method similar to the one you have described - I use continuous double-buffered acquisition to acquire the analogue signal and the counter values, with the OPR pulse signal as the counter gate. However, I have been unable to synchronise the s
    tart of the signal and counter acquisitions together. I can start the signal acquisition using the OPR signal as a trigger but not the counter. I tried using GPCTR_Change_Parameter() to set the start trigger to external (ND_ENABLED) but this is not permitted with my E Series device (PCI-6111E with DAQ-STC).
    Do you know a way round this? And even if I could start my counter acquisition using the OPR signal, how do I ensure that I haven't missed any revs between starting the signal and counter acquisitions (in tests where I use immediate software triggers for the signal then the counter in successive lines of C++ code, my counter is already 2 cycles behind at just 100Hz OPR).

  • Vertical setting during continuous acquisition with NI5112

    I need to change the current vertical range configuration during a continuous acquisition.
    Is it possible without data loss?
    Or I have to stop the acquisition?
    Thanks for your answers.

    Thank you Annette, your answer allows me to understand some details about PCI-5112 board.
    I need to acquire continuously data at 2 Msample/sec for 10 minutes at least, without loss, and signal level can slowly change during the acquisition (es. a sinusoidal amplitude increasing from 0.5 to 2 V into 10 minutes).
    It’s important to adjust the vertical setting due to use all the dynamic range.
    I’ve used “niscope Fetch&Save Forever.vi”, performing a single channel continuous acquisition with 8-bit fetching data (“1 channel acquiring – 1 channel fetching” example).
    Fetch operation is inside the loop, while all the configuration ones are outside, so if I want to change a configuration parameter, I have to exit from the f
    etching loop, stop the acquisition (with “niscope abort.vi”), set the new parameters and finally restart the acquisition, with a necessary loss of data.
    I thought a second way: “2 channel acquiring – 1 channel fetching”.
    If I have well understood, I could acquire the same signal from both the channels, configured with different vertical settings (es. +/-1V and +/-2.5V respectively), so I could fetch data from the better vertical range channel only.
    In this mode I perform an effective vertical setting (but in 2 steps only) during the continuous acquisition without data loss.
    First question:
    Is it right? Is the last example (2 ch. Acq. – 1 ch. Fetch) more expensive with respect to the first (1 ch. Acq. – 1 ch. Fetch) in terms of PC and/or OS resources?
    I have inserted the PCI-5112 board in a Pentium III, 128 Mb RAM, with Windows ME OS.
    Second question:
    Sometimes, during the fetching operation, the board stops the acquisition (I see
    noise only), and it’s necessary to make the shutdown of PC, before to see the signal again!
    Is it necessary a reset (with "niscope Reset.vi")? Is a Windows ME bug? Is a board failure?
    Thank you in advance.

  • Why can I only write the samples to read during continuous acquisition?

    I am acquiring analog voltage signals and attemting to write to a text file when condition is true, thus there is continuous acquisition. However, the written files only contain 100 samples (the size of my buffer).. I need my files to read samples until the while loop is stopped. How can I go abotu doing this?
    Thanks,
    TFlax
    Solved!
    Go to Solution.

    I have been able to make this work, but  it only writes the buffer size. I am new to labview and programming in general and I have tried to make a producer and consumer design however I dont seem to understand the concept properly and fail to run my program properly... So here's my code before any attempt to producer/consumer design which only writes 100 samples to file. Advice on how to modify it to producer/consumer because Im not even sure where to start.
    Thanks,
    Tflax
    Attachments:
    Test_Signals_Dec17.vi ‏745 KB

  • Turn off phone capability of iPhone and continue using cps and cellular data?

    Can I turn off phone capability of any iPhone and continue using cps and cellular data, practically using the device as iPad? Is this going to be possible with iOS8 or iPhone 6 Plus?

    This could be what you are looking for:
    Using an iPhone without a wireless service plan

  • Gsm IQ data capture

    Hi,
    Am using a GSM toolkit to try capture GSM IQ data for analysis. My user interface values are as the fig attached. When i run the app i get the following error -1074118626 full details in the image attached. I tries to lower the trigger level but again returns unspecified error. What could be wrong?
    Regards,
    Waciuri

    Also included is my C file.
    Thanks,
    Moses.
    Attachments:
    uir.PNG ‏40 KB
    error.PNG ‏19 KB
    G.c ‏25 KB

  • Multi-record continuous acquisition with PCI-5112

    Hallo!
    I need to know if it is possible to obtayn a continuous acquisition in multi-record mode.
    In "niScope EX Multi Record Fetch Forever.vi" shipping example (LV 5.1), it seems to stop when "loop index" rises to "number of records -1" value.
    I've not the avilability of the PCI5112 card at the moment, so I cannot to try on, but I need of a confirm.
    If I've well understood, I could modify the loop condition, by erasing the check on loop index, and by wiring "loop index"mod(N), to "fetch record number" attribute (let's define N as "number of records"). So I could continuously fetch the records 0,1,..,N-1, for the first cycle, and again 0,..N-1, for the second cycle, and so on.
    OK! I think that the contents of a reco
    rd number K (with 0<=K<=N-1) are different if acquired in different cycles! In this way I can obtayn a "for ever" multi record acquisition. Is it right?
    Thanks for your answers.

    NatRob,
    It sounds like you are on the right track. The only thing keeping this from running continuously is the comparison of "loop iteration + 1" to the "number of records." Other than that, the loop should only stop when an error occurs or hte Stop button is pressed. Just erase the greater than comparison and the boolean used to stop the loop and it should work.
    Regards,
    Chris Drymalla
    NI Applications Engineer

  • Changed my ID but the Iphone 4 continue with the old ID name and does not syncronize. How can I change it in my Iphone so I can continue to use all my data stored like contacts and notes?

    Changed my ID but the Iphone 4 continue with the old ID name and does not syncronize. How can I change it in my Iphone so I can continue to use all my data stored like contacts and notes?

    Do you mean through iCloud?  You need to go to settings > iCloud and "delete account" and then sign in with the newly named account.  You'll want to do similar for facetime, messages, and store.

  • Dual Channel Continuous Acquisition on the 5640r?

    Hi,
    I'm jumping posts from the Real-Time to the IF-RIO community (you can see  http://forums.ni.com/ni/board/message?board.id=280&message.id=8356&jump=true#M8356 for more background on my problem).
    I would like to be able to write synchronously to two channels as well as achieve continuous acquisition on the other two channels.  I realize that I will need to reduce my bandwidth to be able to do this, but that is not a problem.  I was able to get the ni5640r (Single Channel) Analog Input and Output project (NI's template) working for continuous acquisition under the advice of Jerry_L.  But, in trying to apply the same fixes to the ni5640r Dual Analog Input and Ouput project (again, NI's template), the acquisition is not continuous.  I've attached my current version of this project.  I would greatly appreciate it if someone could offer advice on how to move forward with it.
    Thanks!
    Chris

    JaceD,
    I think you may be right.  I tried to recompile twice today, and it failed both times.  First, it complained about not finding the compiler (listing the IP address of this same machine on which LabVIEW and the IF-RIO is hosted).  Second, it just failed after churning for an hour...I think this is why (from the xilinx log):
    Checking expanded design ...
       'window/theVI/n_0000013E/MiteInterfacex/IrqComponents[0].MiteIrqx/HandShakeIr
       qNum/BlkRdy.iRdyPushToggle_msx' with type 'DFlopBool_1' could not be
       resolved. A pin name misspelling can cause this, a missing edif or ngc file,
       or the misspelling of a type name. Symbol 'DFlopBool_1' is not supported in
       target 'virtex2p'.
       'window/theVI/n_0000013E/MiteInterfacex/IrqComponents[0].MiteIrqx/HandShakeIr
       qNum/BlkOut.oPushToggle0_msx' with type 'DFlopBool_1' could not be resolved.
       A pin name misspelling can cause this, a missing edif or ngc file, or the
       misspelling of a type name. Symbol 'DFlopBool_1' is not supported in target
       'virtex2p'.
       'window/theVI/n_0000013E/MiteInterfacex/IrqComponents[0].MiteIrqx/HandShakeIr
       qAck/BlkRdy.iRdyPushToggle_msx' with type 'DFlopBool_1' could not be
       resolved. A pin name misspelling can cause this, a missing edif or ngc file,
       or the misspelling of a type name. Symbol 'DFlopBool_1' is not supported in
       target 'virtex2p'.
       'window/theVI/n_0000013E/MiteInterfacex/IrqComponents[0].MiteIrqx/HandShakeIr
       qAck/BlkOut.oPushToggle0_msx' with type 'DFlopBool_1' could not be resolved.
       A pin name misspelling can cause this, a missing edif or ngc file, or the
       misspelling of a type name. Symbol 'DFlopBool_1' is not supported in target
       'virtex2p'.
    This is all pretty cryptic...I was hoping you might have some insight.  In the meantime, I'll keep trying to find some consistency in the compile errors.
    Thanks!
    Chris

  • Why a continuous acquisition will stops

    I have download a continuous acquisition program from NI and use PCI-MIO-16E-4 card to tested this program. when choice the sample rate to 10000, if choice the samples less than 100, the acquisition will stop after while. Does anyone known why and have a solution? The buffer of CWAI control was "use default buffer size".

    Hi,
    You are running into buffer overflaw errors; one way to fix this is to increase the buffer size, and/or the number of samples.
    Regards,
    RamziH.

  • Band Pass Filtering during continuous acquisition

    Is it possible to apply digital bandpass filtering to a continuous acquisition using the NI 5112 Digitizer? The measurement filters seem to apply to a fixed length acqusition. The Max Input Frequency does nothing, even in the acquisition example. If this is not possible, how do you select the 20Mhz low pass limit.

    Hello,
    From the information that you gave me, it appears that you are using the niScope Digital Filtering example. This example runs continuously, but there is a fixed number of records that it must acquire for each iteration of the loop.
    If you want to enable the 20MHz filter, try using the function niScope Config Chan Characteristics, and set the Max Frequency to 20 MHz. It sounds as though you have tried this, but you need to make sure you use that funciton.
    Regards,
    Andrew M
    National Instruments

  • DAQ collecting finite samples despite being set to continuous acquisition mode

    Hello,
    I've created a vi which reads data from one channel on my USB 6225 OEM device, displays the data to a chart, and writes the data to a .csv file using the write to spreadsheet file vi. The DAQ acquisition mode is set to Continuous Samples; however it behaves as if it were set to N Samples, as the number of data points written to my .csv file is equal to the number specified in the Samples to Read input.
    I replaced the DAQmx Assistant vi with the Simulate Signal vi and observed the same behavior. Why does this happen?
    Attached below is my vi.
    Attachments:
    chart time.vi ‏78 KB

    When the acquisition mode is set to continuous samples, the samples to read input becomes the buffer size -- not the number of samples read. I expect the DAQ to collect samples until I stop the vi. This is the behavior I have always seen in the past, so don't know why it is any different this time. 

  • Continuous acquisition using PXI 6556

    A test I am performing requires me to perform continuous data aquistion after an intial start trigger, using using PXI 6556. Is this possible? If so could you tell me how? 
    Also, is it possible to fetch data from the PXI memory to the PC while data acquisition is taking place?
    Thank you in advance for your time,
    Best Regards,
    Arjun

    Hi Guys,
    I do know for a fact that Measurement Manager does work properly, and that's part of what makes it so frustrating, I can setup the channels however I want in Measurement Manager and it works properly, but if I don't do anything but change to Labview (or the Agilent VEE software, I've had the same problems there as well) then it doesn't work properly.
    I've been in contact with Agilent support, and they haven't been able to solve the problem for me yet.  As an example, they gave me a small piece of code to try with the Agilent Interactive IO, something like this (I might not get it exactly right, I'm at home this week, so please bear with me!):
    VOLT:RANG 10
    VOLTOL BIP
    VOLTTYP DIFF
    MEAS? (@101)
    And with these steps (inputted one line at a time, obviously), along with a constant 1.0Vdc on channel #1 in differential mode, I get a reading of 999.9, which indicates that it is out of range, but it's not!  If I do get a reading, it's usually between 50 - 60mV, and every once in a while it will read bang on.  I can't think of any further information to give you right now, I'll be sure to post when I do.
    Thanks for all the suggestions,
    Steve

  • Usb-6009 high-speed continuous acquisition for slow control loop application

    Hi,
    After watching a few Youtube videos, I successfully built a control loop in LabVIEW using my USB-6009. Currently, this loop is limited by the speed my actuator can take and respond to commands, topping out at 200 Hz. This is completely sufficient for my application. My question is more regarding the wasted potential of the USB-6009 to acquire samples at a much higher rate than what would be obtained if I used a simple single sample-on-demand during every iteration of the loop.
    It seems to me that having the USB-6009 continuously acquire samples and having my control loop periodically check in for the latest data when it is ready to execute would have the advantage of allowing me to average groups of samples together to lower the overall noise associated with the measurement process (I am reading voltages from an amplified photodiode).
    1) Does anyone know how I would instruct the USB-6009 to continuously acquire at say 10 kHz, so that on each loop I will have 50 or so samples that can be averaged together for a more accurate measurement of my control variable? Unfortunately, I'm new to this and not too familiar with DAQmx Timing.vi.
    2) I've heard that reading into a buffer can increase latency for moving data into the computer. Given the low speed of my control loop, I don't foresee this as being a problem. Is this a correct assumption? I can probably live with an extra millisecond of latency.
    3) I goofed around briefly with DAQmx Timing and managed to see a buffer overflow error. Certain rare events will by necessity cause my control loop to take much longer to execute, so I cannot guarantee that occasionally during normal operation I will not overflow the buffer. Can I suppress this error so that the dialog box does not pop up and the program continues to run uninterrupted? If the buffer overflows and old data gets overwritten it isn't a big deal for me since the control loop is only concerned with the latest data anyway.
    Thanks for any info!

    Howdy Patrick!
    Here is a picture of the front panel:
    Here is the block diagram:
    And I've attached a copy of the VI saved for LabVIEW 7.1.
    Regards,
    Barron
    Applications Engineering
    National Instruments
    Attachments:
    most recent samples.vi ‏73 KB

  • How to use AI acquire waveform.vi for continuous acquisition

    Hello all,
    I am using LabVIEW 5.1 and PCI-6023E to acquire a voltage signal continuously, display the acquired data on a chart(display one minute of data at a time)then save all the acquired data to a spreadsheet file.
    When I used the random number as a signal to develop my program; everything has worked as expected. However,it is not working now as I replace the random number with a real voltage signal using the AI Acquire Waveform.vi. I have encounterd several problems:
    1/ Only display one second of data at a time.
    2/ The elapse time that I have calculated does not match with the time display on the chart.
    3/ The program runs very very slow when I increase the number of scans
    to acquire to 1000, but my program need to acquire the signal for 15 minutes at a rate of 50Hz(50sample/second); it is about 50,000.00 samples.
    Do you have any idea how should I do to make it works? I am a novice in LabVIEW; any help would be greatly appriciate.
    Hao
    P.S: I've attached my program if you want to take a look at them.
    Attachments:
    Acquire_Using_Random_Number.vi ‏89 KB
    Continuous_Acquire.vi ‏96 KB

    Helleo Labviewguru,
    Yes, I did tried to see those examples but I could not display on a chart nor store to an array and save to a spreadsheet file when I used the AI Config.vi, AI Start.vi and the AI Read.vi(in a while loop). Can you please help me with this.
    Thank you in advance.
    Hao

Maybe you are looking for