NOR-4351 incorrect Thermocouple readings

Similar Questions

• Re: Incorrect accelerometer readings

  I have a strange problem: shortly after the start of my tablet, the accelerometer is weird. Therefore, the acceleration of the screen is always upside down, and it does not meet the rotation of the tablet.

  If I read the readings of accelerometer with a test program, the trend is good, but the zero level is incorrect. 0 g, X denotes + 4 m/s, Y indicates-9 m/s and Z watch-5 m/s. What explains the problem with the rotation of the screen. The only solution seems to be a reset.

  Is that what I can do to solve this problem, or do I need to bring it back? I'm just inside 6 months since I bought it, so I need to know soon...

  PS: This is a Pro to excite 10.1 16 GB, I think AT10LE-A108 is the official type.

  > I feel it was a rogue background process.
  > It is difficult to say which, but I learned that any application can recalibrate (or spoil) the accelerometer.

  Sometimes its very useful restore Android system, but also the tablet to the factory settings. Where the Android system was confused upward through an app or a process, this reset should solve the problem.
  That's why I think you should check it out in case you no it did not in the past.

• Thermocouple readings of the CRIO

  Hello

  I am fairly new to work with Compact RIO and I have problems with thermocouples that I have connected. My Setup has two modules of thermocouple in the NI 9213, NI 9211.

  I have connected a Type K thermocouple (one of each) both of the units. I used the vi FPGA target for reading from the Thermocouple channels as well as the CJC values and put two modules. I also CRIO vi which reference the FPGA vi, and then uses the values and feeds them to the "voltage convert to Temperature.vi. I've attached screenshots of the vi.

  The problem is the output I get is - 2 or 1 degree. When I touch the thermocouple increses value to about 5 or 8 degrees.  The room temperature is about 24 degrees.

  Can someone please help with where I'm wrong.

  concerning

  Bastien.

  Yes, it's the bad VI to be used with CompactRIO.  I'm not 100% sure why this does not work, but I don't know that the scaling VI that you use is designed to be used with NOR-DAQ, not CompactRIO.  Please open the examples for your modules to see the correct way to the scale of the CompactRIO thermocouple data.  I hope that these scaling methods will work for you.  You should find the examples here:

  C:\Program NIUninstaller Instruments\LabVIEW 8.6\examples\CompactRIO\Module Specific\

  This is the best advice I can give you, unfortunately.  If you need more detailed help, maybe someone on the forum knows more what to do about the scale of the data of thermocouples cRIO in degrees celsius.

• NOR-DAQmx Base: Thermocouples

  Hello. I use NEITHER-DAQmx Base for mac on LabVIEW 8.2 and I struggle to get the differential voltage for thermocouples type k of data acquisition that I use. The conversion is easy using the thermocouple vi, but somehow the pressure readings seem not just.

  When using CQI. example of samples vi continuous or acquire it only sample vi, the measured voltage I get just a regular temperature thermocouple are 0 and - 0.00048 (especially remains on 0 if); which for me, is not look right. The tension of the CJC reading also reads about 0.3 V (I don't really know how it works yet, but here it is if it helps).

  A sales engineer field came the other day and seemed to have it. When tinker around with the example vi, he kept getting small positive values that seem to work. In addition, when it is combined with LabVIEW 6.0, the data acquisition system works very well.

  Please, any help would be appreciated.

  K type thermocouples have a maximum temperature of-200 to + 1250 ° C.  The output goes to about-6 mV to + 51 mV for this temperature range.  If you need to use the 0 to 100 mV or + / 50 range mV on your data acquisition card, regardless of the better matches the actual temperatures you will be measuring.

  If you don't you not explicitly connected resistances of polarization, they aren't there.  Look at page 4 to 6 of the user's Guide of SCB - 68 for the advanced features for more information on the connection of thermocouples.

  Lynn

• Great variation on thermocouple readings

  I have to type K thermocouples (two long wires twisted and welded at the end) connected to a map of SCC - 68 (without modules). This card connects to a data acquisition NI PXI-6221 multifunction with compensation of CYC.

  I have install a global channel virtual for the CCM, connected according to the diagram in the user manual, etc, etc-, that everything seems to work fine. When I connect my thermocouples, however, their readings are very sporadic; they could go from 69 degrees F up to 89 degrees F or more.

  Suggestions as to how I can get a more uniform reading? Honestly, I don't care if it jumps around a few degrees, but variations of 10 to 20 degree seem a bit much.

  I have attached a copy of my VI (LabVIEW 8.2) that I use to display temperatures (it's part of a larger system of control, so ignore everything except areas thermal two on the left ).

  Can be measured in differential mode?

  How the signal look like? UM, cleats, white noise?

  What about using a filter? Try fist: enjoy with 1kS/s and uses the average of 300 samples (work of 300ms for 50 Hz and 60 Hz power line noise)

• incorrect thermocouple reading

  I have an NI PXI-1033 with an NI TB-2709 block and I'm under Labview 9. I'm just trying to read the temperature with a thermocouple to any of the eight channels. Unfortunately, when I look at the reading of the measure and menu task Automation Explorer value fluctuates all about the difference from peak to Valley about 50 degrees C. I tested the thermocouple on a multimeter and it gives a good reading. What's wrong. Help, please.

  Once I updated the chassis ground to the shield of the input cable that the noise went away.

• Noise on the readings of thermocouple on the NI PCI-6225

  Hi all

  I have a problem with what appears to be static electricity caused by noise on thermocouples.

  We test with a sand as a medium flowing through a plexiglas window and measure the temperature in the stream. The interaction of mixture air/sand flowing through the plexiglas creates a significant amount of static electricity and our thermocouple readings are severely affected. Is there a way to filter the signal so that my data and off-scale obvious signal analysis tools ignore?

  The filtering I see seems to apply only to high frequency noise. I would like to cut the signals from the TCS to ignore all of the above measures 700DegF and under 32Degf.

  Thank you

  Hi Emi_emii,

  It might be useful to see what the current state of your VI acquisition is - just to get an idea of your overall architecture. I see a couple of alternatives.

  1. You could do some external signal filtering to get rid of the extra load on your son of thermocouple - see this valuable whitepaper on the topic of wiring: http://www.ni.com/white-paper/3344/en/
  2. The extent of the filtering software, you could use the cooker and force the function (http://zone.ni.com/reference/en-XX/help/371361J-01/glang/in_range_and_coerce/) on your data and the use of the Boolean output to hide your actual data or simply to force your MAX/MIN values

  Hope this helps!

• Problem PCI 4351

  Hello

  When I try to use a pci card 4351 for thermocouple with dasylab and nidaq driver, I have 3 problems:

  -first of all, when I used the module of scale to use with thermocouple, I disable it compensation CYC, is possible to solve that?

  -the second is when I record with this card for a long time, I have a lag (+ 2 hours to 2 days) in the Terminal. Is it possible to fix this?

  -third, I ask at OR, if it is possible to use this card with driver Nidaqmx or develop daqmx driver for this card very useful.

  Thank you for your answers

  Moldy,

  It's to the Max, in the area of data. Click on "Create New" and select the traditional virtual of NOR-DAQ channel.

• Thermocouple configured in module module-9221

  Hi all!

  Nice day!

  I try to configure thermocouples type K 6 through the NOR-9221 analog input module and chassis cDAQ-9174. I'll be able to get the direct temperature readings outside this module not being a thermocouple module? Otherwise? Please suggest me how to get the temperature for this add-on module-9221 directly! Quick help will be very appreciated!

  Best regards!

  Tajim

  To build on what the broken arrow, the 9221 is really not at all optimal for measurement by thermocouple.  Most of the measures by thermocouple are between 0 to 80 mV.  The module 9221 is a 12-bit with a range of ±60V module.  The width of the code for this module is about 15 mV and your accuracy is 156 mV.  All your thermocouple readings will be lost in the noise for this add-on.  I would recommend the 9211 or the 9213 for measurement by thermocouple, because each has CYC and is specially designed for thermocouples.  If you want to try an external amplifier, which can run, but you will probably need something that can amplify from 0 to 80 mV to 0 - 60V.

  Kind regards

• Registration of multiple Thermocouples

  Hello world

  I'm watching 4 Thermocouples simultaneously using a cDAQ-9174 and the NI 9211 thermocouple module. I am very new to LabView. I found a VI which seems to do what I want on the forum (I'll hang), but I can't seem to operate beyond recognition the first data channel.

  I think I missed something simple when it comes to select the analog inputs of the VI fort, in order to get the four channels to work.

  I am also open to suggestions for a better example VI that can connect 4 thermocouple readings at the same time.

  Thanks for your help!

  You have to hit the ": 3" at the end of the round.  Select channel 0 from the list, and then add the ": 3" to it.  Who says DAQmx you want channels 0 to 3.  I have a slightly different material (a 9213 instead of 9211) but your VI read the 4 first thermocouples I connected and stacked the traces in the first four graphs.

• 4351 NI NI DAQ traditional for Vista deploy on RT

  We meet the following problem.

  We have several RT platforms with the advice of NOR-4351.

  We have developed the software on LV8.2 with XP operating system and now we are again moving PC (laptop almost) with Vista and LV8.6.

  We found that the traditional NI-DAQ support is not released the LV for Vista OS (unless the MAX reports that Tradidional NOR-DAQ 7.4.4)

  How can we solve this problem?

  Taking into account the fact that the software is deployed on the controller of the RT (PharLap)...

  Sincerely

  Hi Luigi,

  Have you looked into NOR-DAQ traditional (old) for the beta of Windows Vista?

  Another possibility: If you only install devices NI 4351 on the controller of RT and not the Windows PC, you may be able to deploy your application to the controller of the RT of a virtual machine (Virtual PC, VMware, VirtualBox, etc) that are running Windows XP and OR-DAQ traditional (old). (None of these virtual machine solutions supported PCI/PXI devices, but they can run LabVIEW).

  Brad

• control thermocouples

  Hey, I have a strange problem and I hope someone can help. I have been using a program for about 6 months now that basically keeps a cold temperature next to a heat sink and maintains a warm temperature on the other side.  Then I 25 hung in the meantime thermocouples to measure temperatures I can do the analysis of the material in the environment.  My problem is that all of a sudden the readings of the thermocouples were out of control and unpredictable.  I add me automation program so it could run several tests at the same time and in the process developed by this problem.  The weird part is that the problem is also past in the old version of the program now too, and that has worked perfectly for the last 6 months.  I have 25 hung thermocouples and temperatures will all look all right, but then 3-5 of them will be quite wrong at random.  What is interesting about this problem, it is that when I change the thermocouple which become the use of heaters to maintain the set temperature, the values that were wrong again on the right and some other thermocouples start giving invalid data.  The installation program uses a NI 9213 and 3 NI 9211 inputs for thermocouples.  It also uses one OR 9401 to control heaters through a box pulse width modulation power we have.  Someone at - he never experience something like this or have any ideas?  Thanks for any help

  Hey Nathan,.

  Thanks for the ideas.  I ended up spending to playback of multiple samples as you suggested and this error has not popped up once again, so hopefully that fixed this issue.  I think I solved the problem of both weird thermocouple readings! I think that I had a ground loop problem which I fixed it by the grounding all thermocouples to a metal table.  For all those who on their getting odd unexplained readings, certainly experiment with ground everything correctly.

• Cold welding of 2 ° C error

  I use a PCI-6229 to measure temperatures using thermocouples type K and a channel of thermistor for cold junction compensation.  The thermistor cricuit, I've done seems to work very well.  It is the reading of good ambient temperature, which is be 20.7 ° C and is essentially the same as what I get on three different thermocouple panel meters, more it agrees with my cacluations of this thermistor voltage-temperature relationship.  This thermistor is settled in a terminal used on the CB-68LPR, right there where plug thermocouple extension cables.  It fits perfectly in one of the small holes.

  But when I use this channel of thermistor for CCM my measures by thermocouple readings are constantly low, about 2 ° C, even using thermocouples of same that I use with the Panel counters.  The error of-2 ° C is constant in all of my channels of thermocouple.

  With junctions to measure thermocouples is the same temperature as the CB-68LPR, the tensions of thermocouple to the places where the thermocouple extension cables are connected to this block should be 0 volt.  I've confirmed with a voltmeter. If the PCI-6229 map should see 0 Volts on the channels for thermocouple, either by NIST, 0 ° C tables.  It seems that all this has to do is now to add measurements of temperature thermistor.  Better, I can understand, this addition is not right, or not, 0 Volt is equal to 0 ° C, on this forum or something else happens.

  I use DAQmxCreateAIThrmstrChanIex to configure the channel of the thermistor and DAQmxCreateAIThrmcplChan to configure the channels of thermocouple.  The CJC sourse is DAQmx_Val_Chan.

  No idea what's going on, what I am doing wrong, etc.. ?

  Thank you.

  Looks like you do everything right, but THST is close enough to the accuracy of the system.  The K type thermocouples only have an accuracy of 1.5 degrees.  Furthermore, a K type thermocouple voltage changes by about 40 microvolt/degree, and the accuracy of the 6229 (when it is in its smaller range of +/-2V type 0) is 112 microvolts.  It is generally recommended that you do some conditioning on thermocouple inputs before reading signals data acquisition card.  It SCC and SCXI modules already have the conditioning of signals, and the CJCS included.  It can allow you to get better results, but you are still limited by the precision of the thermocouple.

  -Christina

• Is there a single SCXI module adapted to the entries for mixed probes?

  I'm trying to set up an SCXI system to receive signals from a number of different types of sensors. I have a large number of thermocouples for which I decided to use the SCXI-1102 module. I also have a unique pressure sensor (unknown spec so I'll assume type of strain gauge), a unique accelerometer (once again, unknown technique) and possibly a few tensions ahead right (unknown County and spec so assume - 10 v to + 10 v Beach max).

  Is there a single SCXI module through which I can acquire voltage signals, accelerometer and pressure sensor? Or maybe just use 2 modules instead of 3 if I have a SCXI-1530 for my accelerometer and an another module for the tensions and the pressure transducer? I was watching the module SCXI-1121, which looks promising for the tensions and pressures but then was unsure as to what block of connection to use for the combination of signals (possibly, I could live with a - 5V to + 5 v range if necessary).

  (Additional info: I use TC-2095 blocks with my SCXI-1102 module, can not really use spare entered on those voltage inflows).

  Thanks for any help.

  CASE NO.

  It's expensive,

  Thanks for your inquiry. You obviously already did a lot of research on this issue. I fear that it is unlikely that you will be able to use a single SCXI module to perform any function you listed. Necessary accelerometers such air conditioning specialist, it will take a module - as you mentioned already, something like the 1530 (4 channel accelerometer input module) would be ideal.

  However, you have a number of different options for the pressure, voltage and temperature measurements.

  For example, you could buy a mudule 1520 for your measurements of pressure and then use a generalist 1102 b for voltage and temperature (need you the connection block insulated from 1303 to condition the thermocouple readings... and work around the CYC technology for pressure readings).

  Or, you may use the module thermocouple 1102 for your temperature readings and then use a 1102 b to take pressure readings and the pressure. Of course, that would require making your own bridge to the pressure sensor configuration, but this should be pretty easy.

  Before making any final decision, I would recommend that you call your local branch of the NC and speak with a sales representative. Perhaps, a member of the sales field staff might actually come see discuss you it face to face.

  Finally, it looks like you have a number of ways relatively high for some of your reading, is why you decided to use the SCXI platform. I was just wondering if you had considered compact DAQ (cDAQ), which combines the DAQ hardware with signal conditioning. Top spec, ease of use, lower number of channels. Swings and roundabouts I guess.

  I hope this has been of some use to you.

  Best wishes

• Several acquisition module and the error

  Let me start by saying: this is the first written time code to communicate with the DAQ hardware and I'm learning.  I develop a test bed that will have different inputs and outputs listed below:

  cDAQ 9172:

  Mod1: NOR-9211 (4 Thermocouples)

  Mod2: NOR-9211 (3 Thermocouples)

  Mod3: Not currently used

  Mod4:-OR-9201 (flow 6 sensors)

  Mod5: NOR-9201 (5 pressure sensors)

  Mod6: NOR-9481 (4 relays)

  Mod7: NOR-9481 (3 relays)

  Mod8: NOR-9401 (2 float switches)

  Of after a suggestion of a more experienced colleague, I was going to have an another while loop for each type of module running in parallel from my main program.  For loops, I do a "Create Channel" and then "Start Task" as a setting the clock before entering all loop.  I started to do that with the switch float (DI) and the 1 loop for each fo relay cards (DO) and then 1 loop for the 7 thermocouples (HAVE).  That all ran fine with values update as needed and I could control all relays.  When I then added the next loop to read in pressure sensors, I get an error in 'Start the task' for loop making the entrance of thermocouple, saying that the resource is reserved.  I don't know what is the cause, the task name is unique to each loop and that they acquire signals from different modules.  My method works?  Do I need to have just a single loop for all modules?  I don't know how I would do a loop when I have so many different types of data.  I can add screenshots later if needed, I'm not near this workstation currently and it is not connected to the internet.

  Here is a knowledge base that gives a way how to do this

  .. .but really, it's all is creating a 'task DAQmx' and then passing this task to several "Create Channel XX" live (tasks are composed of one or more channels).  It is more readable if you call 'Create DAQmx Task.vi' and then use the task as an input for each of your 'XX.vi create channel' live it was you can even name your task 'Task My AI' and then it's easier to debug.

  Just for the record, the knowledge base does not call to 'Create a task DAQmx' explicitly as the first 'Create channel XX.vi' will implicitly do it for him.