10-12-2007 09:20 AM
10-15-2007
01:18 PM
- last edited on
12-09-2008
10:53 AM
by
Support
Message Edited by Neal M on 10-15-2007 01:19 PM
10-15-2007 04:24 PM
10-16-2007 04:59 PM - edited 10-16-2007 04:59 PM
Message Edited by Neal M on 10-16-2007 05:00 PM
Message Edited by Neal M on 10-16-2007 05:00 PM
11-08-2007 02:20 PM
11-11-2007
12:41 PM
- last edited on
12-09-2008
10:54 AM
by
Support
11-12-2007 08:38 AM
Thanks, I will look some of these things over, although I have been trying to work from the manual when trying to fix the problem.
When I thought it was fixed, I had set up the labview to read the voltage of the TC and then I had multiplied that by 10 (since it says the module provides a gain of 100). That seemed to allow the TC to react similar to how I thought it should to changes in temperature. However, I also had to provide an offset which changed each time I started the VI again (it could be due to changes in ambient temp). I also noticed that still the voltage always remains the same sign even if I change the polarity of the wires (this is puzzling).
I am using the 'new' labview routines. I have set up TC before with no problem, but that was using the old 'classic' labview.
Thanks,
ROb
11-13-2007 06:47 PM
Hi Rob,
You mentioned that the offset voltage you had to provide in your program changed each time you started the VI, and indicated that this was possibly due to changes in ambient temperature. This would be compensated by the CJC sensor, which is built into your SCC-TC01. Since MAX does not allow you to select the built in CJC Sensor, the SCC may be configured incorrectly, possibly due to the SCC-TC01 being assigned to the incorrect port or some other mistake. You did not mention in your previous post the results of going through the quick start guide and ensuring the configuration is correct. This would be a helpful trouble shooting step. Since the device is for signal conditioning, if the configuration is off, the resulting data will be off.
You had also mentioned that you are using the “new” LabVIEW routines. If you are referring to programming with DAQmx instead of Traditional DAQ, this will not be a concern. In MAX, where the test panels are being run, it does not matter if you were using DAQmx or DAQ, since the test panel is looking at the actual hardware.
I hope that this helps. Please let me know if you have any further questions I can clarify or if this solution does not take care of your missing VI issue. Thanks-
Mallori M
11-27-2007 04:21 PM
11-28-2007 03:06 PM