Resample DASYLab Data to Lower Sampling Rate

Hi.
My hardware has built-in antialiasing filters at 20 kHz so I'll be scanning at 40 kHz minimum. 
My needed data range is low pass at 1 kHz. 
Can DASYLab resample the 40 kHz input to "decimate" the signal to the needed 1 kHz input? 
40x less data would be very helpful.  And if the data can be reduced, is this process CPU intensive (would it impose a large computational load on my computer)?
I prefer to use DASYLab but does LabView have this interpolation/decimation capability? 
Thanks,
Bob

signal1,
In LabVIEW there are several VIs (functions) that can be used to resample a signal.  Among these are the Decimate.vi and the Resample Waveforms.vi.  The Decimate.vi averages values to obtain the resampled waveform while the Resample Waveforms.vi employs interpolation.  You can view the help for these VIs at http://zone.ni.com/reference/en-XX/help/371361A-01/lvwave/resample_waveforms_cont/ and  http://zone.ni.com/reference/en-XX/help/371361A-01/lvanls/decimate/.  You can get the specific details about DASYLab from DASYLab Online support found at http://www.dasylab.com/content/mydasylab.php?action=start.
Regards,
Neil
Applications Engineer
National Instruments

Similar Messages

  • Low sample-rat​e measuremen​ts on the PCI-6115 DAQ card

    I need to measure an analog signal at a sampling rate of a few tens to hundreds of Hz in sync with the rising edge of an external clock. I have a PCI-6115 DAQ card w/ Labview 6.1 and NI-DAQ 6.9.2. The PCI-6115 is a high speed card and has a minimum sample rate of 10 KS/s. Is there any way of implementing a low sampling rate measurement using the PCI-6115 in sync with an external clock?
    Thanks in advance.

    Kuldeep,
    It is possible to do what you are describing above (in fact I don't think an external clock is required to do this), however, bear in mind that the reason for this minimum sampling frequency is due to the ADCs used on this high speed board. The ADCs used are pipelined ADCs, meaning that when a signal is digitized, it is digitized in distinct stages within the ADC (in the case of the 6115, I think there are 3 stages involved). Data is moved from one stage of the ADC to the next each time a sample clock pulse is recieved. If too much time elapses between these clock edges, the signal to be digitized can actually 'leak' off of the ADC. This can result in improper digitization, which can lead to less accurate measurements. So, while it is possible to mak
    e the device sample below it's minimum rate, it may be advisable to sample faster than the rates required by your application, and either average multiple data points per measurement, or throw away extra points taken.
    I hope this helps,
    Dan

  • Record data at one sample rate and calculate velocity

    I need to record position data at a sample rate of 10 hz but I would like to calculate velocity every half a second.  What is the best way to do this so the velocity display does not jump?  I want to capture quick responses but I would also like to calculate the velocity over a longer period of time like 1 minute. 

    I am trying to calculate vertical speed based on pressure altitude data.  I am using serial communication to measure pressure at 10 Hz.  I am using Labview 8.2 for all of the calculations and measurements. 
    I am looking for some way to average the data over some time interval that I have yet to determine.  I want to be able to see any major pressure changes whithin about .5 seconds but I also need to see trends over a longer time period say 2 to 10 seconds. 
    I have thought about using an array and then averaging the array or implimenting a rolling digital filter. 

  • Low sample rate with NI USB-6008

    Hello,
    We are working on a project collecting data from a hybrid rocket motor for
    University research. We are using a NI USB-6008, which has a sample rate of
    10kHz. We are using 3 channels and getting a sample rate of ~60 samples per
    second. I have attached the VI. Is this slowed by software, or physical
    computer computation speed? This sample rate needs to be much higher. Any help
    is greatly appreciated.
    - Theo
    Attachments:
    Hybrid DAQ_10.vi ‏73 KB

    Hi Rocket 154,
    You’ve already had some
    great responses, but I just wanted to add a little bit. A great starting point
    to writing good code would be the Getting Started with NI-DAQmx: Main Page,
    as well as the shipping examples (In LabVIEW, Help » Find Examples) already
    mentioned.
    If you navigate a bit
    through the links (Basic Programming with NI-DAQmx » Getting Started with NI-DAQmx
    Programming in LabVIEW) you’ll end up with some great resources. I recommend Learn
    10 Functions in NI-DAQmx and Handle 80% of your Data Acquisition Applications.
    It will detail many of the functions you can use and give you a feel for proper
    code style in LabVIEW.
    I hope that helps.
    Mark E.
    Precision DC Product Support Engineer
    National Instruments
    Digital Multimeters (DMMs) and LCR Meters
    Programmable Power Supplies and Source Measure Units

  • Why LV 6.1 and Nidaq 6.9.3 can't acquire low sampling rate and high frame size

    My platform is LV 6.1, Nidaq 6.9 on win98
    Everytime i want to acquire data with sampling rate 6 Hz
    and frame size 7200, it acquire just 2 or more data (under 10 data), never 7200 data.

    Greetings,
    I assume by "frame size" you are referring to the numbers of samples to acquire. Please launch the "Find Examples" browser in LabVIEW 6.1. Open the example "Acquire N Scans.vi." This VI has only 4 inputs. After setting your device and channel you will set number of scans to acquire to 7200 and your scan rate will be 6. Since you're only acquiring at 6Hz and wanting 7200 samples, this VI will take 20 minutes to run. At that point the graph will be updated with your data.
    Regards,
    Justin Britten
    Applications Engineer
    National Instruments

  • Counter Problem at low sampling rate

    What I am trying to do is to count the input from the camera and generate the number of pulses depending on the delay and interval. At the rate of 33ms the program works perfectly but if the sampling rate is 150ms it generates 2 pulses at a time. Is there a better solution to my problem ? Am I doing anything wrong ? Is it a problem with the loop timing or acquisition timing? I have attached the program. What puzzles me is that it doesnt work if the rate is lower! Please HELP.
    Thanks 
    p.s. I am very new to LabView so please excuse my ignorance.
    Attachments:
    CoolSnap.vi ‏142 KB

    Hello sha33,
    Thank you for getting back to me with more information. After looking through your code once more, I believe I have found the issue. Since this application is timed entirely in software, it is based on how quickly your operating system can run the program, and thus cycle through loop iterations. Since you have no Timing VIs in the program, this loop is running as fast as possible. Now, in the 33 ms case, you are getting a TTL edge a lot faster, so the DAQ assistant is updating its count faster as well. Lets say hypothetically that your loop is iterating at 60 ms. This means that every time you run through the loop your DAQ assistant will read the updated count value, and since you are counting every 33 ms, your count value will have updated.
    Now let's look at your 150 ms TTL signal. This is significantly longer than the 33 ms signal in the previous case. Lets say hypothetically your loop is running on average at 60 ms again. This time, your edge will come in and the counter will increment, generating a pulse with the second DAQ assistant accordingly. Now your loop will run through again 60 ms later but your next edge on the 150 ms signal is still around 80-90 ms away. This means that your DAQ assistant will return the same count value as the last iteration, and once again a pulse will be generated.
    Obviously the numbers I used for the loop iteration timing are hypothetical and entirely dependent on the operating system and its resources (i.e. it will run slower with an MP3 or Movie playing in the background). My suggestion would be to use a timing VI such as Wait Until Next ms Multiple to clock your loops more consistently. The goal would be to make sure that your loop is repeating faster than your counter is updating. Alternatively, you could account for the possibility of no counter input in your overall application to prevent a false positive.
    Let me know if I can clarify any of the above information, or if you have any additional questions related to this issue.
    Regards,
    Chris Behnke
    Sr. RF Engineer
    High Frequency Measurements

  • Conflict between the saved data and the sampling rate and samples to read using PXI 6070e

    Hello, I am using PXI 6070e to read an analog voltage. I was sampling at 6.6 MHz and the samples to read were 10. So, that means it should sample 10 points every 1.5 um. The x-axis of the graph on the control panel was showing ns and us scale, which I think because of the fast sampling and acquiring data. I use "write to measurement file" block to save the data. However, the data was saved every 0.4 second and as 35 points data at the beginning of each cycle (e.g. 35 points at 0.4 sec and 35 at 0.8 sec, and so on) and there was no data in between. Can anyone help me how there are 35 reading points every cycle? I could not find the relation between the sampling rate and samples to read, to 35 points every 0.4 second!
    Another thing, do I need to add a filter after acquiring the data (after the DAQ assistant block)? Is there anti-aliasing filter is built in PXI 6070e?
    Thanks for the help in advance,
    Alaeddin

    I'm not seeing anything that points to this issue.  Your DAQ is set to continuous acquire.  I'm not sure if this is really what you want because your DAQ buffer will keep overwriting.  You probably just want to set to Read N Samples.
    I'm not a fan of using the express VIs.  And since you are writing to a TDMS file, I would use the Stream to TDMS option in DAQmx.  If you use the LabVIEW Example Finder, search for "TDMS Log" for a list of some good examples.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Lossless to lower sampling rate automatic?

    I use Apple lossless for many of my imported songs. Will the iPod touch offer to lower the sampling rate on the fly? My shuffle used to do this.

    Okay, I tried to bite the bullet and include lossless ripped music files in a synch. I did a SmartPlaylist and limited it to 10GB taken from my general Music Playlist, not played in 90 days. It is now synching a little over 5.6GB in lossless and the rest of the 10GB 128/256. All told 1,235 songs.
    It is taking forever to sych. Pardon the pun, but this just about rips it I've got to downgrade the my lossless library which comes from CD's I own. I'm reducing the lossless files now. Hope this works without mucking up the sound too much.
    Apple, please add the automatic conversion to a small file via iTunes like my iShuffle!!! Otherwise I've got to manage two music libraries. Any other Apple Lossless Touch users out there?

  • How To Lower Sample Rate

    Is it possible to adjust the sample rate lower than the default when attempting to record an audio source?

    44.1 is the lowest sample rate to record audio at in Logic. But put a Bit crusher plugin on the track and change the resolution there for more lo-fi sounds.
    JG

  • NI 5761 with low sampling rate

    Hi,  is it possible to change the NI 5761 sampling rate without programming FPGA? Thank you very much!

    Hi, as mentioned above you can play with the sample rate by using an external Sample clock. Take a look at the picture attach for the general idea. Simply replace the Boolean buttons for digital input ports. I hope this helps
    Alejandro | Academic Program Engineer | National Instruments
    Attachments:
    Capture.JPG ‏256 KB

  • Lock-in amplifier, low sample rate options

    Hello!
    I would like to implement a lock-in amplifier in labview (version 8.5).  I understand that there is a developer kit for the LIA available, and have checked it out; however, it is incompatible with my equipment.
    I have a usb 1608fs card that I am using for for digital to analog conversion, which has a max sample rate of 16000 hz for two channels (signal and reference).  The signal I am trying to lock in on is between 5 and 10 hz.  The main contribution to the noise is 60Hz noise from the air, which shouldn't be a problem.
    However, the lock-in amplifier by labview refuses to work at under 50KHz sample rate, so I am at an impasse.  I could put one together myself, but I wanted to see if there were any options available to me; no point in reinventing the wheel.
    Regards,
    MB

    Here it says the minimum rate is 50kHz. Sorry, but ther is no option to change that.
    Also look at Lock-In Amplifier Startup Toolkit Compatibility with National Instruments Hardware.
    Btw, there is no USB 1608fs card from NI.

  • Timebase data for high sample rate

    Hi.
    I am running a Labview program which is sampling data from a strain gauge module in a CDAQ unit at 2kHz.
    The data is being logged to a TDMS file. The porblem I am having is finding a clock that is quick enough to use as a time base for this data. The clock that I am currently using is too slow and I see repeated time data for a few rows in the data file.
    See attached picture.
    So basically I need the clock data that can update at least 2000 times a second.
    Thankyou in advance.
    Rhys.

    As I already said, the internal timebase is more than capable so if you are reading multiple samples and specifying the internal clock, you should not have any problems. I don't know if your problem is how you are recording the data or reading it but the samples should be .5ms apart.

  • DASYLAB QUERIES on Sampling Rate and Block Size

    HELP!!!! I have been dwelling on DASYLAB for a few weeks regarding certain problems faced, yet hasn't come to any conclusion. Hope that someone would be able to help.Lots of thanks!
    1. I need to have more data points, thus I increase the sampling rate(SR). When sampling rate is increased, Block size(BS) will increase correspondingly.
    For low sampling rate (SR<100Hz) and Block size of 1, the recorded time in dasy and the real experimental time is the same. But problem starts when SR>100Hz for BS=1. I realized that the recorded time in dasylab differs from the real time. To solve the time difference problem, I've decided to use "AUTO" block size.
    Qn1: Is there any way to solve the time difference problem for high SR?
    Qn2: For Auto Block Size, Is the recorded result in dasylab at one time moment the actual value or has it been overwritten by the value from the previous block when AUTO BS is chosen.
    2. I've tried getting the result for both BS=1 and when BS is auto. Regardless of the sampling rate, the values gotten when BS=1 is always larger than that of Auto Block size. Qn1: Which is the actual result of the test?
    Qn2: Is there any best combination of the block size and sampling rate that can be used?
    Hope someone is able to help me with the above problem.
    Thanks-a-million!!!!!
    Message Edited by JasTan on 03-24-2008 05:37 AM

    Generally, the DASYLab sampling rate to block size ratio should be between 2:1 and 10:1.
    If your sample rate is 1000, the block size should be 500 to no smaller than 100.
    Very large block sizes that encompass more than 1 second worth of data often cause display delays that frustrate users.
    Very small block sizes that have less than 10 ms of data cause DASYLab to bog down.
    Sample rate of 100 samples / second and a block size of 1 is going to cause DASYLab to bog down.
    There are many factors that contribute to performance, or lack there of - the speed and on-board buffers of the data acquisition device, the speed, memory, and video capabilities of the computer, and the complexity of the worksheet. As a result, we cannot be more specific, other than to provide you with the rule of thumb above, and suggest that you experiment with various settings, as you have done.
    Usually the only reason that you want a small block size is for closed loop control applications. My usual advice is that DASYLab control is around 1 to 10 samples/second. Much faster, and delays start to set in. If you need fast, tight control loops, there are better solutions that don't involve Microsoft Windows and DASYLab.
    Q1 - without knowing more about your hardware, I cannot answer the question, but, see above. Keep the block size ratio between 2:1 and 10:1.
    Q2 - without knowing more about your hardware, and the driver, I'm not sure that I can fully answer the question. In general, the DASYLab driver instructs the DAQ device driver to program the DAQ device to a certain sampling rate and buffer size. The DASYLab driver then retrieves the data from the intermediate buffers, and feeds it to the DASYLab A/D Input module. If the intermediate buffers are too small, or the sample rate exceeds the capability of the built-in buffers on the hardwar, then data might be overwritten. You should have receive warning or error messages from the driver.
    Q3 - See above.
    It may be that your hardware driver is not configured correctly. What DAQ device, driver, DASYLab version, and operating system are you using? How much memory do you have? How complex is your worksheet? Are you doing control?
    Have you contacted your DASYLab reseller for more help? They should know your hardware better than I do.
    - cj
    Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

  • Why is it that I can't do a continuous streaming to disk with a 5102 scope card (PCI) when I can do it with a DAQ Card of much lower specs (my requirement is for small sampling rates only)?

    I am told that the 5102 Card (PCI) does not support continuous streaming of data to the hard disk. My application requires only very low sampling rates. If I can do it with a low spec DAQ Card using LabView why can't I do it with this card?

    Hello,
    The PCI-5102 is a high-speed digitizer card that has a slightly different architecture than the DAQ cards and was not built with the ability to stream data to the PC. However if you are sampling at low rates you can still acquire up to 16 million samples, which is done by using dma to tranfer data from the onboard memory on the 5102 to the PC memory. However, you will not be able to save the data to disk until the acquisition is complete.
    Another option would be to purchase either a DAQ card or a PCI-5112. Both boards can continuously stream data to the host PC and you should not run into any PCI bus limitations if you are stream to disk at relativiely slower rates.

  • Graph data at a certain sampling rate

    I am acquiring data at a sampling rate of 50kHz and I want to plot it on a graph or a chart continuously. The data is in an array which is connected to the graph/chart. I can see the signal (sine wave) but the time scales are not right. I have set "multiplier" field to 0.00002 to reflect my sampling rate but the start and end of the graph are not correct. They usually have a width of about 25 ms. How can I change it to 30 seconds? The graph should always be showing 30 seconds of data at any given moment. 

    Do you want it to be a graph or a chart?  They are 2 fundamentally different things.  A chart maintains a history of previous points and you can add to it a point or several points at a time.  A graph has no history and it only shows what you send to it at a given point of time.
    One problem you'll have with a 50kHz sample rate and 30 seconds worth of data is that is 1.5 million samples.  That is way too many to truly be able to see on a graph or chart at one time where even a large display might only be 1000 pixels wide.
    If you are using a waveform chart, you are probably seeing a limit on the chart history length which by default is 1024 data points.  At a 50kHz data rate, that would be about 20 ms worth of data.  Set the chart properties to have a larger history length.
    Message Edited by Ravens Fan on 10-03-2008 11:52 AM

Maybe you are looking for