TC-32

1 year is the recommended calibration cycle. Measurement Computing uses NIST traceable calibration equipment. The cost to calibrate the TC-32 comes to $463.80 and includes a calibration certificate. Calibrations, barring any issues with the device, generally take approximately 3 weeks. Due to the test equipment needed to calibrate the TC-32 (test stand), third party calibration is not available. However, you can use a third party calibration laboratory to verify and certify our calibration.

Was this answer helpful? Yes (0) / No (0)

Sorry, communication with the TC-32 is through our proprietary software and/or drivers.

Was this answer helpful? Yes (1) / No (0)

The TC-32’s hardware-based alarms (configured in InstaCal, not in your program) have one-to one mapping, between its 32 thermocouple channels and its 32 DO bits, hence the hardware-based alarm capability cannot achieve what you describe. However, in your custom program, you could decide in your code when to turn on/off a single digital output bit (i.e. you could achieve your goal via your own software-based alarm strategy).

Was this answer helpful? Yes (1) / No (0)

As detailed in our previous answer the TC-32’s architecture only supports reading the data via software polling. However each enabled thermocouple input is sampled continuously and converted at the maximum A/D converter rate of 3 Hz per channel (max). The best approach for continuously reading your data within LabVIEW would to put our ULx Read.VI in a “Timed Loop” structure.

Was this answer helpful? Yes (1) / No (0)

The TC-32 architecture supports only software-paced readings (hence the error when you try to specify a clock rate). While the TC-32 architecture has a “voltage” mode (which is of the range +/- 78 mV), it is not supported in ULx. If you wish you measure millivolts in LabVIEW with the TC-32, then please contact our Technical Support folks, who can provide you an example of a workaround (how to call our underlying UL from within LabVIEW).

Was this answer helpful? Yes (1) / No (0)

The physical CD you are installing from appears to pre-date the release of our LabVIEW 2016 compatible ULx driver. Instead, download the latest MCCDAQ software suite from our website, and it will install properly on LabVIEW 2016.

Was this answer helpful? Yes (1) / No (0)

Yes, DASYLab can communicate with multiple DAQ devices at the same time. You will have no conflicts using an IOtech DaqLab/2001 and a TC32 in the same DASYLab program. Both drivers are compatible with each other.

Was this answer helpful? Yes (3) / No (0)

The TC-32 is currently supported by the Universal Library Python API for Windows. More information is available at: https://www.mccdaq.com/daq-software/Python-Support.aspx

Was this answer helpful? Yes (3) / No (0)

Hello JB - MCC does not currently have formal python support or examples. Some customers have called our Universal Library’s DLL from Python, and several have posted their efforts on the internet

Was this answer helpful? Yes (3) / No (0)

The current MATLAB driver set does not have support for the TC-32. However, Mathworks is actively developing 64-bit drivers to support MCC products in MALAB version R2016. For more information, or to request support for a specific device please contact the Mathworks at www.mathworks.com/support/contact_us

Was this answer helpful? Yes (3) / No (0)

Yes, multiple TC-32/TC-32-EXP configurations can be used to obtain additional temperature inputs. The TC-32/TC-32-EXP is compatible with 10Base-T or 100Base-TX Ethernet ports, hubs, or switches.

Was this answer helpful? Yes (3) / No (0)