AI acquire waveform. vi update rate

Hello,
I would like to increase the update rate ( which governs how many samples are acquired per second) for the attached vi- AI Acquire Waveform(waveform).vi.
This vi is a built in vi obtainable from Analog Input palette under Measurement I/O.
The update rate preset is 1000 samples per second, i want it to be 10,000 per second.
If i type it manually, it doesnt stay and reverts back to 1000.
I am using LABVIEW 8.6 on Windows XP machine
Thank you very much and Regards
poli
Solved!
Go to Solution.
Attachments:
AI Acquire Waveform (waveform).vi ‏14 KB

Hi Poli
Have you looked at the the daq examples. Labview is shipped with a lot of examples. Also are you running this by using the continuous run button? That button is for debugging only, and it is a no-no to use it for other purposes
If you are new to Labview perhaps some of the online basic lessons will do you good.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Similar Messages

Can I acquire waveform at faster sampling rate using external clock?

I am trying to acquire waveform at a sampling rate of 1MHz. My 6036E card is maxed out at 200KHz. Is there a way to achieve a sampling rate of 1MHz using an external sample clock? Your PFI pin can take external clock as an AI sample clock, right?

Hi,
I remember I asked the similar question before in the NI forum, they reply me:
the max sample rate (scan/s/channel) cannot be greater than your board max sample rate, even you use external scan clcok. So the answer is no for your case.

How to generate a waveform (with changeable update rate and sample) with USB 6008

Apologize about my awful English.
In Tradition DAQ I can set different update rate with "AO Start" vi.
Transform into USB-6008 device things turn into quite different.
I don't know which vi I can setup update rate.
Is there any example for this.
THX a lot!

Hello D.
To use the USB-6008, you need to download DAQmx Base driver from the web at http://digital.ni.com/softlib.nsf/websearch/CE3686A8D5B0CEDC86256FFD007C9C4A?opendocument&node=132070_US .
The driver will install with example programs that you can access by going to Start->Pograms->National Instruments->DAQmxBase->Examples. You new to have LabVIEW 7.x to use this driver.
SergesL

FFT Frequency Resolution vs. Graph Update Rate of a Vibration Signal

Hello,
First, what I know:
The frequency resolution (Hz) of an fft is 1/acquisitionTime (e.g. if 2 seconds of data are acquired, the frequency resolution is 1/2s = 0.5Hz).
What I'm Wondering:
Let's say I'm displaying an acquired signal on a graph and freq res = 0.5Hz. The graph update rate is therefore approx 2sec.  This may appear to be an application with a problem from a user's perspective.
Can I increase the update rate?
It seems that with vibration data (i.e. mostly non-periodic) I could create a buffer that is 2sec long.  The first data acquisition sequence will fil the buffer with 2sec of data. Then I could just acquire something shorter than 2sec of data (let's say 1/4sec). If I am acquiring data continuously and I push the 1/4sec of data into the front of my buffer then perform the fft again, I have effectively increased my graph update rate to 1/4sec and my users think I'm great.
Can anyone shed any light on whether or not (why/why not) this will work?
Thanks for your time,
Chris

The best tool NI provides for your application is the Zoom FFT. This allows you to specify the span (frequency range of the FFT) and the zoom (the delta f such as 0.5hz) in the FFT. The Zoom FFT has a built in buffer, called overlap and allows you to set the overlap so that it updates at the appropriate rate, event though you may need many seconds of data to get the delta-f in the FFT you are looking for. We package all this and manage units to display the correct units for power density, power, linear, magnitude, rms, 0 to peak, peak to peak, etc. We even provide a express VI for the zoom FFT and it is also part of the Sound and Vibration Assistant, requiring no programming at all.
http://digital.ni.com/public.nsf/allkb/F70DB3441DC5AB9986256E97005BA825
http://zone.ni.com/devzone/cda/tut/p/id/6107
http://zone.ni.com/devzone/cda/epd/p/id/5505
http://sine.ni.com/nips/cds/view/p/lang/en/nid/12152
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

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

AI acquire waveform. maximum readable data

Hello,
For acquiring data from an DC-accelerometer I'm using the 'AI acquire
waveform.VI' to perform this task. I'm scanning for 10 seconds at a sampling
rate of 10.000 S/s. When I'm looking at the amplitude spectrum I find
spectral components below 1 Hz which can't physically be there. (10 seconds,
so df = 0.1 Hz). Is it possible that this has got to do with the acquiring
technique??
Thanx,
Ron@ld

To expand on the previos response, Nyquist Thereom tells us we need to sample at least twice as fast as the signal's frequency to get an accurate sampling and reduce aliasing effects. Aliasing can also be due to noise sources in the environment so using a low-pass filter is still a good idea. Here is a Knowledge Base on aliasing and low-pass filtering:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/68f14e8e26b3d101862569350069e0b9?OpenDocument

Can I manipulate update rate of the NI-PCI-5411?

Hallo everyone,
How can I change the update rate of the NI-5411 AWG card ?
Thank you for your replies.
Kind Regards,
rainbow27

If the module is currently generating, call niFgen Abort Generation.vi (niFgen_AbortGeneration) to stop generation.
The sample rate is then set with niFgen Set Sample Rate.vi (niFgen_ConfigureSampleRate).
(Re)Start waveform generation with niFgen Initiate Generation.vi (niFgen_InitiateGeneration).
Jerry

Problems using acquire waveform...

We are trying to read an accelerometer signal using AI Acquire Waveform(it didn't work with similar boxes either).
The problem is that we set a scan rate of say: 10k samples/s and number of samples of 10k.
So every second the buffer is refreshed(so we can see the graph) and there is a big distortion.
Distortion is always the lenght of the buffer. We could do a "blind" acquisition setting a big buffer(# of samples). That would solve the problem but it shouldn't be like that.
Thanks,
Erick

Could you explain a little more what the distortion you see looks like?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Lookout OPC Client – Asynchronous I/O and Update Rate serious problems (Sequence of data)

I am using the Lookout OPCClient driver to connect to AB PLCs (EtherNet/IP protocol) and power measurement equipment (Modbus TCP protocol). The OPC server is the NI OPC Servers. The data that are read out from PLCs and PMs are energy meter readings, energy counters, power, voltage, current, frequency, power factor and el. energy quality measurements (THD). That energy meter readings are being stored in SQL database.
I am experiencing a serious problem regarding the accuracy of the meter readings. Several times per day, randomly, meter readings are losing the time sequence. For example, sequence is: 167, after few seconds 165, 166. In other words, present value followed by two previous old values. That generates a serious problem in our application that is expecting a naturally rising sequence of counter values.
Analyzing further, I isolated the problem to the connection between Lookout OPCClient and OPC Server. I made a simple application in Lookout 6.7 (opcproc.lkp, attached) with OPCClient parameters: NIOPCServers, OPC2, Asynchronus I/O, Update rate: 10000, Deadband: 0.0, that is reading just one tag from NI OPC Servers demo application (simdemo.opf).
By using OPC diagnostic tool from NI OPC Servers I record the sequence of OPC requests and responses. I found out that OPCClient sends every 2.5 sec “IOPCAsyncIO2::Refresh2()” call that is request for refreshing of all items in one OPC group. Few milliseconds later OPC Sever responds with callback function “IOPCDataCallback:: OnDataChange()(Device Refresh)” that actually refresh the data.
This periodic sequence is intrinsic to the OPCClient and cannot be disabled or changed (by my knowledge). This sequence is periodically interrupted by “IOPCDataCallback:: OnDataChange()” caused by update rate parameter of OPCClient (client is subscribed to server for periodic update of changed items).
In the case of demo application on every 4 refresh callbacks caused by refresh requests (2.5 sec) there is one update subscription callback determined by Update rate (10 sec).
QUESTION 1:
What is the purpose of update sequence and update rate when we have every 2.5 sec fresh values?
PROBLEM
The problem arises when we have a large number of items in OPC group. In that case the OPC Server starts to queue refresh requests because they cannot be fulfilled in 2.5 sec time because of large number of I/O points that must be scanned. At the same time update subscription callbacks are running at the period determined by Update rate. I observed in my production system that regular update callbacks has higher priority than refresh callbacks from the queue. That causes the loosing of timed sequence of data. After the update callback with fresh data, sometimes follow one or two refresh callbacks from queue with old (invalid) data. By adjusting Update rate parameter (1 hour, 2hours …) I can postpone the collision of data refreshes but I cannot eliminate it. Furthermore, the 2.5 sec automatic refresh are large burden for systems with many I/O points.
QUESTION 2:
Is there a way to disable automatic refresh request every 2.5 sec and just use update requests determined by Update rate?
QUESTION 3:
Is there a way (or parameter) to change the period of automatic refresh (2.5 sec)?
This problem is discovered for Lookout 6.5, 6.6 and 6.7 so I could say it is intrinsic to OPCClient. If I use synchronous I/O requests there is not an automatic refresh, but that is not an option for large systems.
Thanks!
Alan Vrana
System engineer
SCADA Projekt d.o.o.
Picmanova 2
10000 ZAGREB
CROATIA
T +385 1 6622230
F +385 1 6683463
e-mail [email protected]
Alan Vrana
SCADA Projekt d.o.o.
ZAGREB, Croatia
Attachments:
opcproc.zip ‏4 KB

The physical connection from LV to the switch is (I believe) copper crossover to fiber converter into a switch. Then, fiber from the switch to the end device (relay). The relay has all of the typical modbus registries and has been verified by inducing signals in to the system and measured/polled in LabVIEW and observed Variable Monitor. I am working with LV 8.2 and 8.5.
An OPC server would only add an additional translation of addressing within the configuration. The only real draw back would be the network overhead required to do this processing and not being representative of the end design configuration.
I will reiterated my question in another way:
I must answer the question to management that relates to data collection, test results and analysis; how often are you polling the client in relation to the outcomes measured? At this time I can not point at any configuration in the set up and execution that directs the data framing rate. I only measure the traffic and work with results. This needs to be clearly identified based on the relay modbus/tcp design capability of supporting an fixed number of client requests per second.
For testing purposes, I would like to be able to stress the system to failure and have prove capabilities with measured data. The present problem is that I have no basis to establish varying polling rates that effect the measured data transmission.
This raises another question. What handles the Variable Monitor data requests and how is this rate determined?
Thanks for your interest in my efforts.
Steve

Error 10401 occurred at AI Hardware Config, when using AI Acquire Waveform vi

I can successfully run applications that use the AI Sample Channel vi, however when I use the AI Acquire Waveform vi the following errors are generated:-
Error -10401 occurred at AI Hardware Config, followed by
Error -10401 occurred at AI SingleScan.
All applications have been developed using Labview 6.0.2, on an NT machine. The applications are then run (or atleast attempted to be run) using the Labview Run-Time Engine on a different NT machine.
The driver software I am using is the NI-DAQ Native Data Acquisition Driver Software Version 6.1.

Hi,
I've found a Knowledge Base on the NI website describing some situations where this problem occurs:
http://digital.ni.com/public.nsf/websearch/46F78EDD19BA0CC386256CEE007201FC?OpenDocument
That error code is generally seen when something has changed in the DAQ card's configuration, or the drivers are not installed properly. It's strange that this is showing up only on certain functions for your application.
Also try having a look through the DAQ troubleshooting pages on the website:
http://www.ni.com/support/daq/
Regards,
Mark Lee
National Instruments

AI Acquire Waveforms High and Low Limit

Hey everybody,
I am currently working with Labview 7.1 and a daq card. I am collecting 4 channels and using ai acquire waveforms to do this. I want to have different high and low voltage limits for each channel though. Is there a way to do this with ai acquire waveforms or would can I use something else.
Thanks for the help!
Devon

Hey Devon,
In addition to what David said, there is a great knowledgebase article here with more information about setting multiple ranges for Analog Input. The Traditional DAQ vi, AI Acquire Waveforms, doesn't expose the ability to set multle input ranges per channel, but there is a quick fix that you can do to be able to add it to the vi. See below:
The block diagram of the AI Acquire waveforms is as follows:
As you can see, the inputs of the vi that are exposed are simply the first element in a array of clusters including the high and low limits per channel. To set the high and low limits for other channels, you need to simply add another element to the array for channels 1, 2, and 3. See below:
Here you can see I simply added one element, you need to add 2 more for your 4 channels. If it turns out that you are using DAQmx and this doesn't apply, please refer to the knowledgebase above for details and an examples on how to set different ranges.
Regards,
Paul C.

Ai acquire waveform.vi

Hi,
Recently I receive a code from my senior to read data from DAQ bnc-2090. I have installed DAQmx 9.3 but I cannot run the code due to "cannot load ai acquire waveform.vi." I have find the answers that an old version of DAQ driver is needed. However, TDAQ driver is only suitable for Windows XP/2000, and I use Windows 7. What should I do to solve this problem? Thank you.

The only driver for that card is traditional DAQ and you've already found out that it is not supported on Windows 7 so why this question?

AI acquire waveform

For my project, I am using a last year student's VI as reference, but when loading it up, it asks for a "AI Acquire Waveform.VI" which I cannot be found, and there is no "data acquisition" tab under which it is normally found according to the manual, why is this?

Hi AV34,
What versions of LabVIEW/DAQ do you have installed?
If you installed DAQmx 8.0 then the traditional drivers (NI-DAQ) would not have been installed.
You need to install DAQ 7.4.1 or earlier onto your computer to get the traditional DAQ vi's.
They can be found at the following address:
http://digital.ni.com/softlib.nsf/websearch/3dbf3d343476a28f8625709e006a4937
All that said and done.. What aquisition device are you using? (DAQmx might be the beter way to go)
Many Thanx
AdamB
Applications Engineering Team Leader | National Instruments | UK & Ireland

A question about "AI acquire waveform.vi ".

I use my DAQcard(PCI-6024E) to acquire two AI signal at the same time through AI acquire waveform.vi.
But it is getting into a serious delay on my executing progarm by monitoring my time depended plot or time-counter(It is about 5 seconds in the real world vs. 1 second the program runs.).
however,I didn't encounter that problem when altering another AI vi(AI sample channel.vi),but it couldn't conform to my needs.
My AI acquisition program structure is "AI acquire waveform+equi-Ripple lowpass+mean" and another is "AI acquire waveform+mean".All settings are default except the high and low limit.So,does anyone solve my troubles?I really need help!!
(The situation is Labview 5.1 in the PC of p-133,32MB,and more than 1G reserv
ed capacity for C
thanks a lot!

Hello;
The best way to go about that is to use the Labview shipping example named Continuous Acquisition and Chart (buffered).vi that you can find at Search Examples->I/O Interfaces->Data Acquisition->Analog Input->Continuous Analog Input; as the start point for your development.
That vi shows the best way to do a data acquisition. You can insert you average VI inside the while loop of that VI.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

Waveform Chart Update With Relative Time

Hey,
I have a question about how a waveform chart updates. I am running a test in the pictures attached it is only for 4 minutes and I read in a data value every 90 seconds. I was wondering why the waveform chart doesn't look like chart 2 (photoshop what I want) instead it looks like chart 1.
I pass to the waveform chart a double every 90 seconds or so. How can I make the chart behave like picture 2? Where it connects the data points with the time each data value is sent to the chart.
Attachments:
Chart1.png ‏26 KB
Chart2.png ‏10 KB

Actually if you look carefully at chart 1 it appears that it is connecting the dots. But the time scale is messed up. Can you post some example code?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

AI acquire waveform. vi update rate

Similar Messages

Maybe you are looking for