Jump to content

John Brock

Members
  • Posts

    16
  • Joined

  • Last visited

John Brock's Achievements

Member

Member (2/4)

0

Reputation

  1. No exact examples on setting the TC Type for the USB-2001-TC in python on Windows so here is what works in case it helps someone else: from mcculw import ul from mcculw.enums import ULRange from mcculw.ul import ULError board_num = 0 channel = 0 scale = 1 # for setting scale parameter to Fahrenheit dev_num = 0 info_type = 2 #2 sets BOARDINFO CHANTCTYPE = 347 #needed to point set_config options to change the TC type TCType = 2 #B=7, E=4, J=1, K=2, N=8, R=5, S=6, T=3 # Set thermocouple type to type K ul.set_config(info_type, board_num, dev_num, CHANTCTYPE, TCType) try: # Get a value from the device value = ul.t_in(board_num,channel,scale) # Display the value print("Value = " + str(value)) except ULError as e: util.show_ul_error(e)
  2. Thank you for the response. Yes, I can't get any of those examples to work on Windows for this board yet. For Linux, I'm using the uldaq package and was hoping to be able to build drivers on Windows that work with that module so there would be no rewrite on my code. I'll keep working on it.
  3. I have a python program working on a raspberry pi OS installation and now need to mod it to run on Windows for a client who prefers to use a PC. I can't find the right drivers, modules, settings to make the python code work on Windows. Any tips for porting this?
  4. Just to close up this item: the filter did indeed cause a non-linear off-set as you predicted so I returned it. The good news is the USB-2001-TC has fixed the problems of EMF interference above 1000C. I finished testing last night and it worked beautifully to 1200C. This is a good solution for us (and the other USB devices) since they can be used with any computer rather than just the Raspberry Pi hat products. Thanks again for all the help on this issue!
  5. I got it to work with just this: #daq_device.get_config() ai_device = daq_device.get_ai_device() ai_config = ai_device.get_config() ai_config.set_chan_tc_type(0, TcType.K)
  6. Thank you for clarifying that. I'll use the python code. I get this output, however, when I run the example code you sent " Found 1 DAQ device(s): Error: No USB-TC found. Can't debug why this is happening. Can you help me find just the minimum code to set the TcType. The example contains a lot of checking that may not be needed.
  7. Very helpful. Thank you. Can you please confirm that once set, the TcType.K is stored on the device and does not need to be reset? This is the way I read the manual.
  8. Thank you very much. It's on Linux (Raspberry Pi). Does that make any difference?
  9. I have a USB-2001-TC. I don't use the packaged software but use the python API. How do I set the thermocouple type to Type K using python? I understand the type is stored on the device but can't find how to set it.
  10. I see your points on using the filter. I have tried shielded TC wire. Tried both grounding the shield only at the measurement site to the equipment and then only to the ground pins on the Raspberry Pi. No effect. I then switched to unshielded wire which actually goes to a little higher temp before common mode errors show up. Thank you for continuing to work on this with me. Any other ideas?
  11. Thank you for the information. I'd like to use the MCC 134 if possible because this is a test case for a decision. The other applications we have are less demanding so the MCC134 is economical and I'd like to standardize on those. Do you think one of these might help? https://lookingforsolutions.com/collections/thermocouple/products/thermocouple-connector-mv-v-with-noise-reduction-filter-board-model-lfs110-series
  12. Thank you JRys for the idea. This may very well be the issue. It makes perfect sense with the phenomenon I'm seeing. I'd like to not loose my investment in the MCC134 board if possible. Is there any sort of conditioning that could be used with the the Type K and keep it in a format compatible with the MCC134? Maybe something in software?
  13. The tip of the TC rods are welded. The other end of the thick rod leads are clamped in the terminal block with a screw. See photo. I have run both short continuous TC wire to the TC and am now using the mini connector show below - so 1 additional connection in the plug. Same problem appears when I used the short wire with no connectors. Thank you very much for debugging this with me!
  14. N,o the wire would not be hot at the MCC board. I have a monitoring TC there at the board and it's never over 78F. At the measuring end, however it could get hotter. The TC sticks through the kiln and terminates on a ceramic block insulator. There are screw terminals for the TC wires. It's possible this is terminal block and wiring is get pretty hot. I have not been around when the kiln was at max temp but have found the terminals still hot sometime later. At what temperature might that cause problems? Is there a way we can compensate for it? I used actual Type K wire rather than extension wire back to the MCC.
  15. Thank you Fausto for your response. The TC tip is in air, not touching anything and fully insulated from the vessel being measured (electric ceramic kiln). I have tried multiple iterations of shorter wire (down to 4 feet, direct connected with no connectors and up to 15 feet with one set of mini-plugs). Exactly the same result in all cases. No other equipment comes on during the firing so all is consistent there. There are two other Type K TC's on the board running near room temp. I have also tried it with those disconnected. Any other ideas? Thanks again for responding. JB
×
×
  • Create New...