Lecroy oscilloscope multi pulse acquisition

Hello, I am working with a Lecroy 24Xsa oscilloscope to acquire a waveform with multiple pulses connected to computer over TCPIP.  I have used the labview drivers and example code provided by Lecroy and am able to capture the wave and save it to my computer, but capturing the whole wave at once results in too low of a resolution.  The problem comes from the fact that the multiple pulses are of varying amplitudes across a relatively long time frame.  Is there a way to change the vertical resolution and shift along the x axis, while keeping the timing in order to accurately record the pulses time and amplitude?
Thank you in advance for your help

Hello,
You can use a zoom trace to zoom in on a single pulse.  This will give you better resolution.  Be aware that the zoom uses the lowest resolution that it is set to.
This means that zooming out, will change the resolution (Just like changing the vertical scale on the input channel) but zooming back in will not increase it again, you would have to turn it off and zoom again.
The easiest way to zoom is to use a mouse or the touchscreen and simply draw a box around the section of the signal you want to zoom to.
Then you can grab the data from the zoom trace.
NYC is correct that this is not a LabVIEW issue and should not be on the NI forums.  If you have more questions or are not sure how to setup the zoom etc.  you may give me a call or send me an email and I am happy to help!
Cheers,
Leonard Brown
Applications Engineer
Teledyne Lecroy
[email protected]
1-800-553-2769 (Extension 6088: 8am to 5pm Pacific Time).

Similar Messages

  • Multi-buffered acquisition with digital trigger

    I have a PCI-MIO-16E1 and I need to do three channel (250KHz/channel - ~400 scans/trigger) multi-buffered acquisition with digital trigger (trigger => 30 Hz).
    I could not find any example of multi-buffered acquisition. Could anybody help me?

    Hello,
    I assume that you are refering to a retriggering setup where each time you recieve a trigger you take 400 samples on each channel at a rate of 250kHz per channel (total scan rate = 3CH * 250kHz = 750kHz).
    In order to keep the system hardware timed you can use the two counters on the board to produce a retriggerable pulse train that will act as your scan clock. For example each time the counter recieves a trigger it will output a clock signal of 750kHZ with 400 or so pulses in order to take ~400 scans/trigger.
    This clock signal can then act as the scan clock for your 3 channel analog input operation.
    Now we have to figure out how to set up the retriggerable pulse train from the counters and have the analog input use the counter output as a sca
    n clock.
    Good thing there is an example that is already written
    http://zone.ni.com/devzone/explprog.nsf/6c163603265406328625682a006ed37d/aab61e455564a04d862568930018e725?OpenDocument.
    Good Luck.

  • Important question: I have got a PXI-4472 and I am able to do single-channel acquisition. How does multi-channel acquisition work?

    Look at the VI: it is quite eleborate, but the crucial point is Data Acquisition and Trigger&Gate (and, consequentely, Write to File operation).
    I can add plot on the Waveform Graph DATA, this is rather easy, simply adding the channel numbers in the channel control (es. writing 0,3,7 will collect data from the three channels).
    First question: is this operation of adding plots correct?
    Second question: does the sampling rate dwindle when I consider multi-channel acquisition? I mean: 1 channel-->100KHz ; 2 channels-->50 KHz
    More over, and MORE IMPORTANT: is it possible to set different trigger conditions for different channel
    s? How can I control this operation?
    Third: can you have a look at the VI as all (the appearence, the functionality, the logical sequence...). I am looking forward to get your advice. In particular:
    Look at the frontal panel: what do you suggest to make it "smaller"? More tab controls?
    Look at the Block Diagram: do I have to connect ERROR IN and ERROR OUT to every suVI or function that makes this connection possible (as Trigger&Gate and Write File)?
    Attachments:
    Start&StopTrig_SpectralMeas_style+image.vi ‏700 KB

    First: yes, the operation is correct.
    Second: yes again. When you consider a multi-channel acquisition, your sampling rate must be shared among the channels.
    Third: when you specify a list of channels you want to acquire from, the channel considered for analog triggering is the first you put in the list.
    Connect the error clusters whenever you can,in particular when you are dealing with I/O operations.
    Bye!

  • How to do multi-buffered acquisition on NI-6115

    I need to acquire multiple sequential arrays of data over a single channel using an external clock and a digital trigger (~1000 arrays total, 1000 samples/trigger, external clock frequency 500kHz, trigger frequency 250Hz). It is important that the sampling start right after every trigger, and that I do not miss any triggers. I can already do this using simple buffered acquisition with the ai start and ai read vis in a loop, except it misses triggers while the loop re-starts. Is there any way I can define a buffer large enough to hold all of the samples I need, then to have it read only the number of samples I want after each trigger into this large buffer? I don't need to see the data until the whole acquisition (1000 x 10
    00 samples/trigger) is over. Is this what multi-buffered acquisition does? I cannot find any literature on the NI site related to multi-buffered acquisition. Thanks for any help.

    So every 4 msec you get a trigger signal that should initiate a 2 msec acquisition (1000 samples at 500 kHz sampling rate)?
    There's an example of a way to use your board's counters to support retriggered analog acquisition here on the NI site: Retriggered Analog Input Example. The code may look a little complicated, but the basic idea is described pretty well.
    The goal is to make sure the timing is handled in hardware so you don't miss triggers while doing the software reprogramming. AI Start would be called only one time prior to your loop, and only AI Read would be calle
    d inside the loop.
    Just be careful about your timestamp info. The analog acq. task won't have any "awareness" of time intervals between samples. It'll be up to you to slice up the data into appropriate chunks. You can probably do this by simply requesting the right number (1000) from AI Read.
    Good luck,
    -Kevin P.

  • 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

  • LeCroy Waverunner 640Zi -- Data Acquisition

    Hello... I am trying to set up my waverunner oscilloscope with LabVIEW SignalExpress for data aquisition. 
    Steps I have taken thus far:
    1. Pulse generator hooked to scope for signal generation
    2. USB from scope to Computer with LabView installed
    3. Downloaded lecroyscope driver 3.2.9-x64
    I turn the scope on, and plug in the USB to the computer and SignalExpress starts up. 
    a. start using data aquisition
    b. add step/aquire signal/ IVI aquire/ IVI scope aquire
    c. create new IVI session .. resource descriptor (I choose my USB device "USB0::0x05FF::0x1023::2812N61507::INSTR"), I select the correct driver (lcscope), and I don't click enable simulation data, hit ok
    d. I keep getting configuration errors
    e. Did research.. some forum said to goto MAX, find drivers and unclick Cache and Interchange Check
    f. Trying to initialize ... still get config errors. 
    g. Back to MAX .. change simulate with specific driver. 
    h. Initialization works... NO errors, BUT no data is being aquired. 
    PLEASE HELP ! 
     

    Hello,
    Sorry to jump in so late, I have been out of the country for a while and am still catching up on things in my office.
    I think you are looking for someone to say "yes, you can connect to the scope with NI-MAX and the VISA Interactive Tool, and here is how to do it"
    A few things:
    The LabVIEW driver for XStream scopes is the right one.  It works with all of the TeledyneLeCroy Windows based scopes.
    As I see was already pointed out. (I will give Kudos soon), the scope must be setup to use the USBTMC interface.  To do this, go to the Utitlites pulldown menu on the scope and select "Utilities Setup..." on the tabs that appear at the bottom of the display, select the "Remote" tab and ensure the interface type is set to USBTMC.  This will also show you the VISA resource (I see it in the title of the VISA interactive tool image shown in a previous post).
    Once this is selected, the PC should detect the USB connection and install the device. (you can see it in your device manager as a USB Test and Measurement Device:
    Once this is done, you can then go into NI-MAX and it will detect and show the resource.  You can now communicate with the device:
    If you have any challenges, feel free to give me a call and I am happy to walk through this over the phone.
    Regards,
    Leonard Brown
    Applications Engineer
    Teledyne LeCroy
    1-800-553-2769
     

  • MAX keeps crashing while trying to locate lecroy oscilloscope

    MAX keeps crashing on me while I try to find my oscilloscope over
    ethernet.  WINXP, LeCroy 454, LabView 7.1, NI VISA Server
    3.3.  I can connect to the scope with TightVNC.  If I select
    the scope in the MAX menu tree.  I get a very long hourglass, then
    crash of MAX.  MAX actually crashes a lot.  Is that common?
    thanks,
    Cullen
    LabView 6.2 for Linux running on Ubuntu (Debian) with 2.6 Kernel
    Labview 8.0 for Windows running on XP, IMAQ 3.6.0, NI-1428, NI-1430, NI Camera Link I/O Ext Board

    Cullen,
    Sounds like you might have two separate issues.  First if MAX crashes a lot, I would recommend that you try to repair the installation of the drivers you have installed on your computer, as well as MAX.  This can be done pretty easily by going to Add or Remove Programs then selecting National Instruments Software and clicking Change.  This should bring up another window where you can select the different programs to repair.  Hopefully once you have done this you will no longer have problems with MAX crashing. 
    After looking around a bit for more information about using the LeCroy 454, I found that it is recommended to install the IVI drivers for this instrument to communicate using TCP/IP.  These drivers use the LeCroy VISA to communicate, and may explain why you are unable to get MAX to recognize the driver and why it crashes.  I would recommend trying to install the IVI driver for this instrument and see if you can get it working after that.  The IVI drivers are maintained by LeCroy and can be found at the following website. 
    http://www.lecroy.com/tm/Library/Software/LabView/LabViewDrivers.asp?menuid=8
    Hope this information helps!
    Andy F.
    National Instruments

  • 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]

  • DL9000 series oscilloscope: N-single acquisition

    Hey all,
    I'm running a Yokogawa DL6104 oscilloscope through LabVIEW with a Yokogawa DL9000 driver (which supports model DL6104). I'm trying to acquire several waveforms using the N-single acquisition mode through a revised Edge Triggered Acquisition.vi example, wherein I created controls for the trigger's -mode and -counts on the YKDL9000 Config Edge Trigger sub VI.
    Still, I'm getting no luck. I receive this error:
    YKDL9000 Error Query;
    instrument reports:
    662,"Acquisition in process in N Single trigger mode. Press Run/Stop key or wait until the process is completed."
    0,"No error"
    Can anyone help guide me to what my mistake is, and perhaps direct me to resolving the problem?
    Big Thanks!
    - Ryan

    Okay, here are the screen shots: (1) the edge trigger example _ unaltered (2) my alterations and (3) my alterations illuminated with the error code I'm now getting.
    Attachments:
    Edge trigger - unaltered.png ‏120 KB
    Edge trigger - altered (no reset, no control of vertical or time axes, multiple waveform acq.).png ‏169 KB
    Edge trigger - altered (no reset, no control of vertical or time axes, multiple waveform acq.) _ error.png ‏193 KB

  • Pulse acquisition

    Hi!
    I'm trying to build a project that measure the pulse of the heart. I have succesfully get the pulse signal into the computer through the PCI-card 6014. I have used the example VI: Cont Acq&Graph (buffered).vi Now can I "print" out the pulse in the graph in "real time" but I also want to measure the frequency as a mean value every fifth second. How do I do that if I set the scan/sec and scans to read a time to 1000. I want to update my graph as fast as possible, not only every fifth second.

    What you try to do really requires a point-by-point acquisition. If you don't have access to LabVIEW-RT you can try to acquire continuously with a very smaller buffer size (ideally one point). You may have to reduce your sample rate to keep the pace.
    Then pass your point-by-point acquisition to a waveform chart. You can choose different display modes for a chart incl. "Scope" and "Sweep" modes.
    I've attached a demo VI that shows the concept. The VI produces a point-by-point sine tone and measures the frequency every N (in my case 1000) points.
    Attachments:
    Waveform_Chart_display_and_Waveform_Analysis.vi ‏37 KB

  • Multi sockets acquisition on 6259 lead to dummy data.

    Hi
    I have a 2 sockets parallel run sequence with only one DAQ card, everytime if I just run only one socket, the acquisition result is correct, but they are mostly wrong when the two sockets runs at a same time, the results are so far away from limits, I know this is caused by the two sockets manipulate the card at same time, but any way to solve it.
    Thanks very much.
    *The best Chinese farmer*

    Hi Sam R
    I am using customized parallel model but just a little changes from original.
    Every step of LabVIEW code to access DAQ dose open a new task and close the task when finish the step, and the driver is DAQmx, NI said it is multithreading safe, but I still need to lock the DAQ access blocks otherwise the card often crush.
    But now I have locked related blocks regardless it is DAQmx, the sequence is better. The same case happen at serial port, if one socket have a long time reading of RS232A, another socket often has error, when I reduce the timeout time from 5 to 1, the serial ports are better than before, but still has error sometimes, I guess the two serial port has only one controller chipset.
    Another case is the DMM read step type can often not get value, see attachement.
    Thanks very much. Sam
    *The best Chinese farmer*
    Attachments:
    dmmerror.JPG ‏153 KB

  • I'm having trouble with a multi channel acquisition and download with PXI-5922

    I am having trouble with getting data out from both channels of a PXI-5922.  My software seems to be working, but when I do the fetch there is no data for the second channel.  I am using the same format for all of the channelList inputs (0,1).  I've checked the instrument handles and anything else I can think of, but this is my first time trying to collect data on 2 channels of a digitizer.  Any help would be appreciated.

    Hi schliepe,
    Try checking your code against an existing example. The
    Developer Zone Example: Independent
    Channel Configuration with NI-SCOPE is a good VI to reference. Also note
    that there are several examples that come with the NI-SCOPE driver. They can be
    found in Windows by going to Start »
    Programs » National Instruments » NI SCOPE » Examples. Additionally, if you find that the examples are not working either, verify that both channels are functioning by running the
    NI-SCOPE Soft Front Panel.
    Please post back if you have any questions. Have a great
    day!
    Ryan D.
    District Sales Manager for Boston & Northern New England
    National Instruments

  • 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

  • Trigger delay in Multi acquisition mode

    I'm trying to use the 5112 to acquire a burst waveform.  I want to average 20 acquisitions or records and take measurements on the average waveform.  The burst arrives a certain time after my trigger so I need to use a trigger delay.  When I try to change the trigger delay while my program is running I get "Trigger Delay is Invalid" error.  The only way I can get it to work is if I reset the device before I reconfigure the trigger.  Is this the only way to adjust the trigger delay in multi-record acquisition? 
    Thanks,

    Hello Rudy27,
    There are two things you need to consider for the trigger
    delay:
    1)      
    In a multi-record acquisition using the
    NI 5112, the time per record should be > 42 µs and trigger delay should be
    > 42 µs. Otherwise, you may observe trigger timeouts. This is found on the
    help file Start » All Programs » National Instruments » NI-SCOPE »
    Documentation » NI High Speed Digitizers.
    2)      
    You cannot change the trigger delay
    during runtime. You need to stop the acquisition, then reconfigure the device
    and then start it again.
     I would like to know if your trigger arrives multiple times in
    the burst or just a single one each?
    If is multiple times, then you can make your record size to be
    the entire burst.
    If is single time, then I would assume is always the same
    delay.
    Hope this helps.
    Gerardo O.
    RF Systems Engineering
    National Instruments

  • Multiple record acquisition on 5911

    Has anyone tried a multiple record acquisition on the 5911 in Win95 ?
    The niscope_initiateacquisition function takes a long time to get going
    (anything from a few ms upwards), which means I miss a lot of lines in
    the image I'm trying to grab. Do I need to tell Windows to stop doing
    anything else during my acquisition loop ? If so how ? I've tried disabling
    interrupts (using Borland _disable(), _enable() functions), which improves
    things a little bit, but the problem's still there.

    Hi David,
    The first time you make a call to Initiate Acquisition will take a lot of
    time because this is when all your configurations are sent down to the board.
    I tried this here and found it took nearly 16 ms for this call and I have
    a very fast machine (800 MHz).
    It seems that you are starting your device and the NI 5911 at the same time.
    Could you start the NI 5911 before your device? This way it will be up
    and running and waiting for a trigger and you won't have to worry about this
    delay.
    In multi record acquisition, you only have to call the initiate acquistion
    one time so after this call, the time between acquisitions will be very small
    since it happens on the hardware and windows will not interfere.
    "David Bell" wrote:
    >>Has a
    nyone tried a multiple record acquisition on the 5911 in Win95 ?>The
    niscope_initiateacquisition function takes a long time to get going>(anything
    from a few ms upwards), which means I miss a lot of lines in>the image I'm
    trying to grab. Do I need to tell Windows to stop doing>anything else during
    my acquisition loop ? If so how ? I've tried disabling>interrupts (using
    Borland _disable(), _enable() functions), which improves>things a little
    bit, but the problem's still there.

Maybe you are looking for