Waveform-oscilloscope

i've extracted a waveform graph from a sound file.
is it possible to plot this graph in an oscilloscope?
Attachments:
check for max.vi ‏29 KB

You may be able to upload the file to the oscilloscope and open it (the data) using the scope.
But do you really want to do that? 
Can you describe what you are trying to achieve?

Similar Messages

  • DAQ doesn't show the input waveform in Labview as it is in oscilloscope.

    Just bought a PCI-6035E DAQ board + CB-68LP connector and testing it by inputing a square/triangluar/sine wave from a wave generator. In MAX, I can see the waveform as in the oscilloscope. However, when I try to see this input in Labview by using the Waveform Chart VI, the displayed waveform becomes an arbitrary one. Why is it happening and how can I correct it? I'm a novice in this field, so your advice would be highly appreciated.

    Seems that there's something missing in connecting to the daq card: in most cases this situation occurs when the signal reference is missing. When you input a signal in an oscilloscope, you wire both a signal and its reference (ground or similar), otherwise you see nothing than noise and disturbs.
    With a daq card things are a little more complicated 'cause you have a more flexible and more universal instrument than an oscilloscope; you must decide which type of connection to use: referenced- or not-referenced- single ended or differential connection, which channel(s) to use... and the configurations in MAX and in labview must match if you want to simplify your job.
    I suggest you to study carefully the card user manual when it describes the analog input w
    iring and all the consideration about different types of connection. My experience is that in most cases the differential input is better to reduce signal noise and reject disturbs, but you must use 2 channels per signal...
    You can also look at this tutorial about wiring an input signal:
    http://zone.ni.com/devzone/devzoneweb.nsf/opendoc?openagent&2E07CE2019CCB1D3862568650057930A&cat=99368070225FE073862567E6006C8DD7
    You're entering a (slightly) complicated but (very) interesting world. Good job!
    Roberto
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • How to calculate de area of a waveform in LabView with the oscilloscope Tektronix TDS380

    I have a question about a mathematical algorithm. I am using the Tektronix oscilloscope model TDS 380 and since now I have been taking measurements peak to peak, putting in the labview program MEASU: MEAS1: VAL?
    I am interested in calculating the area of the waveform, and the instruction manual for the Tektronix TDS 8000 found the command MEASU: MEAS1: TYPE AREA. This command is not in the manual for the model TDS 300 and therefore do not know if you can apply FOR IT. When I insert it I get the error code -1073807339.
    My question is: would it be possible to calculate the area with my oscilloscope TDS380 somehow and with LabView? Is it possible to apply the algorithm or can be done differently?

    Sorry about not posting. I'm on a business trip right now. Here's the VI, though.
    Attachments:
    get_second_derivative.vi ‏56 KB

  • Bad resolution waveform transferred from Lecroy oscilloscope to PC

    Hello,
    I am currently using Lecroy WavePro 7300A to analyze waves. When I tried to acquire the waveform from this oscilloscope to my nearby PC via Ethernet cable (using VICP::x.x.x.x as VISA address) I got problems with the resolution of the waveform picture.
    In fact, as you can see from my attached pictures, the BadRes.jpg picture represent the captured waveform when the vertical scale of the oscilloscope was set to 50mV/div and the GoodRes.jpg represent the waveform when the vertical scale was only 10mV/div. The peak value of the waveforms is around -12.5mV to 12.5mV
    It is quite obvious that the main trends of the two waveforms captured are the same, but from my point of view, it is like you have 2 pictures of the same scene and size, but one of them has only 1 megapixel resolution, and the other one has 5 megapixel, so the second one looks sharper when the size of the pictures is large enough.
    Consider the LabView VIs, I have enclosed my GetWave.vi as you saw in the pictures, and all other the sub VIs either comes from the default VIs (when install LabView), or VIs from the installation of LabView Driver CDs, or VI from the installation of Lecroy Drivers  "lcwave" and  "LeCroy Wave Series". I am currently using LabView 8.2.
    Finally, I would like to ask if there is any to get a good resolution of the waveform even when I set the vertical scale of the oscilloscope to very large, say 100mV, for example.
    Thank you for your reading.
    SG.
    Attachments:
    GetWave.vi ‏40 KB
    BadRes.JPG ‏119 KB
    GoodRes.JPG ‏118 KB

    Hi - Alan from LeCroy Tech Support here...
    Let's start with the 10mV/div setting.  With a signal that is 25mV peak to peak, you are only using about 31% of the scope's full scale range. (31% = 25mV / (8divs * 10mV/div). When you change to 50mV division, you are only using 6% of the full scale range.  The resolution drops in the same way;  the scope is an 8 bit digitizer over the full scale range.  31% of this range is = 0.31*255 = 83 levels;  6% is only about 15 levels.  This is what you are seeing in your images; the volts per ADC code increases by a factor of 5 when you change the gain from 10mV to 50mV.  Since your signal is small compared to full scale, you don't have much resolution.  In general, you always should use as much of the grid as possible to get the best resolution.  See LAB WM308 for more information and examples: http://www.lecroy.com/tm/library/LABs/PDF/LAB_WM308.pdf
    Note that Scope Explorer can retrieve the volts per ADC code.  Go to the Traces screen, right-click on a channel, and choose "Show Trace Properties". For 50/div, the vertical_gain is only 0.00220973 (2.2mV per ADC code). For 10mV/div, the value is 0.000441946  (442uV).
    Feel free to contact me for more discussion!
    Best Regards,
    Alan
    Alan Blankman, Technical Product Marketing Manager and LabVIEW Developer
    LeCroy Corporation
    800-553-2769 x 4412
    http://www.lecroy.com
    [email protected]

  • Acquire waveforms from function generator to oscilloscope

    I have a problem. We constructed a virtual function generator and a virtual oscilloscope. It's working well, the oscilloscope is displaying the (almost) correct data. My problem is that the waveform displayed in the oscilloscope vi is always sine, although the selected waveform in the function generator is already different.
    I should replace the constant 'zero' with something so that the cases will change in order for my oscilloscope to display different waveforms. Is there a way to acquire the values of the constant enum, for instance, from another vi to this vi?

    Yes, you would need to replace the constant with a control. Once you do this, in the main VI you simply do a right click on the subVI's terminal and select Create Control/Constant that but you cannot change it as the subVI runs.

  • Acquiring Agilent 54642D Oscilloscope Waveform AND Settings

    Hi,
    I would like to use LabVIEW to capture the waveform already displayed on the screen of my Agilent Oscilloscope (model 54642D). With this waveform, I would like to obtain the current settings of the oscilloscope-channel as well (volts/div, time/div, probe atten., delay, offset, cursors with freq/period, etc.). In other words, I acquire a signal with the scope (not LabVIEW), adjust the scope settings to my liking on the front panel of the oscilloscope, and then I would like to capture the exact waveform displayed on the scope screen WITH the settings of the oscilloscope.
    I have been using the project-style driver, found here: http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=724
    This works for controlling the oscilloscope settings and acquiring a waveform, but it's not what I want. I simply want LabVIEW to capture the current state of the oscilloscope display and settings used.
    Thanks much,
    Brad
    Solved!
    Go to Solution.

    I couldn't find any of the commands in that manual.  There's should be a programmer's manual somewhere.  In it will be SCPI commands that you can send via VISA.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • How to acquire reference waveforms from Tektronix oscilloscopes

    Hi,
    I want to acquire stored waveforms .wfm from oscilloscope to LabVIEW for analysis purpose.I tried by using Tek scope drivers,but gives error. what is the appropriate way to do it. Plz help...
    Thanks in advance.
    sayaf.

    Use Tektronics Programer Manual. Find All GPIB commands and there find what command to acquire waveforms. Usually, you write GPIB command and read response from Tek.

  • Waveform collect lecroy oscilloscope

    I'm just working on lecroy oscilloscope. I've to save waveform which is averaged by oscilloscope. Then I've few seconds delay and it will continue like this way. Then I've to integrate all graphs and have to save in pc.
    I can do everything but my vi shows error  when I want to attach unbundle function in my vi and also i couldn't connect this function to read waveform vi. Pleae help me if anyone has some idea.I'm new in labview. 
    Best regards
    Abdul

    I wrote this program for another oscilloscope but i've to change for lecroy oscilloscope where read waveform.vi will change and all other necessary changes . But when i add read waveform.vi which is for lecroy oscilloscope, i couln't connect unbundle and others. Please give me a brief description and if you have idea how would i change this vi for lecroy or you can do it and upload for me. I'll be grateful to you.
    Attachments:
    TOF-MS_delay Mih_Jul_2007_30.vi ‏200 KB

  • How to display current waveform on oscilloscope?

    Hi
    sorry if i asked in a wrong place
    i know Oscliscope only shows Voltage waveform but i heard you can do current too
    can anyone help me to do that for this circuit on Multism
    thank you
    Attachments:
    GHFR.ms12 ‏219 KB

    The current probe is on the instrument toobar.  You place the probe on a wire then connect it to the scope to it, now the scope shows current instead of voltage for that channel.
    Tien P.
    National Instruments
    Attachments:
    current.PNG ‏28 KB

  • Trouble capturing waveform from PXI-4472

    I'm really a very green newbie at this stuff, so bear with me...
    I've got a PXI-4472 data acquisition board and a PXI-5411 waveform generator. I've connected the arbitrary out of the 5411 to the channel 0 in on the 4472. An external oscilloscope shows a 1v-amplitude sine wave being generated.
    I created a very simple VI to show what the 4472 is capturing. It connects a NI-DAQ channel I generated to the standard "AI Acquire Waveform.vi", then out to a Waveform Chart, all within a while loop with a Stop button. Problem is, all the waveform chart seems to be showing is the running average of the waveform instead of the form itself (solid line, a tad above zero).
    I can hook the 4472 input channel up to a DC-out power supply, a
    nd when I vary the voltage, the waveform chart changes as well.
    So my question (whew!): What's wrong here that's not allowing me to capture a waveform from the 4472 (in turn from the 5411) and display it on my waveform chart?
    Thanks in advance for the help.

    Never mind.... it was a sample rate problem. I upped the sample rate and it came out ok.

  • How do I give a separate task ID to two compute waveform sub vi's running sumiltaneously in one vi?

    I'm running two compute waveform sub vi's in one main vi. The idea is to output two signals that I can vary independently to each other but when I hook LabVIEW up to a Oscilloscope, I only get one output and the other is just a flat line. I noticed that I'm unable to modify the subvi's independently ie: I change the duty cycle on one and its changed on both of them. Do I need to assign a separate task ID? If so, how do I do this?
    Attachments:
    analogtriggerattmemptwith2outputsignals_2.vi ‏247 KB

    Hello;
    In case you are outputing two waveforms to two analog output channels, you don't need to have two task IDs to accomplish that.
    In case you want to vary one of the two waveforms and keep the other one stable, you can juct modify the buffer array of data points that will be output. Once you configure a analog output channels for two channels of the same DAQ device, you first setup a buffer of data, and such buffer is formed in a way that first data point goes to channel 0, second data poing goes to channel 1, third data point to channel 0 again, fourth data point to channel 1, and so on. That means you can alter only the data points that correspond to one of the channels, while keeping the other ones fixed. That will make only one analog output channel t
    o change.
    Hope this helps.
    Filipe A.
    Applications Engineer
    National Instruments

  • Is it possible to get 2-ch signals from TDS2012 oscilloscope at the same time with LabVIEW "7.0"?

    Hi, everyone.
    I've been trying to get the signals from 2-ch of Tektronix TDS2012 oscilloscope at the same time using IVI connection with LabVIEW "7.0"
    I've already searched this developer zone for the answer.
    I've tried the famous example: "IviScope - Acq Dual Wfm Edge Triggered.vi"
    and it gave me the error message like:
    Error -1074110451 occurred at IviScope Initialize With Options.vi
    Possible reason(s):
    Driver Status:  (Hex 0xBFFA600D) Primary Error: (Hex 0xBFFA600D) The Config Server module is not present on the system.
    I think I've installed all~ the required softwares for IVI. For example, ICP 2.2, IVI engine 2.0.46, and tktds1k2k ivi (instrument driver for tds2012, in fact this one is for LabVIEW "7.1"... :-P)
    TDS2012 and my computer is connected through HPIB(GPIB) and it is shown on the MAX (a GPIB instrument as well as an IVI hardware asset)
    I've tried GPIB connection but it gives me asynchronous signals...
    Is it possible to get 2 signals at the same time with LabVIEW 7.0(not 7.1 or higher) by any means?
    What in the earth is the "Config Server" in this case?
    I don't need to sticking to IVI and any method to achieve my goal will be welcome.
    Could anyone give me the hint for this problem, plz?

    I think your problem is that the instrument specific driver is version 7.1 and you are using the class driver with 7.0. You can create your own 7.0 driver by downloading the LabWindows driver and using the Import CVI Instrument Driver under the Tools>Instrumentation menu.
    Since you don't seem to have a good reason to use IVI, why don't you try the native LabVIEW driver at http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9139659CE034080020E748.... I believe you have all of the functions to setup each channel and then when you trigger the scope, both channels will be captured. You would then transfer each waveform separately. The data is always read sequentially but that's not important as long as both channels are triggered at the same time.

  • Has anyone "zoomed in" on a portion of a waveform graph?

    Has anyone ever used two cursors to zoom in on a portion of a waveform graph?
    I've seen that newer Oscilloscopes offer features to do this both horizontally and vertically. 
    See the attached jpg for an example of what I'm trying to do.  It is from Google Finance.  Notice the area circled in red.  The two cursors define the portion of the waveform to be displayed on the main graph.  There is also a scrollbar beneath them which allows the user to quickly move the zoomed-in area across the graph- I would love to have that functionality on the LabVIEW graphs. 
    My first thought is that I can do this using mostly property nodes.  Not sure on vertical zooming scrolling the horizontal zoom- I'm thinking maybe this would best be done using scrollbars which are not part of the graph itself. 
    Any ideas or comments?
    Thanks,
    Dave
    Attachments:
    deleteme.jpg ‏38 KB

    Cursor position is available in Labview via a property node. You can also set about every chart property with property nodes. I have used this many times. Here is a trick. If you have two cursors, Make separate arrays of the x and y  positions. Then  use the "Array max&min" to sort them. This will make your program independent of the cursor sequence.
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • Writing waveforms from Ch. 0 of niSCOPE to binary file in a multi-record setup?

    Hello,
    I am not very experienced with niSCOPE and writing waveform records, so I need some expert help here.
    Here is my application:
    I am generating a pulse train using a 6602 counter/timer. Each rising edge of this pulse train triggers an niFGEN to generate a single sawtooth waveform output to another device and, at the same time, acquiring data from Ch. 0 of an niSCOPE. I am fetching one record per rising edge of the pulse train for the niSCOPE (multi-record setup).
    The attached VI is where I am at thus far. All triggering and reading/fetching of the waveforms seems to be working just fine when testing with an oscilloscope. I now need to save each waveform record along with the timestamp of its rising edge trigger to a binary file. The bottom of the VI is where my attempt is at saving the waveforms to a binary file, so the attention should be there when looking at it.
    I am running LabVIEW from a computer connected to the NI PXI-Chassis using a cross-over cable.
    Questions:
    1.) Do I need to convert the data coming in on Ch. 0 of the niSCOPE to digital? Does it come in as analog from an oscilloscope? If I need to do this, how can I accomplish this?
    2.) When I try to run an example VI to write a waveform to a binary file by choosing "My Computer" in the bottom left of the VI window, it works it saves the file just fine. When I change this to run on "PXI2", a file is not even created and I get an error on File Dialog (code# 7, I think) each time the file is attempted to be closed. This may be a stupid question, but why can I not save data to a file on my computer if running the VI on "PXI2"?
    3.) Assuming the saving of each waveform to a binary file is working (read: (2) is successfully addressed), how can I also write the timestamp of the starting trigger for the waveform along with the waveform in the binary file? An example VI of how I can accomplish this would be fantastic, but I haven't been able to find one thus far.
    4.) When I was messing around and trying to accomplish this, it seemed that doing this writing may slow down the entire process too much. I need to record data to the extent of the sawtooth waveform generated by the niFGEN AWG for each trigger. Is there any changes I should make to my acquisition process in the niSCOPE section so that I can read each waveform, along with keeping the timestamp for each, and write this information to a binary file?
    I need to get this working quickly, so any help on this is greatly appreciated. Thanks in advance.
    Attachments:
    5124_update.vi ‏157 KB

    Thank you so much for your reply, David. Let me try and explain my
    situation and setup a little better, as well as discuss the points you
    made in your reply. Beware, you may want to refill your coffee as this
    post is long .
    I am using an embedded controller in a PXI-1044 chassis. I now have the
    chassis hooked up to our local network, and I am deploying my project
    to the chassis over the network as I am also connected to the local
    network. I have an oscilloscope next to me that takes as input the
    pulse train for a trigger and the generated sawtooth from the niFGEN
    for each trigger (rising edge of the pulse train from the 6602
    counter). Just to make sure synchronization is taking place, the
    sawtooth is also fed as input to the niSCOPE for acquisition.
    "PXI2" is what shows up when I choose to run a VI on the PXI chassis
    rather than "My Computer"; not sure why the 2 is there either, but that
    is what it says. I may have tracked down the issue I was having with
    writing, but more about that a little later...
    The attached VI is an update, although not much has changed. My
    application design is like this (keep in mind that some values for VI's
    are still constants in the block diagram while others are controls on
    the front panel): I am using the 6602 to generate a 1 KHz pulse train
    and routing this pulse train to PXI_Trigger0/RTSI0. I am also using the
    PXI_Clock (10) as a sample clock for this, and also using this same
    clock as the reference clock for both the 5422 and the 5124 (as per the
    synchronization help file mentioned for synchronizing multiple
    devices). Both the 5422 and the 5124 are triggered by a digital rising
    edge (from the pulse train) on PXI_Trigger0/RTSI0 (as it was routed
    there). For each trigger, the niFGEN generates a sawtooth waveform
    using a stepped trigger mode and outputs it. For each trigger, the
    niSCOPE acquires data. They are both synchronous, which is tough to see
    since one has its trigger source on the front panel and the other has
    its trigger source on the block diagram. All devices use PXI_Clock so
    they are synchronized.
    The expected behavior is to only generate a single sawtooth waveform
    per trigger with a certain number of sample points. I want to acquire
    the same number of samples using the niSCOPE, which is what I meant by
    "the extent of the waveform" in my previous post. So, should I change
    the 8192 to 1000 for the number of samples for the niSCOPE? What would
    you recommend for the sampling rate? I have been using 5 MHz for the
    niFGEN and 5 MHz for the niSCOPE...this is how it should be done,
    correct? If it is different in the VI, please let me know. For some
    reason, I have to adjust all of the values each time I open it since
    the default values are not the ones I want.
    I want to generate and acquire one waveform per trigger (one waveform
    per record). However, I want to be able to record a large number of
    records so I have enabled the circular buffer-like treatment of the
    acquired waveforms. The 100 or 1000 records is actually just a number I
    am giving it for now to make sure it is working before recording many
    more records.
    As for saving the niSCOPE data, I would like to save all data in a
    single file that is NOT ascii (to save space). I have been looking at
    the HWS file format, and would like to use it. I think the attached VI
    includes this at the bottom of the while loop. For each trigger, I
    would like to save the time (as accurate as possible) that the trigger
    occurred for the record/waveform, which appears to be (absoluteInitialX
    - relativeInitialX) as you said in your post (thanks!). I just need to
    store as much information about the waveform and time information for
    it as possible with the waveform in the file. So it looks like I will
    need to use the wfm info for that information, providing portions of it
    as waveform attributes in the HWS VI's?
    What format of data do you recommend I fetch, and will I be fetching a
    "Single waveform" or "Multiple waveforms"? Should I use I32, DBL, WDT,
    or other for the format? A balance between good precision in values and
    time it takes to fetch/record would be best.
    Given all of the above, I am having one troube with saving data to a
    file. As a reminder, I am deploying the project to the chassis over the
    network. When I choose a location and/or file to save the HWS data to,
    I only get choices that are on the PC's hard disk (such as C:\Documents
    and Settings\cgifford\...) NOT the chassis's hard disk. When I choose
    something other than "C:\" I get an error that the file could not be
    opened. However, when I choose "C:\" everything goes fine. The saved
    data is nowhere to be found on my PC though, so I am assuming that it
    is being stored on the internal 60G hard disk in the chassis that must
    be named "C" by default or something!?
    I have been told by phone support that I should be able to make a
    direct connection with the chassis just like another PC, and should be
    able to access the information on its internal hard disk in a drag and
    drop fashion. I however cannot directly connect to the PXI chassis to
    get the data that has been saved on the hard disk. We are running
    Windows XP on the PC. We did some poking around and noticed that the
    chassis is not running Windows file sharing, and only has ftp and http
    running. We tried to access it using ftp, but we didn't have a username
    and password to supply it. So, how can we enable Windows file sharing
    on the chassis? How can I connect to it to do drag and drop to get
    saved waveform data off of it? This is the main problem I am now
    facing. Eventually we would like to store data to an external hard disk
    connected to the chassis, which assumes that I can have access to the
    internal storage to tell it to save files to the external hard disk.
    For now saving it to the internal hard disk is just fine until
    everything is proven to work, but I would like to get the data off of
    the internal hard drive to put on another computer.
    Any answers/suggestions on my above questions are greatly appreciated.
    I also want to thank you for reading this long post . I eagerly await
    a reply. Thanks again in advance.
    Chris
    Attachments:
    5124_update.vi ‏143 KB

  • How does buffer size affect double buffered waveform generation?

    I had originally posted the following question:
    "Why does the double buffered waveform generation pause after the first buffer before continuing?"
    "I am using an AT-AO-10 board to generate a multiple channel waveform in double buffered mode. The board's DAC's are updated by an external clock signal. While the waveform generation performs well, I notice that after the first buffer has been generated there is a time delay before the next buffer is output. However the second buffer and thereafter perform well without any time delays. If anyone can provide me an explanation on why this happens I would appreciate it. I am using NI-DAQ API functions to generate the waveforms and my settings for the WFM_DB_Config function are 1 for oldDataStop to disallow regeneration of data and 0 for partialTransferStop to not stop when a half buffer is partially transferred."
    -posted by Vadi on 6/7/2001
    I received a response from Geneva as follows:
    Geneva L. on 6/11/2001 says:
    "Vadi,
    The first thing is to make sure that you have the latest version of NI-DAQ installed, NI-DAQ 6.9.1. If you need to install it, make sure you completely uninstall any prior versions. Then, you will have examples installed in either the NI-DAQ or the CVI directory. In the AO directory, you should find the WFMdoubleBuf example.
    Start with that to make sure the output appears as you expect. Then, you can modify it to apply your external update clock, following the idea presented in the WFMsingleBufExtUpdate example. You might even want to double-check that your external clock acts as you expect using an oscilloscope.
    Finally, modify the example such that you can update on multiple channels, remembering that you interleave each channels buffer into one buffer for WFM_DB_Transfer. Whatever data is in the buffer will be updated on the output channels.
    Regards,
    Geneva L.
    Applications Engineer
    National Instruments"
    I have checked my version of NI-DAQ and it is 6.9.1. I am generating the double buffered waveform according to the format shown in WFMdoubleBuf and with some modifications from WFMsingleBufExtUpdate to allow me to use my external update clock. However I continue to notice the same phenomena again and again. For a buffer size of 7500 or 10000 points there is a time lag meaning after the first buffer has been output there is a noticeable time delay before the second buffer and buffers there after is output. This time lag doesn't exist for the buffers that are output after the first buffer but it does exist for the first buffer. When I decrease the buffer size down to 5000 points the time lag disappears (Note: this phenomena also occurs when I use an internal time base as opposed to my external clock). Is there a reason for this? I am using a AT-AO-10 board and I know the on board FIFO is 1024 points deep. However from the documentation provided it doesn't indicate that double buffered mode uses the on board FIFO at all. In fact, the functions require that the FIFO mode be turned off (in WFM_Load) for double buffered waveform generation. Is there a reason why when the buffer size is increased that there is a time lag after the first buffer? Is this because of the functions themselves or is this because of the AT-AO-10 board?

    Vadi,
    Make sure that your buffer size is set to the same number of points that you're actually writing to the buffer initially. For instance, if you run the example as-is, the NIDAQMakeBuffer puts exactly the ulCount amount of data into the buffer. Then, it continuously writes out half buffers. Thus, if you are not writing enough data to fill up the buffer the first time, there will be that lag until the section where half buffers are output.
    Regards,
    Geneva L.
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

Maybe you are looking for