NI 9213

I am trying to plug in a thermocouple into N-9213 and see if i can get measurments of temperature. I am very new to LabVIEW.. i am trying to see if i can get the temperatures in LABview Express ...
it gives the following error. I am not sure if i am doing the write thing. Can anyone help me how to go about this..
Error -88302 occurred at DAQ Assistant
Possible Reason(s): An internal error occurred. --------------------
Error -200486 occurred at DAQ Assistant
Possible Reason(s): Measurements: Specified channel is not in the task. Channel Name: cDAQ1Mod4_ai0

Hey Shanky,
One reason you might be getting that error could be due to not having that channel name in Measurement and Automation Explorer. You'll want to check to make sure that cDAQ1Mod4 is the 9213 you're trying to reference. As well, you may want to reference this post and this post, which describes a similar error. It could simply be that there's something wrong with MAX. Let me know if either of those solutions doesn't work!
aNItaB
Applications Engineer
National Instruments
Digital Multimeters

Similar Messages

NI 9477 DO causing NI 9213 TC noise

On my cRIO-9073 I have basic LabVIEW code accepting NI 9213 thermocouple measurements, calculating some simple logic based on desired setpoints, and then sending out an on/off digital signal via NI 9477 to switch a solid state relay which in turn switches a motor on/off for each. This is all being done with NI Scan Interface for about 17 channels.
Everything functions fine until the Digital Out is set to "TRUE" on one particular channel (10). When this channel switches it throws noise across all the TC inputs and occasionally freezes all of them. Most bounce 10 degrees F high or low and channel 10 reads 60-70 F high. The only way to fix this is to assure that the DO on channel 10 is set to "FALSE" and to reboot the cRIO. I don't have this problem on any of the other channels!
All of the output voltages seem good when read with a multimeter. I've checked the physical wiring many times and cannot find any issues. There is no error out of the scan interface variables in the LabVIEW wiring diagram. Seems to me like the DO module and the TC input module should operate independently if not for the cRIO backplane they are both connected to. The cRIO and the NI 9477 DO module (which needs its own PS to send voltage out) do share the same power supply (NI FP-PS-4) although I can't see how this could be the issue.
If anyone has any suggestions I'd love to hear them! Thanks in advance for your feedback.
- John

Jared -
Each channel of the 9477 is connected to a solid state relay that is switching a dedicated circulating pump motor. Each of these channels from the cRIO is switching the relay with 28 VDC and 1 Amp (or less). On the other side each relay is using about 120 VAC to drive the pumps.
Like I said 16/17 of these channels give me no problems, its only the one channel that throws everything off. I don't have a way of testing just the TC module independently.
I'm thinking of changing out the pump motor. These do go out occasionally causing shorts - although I still have trouble believing this could be whats throwing off all of the TC data. Is that a waste of time or should I focus elsewhere?
Thanks again. - John

Measuring whole module instead of on thermocouple (9213)

Hi
Sorry not sure what board to put this under. Does a cRIO come under 'Field Point family'?
I am using a cRIO 9074 with 8x 9213 modules in (16 channel thermocouple module). The basic premise of my software is to wait for a change of a networked variable, wait for a defined time, record for a defined time, create a file, ftp the file and wait to go again.
I have just started playing and can happily record one thermocouple as below
I actually have 128 thermocouples and where I have the double 'TC0' I would just like to put double 'everything' and just record all 128 channels. Is there a method or do I have to really drag 128 variables in?
Thanks
nice

Hello nice,
If you have LabVIEW 2009/RIO 3.2 or later you can use the programmatic api to access IO and configure modules.
See this whitepaper http://decibel.ni.com/content/docs/DOC-6063 for more information on how to use it.
Thanks,
Sebastian

NI 9213 - cRIO 9082

Buongiorno a tutti,
premetto che utilizzo da poco il cRIO.
Il mio attuale problema è questo: vorrei acquisire il segnale in arrivo dalle termocoppie collegate al modulo 9213 in tensione e tramite
sviluppo polinomiale trasformarle in temperatura.
Sto utilizzando la modalità "scan mode".
Se vado sulle proprietà del blocco 9213 ho la possibilità di selezionare il formato del segnale "raw voltage".
Tuttavia mi sembra di capire che questo valore di tensione sia quello che deve essere compensato perché se applico la formula per lo sviluppo non ottengo un valore di temperatura sensato.
Qualcuno che possa darmi un consiglio?
Grazie
Luca

Buongiorno,
molto probabilmente dovrà interpretare i dati RAW prima di applicare l'algoritmo per la temperatura. Le allego i seguenti link che le potrebbero essere utili:
http://digital.ni.com/public.nsf/allkb/0FAD8D1DC10142FB482570DE00334AFB?OpenDocument
http://www.ni.com/example/26611/en/
Spero che le info le siano utili
Saluti

USB-9213 Calibration question

I am considering purchasing a USB-9213 16 channel TC module but wanted to be sure that it could be calibrated in-house. The calibration procedure posted on NI website says it requires plugging the module into a NI cDAQ-9172 chassis to do this. My question is, can the calibration be performed over the USB connection instead or is there some additional features/connections in the backplane of the chassis that are not avaivable over the USB? Thanks.

Hi hgcdte,
It is required for proper calibration to use a cDAQ Chassis. The communciation is different enough that it would affect the calibration procedure. Post back if you have questions!
Regards,
Dustin D

NI 9213 Stops updating temperature values

I have a CRIO Chassis NI 9074. It has a NI 9213 in the first slot followed by a NI 9205, NI 9264 and NI 9477. This setup is used to read 16 thermocouples, few flow meters, control few blowers and pumps and turn on/off heaters.
When I am using the heater to heat the system, the NI 9213 suddenly (after reading for a few minutes)stops updating the temperature values and is stuck to the old value. The time and temperature at which it gets stuck is different every time. Even if I disconnect a thermocouple it does not detect the open thermocouple. At this time all the analog input values are being updated and the analog outputs and digital outputs are also being updated. I have to reboot the CRIO chassis or cycle power to the chassis to make start reading the temperatures again.
Can you please suggest what is causing the NI 9213 to stop reading and show its old value?
Thanks.

Thanks! a lot body.
That was my problem, bad ground. My system have the heaters insulated with ceramic from the chassis, and obiously that avoid the ground. I put gound in all of them and voala, problem solved.
Thanks again.
Ferdinand Martinez
FMO Automation LLC

How to simulate NI 9213 and NI 6211 modules in LabVIEW?

Hi All,
I've been working on a VI in LabView 2011 that communicates with the modules NI 9213 and NI 6211. I'm currently overseas and would like to continue working on my VI without having the devices physically connected to my computer. Is there a simple and quick way to simulate these devices or to replace them by virtual ones so that I can test my programming?
Kind regards,
Thomas
Solved!
Go to Solution.

Go into MAX and right click on devices and select Create> New>Simulated DAQmx device and pick the devices you want.
Note: I am posting from my phone and wording may not be exact - I am going from memory but you should be able to figure it out. Also, the simulation features are fairly limited. For example, analog input is only a 1kHz sine wave.

[svn:fx-trunk] 9213: Adding missing ASDoc comments to GraphicElement

Revision: 9213
Author:   [email protected]
Date:     2009-08-10 17:29:10 -0700 (Mon, 10 Aug 2009)
Log Message:
Adding missing ASDoc comments to GraphicElement
QE notes: None
Doc notes: Review ASDoc comment additions
Bugs: FLEXDOCS-531
Reviewer: none
Tests run: none
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXDOCS-531
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/AdvancedLayoutFeatures.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/StrokedEleme nt.as

Vmware not fully recognizing USB-9213

Hi All:
I am running VMware Fusion 2.0.7 hosting WinVista SP2. I plug in a USB-9213, and I only get a partial recognition of the device. I get the New Hardware Found for the 9216 carrier module, but never the same for the 9213 module connected in the carrier. Of course this means DAQmx and MAX don't see the device to let me use it. I can install successfully a virtual 9213 in MAX, but I can't get the real device fully installed. VMWare is running in Mac OS 10.5.8, and the USB is configured so VMWare can see it and use it as the partial New Hardware Found path seems to show. Any ideas how to get through the last hurdle? I know the USB-9213 is good, since it installs and runs fine in WinXP machine I have access to.
bj

Hi Brad:
I just finished upgrading to MAX 4.6.2 and DAQmx 9.0.2. (Should I look for even newer versions?) This represents progress, as the NI-9213 is now seen in Device Manager (and System Profiler on the Mac side), but it is still not seen in MAX. I could create a simulated NI-9213 in my older versions, and I still can, but the one I create now does not work while the old simulated one did work. The new simulated NI-9213 always fails Self-Test. (And deleting the simulated device hangs MAX. It can be deleted only on the restart of MAX) The fact that I could create a working simulated NI-9213 under the older DAQmx version 8.8 had led me to believe that I had a new enough version. The basic issue is still there though, I can not see the real NI-9213 in MAX, so I can not use it in LabVIEW. It does not matter if I have the simulated NI-9213 present or not in MAX, the real one is never seen there, but it is always seen by Device Manager now. The simulated one has also gone invisible to LabVIEW while the older one could be used there. By the way, sorry for being dyslexic yesterday when I kept typing 9123 instead of 9213.
bj

Higher input voltage: 9213 Thermocouple Device with CompactDAQ-9178

Hello,
We're currently using a NI-9213 thermocouple device with our cDAQ 9178 chassis. We need to take temperature measurements on pcb components such as voltage regulators and cathodes of diodes, thus would to use our 9213. However, we've noticed that input volage on the 9213 device is +/-78mV. Are there any options or methods to use the 9213 with thermcouples that possible be attached to components that may be as high as +25vdc?? Thanks for any ideas!

Use isolated thermocouples. They tend to be bulkier and have slower response times, but might be an option. Omega has 24 AWG thermocouples with PFA insulation rated to 250 C for example. They also have many other styles.
Lynn

Thermocouple device 9213, 3 questions

Hello Everybody,
I am using the NI USB 9213 with the USB 9162 carrier. I am taking measurements(continuous mode) by using all 16 channels.However, there are three newbie questions I would like to ask.
Firstly, I am using 3 DAQ assistant VIs. Each one uses 5 channels(the third one uses 6) that represent an area as perceived by me, namely, Upper, Middle, Lower. In order to get measurements from all three tasks, I have put true constants to the stop input of each VI and have connected the error out to error in to acquire measurements from each DAQ in an order. My question is, If, When I am changing the temperature of a channel that belongs to Upper VI and at this specific moment my program is acquiring data from the Middle VI, is the delay of response negligible?
Secondly, I would prefer to use one Daq assistant for all channels, but is there a way to plot the responses in more than one graph?
Lastly, for the former case where I am using the three tasks, If I change the acquisition mode in High speed, will this apply to all channels, even though they are used in three different tasks?
Thank you in advance,
Ioannis

Using 3 separate DAQ Assistants makes no sense. Use one and then you can just use the Split Signal function.

SBRIO slot 1 thermocouple module 9213 not detected on aluminum plate, while in other 2 slots working fine, any reason ?

Hi,
i have a peculiar problem,
I have a sbrio 9642XT mounted on an aluminum plate (also connected to earth ground) along with 9213 thermocouple on slot 1 and 9477 digital out module on slot 3.
previously this setup used to be on an acryllic plastic plate. and now when i shifted to the aluminum plate the thermocouple module is not being detected by labview project under chasis, while the 9477 is still being detected.at slot 3
i placed an analog inpt 9205 module on slot 1 just to see if there is a problem with slot 1, and yes the new module is also not detected on slot 1,
so placed it on slot 2 and now the thermocouple module is detected and works fine on slot 2.
the attached picture shows the Ungrounded T- type of Thermocouple Probes that I use , these are immersed in ice water and in some other inert liquids to read the temperature
so my question is, is the problem related to grounding issue caused by liquids and did it ruin the slot of the SBRIO some how or is the sbrio just got faulty after using for an year. or is it got something to do with the mounting on aluminum plate (earth ground)
also i never used slot 2 before.
is there a way to test in any other way to know if the slot 1 is ruined because of the above reasons or is it a software issue
i dont want to ruin the slot 2 of the sbrio by placing that thermocouple module. please help
many thanks,
Attachments:
thermocouple picture.pdf ‏105 KB

Hi Freemason,
Nothing you have described should be causing a slot to stop working; as long as the sbRIO is properly mounted and not touching the backplane, it shouldn't be a problem. If your slot 1 is not working, you could also send the board in to National Instruments for repair. Are you still under warranty?

9213 thermocouple

Hello,
I'm doing a thermal conductivity lab and I need to know whether the maximum and minimum temperatures listed with the 9213 thermocouple correspond to expected measurements or what can be measured? Thank you for your time.

The 9213 is not a thermocouple. It is a module which can read them. Since there are many types of TCs and the 9213 can be configured for most of them (8 types) you can read almost any conceivable temperature. Read up on the various TC types and see which one suits your app...
Using LabVIEW: 7.1.1, 8.5.1 & 2013

NI 9213 FPGA Node duplicate terminal

Hello,
When I run the subVI for the NI 9213 Getting Started.lvproj, "NI 9213 Gettting Started (FPGA).VI, get a error statitng that the FPGA node has duplicated terminals. When I look at the terminals I don't see any duplicated ones... I can't seem to edit this VI also. What could be causing this error and how can I resolve it?
Thanks
Jose
Solved!
Go to Solution.

OK,
I talked to an engineer and it seems that I had to separate the Auto Zero terminal from the rest. I opened a new node where only the Auto Zero was located and removed it from the original node. I was able to compile it untill I got a new error that says:
"You cannot run this VI because the target resource does not match the actual type of device.
Right-click on the FPGA target in the Project Explorer window and select Properties from the shortcut menu. Enter a Resource on the General page that matches the target type."
I went to the FPGA Target, but and I think that the default Chassis used is 910x. I'm using 9114, I want to change this but I can't seem to be able.
Jose

NI 9213 Thermocouple connection problems

We recently got the NI 9213 16-Ch 24-Bit Thermocouple Input and we can't get the thermocouple wire to stay securely plugged in. I looked at the manual and my thermocouple wire is the correct size and length. It said to stick a screwdriver into the hole to activate the spring and then insert the wire, then remove the screwdriver. After removing the screwdriver the wire is still loose and falls right out. What is the deal and how can i get the thermocouple wire plugged into the device.
Thank you for the help

Does the screwdriver fit completely in the hole to unlatch the spring? I've had similar problems when the screwdriver was too large to go all the way in.

NI 9213

Similar Messages

Maybe you are looking for