LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

MCC DAQ Temperature Input No Physical Channels

Hi,

 

I hope someone can help me out here. Recently, I purchased the USB-2408-2A0 from Measurement Computing. There are no channels for my to select when a "
Create channel" of temperature input is created. However, this works fine for other inputs, such as analog or digital.

 

I've tried every possible solution on the internet to troubleshoot this problem. However, to no avail.

 

Here is an example of what I wish to accomplish: Reading temperature input

 

Thank you,

Ashton

0 Kudos
Message 1 of 9
(5,676 Views)

I'm assuming you followed all of the steps shown in the YouTube video, right?  I'm guessing that you are confused about how to set the Front Panel Control.

 

To find the appropriate value for the Control, you need to know how LabVIEW names your device.  Have you ever used MAX (the Measurement and Automation eXplorer, which (when you installed LabVIEW's Device Drivers should have appeared as an Icon on your PC's Desktop)?  If you fire up MAX, you can ask it to show your the Devices plugged into your PC.  Find your device and notice the name MAX gives it (possibly "Dev1").  Double-click the device to open it in MAX.  Now play around with it -- you can start it, configure it, see what it does and how it works.  If it has specific channels to which you have wired a sensor, you can ask it to read (and plot) that channel and see if you are able to get meaningful readings.

 

Now, when you go to configure the Front Panel Control for your LabVIEW code, simply choose the same Device and Channel information that you used in MAX.  Give it a try, and let us know if you were successful!

 

Bob Schor

0 Kudos
Message 2 of 9
(5,643 Views)

I do have basic knowledge of LabVIEW. I intend to use my DAQ device from Measurement Computing (MC) with LabVIEW. Since I'm not using an official NI DAQ device, I believe the problem might be stemming from the drivers or some sort?

 

Reiterating my problem as spoken above, I intend to create a temperature input channel as shown in the youtube video. However, no channels are shown. I've tried all the listed solutions in this link: Solutions.

 

And, no, I believe NI Max wouldn't be able to detect any 3rd party devices other than NI's very own DAQ devices.

 

Thank you,

Ashton

0 Kudos
Message 3 of 9
(5,628 Views)

@hahaashton wrote:

And, no, I believe NI Max wouldn't be able to detect any 3rd party devices other than NI's very own DAQ devices.

 


The Good News, Ashton, is your "belief" is Wrong.  As a first approximation, if there's a Driver for it (and you can "talk" to it with LabVIEW), then MAX can "see" it.  I have a colleague who has several non-NI USB devices (SensorDAQ and others) that MAX sees.  On my system, I have two non-NI cameras that both show up in MAX (complete with the identification of the manufacturer).

So if you do NOT see it in MAX, then you are probably missing the Device Driver, and won't be able to use it with LabVIEW.

 

Bob Schor

0 Kudos
Message 4 of 9
(5,610 Views)

Sorry for the late reply. Just found out that MCCDaq doesn't support NI Max, which is a real bummer... Source

 

I'm desperately trying to find out why the physical channels aren't shown when AI Temperature is selected only. I've even tried using my DAQ on my other computer, and it still doesn't work.

 

 

0 Kudos
Message 5 of 9
(5,544 Views)

Thanks, I stand corrected.  I just looked at MCC's videos, and their LabVIEW "ULx" drivers are such copies of DAQmx that I'm sure some lawyers are earning money over this ...

 

It does look, however, that one should be able to use MCC's device as though they were DAQmx (except without getting MAX to help -- you'll need to use their InstaCal, or whatever the name is, Utility, I guess).  They show some very clear, very elementary examples that you should have been able to copy.

 

But we haven't seen your code, so can't easily say "Oh, you forgot a wire" or "That's not how that function works".  So to provide useful help, please do the following:

  • Attach the VI (actual code, please, no pictures) that fails.  Don't worry that we can't run it because we lack hardware and drivers.
  • Describe in as much detail as possible what happens when you run the code.  [Note -- as some have said on this forum, the code will do exactly what you tell it to do, so feel free to also tell us what you want it to do].  If there are error messages, feel free to attach a picture of the Error Message (or type it in carefully, making sure to get the Sign of the Error number correct).

With these, we should be able to quickly suggest either a fix or something to try that will help you out.

 

Bob Schor

0 Kudos
Message 6 of 9
(5,526 Views)

@Bob_Schor wrote:

Thanks, I stand corrected.  I just looked at MCC's videos, and their LabVIEW "ULx" drivers are such copies of DAQmx that I'm sure some lawyers are earning money over this ...



Probably not.  MCC is owned by NI.

0 Kudos
Message 7 of 9
(5,517 Views)

Aha -- very interesting.  So why can't MCC devices be "seen" and tested with MAX?

 

BSchor

0 Kudos
Message 8 of 9
(5,511 Views)

Maybe one day it will.  But it seems like NI is keeping MCC as an independent entity.

0 Kudos
Message 9 of 9
(5,505 Views)