Accelerate the daq meter

Hello

I am trying to determine a signal pulse width using the meter of a NI USB 6216. It works pretty well, except that the acquisition is too slow for my needs.

Below you can see a stripped down version of my vi acquisition. In the depicted scene of version 2 of the loop takes 3ms to run. He is scheduled to count the number of times (20) low in the signal, I am able. The whole loop takes 30ms however (measured beginning at the end of loop - not from beginning to beginning of the next iteration).

If I remove task to start and stop the job screw does not change the loop time, all the time apparently taken over by reading vi.

I would like that the loop to run with less overhead (ideally no :-).) Can someone with more experience shed some light on how to speed up this vi?

Best regards Florian

Be sure to make you a life-long.

Tags: NI Software

Similar Questions

  • How to connect an International ST75 components fluid flow meter to the DAQ system?

    Hello

    I am trying wire a ST75 meter to my DAQ system consisting of a device PCI 6052E DAQ, SCXI 1102 b card and a block to connect SCXI-1300. 1102 b has four 249 Ohm resistors connected to channels 0-3 for use with the current of the flow meter signals.

    The flow meter has two output signals 4-20 my and RTN, SINK, SOURCE and com connections The documentation is not clear how to connect the sensor to the Terminal Board, other than to say if the two output signals is used, one of the sons of RTN are used. So far, I can not get the signal from the flow meter to work in LabView, so I don't know if I have it plugged properly. Currently I have 1 wire OUTPUT on the Terminal Board + CH2, CH2 - wire to the chassis ground terminal and the COM lead on the sensor.

    Thanks in advance.

    Towards the end of the manual there are wiring diagrams:

    http://www.fluidcomponents.com/industrial/library/manuals/flowmeters/ST50, % 20ST 51, 20ST 75% 20Guides %2%...

    SINK/SOURCE/COM are used for pulse ouptuts. It seems that there are two outputs, one for 4-20mA temperature the other for flow.

    The one you need (flow) conjnction with RTN wired to use the + and - (or COM) your DAQ hardware.

    -AK2DM

  • Using the DAQ USB-6009 meter and an analog input voltage at the same time.

    Hello

    Currently, I'm reading the two channels of voltage with the USB-6009. It happens that one of the channels is the output of a digital coder, and it would be much easier to use it directly to the PFIO entry that is defined as a counter. The problem I am facing right now, it's that I can't use the DAQ Assistant to use the analog voltage to a channel and the digital channel counter at the same time. Once I put the DAQ Assistant to read the input from analogue voltage, I won't be able to add analog inputs. And as I put the DAQ Assistant to use the PFIO as a counter, I can add more entries to read analog voltage is.

    I wonder if it is possible to solve this problem using the lower level data blocks? Another solution would be to read two channels in analog input voltage and that the use of Matlab to process data resulting from it, since I was not able to do the counting to work simultaneously with the acquisition in Labview to impulses.

    Hope you guys can help out me.

    Thanks in advance.

    Using a simple wizard of DAQ is incorrect. You need one to acquire analog inputs and one for the meter.

  • Help explain the flow meter VI

    After a lot of tinkering, I seem to have developed an effective VI for use with a type/pelton turbine flowmeter. The flow meter outputs a stream of pulses which

    can count on the counter of my 6501 line. Unfortunately this eureka moment happened somewhat by chance, and I'm hoping someone

    could be kind enough to explain step by step or in terms very simple for beginners (me) works of VI, thank you.

    Kind regards

    GER

    GER,

    Welcome to the Forums and LabVIEW.

    If you don't the have already made, please work through the tutorials online to get started with LabVIEW. The answers to some of the questions you may have are probably there.

    A brief description of your VI:

    1. the overall structure is a loop For. It works for the number of iterations that is connected to the Terminal in your case 5 N.

    2. the calendar of the loop is determined by the longest time required for any part of the code inside the loop execution. On the first iteration, the DAQ Assistant configures the counter and starts measurement. On all subsequent iterations, he reads everything simply an indictment. On these iterations, the 25 les 25 ms ms expect will dominate. This VI runs approximately 40 iterations per second (for 5 iterations).

    This means that the program will take place on 5 * 25 ms = 0.125 sec and then stops. If you run for more 1/8 of a second to help run it continuously button, STOP. Which is intended for certain types of troubleshooting only.

    3. the table of waveform and the flow rate meter only shows the last value of the five iterations. (This suggests also that you use run continuously)

    4. the registers at offset in this VI nothing do. The upper shift register calculates the cumulative number of the flow meter, but the result is never used. The underpass registry has nothing connected to the Terminal inside the loop on the left. It could be replaced by a terminal.

    Suggestions:

    1. in order to avoid using run continuously, replace the loop with a while for loop. Add a stop button on the front panel and connect it to the stop it real terminal in the loop. Move the graphic terminals of waveform and flow inside the loop.

    2 check your pulse to the algorithm of flow rate. The time for the count interval must be considered.  For example if the meter registers 25 pulse in 25 Member States, which represents 1 000 pulses per second. This isn't which will show your VI.

    3. see examples of code that uses counters.

    Lynn

  • Device simulated in MAX, auto test without error and has work Test panels, but is not displayed in the DAQ assistant.

    I am trying to create a development machine, where we can test the new code without using our physical hardware. I followed this guide to set up a system of simulation. I get to step 3.2 b, but the device does not appear in the DAQ assistant. MAX, the device self test and gites calibrated successfully, and when I open the test panels, I see some sort of signal. I guess that's a default entry simulated since I didn't that device to look for anything? Note that two devices, I am creating the show upward into the devices section and Interfaces, but that, even after running auto calibrate, automatic Calibration date is not yet specified.

    When I try to test the device and create a voltage according to the guide, I can't see a device in the creator of data acquisition task.

    Steps 1 and 2 of this guide are of course met. Step 3 is not, but this is not surprising because a simulated device is in device in any case manager. Also, I'm not under RT, so step 4 is satisfied.

    Someone at - it ideas?

    That would be because the PXI-5124 is a digitizer not an analog input device.  You must use the NI SCOPE not NOR DAQmx driver

  • 201003-error occurred in the DAQ Assistant

    Hello. I use "cDAQ-9178" and "NI 9215" and "NEITHER 9402" are added on. "

    However, when I run Labview code, "Error-201003" occurs.

    {

    Device not available. Possible causes:

    Device is no longer present in the system / device is not powered.

    Device is turned on, but was temporarily without electricity / device is damaged

    }

    (Error appears as the 1st and 2nd figures below).

    (Plans of logic is the figure below).

    Thank you.

    I could be something with the pilot

    Check this box:

    Error 201003 to the MAX test panel or all by running the DAQ Assistant

    http://digital.NI.com/public.nsf/allkb/5413F392D88326148625746B006745C5

    In this forum, they speak the same error:

    Spontaneous error code 201003 for acquisition of data PCI configuration

    http://forums.NI.com/T5/SignalExpress/spontaneous-error-code-201003-for-PCI-DAQ-Setup/TD-p/830707

  • Simulate signals wired to the DAQ assistant for USB-6009 device

    Hello

    I'm trying to send a signal to the DAQ Assistant Express VI.  I watched the movie "Generating a Signal" on the Web site of NOR (www.ni.com/academic/students/learnlabview/generate.htm) and I have my Signal simulate connected directly on the DAQ Assistant, as shown in this film.  In my case, the DAQ Assistant sends the signal to a device USB-6009.

    However, I received this message:

    Error-200077 occurred to the DAQ Assistant
    Possible reasons:

    Requested value is not supported for this property value. The value of the property may be invalid because it is in conflict with another property.

    Property: SampTimingType
    asked the value: Sample clock
    You select: On-demand

    If I select 'On Demand' in my DAQ assistant and run the vi everything works beautifully.  However, I need my DAQ assistant to be configured to generate a waveform AC continuous, not output a single alternating current rippling.

    What happens here?  I did not have this problem before on other devices of NOR. I am using LABView 2010.

    Please answer.

    Thank you.

    double post

  • Channel of the DAQ (SMU-4498) task order

    I have an SMU-4498 for which I generate an acquisiiton task programmatically. When the task is created channel order is not necessarily in ascending order of channel number.

    My question is if the DAQ card will return the data in the order in which I defined the task or channel order?

    Thank you

    It seems that the answer is that channels must be specified in the order, when creating a task.

  • Multiple entries to the DAQ Assistant

    Hello

    I'm doing my DAQ Assistant, in several (formed of an array) Boolean inputs where there is 1 digital output. (see attached software folder)

    Physically, I want a valve to open and close at a certain pace, where the user can install/control this pattern until the program starts.

    I think that the best way to do it is to have multiple Boolean values that the user can press or unpress.

    Before that, I started, I tried with only Boolean 1 where it worked perfectly.

    As seen on the attachment (error), it is possible to an easy problem to solve, but I just can't figure it out, I'm stuck at my already made solution.

    I use USB6008.

    I hope that there is a gentle soul who can help out me.

    Best regards

    Kenneth G. Vejen

    Hi Kenneth.

    When the output to the generation mode is set to "sample 1", which means that whenever you call the DAQ Assistant will generate 1 sample. In order to generate 5 samples, you must therefore call 5 times.

    I have attached a modified version of your VI, which shows a way to archive it. However, be aware that the samples will be generated fast and not at 100 ms note your loop runs. It depends on your application, if it is as you want samples to be issued.

  • Calibration of thermocouples in the DAQ Assistant, using data from spreadsheet?

    Hi all

    For my first application LabVIEW, I'm looking to automate the calibration of thermocouples by measuring their response at different temperatures in a dry well Sizer. I get temperatures of thermocouples six by SCXI 1303/1102/1600 and have six channels put in place in one of my subVIs in the DAQ assistant.

    I compare these values to temperature calibrator that I am acquiring by VISA series in an other Subvi. All these values are written in a .csv file.

    Can I import these data into the DAQ Assistant to use for calibration? Is there a simpler way to associate with the channel calibration data? Currently, I could manually copy - paste the cells on the worksheet in the calibration sheet, but that seems just silly.

    If there is everything that I could provide to help solve the problem, let me know!

    Thank you!

    Hi Zoysiamo,

    It is possible to automate the calibration screws DAQmx at a lower level, in particular the DAQmx channel property node. Using you can specify advance nationwide and the values on the scale for your channel. I recommend you take a look at this example of the community. The property node configuration will be similar to, as illustrated below:

  • Error of the DAQ Assistant

    I've just updated LV 2009 SP1 LV 2010. I use a LV 32-bit on a 64-bit computer.

    When I open the DAQ Assistant, I get a pop up window that says "LabVIEW: an exception occurred in the external code that is called by a function of the call library node."  This could have corrupted memory of LabVIEW.  Save all work to a new location and restart LabVIEW.  VI "Advanced Timing.vi:1" was arrested in node "" a call to "get of DAQmxAssitant_DAQmx IO Info.vi of control.

    If I hit OK, DAQ Assistant is locked up, if I use the Task Manager to close the LabVIEW vi breaks down.

    I already reinstalled 9.5.1 DAQ device drive. without success.

    There is no such version. The most recent is 9.2.2.

  • color of the digital meter ramp or slide is missing the performance

    Hello

    I, m using CVI 2010 (10.0.1. (419) on windows 7-64 bit.

    In a simple program, I use a digital meter. I also use the color of the digital counter and on the IUR ramp, I see the ramp as expected with the defined colors. But when I run the Panel (in the debugging or mode of publication), the instrument (meter) shows but without the color ramp.  If I save the uir file, close it, then reopen it, the ramp of color in the file of the IUR is also missing, so I have to configure it again. It's the same with a digital slide.

    I think it's a bug? Someone at - it the same problem?

    Greetings from bremerhaven

    Norbert

    My guess is that you have inadvertently saved the. IUR in an old format (8.1 or older). In the user interface editor, check the bottom right of the window to see what the current format of the. IUR is.

    If this happens, you will have to change via file > save as.

    Luis

  • Units of the number of samples and rates for the DAQ Assistant units

    Hello

    I use the DAQ assistant for analog voltage of an input OR data acquisition card. What is the difference between the rate and the number of samples in the DAQ assistant and what are the units of the two?

    Thank you.

    The number of samples is how many discrete to measures. Rate (per second) is how fast to acquire the specified number of samples.

    If number of samples is 100 and the rate is 1000 samples per second, then the acquisition would take 0.1 second (100 / 1000).

    -AK2DM

  • Discordance between the DAQ rate Wizard and the dt output waveform

    I use a NI 9239 to acquire analog input data. Using the DAQ Assistant, I put the N samples, 8 k samples read acquisition mode and the frequency of acquisition of 8 k. I wire the data output of the DAQ Assistant directly to an indicator of waveform.

    I expect the dt for the waveform to be 0.000125. I have 0.000120, which is a rate of acquisition of 8333,333 Hz.

    What I am doing wrong?

    Thank you.

    To read the 9239 specifications in order to answer your question. Focus on page 18/19.

    Bonus tip:

    You specify the MINIMUM for acquiring sampling frequency in the DAQ Assistant.

    hope this helps,

    Norbert

  • In Labview 8.5, what happens if the input signal exceeds the scope of the signal defined by the DAQ Assistant?

    Hi all

    This should be a pretty simple question, but I can't seem to find the answer online and currently do not have the functionality to test this:

    I'm using LabVIEW 8.5 and have a VI that imports data from sensor through the DAQ Assistant. In the configuration tab, there is a range of signal input. What happens if my sensor exceeds this range? I get a warning? The default value is the maximum (or minimum)? I was interested in writing a code to display an error that I approach the limits of this range, but did not know if I also need to include code to display an error if the scope is exceeded as well.

    Thanks for the help,

    Tristan

    Hello, Tristan,.

    The behavior depends on the selected range and the device you are using.

    If you are using a device with a single input range is valid, we will use this range, even if you set a smaller minimum and maximum in the DAQ Assistant.  So, if your device only supports ±10V and you set the range to ±8V, you will still continue to get valid data after your top sensor 8V until what you approach 10V.  When you reach the limit of the extent of your device, the output will be 'rail', and simply return the maximum value until the signal is less than the maximum value again.

    Note: A device that is nominally ±10V usually has a go-around (such as ±10.2V) which are usually specced in the manual.

    However, if you use a device with several ranges of entry then things become more complex.

    NOR-DAQmx player will choose the smallest range that entirely covers the interval you choose.  For example, suppose that your device supports the following input range: ±0.2V, ±1, ±5V, ±10V and you choose 0V - 3V as the range in the DAQ assistant.  The NOR-DAQmx driver will focus on the input range and the list of the entry lines that your hardware supports and choose the smallest encompassing the entire range that you set.  This would be the ±5V, because this is the only beach that contains up to 3V.  Thus, all between ±5V input signal is returned and none outside this range will be 'rail' to the maximum or minimum value.

    We do this because using small beaches make more efficient use of the resolution of the ADC.  So, we try to use the most effective range based on what you ask without picking up a range that will make you miss data.

    Let me know if I can clarify it more.

Maybe you are looking for