Thermocouple Measurements using an RTD for CJC

I am using an SCXI 1001 chassis with SCXI 1102 cards attached to TBX 1303 units and also SCXI 1121 cards attached to TBX 1328 units. I need to measure a number of K and T typre thermocouples in this system (using 1102 cards), and was hoping to use a PT100 RTD for my Cold Junction Compensation. Is it possible to achieve this by using the excitation current from an 1121 card and measuring the RTD value with the 1102 cards. It seems that when trying to select the CJC source in Max in the 1102 setup screen, there is no capacity for reading values from cards other than 1102 cards i.e I can't read the 1121 values.
What is the best way to achieve this using the setup I have?

James,
On the virtual channels of SCXI 1102 MAX configuration if you have not set-up any additional channels at this point then the CJC selection will only offer the internal Thermistor for it's CJC reference or a user value defined one. If you wish to use a PT100 you will need to set this up in MAX first using the Virtual Channels. Once you have that working go back to the SCXI 1102 and configure the CJC reference as User Defined, you should then be able to use the PT100 channel that you have just created.
Side note: The 1102 has been designed to thermocouple measurements and the internal CJC should be accurate enough for general measurements.
Kind regards
Joe
NI-UK

Similar Messages

Noise in thermocouple measurement using PCI-6024E DAQ card

I am using a PCI-6024E DAQ card for thermocouple(TC) measurement. The
TC is installed in the mold cavity of an injection molding (IM)
machine. The leads from the TC are connected to the DAQ card using a
CB-68LP board. I made a temperature mesurment task in LabView 7.0
with the two leads from TC as differential inputs and used CJC value of
25 deg C.
The problem is that when the IM machine is OFF, I get a reasonable temp
reading with some slight noise but as soon as I turn ON the IM machine,
the temp readings go wild with a lot of variations around the mean
value. The temp values also don't go to higher values when the TC is in
contact with the molten plastic in the IM machine.
Do I need to ground something here or put a resistor in the I/O board?
BTW the IM machine is grounded and the TC give correct temp values when
connected to a hand-held temp reader.
Any help will be highly appreciated.

Hello Aftab,
Looks like you need to use bias resistors to reduce the noise. Check out the following tutorial for more information about how to use bias resistors.

Thermocouple measurment using NI 9219

I have a NI 9219 and an omega j type thermocouple,
When i connect the thermocouple to NI9219 terminal 4 and 6 ( positive and negative terminals) and open up Signal express I don't see the voltage change! is there something else that i need to do before i can see the measurments?

chrisger wrote:
you have to use terminals 4 and 5 for thermocouples. See page 11 on the user manual: http://www.ni.com/pdf/manuals/372407a.pdf
That is correct. In my experience (the little there is), thermocouples are almost always in adjacent terminals
Message Edited by Cory K on 01-02-2009 10:41 AM
Cory K

Type C thermocouple measurement and compesation with DAQmx

Need to make type C thermocouple measurment using DAQmx. Analog thermocouple channel configuration VI has spot for custom scales in the units box but nowhere to wire the scale. Want to use cold junction compensation so is the only option to use a voltage input then subtract the cold junction voltage and then run that value through a conversion formula?

That does not work. The program seems to already try and apply a scale since I get an error from start task that says the prescaled units are already Deg C, and the scale of course goes from volts to degrees. When I try to change the custom scale name after start task I get an error that says the units are invalid for this measurement type. So there seems to be some coding that won't allow you to replace the scale for a thermocouple measurement. I'll probably have to take voltage readings and apply the scale after I subtract the junction value which is unfortunate I have to do things that way.

Constructing Calculated Measures in MDX for different measures using same columns in a fact table

Hello,
i have a fact table with 2 columns corresponding to dimensions Dim1, Dim2. In the same table i have 4 other columns Value_Type(int), INT_VALUE(int), FLOAT_VALUE(float), TEXT_VALUE(string). There are a number of measures which are identified by Value_Type and
depending on their nature could be written in one of the 3 columns (INT_VALUE(int), FLOAT_VALUE(float), TEXT_VALUE(string)) Let's say Measure1 with Measure_Type=1 is age, 2 is account balance and 3 is Name for clarity. There could be other measure types that
use these 3 same columns for data. So the sample fact table looks like this
Dim1 Dim2 Measure_Type INT_VALUE FLOAT_VALUE TEXT_VALUE
10 10 1 25
10 10 2 2000,34
10 10 3 John
10 20 1 28
10 20 2 3490,23
10 20 3 Frank
My task is to write an MDX query for each Dim1, Dim2 combination which returns all 3 measures in the same row. The idea is to construct a calculated member for each Measure that returns value from the right field. For example for Measure1 we take INT_VALUE
with measure_type=1. The problem is i don't know how to construct MDX query for these calculated members. Can you please help me?
So my final goal is to write an MDX query that returns all measures in one row for each set of Dim1, Dim2
SELECT [Measure1], [Measure2], [Measure3] ON COLUMNS,
NON EMPTY [Dim1].[Dim1].[Dim1].Members*[Dim2].[Dim2].[Dim2].Members ON ROWS
FROM [Cube]
Dim1 Dim2 Measure1 Measure2 Measure3
10 10 25 2000,34 John
10 20 28 3490,23 Frank

Hi Kosmipt,
I would combine the "INT_VALUE", "FLOAT_VALUE" and "TEXT_VALUE" columns into one with STRING data type for the fact table. And there should be one dimension to store the Measure_Type informations. Then in cube, you can write MDX scope for every one of
"Measure_Type" dimension members. For example,
scope(
            [Measures].[M]
    [DimMType].[MType].&[1]= CINT([Measures].[M]);
end scope;
Once the cube is built by the above way, you can write MDX like something like the following to achieve your purpose.
WITH member [Measures].[Measure1] AS ([DimMType].[MType].&[1],[Measures].[M])
         member [Measures].[Measure2] AS ([DimMType].[MType].&[2],[Measures].[M])
         member [Measures].[Measure3] AS ([DimMType].[MType].&[3],[Measures].[M])
thanks,
Jerry

I am using garage band for the first time. I dragged and dropped a song from itunes into the program and I want to extend the length of the song by repeating the first 28 measures. I can't figure it out. Please help

I am using garage band for the first time. I dragged and dropped a song from itunes into the program and I want to extend the length of the song by repeating the first 28 measures. I can't figure it out. Please help. I have spent several hours trying to figure it out on my own but have not been successful. It seems like an easy task. Can anyone help?

dewin1or wrote:
I want to extend the length of the song by repeating the first 28 measures.
split the region at the 28th measure
http://www.bulletsandbones.com/GB/GBFAQ.html#split
(Let the page FULLY load. The link to your answer is at the top of your screen)
then select only the first region and option-drag it to the end of the song

I am using IMAQ vision for Measurement Studio, Ver6.0 with Measurement Studio Base Package,Ver6.0(Professional Edition).Can I work in IMAQ Vision for Measurement studio, Ver6.0 If I upgrade Measurement studio to Enterprise Edition,ver8.0.1

I am using IMAQ vision for Measurement Studio, Ver6.0 with Measurement Studio Base Package,Ver6.0(Professional Edition).Can I work in IMAQ Vision for Measurement studio, Ver6.0 If I upgrade Measurement studio to Enterprise Edition,ver8.0.1
Thanks
Biswajit

Howdy Biswajit,
The IMAQ and Vision ActiveX controls you are using with Visual Basic 6 do not install with Measurement Studio. They are installed when you install the IMAQ software and include support for Visual Studio 6. Upgrading to Measurement Studio 8.0.1 will have no effect on your IMAQ controls since they are not related to one another. Purchasing Measurement Studio Professional or Enterprise packages allows you Visual Studio 6 support for other ActiveX components. Refer to this link for a list of ActiveX components included in those packages.
If you are asking about using the ActiveX controls in .NET, then take a look at this KnowledgeBase entitled Do NI-IMAQ and NI Vision Support Microsoft Visual Studio .NET?
Hope this clarifies things!
Best Regards,
Jonathan N.
National Instruments

6602: How to use 8 counters simultaneously in C++ using traditional Daq for frequency measurement

Hi Everybody;
I'm new to Ni-DAQ cards and working on NI PCI-6602 Card in Borland C++, I should use Traditional DAQ for my project. Now I want to use all the 8 counters simultaneously for frequency measurement.
1.Where should I connect my External signal, to source or gate, at present I have connected to source.
2. How to set parameters and start the counters simultaneously, what are the parameters to be set for frequency measurement.
3.How to start counting.(parameter settings)
4.Should I set any PFI Lines or by default are they set to counters.
status = GPCTR_Set_Application (1, gpctrNum, ND_SIMPLE_EVENT_CNT)
status = GPCTR_Change_Parameter (1, gpctrNum, paramID, paramValue)
iStatus = GPCTR_Watch(1, gpctrNum, ND_ARMED, entityValue);
status = GPCTR_Watch (deviceNumber, gpctrNum,ND_COUNT, entityValue)
what is the paramID in my case, Clear and appropriate answers would be very helpful and thanks in advance.
Message Edited by Pavan K on 07-11-2009 12:38 AM

I have made a program with LabVIEW 5.1 based on NI 6602, in which four counters were used.
Counter 3 is used to generate pulses, which are directed to the gates of counter 0, 1 and 2.
The source terminals of counter 0,1 and 2 receive pulses, individually, to count how many pulses appear during the time interval of each gate pulse.
The results are stored in a data file.
In order to test its performance, only one signal of ramdom pulses is sent to counter 0,1 and 2.
But I find that at the beginning the counts for the three counters are the same, but the following counts are totally different!
What's wrong? And how to solve such a problem? Does it have something related with synchronization?
Thank you very much!

Thermocouple measurements that after a period of time suddenly go bad

Good Afternoon,
I originally posted this on the multifunction DAQ thread but haven't gotten any response. I don't think the problem is software but...
I'm making long term temperature measurements using a PCI6040E, SCXI1001, SCXI1102 32-channel thermocouple amp and a SCXI1303 isothermal block. These are making readings using J type t'couples. My customer's problem is that the measurements will be fine for a period of time (minutes, several hours) and then suddenly some channels will start giving really bogus temperatures, i.e.: -270 DegC vs the more realistic 35 DegC. I came in the last time it was doing this and when I went down into the code to my DAQ portion the DAQmx Read vi, set as analog, temperature, J type measurement was returning those numbers for the offending channels. Some were still giving valid numbers while others were giving the weird numbers and when a Fluke meter was used to measure the output of the "bad T'couple" it too was giving valid numbers. When I stop the LabVIEW program and go into DAQmx to try and troubleshoot it, there usually seems to be no problem. If I restart the LabVIEW program there also seems to be no problem, but when there is those numbers are coming out of the lowest level of code that I have programmed (the standard DAQmx read). I'm suspecting something "electromechanical" like connectors in/on the SCXI chassis, but the fact that it goes away when software is restarted is confusing me, as well as making troubleshooting difficult.
Thanks,
Putnam Monroe
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Like I said, you have a bear of a problem.
bad values at the lowest level I can access (in the LabVIEW program the actual DAQmx read, or running test panels in MAX).
That pretty much eliminates your LabVIEW code.
seem to remain bad until the SCXI-1001 chassis is reset
What exactly do you mean by "chassis is reset"? (I'm not a SCXI expert, but I do have a SCXI-1000 chassis here). There is no reset button. It's not hooked up at the moment, so I can't tell if there's a software "reset" function.
Do you mean power Off & On ?
Do you mean a reset button (maybe the 1001 has one, I don't know).
Do you mean a software reset from LabVIEW / Max ?
I don't see how any channel could hang up at 25°C and stay, that's not likely the top or bottom end of your TC range.
Possibly some sample/hold or track/hold amplifier quits sampling, and stays holding.
It IS about room temperature, I wonder if your CJC channel is somehow being read instead?
Ground loops would not likely be the problem, unless there's something else happening when the channels fail (like a welder firing). Even then, it's not likely that a rest would fix that.
My first thought would be to disassemble the SCXI stuff, and look for the usual suspects: dirty connectors, chips not in sockets, loose screw terminals, broken wires. Sounds like hardware to me.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Measuring temperature with RTDs over a long distance

I have created an application using the FP-RTD-122 to take RTD mearurements from multiple locations in a plant. The measurments are correct when the RTD leads are connected directly to the module (about 6ft). However when we wire the RTDs in the plant to the module, the measuremtns are incorrect. For instance the temerature is 79C at one location, but shows as between -193C and 19C in Measurment and Automation Explorer. The distance is about 150 ft. I have found a reference in the internet that suggests using a temperature transmitter that converts the RTD signal to a 4 to 20 mA signal. Does anyone have any experience with measuring RTD over long distances? Do I really need a temperature transitter? If so, do I need to use the FP-AI-111 module instead?

Nate,
RTDs allow temperature measurement by reading the resistance of a sensor. This is normally done by exciting the sensor with a known current and measuring the resulting voltage. There are three general types of RTDs; two-wire, three-wire, and four-wire. Two wire RTDs are less accurate because the wire resistance is indistinguishable from the sensor resistance. Three wire RTDs use two wires on one leg (one to carry the known current and one to measure the voltage) allowing one portion of the wire resistance to be nullified. 4 Wire RTDs use two wires on each leg (one for the excitation current) to nullify the wire resistance. As a result, 4 Wire RTDs are the best ones to use for high precision or long distance measurements. To measure 4 Wire RTDs with FieldPoint, you will need to use the [c]FP-RTD-124 module instead of the [c]FP-RTD-122. With that said, I do not know how well 4 wire RTDs will do at 150 feet. 4-20 mA transmitters will easily handle 150 feet so they will probably be your best option. To measure the 4-20 mA signal, you can use the [c]FP-AI-100, [c]FP-AI-110, [c]FP-AI-111, [c]FP-AIO-600, or [c]FP-AIO-610 modules.
Regards,
Aaron

[Forum FAQ] How do I create calculated measure using AMO in SQL Server Analysis Services?

Introduction
In SQL Server Analysis Services (SSAS), you can create a calculated measure in SQL Server Data Tool (SSDT)/Boniness Integrated Development Studio (BIDS). Sometimes you may need to create calculated measure by using AMO in a C# or VB project.
In this article, I will demonstrate so how to create calculated measure using AMO in SSAS?
Prerequisites
Before create calculated measure using AMO, you need to ensure that the following components were installed in your server.
The multidimensional database AdventureWorks Multidimensional Model 2012
A SQL Server with SSIS and SSAS installed
The AMO libraries installed:
X86 Package (SQL_AS_AMO.msi)
X64 Package (SQL_AS_AMO.msi)
Solution
Here is the detail steps to create calculated measure using AMO in SSAS.
Open SSDT and create a new SSIS project.
Drag Script Task to the design surface.
Click SSIS-> Variables to open the Variables window and add two variables that used to connect to the server and database.
Create a connection to connect to SSAS server.
Rename the connection name to ssas.
Double click the Script Task to open Script Task Editor.
Add Connection and Database variables to ReadWriteVariables textbox and then click Edit Script button.
Add AMO reference in the Solution Explore window.
Copy the script below and paste it into the script.
Dim objServer As Server
Dim objDatabase As Database
Dim strDataBaseID As String
Dim objCube As Cube
Dim objMdxScript As MdxScript
Dim objCommand As Command
Dim strCommand As String
objServer = New Server
objServer.Connect("localhost")
objDatabase = objServer.Databases("AdventureWorksDW2012Multidimensional-EE2")
strDataBaseID = objDatabase.ID
If objDatabase.Cubes.Count > 0 Then
objCube = objDatabase.Cubes("Adventure Works")
If objCube.MdxScripts.Count > 0 Then
objMdxScript = objCube.MdxScripts("MdxScript")
objMdxScript = objCube.MdxScripts(0)
Else
objCube.MdxScripts.Add("MdxScript", "MdxScript")
objMdxScript = objCube.MdxScripts("MdxScript")
End If
objCommand = New Command
strCommand = "CREATE MEMBER CURRENTCUBE.[Measures].[Multipy Measures By 3]"
strCommand = strCommand & " AS [Measures].[Internet Sales Amount] * 3, "
strCommand = strCommand & " VISIBLE = 1 ; "
objCommand.Text = strCommand
objMdxScript.Commands.Add(objCommand)
objMdxScript.Update()
objCube.Update()
End If
objServer.Disconnect()
Then you can run this SSIS package to create the calculated measure.
Applies to
Microsoft SQL Server 2005
Microsoft SQL Server 2008
Microsoft SQL Server 2008 R2
Microsoft SQL Server 2012
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Thanks,
Is this a supported scenario, or does it use unsupported features?
For example, can we call exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='b64ce7ec-d598-45cd-bbc2-ea202e0c129d'
in a supported way?
Thanks! Josh

How to use Value Mappings for simple translations?

Hello,
I want to use Value Mappings for simple translations in mappings, e.g. from IDoc to Inhouse structures.
For example unit of quantity:
IDOC    -->    INHOUSE
PCE               P
ABC               A
How can I use Value Mapping for this? What should be used as Agency, what should be used for Scheme? What about groups? I tried the following: I created a new Value Mapping in Integration Directory:
- Source Agency: DELVRY05
- Source Scheme: MENEE (IDoc field name)
- Target Acency: INHOUSE_DESADV (Name of structure)
- Target scheme: UNIT (Name of field)
Then, in the table, I added several lines for translating PCE to P and ABC to A and so on. But I have to define a group name for each line. I used INHOUSE. But than I get one INHOUSE group for each line.
This seems very complicated for simple translations from A to B. I don't want to use FixValue in Message mappings.
Any help appreciated.
Thanks,
Christoph

Hello,
@pavan kumar: Thanks, but I know all Blogs about Value Mappings. That does not help me. And I refer to PI 7.1.
Lets get it very simple: I want to have exactly the same functionality of "FixValues" as ValueMappings. In 7.1, I need to define a Group for every row / line in the conversion table (e.g. for units of measurement conversion between IDoc and FlatFile). That does not make sense for me, as the Group is always the same, e.g. "Unit of measurement". So I will get dozens of same groups called "Unit of measurement".
I don't really understand the concept of Groups. Maybe this is just not appropiate for my intenses? Maybe the Group has to be defined as one specific value of Unit of measurement, e.g. "pieces"?
CHRISTOPH

Using CASE WHEN for Essbase column in OBIEE 11g

Hi all,
I have a business model in OBIEE 11g, taking the source from Essbase 11. The measures of the Essbase cube in the physical layer is flattened, and the aggregations for the measures are set to SUM.
The Product dimension has 5 generations. In Product logical table, I created a logical column called "Product Grouping" using a simple CASE WHEN formula:
CASE
WHEN "TEST"."Product"."Gen5,Product" IN ('100-10', '100-20', '200-10', '300-10') THEN 'Group 1'
WHEN "TEST"."Product"."Gen5,Product" IN ('100-30', '200-20') THEN 'Group 2'
ELSE 'Group 3'
END
Problems:
1. If I don't place this "Product Grouping" in the logical level/hierarchy, I got error in the report when I simply show Product Grouping and a measure.
2. If I place this "Product Grouping" in the logical level/hierarchy (on the 5th level), no more error in the report when I simply show "Product Grouping" and a measure. The measure value also shows the correct SUM (group by). However, when I add "Gen1,Product" the "Product Grouping" and the measure value suddenly becomes not grouped by.
Has anyone ever tried and encountered something like this? Any thoughts?
Thank you very much!

Hi Deepak, thansk for the suggestion.
However, I can't use calculated item for this report because:
1. incorrect result will be shown when my measures involve a formula to derive a percentage value.
2. calculated item is not available if we do "combine requests" (or union) in 11g.
Any thoughts anyone on how to solve this? Is this just me, or it's a bug?
Thank you very much.

Issue: Proportion/produciton unit of measure NO is invalid for item 900001.

Hi All,
Issue: Proportion/produciton unit of measure NO is invalid for item 900001.
Here we have MTO Scenario: In outbound delivery when we do batch split & batch determination we are getting the above error.
Consider the following settings: at MM01 - Prodution/Proportion unit data is maintained with a characterstic specific to batch. Means Batch specific unit of measurement. In Work scheduling view produciton unit, unit of issue are maintained as 'NO'. All these settings are same for all material codes.
Please suggest us why we are getting the issue for perticular material coce.
Info: We resolve the issue by adding one more line item in the sales order & do the transfer posting the stock from line item to line item. But this is not the permanent solution.
Regards
Chowdary

I believe the error message no is VL 382 (Proportion/product unit of measure & invalid for item &)
You need to double click on the error message flashing on the status bar to get the error number.
I believe long text for the error message is self explainatary. Refer it and make necessary changes to resolve the issue.
Diagnosis
You want to use a proportion / product unit for an item.
You are not allowed to change the unit of measure into a proportion / product unit if:
- The following exist for a sales document item:
Preceding documents
Subsequent documents
- You are processing a scheduling agreement for the component supply industry
- You change the target unit of measure in a scheduling agreement item (and the sales unit is not a proportion / product unit)
- You are processing a customer requirements plan
- The following exist for a delivery item:
Preceding documents
Subsequent documents
Batch split items
- You are processing a batch split item
Procedure
Use a different unit of measure.
If you want to change the target unit of measure into a proportion / product unit in a scheduling agreement item, you need to change the sales unit accordingly. The system then sets the target unit of measure to the same as the sales unit.
Further, if you are working on older version, refer SAP Note 364206 - VLSP:indic.for proportion/product quantities deletd.
Regards
JP

Error message :PurchOrder : Unit of measure PC not defined for language ES,

Hello,
I am facing a problem with PO replication to R/3 backend.
POs are not replicated to R/3, POs are in status 'Transfer Failed (E.Sys.)' .
When I check with 'RZ20' transaction I got this message :
PurchOrder : Unit of measure PC not defined for language ES.
SRM 4.0 Extended classic scenario
Regards,
Shaiek

Hi
This seems to be a configuration issue,.
Pls maintain the unit of measure in configuration using transaction CUNI
Hope this will help.
Pls reward suitable points.
Regards
- Atul

Thermocouple Measurements using an RTD for CJC

Similar Messages

Maybe you are looking for