Similar Questions

• USB DAQ error after update to 15.1 DAQ

  Everything worked well (DAQ 9.5) on my windows XP SP3 machine, so I thought that it's a good idea to install the last DQA 15.1, NOW my USB DAQ has a Red Cross in NI MAX and does not

  I tried to reinstall OR DAQ 15.1, restarted the PC, plug the NIDAQ inside and out, but the error remains.

  Any ideas how to solve this problem?

  Thanks for the info. I tried the above and uninstall and reinstall everything, but in the end, the only thing that solved the problem was to install a new copy of the operating system, windows XP in this case.

• USB6363 DAQmx (reading and writing) calendar seems slower than other similar USB DAQ devices

  Hey people,

  I have currently a service waiting number with OR the subject, but I thought I'd post up incase anyone has ever dealt with a similar question pertaining to USB DAQ hardware.

  Try to understand why there is a difference of synchronization between the 6363 USB and some of the other less expensive USB devices like the 6525 or 6501.

  

  It's a watered the actual code that my team has noticed this difference in the simplified version.  The actual code is a reading analog daqmx (it's triggered hw, so we begin the task of analog playback, trigger, wait the time we acquire to and then run reading daqmx. who takes 6 ms to read a single 50 values of the buffer).

  Thank you

  -Pat

  Hi Pat,

  Try benchmarking of HAVE it read that way (with the wait timed by the software, it seems to me that the task is probably not yet made to the time you want to read - I guess that the question is relative between the event of the task performed and all the data is available in the DAQmx buffer, I don't have a series of X USB to see) :

  

  Try benchmarking your writing clocked by the software in this way (there no reason to include the check/reserve/validation/start sequence in your writing of reference when the task can easily be launched during initialization of your program):

  

  On my PCIe X Series as the two cases take< 1="">

  Best regards

• Writing USB DAQ: Reading the data, analyze, analyzed data - does not

  I have Labview 2011 32 bits (without tools), on Windows 7.

  Material: Enclosure OR USB - 6251 DAQ board.  I use analog analog out.

  I'm trying to collect data (reading), analyze (like part or derivative) to a new waveform (or a data table)., then convert them this new waveform. As in this example:

  http://zone.NI.com/reference/en-XX/help/370466V-01/mxcncpts/hwtimedsimio/

  However, I don't have hardware timing.

  I tried a lot of things. Those who work temporarily, until the start to write task threw an error: http://i.imgur.com/as5ItdO.png

  Another who work temporarily, but it has a 7 second delay: http://i.imgur.com/VLbyZbo.png

  Ends up having this error: Warning 200015 occurred

  When writing to the buffer during a regeneration, the actual data generated may have alternated between the old and new data. In other words, while the pilot was replacing the old model of the buffer with the new model, the device could have generated some new data, while a part of the old data and then a part of the new data again.

  Reduce the sampling frequency, use a larger buffer or refer to the documentation on DAQmx write me for more information on other ways to avoid this warning.

  Can someone tell me what I'm missing?  It seems very simple.

  Thank you.

  Thank you for an update. Sorry I missed you use hardware USB DAQ and this is the reason why we see this error

  http://digital.NI.com/public.nsf/allkb/EC1968728E660B288625780700570D06?OpenDocument

  In general, when you receive errors like that they give you a pretty good idea on what is going on. Therefore, you can try to remove your task AO timming daqmx or try to set the size of the buffer.

  This might help

  http://digital.NI.com/public.nsf/allkb/E1E67695E76BA75B86256DB1004E9B07

• Question about USB DAQ 6363

  Hi all,

  I'm new with LabView, currently, we plan to purchase NI DAQ USB 6363 to use the entry to read the value of the resistor, capacitor and a diode and use digital i/o to check the functionality of the analog shift register. I want to check if it is possible that NI DAQ USB 6363 to acquire communication RS232 function because I want to drive barcode interface on it. I'll use LabView to log the reading result of database (SQL, Access) to do some data analyzation. IM also confused on test bench OR what is the relationship between she and NI LabView? is this another software to install except for LabView?

  Thank you

  No, you do not connect an RS-232 device to the DAQ card. The RS-232 is connected to the pc. If your pc lacks a built-in port you can use a USB-> RS232 converter.

  TestStand is a test of the direction which runs tests written in several languages, including LabVIEW. He plans the tests determine the success/failure, record results, create reports, etc.

• Ghost NI USB DAQ card readings

  Hello

  I have a question about the behavior of the NI USB-6218 data acquisition card.  Right now I use Labview to take several current readings of different channels to HAVE it.  I use resistors 250 ohms for each channel just as the instructions say to make the current readings.  I had an incident where he has been disconnected one end of a resistance at the entrance to the port.  I expected to see the reading go to zero, but instead, he began to piggback off the coast of reading one another channel give me a kind of 'reading ghost' because there was essentially no current crosses.  Playback of disconnected channel displayed the current reading of the canal connected even while values went upwards or downwards.  Can someone explain why the DAQ card would do that? and anyway to avoid this to happen?

  Thank you.

  A data acquisition uses a multiplexer to send a signal to the ADC.  Due to having only 1 ADC, you will get this effect if the ability has no way to bleed.  There is no way to avoid this if you disconnect the side DAQ, leaving the open input channel.

  You could try adding in some amplifiers specially designed for the shunts of currents.  I have used TSC103IPTwith success.  This amplifier gives you a single output is completed.  But I don't know what will happen with these if you disconnect one side of the resistance of the amplifier.

• Continuous output signal using usb DAQ 6008 in matlab

  
  

  Hi Takou,

  You already post with the same subject. Is this the same thing, isn't?

  If so, refer to the following link:

  How to get out a sinus with usb 6008 on MATLAB

  http://forums.NI.com/T5/Multifunction-DAQ/how-to-output-a-sine-with-USB-6008-on-Matlab/m-p/1510508#M...

  Best regards

• Serial RS232 directly to a USB DAQ?

  Hello

  I have a question about serial communication: is it possible to directly connect a device through RS232 serial to digital pins of an acquisition of data USB-6211? (Or perhaps even a USB-6008?)

  If so, where should I wire the pins to?

  If this isn't the case, could you recommend me a not too expensive, but functional RS232 to USB adapter that could work well? (I plan to interface a capnometer Datex or an infusion of Fresenius pilot C pump first, but if I could find a relatively cheap multi-port adapter I'd both. BTW, can I include more NI-VISA requests in parallel in LabVIEW?)

  Thank you

  No, you cannot use a DAQ hardware to simulate a serial port.

  I do not have a specific recommendation for a seller, but I've had much better luck with adapters built with a chip from ftdi than others. Google "usb to serial adapter".

  You can have multiple threads of communication with several cards.

• Design practice nor 6008 USB DAQ

  Hello

  I have a few question, I'd like to introduce. I need some sort of indication on how to better perform a timed cycle of acquisition driven by WSF.
  I'll send my VI (conceptual, not one currently working one) and ask for explanations.
  The goal

  I need to acquire a battery voltage. Load current consumption is driven by a couple of transistor.  I drive the hollow transistors two digital i/o for USB data acquisition.

  Because I need to have a power for a given time cycle, I need to have some sort of time control on the output.
  So I wrote a simple state machine whose States are updated when a timer reaches zero. Each State has its own queue time.
  Moreover, I differentiate between acquisition and control operations using two all in cycles.
  First question: is this a correct way to a timed WSF of construction?

  and now:

  The problem (s):

  I need to connect and establish a correlation between the input line for the internal of the fsm States. So I madesome digital indicator on the face before of the VI and created a local variable (I know that local variables are BAD, but I had no other idea everything) to pass values for some time to the other.

  I also want to select State sequent of the FMS based on the input value, I get a channel. I can stil use a local variable?

  Are the two related tasks?

  Second question: are local variables, something that I can use for this task?

  Last but not least: I need to filter on the values.
  In this vi I perform a filtering operation and then I get the I use for control of local variables.

  will be this filtering desync the two cycles while? will I run out of control before running the filtering?
  

  The same question is valid for the purposes of registration: the unfiltered data record, I guess is unnecessary. But based on this 'architecture' I know the country reports and the recorded signals are out of sync (as happens in many game data acquired with this vi).
  Is this a problem of logging (perhaps given by different buffers for data acquisition and internal State or something similar) or the whole WSF will be out of sync, then all acquired data is more useful because it is out of sync?

  Any advice would be much appreciated.

  Best regards

  Luca.

  Luca,

  Question 1: This is a reasonable start but need some things to make it a good WSF. There is no waiting or delay in the loop so it will run as fast as possible. U.S.-6008 outputs digital software timed so that the DAQ Assistant can take a long time, but the amount of time is unknown and not necessarily consistent from iteration to iteration. Since the DAQ Assistant Analog Input in the other races of loop to<= 10="" iterations="" per="" second,="" a="" wait="" of="" 100="" ms="" in="" the="" fsm="" loop="" seems="" like="" a="" good="" starting="" point.="" waiting="" 3000="" ms="" is="" not="" a="" good="" idea="" because="" the="" loop="" becomes="" unresponsive="" to="" the="" stop="" button="" for="" long="">

  Do you need to write on the lines on each iteration, even when the data has not changed? Add a write state that is called only when the data changes.

  The DAQ Assistant has a Stop input and an output of Stopped. When you are ready to stop the loop, the stop signal must be wired to these inputs so that the DAQ Assistant can delete tasks. The output of the order can be connected to a Terminal to stop the loop.

  Problem (s):

  It seems that you want to link the two loops.  Local variables are usually a bad way to do it. The best way is to use queues.  A queue can send the current state of the file loop. (More comments later if that's really what you need). Another line can send data, or better, the commands, the loop of the file to the loop.

  I think you want digital output values rather than the State. Especially if you add a State writing as I suggested above, the current state will not always represent the condition of the power of your test.  To make this work with the additional state Boolean matrix must be moved from one iteration to another via a shift register.

  It seems that you have at least two controls to be sent from the loop of the file to the loop. One is the stop command. The other went to the higher power level control.  You should probably have a command to set off power level which can be used if the battery voltage becomes too low and before stopping.  How your program is currently configured, the last level of power will continue as long as the power of the computer is on and the USB-6008 is always plugged. The cessation program does NOT reset the lines.

  When you use anti-parallel to the queues, you must be careful on the definition of wait times and the timed out case management.

  The benefits of the queues are that it is easy to ensure synchronization at the level you need, the data can be stored according to the needs, and there are good examples. It also avoids the possibilities of race conditions, often introduced by local variables.  This program could be based on a variation of the design producer/consumer model.

  Filter questions: any filter introduces a time delay. In your case when you filter 100 samples 10 times per second, it is likely that the filter will do well until the next data set has arrived. The delay of the filter is not affecting your synchronization. The above lines will solve problems.  Since you are looking at time of cycle seconds and the minimum interval on the order of 100 ms, the exact chronology (to tens of milliseconds level) is probably not too important.

  The real question about filtering boils down to this: does the control work better if the signal is filtered?

  - - - - -

  I'd probably all this a little differently. Given the slow speeds and the small amount of data, a simple loop with an improved state machine is all that is needed. Get rid of the DAQ Assistant and learn how to use DAQmx screws.  States could include: Init THE Init, Init File, Idle, read, write, DO, Analyze, filter, adjust the power, wait, Save, close file, DO, AI Shutdown Shutdown, error and exit.  No variables. No indicator fake just to allow the creation of local variables. Very little code outside the structure State case. None of the queues.

  Lynn

• Different value of USB DAQ device on different computers?

  Hello

  I have not found an answer to this one, so I open a new question. Here's the problem:

  I have a card OR USB 6003 and I read some analog signal of a sensor with a framerate of 1000 Hz (I use actually 4 analog inputs for 4 sensors). I created a VI and everything works fine on my computer. Then, I created a standalone application (.exe) and the installer that includes the drivers for the hardware DAQ and LabView Runtime Environment. When I install everything on computer target, the program works, but the sensor readings are weird! For example: I get a reading of 1 bar with a deviation of 0.02 bar on my original computer. When I plug the device on the host computer, I get an average reading of 1 bar with a gap of 0.5 bar, which is a lot! This gap could be considered some disturbances high frequency - like noise. What could be the problem? Is this even linked with LabView or is it hardware problem?

  OS information:

  Win 7, 64-bit (my computer)

  Win 7 32-bit (host)

  News of LabView:

  LabVIew 2013, version 13.0f2 (32 bit)

  OR MAX version 14.0.0f0

  Setup includes:

  NI LabView Run - Time Engine 2013 f2

  NOR-DAQmx run 14.0

  Thanks in advance on this one!

  Best regards

  Geraldine

  If you run the Test NI MAX Panel on each computer, you get the same result? Way that you specify which device to use in your code (for example MAX tasks? Project tasks? DAQmx configuration screw?) and the devices have the same configuration? Are you using the exact same device USB 6003 or use a different one on each PC?

  A computer is a desktop computer and another laptop? Economic DAQ devices are not isolated, so you could get the sound of your PC power.

• 2 boards of different USB DAQ in parallel

  Hello

  I have 2 x USB-6210 on 2 x USB ports on my laptop.   (Windows 7, Labview 2010). My goal is to synchronize these two boards.

  I put the same voltage (50 Hz) sine signal on their first input channel (AI0), to have and to see them in the same graph and synchronized.

  I put code in 2 different while loops. I tried with the wizard daq and daqmx (see attachments).

  I jumped 'DAQmx Start trigger' do something good, but not luck.

  But there is always a delay between them, a few milliseconds on the chart. And never the same deadline, if AI run the program again.

  If I turn on the yellow light bulb when running, I see one of the 'while' running loop and then the other, not in parallel.

  Is it possible to synchronizing them, immediately, after that I ran the .vi?

  Thank you.

  Based on the video, I created this example VI. Could test you? Don't forget, you must connect the PFI0 to PFI0 and PFI1 to the PFI1 BNC terminals with BNC cables between the two modules (you can choose other PFI connectors according to your devices, but then you must change the corresponding channels of PFI in the VI also).

  

• Integrate USB DAQ 6008 program Labview

  I'm new to LabVIEW and am currently writing a vi to access the 6008. I'm using LabVIEW 2012. I installed the driver NOR-DAQmx 3.6, however, the sample code is code c - no vi. Also, I can't see examples of NOR-DAQmx in the finder of the example. I downloaded various examples, but each are missing Subvi which I believe should be installed with the driver. All advice is appreciated.

  Harry,

  1 DAQmx Base is only supported on Mac OS.  You can find petitions on the exchange of idea ask for better support.

  2 DAQmx and all its beautiful examples are not installed on the Mac.  This means that the measurement and Automation Explorer (MAX) is not installed on the Mac and things such as the DAQ Assistant exist (although it is not a great loss).

  3. when DAQmx Base is installed on Mac OS X with LV 2012 you should have the DAQmx Base screws accessible from the measures of e/s palette.

  4 installation DAQmx Base includes a bunch of examples in this direction: Applications: National Instruments: LabVIEW 2012: examples: daqmxbase: However, the example Finder doesn't seem to know they are there, then you will need to manually search.

  One good thing about DAQmx Base is that it is almost entirely written in LabVIEW, so you can see what he does.

  Once you get past the obstacles, the USB-6008 case works well with DAQmx Base and the Mac.

  Lynn

• What PCMCIA or USB DAQ card to buy?

  For the purposes of my project, I would like read 2 quadrature encoders and
  2 analog outputs (0 to + 5 V) duty to control 2 Motors simultaneously.
  What PCMCIA or USB card that you would recommend for me?

  The PCI card that I used for the same project was the NI PCI-6221.

  6221 USB would correspond to my needs?

  Best regards
  Fotio

  Yes, that should be fine. You can always visit the DAQ hardware page to find the material for the acquisition of data appropriate for the needs of your project.

• How to make accurate measurements at high impedance using NI USB DAQ 6343 in Labview

  Hello.  I use a DAQ 6343 for measurement of analog voltage on a signal of high impedance.  I am aware that low impedance is recommended, but it is what is on my Board.  I tried to measure several times to an A/D channel only, increasing the number of samples, sample rate reduction, and I find significant variations in all of the measures.

  I wonder what is the best way to stabilize the A/D before taking a step on the way to analog input?

  Thanks in advance for your help.

  Jodi

  Hi jschwatz100,

  Here is a good link on ghost image, which talks about solutions for playback of a signal from a high impedance source:

  http://digital.NI.com/public.nsf/allkb/73CB0FB296814E2286256FFD00028DDF?OpenDocument

  I would recommend a circuit follower of simple tension of construction as a buffer between your signal source and data acquisition. Here is a Wikipedia article about it:

  http://en.Wikipedia.org/wiki/Buffer_amplifier

  I also recommend to maintain a ratio of 10:1 for your sample rate: Buffer Size(N Samples in Continuous Mode) and lowering/raising them both the same way.

  DylanC

• Looking for USB DAQ for AO using the external sample clock

  Hi all

  I'm looking for a cheap solution for the acquisition of data to select the AO using an external digital signal as sample clock, and I just realized that the USB-6001 is not a good candidate. Please someone remind the cheapest USB version for this task? There no need for high sampling rate. Thank you.

  Define cheap and low sampling rate. You've already been told on the 6211.