Similar Questions

• Neither USB-6221 thermocouple

  Anyone who has used the USB-6221 for measurement by thermocouple? I'm doing a number of analog measures with two of them being J type of transport CANADA, have not used the 6221 before, but my client is not the money to go the compact DAQ road on this project. I would like to have compensation CJ, don't know how I'd do.

  A similar position is on the page of multifunction data acquisition, know that this one gets more views.

  Thank you

  I got my answer in the multifunction, DAQ card so I guess that it really is looked at frequently! Sorry for those who are hiding on this Board! I guess my point of view, LabVIEW-centric shows!

• driver for usb-6221 XP LAbview 6.0.2

  I'm trying to connect the usb-6221 to an old laptop with XP and Labview 6.0.2. I said that's not possible with NOR-DAQmx. This old version of Labview does not NOR-DAQmx, there NEITHER-DAQ 6.8 installed. Reading me for it suggests works with USB, but I can't find the USB drivers in installation.

  Based on the response to your message here, the only USB devices supported in NOR-DAQ 6.8 are old appliances DAQPad E Series USB such as the NI DAQPad-6015 or DAQPad-6016.  All material of the M series, including variants of the USB, are no longer supported in NOR-DAQmx.

• NEITHER USB-6501

  Hello

  Could someone give me some information about whether it is possible to use the

  NEITHER USB-6501

  As a generator PWM to control the dimming of 18 power LED function?

  calendar is not so relevant and if the pulse width can be controlled in the PC itself application the purpose would be financed

  Hello ONavarro,

  It is technically possible, but please note that USB-6501 as only software clocked e/s digital (e/s static). In other words the duty cycle of the PWM periodocity Ant you want to generate will be determined by a loop software, so depending on your system and the USB bus. I think that you will not be able to get a better rate of loop (ability to change the State of a digital line) less than some milliseconds (depending on the system).

  By example, if the loop runs at 5ms, and I want 10 steps in my PWM, this means the period will be 50ms, therefore a 20 Hz base frequency. If you can't reach 1ms, you will get 100 Hz. If you want more than 10 duty cycle value, you reduce the frequency.

  And it is NOT stable (loop software 5ms, first delta 5.8ms, then 4.9ms, 5.1ms, 6.7ms, and so on), because it is based on the software. If you need something stable and faster, choose a device with hardware synchronizing.

  Best regards

• Test capacitor does not load when DAQ USB-6221 is used as a measuring device

  Forum of NOR expensive, I have a Setup (see below) which is supposed to read the tension between a capacitor and a resistor in series.  Unfortunately, I found that the capacitor is unable to load completely with the connected acquisition of data entry.  However, if I remove AI0 connection of the circuit and the capacitor charges normally...

  I would be grateful if someone could explain to me:

  • Why this happens
  • If there is a way to change my test circuit in order to fully load the DAQ capacitor is connected

  For reference, I tried to change the position of resistance and capacitor (i.e. initially the capacitor in series), and in this case, the capacitor had no problem charging.  But for my purposes, I will need to test with first series resistance because I already have a lot of maps of test which are built this way.

  The food is set up to provide 75V (the rated voltage of the capacitor) when put on and the current limit is set at 20 Ma.  With these settings my capacitor only charge about 20 or 30 V with DAQ in the circuit.

  

  Let me know if I can give more details and thanks in advance to those who give thought to my question,

  You may test the limits of your USB-6221 surge.  I hope that you don't him don't have not damaged.

  You should be able to use some simple resistive voltage dividers for tensions in the acceptable range.  They will limit your ability to measure the leakage current.

  Lynn

• driver for USB - 6221 LabView 6.0 XP

  I'm trying to connect an old laptop with Windows XP and Labview 6.0.2 for USB-6221. I can't find the drivers on the site of NOR. Can someone point me at home or another source? Thank you.

  Support for the USB-6221 was added in the NOR-DAQmx 8.6.1, driver that only supports back to LabVIEW 7.1.  Unfortunately, there is not a version of NOR-DAQmx driver that supports the USB-6221 and LabVIEW 6.0.2.

• NEITHER USB-6008 connect to thermocuples and pressure sensors, control valve

  I am endevoring to build a gasification plant biomass for bench scale test process control plans. NEITHER USB-6008/6009 will be adapted for use as a data acquisition. I'll take RTDS, thermocouples and pressure sensors. I don't want to use industrial automation controllers.  It is also possible to use the channel of analog output for sending signals to a control valve position (using sufficient current/voltage between the two drivers).

  (1) OK.  I just wanted to be sure that you were aware of the potential dangers.

  (2) an RTD is a resistance that has small changes in resistance per degree of temperature change. To measure that you have need of a current source and a sufficient resolution in order to detect small changes.  At 25 degrees C a typical RTD is 109,73 ohms and resistance ohms 0.38 per degree changes.  If you had 1 my crossing this RTD voltage through it would be 109,7 mV and the voltage change of 0.38 mV by degree.

  The resolution of the 6008 on the most sensitive range is 0.49 mV > 1 degree.  The accuracy of the 6008 is 1.5 mV typical.

  For a Type K thermocouple, voltage at 25 degrees is 1.407 mV and change by degree is 39 µV.  Millivolt solving half of the 6008 translates into about 12 degrees.

  If you need a source of excitement for RTD and a kind of amplification for thermocouples and RTD before she would make any sense to try to use USB-6008.

  (3) I have not used anything except LabVIEW with DAQ devices and drivers.  I think DAQmx can be used with MATLAB and other languages.

  (4) the 6008 is the low range made by NOR. You will need to go to a more expensive camera or add signals conditioning circuits.  Talk to your representative OR assistance in the choice of a suitable device.

  Lynn

• NEITHER USB-9162 driver works for MAX and SignalExpress, but not for LabView

  Hello

  I looked for a solution for a while now. According to Web sites OR the NI USB-9162 is compatible with LabView 2012. I installed the last DAQmx. My hardware has been detected and is sensitive to MAX and works very well in LabView Signal Express. But it is not detected in LabView 2012. I searched the forum and not found any solution other then all uninstallation and reinstallation of any. It is quite conssuming time and would rather avoid if possible. Anyone have a solution? I wish I could appreciate.

  Tool:

  NEITHER USB-9162

  NEITHER RIO-9215

  Benjamin

  I reinstalled everything, and now I can work with it. I can't say that I was wrong on the first time, but now it works very well as well as other bugs that are now set.

  Thank you for your answers

• Firmware of switching of NOR-DAQmx Base on Linux to the USB-6221

  Our Windows machines are locked - even as developers, we without administrator privileges.  Which is updated from the impossible firmware via the Windows Device Manager.  On the other hand, we have total control on our Linux machines.

  Is it possible to download and check out the images of the firmware on Linux?  In particular, I need to move a USB-6221 to NOR-DAQmx Base.  I couldn't find all the instructions to do this on Linux.

  wlbaker

  I had a moment of complete Dyslexics your first post - powered external USB DAQ playback devices (USB-622 x, USB-625 x USB-628 x) are not supported under Linux (by DAQmx 8.0.1 or DAQmx Base 3.3), while DAQ USB (USB-621 x) bus-powered devices are supported by only DAQmx Base. The Readme files for the two drivers list the devices on which they based [1] [2].

  The USB-6212 case is the closest to the USB-6221 match, although if you don't have extenstive digital i/o in your application, the USB-6211 housing would also be a good fit.

  [1] DAQmx 8.0.1 Readme
  http://FTP.NI.com/support/softlib/multifunction_daq/nidaqmx/8.0.1%20Linux%20Only/Readme.txt

  [2] DAQmx Base 3.3 Readme
  http://FTP.NI.com/support/softlib/multifunction_daq/nidaqmxbase/3.3/Linux/Readme.txt

• How to create a simulator of hall sensor using NI USB-6221

  Hello.

  I am creating a hall sensor Simulator using the NI USB-6221 case.

  The idea is to have three digital outputs that generates output a digital pulse according to six different stages train.

  See the table below.

  

  And it's interesting to have this work in for example 5000 RPM (meaning 2 milliseconds between each stage).

  My question is, is it still possible with the NI USB-6221 housing?

  I tried to create a simple state machine, leading the outputs according to a predefined table.  But it became clear that it is far too slow.  The NI USB-6221 uses 10 to 15 ms to generate a numerical value of LabVIEW.

  Thanks for any ideas on how to do it.

  Looking at the datasheet.

  http://sine.NI.com/DS/app/doc/p/ID/DS-10/lang/en

  Under the digital I/o, you can see that the digital lines on Port 0 maximum clock frequency is 1 MHz.  This means that you can go from a Summit to a minimum once all the 1 micro second.  Your hardware is capable.

  The software side of things you should realize that to change the digital line from a high to a low that fast, you need to use certain types of calendar that does not have Windows.  Windows (and other operating systems) are not deterministic.  So instead of being in a loop from one State to the other, put in the buffer of the DAQ one card series of digital States and then specify the DAQ hardware to read at a given speed.  Then your synchronization is performed by the hardware, not by your software.

  Search for finder example for Digital - output continuous for an example on how to do this.

• Pilot DAQmx 14.1 installed but not seen by USB-6221

  Hello

  After a week of fighting to install driver DAQmx on my 2013 Labview (Win XP), I finally got with OR DAQmx 14.1.

  All right, I can run my screws

  But, when I connect my NI USB-6221 BNC-nothing happens.

  I checked in MAX if she communicated, MAX sees the device but says that the device drivers are not installed.

  Then I checked if there was other drivers for this device on the site Web of SNA apparently no, it runs with DAQmx.

  Someone have a solution?

  Thank you

  The descriptions I see say that USB-6221 is a legacy device.  That probably means support for it in future versions of DAQmx were dropped.

  I found this http://sine.ni.com/psp/app/doc/p/id/psp-84/lang/en

  It does not say definitely what versions of DAQmx take in charge the device, but this list seems to only go up to version 9.8.

• USB-6221, replaced by USB - 6221 BNC - error-50103

  My client is reproducing a system that worked well with NI USB-6221 enclosure. Now, I get an error with the NI USB-6221 BNC. The error only occurs when I try to perform auto calibration.

  ---
  The error:

  Error-50103 occurred at DAQmx Self Calibrate.vi:1

  Platform AND Services: The specified resource is reserved.
  ---

  I've implemented the pilot as a driving force.

  What is strange to me is that I can run the engine of the autonomous action to set up the device and run the auto cal without getting an error. But when I call these routines of an another vi - the error occurres.

  To specify (and reproduce the problem) - with USB-6221 BNC is defined as 'dev1 ':
  (1) acquisition of analog data in AE.vi - select 'Configuration' as an action on vi and then run it
  (2) acquisition of analog data in AE.vi - select 'Cal' like action then don't run it - no error
  (3) place the screw DAQ in a new vi as shown - run and that's when I get the error

  

  This is my first experience with DAQmx, any ideas what could cause this problem would be appreciated.

  Thank you
  Steve

  LV2009 Sp1
  MAX 4.71
  NOR-DAQmx Device Driver 9.2.1

  Hi Steve,.

  "Setup" action leaves the DAQmx run task, so the 6221 AI resources are reserved to prevent other programs and live to interfere. When the top-level performance, LabVIEW VI automatically tells DAQmx to clear the task. That's why you get different behavior when you run the action as the first level VI engine when you run the engine of the action as a Subvi. Self-cleaning, you must cancel (e.g. stop or clear) all the tasks before you can calibrate the device automatic, try performing the action 'Close' before 'Cal

  Brad

• period measurement Semi USB 6221

  Hi guys,.

  I have a problem measuring the period of semi of a digital signal. I'm gernerating a pulse with my USB 6221 DAQ board and I use the counter 0 (9 PFI) for the period of semi. But I don't get all the values. Also, I tried to generate a signal of pluse using the 1 meter and measured the period using counter 0 and it worked perfectly fine. Take a look at the code can be I am doing something wrong.

  found the problem. I was reading more samples then I sent.

  

• Acquisition of data GSM using NI USB-6221

  Hi people

  This is my first post at NEITHER and I just acquired for my 6221 USB NI LabView. Now my field of research is the analysis, acquisition and modulation of GSM data. I've not seen much traction along this area and I was wondering if someone would have done something similar.

  Thank you

  
  

• NEITHER USB-8452 - reach the maximum write SPI speed

  Hello

  I have a USB-8452 with the latest version of the software installed (2.1.2). The host computer is a Core i7. I am trying to achieve the maximum SPI write speed with the camera possible. I tried the basic block read/write SPI, SPI Scripting blocks and SPINNAKER streaming, but the first two have large delays between CS falling and the data being written (with so that delays in loop), and the last seems to be useful only for read operations.

  Can someone tell me if there is a way of a) reduce the time of installation for basic SPI / SPI Scripting or b) writing different values in a single stream of SPI? Thanks in advance for any help on this issue, even if it's just confirmation that yes they is hard limits that cannot be overcome with the LabVIEW 8452 interface at this time.

  Here's the best I can do right now, as shown in my logic analyzer. Change of the SPI clock speed does not affect installation time and delays that are primary and secondary bottlenecks:

  SPI read/write database-

  Program: Basic Configuration followed by read/write of SPI block itself in a while loop

  Main bottleneck: ~ 450 delay us into iterations of the loop (see Figure 2)

  Secondary bottleneck: ~ 6 us delay between falling edge of CS and the first synchronization signal (see Figure 1)

  Capture 1 - delay highlighting between CS falling and first SCLK pulse

  

  2 delay highlighting between all iterations of the loop of capture

  

   

   

  Scripts of SPI-

  
  Program: Followed two Script blocks Basic Configuration run in a while loop (to check the two block to block and delay loop iteration)

  
  

  Main bottleneck: ~ 450 delay us into iterations of the loop (see Figure 3, space between the second and third images captured)

  Secondary bottleneck: ~ 250 us delay between blocks of Script run consecutive (see Figure 3, space between the first and second captured images)
  

  Capture 3 - highlighting delays consecutive run the Script and delays between while the loop iteration
  

  
  

  SPI in Streaming- It's the closest to achieve a fast writing speed, but unfortunately, it seems to be only useful for read operations (e.g., ADC), do not write.

  Program: Configuration of the base stream followed by start of the flow block

  Main bottleneck: impossible to write something else than the data value unique property "wave 1-> MOSI data." I can write a byte array to this property, but it will simply put all these bytes in an image and repeat this framework (see Figure 4) rather than go through each value.
  

   

  4 - two bytes sent repeatedly using SPI capture stream. Delay of CS is finally good, but no possibility to change the MOSI image to image data.
  

  

  Hi JBender1,

  This show looks like what we would expect for a 8452.

  If you need higher performance, I encourage you to watch using a card R or FlexRIO FPGA series for your implementation.