Thermocouple in USB-6210

Hi,
I would like to know how can I read temperature in a USB-6210 device with thermocouples. Labview 8.5 don´t recognize thermocouple tasks. Is it necessary configure a CJC? How can I do it?

Hi VAIronman,
I'm not sure why the previous poster posted in the digitizers forum back in the day, as the USB-6210 is an M Series DAQ device and would probably receive better responses within the Multifunction DAQ support forum. However, I may be able to provide some suggestions from my previous experience with the DAQ products.
In terms of his sensors, if they are thermocouples or thermistors, we have specific tasks in DAQmx made to measure these components. Essentially, we are taking a voltage measurement from them, but the tasks will automatically scale and convert the data into the appropriate temperature based on the configuration you set for the specific thermocouple or thermistor that is being used. If the client is using LabVIEW, the easiest method would be to drop down a DAQ Assistant Express VI on the block diagram, and create a task based on the measurement he is making. For one of the temperature sensor types, he can choose Acquire Signals » Analog Input » Temperature and then select one of the sensor types he is using.
Click "Next" then select the channels to acquire on (hold shift and click the channel names to select multiple channels). Click "Finish" to complete the wizard and enter the channel configuration.
Here you can configure everything specific to your sensor and measurement. The best part is, there is a tab at the top labeled "Connection Diagram". If you select this tab, you will see exactly how to wire each channel.
For the other two channels connecting to the analog output source, you probably want to configure those as just a standard Voltage task. The same connection diagram can be found in the DAQ Assistant, but note that the connection will change depending on how you configure the terminal configuration. You can select between differential, referenced single-ended (RSE), and non-referenced single-ended (NRSE), each of which will change how the device is to be connected. The image below shows a channel being connected in differential mode.
If you have any specific questions further related to this device, I would suggest posting in the Multifunction DAQ forum linked above. If you have questions regarding the DAQ Assistant or DAQmx tasks, I would also suggest doing a few quick searches on ni.com or visiting the Getting Started with NI-DAQmx: Using the DAQ Assistant tutorial. Additionally, it may be worthwhile taking a look at the USB-621x User Manual, which has a lot of in-depth information on the device and different measurements it is capable of. Note that the DAQmx task creation above can also be performed in Measurement and Automation Explorer by right-clicking the device and selecting "Create Task..." Hope this helps!
Daniel S.
National Instruments

Similar Messages

How to control a NI USB 6210 from a Lab View program?

Hi,
I started today with Lab View with some earlier experience long ago.
While it took me only about half an hour to get my first program running (great), installation time nor included (of course), I meanwhile read documents for some hours and cannot find out how to control measurement hardware in Lab View.
I want to use a USB 6210 to set a 1-bit digital port. But at the moment there is no USB6210 available so I wanted to write (or do you say draw ?) the program without it and if possible simulate the hardware.
I drew DAQ Assistant into my block diagram and selected digital line output but get "No supported devices found". I don't know if the appropriate driver was installed during Lab View installation.
Also I don't understand the mechanism between DAQmx, tasks and the real hardware. Now I have a "Digital Bool 1Line 1Point" Control in my block diagram. How do signals get from program flow to hardware pin? How can I create a simulation for not connected hardware?
Any help is greatly welcome
Thanks a lot
Martin

Okay here is some more tutorials if you get some free time, specifically the hardware stuff will be relavent.
NI Learning Center
NI Getting Started
-Hardware Basics
-LabVEW Basics
-DAQ Application Tutorials
3 Hour LabVIEW Introduction
6 Hour LabVIEW Introduction
Self Paced training for students
Self Paced training beginner to advanced, SSP Required
LabVIEW Wiki on Training
Launch MAX, it was known as Measurement and Automation Explorer, there should be a shortcut in your start menu / desktop. Under devices and interfaces you can find your hardware and open test panels to control it. This is the first place to ensure your hardware is working. If the device isn't seen you'll need to install the drivers and DAQmx software. If it is there, great.
Now launch LabVIEW. The easiest way to control hardware is using the DAQ Assistant. It has many limitations and isn't recommended for large applications. But for something quick and dirty it works fine. You'll find it under the Measurement I/O >> NI DAQmx palette on the block diagram. If it isn't there you may need to reinstall the DAQmx drivers. This can happen if you installed DAQmx before LabVIEW.
Also you'll find under Help >> Find Examples on the toolbar, many examples on controlling hardware. Feel free to post some code if you are having problems.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

How to run 3 operations through my USB-6210 at the same time w/o gettin an error

Hi, I am using a USB-6210 data logger from national instruments to collect data and run it through labview 7.1. However, when i try to run two labview files at the same time on two different channels in the data logger i get an error #50103 "The specified resource is reserved the operation could not be completed. How do i fix this?

Hi Mariachi,
I believe your overall project will be to collect data from
your USB-6210 on multiple lines and save this to a file. Photon Dan is correct
in the reason why you cannot use multiple tasks – because of the multiplexor,
only one AI task can be run at a time. I would suggest putting all lines into
one task and program, therefore eliminating the error, the need for multiple VI’s,
and writing all data to a file at once. If you have further questions, I would
ask that you post more detail about how you are collecting data (LabVIEW?
SignalExpress? Etc) and your program. Unless you are connecting to other
computers, you will not need to use VI Server, TCP, etc.
David L.
Systems Engineering
National Instruments

Using timer/counter with PCI-6221/USB-6210 to control timed-loop VI

Dear all,
I need to ask about two devices and one of their functionalities, PCI-6221 and USB-6210. For our NI-based system, we need to control some timings in a Timed-Loop vi, for that currently we are using PCI-6221 and we give external TTL signal (at 1 kHz) to it,
recenntly we need to make some changes and for that we found USB 6210 DAQ to be more suitable, but we need to clear ourselves on some specific things.
Can the counter/timers functions available in the either PCI 6221 or USB 6210 can be used to control the Timed-loop VI by giving external clock or by using their own internal clock source?
Although we are using external clock with the PCI 6221 but we want to know about the usage of their internal clock, also are controlling timed-loop also possible for USB-6210
Also... What if we use the RTOS, are they still able to control the timed-loop VI without giving any 'EXTERNAL CLOCK' and using the internal clock sources of the DAQs
Waiting for reply,
Bests,
RaJaf
Solved!
Go to Solution.

Ben,
I having read previous email which I send earlier with general overview, we discussed in more detail within our team and I am giviing the specific answers.
Please check in RED the most recent answers. Blue are the questions/suggestions by your side.
1.    Using Internal hardware clock of PCI-6221 would enable us get rid of external clock, but how to divert the internal hardware clock to the current settings. Any idea (can you provide us with some reference manul for otherwise). I mean is there some flag-bit etc. or VI
2.       Is it also meant that with the installation of RTOS the timed-loop can directly get the timing source from the internal hardware clock PCI-6221? --- How???
3.       In order to make desktop to work as RT system, what is the hardware (motherboard, processor, etc..) requirement? What are the LabVIEW modules (specific name) that needed to be installed? Our platform is LabVIEW 8.6. (Currently we have windows-7 with i7 core processor)
What kind of application are you intending for this system? ---- high-speed laser scanning system.
Are you most concerned about accuracy, speed, or responsiveness? To control the laser mirror scanner to move at 1 kHz or 2 kHz speed. On the other hands, using PCI-5105 (128 MB memory) as a DAQ for real-time/on-the-fly data processing.
Bests,
RAJAF

Read data with trigger usb-6210

Hello
I'm using LabView 8.6 full development
First sorry for my english
My problem is: I'm using USB-6210. I connected a encoder signal to one of digital inputs and then generate trigger signal according to encoder. Now I need to read data from 4 analog inputs at the rising edge of trigger. But I must read all data at one time. I have around 200 measurements points. So my idea is: when the trigger appears card read data, but I not taking them. I take data when card have all 200 measurement points. Is it possible to do with this card? and how. Frequency of trigger signal is around 1kHz
Bartek

Hello Bartek,
If I understand correctly, you need to start Analog Input (AI) measurement on 4 AIs with rising edge on digital input (DI). Moreover, you want to read all configured samples at once.
If I understand correctly, than you need to perform Finite Samples AI Acquisition with Digital Start Trigger.
I strongly recommend to read some manuals to get familiar with your device. I would start with M Series User manual, which I personally consider to be very useful for finding most important information about your device. Moreover, there might be some "specialties" for USB-6210, which you might find in NI USB-621x Specifications.
Please go trough following sections of recommended manuals:
AI Start Trigger Signal - M Series User Manual page 4-35
Chapter 11, Triggering of M Series User Manual
NI USB-621x Specifications - page 9, External Digital Triggers
If you wonder how to realize the measurement in LabVIEW, I would point you to Example Finder, where you can actually find such a example.
In LabVIEW menu, open Help -> Find Examples...
Navigate to Hardware Input and Output -> DAQmx -> Analog Measurements -> Voltage
Open Acq&Graph Voltage-Int Clk-Dig Start.vi
I believe this example should perform exactly what you need.
Best regards,
Martin Stefik
Application Engineer
Czech Republic

USB 6210 Using counter as an external clock

I was referencing an old post for how to read and write data from a quadrature encoder. I am using a USB 6210 card along with Labview 8.2.1. In the previous post it describes needing to:
"You will have to create an external clock using the other counter on
the board then route the signal either externally or internally"
I do not know what this means and I do not understand what is required to do such (Changes to wires, change the Vi...etc). If someone could please shed some light on this I would really appreciate it.
I am basing my approach on the following NI example:
Meas Angular Position-Buffered-Cont-Ext Clk.vi

Hi rose8,
The example you are referencing requires an external clock to basically take samples of the angular position based on time. For instance, you can rotate your angular encoder all you want, but it will not save which position you are at until a sample clock rising edge is seen. When the sample clock rising edge is seen, then it places that position into a buffer, and continues to wait for the next sample clock rising edge to happen. Every time the rising edge happens, the position of your angular measurement is recorded one point at a time, stored in a 1D or 2D array.
The sample clock cannot be an on board clock that is already created. So now, we look at what sources we can use for our external clock to sample the position of our encoder and save it in our memory buffer. We can use an external source and bring it into the board, or we can create a clock using another counter on the board. Since you are looking to do this, I'll assume you want to create a clock from there.
In software, you specify two counter tasks; one to measure your angular position and one to generate a pulse train. The pulse train you generate will be the sample clock for the buffered angular position measurements you are taking. Now, you can route this externally or internally, based on your application. The easiest way is internally, because it doesn't require any additional wires to accomplish.
To route internally, all you have to do is for your DAQmx Timing VI, specify CtrXInternalOutput from your USB 6210 as the source, where X is the counter you generate your pulse train on. To see this source as an available selection, right click your Resource Name and select I/O Name Filtering from the shortcut menu, and then be sure that Include Advanced Terminals is checked.
In programming, you would want to start your angular position task first, and then start your clock generation from your second counter. They will run in parallel and just be sure to clear both threads at the end of your program. Hopefully this clears up some confusion for you.
Kyle A.
National Instruments
High Speed Digital I/O Product Support Engineer - R&D

I need help changing a VI from NI PXI-1042Q to USB-6210

Hello all. This is my first post, and I apologize ahead of time if it's in the wrong place or is inappropriate... I was instructed to come here for help.
I am working on changing a VI that is functioning perfectly with an NI PXI-1042Q over to a much smaller unit, the USB-6210. Supposedly the USB-6210 can handle the same inputs/outputs that I need (one analog input read at 30 kHz, 2 digital outputs written at 10 kHz), however I am having a bit of trouble getting it to work properly. The outputs seem to go where they are supposed to, but the new system is orders of magnitude slower than the original, and for the system I am using this is unacceptable.
I'm sure I'm doing something wrong, but I'm about as new to LabView as you can get so I have no idea where to start. Any help would be appreciated.
Additional info you might need:
LabVIEW 2010
The VI is attached.
Respectfully,
Emrys Maier
University of Texas at Arlington Research Institute
Research Assistant
Solved!
Go to Solution.
Attachments:
Need_to_work_on_USB-6210.vi ‏250 KB

one is using the PCI bus the other is using USB
(And probably has some power management problems and a 1.0 device on the hub)
A Quick link to USB FAQs- pay attention to FAQ2 1-3
USB Plug-n-Play Devices (Windows)
Options
Mark as New
Bookmark
Subscribe
Highlight
Print
Email to a Friend
Report to a Moderator
‎01-22-201202:20 PM
In this topic we will discuss some of the common problems that have been observed using USB devices with LabVIEW on Windows operating systems. Many of these points are also applicable to other environments but the examples will be use the Windows 7 OS.
FAQ 1 : My USB device stops working unexpectedly.
The first thing to look at is the OS power saving options. There is a global trend towards developing "Green" electronics and energy star ratings are getting fairly common. "If its not being used shut it off" is nothing new. Cavemen learned how to bank a fire to preserve energy that would otherwise be wasted. Likewise, the Windows OS has a power saving feature to shut down power to the USB hubs when no user activity is present. In Automated systems this feature can cause problems since removing USB hub power will shut down the USB device. Solution: Use the device manager to change the USB hub Power Options.
FAQ2: I set the power options and my device connection is still unreliable: Remember, those computer USB ports are often the cheapest that can be mounted on the chassis and share the PC system power supply to supply USB Power. Most uses of USB are temporary connections like a thumb drive or a camera. These connections do not require high reliability since the user is right there interacting with it. Power surges and fault tolerance at worst cause the operator to retry the data transfer. Automated systems require a bit more robustness. Solutions:
1) ALWAYS use an external self powered hub. Perform your engineering due diligence and inspect the devices specifications too- If you can't find them for that device that should clue you to seek an product from a vendor that WILL publish their specs.
2) High noise environments require the use of ferrites on the USB cable- and don't buy the cheapest cable either! The cheap ones are poorly shielded.
3) PROTECT the HUB connections- If you have a USB2.0 device and Joe User plugs in a 1.0 device in a open slot managed by the same hub- Bingo every port on the hub may back convert to USB1.0. WORSE there are a lot of damaged or marginally engineered USB devices out there. Joe User's device may cause power fluctuations when it is inserted or removed from the hub just don't let it happen!
FAQ3: I am testing USB devices and the OS can't find them anymore.
This is a Plug-n-Play feature that deserves some exposure. When you connect a P-n-P device the OS remembers its serial number in a HKEY (Hive-Key) registry entry. This is helpful when (for example) you want a specific instrument, Say an NI-USB-6008, to show up as a DAQmx Device with VISA Alias "MyDAQ1" every time it is plugged it. On the other hand, If you want to test a line of USB-Serial converters this can be problematic since the P-n-P driver will mount the first serial number as "COM3" and the next as "COM4" add infinitum until the enumerator controller in the registry and VISA recognized aliases get used up. Solution: Use the Windows registry API and the Hardware Configuration API in LabVIEW to clear unused VISA Aliases and HKEY entries. Speak with your staff IT professional about HKEY structure and possible side effects before developing a plan to edit registry entries.
Jeff

Buffered event counting: migration from E/M series to NI-USB 6210

Hello,
I create a project developed in LabWindows CVI that does buffered event counting.
The project ran on E/M series for a year. Now I have to migrate to NIDAQ-USB and precisely NI-USB-6210 (that is a M-series). The problem concerns reading acquired samples. The buffered event counting that I need is performed in this way:
1) Start a buffered event counting task
2) After n seconds, read the number of samples and read the samples
3) Stop the task
This procedure works fine on E/M series on PCI bus, but it does not work with NI-USB. With NI-USB, the number of samples is always 0. I link a project that demonstrates that (the "after n seconds" clause is simulated by pressing "stop" key).
After many tries, I saw that the problem is in reading number of samples and so I modified the sequence of operation in this way:
1) Start a buffered event counting task
2) After n seconds, try many times to read the number of samples
3) Read the samples
4) Stop the task
After some houndreds of attempts, the number of samples moves from 0 to the correct number of samples...It seems a bad working....And I don't know after how many attempts I can surely assert that no samples effectively "crossed" card input....
Is there an error in my procedure? Have I made some incorrect operations? Or maybe is there a inconsistency in NIDAQmx driver?
Attachments:
Provausb.zip ‏463 KB

Hello Luca,
I changed the code a bit and I found something interesting about your situation; in the attached VI there is your CVI project modified as follows:
After the Stop button hes been pressed, and the corresponding callback function is called, we read the acquired samples two times: the first one we ask for 1 sample only. This allows to avoid the USB transfer mechanism issue and then, with the second read function it is possible to get all the remaining samples acquired (selecting -1 as "number of samples to read");
Hope this helps you,
Best regards
Fabio Mussi
P.S. A SR request about this problem has been opened too. If you need more information, call me at 02-41309217;
Fabio M.
National Instruments
Embedded & OEM Systems Engineer
Attachments:
Provausb_modified_2.zip ‏471 KB

Trigger numérique sur une carte NI-USB 6210

Bonjour,
Je vous remercie d'avance pour votre aide.
Ce matin en voulant tester le programme (sous-VI) en pièce-jointe. Je me suis rendu compte que je n'arrivais pas à voir le signal de déclenchement qui est un
front montant (impulsion de 10V)
Mon programme est censé remplacer un oscilloscope pour mesurer une constante de temps sur le moteur (je ne sais pas si c'est claire), je pensais que le soft à faire serait simple mais à force de faire des modifications et des essais. Je ne sais pu, si il est apte à faire ce que je lui demande ... Du coup, je ne sais pas si le problème vient du câblage entre le moteur et la carte ou sur le soft.
Ma question est : Est-ce que mon Sous-VI peut mesurer la constante de temps du moteur ( 200 points sur 2 ms) lorsque mon trigger est déclenché?
Résolu !
Accéder à la solution.
Pièces jointes :
Mesure_de_constante_de_temps-Sous-VI-2-machines d'état.vi ‏125 KB

Salut alexandrefcsm,
Premièrement pour ta question sur le tableau des charactéristiques des entrées numériques:
- Vil est la tension d'entrée pour lequel un état numérique bas est détectée.
Pour n'importe quel tension comprise entre 0 et 0.8V un état bas sera détecté donc oui une tension de 0.5V sera considéré et mesuré comme un état bas part ton système de mesure.
- Vih est la tension d'entrée pour un lequel un état numérique haut est détectée soit une tension comprise entre 2 et 5.25V.
- Toute tension détecté qui se situe entre 0.8V et 2V correspondra à un état numérique indéterminé.
Concernant ton système peut-tu me donner des précisions sur les branchements que tu effectue sur ton NI-USB 6210 et quelle entrée tu utilise pour déclencher ton trigger ? Pourrais-tu fournir le VI "Variable global - test.vi" qui est demandé lors de l'ouverture de ton VI mesure_constante_de_temps ?
A +
Louis
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

Mesure de fréquence avec NI usb 6210

Bonjour,
Je viens de faire l'acquisition d'une carte NI USB 6210, je cherche à recupérer la fréquence de mon signal alternatif 50hz, mais je n'y arrive pas.
J'ai cabler en entré de l'entrée PFI1 in et DGND mes deux fils conducteur, et ensuite sur Labview signal express j'ai créer un DAQmx fréquence. J'obtiens comme résultat un nombre qui alterne entre 63 et 255. Je ne trouve pas d'expliquation à mon résultat...
Merci d'avance pour votre aide

Bonjour Rj293,
Les caractéristiques de la carte USB 6210 en niveau TTL sont:
- 0/0.8V pour un niveau logic bas
- 2/5.25V pour un niveau logic haut
Avec une amplitude de 2.5V votre mesure de fréquence devrait fonctionner.
Cependant, le signal sinusoidale que vous utilisez à une amplitude de 2.5V en Pkk, et une valeur moyenne nulle? Par ailleurs, pouvez-vous joindre les deux courbes (sinusoidale et carré) avec echelles?
Cordialement,
Rémi D.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Les rencontres techniques de NI - Mesures et acquisition de données : de la théorie à la mise en ...

Acquistion avec un thermocouple type K et NI USB 6210

Bonjour,
Dans le cadre de mon stage, je suis amené à utiliser une carte d'acquisition NI USB 6210.
Avec ce matériel, je dois acquérir des températures avec des thermocouples de type K.
J'utilise la tache température comme indiqué dans MAX. Cependant, la valeur varie relativement fortement (+ ou - 5°C) et au bout de quelques minutes dérive complètement vers des valeurs incohérentes (par exemple valeur négative).
J'ai donc plusieurs questions :
La carte NI USB 6210 convient t-elle pour une mesure de température avec un thermocouple?
Pourquoi mon signal dérive de la sorte?
Y a-t-il une autre méthode d'acquisition pour ce type de mesure (thermocouple)
Merci d'avance pour vos réponses.
PS : Une version simple du VI que j'utilise est en pièce jointe.
Pièces jointes :
Temperature.vi ‏28 KB

La carte USB 6210 n'ai pas faite pour faire des mesures sur thermocouples, mais vu la sensibilité et la précision de la carte, vous pouvez quand même le faire.
Par contre attention cette carte ne calcul pas automatiquement la température de soudure froide, donc la valeur de votre thermocouple sera une différence de température uniquement (entre la sonde de votre thermocouple et le raccordement de votre thermocouple).
Pour améliorer la précision, j'ai modifié quelques trucs dans votre vi, vous le trouverez ci-joint :
Chef de Projet
ERM Automatismes Industriels
Certified LabVIEW Associate developer
Pièces jointes :
Temperature 2.vi ‏18 KB

NI USB 6210 TTL signal

I am trying to get the NI USB 6210 to talk to a Bio-Logic VMP3 battery cycler through TTL signals and was wondering if someone could direct me to some relevant examples? Basically, I am assuming that the PFI <0..3> ports can accept TTL signals and that the PFI <4...7> can generate TTL signals. Could someone please confirm this? Also, is there an example on the USB 6210 or some related device's signalling capabilities?
Thanks a ton!

Have you even opened the examples that come with LabVIEW? Help>Find Examples>Hardware Input and Output>DAQmx>Digital Generation.
Your manual explains the pinouts.

Pinouts for Connecting Thermistor to USB-6210

I want to connect a thermistor to a USB-6210 for cold junction calibration. I cannot find which pinouts to use. Can you please help?

Hello mhschmid. In terms of connecting your thermistor to the USB-6210, you can simply take a differential measurement across two analog input channels (for example pins 15 and 16). Then, you can configure a DAQmx task to automatically convert that voltage into a temperature by creating a DAQmx temperature task.
In regards to using CJC with a thermistor, that isn't necessary. A thermistor is a resistor that varies on temperature and thus does not require CJC. However, a thermocouple requires CJC to be completely accurate since the thermocouple is composed of two different metals introducing a voltage difference at the junction of the two metals. So, if you want to connect a thermistor to the 6210, CJC is not required. If you want to connect a thermocouple to the 6210, then you can configure the CJC only in software (Measurement and Automation Explorer or LabVIEW) since the 6210 doesn't have a CJC sensor on it. I hope this helps! If anything needs clarification, I will be monitoring this forum.
Brian Fleissner
National Instruments

Event counter using USB-6210 analog

Hi,
Any suggestions or directions where to look to generate a VI that would record event from a magnetic counter of a mouse wheel. I would like to record up to 16 wheels using the USB-6210 device. Thanks!
VO2max

Thanks for the extra information.
The 6210 actually has two counters, so you could count the edges (on two of the wheels) if the signals are TTL compatible. You can use the Count Digital Events.vi example to help you get started. From LabVIEW, it can be found at:
Help » Find Examples... » Hardware Input and Output » DAQmx » Counter Measurements » Count Digital Events
If your signals are TTL compatible, I would highly recommend purchasing a PCI-6602 and using this method for all 8 channels. You could modify the example code by increasing the delay (software-timed sample rate) to a larger value (say 1 minute), and logging the results to a file as you run. Doing this would log the value of the event counter every minute, and would keep the file size relatively small (about 15kB if you run for 8 hours).
If you must use a single 6210 and require all 8 channels, the only option would be to use continuous analog inputs. You would have to sample at a high enough rate to not skip the pulses (I am not sure what that is without knowing more about the signal), and then process the digitized signal in software to determine the information that you need. I would use the Producer/Consumer design template in conjunction with a continuous analog input example to get started. In the consumer loop, you would have to implement the functionality of the counter in software.
Using a hardware counter would be preferrable to using analog inputs. The counter is made for exactly this type of task, and implementing it in software can be complicated as well as processor intensive. If you have any questions let me know, I'm happy to help you out. You can always try out the counter task on the 6210 for two wheels to see how it will work before deciding whether or not to purchase a new board.
-John
P.S. After your first post I had assumed that you were testing computer peripherals, but it looks like you actually have eight rodents. We had a good laugh over here over my confusion.
John Passiak

Can Ni daq usb 6210 measure distance if attach with sharp proximity sensor?

good evening. my name is hadi from university tun hussein malaysia. i already bought National instrument device DAq usb 6210 for my final year project. did my device can measure distance if i attach it with sharp proximity distance sensor.. hope your company can teach me or guide me. tq

Mike,
There are a couple of options for you to get your SCXI system up and running. You will need either a M-Series or an E-Series card to connect to your SCXI system or you could look into the NI SCXI-1600 which is a controller for your SCXI chassis and would allow you to connect your laptop to the controller through a USB cable. This controller is going to operate similar to the E-Series Cards and the M-Series Cards.
We also offer a couple of PCMCIA cards that would allow you to integrate the SCXI system with your laptop. These are the NI DAQCard-6036E and the NI DAQCard-6062E. Unfortunately, your NI USB-6210 is unable to be used as the Data Acquisition device for your SCXI chassis. The list of DAQ cards that are possible for use with your system can be found here under the "Controller" tab.
http://ohm.ni.com/advisors/scxi/pages/scxi/modules.xhtml?conversationContext=1
Also we have an older SCXI Getting Started Manual that you can find here:
http://digital.ni.com/manuals.nsf/websearch/C195895E8C9CAE3D8625691F004DB285
Aaron W.
National Instruments
CLA, CTA and CPI

Thermocoup​le in USB-6210

Similar Messages

Maybe you are looking for

Thermocouple in USB-6210