Data Acquisition Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

There are a few different versions of the NI USB 9211 Thermocouple Module.  The USB 9211 is now a legacy device and the USB 9211A is the upgraded version for higher performance.  The issue that I have seen when using the USB 9211A for Mac is that the DAQmx Base drivers that support the USB 9211 are different than the drivers that support the 9211A, but the device itself does not specify which version of the 9211 the customer has. DAQmx Base 2.1 supports the 9211 and DAQmx Base 3.2 supports the 9211A, but the device will not be recognized if the incorrect driver is downloaded.

 

My suggestion would be to print the "A" after the 9211 on the new devices to make sure that the customer knows which driver to download for their device.

We have a need to a DAQ card that can handle more than 10V.  I know there's an SC module that does 300V, but antenuation by 30 in signal conditioning seems a bit much.  In retrospect, Agilent has a 100V input PXI card without the signal conditioning (32 Channels, 16-bit, 250kS/s).

I rarely have to set up hardware for a new analog measurement and always have to puzzle over the difference between RSE and NRSE modes. I think of the inverting input as the reference, so "Non-Referenced Single-Ended" doesn't make sense to me. And, if I run the AISense line to my remote sensor, isn't that a Referenced Single-Ended measurement?

 

Yesterday, I noticed that at least some on-line documentation now refers to GRSE (Ground Referenced Single-Ended); adding that single letter helps a lot. What about adding another single letter and referring to the other mode as RRSE (Remote Referenced Single-Ended)? One letter could save a lot of people a lot of time.

 Does NI notice that the R&D requirement of MEMS sensors with "atto scale capacitance or inductance change?" In the past years, we can only achieve the measurements by MS3110 or Agilent E4980A. But they are not easy to be integrated with other equipments. The operiating or measurement frequency of the sensors, for example MEMS microphone, accelerometer, gyroscope, tactile sensor, is usually DC~100kHz, with aF or aH capacitance or inductance change.

 

MS3110

http://www.irvine-sensors.com/Chips&Modules.html 

 

On the other hand, which relay type of switch/multiplex/matrix card is proper for the MS3110 or Agilent E4980A with lower capacitance or inductance?

Based on this LabVIEW Idea...

 

Support the iPad as an execution target

 

Adding this type of support would allow NI and others to develop applications similar to the Oscium oscope using NI DAQ hardware.

 

Would like to be able to collect a couple channels of analog inputs to the iPad.  This is nice but I need a minimum of 2 analog inputs and I would rather have NI:  http://www.oscium.com/

 

Response from coorporate:

"We don't currently have anything that would meet the customer's requirement of being able to plug in directly into the iPad for data acquisition.

I don't believe that the iPad supports Silverlight which is a framework developed by Microsoft.  Also, wireless DAQ has to communicate with a host running DAQmx, so the customer would still need a 2nd computer even if using wireless DAQ.

If you want to connect data acquisition hardware (of any form-factor) to a machine running LabVIEW and DAQmx,  then use LabVIEW Web Services to publish the front panel to the web and view/control it from his iPad.

We do have several USB products that will work with Windows-based netbooks that could be an alternative solution if topic is open to a non-Apple platform.  For example, the 5132/5133 are bus-powered digitizers with much higher sample rate, bandwidth, and buffer size compared to the Oscium device.  However, the price is also quite a bit higher."

I recently had a customer offer the suggestion to expand the support for the USB-8451 to include a coding environment that includes .NET. Currently the only supported development environments are:

 

LabVIEW™ 8.5, 8.6, LabVIEW 2009 (32-bit), and LabVIEW 2010 (32-bit)
LabWindows™/CVI™ 8.0 (or newer)
Microsoft Visual C/C++ 6.0

 

I just wanted to share this with the community.

Currently, DSA devices that use voltage excitation have no method to provide that excitation to a particular device within test panels. The only method to do this would be to create a task in Measurement and Automation Explorer which takes much more time that doing a simple test panels test. This should be a fairly simple addition to the test panels user interface. One could simply have a box to check if they require excitation, and a control to determine the voltage level to provide to the DUT. They currently have this for IEPE devices, and it makes sense that voltage excitation should be the same.

I am not an electircal engineer, so I have no idea if there is some reason this has not been implemented in exiting versions of teh cDAQ chassis.  But there are a whole host of applications where a user wants to do Hardware timed digital output to different channels using DIFFERENT time bases.  It would be nice to have more than one DO timing engine available.  I would love to see that in future versions of the cDAQ chassis.

 

Thanks

Matt

If NI already has the product, please let me know. I need it in my project. If otherwise, I would like to suggest NI to develope one based its NI-9234 and WLS-9163. It can be readily developed by just remove three channels of the NI-9234 and make a smaller version of WLS-9163 for one channel. I would like the product be one unit to achieve a small size. The one channel wireless data aquisition module will have two imporatnt advantages: 1) much smaller size, therefore can be fit into difficult locations; 2) much lower power consumption, therefore can make much longer recording. These two advantages are essential for wireless measurement, thus the product will have good market potential.

May be speaking for myself here, but the M-Series DAQ in USB forms have mass termination option (to connect to VHDCI connectors) and the X-Series do not.  Why?

 

We have hardware that is already setup for the 68-pin cables, and I would like to take advantage of the portability of the USB, and the extended performance of the X-Series vs. the M-Series.  Specifically I was comparing teh USB-6361 X Series and the USB-6251.  The price difference is minimal for the added sample rates and extra counters.  But without the mass term option, I am forced to settle for lesser hardware.  This should be fixed.

This question goes for usb-6008 and 9

 

From the User Guide and Specs:

"The progammable-gain amplifier provides input gains of 1, 2, 4, 5, 8,
10, 16, or 20 when configured for differential measurements and gain
of 1 when configured for single-ended measurements"

 

Why can't I use the PGA in single-ended modes?

 

best

Niels

Suggest NI produce an inexpensive (<$100) USB "stick" that has 2 hardware counters on it for optically isolated measurement of encoders, or other high-speed devices. The stick would have a standard connector it for easy wiring of differential encoders with ABZ lines. The device would enable measuring two separate encoders or track two sections of a shaftless drive line that needs to position-follow. One or two DIO lines would be a bonus. This would seem to be a good fit for the industrial machine markets (at the very least). Today you need to buy a multifunction daq for a several hundred dollars if you want two counters.

 

Contact me with any further questions.

 

 

Thank you!

 

Rick Yahn

QuadTech, Inc.

414-566-7938

rick.yahn@quadtechworld.com

 

NI USB-4432 has 5 input,But only There are 4 channels with software-selectable IEPE signal conditioning (0 or 2.1 mA).

 

 

Make NI USB-4433  5 channels with software-selectable IEPE signal conditioning (0 or 2.1 mA).

 


 


 

I would like to see a new line of HW on the lines of the lego NXT brick.

basically something between the sbrio and low end usb daq.

this could be a bare bones arm processor, low to mid end daq (8-32 dio (fpga to make them optional ctrs i2c/spi pwm  or timmed io, a few Ai and AO).  this line is for stand alone robotics or data logging.  lower cost and power and expandablilty than the crio but not requiring a PC (except as a client) like the crio.  This would fill in to the labview everywhere model, and programmed just as the crio with labview RT and FPGA.  The cost of the crio makes it not practical and an overkill for some applications and for the hobbiest/education robotics market, maybe something like the NXT brick but higher end would be nice to see.

There is a variety of connection posibillities (link below), but I really miss one for high channel counts, like a SubD25.

http://sine.ni.com/nips/cds/view/p/lang/de/nid/1721 

 

Based on this question, I would like to add a new category of events to LabVIEW: Max-events.

 

This category could contain the following events:

-Hardware Added

-Hardware removed

-Configuration changed

    -Scales

    -Channels

    -Tasks

 

If you know other events, please post them.

I'm not sure who reads this, but I'm not seeing any feedback in the forum so I thought I'd post up here.   This may seem like a simple thing, but hopefully my pain will be someone else gain.  I messed with this off and on for two months before I finally figured it out.  It's probably obvious to those who work with this equipment every day and have EE degrees, but not so much to those of us who do not. 

 

Please see http://forums.ni.com/t5/Multifunction-DAQ/Measuring-220VAC-with-CompactDAQ/td-p/1145956 for a description of the issues I was having. 

 

Some will tell me to "search"... well, I did.  ...and everywhere I looked all I found was that I needed to measure from the power leg to ground.  All of the examples either were only measuring 120 which is fine since what you have is one power leg and neutral... which is basically ground!  So those numbers come out fine.  Or they were for 3 phase, which I don't use currently.  BUT when you try and measure anything with two power legs (basically anything between 208VAC to 240 VAC) the numbers don't work out right if you try to measure between each power leg to ground and then try to recombine them and plug them into the Power VI's.  Not one place that I looked did it tell me that I need to measure both power legs across a single channel.  I only finally tried it because I'd done pretty much everything else.  I know this is pretty basic stuff, but when all you give me says one thing... that's what we do.  Just trying to help others.

Thanks,

Chad

In addition to USB-TC01 one thermocouple channel, the device should be able to log ambient temperature. Most temperature data needs to be referenced to something.

I would like to have an programmable gain amplifier in the analog output path that I can use to adjust the amplitude of an output signal.  In control applications, this would be much better than having to stop a continuous task, reload the data with a new amplitude, and start the task again.

 

Ideally, for some of my applications, it would be nice to be able to generate a basic waveform scaled to +/- 1V and then have a property that I can write to while the task is running to set the gain.